[Touch-packages] [Bug 2048701] [NEW] Xorg freeze
Public bug reported: After updating from 23.04 to 23.10 Screen freezes on boot. Booting with 23.04 kernel 6.2.0-36 still works. After getting 6.5.11-060511 from kernel ppa it works fine. >From journal of failed X: jan 08 22:14:06 chromium kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] applying backlight present quirk jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] [ENCODER:76:DDI A/PHY A] HPD is down, disabling eDP jan 08 22:14:06 chromium kernel: i915 :00:02.0: [drm] *ERROR* crtc 45: Can't calculate constants, dotclock = 0! jan 08 22:14:06 chromium kernel: [ cut here ] jan 08 22:14:06 chromium kernel: i915 :00:02.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev)) jan 08 22:14:06 chromium kernel: WARNING: CPU: 1 PID: 101 at drivers/gpu/drm/drm_vblank.c:728 drm_crtc_vblank_helper_get_vblank_timestamp_internal+> jan 08 22:14:06 chromium kernel: Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm crct10dif_pclmul crc32_pclmul drm_display_helper cec polyval> jan 08 22:14:06 chromium kernel: CPU: 1 PID: 101 Comm: (udev-worker) Not tainted 6.5.0-14-generic #14-Ubuntu jan 08 22:14:06 chromium kernel: Hardware name: Acer Peppy, BIOS 03/02/2017 jan 08 22:14:06 chromium kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 df 49 68 e4 48 c7 c1 48 b5 71 c0 48 89 da 48 c7 c7 50 e3 71 c0 48 89 > jan 08 22:14:06 chromium kernel: RSP: 0018:a231804c3658 EFLAGS: 00010046 jan 08 22:14:06 chromium kernel: RAX: RBX: 933d80c7be30 RCX: jan 08 22:14:06 chromium kernel: RDX: RSI: RDI: jan 08 22:14:06 chromium kernel: RBP: a231804c36c8 R08: R09: jan 08 22:14:06 chromium kernel: R10: R11: R12: jan 08 22:14:06 chromium kernel: R13: 933d8b6f04a8 R14: a231804c36ec R15: 053f jan 08 22:14:06 chromium kernel: FS: 7fed1ae408c0() GS:933df8b0() knlGS: jan 08 22:14:06 chromium kernel: CS: 0010 DS: ES: CR0: 80050033 jan 08 22:14:06 chromium kernel: CR2: 56204b159120 CR3: 00010027c004 CR4: 000706e0 jan 08 22:14:06 chromium kernel: Call Trace: jan 08 22:14:06 chromium kernel: jan 08 22:14:06 chromium kernel: ? show_regs+0x6d/0x80 jan 08 22:14:06 chromium kernel: ? __warn+0x89/0x160 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? report_bug+0x17e/0x1b0 jan 08 22:14:06 chromium kernel: ? handle_bug+0x51/0xa0 jan 08 22:14:06 chromium kernel: ? exc_invalid_op+0x18/0x80 jan 08 22:14:06 chromium kernel: ? asm_exc_invalid_op+0x1b/0x20 jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x2ba/0x3f0 [drm] jan 08 22:14:06 chromium kernel: ? _raw_spin_lock_irqsave+0xe/0x20 jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_get_vblank_timestamp+0x18/0x30 [i915] jan 08 22:14:06 chromium kernel: drm_crtc_get_last_vbltimestamp+0x56/0x90 [drm] jan 08 22:14:06 chromium kernel: drm_reset_vblank_timestamp+0x73/0x100 [drm] jan 08 22:14:06 chromium kernel: drm_crtc_vblank_on+0xa9/0x1a0 [drm] jan 08 22:14:06 chromium kernel: ? assert_vblank_disabled+0x1d/0xd0 [i915] jan 08 22:14:06 chromium kernel: intel_crtc_vblank_on+0x34/0x90 [i915] jan 08 22:14:06 chromium kernel: intel_modeset_setup_hw_state+0x1ea/0x540 [i915] jan 08 22:14:06 chromium kernel: ? drm_modeset_lock_all_ctx+0x99/0x1d0 [drm] jan 08 22:14:06 chromium kernel: ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0xa0 [drm] jan 08 22:14:06 chromium kernel: intel_display_driver_probe_nogem+0x186/0x250 [i915] jan 08 22:14:06 chromium kernel: i915_driver_probe+0x315/0x5b0 [i915] jan 08 22:14:06 chromium kernel: ? drm_privacy_screen_get+0x16d/0x190 [drm] jan 08 22:14:06 chromium kernel: ? acpi_dev_found+0x64/0x80 jan 08 22:14:06 chromium kernel: i915_pci_probe+0xd0/0x170 [i915] jan 08 22:14:06 chromium kernel: local_pci_probe+0x44/0xb0 jan 08 22:14:06 chromium kernel: pci_call_probe+0x55/0x190 jan 08 22:14:06 chromium kernel: pci_device_probe+0x84/0x120 jan 08 22:14:06 chromium kernel: really_probe+0x1c4/0x410 jan 08 22:14:06 chromium kernel: __driver_probe_device+0x8c/0x180 jan 08 22:14:06 chromium kernel: driver_probe_device+0x24/0xd0 jan 08 22:14:06 chromium kernel: __driver_attach+0x10b/0x210 jan 08 22:14:06 chromium kernel: ? __pfx___driver_attach+0x10/0x10 jan 08 22:14:06 chromium kernel:
[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
I have a similar issue with Meizu MX4 which pairs, connects but drops the connection to the car kit after being connected 2 sec. This bug hasn't been resolved in 1 1/2 year time and ota5 - ota14 releases. Now we hear that there will not be a ota15 for a long while and maybe even never for the Meizu and BQ, it looks it will never be fixed. I really don't think ubuntu phone has a future it we can't get a simple thing to work like hands free calling in the car, or playing music over the car speakers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1496102] Re: Bluetooth connection breaks in a few seconds
This is still an issue with OTA14. I am a bit disappointed to hear there will not be a OTA15 soon and possibly even never for this device. Canonical, do you really think you can be successful in phone/touch if you give up something basic as bluetooth? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+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 1496102] Re: Bluetooth connection breaks in a few seconds
With OTA13 I managed to play music 1 or 2 times. Mostly it continues to disconnect immediately after connecting. The only difference I can think of is when I get in the car, start the engine and try to connect it fails, while if I wait a while it might work (but normally I don't have time to play after start driving). I may have something to do with the car trying to connect the handsfree phone function while the phone tries to connect the 'headphone' function for playback. I noticed on my desktop also a bt connection to a phone breaks when connecting to a second phone. May be related? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+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 1373571] Re: Add the ability to include the device product name in the user agent string
In OTA 13 the current settings cause www.blendle.com to show a 'invalid browser' page. This is a regression compared to a previous version (can't remember when this worked). This web site works with android's browser and even with sailfish. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1373571 Title: Add the ability to include the device product name in the user agent string Status in webbrowser-app package in Ubuntu: Triaged Bug description: In order to be well supported in the wurfl database we would like to include a product name in the string. This is used as a key to ascertain capabilities. Our default UA already has a placeholder for a device ID, which by default is empty. What we’re missing is a mechanism to expose the actual device ID to QML. We would need to do additional testing to ensure the addition does not adversely affect results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1373571/+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 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
On my Renault Laguna (2010) with TomTom Carminat I managed to pair, but connect doesn't seem to work. I ssh'ed into the phone (Arale) while connecting and saw that it actually does connect, but is disconnected after 2 seconds. This seems to confuse the TomTom shows it is trying to connect while in reality it was connected until the connection broke. I didn't see any reason why it disconnects in log etc. But maybe I'm looking in the wrong place. I would say it's about time we get this fixed. It seems to be some sort of timing issue. I'd be happy to collect logs, just let me know how. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
My Meizu MX4 is paired with my car (Renault with Carminat TomTom), but the connection breaks within 2 sec. after connecting. The sad thing is that it did work a bit before OTA 9. Will this be fixed by the new silo? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1496102] Re: Bluetooth connection breaks in a few seconds
This problem still happens with OTA11 on Meizu MX7. The car kit is a Carminat (TomTom) in a Renault Laguna. Using bluetoothctl I can see the connection is established (there is no problem with pairing as in other bug reports). However the connection is disconnected after about 2 seconds. In a very early version (can't remember which OTA) bluetooth actually did work but only after a reboot. What can I do to get this fixed in OTA 12? I can ssh into my phone while connecting etc, but I didn't see any error messages. I just disconnects. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+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 1496102] Re: Bluetooth connection breaks in a few seconds
My Meizy MX7 with OTA10 breaks the connection to my car kit in about 2 seconds I ssh'ed into the phone during trying to connect to my car kit to see whats going on: - the car kit is paired -the car kit is trusted - the connection is established then disconnected after to seconds -not error messages (in bluetoothctl) I have this phone now about 1 /1/2 year and it would be really nice if I could connect to my own car, as everybody else with a Android can. What can I do to debug this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1496102 Title: Bluetooth connection breaks in a few seconds Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Tried to connect with my MX4 to an Android, then to a Lumia phone. Devices discover each other, they get "Connected", but in about 5-15 seconds they get "Disconnected" again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496102/+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 1509434] Re: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin
Looks like dependency problems in the python libraries. But since first reporting, in the meanwhile I used Kubuntu Backports to upgrade to plasma 5.5.3, qt 5.5.1 and I am running kernel amd64 4.4.0-040400-generic from ubuntu kernel ppa. I also tried newer xorg from xorg-edgers and oibaf. All of this changes nothing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1509434 Title: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin Status in xorg package in Ubuntu: Incomplete Status in plasma-desktop package in Fedora: Unknown Bug description: After my upgrade from 15.04 to 15.10 certain Plasma elements don't redraw. This affects the task bar (in the panel), the starter and the desktop at least. So after starting an application it's not shown in the task bar. After adding a favourite it's not shown in the starter and after dropping a file on the desktop it's not shown. For the task bar I found a work around, by selecting the auto hide function. So each time I move to the bottom edge the task bar pops up, gets redrawn and shows the correct open applications. For the starter: after adding a favourite, click the starter icon (closes), then click again (opens with the change shown). For the desktop I could only logoff, then login. Prior to upgrading I had 15.04 with the Kubuntu Backports installed, and had not this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509434/+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 1509434] Re: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin
I'm trying but: apport-collect -p xorg 1509434 The authorization page: (https://launchpad.net/+authorize-token?oauth_token= allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 530, in sys.exit(UserInterface.run_argv()) File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv return self.run_update_report() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 569, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/share/apport/apport-kde", line 367, in ui_present_report_details desktop_info) File "/usr/share/apport/apport-kde", line 184, in __init__ self.ui.ui_update_view(self) File "/usr/share/apport/apport-kde", line 358, in ui_update_view QTreeWidgetItem(keyitem, [str(line)]) UnicodeEncodeError: 'ascii' codec can't encode character u'\u2018' in position 27: ordinal not in range(128) Segmentation fault (core dumped) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1509434 Title: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin Status in xorg package in Ubuntu: Incomplete Status in plasma-desktop package in Fedora: Unknown Bug description: After my upgrade from 15.04 to 15.10 certain Plasma elements don't redraw. This affects the task bar (in the panel), the starter and the desktop at least. So after starting an application it's not shown in the task bar. After adding a favourite it's not shown in the starter and after dropping a file on the desktop it's not shown. For the task bar I found a work around, by selecting the auto hide function. So each time I move to the bottom edge the task bar pops up, gets redrawn and shows the correct open applications. For the starter: after adding a favourite, click the starter icon (closes), then click again (opens with the change shown). For the desktop I could only logoff, then login. Prior to upgrading I had 15.04 with the Kubuntu Backports installed, and had not this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509434/+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 1510839] [NEW] do-release-upgrade to Wily hangs
Public bug reported: I have experienced a hang during the upgrade to Wily on 2 separate machines, probably at the same point. The upgrade is started from Muon, so the release upgrade uses: do-release-upgrade -m desktop -f DistUpgradeViewKDE -d The hangs appears to occur on dpkg trying to configure a bunch of packages. The hanging dpkg uses 0% CPU, and appears to be waiting for something. Killing the upgrade and running: sudo dpkg --configure -a continues configuring the packages, until it requests user input when configuring dll.conf (part of saned). After this I need to clean up unneeded packages manually, but furtunaly are able to reboot. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: 15.10 kubuntu ** Package changed: apport (Ubuntu) => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1510839 Title: do-release-upgrade to Wily hangs Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I have experienced a hang during the upgrade to Wily on 2 separate machines, probably at the same point. The upgrade is started from Muon, so the release upgrade uses: do-release-upgrade -m desktop -f DistUpgradeViewKDE -d The hangs appears to occur on dpkg trying to configure a bunch of packages. The hanging dpkg uses 0% CPU, and appears to be waiting for something. Killing the upgrade and running: sudo dpkg --configure -a continues configuring the packages, until it requests user input when configuring dll.conf (part of saned). After this I need to clean up unneeded packages manually, but furtunaly are able to reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1510839/+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 1478257] Re: [MX4] phone does not ring and call can not be picked up
Eh, sorry that would be OTA6 (AKA Arale 15.04 r4) -- 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/1478257 Title: [MX4] phone does not ring and call can not be picked up Status in dialer-app package in Ubuntu: Confirmed Bug description: Hello, I noticed that sometimes I can not answer a call on the Meizu MX4 (OTA-5 installed). Symptoms when someone tries to call: - no ringtone (even though the phone is not set to silent) - the display wakes, now on the first attempt the red and green buttons appear. I accept the call, but I can hear nothing and the person who is calling still gets the "ringtone" on his side - so the call actually was never picked up. - if immediately called again the screen wakes, but this time the red/green buttons to answer the call do not appear anymore at all - the call is registered as missed call in the notifications I observed this behavior already two times so far. So it keeps reappearing, although it is not exactly reproducible in the sense that it would happen always. I have accepted calls with the phone, which was not powered off between the time when it did work and now that it doesn't work. Please let me know, if you need further details and I will try to provide them. release: ubuntu 15.04 (r3) Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1478257/+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 1478257] Re: [MX4] phone does not ring and call can not be picked up
I have this since OTA5, the phone rings, accept/reject button appear, but when I touch accept nothing happens, and I miss the call. -- 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/1478257 Title: [MX4] phone does not ring and call can not be picked up Status in dialer-app package in Ubuntu: Confirmed Bug description: Hello, I noticed that sometimes I can not answer a call on the Meizu MX4 (OTA-5 installed). Symptoms when someone tries to call: - no ringtone (even though the phone is not set to silent) - the display wakes, now on the first attempt the red and green buttons appear. I accept the call, but I can hear nothing and the person who is calling still gets the "ringtone" on his side - so the call actually was never picked up. - if immediately called again the screen wakes, but this time the red/green buttons to answer the call do not appear anymore at all - the call is registered as missed call in the notifications I observed this behavior already two times so far. So it keeps reappearing, although it is not exactly reproducible in the sense that it would happen always. I have accepted calls with the phone, which was not powered off between the time when it did work and now that it doesn't work. Please let me know, if you need further details and I will try to provide them. release: ubuntu 15.04 (r3) Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1478257/+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 1490258] Re: It's difficult to answer a call on arale
On my phone I can't accept the call at all! It seems the indicator has a too small touch sensitive area that I can't find in time. This problem is present in other buttons as well, like the send button in Telegram the restart button (after pressing the power button) This is on MX4 with OTA6 -- 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/1490258 Title: It's difficult to answer a call on arale Status in Ubuntu UX: New Status in dialer-app package in Ubuntu: Confirmed Bug description: The indicator to answer a call is at the top of the phone. On large screen, as the MX4, it's difficult to answer to a call using only one hand. Probably there could be improvements, like moving the indicator to the bottom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1490258/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
My Meizu with OTA 6 seems to pair with my car (Renault, with built-in TomTom, phone sees the car as My_Radiosat, car see the phone as "MX4 Ubuntu Edit" truncated from Edition), however it does not connect most of the time. I managed to get it to connect a few times (audio), but sound does not come from the car speakers but from the phone. Also phone functions from the car don't work. Selecting the phone to dial out cause a bluetooth reconnect that fail after a while. (these functions worked with android phones of course). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1477342] Re: Data network not reconnecting
On my Meizu (15.04 r4) I note that when I arrive home my wifi does not reconnect to my access point. It seems that the phone rescans only the 2.4GHz network (as I see those in the list), however the 5GHz shows still the access points I had at the office. As a result the phone thinks it is still connected to the office access point. This seems like bug 2 above, except the problem is only with 5GHz. Turning off/on wifi obviously solves the problem, as this forces a network scan. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1477342 Title: Data network not reconnecting Status in indicator-network package in Ubuntu: Confirmed Bug description: BQ Aquarius 4.5 15.04(r24) Network is not always recognised. After time or when I move from a wifi to mobile 3g connection the phone will do either: 1) not connect to mobile network, even though from the network dropdown bar, it shows a data network is available next to sim1 slot, but topbar shows wifi not connected icon and no network is accessible on anything. 2) when wifi is available, it keeps me on mobile data connection and doesn't refresh available wifi networks. Number 1 can sometimes be corrected by entering flight mode and back again - sometimes. Number 2 can be corrected by switching on and off the wifi mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1477342/+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 1429098] Re: systemd[1]: ureadahead.service failed.
Did you try a one time boot with the default kernel? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1429098 Title: systemd[1]: ureadahead.service failed. Status in NULL Project: Invalid Status in ureadahead package in Ubuntu: Confirmed Bug description: dmesg: [4.717252] systemd[1]: ureadahead.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 6 08:55:40 2015 InstallationDate: Installed on 2014-09-25 (162 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc2-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 init=/lib/systemd/systemd SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1429098/+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 1429098] Re: systemd[1]: ureadahead.service failed.
Yes, I had the same. I traced it back to the following: Before and after the upgrade to 15.04 I was running kernel 4.0 (same as reporter). Apparently with this kernel something doesn't want to trace (whatever that means in this context). As a result no 'pack' file is generated in /var/lib/ureadahead. The missing pack file causes ureadahead again to try to trace on the next boot, which again fails. Solution: boot one time as 15.04 default kernel (3.19.0) with systemd, not upstart. This will let ureadahead create the 'pack'. Lot's of uninteresting stuff fills syslog (about ignoring relative path blabla). On the next boot with kernel 4.0 ureadahead failure disappeared. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1429098 Title: systemd[1]: ureadahead.service failed. Status in NULL Project: Invalid Status in ureadahead package in Ubuntu: Confirmed Bug description: dmesg: [4.717252] systemd[1]: ureadahead.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu3 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 6 08:55:40 2015 InstallationDate: Installed on 2014-09-25 (162 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc2-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 init=/lib/systemd/systemd SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1429098/+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 1390962] [NEW] rsyslog won't start with upstart on chromebook
Public bug reported: On utopic (14.10) I have the following probllem: Each time I reboot rsyslogd is not running. #lsb_release -rd Description:Ubuntu 14.10 Release:14.10 #uname -a Linux chromium 3.17.2-031702-generic #201410301416 SMP Thu Oct 30 18:18:02 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux #apt-cache policy rsyslog rsyslog: Geïnstalleerd: 7.4.4-1ubuntu11 Kandidaat: 7.4.4-1ubuntu11 Versietabel: *** 7.4.4-1ubuntu11 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status When I do: #sudo service syslog start the system responds that the service is already running. However using: #ps -ef | grep syslog shows that there is no such procesa. When doing: #sudo service syslog restart the (non-existing service) is stopped and started and runs normally. Finally (after many frustrating hours) I found the following line in /var/log/upstart/rsyslog: ERROR: Could not determine network interfaces, you must use a interfaces config line I suddenly realized old problems in the past getting smbd started before the network becomes available. Appearantly that is the case here as well. So I went ahead and changed /etc/init/rsyslog.conf (copied the line from /etc/init/smbd.conf): #sudo servicestart on filesystem start on (local-filesystems and net-device-up) Now rsyslogd starts properly. Note that a chromebook has no ethernet port, only wifi. I have no idea if this is the optimal start on event. ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1390962 Title: rsyslog won't start with upstart on chromebook Status in “rsyslog” package in Ubuntu: New Bug description: On utopic (14.10) I have the following probllem: Each time I reboot rsyslogd is not running. #lsb_release -rd Description:Ubuntu 14.10 Release:14.10 #uname -a Linux chromium 3.17.2-031702-generic #201410301416 SMP Thu Oct 30 18:18:02 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux #apt-cache policy rsyslog rsyslog: Geïnstalleerd: 7.4.4-1ubuntu11 Kandidaat: 7.4.4-1ubuntu11 Versietabel: *** 7.4.4-1ubuntu11 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status When I do: #sudo service syslog start the system responds that the service is already running. However using: #ps -ef | grep syslog shows that there is no such procesa. When doing: #sudo service syslog restart the (non-existing service) is stopped and started and runs normally. Finally (after many frustrating hours) I found the following line in /var/log/upstart/rsyslog: ERROR: Could not determine network interfaces, you must use a interfaces config line I suddenly realized old problems in the past getting smbd started before the network becomes available. Appearantly that is the case here as well. So I went ahead and changed /etc/init/rsyslog.conf (copied the line from /etc/init/smbd.conf): #sudo servicestart on filesystem start on (local-filesystems and net-device-up) Now rsyslogd starts properly. Note that a chromebook has no ethernet port, only wifi. I have no idea if this is the optimal start on event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1390962/+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
