[Desktop-packages] [Bug 1502717] [NEW] wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
Public bug reported: wpa_supplicant crashed with SIGSEGV when removing kernel module brcmfmac. rsalveti@evapro:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Wily Werewolf (development branch) Release:15.10 Codename: wily Linux evapro 4.2.0-14-generic #16-Ubuntu SMP Fri Oct 2 05:14:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux MacBook Pro Retina 13' 12,1 43557 Oct 4 18:02:56 evapro kernel: [ 86.406354] usbcore: deregistering interface driver brcmfmac 43558 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing workstation service for wlp3s0. 43559 Oct 4 18:02:57 evapro NetworkManager[936]: devices removed (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlp3s0, iface: wlp3s0) 43560 Oct 4 18:02:57 evapro NetworkManager[936]: (wlp3s0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] 43561 Oct 4 18:02:57 evapro NetworkManager[936]: (wlp3s0): failed to disable userspace IPv6LL address handling 43562 Oct 4 18:02:57 evapro gnome-session[2190]: (nm-applet:2346): GLib-CRITICAL **: Source ID 190 was not found when attempting to remove it 43563 Oct 4 18:02:57 evapro NetworkManager[936]: radio killswitch /sys/devices/pci:00/:00:1c.2/:03:00.0/ieee80211/phy0/rfkill0 disappeared 43564 Oct 4 18:02:57 evapro kernel: [ 86.947963] show_signal_msg: 39 callbacks suppressed 43565 Oct 4 18:02:57 evapro kernel: [ 86.947968] wpa_supplicant[1330]: segfault at 0 ip 7f835170fcba sp 7fffc00140c8 error 4 in libc-2.21.so[7f835167+1c] 43566 Oct 4 18:02:57 evapro NetworkManager[936]: wpa_supplicant stopped 43567 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): supplicant interface state: completed -> down 43568 Oct 4 18:02:57 evapro NetworkManager[936]: (NetworkManager:936): GLib-CRITICAL **: Source ID 167 was not found when attempting to remove it 43569 Oct 4 18:02:57 evapro NetworkManager[936]: Failed to GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.30 was not provided by any .service files: remove network. 43570 Oct 4 18:02:57 evapro dbus[969]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' 43571 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): device state change: activated -> unavailable (reason 'supplicant-failed') [100 20 10] 43572 Oct 4 18:02:57 evapro systemd[1]: Started WPA supplicant. 43573 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): canceled DHCP transaction, DHCP client pid 1915 43574 Oct 4 18:02:57 evapro NetworkManager[936]: (wlx048d38ab601a): DHCPv4 state changed bound -> done 43575 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for 192.168.1.17 on wlx048d38ab601a. 43576 Oct 4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on interface wlx048d38ab601a.IPv4 with address 192.168.1.17. 43577 Oct 4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv4 no longer relevant for mDNS. 43578 Oct 4 18:02:57 evapro avahi-daemon[950]: Withdrawing address record for fe80::68d:38ff:feab:601a on wlx048d38ab601a. 43579 Oct 4 18:02:57 evapro avahi-daemon[950]: Leaving mDNS multicast group on interface wlx048d38ab601a.IPv6 with address fe80::68d:38ff:feab:601a. 43580 Oct 4 18:02:57 evapro avahi-daemon[950]: Interface wlx048d38ab601a.IPv6 no longer relevant for mDNS. 43581 Oct 4 18:02:57 evapro NetworkManager[936]: Writing DNS information to /sbin/resolvconf 43582 Oct 4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus 43583 Oct 4 18:02:57 evapro dnsmasq[1607]: using nameserver fe80::e6f4:c6ff:fe0b:5c4d#53 43584 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: https://daisy.ubuntu.com 43585 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] offline 43586 Oct 4 18:02:57 evapro whoopsie[994]: [18:02:57] Cannot reach: https://daisy.ubuntu.com 43587 Oct 4 18:02:57 evapro NetworkManager[936]: Writing DNS information to /sbin/resolvconf 43588 Oct 4 18:02:57 evapro dnsmasq[1607]: setting upstream servers from DBus 43589 Oct 4 18:02:57 evapro NetworkManager[936]: NetworkManager state is now CONNECTED_LOCAL 43590 Oct 4 18:02:57 evapro NetworkManager[936]: NetworkManager state is now DISCONNECTED 43591 Oct 4 18:02:57 evapro nm-dispatcher: Dispatching action 'down' for wlx048d38ab601a 43592 Oct 4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Main process exited, code=dumped, status=11/SEGV 43593 Oct 4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Unit entered failed state. 43594 Oct 4 18:02:57 evapro systemd[1]: wpa_supplicant.service: Failed with result 'core-dump'. 43595 Oct 4 18:02:58 evapro gnome-session[2190]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. 43596 Oct 4 18:02:58 evapro org.freedesktop.Notifications[2012]: ** Message: resizing pixbuf to 44 ProblemType: Crash
[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store
Basically we need to change pulseaudio in a way it can ask trusty store for the right permission when starting the recording process. Please ping tvoss to know more about how that can be done at the trust-store level, since there are some examples in the trust-store project. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1224756 Title: Pulseaudio should integrate with trust-store Status in the base for Ubuntu mobile products: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Currently the 'audio' policy group allows access to pulseaudio which allows apps to use the microphone and eavesdrop on the user. Pulseaudio needs to be modified to use trust-store, like location- service does. Integrating with trust-store means that when an app tries use the microphone via pulseaudio, pulseaudio will contact trust-store, the trust-store will prompt the user (Foo wants to use the microphone. Is this ok? Yes|No), optionally cache the result and return the result to pulseaudio. In this manner the user is given a contextual prompt at the time of access by the app. Using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in settings. Targeting to T-Series for now, since the trust-store is not in a reusable form yet. Original description: David and the security team (inspired by an observation from Rick) discussed that when recording, pulseaudio should somehow unobtrusively show the user that it is recording. The easiest thing to do would be for pulseaudio to alert indicator-sound which would then turn its icon red (similar to indicator-message turning blue with new messages). Marking 'high' because apps with access to pulseaudio can currently eavedrop on users. If the app is allowed to do networking (the default for apps), then it can ship that information off to a server somewhere. Note 1, the alert to indicator-sound must happen via the out of process pulseaudio server and not the confined app itself to be effective. Note 2, we should consider how to enforce this for foreground apps only. Application lifecycle should probably handle this for 13.10 (apps are suspended if not in foreground or if the screensaver is on), but we don't want an app on the converged device to record in the background when the user isn't paying attention. Example eavesdropping attack: start recording only when the screensaver is on (perhaps inhibiting the screensaver during recording would be enough). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455107] Re: Creating and destroying SoundEffects causes crashes
** Also affects: qtmultimedia-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1455107 Title: Creating and destroying SoundEffects causes crashes Status in pulseaudio package in Ubuntu: Confirmed Status in qtmultimedia-opensource-src package in Ubuntu: New Bug description: I keep on receiving bug reports about Machines vs. Machines being crashy on Ubuntu Phones and I tracked it down to the SoundEffect item. When playing without sound effects enabled, the game seems very stable. To get to the bottom of this I created an app that simulates a bit how a game works with sound effects. It's a bit more aggressive than Machines-vs-Machines (still not really far fetched from a real game scenario) and reliably triggers some crashers in less than a minute here. So far I've seen crashes in creating SoundEffects items as well as removing them from the scene. Please find the example here: lp:~mzanetti/+junk/soundcrasher You should be able to run it on any vivid powered device by just opening the .pro file in QtCreator and hit the play button. The logs vary a lot between crashes. Sometimes I get some PulseAudio messages, sometimes it just crashes without any. Probably some raciness. Anyhow, this example app should be give the system a hard time and reveal most of the crashes eventually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1455107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1426923] Re: Allow ubuntu-system-settings to set a device's firmware
** Package changed: wpasupplicant (Ubuntu) = lxc-android-config (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpasupplicant in Ubuntu. https://bugs.launchpad.net/bugs/1426923 Title: Allow ubuntu-system-settings to set a device's firmware Status in lxc-android-config package in Ubuntu: In Progress Bug description: Background: To do Wi-Fi hotspots on krillin, we need to poke wifi by doing a call to wpa_supplicant's (undocumented/local) SetInterfaceFirmware method. See [1] for details. Rationale: Ubuntu System Settings needs to do the same things as aforementioned script, but via dbus [2], as phablet/current non-privileged user and unconfined. What happens: If phablet runs [2], this error message [3] is produced, which I interpret to be equivalent with you're not welcome here. What should happen instead: Ubuntu System Settings should be able to make the call to wpa. [1] http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py [2] gdbus call --system -d fi.w1.wpa_supplicant1 -o /fi/w1/wpa_supplicant1 -m fi.w1.wpa_supplicant1.SetInterfaceFirmware / ap [3] http://pastebin.ubuntu.com/10489519/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1426923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store
Please move this to ww21. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1224756 Title: Pulseaudio should integrate with trust-store Status in the base for Ubuntu mobile products: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Currently the 'audio' policy group allows access to pulseaudio which allows apps to use the microphone and eavesdrop on the user. Pulseaudio needs to be modified to use trust-store, like location- service does. Integrating with trust-store means that when an app tries use the microphone via pulseaudio, pulseaudio will contact trust-store, the trust-store will prompt the user (Foo wants to use the microphone. Is this ok? Yes|No), optionally cache the result and return the result to pulseaudio. In this manner the user is given a contextual prompt at the time of access by the app. Using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in settings. Targeting to T-Series for now, since the trust-store is not in a reusable form yet. Original description: David and the security team (inspired by an observation from Rick) discussed that when recording, pulseaudio should somehow unobtrusively show the user that it is recording. The easiest thing to do would be for pulseaudio to alert indicator-sound which would then turn its icon red (similar to indicator-message turning blue with new messages). Marking 'high' because apps with access to pulseaudio can currently eavedrop on users. If the app is allowed to do networking (the default for apps), then it can ship that information off to a server somewhere. Note 1, the alert to indicator-sound must happen via the out of process pulseaudio server and not the confined app itself to be effective. Note 2, we should consider how to enforce this for foreground apps only. Application lifecycle should probably handle this for 13.10 (apps are suspended if not in foreground or if the screensaver is on), but we don't want an app on the converged device to record in the background when the user isn't paying attention. Example eavesdropping attack: start recording only when the screensaver is on (perhaps inhibiting the screensaver during recording would be enough). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
Yup, modem is online just fine, the side effect is the same described by Alfonso (and you at comment #5). Modem is online, powered and attached, without any active context. current build number: 179 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2010-01-01 01:29:38 version version: 179 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
And works fine after a reboot (still with wifi disabled). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
Just tested again and was again able to reproduce on mako:
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ ./list-modems
[ /ril_0 ]
Revision = M9615A-CEFWMAZM-2.0.1700.98
Serial = 353918052313257
Online = 1
Type = hardware
Features = ussd net gprs sms rat sim
Emergency = 0
Model = Fake Modem Model
Lockdown = 0
Powered = 1
Interfaces = org.ofono.CallBarring org.ofono.CallSettings
org.ofono.SupplementaryServices org.ofono.NetworkRegistration
org.ofono.ConnectionManager org.ofono.Phonebook org.ofono.CallForwarding
org.ofono.SmartMessaging org.ofono.PushNotification org.ofono.MessageManager
org.ofono.NetworkTime org.ofono.MessageWaiting org.ofono.RadioSettings
org.ofono.SimManager org.ofono.CallVolume org.ofono.VoiceCallManager
Manufacturer = Fake Manufacturer
[ org.ofono.CallBarring ]
VoiceIncoming = disabled
VoiceOutgoing = disabled
[ org.ofono.CallSettings ]
CallingLineRestriction = off
CalledLinePresentation = disabled
CallingLinePresentation = enabled
HideCallerId = default
ConnectedLineRestriction = unknown
ConnectedLinePresentation = unknown
VoiceCallWaiting = enabled
CallingNamePresentation = unknown
[ org.ofono.SupplementaryServices ]
State = idle
[ org.ofono.NetworkRegistration ]
CellId = 3198203
Technology = umts
MobileCountryCode = 724
LocationAreaCode = 40248
Status = registered
MobileNetworkCode = 06
Mode = auto
Name = VIVO
Strength = 45
[ org.ofono.ConnectionManager ]
Attached = 1
Powered = 1
RoamingAllowed = 0
Bearer = hspa
Suspended = 0
[ org.ofono.Phonebook ]
[ org.ofono.CallForwarding ]
ForwardingFlagOnSim = 0
VoiceNoReplyTimeout = 30
VoiceNoReply = +550174891818716
VoiceUnconditional =
VoiceBusy = +550174891818716
VoiceNotReachable = +550174891818716
[ org.ofono.SmartMessaging ]
[ org.ofono.PushNotification ]
[ org.ofono.MessageManager ]
ServiceCenterAddress = +550112102010
Alphabet = default
Bearer = cs-preferred
UseDeliveryReports = 0
[ org.ofono.NetworkTime ]
[ org.ofono.MessageWaiting ]
VoicemailMailboxNumber = *555
VoicemailMessageCount = 0
VoicemailWaiting = 1
[ org.ofono.RadioSettings ]
TechnologyPreference = umts
FastDormancy = 0
ModemTechnologies = gsm umts
[ org.ofono.SimManager ]
BarredDialing = 0
CardIdentifier = 89551090318161348308
FixedDialing = 0
MobileNetworkCode = 06
Retries =
LockedPins =
SubscriberIdentity = 724064900113482
PinRequired = none
MobileCountryCode = 724
ServiceNumbers = [Policia] = '190' [Defesa Civil] = '199' [Bombeiros] =
'193' [Vivo no Mundo] = '+551139598262' [Vivo] = '*8486' [Ambulancia] = '192'
SubscriberNumbers = +554891818716
Present = 1
PreferredLanguages = pt es en
[ org.ofono.CallVolume ]
SpeakerVolume = 0
MicrophoneVolume = 0
Muted = 1
[ org.ofono.VoiceCallManager ]
EmergencyNumbers = 08 000 999 110 112 911 118 119
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ ./list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Active = 0
Password = vivo
Preferred = 0
MessageCenter = http://termnat.vivomms.com.br:8088/mms
MessageProxy = 200.142.130.104:80
IPv6.Settings = { }
AccessPointName = mms.vivo.com.br
Protocol = dual
Name = Vivo MMS
Username = vivo
Settings = { }
Type = mms
[ /ril_0/context2 ]
AccessPointName = zap.vivo.com.br
Protocol = dual
Active = 0
Name = Vivo Internet
Username = vivo
Preferred = 0
Type = internet
Settings = { }
Password = vivo
IPv6.Settings = { }
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ ifconfig
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1039 errors:0 dropped:0 overruns:0 frame:0
TX packets:1039 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:109170 (109.1 KB) TX bytes:109170 (109.1 KB)
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ system-image-cli -i
current build number: 180
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-21 19:27:48
version version: 180
version ubuntu: 20150421.1
version device: 20150210
version custom: 20150421.1
phablet@ubuntu-phablet:/usr/share/ofono/scripts$ dpkg -l | grep network-manager
ii network-manager 0.9.10.0-4ubuntu15
[Desktop-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
It seems NM was trying to connect, but that never actually succeeded: Apr 21 21:47:01 ubuntu-phablet NetworkManager[1518]: debug [1429652821.190832] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... Apr 21 21:49:01 ubuntu-phablet NetworkManager[1518]: debug [1429652941.287746] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... Apr 21 21:51:01 ubuntu-phablet NetworkManager[1518]: debug [1429653061.188103] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... Apr 21 21:53:01 ubuntu-phablet NetworkManager[1518]: debug [1429653181.282422] [nm-modem-manager.c:205] poke_modem_cb(): Requesting to (re)launch modem-manager... ** Attachment added: syslog on mako, after reproducing the issue https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+attachment/4380844/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1433563] Re: QAudioRecorder recording hangs
** Package changed: pulseaudio (Ubuntu) = gst-plugins-good0.10 (Ubuntu) ** Also affects: qtmultimedia-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1433563 Title: QAudioRecorder recording hangs Status in gst-plugins-good0.10 package in Ubuntu: New Status in qtmultimedia-opensource-src package in Ubuntu: New Bug description: Recording audio with QAudioRecorder intermittently fails for me. Another user even reported that it only works 1 out of 5-10 times. QAudioRecorder seems to hang on requesting the audio to be recorded (status QMediaRecortder::StartingStatus). When it actually works, it properly goes from starting to recording and then it's possible to record audio and playback. QAudioRecorder has an error() method, but it returns QMediaRecorder::NoError Since it was confirmed by two people (victorp, karni) we suspect it's a bug in the middleware rather than the apps. A test click has been sent to Ricardo's e-mail by Victor. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 20 device name: krillin channel: (the BQ channel) last update: 2015-02-26 17:06:15 version version: 20 version ubuntu: 20150219 version device: 20150225-b67e0b6 version custom: 20150216-561-29-186 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1433563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1433563] Re: QAudioRecorder recording hangs
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1433563 Title: QAudioRecorder recording hangs Status in the base for Ubuntu mobile products: New Status in gst-plugins-good0.10 package in Ubuntu: Confirmed Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Bug description: Recording audio with QAudioRecorder intermittently fails for me. Another user even reported that it only works 1 out of 5-10 times. QAudioRecorder seems to hang on requesting the audio to be recorded (status QMediaRecortder::StartingStatus). When it actually works, it properly goes from starting to recording and then it's possible to record audio and playback. QAudioRecorder has an error() method, but it returns QMediaRecorder::NoError Since it was confirmed by two people (victorp, karni) we suspect it's a bug in the middleware rather than the apps. A test click has been sent to Ricardo's e-mail by Victor. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 20 device name: krillin channel: (the BQ channel) last update: 2015-02-26 17:06:15 version version: 20 version ubuntu: 20150219 version device: 20150225-b67e0b6 version custom: 20150216-561-29-186 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1433563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445080] Re: Cellular data not activated after exiting flight mode
I could also easily reproduce that with mako/arale 173, without any custom network manager packages. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: New Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output is fine too Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445134] [NEW] Network manager never scanning for new access points
Public bug reported: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1445134 Title: Network manager never scanning for new access points Status in network-manager package in Ubuntu: New Bug description: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with
[Desktop-packages] [Bug 1420395] Re: [mako] upower consuming over 17% cpu when in idle
** Changed in: canonical-devices-system-image Assignee: Ricardo Salveti (rsalveti) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: [mako] upower consuming over 17% cpu when in idle Status in the base for Ubuntu mobile products: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. The upower cpu consumption is just a side effect of the amount of battery related events the kernel send, and specific to mako. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1361864] Re: add Tag property to ConnectionContext interface
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1361864 Title: add Tag property to ConnectionContext interface Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Status in nuntium package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Fix Committed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443244] Re: [touch] small cracking sound when changing volume
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Description changed: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. + + Not critical for the user experience but can be a bit annoying. + + Remember that here pulse is only changing the volume for the multimedia + role itself (or any other active role used when reproducing the bug). + Not really touching the hardware. ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1443244 Title: [touch] small cracking sound when changing volume Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. Not critical for the user experience but can be a bit annoying. Remember that here pulse is only changing the volume for the multimedia role itself (or any other active role used when reproducing the bug). Not really touching the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443244] [NEW] [touch] small cracking sound when changing volume
Public bug reported: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. Not critical for the user experience but can be a bit annoying. Remember that here pulse is only changing the volume for the multimedia role itself (or any other active role used when reproducing the bug). Not really touching the hardware. ** Affects: canonical-devices-system-image Importance: Undecided Assignee: Canonical Phone Foundations (canonical-phonedations-team) Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1443244 Title: [touch] small cracking sound when changing volume Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 169 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-12 20:38:14 version version: 169 version ubuntu: 20150412 version device: 20150210 version custom: 20150412 Just change the volume quickly when playing a sound, and you can hear really small cracking sounds as the volume increases/decreases. This is even more noticeable with Pathwind's (touch game) soundtrack. Not critical for the user experience but can be a bit annoying. Remember that here pulse is only changing the volume for the multimedia role itself (or any other active role used when reproducing the bug). Not really touching the hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443178] [NEW] Accounts Service always relies on language fallback if never set by the user
Public bug reported:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-sound,
as that will cause a sync to accountsservice in order to sync the
volume. Once that sync happens, it will request the user properties, and
in case the user doesn't have a valid language at
/var/lib/AccountsService/users/user, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any language
when the wizard shows up, run top and then change the volume by pressing
volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user-language)
g_value_set_string (value, user-language);
else
g_value_set_string (value, user_get_fallback_value
(user, Language));
break;
case PROP_FORMATS_LOCALE:
if (user-formats_locale)
g_value_set_string (value, user-formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, FormatsLocale));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/user, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while for
accountsservice to reply back to indicator-sound when the sync happens,
possibly causing sync aborts (as indicator-sound only waits 1 second
before triggering another sync).
Some possible ways to fix this issue:
1) Make wizard to set language even when the selected language is already the
default one;
2) Change accountsservice to save the fallback value at the first time it gets
that from the system;
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/user, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Summary changed: - Network indicator lists the non-exist AP (timeout for the AP to be removed is too big) + Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
Just to compare, on both iphone and android the AP disappear in no more than 30 seconds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big)
** Summary changed: - Network indicator lists the non-exist AP + Network indicator lists the non-exist AP (timeout for the AP to be removed is too big) ** Description changed: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. + + The main issue is that the timeout for the AP to be removed from the + known AP list is too big when comparing with other phones. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big) Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420395] Re: upower consuming over 17% cpu
After profiling upower, this is actually not an issue in there, as the only thing it is doing is getting the battery change event from the kernel, updating the internal struct and sending another dbus message so the clients could see the changes. The main issue here is that the kernel is sending a big amount of battery events (all valid, and different changes), which results in udev, upower and dbus consuming a bit of your cpu. Verified this bug against both krillin and arale and that is not the case there, as I already did the profiling and reduced the amount of battery events. As this bug is just specific to mako, and would require a kernel change to reduce the amount of events, we can lower the priority and fix in vivid only. ** Summary changed: - upower consuming over 17% cpu + [mako] upower consuming over 17% cpu when in idle ** Description changed: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool - mpdecision and systemd-udevd also change their behavior. + mpdecision and systemd-udevd also change their behavior. + + The upower cpu consumption is just a side effect of the amount of + battery related events the kernel send, and specific to mako. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: [mako] upower consuming over 17% cpu when in idle Status in the base for Ubuntu mobile products: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. The upower cpu consumption is just a side effect of the amount of battery related events the kernel send, and specific to mako. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
I was finally able to reproduce the issue I saw before with media-hub,
following the steps described by comment 14. After recording a few
videos and trying to play one of them, I got media-hub to consume 100%
of my cpu, blocking the loop and blocking any new connections as
consequence.
Strace shows it's busy in epoll_wait:
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\2\1\1\20\0\0\0T\5\0\0\37\0\0\0\6\1s\0\6\0\0\0:1.107\0\0...,
48}, {\1x\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 64
epoll_wait(6, {{EPOLLIN, {u32=33486680, u64=33486680}}}, 128, -1) = 1
recvmsg(4, {msg_name(0)=NULL,
msg_iov(1)=[{l\1\0\0011\0\0\0\25\5\0\0\247\0\0\0\1\1o\0%\0\0\0/core/ub...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 233
recvmsg(4, 0xbe938130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
epoll_ctl(6, EPOLL_CTL_MOD, 4, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP|EPOLLET,
{u32=33486680, u64=33486680}}) = 0
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\2\1\1\20\0\0\0U\5\0\0\37\0\0\0\6\1s\0\6\0\0\0:1.107\0\0...,
48}, {\1x\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 64
epoll_wait(6, {{EPOLLIN, {u32=33486680, u64=33486680}}}, 128, -1) = 1
recvmsg(4, {msg_name(0)=NULL,
msg_iov(1)=[{l\1\0\0011\0\0\0\26\5\0\0\247\0\0\0\1\1o\0%\0\0\0/core/ub...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 233
recvmsg(4, 0xbe938130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
epoll_ctl(6, EPOLL_CTL_MOD, 4, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP|EPOLLET,
{u32=33486680, u64=33486680}}) = 0
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL,
msg_iov(2)=[{l\2\1\1\20\0\0\0V\5\0\0\37\0\0\0\6\1s\0\6\0\0\0:1.107\0\0...,
48}, {\1x\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 64
epoll_wait(6, {{EPOLLIN, {u32=33486680, u64=33486680}}}, 128, -1) = 1
recvmsg(4, {msg_name(0)=NULL,
msg_iov(1)=[{l\1\0\0011\0\0\0\27\5\0\0\247\0\0\0\1\1o\0%\0\0\0/core/ub...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 233
recvmsg(4, 0xbe938130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
epoll_ctl(6, EPOLL_CTL_MOD, 4, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP|EPOLLET,
{u32=33486680, u64=33486680}}) = 0
epoll_wait(6, {}, 128, 0) = 0
sendmsg(4, {msg_name(0)=NULL, msg_iov(2)=[{l\2
Getting dbg symbols now to get a trace.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1398560
Title:
Music playback randomly stops working
Status in the base for Ubuntu mobile products:
In Progress
Status in Media Hub:
Invalid
Status in QT Ubuntu Camera:
New
Status in pulseaudio package in Ubuntu:
In Progress
Bug description:
While listening to music media-hub stops randomly. Restart of the job
and reboots don't fix it. Video works fine. Also, 320 kbps music
pauses randomly, might be related. I have also talked about this on
the mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
Backtrace when attaching with gdb:
#0 0xb62c9712 in epoll_wait () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1 0xb6ee93fa in boost::asio::detail::epoll_reactor::run (this=0x1fef6e8,
block=block@entry=true, ops=...) at
/usr/include/boost/asio/detail/impl/epoll_reactor.ipp:392
timeout = optimized out
events = {{events = 0, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 0}}
repeats 38 times, {events = 0, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
141392522407575552}}, {events = 32920512, data = {ptr = 0x1f5a0d0, fd =
32874704, u32 = 32874704, u64 = 32874704}}, {
events = 32872688, data = {ptr = 0x4, fd = 4, u32 = 4, u64 = 4}},
{events = 32920512, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 0}}, {events =
32920512, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 141392522407575552}},
{events = 32874704, data = {
ptr = 0x1f598f0, fd = 32872688, u32 = 32872688, u64 =
13176978892729456880}}, {events = 3068944384, data = {ptr = 0xb6e459c5, fd =
-1226548795, u32 = 3068418501, u64 = 13181015765591284165}}, {events = 0, data
= {ptr = 0xaa903f48, fd = -1433387192,
u32 = 2861580104, u64 = 13178762878944034632}}, {events = 0, data
= {ptr = 0x1f5ef58, fd = 32894808, u32 = 32894808, u64 = 32894808}}, {events =
3197337120, data = {ptr = 0x1f5ef58, fd = 32894808, u32 = 32894808, u64 =
14429902988664}}, {
events = 33597384, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
13732458124168658944}}, {events = 33607216, data = {ptr = 0xbe937e20, fd =
-1097630176, u32 = 3197337120, u64 = 13177003737984761376}}, {events = 0, data
= {ptr = 0x0, fd = 0, u32 = 0, u64 = 0}}, {
events = 0, data = {ptr = 0x2, fd = 2, u32 = 2, u64 =
145269464831623170}}, {events = 2, data = {ptr = 0x22b0ddc, fd = 36376028, u32
= 36376028, u64 = 8626310620}}, {events = 36376028, data = {ptr = 0xbe937e4c,
fd = -1097630132, u32 = 3197337164,
u64 = 13123924874283417164}}, {events = 36376028, data = {ptr =
0x2c, fd = 44, u32 = 44, u64 = 193273528364}}, {events = 3069841168, data =
{ptr = 0x2d, fd = 45, u32 = 45, u64 = 45}}, {events = 1, data = {ptr = 0x1, fd
= 1, u32 = 1,
u64 = 145246894778482689}}, {events = 2, data = {ptr = 0x3, fd =
3, u32 = 3, u64 = 18161629713510957059}}, {events = 36376028, data = {ptr =
0x6c, fd = 108, u32 = 108, u64 = 145246894778482796}}, {events = 36376028, data
= {ptr = 0xbe937f38,
fd = -1097629896, u32 = 3197337400, u64 = 13732460669986635576}},
{events = 103, data = {ptr = 0x1, fd = 1, u32 = 1, u64 = 463856467969}},
{events = 3197337416, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
13732459361119240192}}, {events = 0, data = {
ptr = 0x76, fd = 118, u32 = 118, u64 = 13732459567277670518}},
{events = 103, data = {ptr = 0xbe937f38, fd = -1097629896, u32 = 3197337400,
u64 = 13732459639194484536}}, {events = 3197337400, data = {ptr = 0x67, fd =
103, u32 = 103,
u64 = 13123673752938217575}}, {events = 3197337368, data = {ptr =
0xb6fa0f10 __stack_chk_guard, fd = -1225126128, u32 = 3069841168, u64 =
13123673481130151696}}, {events = 43, data = {ptr = 0xbe937fec, fd =
-1097629716, u32 = 3197337580,
u64 = 13123643665594679276}}, {events = 3197337400, data = {ptr =
0x0, fd = 0, u32 = 0, u64 = 13732459361119240192}}, {events = 3197337444, data
= {ptr = 0xbe937f58, fd = -1097629864, u32 = 3197337432, u64 = 7492304728}},
{events = 9, data = {ptr = 0x1,
fd = 1, u32 = 1, u64 = 1}}, {events = 4, data = {ptr =
0xbe937f58, fd = -1097629864, u32 = 3197337432, u64 = 11787272024}}, {events =
4, data = {ptr = 0xbe937f58, fd = -1097629864, u32 = 3197337432, u64 =
13128831883009032024}}, {events = 3055657113,
data = {ptr = 0x20419a0, fd = 33823136, u32 = 33823136, u64 =
206192253344}}, {events = 36376152, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
0}}, {events = 3197337416, data = {ptr = 0xb6235398, fd = -1239198824, u32 =
3055768472, u64 = 13124425637263791000}}, {
events = 33519408, data = {ptr = 0x1feceb0, fd = 33476272, u32 =
33476272, u64 = 156233833471987376}}, {events = 36376108, data = {ptr =
0x1fec7c0, fd = 33474496, u32 = 33474496, u64 = 143772277920417728}}, {events =
64, data = {ptr = 0x22b0e18,
fd = 36376088, u32 = 36376088, u64 = 13184867420510817816}},
{events = 16, data = {ptr = 0x0, fd = 0, u32 = 0, u64 = 13184867420474441728}},
{events = 3069841168, data = {ptr = 0x0, fd = 0, u32 = 0, u64 =
156233850618380288}}, {events = 36376088, data = {
ptr = 0x0, fd = 0, u32 = 0, u64 = 143771865570082816}}, {events =
3069841168, data = {ptr = 0x20, fd = 32, u32 = 32, u64 = 143771865570082848}},
{events = 3069841168, data = {ptr = 0x20, fd = 32, u32 = 32, u64 =
13732461216545112096}}, {events = 3069841168,
data = {ptr = 0xbe938174, fd = -1097629324, u32 = 3197337972, u64 =
13123867742628446580}}, {events = 3197304832, data = {ptr = 0x1fec7c0, fd =
33474496,
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
Trying to reproduce but I'm still unable to get the issue described at comment #14. I was able to get the system to hang for a bit, but that was because mediascanner crashed. It seems that at one point media-hub wasn't able to accept new connections (couldn't play music via music- app). The problem is that it worked fine after a reboot, so not really pulse specific. I also tested the pulseconfig described by comment #16, but audio is also working as expected (if the file was corrupted or with the multimedia role muted, it would show up when using such configs). Will keep trying to reproduce the issue (this is latest RTM/krillin). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1435776] Re: NM does not activate a valid ofono context
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1435776 Title: NM does not activate a valid ofono context Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
** Attachment added: media-hub-taabtfull.txt https://bugs.launchpad.net/media-hub/+bug/1398560/+attachment/4361422/+files/media-hub-taabtfull.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
As before, pulse was fine after a reboot. Will now try to manually corrupt the database and see what I can get (wondering if this is related with the mute issue we have with pathwind). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438486] [NEW] Turning off sound in Pathwind mutes other apps too
Public bug reported: current build number: 260 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-30 18:17:44 version version: 260 version ubuntu: 20150330 version device: 20150327-f7072d0 version custom: 20150216-561-29-186 In Pathwind (part of the custom tarball installed with newer flashes but also in the store) one can toggle sound on/off. If set to off sound won't be heard in youtube playbacks in the browser, cut the rope, media player. It still works for keyboard press sounds if enabled, and ringtones work as well. This may be intentional, but at least on one occasion it persisted even after pathwind quit, and sound did not work in the rest of the apps. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: pulseaudio (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1438486 Title: Turning off sound in Pathwind mutes other apps too Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu RTM: New Bug description: current build number: 260 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-30 18:17:44 version version: 260 version ubuntu: 20150330 version device: 20150327-f7072d0 version custom: 20150216-561-29-186 In Pathwind (part of the custom tarball installed with newer flashes but also in the store) one can toggle sound on/off. If set to off sound won't be heard in youtube playbacks in the browser, cut the rope, media player. It still works for keyboard press sounds if enabled, and ringtones work as well. This may be intentional, but at least on one occasion it persisted even after pathwind quit, and sound did not work in the rest of the apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
Opened bug 1438491 for the issue I had with media-hub. For this bug I'll just force pulse to not store/restore any mute or device related value for the multimedia role. I think the original issue is that the multimedia role stream got muted, causing the blocking issue just for multimedia related apps (ringtone and alarms were playing fine). This is probably a similar issue as described by bug 1438486 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
** Description changed: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. + + This is probably a side effect of bug 1438486 (or similar), as pulse is + working but without sound just for the multimedia related roles. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: In Progress Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Status in ubuntu-touch-session package in Ubuntu: New Status in ubuntu-touch-session package in Ubuntu RTM: New Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. This is probably a side effect of bug 1438486 (or similar), as pulse is working but without sound just for the multimedia related roles. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438486] Re: Turning off sound in Pathwind mutes other apps too
** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1438486 Title: Turning off sound in Pathwind mutes other apps too Status in the base for Ubuntu mobile products: New Status in pulseaudio package in Ubuntu: Confirmed Status in ubuntu-touch-session package in Ubuntu: New Status in pulseaudio package in Ubuntu RTM: New Status in ubuntu-touch-session package in Ubuntu RTM: New Bug description: current build number: 260 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-30 18:17:44 version version: 260 version ubuntu: 20150330 version device: 20150327-f7072d0 version custom: 20150216-561-29-186 In Pathwind (part of the custom tarball installed with newer flashes but also in the store) one can toggle sound on/off. If set to off sound won't be heard in youtube playbacks in the browser, cut the rope, media player. It still works for keyboard press sounds if enabled, and ringtones work as well. This may be intentional, but at least on one occasion it persisted even after pathwind quit, and sound did not work in the rest of the apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1435776] Re: NM does not activate a valid ofono context
** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1435776 Title: NM does not activate a valid ofono context Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: Device: Krillin Software: Vivid r157 NM does not activate a valid ofono context which is present in the gprs file (context_1 in this case) I was able to activate the context manually using ./activate-context /ril_0 1 You can find syslog, list-modems and list-contexts attached To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436971] Re: calendar alarm would not stop sounding
*** This bug is a duplicate of bug 1436162 *** https://bugs.launchpad.net/bugs/1436162 ** This bug has been marked a duplicate of bug 1436162 [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436971 Title: calendar alarm would not stop sounding Status in indicator-datetime package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: vivid-proposed on mako I had a calendar alarm notification sound at 9:00am this morning and it keep ringing/vibrating and did not go away until I swiped it. At that point, I think something crashed because my datetime indicator is stuck at 9:01am and I cannot launch Time and Date settings from the menu. I do have a crash file (with an earlier timestamp, so not sure if it's the same or different crash). Attaching that and the indicator- datetime log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1436971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
** Changed in: pulseaudio (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: In Progress Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1437065] Re: Configure a proper folder setup for file transfers computer to phone
There is a way to point out the root folder, we just need to verify if we want to expose the entire home or just the same folders used by mtp (preferred). I'll check if there is a way to point it out into a tmp folder that would have the right links (there is a root-script argument that gets called in order to prepare the root folder). ** Changed in: obexd (Ubuntu) Status: New = Confirmed ** Changed in: obexd (Ubuntu) Importance: Undecided = High ** Changed in: obexd (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to obexd in Ubuntu. https://bugs.launchpad.net/bugs/1437065 Title: Configure a proper folder setup for file transfers computer to phone Status in obexd package in Ubuntu: Confirmed Bug description: We can currently pair a ubuntu desktop to an ubuntu phone. When using the file browsing option the user is presented with /tmp from the phone. this should be configured to show the proper set of folders within the /home/phablet area similar to mtp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obexd/+bug/1437065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
So this issue is a combination of the following patches: https://sourceware.org/git/?p=glibc.git;a=commit;h=47c5adebd2c864a098c3af66e61e1147dc3cf0b4 https://sourceware.org/git/?p=glibc.git;a=commit;h=03d41216fe09fc71a2750946af8fe2892bf4feb5 Basically the main problem is that futex_atomic_cmpxchg_inatomic got disabled, even though we have that well supported in our kernels. I just did another build (in canonical-arm-dev) including the patch bellow, and with that I'm unable to reproduce this bug: Index: glibc-2.21/sysdeps/unix/sysv/linux/arm/kernel-features.h === --- glibc-2.21.orig/sysdeps/unix/sysv/linux/arm/kernel-features.h +++ glibc-2.21/sysdeps/unix/sysv/linux/arm/kernel-features.h @@ -37,8 +37,10 @@ /* The ARM kernel before 3.14.3 may or may not support futex_atomic_cmpxchg_inatomic, depending on kernel configuration. */ +/* #if __LINUX_KERNEL_VERSION 0x030E03 # undef __ASSUME_FUTEX_LOCK_PI # undef __ASSUME_REQUEUE_PI # undef __ASSUME_SET_ROBUST_LIST #endif +*/ ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Confirmed = Invalid ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 Status in glibc package in Ubuntu: Confirmed Status in gst-plugins-good1.0 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1436162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
SMP support for futex_atomic_cmpxchg_inatomic was added in 2.6.38, but it required !CPU_USE_DOMAINS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 Status in glibc package in Ubuntu: Confirmed Status in gst-plugins-good1.0 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1436162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
** Changed in: canonical-devices-system-image Assignee: Michael Frey (mfrey) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
It seems the issue only happens when at least 2 threads are waiting for the wait condition (that gets triggered by pa_threaded_mainloop_signal). When I'm unable to make it to crash, it always shows only one thread waiting the signal. So my current theory is that there might be issues when calling pthread_cond_wait on more than one thread at the same time (maybe when increasing/decreasing the mutex count). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 Status in glibc package in Ubuntu: Confirmed Status in gst-plugins-good1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1436162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
The mutex in question is the one used by pulse's mainloop, which gets used by pa_threaded_mainloop_lock, pa_threaded_mainloop_unlock and pa_threaded_mainloop_wait. As the pulseaudio calls are all asynchronous, gst (pulsesink element) calls pa_threaded_mainloop_wait right after calling pulseaudio, so it can block the thread until pulseaudio returns via callback (which then calls pa_threaded_mainloop_signal, unblocking the thread). The mutex is also recursive, allowing many lock and unlock calls to happen in parallel. Follows the log when I'm able to reproduce the crash (with the mutex recursive count): Interrupt: Stopping pipeline ... Execution ended after 0:00:06.840520615 Setting pipeline to PAUSED ... (thread id: 3069599744) pa_threaded_mainloop_lock - mutex: 0xb5250e00 (thread id: 3069599744) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3069599744) pa_mutex_lock - m: 0xb5250e00 (count new 1) (thread id: 3069599744) pa_threaded_mainloop_unlock - mutex: 0xb5250e00 (thread id: 3069599744) pa_mutex_unlock - m: 0xb5250e00 (count prev 1) (thread id: 3069599744) pa_mutex_unlock - m: 0xb5250e00 (count new 0) 0:00:07.586470308 12439 0x15d1dc0 DEBUG pulse pulsesink.c:1272:gst_pulseringbuffer_pause:pulsesink1 Pausing and corking, before calling mainloop lock (thread id: 3069599744) pa_threaded_mainloop_lock - mutex: 0xb5250e00 (thread id: 3069599744) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3069599744) pa_mutex_lock - m: 0xb5250e00 (count new 1) 0:00:07.586854770 12439 0x15d1dc0 DEBUG pulse pulsesink.c:1135:gst_pulsering_set_corked:pulsesink1 Setting corked state to 1 0:00:07.587025308 12439 0x15d1dc0 DEBUG pulse pulsesink.c:1142:gst_pulsering_set_corked:pulsesink1 Calling pa_threaded_mainloop_wait (PA_OPERATION_RUNNING) (thread id: 3069599744) pa_threaded_mainloop_wait - cond: 0xb52517b8, mutex: 0xb5250e00 (thread id: 3069599744) pa_cond_wait - m: 0xb5250e00 (count before wait 1) (thread id: 3018630240) poll_func lock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count new 1) (thread id: 3018630240) poll_func unlock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count prev 1) (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count new 0) (thread id: 3018630240) poll_func lock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count new 1) (thread id: 3018630240) poll_func unlock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count prev 1) (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count new 0) (thread id: 3018630240) poll_func lock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count new 1) (thread id: 3018630240) poll_func unlock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count prev 1) (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count new 0) (thread id: 3018630240) poll_func lock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count new 1) (thread id: 3018630240) poll_func unlock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count prev 1) (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count new 0) (thread id: 3018630240) poll_func lock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count new 1) (thread id: 3018630240) poll_func unlock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count prev 1) (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count new 0) (thread id: 3018630240) poll_func lock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count prev 0) (thread id: 3018630240) pa_mutex_lock - m: 0xb5250e00 (count new 1) (thread id: 3018630240) pa_threaded_mainloop_signal - cond: 0xb52517b8, wait_for_accept: 0, n_waiting: 2 (thread id: 3018630240) pa_cond_signal broadcast - c 0xb52517b8) (thread id: 2941641824) pa_cond_wait - m: 0xb5250e00 (count after wait 1) (thread id: 2941641824) pa_threaded_mainloop_unlock - mutex: 0xb5250e00 (thread id: 2941641824) pa_mutex_unlock - m: 0xb5250e00 (count prev 1) (thread id: 2941641824) pa_mutex_unlock - m: 0xb5250e00 (count new 0) (thread id: 3018630240) poll_func unlock - mutex: 0xb5250e00 (thread id: 3018630240) pa_mutex_unlock - m: 0xb5250e00 (count prev 0) Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. Aborted (core dumped) -- You received this bug notification because you are a member of Desktop
[Desktop-packages] [Bug 1436162] [NEW] [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
Public bug reported: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. ** Affects: glibc (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: libc (Ubuntu) Importance: Undecided Status: New ** Package changed: libc (Ubuntu) = glibc (Ubuntu) ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Description changed: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. + + To reproduce the issue: + GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 + + Then when playing, just hit control+c, which will then pause the + pipeline, causing the crash. The crash happens with most of the times + you pause or seek the pipeline. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 Status in glibc package in Ubuntu: Confirmed Status in gst-plugins-good1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1436162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store
** Changed in: canonical-devices-system-image Assignee: Michael Frey (mfrey) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1224756 Title: Pulseaudio should integrate with trust-store Status in the base for Ubuntu mobile products: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Currently the 'audio' policy group allows access to pulseaudio which allows apps to use the microphone and eavesdrop on the user. Pulseaudio needs to be modified to use trust-store, like location- service does. Integrating with trust-store means that when an app tries use the microphone via pulseaudio, pulseaudio will contact trust-store, the trust-store will prompt the user (Foo wants to use the microphone. Is this ok? Yes|No), optionally cache the result and return the result to pulseaudio. In this manner the user is given a contextual prompt at the time of access by the app. Using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in settings. Targeting to T-Series for now, since the trust-store is not in a reusable form yet. Original description: David and the security team (inspired by an observation from Rick) discussed that when recording, pulseaudio should somehow unobtrusively show the user that it is recording. The easiest thing to do would be for pulseaudio to alert indicator-sound which would then turn its icon red (similar to indicator-message turning blue with new messages). Marking 'high' because apps with access to pulseaudio can currently eavedrop on users. If the app is allowed to do networking (the default for apps), then it can ship that information off to a server somewhere. Note 1, the alert to indicator-sound must happen via the out of process pulseaudio server and not the confined app itself to be effective. Note 2, we should consider how to enforce this for foreground apps only. Application lifecycle should probably handle this for 13.10 (apps are suspended if not in foreground or if the screensaver is on), but we don't want an app on the converged device to record in the background when the user isn't paying attention. Example eavesdropping attack: start recording only when the screensaver is on (perhaps inhibiting the screensaver during recording would be enough). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP
** Also affects: network-manager (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu RTM) Status: New = Confirmed ** Changed in: network-manager (Ubuntu) Importance: Undecided = High ** Changed in: network-manager (Ubuntu RTM) Importance: Undecided = High ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) ** Changed in: network-manager (Ubuntu RTM) Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] [NEW] Network indicator lists the non-exist AP
Public bug reported: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: High Assignee: Canonical Phone Foundations (canonical-phonedations-team) Status: Confirmed ** Affects: network-manager (Ubuntu RTM) Importance: High Assignee: Canonical Phone Foundations (canonical-phonedations-team) Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP
From previous conversations: Pat McGowan (pat-mcgowan) wrote on 2015-02-12: Yes, I currently have some 50 APs in the list both on command line and the indicator Its as if the phone was picking them up while I was driving Mathieu Trudel-Lapierre (mathieu-tl) wrote on 2015-02-13: Scanlist updates aren't instantaneous, it depends on whether another scan has happened, and whether the network is still in range; and given moving fast through APs as I recall they will also have to timeout from the list. How long in between tests from the command-line? What is the distance between the two locations? Marcus Tomlinson (marcustomlinson) wrote on 2015-02-16: I tested this by turning on and off a WiFi hotspot a few times and observing both the output of nmcli d wifi list (executed every ±30s), and the list displayed in the Network Indicator. Over 4 test cycles I observed the following: When turning on the hotspot it takes about 1min (maybe 2min) for both nm and the indicator to display the new AP. When turning off the hotspot, nm and the indicator took anywhere between 5-10min to recognise that the AP had dissappeared. AFAICT signal strength updates for APs on the list (other than the currently connected AP) also lag by this 5-10min delay. Seeing that the indicator is always in sync with Network Manager, these delays are clearly not caused by the Network Indicator, but by Network Manager itself (as Mathieu mentioned). So yes, Network Manager does recognise when an AP is no longer in range or drops in signal strength, but personally I find the delay far too long (which I think is the concern expressed here). John McAleely (john.mcaleely) wrote 50 seconds ago: Anecdotally, going on a bus journey in london (or a train journey) will produce a long list of garbage AP's that are not interesting when you finally sit down near a hotspot you want to join. It's not an issue on 'other' OS. Seen on RTM based hansets too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424840] Re: [krillin] garbage signal on screen during playback of a specific mp4 video file
** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New = In Progress ** Changed in: gst-plugins-good1.0 (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1424840 Title: [krillin] garbage signal on screen during playback of a specific mp4 video file Status in gst-plugins-good1.0 package in Ubuntu: In Progress Bug description: Image: vivid Gst-good: 1.4.5-1ubuntu1 Hardare: krillin How to reproduce: 1. play the attached mp4 file in Video scope. 2. fast forward to about 00:00:53. 3. you can see lots of garbage signal on the playing screen. The video is correct, and there is no corruption when playing on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1424840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424840] Re: [krillin] garbage signal on screen during playback of a specific mp4 video file
** Summary changed: - [krillin] garbage signal on screen during playing specific mp4 video file + [krillin] garbage signal on screen during playback of a specific mp4 video file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1424840 Title: [krillin] garbage signal on screen during playback of a specific mp4 video file Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: Image: vivid Gst-good: 1.4.5-1ubuntu1 Hardare: krillin How to reproduce: 1. play the attached mp4 file in Video scope. 2. fast forward to about 00:00:53. 3. you can see lots of garbage signal on the playing screen. The video is correct, and there is no corruption when playing on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1424840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1424840] [NEW] [krillin] garbage signal on screen during playback of a specific mp4 video file
Public bug reported: Image: vivid Gst-good: 1.4.5-1ubuntu1 Hardare: krillin How to reproduce: 1. play the attached mp4 file in Video scope. 2. fast forward to about 00:00:53. 3. you can see lots of garbage signal on the playing screen. The video is correct, and there is no corruption when playing on the desktop. ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: Sample.mp4 https://bugs.launchpad.net/bugs/1424840/+attachment/4325801/+files/Sample.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1424840 Title: [krillin] garbage signal on screen during playback of a specific mp4 video file Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: Image: vivid Gst-good: 1.4.5-1ubuntu1 Hardare: krillin How to reproduce: 1. play the attached mp4 file in Video scope. 2. fast forward to about 00:00:53. 3. you can see lots of garbage signal on the playing screen. The video is correct, and there is no corruption when playing on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1424840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420395] Re: upower consuming over 17% cpu
It seems the problem relies more on the kernel side and with the amount of events the battery driver sends to the userspace (even when there is no change). udevadm monitor is already enough to show the amount of kernel events the battery driver sends to the userspace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: upower consuming over 17% cpu Status in the base for Ubuntu mobile products: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420395] Re: upower consuming over 17% cpu
As an example, the amount of upower events when connecting/disconnecting the usb cable (charger) on mako: root@ubuntu-phablet:/sys# upower -m Monitoring activity from the power daemon. Press Ctrl+C to cancel. [03:54:38.613] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.616] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.620] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.621] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.621] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.622] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.624] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.632] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.633] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.634] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.636] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:38.636] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.122] device changed: /org/freedesktop/UPower/devices/line_power_pm8921_dc [03:54:39.128] device changed: /org/freedesktop/UPower/devices/line_power_pm8921_dc [03:54:39.129] device changed: /org/freedesktop/UPower/devices/line_power_pm8921_dc [03:54:39.129] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.130] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.131] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.131] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.131] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.132] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.132] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.133] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.133] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.134] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.134] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.143] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.144] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.144] daemon changed: [03:54:39.427] device changed: /org/freedesktop/UPower/devices/line_power_pm8921_dc [03:54:39.427] device changed: /org/freedesktop/UPower/devices/line_power_pm8921_dc [03:54:39.428] device changed: /org/freedesktop/UPower/devices/line_power_pm8921_dc [03:54:39.430] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.431] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.432] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.432] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.433] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.433] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.434] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.434] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.436] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.436] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.437] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:39.437] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.357] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.358] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.358] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.358] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.359] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.359] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.359] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.360] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.360] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.360] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.361] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:40.361] device changed: /org/freedesktop/UPower/devices/battery_battery [03:54:41.140] device changed:
[Desktop-packages] [Bug 1398560] Re: Music playback randomly stops working
** Project changed: pulseaudio = pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398560 Title: Music playback randomly stops working Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Invalid Status in QT Ubuntu Camera: New Status in pulseaudio package in Ubuntu: New Bug description: While listening to music media-hub stops randomly. Restart of the job and reboots don't fix it. Video works fine. Also, 320 kbps music pauses randomly, might be related. I have also talked about this on the mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 598308] Re: Volume at login set to Maximum after a reboot
** Summary changed: - Volume at login set to Maximum + Volume at login set to Maximum after a reboot ** Also affects: pulseaudio (Ubuntu Utopic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/598308 Title: Volume at login set to Maximum after a reboot Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Trusty: New Bug description: Release: Ubuntu 10.04 64-bit Desktop Edition What You Expected to Happen: System volume to remain as set before reboot and as shown in volume panel applet What Happened Instead: After reboot/shutdown at and after login system volume is set to maximum Extended Description: Intel HD Audio Chipset using S/PDIF coax out to speakers and system audio set to digital output After either rebooting or shutting down my system at the next login the system volume will be set to maximum. Once the panel loads I can click on the system volume applet and if I move the volume slider in any direction the volume will immediately be set to the correct level. **MORE INFO 6/25/10** This also affects the system alert volume in the same fashion as above. Adjusting the slider for the alert value via the panel applet reset the volume to the correct level. LTS Stable Update: [Impact] * Volume at the maximum level after a reboot [Test Case] 1. (logged in system running)slide volume to 75% using system volume applet on panel 2. reboot 3. Login, 4. login soundbite plays at 100% volume 5. open rhythmbox play audio track system volume at 100% 6. click on system volume panel applet, do not click slider, slider shows volume set at 75% as before reboot This is the odd part 7. click on volume slider and adjust in either direction system volume abruptly adjusts to match the volume level indicated by the slider. [Regression Potential] * Small, just restoring the volume in case the device only has sw volume support [Other Info] * Patch already available in upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/598308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 598308] Re: Volume at login set to Maximum after a reboot
** Description changed: Release: Ubuntu 10.04 64-bit Desktop Edition What You Expected to Happen: System volume to remain as set before reboot and as shown in volume panel applet What Happened Instead: After reboot/shutdown at and after login system volume is set to maximum Extended Description: Intel HD Audio Chipset using S/PDIF coax out to speakers and system audio set to digital output After either rebooting or shutting down my system at the next login the system volume will be set to maximum. Once the panel loads I can click on the system volume applet and if I move the volume slider in any direction the volume will immediately be set to the correct level. - Here is how the process goes: + **MORE INFO 6/25/10** + This also affects the system alert volume in the same fashion as above. + Adjusting the slider for the alert value via the panel applet reset the + volume to the correct level. + + LTS Stable Update: + + [Impact] + * Volume at the maximum level after a reboot + + [Test Case] 1. (logged in system running)slide volume to 75% using system volume applet on panel 2. reboot 3. Login, 4. login soundbite plays at 100% volume 5. open rhythmbox play audio track system volume at 100% 6. click on system volume panel applet, do not click slider, slider shows volume set at 75% as before reboot This is the odd part 7. click on volume slider and adjust in either direction system volume abruptly adjusts to match the volume level indicated by the slider. - If any more information is needed please let me know. Thank you + [Regression Potential] + * Small, just restoring the volume in case the device only has sw volume support - **MORE INFO 6/25/10** - - This also affects the system alert volume in the same fashion as above. - Adjusting the slider for the alert value via the panel applet reset the - volume to the correct level. + [Other Info] + * Patch already available in upstream ** No longer affects: pulseaudio (Ubuntu Utopic) ** Also affects: pulseaudio (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/598308 Title: Volume at login set to Maximum after a reboot Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Trusty: New Bug description: Release: Ubuntu 10.04 64-bit Desktop Edition What You Expected to Happen: System volume to remain as set before reboot and as shown in volume panel applet What Happened Instead: After reboot/shutdown at and after login system volume is set to maximum Extended Description: Intel HD Audio Chipset using S/PDIF coax out to speakers and system audio set to digital output After either rebooting or shutting down my system at the next login the system volume will be set to maximum. Once the panel loads I can click on the system volume applet and if I move the volume slider in any direction the volume will immediately be set to the correct level. **MORE INFO 6/25/10** This also affects the system alert volume in the same fashion as above. Adjusting the slider for the alert value via the panel applet reset the volume to the correct level. LTS Stable Update: [Impact] * Volume at the maximum level after a reboot [Test Case] 1. (logged in system running)slide volume to 75% using system volume applet on panel 2. reboot 3. Login, 4. login soundbite plays at 100% volume 5. open rhythmbox play audio track system volume at 100% 6. click on system volume panel applet, do not click slider, slider shows volume set at 75% as before reboot This is the odd part 7. click on volume slider and adjust in either direction system volume abruptly adjusts to match the volume level indicated by the slider. [Regression Potential] * Small, just restoring the volume in case the device only has sw volume support [Other Info] * Patch already available in upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/598308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 598308] Re: Volume at login set to Maximum after a reboot
** Changed in: pulseaudio (Ubuntu Trusty) Status: New = In Progress ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) ** Changed in: pulseaudio (Ubuntu Trusty) Assignee: (unassigned) = Ricardo Salveti (rsalveti) ** Changed in: pulseaudio (Ubuntu) Importance: Undecided = High ** Changed in: pulseaudio (Ubuntu Trusty) Importance: Undecided = Critical ** Changed in: pulseaudio (Ubuntu Trusty) Importance: Critical = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/598308 Title: Volume at login set to Maximum after a reboot Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Trusty: In Progress Bug description: Release: Ubuntu 10.04 64-bit Desktop Edition What You Expected to Happen: System volume to remain as set before reboot and as shown in volume panel applet What Happened Instead: After reboot/shutdown at and after login system volume is set to maximum Extended Description: Intel HD Audio Chipset using S/PDIF coax out to speakers and system audio set to digital output After either rebooting or shutting down my system at the next login the system volume will be set to maximum. Once the panel loads I can click on the system volume applet and if I move the volume slider in any direction the volume will immediately be set to the correct level. **MORE INFO 6/25/10** This also affects the system alert volume in the same fashion as above. Adjusting the slider for the alert value via the panel applet reset the volume to the correct level. LTS Stable Update: [Impact] * Volume at the maximum level after a reboot [Test Case] 1. (logged in system running)slide volume to 75% using system volume applet on panel 2. reboot 3. Login, 4. login soundbite plays at 100% volume 5. open rhythmbox play audio track system volume at 100% 6. click on system volume panel applet, do not click slider, slider shows volume set at 75% as before reboot This is the odd part 7. click on volume slider and adjust in either direction system volume abruptly adjusts to match the volume level indicated by the slider. [Regression Potential] * Small, just restoring the volume in case the device only has sw volume support [Other Info] * Patch already available in upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/598308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1392380] Re: OA gives out all tokens to any app
** Also affects: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1392380 Title: OA gives out all tokens to any app Status in the base for Ubuntu mobile products: Confirmed Status in signon package in Ubuntu: Fix Released Status in signon source package in Utopic: Confirmed Status in signon source package in Vivid: Fix Released Status in signon package in Ubuntu RTM: In Progress Status in ubuntu-touch-meta package in Ubuntu RTM: Fix Released Bug description: The attached app will steal all your tokens. All it takes is the accounts permission in the apparmor file. Here's the code: https://pastebin.canonical.com/120398/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1392380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1413803] Re: music resumes playback after first call hungup and second call on hold
In media-hub we need to add an additional logic to only resume if there is no active calls. ** No longer affects: pulseaudio (Ubuntu) ** Also affects: media-hub (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1413803 Title: music resumes playback after first call hungup and second call on hold Status in Media Hub: New Status in media-hub package in Ubuntu: New Status in media-hub package in Ubuntu RTM: New Bug description: krillin rtm build 208 Steps to reproduce: 1) open music app and play some music through the speaker 2) call ubuntu phone 3) answer call 4) the music is paused correctly 5) call ubuntu phone from another phone 6) answer the second call (the first call is automatically put on hold) 7) hangup the second call Expected results: - the first call is still connected but on hold, no music should be playing - music should not be resumed until all calls are disconnected Actual results: - the first call is still connected on hold, but music is now playing through the earpiece (not speaker) - after un-holding the first call you can hear a mix of the audio from the callers voice and the music - when hang up the call the music switches from the earpiece to the speaker To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1413803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1410523] [NEW] bt pbap needs obexd with phonebook ebook support
Public bug reported: Current obexd version is not building phonebook with ebook support because it's not compatible with current EDS version. In order to use BT PBAP we need to make such backend compatible with EDS. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: obexd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: obexd (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: obexd (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: obexd (Ubuntu) Status: New = Fix Released ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to obexd in Ubuntu. https://bugs.launchpad.net/bugs/1410523 Title: bt pbap needs obexd with phonebook ebook support Status in the base for Ubuntu mobile products: New Status in obexd package in Ubuntu: Fix Released Status in obexd package in Ubuntu RTM: New Bug description: Current obexd version is not building phonebook with ebook support because it's not compatible with current EDS version. In order to use BT PBAP we need to make such backend compatible with EDS. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1408396] Re: media-hub-server crash after recording videos, pulse using high CPU
*** This bug is a duplicate of bug 1398861 ***
https://bugs.launchpad.net/bugs/1398861
** This bug has been marked a duplicate of bug 1398861
Pulse recording stream is never released after recording stops
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1408396
Title:
media-hub-server crash after recording videos, pulse using high CPU
Status in the base for Ubuntu mobile products:
New
Status in Media Hub:
New
Status in media-hub package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
New
Bug description:
Using rtm image 184 on krillin
I was testing recording videos with camera-app and noticed that at
some point during the recording process that pulseaudio was using 40%
CPU and that did not ever get smaller. Then upon closing the camera-
app media-hub-server and camera-app crashes. The following is the
stacktrace which looks like pulseaudio crashed.
Steps to reproduce:
- open camera-app and record a bunch of videos using both front and back
cameras
- run top -d1 during this and you'll see pulseaudio using a lot of cpu
- move camera-app to the background and try to swipe it away and you'll see
the crash
apport-retrace --gdb _usr_bin_media-hub-server.32011.crash
GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as arm-linux-gnueabihf.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word.
Reading symbols from /usr/bin/media-hub-server...(no debugging symbols
found)...done.
warning: core file may not match specified executable file.
[New LWP 12215]
[New LWP 12217]
[New LWP 1]
[New LWP 12218]
[New LWP 12216]
[New LWP 12219]
[New LWP 12224]
[New LWP 2348]
[New LWP 12232]
[New LWP 12235]
[New LWP 2343]
[New LWP 2342]
[New LWP 12258]
[New LWP 8434]
[New LWP 12239]
[New LWP 12227]
[New LWP 12226]
[New LWP 12231]
[New LWP 12221]
[New LWP 12225]
[New LWP 2269]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1.
Core was generated by `media-hub-server'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xb3551cb8 in cleanup_time_events (m=m@entry=0x1965038,
force=force@entry=false)
at pulse/mainloop.c:510
510 pulse/mainloop.c: No such file or directory.
(gdb) bt full
#0 0xb3551cb8 in cleanup_time_events (m=m@entry=0x1965038,
force=force@entry=false)
at pulse/mainloop.c:510
e = 0x600192d3
n = optimized out
__func__ = cleanup_time_events
__PRETTY_FUNCTION__ = cleanup_time_events
#1 0xb3552a8e in scan_dead (m=0x1965038) at pulse/mainloop.c:593
No locals.
#2 pa_mainloop_prepare (m=m@entry=0x1965038, timeout=-1) at
pulse/mainloop.c:796
__func__ = pa_mainloop_prepare
__PRETTY_FUNCTION__ = pa_mainloop_prepare
#3 0xb3553232 in pa_mainloop_iterate (m=0x1965038, block=optimized out,
retval=0x0)
at pulse/mainloop.c:929
r = optimized out
#4 0xb35532c0 in pa_mainloop_run (m=0x1965038, retval=retval@entry=0x0) at
pulse/mainloop.c:950
r = optimized out
#5 0xb355d3b2 in thread (userdata=0x19630d8) at pulse/thread-mainloop.c:88
m = 0x19630d8
mask = {__val = {2147483647, 4294967294, 4294967295 repeats 30
times}}
#6 0xb35080cc in internal_thread_func (userdata=0x1965140) at
pulsecore/thread-posix.c:83
t = 0x1965140
#7 0xb6a8ff98 in start_thread (arg=0xa50fd3e0) at pthread_create.c:311
pd = 0xa50fd3e0
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1525688840, -1525689376,
0, -1525690912,
-1525690592, -1525688812, 0, -1096024600, 1931098388,
1623001989,
0 repeats 54 times}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0},
data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
pagesize_m1 = optimized out
sp = optimized out
freesize = optimized out
__PRETTY_FUNCTION__ = start_thread
#8 0xb6a2f22c in ?? () at
../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92
from /lib/arm-linux-gnueabihf/libc.so.6
No locals.
---Type return to continue, or q return to quit---
Backtrace stopped: previous frame identical to this
[Desktop-packages] [Bug 1397135] [NEW] Error in `/usr/lib/unity-settings-daemon/unity-settings-daemon': free(): invalid pointer
Public bug reported: Using vivid, unity-settings-daemon 15.04.1+15.04.20141127-0ubuntu1. unity-settings-daemon crashes in loop after login, making it really hard to use unity. ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: Crash file https://bugs.launchpad.net/bugs/1397135/+attachment/4269914/+files/_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1397135 Title: Error in `/usr/lib/unity-settings-daemon/unity-settings-daemon': free(): invalid pointer Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Using vivid, unity-settings-daemon 15.04.1+15.04.20141127-0ubuntu1. unity-settings-daemon crashes in loop after login, making it really hard to use unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397135] Re: Error in `/usr/lib/unity-settings-daemon/unity-settings-daemon': free(): invalid pointer
#0 0x7fdef34f8e37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt full
#0 0x7fdef34f8e37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 9423
selftid = 9423
#1 0x7fdef34fa528 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7fffb0559d60, sa_sigaction
= 0x7fffb0559d60}, sa_mask = {__val = {32097008, 755, 1, 0, 0, 0, 0, 1,
30538072, 140736151789040, 140595550913170, 0, 32097008, 408021893121,
4294967300, 30538320}},
sa_flags = -203648753, sa_restorer = 0x7fffb0559d20}
sigs = {__val = {32, 0 repeats 15 times}}
#2 0x7fdef353ab04 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7fdef3643be0 *** Error in `%s': %s: 0x%s ***\n) at
../sysdeps/posix/libc_fatal.c:175
ap = {{gp_offset = 40, fp_offset = 0, overflow_arg_area =
0x7fffb0559f40, reg_save_area = 0x7fffb0559ed0}}
fd = 2
on_2 = optimized out
list = optimized out
nlist = optimized out
cp = optimized out
written = optimized out
#3 0x7fdef3542116 in malloc_printerr (ptr=optimized out,
str=0x7fdef363fcb9 free(): invalid pointer, action=1) at malloc.c:4996
buf = 7fffb055a048
cp = optimized out
#4 _int_free (av=optimized out, p=optimized out, have_lock=0) at
malloc.c:3840
size = optimized out
fb = optimized out
nextchunk = optimized out
nextsize = optimized out
nextinuse = optimized out
prevsize = optimized out
bck = optimized out
fwd = optimized out
errstr = optimized out
locked = optimized out
#5 0x7fdee87ada1d in ?? () from
/usr/lib/unity-settings-daemon-1.0/libpower.so
No symbol table info available.
#6 0x7fdef3aef613 in g_timeout_dispatch (source=0x1e58d00,
callback=optimized out, user_data=optimized out) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:4520
timeout_source = 0x1e58d00
again = optimized out
#7 0x7fdef3aeeb6d in g_main_dispatch (context=0x1d5a670) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3111
dispatch = 0x7fdef3aef600 g_timeout_dispatch
prev_source = 0x0
was_in_call = 0
user_data = 0x1e753e0
callback = 0x7fdee87ad880
cb_funcs = optimized out
cb_data = 0x1ec18b0
need_destroy = optimized out
source = 0x1e58d00
current = 0x1d9b300
i = 1
#8 g_main_context_dispatch (context=context@entry=0x1d5a670) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3710
No locals.
#9 0x7fdef3aeef48 in g_main_context_iterate (context=0x1d5a670,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3781
max_priority = 2147483647
timeout = 501
some_ready = 1
nfds = optimized out
allocated_nfds = 9
fds = 0x1fb7240
#10 0x7fdef3aef272 in g_main_loop_run (loop=0x1e37d10) at
/build/buildd/glib2.0-2.42.1/./glib/gmain.c:3975
__FUNCTION__ = g_main_loop_run
#11 0x7fdef4533165 in gtk_main () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
No symbol table info available.
#12 0x004037f1 in main ()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1397135
Title:
Error in `/usr/lib/unity-settings-daemon/unity-settings-daemon':
free(): invalid pointer
Status in “unity-settings-daemon” package in Ubuntu:
New
Bug description:
Using vivid, unity-settings-daemon 15.04.1+15.04.20141127-0ubuntu1.
unity-settings-daemon crashes in loop after login, making it really
hard to use unity.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397135/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1391230] Re: [TOPBLOCKER] web audio, pulse runs at 6% and screen will not blank on idle
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed ** Changed in: pulseaudio (Ubuntu) Importance: Undecided = High ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1391230 Title: [TOPBLOCKER] web audio, pulse runs at 6% and screen will not blank on idle Status in the base for Ubuntu mobile products: Confirmed Status in Oxide Webview: Fix Released Status in Oxide 1.3 series: Fix Released Status in “pulseaudio” package in Ubuntu: Confirmed Status in “oxide-qt” package in Ubuntu RTM: Fix Released Status in “pulseaudio” package in Ubuntu RTM: Confirmed Status in “unity-system-compositor” package in Ubuntu RTM: Invalid Status in “webbrowser-app” package in Ubuntu RTM: Invalid Bug description: RTM krillin image #154 boot phone - go to Music scope, launch a song in grooveshark, let song start playing application switch back to either Dash or some other application Music will stop due to life cycle kicking in Screen will not turn off attach top - pulse running ~6% if you open spread kill the groove shark web page, the phone will then dim/screen blank on idle you can see the pulse audio process eating 6% go away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1382283] Re: wifi toggle interrupts sound playback
Please make sure this bug moves to barajas, as it's specific to krillin. ** Changed in: network-manager (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1382283 Title: wifi toggle interrupts sound playback Status in “network-manager” package in Ubuntu: Invalid Bug description: Not really sure where this bug should go, but on recent rtm krillin images (such as 112), turning wifi on/off in the network indicator causes a brief interruption in music playback. Steps to reproduce the issue: 1. Start playing a song in the music app. 2. Pull down the network indicator. 3. Toggle wi-fi on or off. For some reason, this makes the sound pause for a moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1382283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394105] Re: Sometimes significant lag between snap dialog and ringtone start
Please enable debug on pulse audio, retest, and give me back your syslog. But please also save the timestamp when the dialog shows up, to see if it was indeed pulse that got blocked or something like that. To enable debug on pulse: $ sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf ** Changed in: pulseaudio (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1394105 Title: Sometimes significant lag between snap dialog and ringtone start Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Incomplete Status in “telepathy-ofono” package in Ubuntu: New Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin When testing a large number of phone calls it could be seen that on certain calls there would be a significant delay between the snap decision dialog being displayed and the ringtone beginning to play. In extreme circumstances this could cause calls to be missed as there would not be enough time to answer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1394105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390618] Re: Uniy8 crashed when creating a wireless connection with an access point
** Changed in: dbus-cpp (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1390618 Title: Uniy8 crashed when creating a wireless connection with an access point Status in “dbus-cpp” package in Ubuntu: Fix Released Status in “media-hub” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Invalid Bug description: current build number: 11 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-07 19:25:24 version version: 11 version ubuntu: 20141106.1 version device: 20141106 version custom: 20141106.1 Had system-settings opened in order to verify for updates, but noticed that I didn't have any valid wireless connection, so when I tried to connect with my access point, unity8 crashed completely. This happened after adding the password and hitting 'Connect'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1390618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1391230] Re: web audio, pulse runs at 6% and screen will not blank on idle
** Package changed: pulseaudio (Ubuntu) = pulseaudio (Ubuntu RTM) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1391230 Title: web audio, pulse runs at 6% and screen will not blank on idle Status in “pulseaudio” package in Ubuntu RTM: Confirmed Bug description: RTM krillin image #154 boot phone - go to Music scope, launch a song in grooveshark, let song start playing application switch back to either Dash or some other application Music will stop due to life cycle kicking in Screen will not turn off attach top - pulse running ~6% if you open spread kill the groove shark web page, the phone will then dim/screen blank on idle you can see the pulse audio process eating 6% go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rtm/+source/pulseaudio/+bug/1391230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390618] Re: Uniy8 crashed when creating a wireless connection with an access point
The stack trace, it seems to be actually a bug on media-hub/dbus-cpp.
#0 __libc_do_syscall () at
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or
directory.
(gdb) bt full
#0 __libc_do_syscall () at
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
No locals.
#1 0xb6154e5e in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
_a1 = 0
_a3tmp = 6
_a1tmp = 0
_a3 = 6
_nametmp = 268
_a2tmp = 3747
_a2 = 3747
_name = 268
_sys_result = optimized out
pd = 0xb6f77000
pid = 0
selftid = 3747
#2 0xb6155b4e in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {1, 3055655487, 3055655416, 3055255819, 3055022821,
3069680328, 3069669376, 3069680504, 3069669376, 3055841280, 729240, 0, 1,
33527928, 40034132, 3069594101, 3069680504, 1, 5,
0, 3198701360, 3054717864, 1, 3055656472, 1, 36773876,
3056202129, 40338480, 3198701360, 3069612528, 40338360, 3069670608}}, sa_flags
= 1, sa_restorer = 0x0}
sigs = {__val = {32, 0 repeats 31 times}}
#3 0xb62920fc in __gnu_cxx::__verbose_terminate_handler () at
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:84
w = optimized out
exc = @0x0: error reading variable
name = optimized out
terminating = true
t = optimized out
#4 0xb6290920 in std::rethrow_exception (ep=...) at
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:246
obj = optimized out
dep = 0x2678430
#5 0xb6290b96 in __GXX_INIT_PRIMARY_EXCEPTION_CLASS (c=0xb629091f
std::rethrow_exception(std::__exception_ptr::exception_ptr)+86
b\204\370#\020\204\370$\020\204\370% \204\370
\340`(F\374\367\220\350(F\373\367\200\352\375\367, incomplete sequence \352)
at ../../../../src/libstdc++-v3/libsupc++/unwind-cxx.h:271
No locals.
#6 __cxxabiv1::__cxa_throw (obj=0xb6290977 std::set_terminate(void
(*)())+30, tinfo=0xb62f7260 typeinfo for std::runtime_error, dest=0xb629f191
std::out_of_range::~out_of_range()+4) at
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:76
globals = optimized out
#7 0xad96371e in core::dbus::Bus::remove_match (this=optimized out,
rule=...) at
/build/buildd/dbus-cpp-4.2.0+15.04.20141105/src/core/dbus/bus.cpp:317
se = {d = std::unique_ptrcore::dbus::Error::Private containing
0x29c85f8}
#8 0xad96d3d2 in core::dbus::Service::remove_match (this=this@entry=0x1ff9878,
rule=...) at
/build/buildd/dbus-cpp-4.2.0+15.04.20141105/src/core/dbus/service.cpp:82
No locals.
#9 0xa7bd1852 in remove_match (rule=..., this=optimized out) at
/usr/include/core/dbus/impl/object.h:331
No locals.
#10 ~Signal (this=0x25635f0, __in_chrg=optimized out) at
/usr/include/core/dbus/impl/signal.h:35
No locals.
#11
std::_Sp_counted_ptrcore::dbus::Signalmpris::Player::Signals::EndOfStream,
void*, (__gnu_cxx::_Lock_policy)2::_M_dispose (this=optimized out) at
/usr/include/c++/4.9/bits/shared_ptr_base.h:373
No locals.
#12 0xa7bafb92 in std::_Sp_counted_base(__gnu_cxx::_Lock_policy)2::_M_release
(this=0x26ed138) at /usr/include/c++/4.9/bits/shared_ptr_base.h:149
No locals.
#13 0xa7bac65e in ~__shared_count (this=0x26a8ea4, __in_chrg=optimized out)
at /usr/include/c++/4.9/bits/shared_ptr_base.h:666
No locals.
#14 ~__shared_ptr (this=0x26a8ea0, __in_chrg=optimized out) at
/usr/include/c++/4.9/bits/shared_ptr_base.h:914
No locals.
#15 ~shared_ptr (this=0x26a8ea0, __in_chrg=optimized out) at
/usr/include/c++/4.9/bits/shared_ptr.h:93
No locals.
#16 ~DBus (this=0x26a8e98, __in_chrg=optimized out) at
/build/buildd/media-hub-2.0.0+15.04.20141105.1/src/core/media/player_stub.cpp:238
No locals.
#17 ~Signals (this=0x26a8e70, __in_chrg=optimized out) at
/build/buildd/media-hub-2.0.0+15.04.20141105.1/src/core/media/player_stub.cpp:173
No locals.
#18 ~Private (this=0x26a8da0, __in_chrg=optimized out) at
/build/buildd/media-hub-2.0.0+15.04.20141105.1/src/core/media/player_stub.cpp:95
No locals.
#19 operator() (this=optimized out, __ptr=0x26a8da0) at
/usr/include/c++/4.9/bits/unique_ptr.h:76
No locals.
#20 ~unique_ptr (this=0x26f3b0c, __in_chrg=optimized out) at
/usr/include/c++/4.9/bits/unique_ptr.h:236
No locals.
#21 core::ubuntu::media::PlayerStub::~PlayerStub (this=0x26f3b00,
__in_chrg=optimized out) at
/build/buildd/media-hub-2.0.0+15.04.20141105.1/src/core/media/player_stub.cpp:255
No locals.
#22 0xa7bac6c8 in core::ubuntu::media::PlayerStub::~PlayerStub (this=0x26f3b00,
__in_chrg=optimized out) at
/build/buildd/media-hub-2.0.0+15.04.20141105.1/src/core/media/player_stub.cpp:257
No locals.
---Type return to continue, or q return to quit---
#23 0xa8558cfc in maybeSpace (this=0xb6f81f10 __stack_chk_guard) at
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qdebug.h:99
No locals.
#24 operator (t=0xa8563048 Streams are
[Desktop-packages] [Bug 1380848] Re: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets
** Also affects: media-hub (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: media-hub (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: media-hub (Ubuntu RTM) Status: New = In Progress ** Changed in: media-hub (Ubuntu) Importance: Undecided = Critical ** Changed in: media-hub (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: media-hub (Ubuntu RTM) Assignee: (unassigned) = Ricardo Mendoza (ricmm) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1380848 Title: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets Status in Media Hub: In Progress Status in “dbus-cpp” package in Ubuntu: New Status in “media-hub” package in Ubuntu: Fix Released Status in “media-hub” package in Ubuntu RTM: In Progress Bug description: I noticed that media-hub-service can get into a state where it uses a large amount of CPU. Steps to reproduce 1) Start music-app 2) Play music 3) Pause music 4) Close the music-app 5) $ pkill unity8 (to emulate unity crashing a resetting) Notice that media-hub-service is now using a large amount of CPU, note this [0] is the media-hub.log at the time. The device has to be reset to get the CPU usage back to normal. 0 - http://pastebin.ubuntu.com/8553411/ To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378397] Re: video thumbnails are not generated for some divx files
** Tags added: rtm14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1378397 Title: video thumbnails are not generated for some divx files Status in “gst-plugins-bad1.0” package in Ubuntu: Confirmed Status in “gst-plugins-base1.0” package in Ubuntu: Confirmed Status in “libhybris” package in Ubuntu: Fix Released Bug description: krillin build #187 last known good build: ? device build: b5e7e45 specific to krillin: Y Other references: - bug 1356331 Video thumbnails are not generated on krillin and mediascanner- service-2.0 crashes. It does not happen with all the videos but most of the one I tried and any format. Test Case: 1. Upload videos from http://www.divx.com/en/devices/profiles/video to the device 2. Go to the video scope and wait Expected result Thumbnails appear after a moment Actual Result No thumbnail. Connect to the device to watch apport running and a crash file of mediascanner-service-2.0 in /var/crash and mediascanner-service-2.0 using lot of CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1378397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1373404] Re: No warning of high volume level
One easy way in the indicator to know if the active port a headphone/headset: http://paste.ubuntu.com/8556022/ I think we should do the following: 1 - Check if the active port is headset; 2 - If headset, see if the volume for the multimedia role is higher than 75%. If higher, change it to 75% (this is basically what is done on Android). This check can be done once at every reboot (or every time someone plugs a headphone/headset). 3 - When changing volume for the multimedia role, warn the user if higher than 75%. You can also do the same for the other roles, but generally we are only concerned with multimedia. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: In Progress Status in “pulseaudio” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1328717] Re: When booting a device with headphones plugged in, audio actually plays through speakers
** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1328717 Title: When booting a device with headphones plugged in, audio actually plays through speakers Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: 1) Turn off your device 2) Plug in headphones 3) Boot the device 4) Start playing audio (eg via music-app) 5) Notice audio is played through the speakers and not the headphones It was expected that the audio would be played through the headphones. # system-image-cli -i current build number: 76 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-06-10 11:58:50 version version: 76 version ubuntu: 20140610 version device: 20140530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1328717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309734] Re: music playing on headphones is played on speaker when phone rings
** Project changed: pulseaudio = pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed ** Changed in: pulseaudio (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1309734 Title: music playing on headphones is played on speaker when phone rings Status in Media Hub: Invalid Status in Music application for Ubuntu devices: Invalid Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Summary: music playing on headphones is played on speaker when phone rings steps: 1. import music in music folder 2. open music app and play song 3. plug in headphones 4. call phone 5. decline phone call expected result: ringer is heard on headphones and speaker. music continues playing on headphones actual results: ringer and music is heard on speaker, music plays on speakers, must unplug and plugin headphones to resume playing music on headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1309734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1324678] Re: [Nexus 4] Earpiece volume too high as compared to Android
The voicecall volume is on a similar level as used by android now, and can be adjusted from the indicator. ** Package changed: alsa-lib (Ubuntu) = pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1324678 Title: [Nexus 4] Earpiece volume too high as compared to Android Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: The earpiece volume during a call is too high on my nexus 4, feels like the earpiece may even burst. That is not a problem on Android. So I believe the setting needs some adjustment on the lower level. rsalveti: What you mean is basically that we might need to tune the volume when enabling voice call (earpiece). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1324678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363083] Re: Music playback does not re-route audio when Bluetooth speaker connected/disconnected
Fixes available at https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-019/ ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = In Progress ** Changed in: ubuntu-touch-session (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1363083 Title: Music playback does not re-route audio when Bluetooth speaker connected/disconnected Status in “pulseaudio” package in Ubuntu: In Progress Status in “ubuntu-touch-session” package in Ubuntu: In Progress Bug description: krillin ubuntu-rtm/14.09-proposed build 4. bluez 4.101-0ubuntu19 armhf SUMMARY: When a Bluetooth speaker is connected/disconnected to the krillin, the music playback route does not automatically update to accomodate this. The music app must be re-started for the new configuration to work. STEPS: 1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss) 2) Start music playback 3) Disconnect the Bluetooth speaker on krillin from the Bluetooth settings EXPECTED RESULT: The music should play back through the Bluetooth speaker until it is disconnected. When the speaker is disconnected it should revert to using the krillin loud speaker. ACTUAL RESULT: The music plays back through the Bluetooth speaker until it is disconnected. When the speaker is disconnected, there is no music heard from the krillin. The music app is still playing the track as the progress bar is still updating, but there is no sound. When the music app is re-started, music will play through the krillin loud speaker. NOTES: The same problem is observed for the opposite situation where a Bluetooth speaker is connected to the device when it is already playing music through the krillin loud speaker. The Bluetooth speaker will only be used once the music app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1363083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378397] Re: video thumbnails are not generated for some divx files
Fixes at: https://code-review.phablet.ubuntu.com/#/c/328/ https://github.com/jhodapp/gst-plugins-bad/pull/5 ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #737599 https://bugzilla.gnome.org/show_bug.cgi?id=737599 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1378397 Title: video thumbnails are not generated for some divx files Status in “gst-plugins-bad1.0” package in Ubuntu: New Status in “gst-plugins-base1.0” package in Ubuntu: New Status in “libhybris” package in Ubuntu: New Bug description: krillin build #187 last known good build: ? device build: b5e7e45 specific to krillin: Y Other references: - bug 1356331 Video thumbnails are not generated on krillin and mediascanner- service-2.0 crashes. It does not happen with all the videos but most of the one I tried and any format. Test Case: 1. Upload videos from http://www.divx.com/en/devices/profiles/video to the device 2. Go to the video scope and wait Expected result Thumbnails appear after a moment Actual Result No thumbnail. Connect to the device to watch apport running and a crash file of mediascanner-service-2.0 in /var/crash and mediascanner-service-2.0 using lot of CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1378397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378397] Re: video thumbnails are not generated for some divx files
gst-plugins-base part available at https://bugzilla.gnome.org/show_bug.cgi?id=737599 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1378397 Title: video thumbnails are not generated for some divx files Status in “gst-plugins-bad1.0” package in Ubuntu: New Status in “gst-plugins-base1.0” package in Ubuntu: New Status in “libhybris” package in Ubuntu: New Bug description: krillin build #187 last known good build: ? device build: b5e7e45 specific to krillin: Y Other references: - bug 1356331 Video thumbnails are not generated on krillin and mediascanner- service-2.0 crashes. It does not happen with all the videos but most of the one I tried and any format. Test Case: 1. Upload videos from http://www.divx.com/en/devices/profiles/video to the device 2. Go to the video scope and wait Expected result Thumbnails appear after a moment Actual Result No thumbnail. Connect to the device to watch apport running and a crash file of mediascanner-service-2.0 in /var/crash and mediascanner-service-2.0 using lot of CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1378397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378397] Re: video thumbnails are not generated for some divx files
** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New = Confirmed ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New = Confirmed ** Changed in: libhybris (Ubuntu) Status: New = Confirmed ** Changed in: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided = High ** Changed in: gst-plugins-base1.0 (Ubuntu) Importance: Undecided = High ** Changed in: libhybris (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1378397 Title: video thumbnails are not generated for some divx files Status in “gst-plugins-bad1.0” package in Ubuntu: Confirmed Status in “gst-plugins-base1.0” package in Ubuntu: Confirmed Status in “libhybris” package in Ubuntu: Confirmed Bug description: krillin build #187 last known good build: ? device build: b5e7e45 specific to krillin: Y Other references: - bug 1356331 Video thumbnails are not generated on krillin and mediascanner- service-2.0 crashes. It does not happen with all the videos but most of the one I tried and any format. Test Case: 1. Upload videos from http://www.divx.com/en/devices/profiles/video to the device 2. Go to the video scope and wait Expected result Thumbnails appear after a moment Actual Result No thumbnail. Connect to the device to watch apport running and a crash file of mediascanner-service-2.0 in /var/crash and mediascanner-service-2.0 using lot of CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1378397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363083] Re: Music playback does not re-route audio when Bluetooth speaker connected/disconnected
** Package changed: bluez (Ubuntu) = pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1363083 Title: Music playback does not re-route audio when Bluetooth speaker connected/disconnected Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: krillin ubuntu-rtm/14.09-proposed build 4. bluez 4.101-0ubuntu19 armhf SUMMARY: When a Bluetooth speaker is connected/disconnected to the krillin, the music playback route does not automatically update to accomodate this. The music app must be re-started for the new configuration to work. STEPS: 1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss) 2) Start music playback 3) Disconnect the Bluetooth speaker on krillin from the Bluetooth settings EXPECTED RESULT: The music should play back through the Bluetooth speaker until it is disconnected. When the speaker is disconnected it should revert to using the krillin loud speaker. ACTUAL RESULT: The music plays back through the Bluetooth speaker until it is disconnected. When the speaker is disconnected, there is no music heard from the krillin. The music app is still playing the track as the progress bar is still updating, but there is no sound. When the music app is re-started, music will play through the krillin loud speaker. NOTES: The same problem is observed for the opposite situation where a Bluetooth speaker is connected to the device when it is already playing music through the krillin loud speaker. The Bluetooth speaker will only be used once the music app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1363083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363083] Re: Music playback does not re-route audio when Bluetooth speaker connected/disconnected
** Also affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1363083 Title: Music playback does not re-route audio when Bluetooth speaker connected/disconnected Status in “pulseaudio” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: New Bug description: krillin ubuntu-rtm/14.09-proposed build 4. bluez 4.101-0ubuntu19 armhf SUMMARY: When a Bluetooth speaker is connected/disconnected to the krillin, the music playback route does not automatically update to accomodate this. The music app must be re-started for the new configuration to work. STEPS: 1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss) 2) Start music playback 3) Disconnect the Bluetooth speaker on krillin from the Bluetooth settings EXPECTED RESULT: The music should play back through the Bluetooth speaker until it is disconnected. When the speaker is disconnected it should revert to using the krillin loud speaker. ACTUAL RESULT: The music plays back through the Bluetooth speaker until it is disconnected. When the speaker is disconnected, there is no music heard from the krillin. The music app is still playing the track as the progress bar is still updating, but there is no sound. When the music app is re-started, music will play through the krillin loud speaker. NOTES: The same problem is observed for the opposite situation where a Bluetooth speaker is connected to the device when it is already playing music through the krillin loud speaker. The Bluetooth speaker will only be used once the music app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1363083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1366819] Re: PulseAudio crashed unexpectedly
Chris Gagnon, the mako and krillin bug are not related with this bug and it was already fixed at https://launchpad.net/ubuntu/+source/ubuntu- touch-session/0.108+14.10.20140929-0ubuntu2 ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = New ** Changed in: pulseaudio (Ubuntu) Importance: Critical = Undecided ** Tags removed: armhf rtm14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1366819 Title: PulseAudio crashed unexpectedly Status in “pulseaudio” package in Ubuntu: New Bug description: PulseAudio crash error occurred without PulseAudio or any audio application open. Error occurred while opening new Firefox 32 tab. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Sep 8 08:42:12 2014 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-09-02 (6 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140826.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/16/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.60 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10ST dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.60:bd01/16/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMKU-04002Q:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite P50-A dmi.product.version: PSPMKU-04002Q dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1366819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1375249] Re: telepathy-ofono tries to open /proc/1728/fd/ and is DENIED access by apparmor
** Package changed: telepathy-mission-control-5 (Ubuntu) = telepathy- ofono (Ubuntu) ** Changed in: telepathy-ofono (Ubuntu) Status: New = In Progress ** Changed in: telepathy-ofono (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1375249 Title: telepathy-ofono tries to open /proc/1728/fd/ and is DENIED access by apparmor Status in “telepathy-ofono” package in Ubuntu: In Progress Bug description: I noticed quite a few occurences of these in my logs: hablet@ubuntu-phablet:/usr/share/ofono/scripts$ sudo dmesg | grep -i ofo [sudo] password for phablet: [ 16.814527] type=1400 audit(1411984297.763:93): apparmor=DENIED operation=open profile=/usr/lib/telepathy/telepathy-ofono name=/proc/1728/fd/ pid=1728 comm=telepathy-ofono requested_mask=r denied_mask=r fsuid=32011 ouid=32011 [ 16.827926] type=1400 audit(1411984297.783:94): apparmor=DENIED operation=exec profile=/usr/lib/telepathy/telepathy-ofono name=/usr/bin/pulseaudio pid=1728 comm=telepathy-ofono requested_mask=x denied_mask=x fsuid=32011 ouid=0 [ 16.843247] type=1400 audit(1411984297.793:95): apparmor=DENIED operation=open profile=/usr/lib/telepathy/telepathy-ofono name=/proc/1729/fd/ pid=1729 comm=telepathy-ofono requested_mask=r denied_mask=r fsuid=32011 ouid=32011 [ 16.865588] type=1400 audit(1411984297.813:96): apparmor=DENIED operation=exec profile=/usr/lib/telepathy/telepathy-ofono name=/usr/bin/pulseaudio pid=1729 comm=telepathy-ofono requested_mask=x denied_mask=x fsuid=32011 ouid=0 [ 16.878315] type=1400 audit(1411984297.833:97): apparmor=DENIED operation=open profile=/usr/lib/telepathy/telepathy-ofono name=/proc/1735/fd/ pid=1735 comm=telepathy-ofono requested_mask=r denied_mask=r fsuid=32011 ouid=32011 [ 16.882130] type=1400 audit(1411984297.833:98): apparmor=DENIED operation=exec profile=/usr/lib/telepathy/telepathy-ofono name=/usr/bin/pulseaudio pid=1735 comm=telepathy-ofono requested_mask=x denied_mask=x fsuid=32011 ouid=0 Not sure how bad that is. But incidentally, I have not been able to get my new SIM to be recognized by the system. This is on an N4 running utopic, image #257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1375249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) ** Tags added: touch-2014-10-9 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1224756 Title: Pulseaudio should integrate with trust-store Status in “pulseaudio” package in Ubuntu: Triaged Bug description: Currently the 'audio' policy group allows access to pulseaudio which allows apps to use the microphone and eavesdrop on the user. Pulseaudio needs to be modified to use trust-store, like location- service does. Integrating with trust-store means that when an app tries use the microphone via pulseaudio, pulseaudio will contact trust-store, the trust-store will prompt the user (Foo wants to use the microphone. Is this ok? Yes|No), optionally cache the result and return the result to pulseaudio. In this manner the user is given a contextual prompt at the time of access by the app. Using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in settings. Targeting to T-Series for now, since the trust-store is not in a reusable form yet. Original description: David and the security team (inspired by an observation from Rick) discussed that when recording, pulseaudio should somehow unobtrusively show the user that it is recording. The easiest thing to do would be for pulseaudio to alert indicator-sound which would then turn its icon red (similar to indicator-message turning blue with new messages). Marking 'high' because apps with access to pulseaudio can currently eavedrop on users. If the app is allowed to do networking (the default for apps), then it can ship that information off to a server somewhere. Note 1, the alert to indicator-sound must happen via the out of process pulseaudio server and not the confined app itself to be effective. Note 2, we should consider how to enforce this for foreground apps only. Application lifecycle should probably handle this for 13.10 (apps are suspended if not in foreground or if the screensaver is on), but we don't want an app on the converged device to record in the background when the user isn't paying attention. Example eavesdropping attack: start recording only when the screensaver is on (perhaps inhibiting the screensaver during recording would be enough). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1224756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1373392] Re: [mako] high cpu usage when playing audio via speaker
** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed ** Changed in: pulseaudio (Ubuntu) Importance: Undecided = High ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1373392 Title: [mako] high cpu usage when playing audio via speaker Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: $ system-image-cli -i current build number: 253 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-09-24 00:51:54 version version: 253 version ubuntu: 20140923.1 version device: 20140923.1 version custom: mako-0.6 I noticed that when playing audio via the speaker/headphones the CPU usage is higher than when playing via a paired bluetooth speaker. Speaker CPU usage: Format pulse media-hub m4a 30 20 flac 30 15 mp3 25 20 Bluetooth Speaker CPU usage: Format pulse media-hub m4a 10 15 flac 10 10 mp3 15 10 It has been suggested that changing the buffer size may resolve this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1373392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval
We could later on have a separated role for dtmf, that would not be affected by corking and not by ducking, but that is currently not possible as it'd break the silent mode use case. Once we're able to group roles, and separate behaviour with volume, we can get this fixed, but post RTM. ** Also affects: tone-generator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1370091 Title: With music playing, pressing the dialpad keys reduces the volume for an odd interval Status in “pulseaudio” package in Ubuntu: Confirmed Status in “tone-generator” package in Ubuntu: Confirmed Bug description: 1. play a track 2. open dialer-app and press the keypad What happens: The sound music turns down for a few seconds and then gets back to normal automatically. While the above feels like a good idea, it need refinement. In its current condition it rather feels broken. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Tue Sep 16 19:45:21 2014 InstallationDate: Installed on 2014-09-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-020205) SourcePackage: media-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1370091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval
So from IRC it's more about the lack of a fading effect when ducking the sound. There's also an issue that the dtmf tone takes a while to disappear after playing the sound, and for that I added a bugtask for tone generator. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed ** Changed in: tone-generator (Ubuntu) Status: New = Confirmed ** Changed in: pulseaudio (Ubuntu) Importance: Undecided = Medium ** Changed in: tone-generator (Ubuntu) Importance: Undecided = Medium ** Changed in: tone-generator (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) = Ricardo Salveti (rsalveti) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1370091 Title: With music playing, pressing the dialpad keys reduces the volume for an odd interval Status in “pulseaudio” package in Ubuntu: Confirmed Status in “tone-generator” package in Ubuntu: Confirmed Bug description: 1. play a track 2. open dialer-app and press the keypad What happens: The sound music turns down for a few seconds and then gets back to normal automatically. While the above feels like a good idea, it need refinement. In its current condition it rather feels broken. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Tue Sep 16 19:45:21 2014 InstallationDate: Installed on 2014-09-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-020205) SourcePackage: media-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1370091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval
The question here is more to what is the desired behaviour when playing DTMF tones. It needs to be an alert, as on silent mode you don't want it to play, but any alert at this moment will trigger the ducking effect described by the bug. Do we want it to duck or to cork? Cork would be even more confusing imho. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1370091 Title: With music playing, pressing the dialpad keys reduces the volume for an odd interval Status in “pulseaudio” package in Ubuntu: Confirmed Status in “tone-generator” package in Ubuntu: Confirmed Bug description: 1. play a track 2. open dialer-app and press the keypad What happens: The sound music turns down for a few seconds and then gets back to normal automatically. While the above feels like a good idea, it need refinement. In its current condition it rather feels broken. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Tue Sep 16 19:45:21 2014 InstallationDate: Installed on 2014-09-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-020205) SourcePackage: media-hub UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1370091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1318360] Re: Poor microphone quality (mako)
Removing rtm tag because this is not affecting the RTM hardware. Will investigate the mako specific issue still though. ** Tags removed: rtm14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359125] Re: ringtone played when on active call
** Changed in: pulseaudio (Ubuntu) Status: In Progress = Fix Released ** Changed in: media-hub (Ubuntu) Status: New = Fix Released ** Package changed: dialer-app (Ubuntu) = telephony-service (Ubuntu) ** Changed in: telephony-service (Ubuntu) Assignee: Gustavo Pichorim Boiko (boiko) = Ricardo Salveti (rsalveti) ** Changed in: telephony-service (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1359125 Title: ringtone played when on active call Status in “media-hub” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Fix Released Bug description: build #199 When there is an incoming call during an active call, the notification uses the configured ringtone. It's very loud to the point you cannot talk anymore until the notification is dismissed. This is very intrusive and the notification should be more discreet like a small beep and a vibration. This behaviour should be the same for all the notifications (alarms, messages) when a call is active. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.6-0ubuntu1 Architecture: armhf Date: Wed Aug 20 09:27:50 2014 InstallationDate: Installed on 2014-08-19 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140819-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1359125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] [NEW] Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
Public bug reported: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. ** Affects: lightdm (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
root@ubuntu-phablet:/var/log/lightdm# cat lightdm.log [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.11.7, UID=0 PID=1323 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/52-ubuntu-touch.conf [+0.00s] DEBUG: Loading configuration dirs from /custom/xdg/data/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/90-phablet.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Registered seat module xlocal [+0.01s] DEBUG: Registered seat module xremote [+0.01s] DEBUG: Registered seat module unity [+0.06s] DEBUG: Monitoring logind for seats [+0.06s] DEBUG: New seat added from logind: seat0 [+0.06s] DEBUG: Seat seat0: Starting [+0.07s] DEBUG: Using VT 1 [+0.07s] DEBUG: DisplayServer: Logging to /var/log/lightdm/unity-system-compositor.log [+0.07s] DEBUG: Launching process 1369: /usr/share/ubuntu-touch-session/usc-wrapper --file '/run/mir_socket' --from-dm-fd 10 --to-dm-fd 13 --vt 1 [+0.07s] DEBUG: DisplayServer: Waiting for system compositor for 60s [+0.07s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.07s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.30s] DEBUG: Loading users from org.freedesktop.Accounts [+0.30s] DEBUG: User /org/freedesktop/Accounts/User32011 added [+1.43s] DEBUG: DisplayServer: READY [+1.43s] DEBUG: DisplayServer: Compositor ready [+1.43s] DEBUG: Seat seat0: Compositor ready [+1.43s] DEBUG: Seat seat0: Creating user session [+1.43s] DEBUG: Seat seat0: Creating display server of type mir [+1.44s] DEBUG: Seat seat0: Display server ready, starting session authentication [+1.44s] DEBUG: Session pid=1623: Started with service 'lightdm-autologin', username 'phablet' [+1.50s] DEBUG: Session pid=1623: Authentication complete with return value 0: Success [+1.50s] DEBUG: Seat seat0: Session authenticated, running command [+1.50s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0 [+1.51s] DEBUG: Session pid=1623: Running command /usr/sbin/ubuntu-touch-lightdm-session ubuntu-touch-session [+1.51s] DEBUG: Creating shared data directory /var/lib/lightdm-data/phablet [+1.51s] DEBUG: Session pid=1623: Logging to .xsession-errors root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log Warning: ignoring unrecognised arguments: --vt 1 GL_VENDOR = ARM GL_RENDERER = Mali-400 MP GL_VERSION = OpenGL ES 2.0 dm_connection_start WARNING: QApplication was not created in the main() thread. initialized brightness parameters Opening session session-0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. From time to time it also works fine, but it's harder to get into a working state (without restarting lightdm by hand) than actually reproducing the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
** Attachment added: u-s-c with 1.11.6 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+attachment/4193835/+files/unity-system-compositor.log.old -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. From time to time it also works fine, but it's harder to get into a working state (without restarting lightdm by hand) than actually reproducing the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
** Attachment added: u-s-c with 1.11.7 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+attachment/4193834/+files/unity-system-compositor.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. From time to time it also works fine, but it's harder to get into a working state (without restarting lightdm by hand) than actually reproducing the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
** Attachment added: lightdm log from 1.11.6 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+attachment/4193837/+files/lightdm.log.old -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. From time to time it also works fine, but it's harder to get into a working state (without restarting lightdm by hand) than actually reproducing the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
** Attachment added: lightdm log from 1.11.7 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+attachment/4193836/+files/lightdm.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. From time to time it also works fine, but it's harder to get into a working state (without restarting lightdm by hand) than actually reproducing the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
root@ubuntu-phablet:~# lightdm --show-config [SeatDefaults] A greeter-wrapper=/usr/lib/lightdm/lightdm-greeter-session B guest-wrapper=/usr/lib/lightdm/lightdm-guest-session C xserver-command=X -core D type=unity D user-session=ubuntu-touch D session-wrapper=/usr/sbin/ubuntu-touch-lightdm-session D unity-compositor-command=/usr/share/ubuntu-touch-session/usc-wrapper E autologin-user=phablet [LightDM] D minimum-vt=1 Sources: A /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf B /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf C /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf D /usr/share/lightdm/lightdm.conf.d/52-ubuntu-touch.conf E /etc/lightdm/lightdm.conf.d/90-phablet.conf ** Description changed: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. + + From time to time it also works fine, but it's harder to get into a + working state (without restarting lightdm by hand) than actually + reproducing the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. From time to time it also works fine, but it's harder to get into a working state (without restarting lightdm by hand) than actually reproducing the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
And the diff between 11.6 and 11.7: root@ubuntu-phablet:/var/log/lightdm# diff -Naur lightdm.log.old lightdm.log --- lightdm.log.old 2014-09-03 02:57:18.492387008 + +++ lightdm.log 2014-09-03 02:57:38.37001 + @@ -1,5 +1,5 @@ [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log -[+0.00s] DEBUG: Starting Light Display Manager 1.11.6, UID=0 PID=1309 +[+0.00s] DEBUG: Starting Light Display Manager 1.11.7, UID=0 PID=1323 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf @@ -10,36 +10,30 @@ [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/90-phablet.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager -[+0.00s] DEBUG: Registered seat module xlocal -[+0.00s] DEBUG: Registered seat module xremote -[+0.00s] DEBUG: Registered seat module unity -[+0.00s] DEBUG: Registered seat module surfaceflinger -[+0.04s] DEBUG: Adding default seat -[+0.04s] DEBUG: Seat: Starting -[+0.05s] DEBUG: Using VT 1 -[+0.05s] DEBUG: DisplayServer: Logging to /var/log/lightdm/unity-system-compositor.log -[+0.06s] DEBUG: Launching process 1355: /usr/share/ubuntu-touch-session/usc-wrapper --file '/run/mir_socket' --from-dm-fd 10 --to-dm-fd 13 --vt 1 -[+0.06s] DEBUG: DisplayServer: Waiting for system compositor for 60s -[+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager -[+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 -[+0.27s] DEBUG: Loading users from org.freedesktop.Accounts -[+0.27s] DEBUG: User /org/freedesktop/Accounts/User32011 added -[+1.83s] DEBUG: DisplayServer: READY -[+1.83s] DEBUG: DisplayServer: Compositor ready -[+1.83s] DEBUG: Seat: Compositor ready -[+1.83s] DEBUG: Seat: Creating user session -[+1.83s] DEBUG: Seat: Creating display server of type mir -[+1.85s] DEBUG: Seat: Display server ready, starting session authentication -[+1.85s] DEBUG: Session pid=1685: Started with service 'lightdm-autologin', username 'phablet' -[+1.94s] DEBUG: Session pid=1685: Authentication complete with return value 0: Success -[+1.94s] DEBUG: Seat: Session authenticated, running command -[+1.94s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0 -[+1.95s] DEBUG: Session pid=1685: Running command /usr/sbin/ubuntu-touch-lightdm-session ubuntu-touch-session -[+1.95s] DEBUG: Creating shared data directory /var/lib/lightdm-data/phablet -[+1.95s] DEBUG: Session pid=1685: Logging to .xsession-errors -[+2.00s] DEBUG: Seat: Switching to Mir session session-0 -[+2.00s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c2 -[+2.85s] DEBUG: User /org/freedesktop/Accounts/User32011 changed -[+7.06s] DEBUG: User /org/freedesktop/Accounts/User0 added -[+58.92s] DEBUG: User /org/freedesktop/Accounts/User32011 changed -[+110.40s] DEBUG: User /org/freedesktop/Accounts/User32011 changed +[+0.01s] DEBUG: Registered seat module xlocal +[+0.01s] DEBUG: Registered seat module xremote +[+0.01s] DEBUG: Registered seat module unity +[+0.06s] DEBUG: Monitoring logind for seats +[+0.06s] DEBUG: New seat added from logind: seat0 +[+0.06s] DEBUG: Seat seat0: Starting +[+0.07s] DEBUG: Using VT 1 +[+0.07s] DEBUG: DisplayServer: Logging to /var/log/lightdm/unity-system-compositor.log +[+0.07s] DEBUG: Launching process 1369: /usr/share/ubuntu-touch-session/usc-wrapper --file '/run/mir_socket' --from-dm-fd 10 --to-dm-fd 13 --vt 1 +[+0.07s] DEBUG: DisplayServer: Waiting for system compositor for 60s +[+0.07s] DEBUG: Acquired bus name org.freedesktop.DisplayManager +[+0.07s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 +[+0.30s] DEBUG: Loading users from org.freedesktop.Accounts +[+0.30s] DEBUG: User /org/freedesktop/Accounts/User32011 added +[+1.43s] DEBUG: DisplayServer: READY +[+1.43s] DEBUG: DisplayServer: Compositor ready +[+1.43s] DEBUG: Seat seat0: Compositor ready +[+1.43s] DEBUG: Seat seat0: Creating user session +[+1.43s] DEBUG: Seat seat0: Creating display server of type mir +[+1.44s] DEBUG: Seat seat0: Display server ready, starting session authentication +[+1.44s] DEBUG: Session pid=1623: Started with service 'lightdm-autologin', username 'phablet' +[+1.50s] DEBUG: Session pid=1623: Authentication complete with return value 0: Success +[+1.50s] DEBUG: Seat seat0: Session authenticated, running command +[+1.50s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0 +[+1.51s] DEBUG: Session pid=1623: Running command /usr/sbin/ubuntu-touch-lightdm-session ubuntu-touch-session +[+1.51s] DEBUG: Creating shared data directory /var/lib/lightdm-data/phablet +[+1.51s] DEBUG: Session pid=1623: Logging to .xsession-errors
[Desktop-packages] [Bug 1364725] Re: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1
** Attachment added: lightdm log from 1.11.7 (from a working boot) https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+attachment/4193839/+files/lightdm.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1364725 Title: Krillin fails to display spinner/unity8 after upgrade to 1.11.7-0ubuntu1 Status in “lightdm” package in Ubuntu: New Bug description: I noticed that after mako's version 213 of ubuntu touch (http://people.canonical.com/~ogra/touch-image-stats/213.changes), the display started failing quite frequently when using it with krillin (rtm is fine though). Tracking down the changes, it seems that the lightdm update from 1.11.6-0ubuntu1 to 1.11.7-0ubuntu1 is the one causing the issue, as I can get my display to work perfectly fine with latest image + lightdm 1.11.6-0ubuntu1 The symptom is a bit weird though, as the display itself is on (with proper brightness and so on), but nothing showing up on the screen (like not being rendered for some reason). Display power off/on doesn't help, and it seems Unity8 is running fine in the background. When I get this issue, I'm also not able to see the ubuntu touch spinner before Unity8 is up. One way to get a working display again is by restarting ligthdm by hand. From time to time it also works fine, but it's harder to get into a working state (without restarting lightdm by hand) than actually reproducing the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1364725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340249] Re: No volume control over speakerphone
Fixed in pulseaudio 1:4.0-0ubuntu19. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1340249 Title: No volume control over speakerphone Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: When putting the phone in speakerphone mode, there's no way to adjust the volume of the call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1340249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1318360] Re: Poor microphone quality (mako)
Can you try the latest image and see if you can still reproduce the issue? We're not yet applying filters, but the volume was adjusted, so I wonder if that would also affect this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1361617] Re: DTMF tones when dialing use wrong speaker
** Package changed: pulseaudio (Ubuntu) = tone-generator (Ubuntu) ** Changed in: tone-generator (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1361617 Title: DTMF tones when dialing use wrong speaker Status in “tone-generator” package in Ubuntu: Fix Released Bug description: When dialing a number, the generated DTMF tones are way too loud. It should use the handset speaker instead of the real speaker to make that noise. Currently its so loud that everyone around can hear which number you're dialing :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tone-generator/+bug/1361617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
