[Touch-packages] [Bug 2031252] Re: Playing video with audio freezes
** Package changed: alsa-driver (Ubuntu) => wireplumber (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2031252
Title:
Playing video with audio freezes
Status in wireplumber package in Ubuntu:
Confirmed
Bug description:
I'm not sure when this started, but any video I play with audio is not
working properly - it severely lags and/or freezes. This happens in
Youtube on both Chrome and Firefox, and in the regular GNOME media
player. Audio by itself works fine, and video with audio muted works
fine. I tried restarting and downgrading the kernel, to no avail.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ari2679 F pipewire
ari2700 F wireplumber
/dev/snd/seq: ari2679 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 13 17:22:56 2023
InstallationDate: Installed on 2022-06-07 (432 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago)
dmi.bios.date: 06/12/2023
dmi.bios.release: 1.61
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET85W (1.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XWCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XWCTO1WW
dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
dmi.product.version: ThinkPad X1 Carbon Gen 9
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2031252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2031252] Re: Playing video with audio freezes
This is still happening for me under Ubuntu 23.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2031252
Title:
Playing video with audio freezes
Status in alsa-driver package in Ubuntu:
New
Bug description:
I'm not sure when this started, but any video I play with audio is not
working properly - it severely lags and/or freezes. This happens in
Youtube on both Chrome and Firefox, and in the regular GNOME media
player. Audio by itself works fine, and video with audio muted works
fine. I tried restarting and downgrading the kernel, to no avail.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ari2679 F pipewire
ari2700 F wireplumber
/dev/snd/seq: ari2679 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 13 17:22:56 2023
InstallationDate: Installed on 2022-06-07 (432 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago)
dmi.bios.date: 06/12/2023
dmi.bios.release: 1.61
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET85W (1.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XWCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XWCTO1WW
dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
dmi.product.version: ThinkPad X1 Carbon Gen 9
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Has anyone found a solution to this problem? I have it too, my computer is an HP Envy x360 Convertible. Any help would be greatly appreciated! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.27
it doesn't look like it's going to be actioned at all, focal (graphics): EXIF/IPTC/XMP metadata manipulation tool [universe] 0.25-4ubuntu3: amd64 arm64 armhf ppc64el s390x which is awful, unfortunately. It's been 3 years now without an update. Not only for the security implications and all the known vulnerabilities but also for the problems this brings to other photography software that depends on exiv2, e.g. lensfun and all the apps that use lensfun, like darktable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.27 Status in exiv2 package in Ubuntu: Triaged Status in exiv2 package in Debian: Fix Released Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.26
Thanks Jeremy. It's a bit challenging for anyone doing photography work with recent hardware. Key apps like darktable and digicam rely on this library and ubuntu/debian are way behind. Last year's fedora had 0.26. Flatpaks could help, I tried darktable's and it includes an updated exiv2, but it has a huge drawback, OpenCL doesnt work with flatpaks (or snaps) yet, so its useless in my case (my photography workstation is built specifically for photo editing with opencl) I guess there is no choice but to try and build exiv2 manually and hope the system doesnt break :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.26 Status in exiv2 package in Ubuntu: Triaged Status in exiv2 package in Debian: Unknown Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.26
Exiv2 0.25 as used by ubuntu 18.04 and the upcoming 18.10 is really obsolete and this brings all kinds of annoying problems with darktable - inability to recognize lenses and so on. Even the current package in 18.10 is obsolete. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.26 Status in exiv2 package in Ubuntu: Triaged Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570310] Re: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
** Changed in: systemd (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1570310 Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in systemd package in Ubuntu: Opinion Bug description: I was upgrading from 15.10 to 16.04 when this error occur. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 21:41:53 2016 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu4_amd64.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2016-01-08 (96 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=70fa96eb-e0d8-4e65-b049-9cb150759b40 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-04-13 (0 days ago) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LJ.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX455LJ.203:bd04/22/2015:svnASUSTeKCOMPUTERINC.:pnX455LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X455LJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1570310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1512851] Re: No network error when making call
I am using the BQ aquaris E4.5 running 15.04 r26. Ari Den 04. nov. 2015 08:18, skrev Sebastien Bacher: > Thank you for your bug report, what device and image version are you > using? > > ** Changed in: dialer-app (Ubuntu) > Importance: Undecided => High > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1512851 Title: No network error when making call Status in dialer-app package in Ubuntu: New Bug description: When the dialer app is not running and I get redirected to it in order to make a call, the first time I hit the "call" button I invariably get the error message: "no network" even though the phone is connected to the GSM network. (My phone has the language set to Norwegian, so I am guessing this is the English equivalent to the message I get.) Here is what I do in detail: - I choose a number from the contacts list - I hit the phone icon next to the number to make a call, - the dialer app screen opens - I hit the "call" button, - message "no network" The status bar at the top shows the phone has a GSM connection the whole time. When I try again a couple of seconds later, the call gets placed normally. The same thing happens when switching from the messaging app to the dialer in order to call the person I have been texting. However, if I wait a moment after entering the dialer before pressing the "call" button, everything runs normally. If the dialer-app is already active in the background when the redirection happens, the bug does not occur. Some kind of slow start issue? Screen appearing before the app is actually ready to take the command? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1512851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512851] [NEW] No network error when making call
Public bug reported: When the dialer app is not running and I get redirected to it in order to make a call, the first time I hit the "call" button I invariably get the error message: "no network" even though the phone is connected to the GSM network. (My phone has the language set to Norwegian, so I am guessing this is the English equivalent to the message I get.) Here is what I do in detail: - I choose a number from the contacts list - I hit the phone icon next to the number to make a call, - the dialer app screen opens - I hit the "call" button, - message "no network" The status bar at the top shows the phone has a GSM connection the whole time. When I try again a couple of seconds later, the call gets placed normally. The same thing happens when switching from the messaging app to the dialer in order to call the person I have been texting. However, if I wait a moment after entering the dialer before pressing the "call" button, everything runs normally. If the dialer-app is already active in the background when the redirection happens, the bug does not occur. Some kind of slow start issue? Screen appearing before the app is actually ready to take the command? ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1512851 Title: No network error when making call Status in dialer-app package in Ubuntu: New Bug description: When the dialer app is not running and I get redirected to it in order to make a call, the first time I hit the "call" button I invariably get the error message: "no network" even though the phone is connected to the GSM network. (My phone has the language set to Norwegian, so I am guessing this is the English equivalent to the message I get.) Here is what I do in detail: - I choose a number from the contacts list - I hit the phone icon next to the number to make a call, - the dialer app screen opens - I hit the "call" button, - message "no network" The status bar at the top shows the phone has a GSM connection the whole time. When I try again a couple of seconds later, the call gets placed normally. The same thing happens when switching from the messaging app to the dialer in order to call the person I have been texting. However, if I wait a moment after entering the dialer before pressing the "call" button, everything runs normally. If the dialer-app is already active in the background when the redirection happens, the bug does not occur. Some kind of slow start issue? Screen appearing before the app is actually ready to take the command? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1512851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen
Update: I have tested this some more now and it seems like the delay from pressing the power button until the screen comes on gets longer the longer the time lapse since the phone was last booted. Yesterday, I had the following experience: * With the phone on and screen off, I pressed the power button and waited... * After more than 3 full minutes I gave up and pressed once more. The screen flashed on for a second and switced off. * Approximately 7-10s later I pressed the power button again. The screen did not light up. * This time I waited for 4 minutes before giving up and pressing the button again. The screen flashed on for a second and switced off. * Again, I waited a few seconds before pressing the button once more. The screen remained dark. * By now my patience was gone and I only waited 10-15s before pressing the buttong again, causing the screen to flash on-off like before. I then immediately pressed one more time and it came on. * When trying to unlock the screen there was an awful lagging behavior. * I decided to switch the phone completely off. * I then restarted the phone. Once it was on, I switched off the screen, waited a short while and pressed the button to switch it on. This time it came on right away. This is not the first time the phone has performed normally right after switching it on (after switching completely off). It is my impression than both the current bug as well as the tendency to lag when swiping across the screen and when scrolling, manifest themselves more the longer the time lapse since the last time the phone was powered on. I hope this helps to narrow down the cause. Good luck! Best regards, Ari Den 26. okt. 2015 23:38, skrev Michael Terry: > Thanks Ari, so that confirms that this is a delayed-screen-on bug, not a > screen-never-comes-on bug. > > You mentioned the shutdown dialog appearing. That's bug 1508563, with a > fix incoming. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Sometimes need 3 power button presses to turn on screen Status in Canonical System Image: Incomplete Status in Unity System Compositor: New Status in powerd package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen
Hi Michael, I just tested, but so far only three times. 1st time: Screen came on after 17s showing the "turn off / restart / cancel" dialogue box. This, incidentally, is something I often get when switching on the screen. 2nd time: Screen came on normally after 15s. 3rd time: Screen came on after 1s (i.e. right away). I will check some more and give an update tomorrow around the same time. Ari Den 26. okt. 2015 13:35, skrev Michael Terry: > Thanks, Ari. I also happened to catch this several times this weekend > on my phone, which is running rc-proposed (so OTA7+). > > Here's an interesting tidbit though: I tried waiting after the first > power button press. So rather than thinking "oh, I must not have hit it > right" and pressing it again (thus causing the screen to flash on and > then off immediately), I waited. Sometimes it took a LONG time like > 30s. But the screen eventually came on by itself. > > So this bug is *not* about the screen not coming on at all after a > press. But rather a long delay. > > Folks that are experiencing this bug: can you please verify by also > waiting next time your screen doesn't immediately come on after pressing > the power button? Please wait up to a minute to test. > > Knowing it's a delay may help narrow this down. A delay that > immediately gets short-circuited when the power button is pressed > again... > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Sometimes need 3 power button presses to turn on screen Status in Canonical System Image: Incomplete Status in Unity System Compositor: New Status in powerd package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen
Sorry for the late reply. I unfortunately overlooked your post.
Yes, I am on OTA-7 and I am getting it constantly, although not every
single time I want to turn on the screen.
Ari
Den 22. okt. 2015 20:20, skrev Michael Terry:
> I'm beginning to doubt that this is particularly associated with system
> load (there was speculation that this is related to the scenario of wifi
> APs causing NetworkManager and dbus-daemon to go crazy, slowing down the
> system, which is a separate bug).
>
> I've used the following script in /etc/init/load.conf to simulate heavy
> system load:
>
> description "load"
> manual
> script
> while true; do true; done &
> while true; do true; done &
> while true; do true; done &
> while true; do true; done &
> while true; do true; done &
> exec cpulimit -l 1 -c 1 -p `ps ax | grep dbus-daemon | head -n 1 | awk
> '{print $1;}'`
> end script
>
> And it definitely slows things down. But I couldn't reproduce this
> specific bug with that running. I actually haven't seen it at all on my
> test or daily driver devices since OTA7. I don't know if that means it
> is fixed, harder to reproduce, or I've just been lucky.
>
> Ari, you mention seeing this a lot. Are you on OTA7?
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1429887
Title:
Sometimes need 3 power button presses to turn on screen
Status in Canonical System Image:
Incomplete
Status in Unity System Compositor:
New
Status in powerd package in Ubuntu:
Confirmed
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
[filing here although may be other components]
Mako running 211 from rtm
I experienced these symptoms which have been previously mitigated in other
scenarios.
Last week while traveling and roaming this happened pretty much 100% of the
time.
This occurred in all areas (hotel, MWC, outside, etc)
Press power button, no response
Press button again, screen turns on for a few seconds then turns off
Press button again, either phone resumes or more often the power dialog is
shown
When I returned back home the function was normal without reboot or
other changes.
The differences in environment:
Roaming on foreign GSM network
Lots of Wifi APs not connected
Attached are some perhaps relevant logs, unfortunately the syslog
rolled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen
On my handset I get the bug whether there are incoming notifications or not. I have reproduced it three times out of four attempts while writing a few emails on my laptop just now. No notifications. Regards, Ari Den 21. okt. 2015 20:08, skrev Robie Basak: > I think this might be related to the phone powering on the screen after > a notification. That is: I believe the occurrence is higher after the > phone has woken the screen (and perhaps then timed out), compared to > when there was no notification since I last used it. This is because it > seems to affect me more when I'm responding to something (eg. > notification LED with screen off) versus when I have taken the > initiative to use my phone. > > I also haven't seen this since OTA-7, where other bugs related to screen > power seem to have been fixed. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Sometimes need 3 power button presses to turn on screen Status in Canonical System Image: Incomplete Status in Unity System Compositor: New Status in powerd package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492161] Re: Messaging app sluggish after OTA-6
The description above quite accurately describes the behavior I am experiencing on my handset (BQ 4.5), both before and after upgrading to OTA-7. The only difference I experience is that the time before the contact names are displayed can be twice what is mentioned on occasions. (My address book has approximately 1000 entries.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1492161 Title: Messaging app sluggish after OTA-6 Status in messaging-app package in Ubuntu: Confirmed Bug description: Since OTA-6 on Bq Aquaris 4.5, the new messaging app is just unbearably slow. The app is very unresponsive and everything seems to take very long. Opening the app takes about 5 seconds, displaying contact names instead of numbers another 5 secs, opening a chat >=5 secs, sending message after pressing button some 3 seconds etc. Sometimes the app sort of pauses while typing, then after a few seconds showing the characters that have been entered. Unfortunately, the latency in the app is so bad it is almost unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1492161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen
The last comment here is from July and I have been experiencing this issue practically every single day since first asking about it on the Ubuntu Phone mailing list in April, so I thought I'd take the time to say that it is still an issue, and an extremely annoying one. If there is anything I can do to help (observe any specific behavior of my phone - BQ 4.5 - or carry out any specific test) I would be more than happy to do so. Just let me know! (I updated my phone to r25 on September 2nd. ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1429887 Title: Sometimes need 3 power button presses to turn on screen Status in Canonical System Image: Incomplete Status in Unity System Compositor: New Status in powerd package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1477838] Re: [MX4] Crackling sound after playing audio and suspended
Same bug is happening after i receive telegram or text message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1477838 Title: [MX4] Crackling sound after playing audio and suspended Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: The Meizu MX4 is doing a weird "tic tic tic..." after receive a notification (from telegram, mail...) and it's suspended. -- When I press the screen lock button on the MX4 shortly after playing music or ending a phone call I hear a radio/fuzzy distorted noise coming from the phone. To make it stop I need to unlock and lock the screen again but this is not ideal. - When the screen is locked and the playing song is finished and waiting for a stopped signal, MX4 will do a weird lower sound. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1477838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447199] [NEW] Qt 5.2.1 QtGraphicalEffects missing
Public bug reported: Ubuntu 14.04 is missing QtGraphicalEffects module. Interestingly, the doc packages for it exist: apt-cache search qtgraphicaleffects qtgraphicaleffects5-doc-html - Qt 5 graphicaleffects HTML documentation qtgraphicaleffects5-doc - Qt 5 graphical effects documentation Missing module leads to this kind of run time error messages when running QML apps trying to use it: file:///home/user/work/project/qml/MyElement.qml:2:1: module "QtGraphicalEffects" is not installed import QtGraphicalEffects 1.0 ^ In later versions of Ubuntu, there is package qml-module-qtgraphicaleffects but this does not exist in Ubuntu 14.04 Note: this module is indeed part of Qt 5.2.1, and it is found if Qt 5.2.1 is installed some other way, such as using binary Linux installers provided by Qt Project. ** Affects: qtgraphicaleffects-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtgraphicaleffects- opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1447199 Title: Qt 5.2.1 QtGraphicalEffects missing Status in qtgraphicaleffects-opensource-src package in Ubuntu: New Bug description: Ubuntu 14.04 is missing QtGraphicalEffects module. Interestingly, the doc packages for it exist: apt-cache search qtgraphicaleffects qtgraphicaleffects5-doc-html - Qt 5 graphicaleffects HTML documentation qtgraphicaleffects5-doc - Qt 5 graphical effects documentation Missing module leads to this kind of run time error messages when running QML apps trying to use it: file:///home/user/work/project/qml/MyElement.qml:2:1: module "QtGraphicalEffects" is not installed import QtGraphicalEffects 1.0 ^ In later versions of Ubuntu, there is package qml-module-qtgraphicaleffects but this does not exist in Ubuntu 14.04 Note: this module is indeed part of Qt 5.2.1, and it is found if Qt 5.2.1 is installed some other way, such as using binary Linux installers provided by Qt Project. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtgraphicaleffects-opensource-src/+bug/1447199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445133] [NEW] Ubuntu phone: Power button - screen wakeup bug
Public bug reported: I have experienced the issue below on my Nexus 4 since October 2014. Now it has appeared on my Bq Aquaris e4.5 approximately 3 weeks after I got the phone. I am currently running Ubuntu 14.10 (r20). Often, but not always, when pushing the power button to make the screen wake up, nothing happens. After waiting a few seconds, I push the button again and the screen wakes up for a fraction of a second and then turns off. The behavior suggests that the second time the button was pushed it was registered as a "switch off screen" command. This can repeat itself a few times. Usually, I have to push the button slightly harder/more decisively (perhaps a hint longer) in order for the screen to wake up and stay on. The screen will eventually come on after pushing the power button an odd number of times, never after an even number. Very annoying! I have tried just waiting for the screen to come on after initially pushing the power button, but my patience usually wears out after 10-15 seconds. I once waited for half a minute. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1445133 Title: Ubuntu phone: Power button - screen wakeup bug Status in unity8 package in Ubuntu: New Bug description: I have experienced the issue below on my Nexus 4 since October 2014. Now it has appeared on my Bq Aquaris e4.5 approximately 3 weeks after I got the phone. I am currently running Ubuntu 14.10 (r20). Often, but not always, when pushing the power button to make the screen wake up, nothing happens. After waiting a few seconds, I push the button again and the screen wakes up for a fraction of a second and then turns off. The behavior suggests that the second time the button was pushed it was registered as a "switch off screen" command. This can repeat itself a few times. Usually, I have to push the button slightly harder/more decisively (perhaps a hint longer) in order for the screen to wake up and stay on. The screen will eventually come on after pushing the power button an odd number of times, never after an even number. Very annoying! I have tried just waiting for the screen to come on after initially pushing the power button, but my patience usually wears out after 10-15 seconds. I once waited for half a minute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1445133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440535] [NEW] Hashtag '#' missing on dialer keyboard
Public bug reported: I am unable to access the hashtag '#' character on the dialer app keyboard. I am now running the latest stable release (r20) on the Aquaris e4.5, but I have had the same problem since October '14, running previous releases on my Nexus 4. The hashtag is frequently required as an "end of field" delimiter when entering numbers in response to automatic phone answering services in my country of residence (Norway). Not being able to access this character makes it impossible to enter the correct response to such services (i.e. some mobile bank services, ticket ordering services and many others). As a result I have had to leave merchandise at the counter when my account balance was too low, because I was unable to transfer funds on the spot using my cell phone. I hope this can be fixed very soon. Thank you! Ari ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1440535 Title: Hashtag '#' missing on dialer keyboard Status in dialer-app package in Ubuntu: New Bug description: I am unable to access the hashtag '#' character on the dialer app keyboard. I am now running the latest stable release (r20) on the Aquaris e4.5, but I have had the same problem since October '14, running previous releases on my Nexus 4. The hashtag is frequently required as an "end of field" delimiter when entering numbers in response to automatic phone answering services in my country of residence (Norway). Not being able to access this character makes it impossible to enter the correct response to such services (i.e. some mobile bank services, ticket ordering services and many others). As a result I have had to leave merchandise at the counter when my account balance was too low, because I was unable to transfer funds on the spot using my cell phone. I hope this can be fixed very soon. Thank you! Ari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1440535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
