[Touch-packages] [Bug 1479440] Re: IN CAR: Missed calls are not shared with the car via bluetooth
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1479440 Title: IN CAR: Missed calls are not shared with the car via bluetooth Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT, a secondary device and a car with bluetooth phone capabilities (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Using the menu system in the car navigate to missed calls 3. Message There are no missed calls 4. Call the DUT from the secondary device 5. Hang up the secondary device once the call is received 6. Check the missed calls log again (shows on the phone but not on the car) EXPECTED: I expect to see a list of missed calls ACTUAL: No missed call are available VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479440/+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 1421598] Re: DisplayPasskey() "entered" number wrong on some devices
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1421598 Title: DisplayPasskey() "entered" number wrong on some devices Status in bluez package in Ubuntu: New Bug description: Using vivid on the n7, the number of "entered" digit is random/wrong, it should start at 0 and increase to 6 as you type, but on that device it returns random value (i.e 75, 92, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1421598/+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 1419877] Re: [bluetooth] krillin advertized as type "computer"
** Tags removed: ubuntu-touch ** Tags added: bluez-touch ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- 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/1419877 Title: [bluetooth] krillin advertized as type "computer" Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Using rtm 228, the device is advertized as being a "computer", it should probably be a "phone" rather? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+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 1492368] Re: Calls made through car bluetooth drop out
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1492368 Title: Calls made through car bluetooth drop out Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Calls made through car bluetooth connection always drop out after about 3 minutes. The phone becomes unusable and I have to hold the power button for 15 seconds to reboot it. Car is Skoda Octavia. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1492368/+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 1445376] Re: A2DP skips when conneted to handsfree device
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Confirmed Bug description: When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk Ego Flash) via Bluetooth I experience a skipping problem when playing sound files through A2DP. Half a second for each second there is a pause. The rest of that half second seems to clear a buffer which results in "extra fast" audio. To illustrate, listening to a podcast I would expect to hear something like "bla bla bla". However, what I do get to hear sounds more like "flapflapflap - pause - flapflapflap - pause - ...". When I connect my Aquaris to my A2DP speakers at home, the audio is perfect. Also, handsfree telephony in my car works like a charm. So I guess it's just the combination of A2DP while connected to the handsfree device which causes the trouble. In the past I've used several phones with the Funkwerk device (always with handsfree *and* A2DP functionality) including an N900 running Maemo. There have never been any problems with those. OS build number 21 KRILIN01A-S15A_BQ_L100EN_2021_150410 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445376/+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 1528856] Re: bluetooth & car handsfree issue
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1528856 Title: bluetooth & car handsfree issue Status in bluez package in Ubuntu: Confirmed Bug description: When playing music through headphone output connected to aux car radio input and going to call someone while driving, i only hear some "beeps" and apparently the call was succesfull but i can't hear anything and no sound is transmitted . In the phone screen appears the speaker icon with an x (like there is no speaker connected) but phone and car are paired correctly. In addition to, when to SIM cards are inserted y only receive call through bluetooth for the one i have selected as default, for the other SIM, ring tones sounds in phone speaker and no through bluetooth device. Device: BQ Aquaris E4.5 Ubuntu Edition Channel: RC-proposed Version: r604 Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1528856/+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 1432788] Re: Race in vivid means sometimes bluetooth is no available
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1432788 Title: Race in vivid means sometimes bluetooth is no available Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: New Bug description: STEPS: 1. Flash a fresh image of vivid on a krillin device 2. Check if bluetooth is on 3. Reboot EXPECTED: I always expect bluetooth to be on ACTUAL: Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how ever it wouldn't connect to anything. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1432788/+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 1423266] Re: Fails to set the HSP/HFP profile with Ford New Fiesta Sedan 2014 (Brazil)
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1423266 Title: Fails to set the HSP/HFP profile with Ford New Fiesta Sedan 2014 (Brazil) Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Car: Ford New Fiesta Sedan 2014 (the one sold in Brazil) Image: RTM 239 Device: krillin I paired the device, and tried to start a call but noticed there was no audio, so with help from Salveti we figured out switching to the hsp profile is faling, so the attached syslog is after running the following command: pactl set-card-profile bluez_card.00_21_CC_E9_02_39 hsp To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1423266/+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 1479449] Re: IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1479449 Title: IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT, a second device, a car with bluetooth phone support (Skoda Supberb 2013 in my case) 1. Connect the DUT to the car 2. From the second device call the car 3. The ringer starts EXPECTED: I expect all audio to come through the car speakers ACTUAL: The ringer is routed through the loud speaker of the phone not the car audio VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479449/+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 1491284] Re: Two spinners showing and the status will become "Not discoverable" after BT enabled for a while
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1491284 Title: Two spinners showing and the status will become "Not discoverable" after BT enabled for a while Status in bluez package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 06:52:45 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid Steps to reproduce: 1.Enable Bluetooth from System Settings -->Bluetooth-->Enabled 2.The status will show as "Discoverable -->Aquaris E4.5 Ubuntu Edition" and the spinner appears in 10 seconds 3.Waiting for a while then check the status again Expected results: The status should be kept as "Discoverable" with device name shown, and only one spinner shows in every 10 seconds Actual results: The status will become "Not discoverable" and two spinners showing after for a while, attached the screenshot and the dmesg output bellow: [ 1050.241914] BT ON <>sec=1441177892, usec=884713 [ 1050.241939] [WMT-STP-EXP][I]mtk_wcn_wmt_func_on: mtk_wcn_wmt_func_on_f type(0) [ 1050.241959] [HCI-STP][I]hci_stp_open:WMT turn on BT OK! [ 1050.241978] Flush type = 0 Rx Queue [ 1050.242119] [HCI-STP][I]hci_stp_dev_init_work:Load custom BT config success [ 1050.275283] [HCI-STP][I]hci_stp_open:hci_stp_dev_init ok [ 1050.275315] Flush type = 0 Rx Queue [ 1078.037588] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1591.020633] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1761.020828] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1813.890670] [mtk_net][sched]dev_deactivate dev = wlan0 [ 1813.904681] cfg80211: Calling CRDA for country: US [ 1825.479625] [mtk_net][sched]dev_activate dev = wlan0 [ 1825.500057] --> mtk_cfg80211_set_default_key() [ 1921.031722] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2161.026379] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2511.029227] [STP-BTIF][I]mtk_wcn_consys_stp_btif_tx:special case for STP-CORE,pbuf(c1001e98) [ 2511.036971] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 3424.024060] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491284/+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 1479453] Re: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1479453 Title: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT, a second device and a car that supports bluetooth phones (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Receive multiple calls EXPECTED: I expect the call audio to always be routed through the car audio and be audible ACTUAL: After a number of calls all of a sudden you can accept the call but you get no audio from the call at all, the mic is still working as expected. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479453/+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 1411437] Re: [mako] crash right after the boot (segfault in plugins/hciops.c:2910)
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1411437 Title: [mako] crash right after the boot (segfault in plugins/hciops.c:2910) Status in bluez package in Ubuntu: New Bug description: current build number: 66 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2015-01-15 21:43:12 version version: 66 version ubuntu: 20150115 version device: 20141213 version custom: 20150115 Right after a clean flash. Backtrace: #0 device_event (event=, index=0) at plugins/hciops.c:2910 No locals. #1 0xb6f76b5c in io_stack_event (chan=, cond=, data=) at plugins/hciops.c:3027 buf = "\004\375\006\001\000\003\000\000\000\000\000\000\237\366߶\200\067\370\276T8\370\276\020\237\363\266_\366߶+\000\000\000\a\000\000\000T8\370\276E\333߶\240\067\370\276$/;\270\000\000\000\000p7\370\276\310\067\370\276\000#a\b\300\067\370\276\001\000\000\000\t\000\000\000\003\237\363\266\001\000\000\000$/;\270/\000\000\000\207\327\340\266\000\000\000\000\001\000\000\000\060\000\000\000$/;\270/\000\000\000\343\327\340\266\020\237\363\266\000#a>\374\001\000\000\b\000\000\000\240\070\370\276g\000\000\000T8\370\276W\332\340\266\060\000\000\000\000#a>\002\000\000\000\a0;\270\002\000\000\000\235\327\340\266$/;\270\002\000\000\000$/;\270\000\000\000\000$8\370"... ptr = 0xbef8372b "\001" si = 0xbef8372b eh = 0xbef83729 type = fd = #2 0xb6e630f8 in g_main_dispatch (context=0xb83ac100) at /build/buildd/glib2.0-2.43.2/./glib/gmain.c:3122 dispatch = 0xb6e9350d prev_source = 0x0 was_in_call = 0 user_data = 0x0 callback = 0xb6f76b01 cb_funcs = 0xb6f01594 cb_data = 0xb83b5748 need_destroy = source = 0xb83b56e8 current = 0xb83b51e0 i = 2 #3 g_main_context_dispatch (context=context@entry=0xb83ac100) at /build/buildd/glib2.0-2.43.2/./glib/gmain.c:3737 No locals. #4 0xb6e6337c in g_main_context_iterate (context=0xb83ac100, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.43.2/./glib/gmain.c:3808 max_priority = 0 timeout = 0 some_ready = 1 nfds = allocated_nfds = fds = 0xb83b5880 #5 0xb6e63618 in g_main_loop_run (loop=0xb83ab018) at /build/buildd/glib2.0-2.43.2/./glib/gmain.c:4002 __FUNCTION__ = "g_main_loop_run" #6 0xb6f473ba in main (argc=1, argv=0xbef83e14) at src/main.c:542 context = err = 0x0 __FUNCTION__ = "main" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1411437/+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 1414142] Re: Continuous skipping of audio track after reconnecting bluetooth to Car
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1414142 Title: Continuous skipping of audio track after reconnecting bluetooth to Car Status in bluez package in Ubuntu: New Bug description: In my car I am seeing a very weird issue with bluetooth playback. After connecting with car bluetooth the second time, the audio playback from my phone in the car speakers starts to skip. I am sure not everyone will be able to reproduce this bug with the below steps but still I should mentions them. 1. Connect mobile bluetooth to the car and play a track Verify: it plays the track fine. 2. Disconnect the bluetooth from the phone and make sure it actually gets disconnected from the car. 3. Re-enable bluetooth and connect to the car. Now when I play the sound track it keeps skipping and I can't really hear much of the song. I have attached hcidump, syslog and 'hcitool lq'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1414142/+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 1362694] Re: Can't pair with car kit (reverse mode)
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1362694 Title: Can't pair with car kit (reverse mode) Status in bluez package in Ubuntu: Incomplete Bug description: My car kit is the party initiating the connection when pairing with the phone. But the request fails, no PIN dialog is displayed and the kit says that pairing failed. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: bluez 4.101-0ubuntu19 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Aug 28 16:25:44 2014 InstallationDate: Installed on 2014-08-28 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140828-030204) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:3229 acl:65 sco:0 events:147 errors:0 TX bytes:3516 acl:66 sco:0 commands:46 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362694/+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
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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 1409047] Re: Bluetooth audio not working with Volvo multimedia
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1409047 Title: Bluetooth audio not working with Volvo multimedia Status in bluez package in Ubuntu: Confirmed Bug description: Calls work just fine, which is in the "Telephone" part of the car's UI. When changing to Multimedia mode and pairing with a Nexus 4, no audio is played, nor is any audio playable later through the phone's own speakers. This is a 2012 Volvo S60 (Norwegian) Steps to reproduce: 1. Pair with car multimedia system 2. Confirm that the car display shows "Playing on Nexus 4" (or something to that effect) 3. Play song What I expected to happen: Audio should have been played through the car's speakers What happened instead: No audio was played Playing any audio, even after turning off bluetooth, does not work Phone: mako using Vivid @ r58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1409047/+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 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+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 1421448] Re: problem pairing Jabra BT2050
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1421448 Title: problem pairing Jabra BT2050 Status in bluez package in Ubuntu: New Bug description: This is tested on: nexus4 (vivid-proposed) #96 bq (stable) #17 Steps taken: 1. turn on Bluetooth on device. 2. put Jabra BT2050 on pairing mode. 3. click on "Jabra BT2050..." in Bluetooth setting on device 4. prompted with new page, click on "Connect" button. 5. New popover with this message "Bluetooth Pairing Request PIN for 'Jabra BT2050' [textfield: ], click on "Pair" button. [ at this point new handset is added to the list and "connected" sound is played in handset but whole settings UI on device is frozen for about 15sec. bluetooth icon in topbar is white-connected. ] 6. In bluetooth setting Click on ">" next to Jabra BT2050 to see more info. 7. Status on that page is saying: "Connecting..." while button at the bottom says: "Disconnect" see attached picture. 8. open Phone app and try to call anyone, sound is coming out from phone speakers. After "forgetting this device" and pairing it again for few times I managed to connect it and it worked but only to make one phone call after I hangup I wasn't able to use bluetooth again. If I good remember this time then it worked I was't prompted for pairing password. Any more info you need please let me know. I must add that this handset works well on nexus4 and other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1421448/+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 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
*** This bug is a duplicate of bug 1246981 *** https://bugs.launchpad.net/bugs/1246981 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1246981, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1246981 Bluetooth mouse fails to re-connect after sleep. -- 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/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481136/+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 1479442] Re: IN CAR: Previous Calls log is not shown in the car display
** Tags removed: ubuntu-touch ** Tags added: bluez-touch -- 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/1479442 Title: IN CAR: Previous Calls log is not shown in the car display Status in Canonical System Image: Triaged Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT a list of previous calls and a car that support bluetooth phones (Skoda Superb 2013 in my case) 1. Connect DUT to the car 2. In the car menu navigate to previous calls log EXPECTED: I expect to see a list of past calls similar to those I see on the phone itself ACTUAL: Car shows no previous calls log at all VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479442/+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 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
# more /etc/fstab /dev/md1/ ext3defaults,noatime 1 1 /dev/sda2 noneswapsw /dev/sdb2 noneswapsw /dev/vg00/usr /usrext4noatime,errors=remount-ro 0 2 /dev/vg00/var /varext4noatime,errors=remount-ro 0 2 /dev/vg00/home /home ext4noatime,errors=remount-ro 0 2 #/dev/hdd/data /data ext4noatime,errors=remount-ro 0 2 proc/proc procnodev,noexec,nosuid 0 0 # mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8154408k,nr_inodes=2038602,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1641468k,mode=755) /dev/md1 on / type ext3 (rw,noatime,data=ordered) /dev/mapper/vg00-usr on /usr type ext4 (rw,noatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) /dev/mapper/vg00-home on /home type ext4 (rw,noatime,errors=remount-ro,data=ordered) /dev/mapper/vg00-var on /var type ext4 (rw,noatime,errors=remount-ro,data=ordered) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=1641468k,mode=700) # cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default (built-in), scan all partitions (/proc/partitions) and all # containers for MD superblocks. alternatively, specify devices to scan, using # wildcards if desired. #DEVICE partitions containers # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md1 UUID=6d35e4d9:3952fbd3:1f51fb89:78ee93fe level=raid1 num-devices=2 devices=/dev/sda1,/dev/sdb1 ARRAY /dev/md3 UUID=682d55c0:d40b40c9:1f51fb89:78ee93fe level=raid1 num-devices=2 devices=/dev/sda3,/dev/sdb3 #ARRAY /dev/md11 level=raid1 num-devices=2 devices=/dev/sdc1,/dev/sdd1 # /usr/share/mdadm/mkconf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default (built-in), scan all partitions (/proc/partitions) and all # containers for MD superblocks. alternatively, specify devices to scan, using # wildcards if desired. #DEVICE partitions containers # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md1 UUID=6d35e4d9:3952fbd3:1f51fb89:78ee93fe ARRAY /dev/md3 UUID=682d55c0:d40b40c9:1f51fb89:78ee93fe # mdadm --misc --detail /dev/md1 /dev/md1: Version : 0.90 Creation Time : Wed May 3 16:13:21 2017 Raid Level : raid1 Array Size : 4194240 (4.00 GiB 4.29 GB) Used Dev Size : 4194240 (4.00 GiB 4.29 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1
[Touch-packages] [Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Systematically, - With a /etc/fstab using UUID or LABEL, update-initramfs works correctly - With a /etc/fstab using PARTLABEL, update-initramfs displays following error messages : cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=Ubuntu-Gnome cryptsetup: WARNING: could not determine root device from /etc/fstab cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu The cryptsetup part of update-initramfs must correctly take into account PARTLABEL inside /etc/fstab Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue May 10 21:14:24 2016 InstallationDate: Installed on 2014-11-03 (553 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+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 1493495] Re: bluetoothd crashed with SIGSEGV in telephony_terminate_call_req from terminate_call from handle_event from rfcomm_io_cb:g_main_dispatch
Low severity. Seems this crash stopped happening after bluez got upgraded to v5 in Ubuntu 15.10. So the only supported release still affected (at most) is 14.04. ** Summary changed: - /usr/sbin/bluetoothd:11:telephony_terminate_call_req:terminate_call:handle_event:rfcomm_io_cb:g_main_dispatch + bluetoothd crashed with SIGSEGV in telephony_terminate_call_req from terminate_call from handle_event from rfcomm_io_cb:g_main_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1493495 Title: bluetoothd crashed with SIGSEGV in telephony_terminate_call_req from terminate_call from handle_event from rfcomm_io_cb:g_main_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/5c150a680b51f277c28dee82a9f97a2e16fe671a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493495/+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 530779] Re: init: does not wait for parent to exit when following forks
upstart is not used in Ubuntu beyond 15.10. ** Changed in: upstart (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/530779 Title: init: does not wait for parent to exit when following forks Status in upstart : In Progress Status in upstart package in Ubuntu: Won't Fix Status in upstart source package in Precise: Triaged Bug description: When following a fork, once Upstart receives the new pid, it immediately starts following that and forgets about the parent entirely not even waiting for it to exit. There are two problems with this: The first is the kind of daemon that forks early, but then maintains communication with the parent so that the parent can exit with an appropriate exit code in case of error (rather than the kind which only fork once they are ready). These kinds aren't ready until the parent exits, not at the point of the fork. Since upstart follows the fork, it will think they are ready "too early" The second is simply any that writes a pid file (which is perhaps a simplification of the above), if they write the pid file in the parent (as even nih_main_daemonise does!) then there's no guarantee the pid file actually exists when the "start" command returns. (Other than the fact we use ptrace tends to mean that the race works out in our favour) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/530779/+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 1250621] Re: The dependencies from sdk-libs pull in numerous unused packages
ubuntu-touch-meta has now been removed from the Ubuntu devel series, so closing this bug. ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1250621 Title: The dependencies from sdk-libs pull in numerous unused packages Status in ubuntu-touch-meta package in Ubuntu: Won't Fix Bug description: Due to the nature of the package dependencies, a number of packages are added to the image which are not used or needed. These include X11 and mesa drivers for other architectures. This has several undesired effects: 1) the image size is larger than necessary 2) it implies a level of support based on the system framework 3) it will cause confusion during technical reviews of the image contents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1250621/+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 1493498] Re: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb:g_main_dispatch
Low severity because this crash seems to have stopped happening in bluez v5 (Ubuntu 15.10 and later). So the only supported release that might still be affected is 14.04. ** Summary changed: - /usr/sbin/bluetoothd:11:avdtp_sep_set_state:avdtp_abort_resp:avdtp_parse_resp:session_cb:g_main_dispatch + bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb:g_main_dispatch ** Changed in: bluez (Ubuntu) Importance: High => Low ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1493498 Title: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb:g_main_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25, the problem page at https://errors.ubuntu.com/problem/89c2536156cfe1ec74b64298c4d38b4e320baac4 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493498/+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 1493528] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch
Low severity because the crash stopped occurring in bluez v5 (Ubuntu 15.10 and later). So the only supported release still affected (if at all) is 14.04. ** Summary changed: - /usr/sbin/bluetoothd:11:state_changed:avctp_set_state:session_cb:g_main_dispatch:g_main_context_dispatch + bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1493528 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/b2077378adbdb76716399672a8b463aeffbfea17 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493528/+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 1442361] Re: Pairing with bluetooth devices not working on 15.04
** Project changed: bluez => mir ** No longer affects: mir -- 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/1442361 Title: Pairing with bluetooth devices not working on 15.04 Status in bluez package in Ubuntu: Incomplete Bug description: Devices paired on 14.10 are working normally but I'm not able to pair with any new device 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 15.04 3) What you expected to happen Window with pairing key and confirmation button should appear 4) What happened instead It doesn't appear e.g: when trying to pair from Windows PC there is window with PIN and "Confirm" button, but it doesn't appear on Ubuntu. When I click "Confirm" on WIndows PC it shows pairing error. (Similar things happen when trying to pair with Android phone and etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1442361/+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 1492441] Re: Cannot connect to 1byone bluetooth keyboard (after successfully pairing)
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1492441 Title: Cannot connect to 1byone bluetooth keyboard (after successfully pairing) Status in bluez package in Ubuntu: Incomplete Bug description: I own a 1byone bluetooth keyboard/touchpad combo device. I'm using wily. I have managed to successfully pair it (the UI did not work for this -- bug 1492443). But doing it via the console did pair it: $ bluetoothctl [NEW] Device 08:73:00:13:CC:45 1byone Keyboard [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# pair 08:73:00:13:CC:45 Attempting to pair with 08:73:00:13:CC:45 [CHG] Device 08:73:00:13:CC:45 Connected: yes [agent] PIN code: 420005 [CHG] Device 08:73:00:13:CC:45 Modalias: usb:v04E8p7021d011B [CHG] Device 08:73:00:13:CC:45 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 Paired: yes Pairing successful [CHG] Device 08:73:00:13:CC:45 Connected: no [CHG] Device 60:03:08:C9:C0:87 RSSI: -59 [CHG] Device 60:03:08:C9:C0:87 RSSI: -48 [CHG] Device 60:03:08:C9:C0:87 RSSI: -60 [CHG] Device 60:03:08:C9:C0:87 RSSI: -48 etc, etc (kept outputting RSSI bits every now and then) OK. So it paired. (which means it's not bug 1490347) But now I can't connect. You can see above that it says "Connected: no". If I go to the Bluetooth panel in System Settings, its "Connection" switch is set to Off and disabled. But it otherwise seems to be successfully paired. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 4 15:16:58 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (967 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=0719ea95-7c02-4d0a-a969-1ba285c420f2 ro quiet splash vt.handoff=7 SourcePackage: bluez SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to wily on 2013-01-31 (945 days ago) dmi.bios.date: 12/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0CK86J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/03/2012:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0CK86J:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:FB:58:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:19494 acl:0 sco:0 events:721 errors:0 TX bytes:3449 acl:0 sco:0 commands:234 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492441/+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 1491988] Re: 15.10: BT Command List not created: bluetooth:__hci_req_sync:298: hci1 end: err -ETIMEDOUT
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- 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/1491988 Title: 15.10: BT Command List not created: bluetooth:__hci_req_sync:298: hci1 end: err -ETIMEDOUT Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: $ hcitool dev Devices: hci100:10:7A:4D:15:33 hci000:1F:3A:E0:0A:AF $ hcitool -i hci1 scan Scanning ... 00:0A:95:4B:BD:C2 Apple Wireless Keyboard $ sudo systemctl restart bluetooth $ journalctl -u bluetooth | grep adapter_service_add Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: src/adapter.c:adapter_service_add() /org/bluez/hci0 $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard [bluetooth]# list Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1491284] Re: Two spinners showing and the status will become "Not discoverable" after BT enabled for a while
** Tags added: ubuntu-touch -- 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/1491284 Title: Two spinners showing and the status will become "Not discoverable" after BT enabled for a while Status in bluez package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 06:52:45 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid Steps to reproduce: 1.Enable Bluetooth from System Settings -->Bluetooth-->Enabled 2.The status will show as "Discoverable -->Aquaris E4.5 Ubuntu Edition" and the spinner appears in 10 seconds 3.Waiting for a while then check the status again Expected results: The status should be kept as "Discoverable" with device name shown, and only one spinner shows in every 10 seconds Actual results: The status will become "Not discoverable" and two spinners showing after for a while, attached the screenshot and the dmesg output bellow: [ 1050.241914] BT ON <>sec=1441177892, usec=884713 [ 1050.241939] [WMT-STP-EXP][I]mtk_wcn_wmt_func_on: mtk_wcn_wmt_func_on_f type(0) [ 1050.241959] [HCI-STP][I]hci_stp_open:WMT turn on BT OK! [ 1050.241978] Flush type = 0 Rx Queue [ 1050.242119] [HCI-STP][I]hci_stp_dev_init_work:Load custom BT config success [ 1050.275283] [HCI-STP][I]hci_stp_open:hci_stp_dev_init ok [ 1050.275315] Flush type = 0 Rx Queue [ 1078.037588] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1591.020633] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1761.020828] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 1813.890670] [mtk_net][sched]dev_deactivate dev = wlan0 [ 1813.904681] cfg80211: Calling CRDA for country: US [ 1825.479625] [mtk_net][sched]dev_activate dev = wlan0 [ 1825.500057] --> mtk_cfg80211_set_default_key() [ 1921.031722] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2161.026379] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 2511.029227] [STP-BTIF][I]mtk_wcn_consys_stp_btif_tx:special case for STP-CORE,pbuf(c1001e98) [ 2511.036971] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) [ 3424.024060] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx data(200) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491284/+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 1492368] Re: Calls made through car bluetooth drop out
** Tags added: ubuntu-touch -- 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/1492368 Title: Calls made through car bluetooth drop out Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Calls made through car bluetooth connection always drop out after about 3 minutes. The phone becomes unusable and I have to hold the power button for 15 seconds to reboot it. Car is Skoda Octavia. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1492368/+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 1493481] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from avctp_confirm_cb:server_cb from g_main_dispatch
Low severity. This crash seems to have stopped occurring after vivid (when bluez upgraded to v5). So at most only trusty systems are still affected. ** Summary changed: - /usr/sbin/bluetoothd:11:state_changed:avctp_set_state:avctp_confirm_cb:server_cb:g_main_dispatch + bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from avctp_confirm_cb:server_cb from g_main_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1493481 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from avctp_confirm_cb:server_cb from g_main_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/1c7ce0e3d4d00429fd1a154776e90a7b6a1a3ca5 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493481/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd
Removing packages from artful: cgmanager 0.41-2 in artful cgmanager 0.41-2 in artful amd64 cgmanager 0.41-2 in artful arm64 cgmanager 0.41-2 in artful armhf cgmanager 0.41-2 in artful i386 cgmanager 0.41-2 in artful ppc64el cgmanager 0.41-2 in artful s390x cgmanager-tests 0.41-2 in artful amd64 cgmanager-tests 0.41-2 in artful arm64 cgmanager-tests 0.41-2 in artful armhf cgmanager-tests 0.41-2 in artful i386 cgmanager-tests 0.41-2 in artful ppc64el cgmanager-tests 0.41-2 in artful s390x libcgmanager-dev 0.41-2 in artful amd64 libcgmanager-dev 0.41-2 in artful arm64 libcgmanager-dev 0.41-2 in artful armhf libcgmanager-dev 0.41-2 in artful i386 libcgmanager-dev 0.41-2 in artful ppc64el libcgmanager-dev 0.41-2 in artful s390x libcgmanager0 0.41-2 in artful amd64 libcgmanager0 0.41-2 in artful arm64 libcgmanager0 0.41-2 in artful armhf libcgmanager0 0.41-2 in artful i386 libcgmanager0 0.41-2 in artful ppc64el libcgmanager0 0.41-2 in artful s390x libpam-cgm 0.41-2 in artful amd64 libpam-cgm 0.41-2 in artful arm64 libpam-cgm 0.41-2 in artful armhf libpam-cgm 0.41-2 in artful i386 libpam-cgm 0.41-2 in artful ppc64el libpam-cgm 0.41-2 in artful s390x Comment: Unused, replaced by systemd; LP: #1649310 1 package successfully removed. ** Changed in: cgmanager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Released Status in upstart-watchdog package in Ubuntu: Fix Released Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd
Removing packages from artful: upstart 1.13.2-0ubuntu35 in artful libupstart-dev 1.13.2-0ubuntu35 in artful amd64 libupstart-dev 1.13.2-0ubuntu35 in artful arm64 libupstart-dev 1.13.2-0ubuntu35 in artful armhf libupstart-dev 1.13.2-0ubuntu35 in artful i386 libupstart-dev 1.13.2-0ubuntu35 in artful ppc64el libupstart1 1.13.2-0ubuntu35 in artful amd64 libupstart1 1.13.2-0ubuntu35 in artful arm64 libupstart1 1.13.2-0ubuntu35 in artful armhf libupstart1 1.13.2-0ubuntu35 in artful i386 libupstart1 1.13.2-0ubuntu35 in artful ppc64el upstart 1.13.2-0ubuntu35 in artful amd64 upstart 1.13.2-0ubuntu35 in artful arm64 upstart 1.13.2-0ubuntu35 in artful armhf upstart 1.13.2-0ubuntu35 in artful i386 upstart 1.13.2-0ubuntu35 in artful ppc64el upstart-dconf-bridge 1.13.2-0ubuntu35 in artful amd64 upstart-dconf-bridge 1.13.2-0ubuntu35 in artful arm64 upstart-dconf-bridge 1.13.2-0ubuntu35 in artful armhf upstart-dconf-bridge 1.13.2-0ubuntu35 in artful i386 upstart-dconf-bridge 1.13.2-0ubuntu35 in artful ppc64el upstart-monitor 1.13.2-0ubuntu35 in artful amd64 upstart-monitor 1.13.2-0ubuntu35 in artful arm64 upstart-monitor 1.13.2-0ubuntu35 in artful armhf upstart-monitor 1.13.2-0ubuntu35 in artful i386 upstart-monitor 1.13.2-0ubuntu35 in artful ppc64el upstart-monitor 1.13.2-0ubuntu35 in artful s390x Comment: Unused, replaced by systemd; LP: #1649310 1 package successfully removed. ** Changed in: upstart (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Released Status in upstart-watchdog package in Ubuntu: Fix Released Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to:
[Touch-packages] [Bug 1671611] Re: USB wi-fi dongles not working with latest updates
^- LinuxMint 18.1 w/ 4.4.0-75 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671611 Title: USB wi-fi dongles not working with latest updates Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Same laptop - two different network dongles (ASUS USB-N13 + Edimax cheap commonly used with RaspPis). Confirmed issue with xenial-updates and xenial-security versions. Going to try to force a downgrade to original xenial to see if it still happens. ASUS dongle -> $ inxi -Fxxrzc0 | pastebin https://gist.github.com/d926d05c2bd23226a9f4b4a593b9de65 Edimax dongle -> $ inxi -Fxxrzc0 | pastebin https://gist.github.com/f76284151c225ae43af82de8439efe02 They work fine w/ the 18.1 Installer/Live Boot.. They worked fine after the install.. when I did the latest update they broke. uname -a -> Linux thinkpad 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Linux Mint 18.1 Serena Release: 18.1 kern.log paste: Mar 9 12:11:17 thinkpad kernel: [ 244.854264] usb 1-2: USB disconnect, device number 4 Mar 9 12:11:17 thinkpad kernel: [ 244.864634] wlx2c4d5406c9c1: deauthenticating from 58:6d:8f:8e:02:5d by local choice (Reason: 3=DEAUTH_LEAVING) Mar 9 12:11:17 thinkpad kernel: [ 244.864846] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xf00069ce Mar 9 12:11:17 thinkpad kernel: [ 244.864858] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424 Mar 9 12:11:17 thinkpad kernel: [ 244.864866] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424 Mar 9 12:11:17 thinkpad kernel: [ 244.864879] rtl_usb: reg 0x1cc, usbctrl_vendorreq TimeOut! status:0xffed value=0x1950812 Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3310] sup-iface[0xa2d380,wlx2c4d5406c9c1]: connection disconnected (reason -3) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3318] device (wlx2c4d5406c9c1): state change: activated -> unmanaged (reason 'removed') [100 10 36] Mar 9 12:11:17 thinkpad kernel: [ 244.899266] cfg80211: World regulatory domain updated: Mar 9 12:11:17 thinkpad kernel: [ 244.899273] cfg80211: DFS Master region: unset Mar 9 12:11:17 thinkpad kernel: [ 244.899275] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 9 12:11:17 thinkpad kernel: [ 244.899280] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899283] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899286] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899290] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899295] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Mar 9 12:11:17 thinkpad kernel: [ 244.899298] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Mar 9 12:11:17 thinkpad kernel: [ 244.899301] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899304] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3642] dhcp4 (wlx2c4d5406c9c1): canceled DHCP transaction, DHCP client pid 2225 Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3643] dhcp4 (wlx2c4d5406c9c1): state changed bound -> done Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3703] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3705] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3708] dns-mgr: Writing DNS information to /sbin/resolvconf Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3879] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3879] device (wlx2c4d5406c9c1): failed to disable userspace IPv6LL address handling Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3880] radio killswitch /sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/ieee80211/phy0/rfkill0 disappeared Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3882] devices removed (path:
[Touch-packages] [Bug 1671611] Re: USB wi-fi dongles not working with latest updates
I second Bazz's statement. All is working normally again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671611 Title: USB wi-fi dongles not working with latest updates Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Same laptop - two different network dongles (ASUS USB-N13 + Edimax cheap commonly used with RaspPis). Confirmed issue with xenial-updates and xenial-security versions. Going to try to force a downgrade to original xenial to see if it still happens. ASUS dongle -> $ inxi -Fxxrzc0 | pastebin https://gist.github.com/d926d05c2bd23226a9f4b4a593b9de65 Edimax dongle -> $ inxi -Fxxrzc0 | pastebin https://gist.github.com/f76284151c225ae43af82de8439efe02 They work fine w/ the 18.1 Installer/Live Boot.. They worked fine after the install.. when I did the latest update they broke. uname -a -> Linux thinkpad 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Linux Mint 18.1 Serena Release: 18.1 kern.log paste: Mar 9 12:11:17 thinkpad kernel: [ 244.854264] usb 1-2: USB disconnect, device number 4 Mar 9 12:11:17 thinkpad kernel: [ 244.864634] wlx2c4d5406c9c1: deauthenticating from 58:6d:8f:8e:02:5d by local choice (Reason: 3=DEAUTH_LEAVING) Mar 9 12:11:17 thinkpad kernel: [ 244.864846] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xf00069ce Mar 9 12:11:17 thinkpad kernel: [ 244.864858] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424 Mar 9 12:11:17 thinkpad kernel: [ 244.864866] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424 Mar 9 12:11:17 thinkpad kernel: [ 244.864879] rtl_usb: reg 0x1cc, usbctrl_vendorreq TimeOut! status:0xffed value=0x1950812 Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3310] sup-iface[0xa2d380,wlx2c4d5406c9c1]: connection disconnected (reason -3) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3318] device (wlx2c4d5406c9c1): state change: activated -> unmanaged (reason 'removed') [100 10 36] Mar 9 12:11:17 thinkpad kernel: [ 244.899266] cfg80211: World regulatory domain updated: Mar 9 12:11:17 thinkpad kernel: [ 244.899273] cfg80211: DFS Master region: unset Mar 9 12:11:17 thinkpad kernel: [ 244.899275] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 9 12:11:17 thinkpad kernel: [ 244.899280] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899283] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899286] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899290] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899295] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Mar 9 12:11:17 thinkpad kernel: [ 244.899298] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Mar 9 12:11:17 thinkpad kernel: [ 244.899301] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899304] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3642] dhcp4 (wlx2c4d5406c9c1): canceled DHCP transaction, DHCP client pid 2225 Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3643] dhcp4 (wlx2c4d5406c9c1): state changed bound -> done Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3703] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3705] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3708] dns-mgr: Writing DNS information to /sbin/resolvconf Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3879] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3879] device (wlx2c4d5406c9c1): failed to disable userspace IPv6LL address handling Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3880] radio killswitch /sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/ieee80211/phy0/rfkill0 disappeared Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3882] devices removed (path:
[Touch-packages] [Bug 1688174] [NEW] package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I was updating the system, a Parallels VM, while the Parallels Tools installation was ongoing. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefano2162 F pulseaudio Date: Thu May 4 13:02:44 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=63164bfa-0aa7-44c0-a592-a36aed290b4f InstallationDate: Installed on 2016-09-03 (242 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=b5191af7-3736-4cd1-81d3-b8fcd5f53bdf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/04/2017 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 12.2.0 (41591) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 13 dmi.chassis.vendor: Parallels Software International Inc. dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr12.2.0(41591):bd04/04/2017:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct13:cvr: dmi.product.name: Parallels Virtual Platform dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1688174 Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I was updating the system, a Parallels VM, while the Parallels Tools installation was ongoing. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefano2162 F pulseaudio Date: Thu May 4 13:02:44 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=63164bfa-0aa7-44c0-a592-a36aed290b4f InstallationDate: Installed on 2016-09-03 (242 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=b5191af7-3736-4cd1-81d3-b8fcd5f53bdf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/04/2017 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 12.2.0 (41591) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 13 dmi.chassis.vendor: Parallels Software International Inc. dmi.modalias:
[Touch-packages] [Bug 1688174] Re: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1688174 Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I was updating the system, a Parallels VM, while the Parallels Tools installation was ongoing. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefano2162 F pulseaudio Date: Thu May 4 13:02:44 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=63164bfa-0aa7-44c0-a592-a36aed290b4f InstallationDate: Installed on 2016-09-03 (242 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=b5191af7-3736-4cd1-81d3-b8fcd5f53bdf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/04/2017 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 12.2.0 (41591) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 13 dmi.chassis.vendor: Parallels Software International Inc. dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr12.2.0(41591):bd04/04/2017:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct13:cvr: dmi.product.name: Parallels Virtual Platform dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1688174/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
I had a similar problem. After upgrading to Xubuntu 17.04, the mouse was too fast but settings had no effects. I solved this problem with xinput. See comments in this bug report (may be a duplicate): https://bugs.launchpad.net/ubuntu/+source/unity-control- center/+bug/1683145 -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1458228] Re: improve error "Device is not available: No such device" of hcitool scan
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1458228 Title: improve error "Device is not available: No such device" of hcitool scan Status in bluez package in Ubuntu: Incomplete Bug description: The feedback `Device is not available: No such device` of `hcitool scan` is unhelpful and should be replaced with a feedback explaining the state (at least which device isn't there) and instructions how fix it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 Uname: Linux 4.0.1-040001-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 23 21:31:08 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (50 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20221 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.1-040001-generic root=UUID=0d646fdd-bb34-4e1c-9271-86a59deb3bf9 ro rootflags=subvol=@ SourcePackage: bluez SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 68:17:29:77:05:46 ACL MTU: 310:10 SCO MTU: 64:8 DOWN RX bytes:34853 acl:308 sco:0 events:1087 errors:0 TX bytes:10432 acl:322 sco:0 commands:265 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1458228/+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 1474324] Re: Sound indicator disappeared after headset connection issue
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1474324 Title: Sound indicator disappeared after headset connection issue Status in bluez package in Ubuntu: Incomplete Status in indicator-sound package in Ubuntu: Invalid Bug description: I switched my bluetooth headset on, it says it's connected. Selecting it in the audio settings doesn't enable it, sound still comes from the internal speakers. Switched my headset off and on again, no effect - usually this would have made it work. The headset doesn't indicate it's connected this time. Headset is still visible as a non-functional device in the audio settings. Meanwhile the sound indicator has disappeared. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150413-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 14 07:38:07 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-13 (62 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-sound SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1474324/+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 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Tags added: ubuntu-touch -- 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+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 1479229] Re: Bluetooth First Pairing OK then no more connection
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1479229 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1479229 Title: Bluetooth First Pairing OK then no more connection Status in bluez package in Ubuntu: Incomplete Bug description: Hello my bug looks like a lot like Bug #27687 the var/lib/bluetooth//linkey is own by root so enable to reconnect my device (mouse in this case) and if i remove the device of known devices bluetooth manager is not able to discover the device again Thanks for the help in advance Kind Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479229/+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 1479442] Re: IN CAR: Previous Calls log is not shown in the car display
** Tags added: ubuntu-touch -- 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/1479442 Title: IN CAR: Previous Calls log is not shown in the car display Status in Canonical System Image: Triaged Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT a list of previous calls and a car that support bluetooth phones (Skoda Superb 2013 in my case) 1. Connect DUT to the car 2. In the car menu navigate to previous calls log EXPECTED: I expect to see a list of past calls similar to those I see on the phone itself ACTUAL: Car shows no previous calls log at all VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479442/+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 1473043] Re: bluetoothd -n consuming 100% after device disconnects
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1473043 Title: bluetoothd -n consuming 100% after device disconnects Status in bluez package in Ubuntu: Incomplete Bug description: On a regular basis after disconnecting a bluetooth device, usually my headset, the laptop starts to heat up and "/usr/sbin/bluetoothd -n" consumes 100% CPU. A temporary solution is to run "sudo service bluetooth restart". This is bluez 4.101-0ubuntu25 on 15.04 with all updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1473043/+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 1479449] Re: IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio
** Tags added: ubuntu-touch -- 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/1479449 Title: IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT, a second device, a car with bluetooth phone support (Skoda Supberb 2013 in my case) 1. Connect the DUT to the car 2. From the second device call the car 3. The ringer starts EXPECTED: I expect all audio to come through the car speakers ACTUAL: The ringer is routed through the loud speaker of the phone not the car audio VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479449/+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 1479440] Re: IN CAR: Missed calls are not shared with the car via bluetooth
** Tags added: ubuntu-touch -- 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/1479440 Title: IN CAR: Missed calls are not shared with the car via bluetooth Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT, a secondary device and a car with bluetooth phone capabilities (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Using the menu system in the car navigate to missed calls 3. Message There are no missed calls 4. Call the DUT from the secondary device 5. Hang up the secondary device once the call is received 6. Check the missed calls log again (shows on the phone but not on the car) EXPECTED: I expect to see a list of missed calls ACTUAL: No missed call are available VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479440/+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 1479453] Re: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth
** Tags added: ubuntu-touch -- 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/1479453 Title: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: Requirements: DUT, a second device and a car that supports bluetooth phones (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Receive multiple calls EXPECTED: I expect the call audio to always be routed through the car audio and be audible ACTUAL: After a number of calls all of a sudden you can accept the call but you get no audio from the call at all, the mic is still working as expected. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479453/+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 1485378] Re: [REGRESSION] bluetooth visibility turns off by itself after 3 minutes
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1485378 Title: [REGRESSION] bluetooth visibility turns off by itself after 3 minutes Status in bluez package in Ubuntu: Incomplete Bug description: I had Ubuntu 14.04 and I had the Bluetooth Visibility set to On. (in the submenu under the bluetooth tray icon, where it reads "Visible") It used to be always on, I didn't have to turn it on every time I wanted my computer to be visible. I upgraded to 14.10 and then to 15.04, and then when failing to send a file over bluetooth to my computer, I found out Visible was off. I turned it on, and it worked. However, after a few minutes, it had turned off again. I can't find a setting anywhere to automatically turn off after N seconds. It would make sense to have that. If there is, it should be accessible through Bluetooth settings. If such a settings doesn't exist and once turned on bluetooth visibility is supposed to remain on, then there's some bug which is causing it to randomly turn off. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 16 23:17:42 2015 InstallationDate: Installed on 2013-10-11 (674 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to vivid on 2015-08-15 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:630 acl:0 sco:0 events:40 errors:0 TX bytes:988 acl:0 sco:0 commands:40 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1485378/+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 1445376] Re: A2DP skips when conneted to handsfree device
** Tags added: ubuntu-touch -- 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/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Confirmed Bug description: When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk Ego Flash) via Bluetooth I experience a skipping problem when playing sound files through A2DP. Half a second for each second there is a pause. The rest of that half second seems to clear a buffer which results in "extra fast" audio. To illustrate, listening to a podcast I would expect to hear something like "bla bla bla". However, what I do get to hear sounds more like "flapflapflap - pause - flapflapflap - pause - ...". When I connect my Aquaris to my A2DP speakers at home, the audio is perfect. Also, handsfree telephony in my car works like a charm. So I guess it's just the combination of A2DP while connected to the handsfree device which causes the trouble. In the past I've used several phones with the Funkwerk device (always with handsfree *and* A2DP functionality) including an N900 running Maemo. There have never been any problems with those. OS build number 21 KRILIN01A-S15A_BQ_L100EN_2021_150410 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445376/+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 1446239] Re: Bluetooth - rtl8723bt doesn't work anymore - Xubuntu, KDE - vivid
** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- 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/1446239 Title: Bluetooth - rtl8723bt doesn't work anymore - Xubuntu, KDE - vivid Status in bluez package in Ubuntu: Invalid Bug description: At least in Beta 1 and Beta 2 of Xubuntu, bluetooth worked fine after installing the latest bluetooth driver from LWfinger (https://github.com/lwfinger/). After the latest kernel release I'm not able to get bluetooth to work anymore. With Kubuntu (vivid) there was and is no way to get rtl8723au_bt running. lsusb: Bus 004 Device 005: ID 5986:053d Acer, Inc Bus 004 Device 004: ID 0bda:1724 Realtek Semiconductor Corp. Bus 004 Device 003: ID 2047:0855 Texas Instruments Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 004: ID 03eb:8814 Atmel Corp. Bus 003 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rfkill list: 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no Hardware Lenovo Yoga 11, WiFi = RTL8723 works without any problem but rtl8723au_bt means no external mouse. In addition to Xubuntu (vivid) the TLP repository with TLP is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1446239/+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 1445408] Re: USB-bluetooth-mouse not detected
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1445408 Title: USB-bluetooth-mouse not detected Status in bluez package in Ubuntu: Incomplete Bug description: Upgraded from Kubuntu 14.04 to 14.10 to 15.04 beta2 yesterday After finishing the final upgrade and rebooting my USB mouse is no longer working. Plugging in the USB dongle (it's a Logitech mouse with bluetooth connection, worked fine so far) I get the following in syslog: Apr 17 11:22:33 tp220 kernel: [13867.118079] usb 4-1.1: new full-speed USB device number 8 using ehci-pci Apr 17 11:22:34 tp220 kernel: [13867.213829] usb 4-1.1: New USB device found, idVendor=046d, idProduct=c52e Apr 17 11:22:34 tp220 kernel: [13867.213840] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 17 11:22:34 tp220 kernel: [13867.213845] usb 4-1.1: Product: USB Receiver Apr 17 11:22:34 tp220 kernel: [13867.213850] usb 4-1.1: Manufacturer: Logitech Apr 17 11:22:34 tp220 mtp-probe: checking bus 4, device 8: "/sys/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1" Apr 17 11:22:34 tp220 mtp-probe: bus: 4, device: 8 was not an MTP device I remember having seen messages that the USB device list could not be accessed, but these are gone now. Please let me know if I can be of further help to track this down. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu2 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: KDE Date: Fri Apr 17 11:18:08 2015 InstallationDate: Installed on 2014-09-09 (219 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 4291S7Z ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-14-generic root=UUID=8c3ff90d-58e2-4696-9e3a-eddf92c84a41 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-17 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291S7Z dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 4291S7ZR9M0ZD3 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4291S7Z:pvrThinkPadX220:rvnLENOVO:rn4291S7Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291S7Z dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1445408/+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 1443985] Re: Apple magic mouse does not pair with Ubuntu
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Summary changed: - Apple macig mouse does not pair with Ubuntu + Apple magic mouse does not pair with Ubuntu ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1443985 Title: Apple magic mouse does not pair with Ubuntu Status in bluez package in Ubuntu: Incomplete Bug description: Same phenomenon as previously: Connection to Apple magic mouse fails. In the pairing window, the device flickers. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CasperVersion: 1.359 CurrentDesktop: Unity Date: Tue Apr 14 14:28:33 2015 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150414) MachineType: Apple Inc. MacBookPro10,1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=de SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:7000 acl:15 sco:0 events:318 errors:0 TX bytes:2665 acl:15 sco:0 commands:155 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1443985/+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 1442941] Re: Bluetooth Built-in HP 650 does not work in Ubuntu 14.10.
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1442941 Title: Bluetooth Built-in HP 650 does not work in Ubuntu 14.10. Status in bluez package in Ubuntu: Incomplete Bug description: When I purchased the HP 650 Laptop, 12.04LTS have installed Ubuntu, built-in Bluetooth function and F12 light was white. I made updates to 12.10 to 14.10. Since then, bluetooth built fails, the F12 LED is orange. USB works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1442941/+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 1436976] Re: cannot enable bluetooth
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1436976 Title: cannot enable bluetooth Status in bluez package in Ubuntu: Incomplete Bug description: One day I decided pairing my computer with my bluetooth headset. I enabled bluetooth via the basic bluetooth manager, and was able to connect my headset. Then I turned off my computer, and since then, bluetooth isn't working anymore. When I go on the bluetooth manager (Applications>System Tools>Preferences>Bluetooth), bluetooth is disabled. I can switch it to the "on" position, but it stays disabled. Ubuntu release : 14.10 bluetooth package : 4.101-0ubuntu20 Computer model : Aspire V3-771 Wireless card : Qualcomm Atheros AR9462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1436976/+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 1432043] Re: DX... Not work Bluethoot after update
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1432043 Title: DX... Not work Bluethoot after update Status in bluez package in Ubuntu: Incomplete Bug description: I update Ubuntu vivid and upgrade Bluez(?) and not on Bluethoot in gnome-control-center. bluez 4.101-0ubuntu23 to bluez 4.101-0ubuntu24 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-control-center 1:3.14.2-2ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 13 17:32:02 2015 InstallationDate: Installed on 2014-09-25 (169 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1432043/+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
** Tags added: ubuntu-touch -- 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 1432788] Re: Race in vivid means sometimes bluetooth is no available
** Tags added: ubuntu-touch -- 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/1432788 Title: Race in vivid means sometimes bluetooth is no available Status in Canonical System Image: Invalid Status in bluez package in Ubuntu: New Bug description: STEPS: 1. Flash a fresh image of vivid on a krillin device 2. Check if bluetooth is on 3. Reboot EXPECTED: I always expect bluetooth to be on ACTUAL: Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how ever it wouldn't connect to anything. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1432788/+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 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1442896 Title: Bluetooth mouse disconnects and reconnects every few seconds Status in bluez package in Ubuntu: Incomplete Bug description: I have a bluetooth mouse (Genius Traveller 9005BT) that I have been using without problems with Ubuntu for over a year. Since a few weeks ago, however, it started disconnecting and reconnected from the computer. The symptoms are like this: 1. The mouse works, and the bluetooth icon on the computer is visible (in gnome-shell's top bar) 2. The mouse stops working, but the bluetooth icon is still visible. This state lasts between 1 and 10 seconds. 3. The bluetooth icon vanishes. This can last for half a second if I keep trying to use the mouse, to forever I I leave the mouse alone 4. The bluetooth icon reappears and the mouse starts working again. This state last from 2-3 seconds if I don't move the mouse, to seemingly forever if I continuously move the mouse This seems to occur only after a suspend/resume cycle, and rebooting the computer fixes the issue. The only thing I see in syslog is this when the mouse reconnects: Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 0005:0458:0139.002F: unknown main item tag 0x0 Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as /devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59 Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] on e8:2a:ea:8b:a5:5f ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 11 09:49:37 2015 InstallationDate: Installed on 2015-01-23 (77 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: E8:2A:EA:8B:A5:5F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0 TX bytes:29044 acl:238 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1442896/+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 1442361] Re: Pairing with bluetooth devices not working on 15.04
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete -- 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/1442361 Title: Pairing with bluetooth devices not working on 15.04 Status in Bluez Utilities: New Status in bluez package in Ubuntu: Incomplete Bug description: Devices paired on 14.10 are working normally but I'm not able to pair with any new device 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 15.04 3) What you expected to happen Window with pairing key and confirmation button should appear 4) What happened instead It doesn't appear e.g: when trying to pair from Windows PC there is window with PIN and "Confirm" button, but it doesn't appear on Ubuntu. When I click "Confirm" on WIndows PC it shows pairing error. (Similar things happen when trying to pair with Android phone and etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1442361/+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 1421448] Re: problem pairing Jabra BT2050
** Tags added: ubuntu-touch -- 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/1421448 Title: problem pairing Jabra BT2050 Status in bluez package in Ubuntu: New Bug description: This is tested on: nexus4 (vivid-proposed) #96 bq (stable) #17 Steps taken: 1. turn on Bluetooth on device. 2. put Jabra BT2050 on pairing mode. 3. click on "Jabra BT2050..." in Bluetooth setting on device 4. prompted with new page, click on "Connect" button. 5. New popover with this message "Bluetooth Pairing Request PIN for 'Jabra BT2050' [textfield: ], click on "Pair" button. [ at this point new handset is added to the list and "connected" sound is played in handset but whole settings UI on device is frozen for about 15sec. bluetooth icon in topbar is white-connected. ] 6. In bluetooth setting Click on ">" next to Jabra BT2050 to see more info. 7. Status on that page is saying: "Connecting..." while button at the bottom says: "Disconnect" see attached picture. 8. open Phone app and try to call anyone, sound is coming out from phone speakers. After "forgetting this device" and pairing it again for few times I managed to connect it and it worked but only to make one phone call after I hangup I wasn't able to use bluetooth again. If I good remember this time then it worked I was't prompted for pairing password. Any more info you need please let me know. I must add that this handset works well on nexus4 and other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1421448/+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 1419877] Re: [bluetooth] krillin advertized as type "computer"
** Tags added: ubuntu-touch -- 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/1419877 Title: [bluetooth] krillin advertized as type "computer" Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: Using rtm 228, the device is advertized as being a "computer", it should probably be a "phone" rather? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+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 1423266] Re: Fails to set the HSP/HFP profile with Ford New Fiesta Sedan 2014 (Brazil)
** Tags added: ubuntu-touch -- 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/1423266 Title: Fails to set the HSP/HFP profile with Ford New Fiesta Sedan 2014 (Brazil) Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Car: Ford New Fiesta Sedan 2014 (the one sold in Brazil) Image: RTM 239 Device: krillin I paired the device, and tried to start a call but noticed there was no audio, so with help from Salveti we figured out switching to the hsp profile is faling, so the attached syslog is after running the following command: pactl set-card-profile bluez_card.00_21_CC_E9_02_39 hsp To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1423266/+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 1421598] Re: DisplayPasskey() "entered" number wrong on some devices
** Tags added: ubuntu-touch -- 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/1421598 Title: DisplayPasskey() "entered" number wrong on some devices Status in bluez package in Ubuntu: New Bug description: Using vivid on the n7, the number of "entered" digit is random/wrong, it should start at 0 and increase to 6 as you type, but on that device it returns random value (i.e 75, 92, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1421598/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd
Removing packages from artful: lxc-android-config 0.230+17.04.20170216-0ubuntu1 in artful lxc-android-config 0.230+17.04.20170216-0ubuntu1 in artful amd64 lxc-android-config 0.230+17.04.20170216-0ubuntu1 in artful arm64 lxc-android-config 0.230+17.04.20170216-0ubuntu1 in artful armhf lxc-android-config 0.230+17.04.20170216-0ubuntu1 in artful i386 lxc-android-config 0.230+17.04.20170216-0ubuntu1 in artful ppc64el lxc-android-config 0.230+17.04.20170216-0ubuntu1 in artful s390x Comment: Discontinued product; LP: #1649310 1 package successfully removed. ** Changed in: lxc-android-config (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Triaged Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart-watchdog package in Ubuntu: Fix Released Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd
Removing packages from artful: upstart-watchdog 0.4 in artful upstart-watchdog 0.4 in artful amd64 upstart-watchdog 0.4 in artful arm64 upstart-watchdog 0.4 in artful armhf upstart-watchdog 0.4 in artful i386 upstart-watchdog 0.4 in artful ppc64el upstart-watchdog 0.4 in artful s390x Comment: Discontinued product; LP: #1649310 1 package successfully removed. ** Changed in: upstart-watchdog (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Triaged Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart-watchdog package in Ubuntu: Fix Released Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd
Removing packages from artful: ubuntu-touch-session 0.109+17.04.20170301-0ubuntu1 in artful ubuntu-touch-session 0.109+17.04.20170301-0ubuntu1 in artful amd64 ubuntu-touch-session 0.109+17.04.20170301-0ubuntu1 in artful arm64 ubuntu-touch-session 0.109+17.04.20170301-0ubuntu1 in artful armhf ubuntu-touch-session 0.109+17.04.20170301-0ubuntu1 in artful i386 ubuntu-touch-session 0.109+17.04.20170301-0ubuntu1 in artful ppc64el ubuntu-touch-session 0.109+17.04.20170301-0ubuntu1 in artful s390x Comment: Discontinued product; LP: #1649310 1 package successfully removed. ** Changed in: ubuntu-touch-session (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Triaged Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart-watchdog package in Ubuntu: Fix Released Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd
Removing packages from artful: ubuntu-touch-meta 1.288 in artful ubuntu-sdk-libs 1.288 in artful amd64 ubuntu-sdk-libs 1.288 in artful arm64 ubuntu-sdk-libs 1.288 in artful armhf ubuntu-sdk-libs 1.288 in artful i386 ubuntu-touch 1.288 in artful amd64 ubuntu-touch 1.288 in artful arm64 ubuntu-touch 1.288 in artful armhf ubuntu-touch 1.288 in artful i386 Comment: Discontinued product; LP: #1649310 Remove [y|N]? y 1 package successfully removed. ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Triaged Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart-watchdog package in Ubuntu: Fix Released Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd
Removing packages from artful: unity8-desktop-session 1.0.13+17.04.20170328.1-0ubuntu1 in artful unity8-desktop-session 1.0.13+17.04.20170328.1-0ubuntu1 in artful amd64 unity8-desktop-session 1.0.13+17.04.20170328.1-0ubuntu1 in artful arm64 unity8-desktop-session 1.0.13+17.04.20170328.1-0ubuntu1 in artful armhf unity8-desktop-session 1.0.13+17.04.20170328.1-0ubuntu1 in artful i386 unity8-desktop-session 1.0.13+17.04.20170328.1-0ubuntu1 in artful ppc64el unity8-desktop-session 1.0.13+17.04.20170328.1-0ubuntu1 in artful s390x unity8-desktop-session-mir 1.0.13+17.04.20170328.1-0ubuntu1 in artful amd64 unity8-desktop-session-mir 1.0.13+17.04.20170328.1-0ubuntu1 in artful arm64 unity8-desktop-session-mir 1.0.13+17.04.20170328.1-0ubuntu1 in artful armhf unity8-desktop-session-mir 1.0.13+17.04.20170328.1-0ubuntu1 in artful i386 unity8-desktop-session-mir 1.0.13+17.04.20170328.1-0ubuntu1 in artful ppc64el unity8-desktop-session-mir 1.0.13+17.04.20170328.1-0ubuntu1 in artful s390x unity8-session-snap 1.0.13+17.04.20170328.1-0ubuntu1 in artful amd64 unity8-session-snap 1.0.13+17.04.20170328.1-0ubuntu1 in artful arm64 unity8-session-snap 1.0.13+17.04.20170328.1-0ubuntu1 in artful armhf unity8-session-snap 1.0.13+17.04.20170328.1-0ubuntu1 in artful i386 unity8-session-snap 1.0.13+17.04.20170328.1-0ubuntu1 in artful ppc64el unity8-session-snap 1.0.13+17.04.20170328.1-0ubuntu1 in artful s390x Comment: Discontinued product; LP: #1649310 Remove [y|N]? y 1 package successfully removed. ** Changed in: unity8-desktop-session (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Triaged Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Status in upstart-watchdog package in Ubuntu: Fix Released Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to:
[Touch-packages] [Bug 1688169] [NEW] artful fresh install is missing gnome-shell / ubuntu-gnome-desktop
Public bug reported: artful fresh install is missing gnome-shell / ubuntu-gnome-desktop Seems to install Unity7 alone. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1688169 Title: artful fresh install is missing gnome-shell / ubuntu-gnome-desktop Status in ubuntu-meta package in Ubuntu: New Bug description: artful fresh install is missing gnome-shell / ubuntu-gnome-desktop Seems to install Unity7 alone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1688169/+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 1687722] Re: lightdm should not have a pulseaudio config
This would need to be fixed in the appropriate greeter - LightDM does not write any files in /home/lightdm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1687722 Title: lightdm should not have a pulseaudio config Status in lightdm package in Ubuntu: New Bug description: If the directory /var/lib/lightdm/.config/pulse exists, then whenever the screen goes blank, the sound volume changes, mutes, or takes on some other random parameters specified by this file. It does not reset on unlocking the screen. This is an extraordinarily dumb behaviour which can be temporarily remedied by deleting that directory, or swapping out lightdm for xscreensaver. Please make sure that lightdm cannot write a pulse config file, or that consolekit or whatever for pulseaudio does not use system users as sources for parameters, and so forth. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 2 11:23:46 2017 InstallationDate: Installed on 2016-10-09 (204 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1687722/+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 1688143] Re: Stop disabling bluetooth!
Yes bluez is the common Bluetooth stack for Linux desktop. It's possible other packages are also involved in this bug, but many people are reporting similar issues so this is likely to get merged into some other existing Bluetooth bug. -- 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/1688143 Title: Stop disabling bluetooth! Status in bluez package in Ubuntu: New Bug description: Randomly after resuming from sleep, restarting, logging in or opening the screen on a laptop, bluetooth gets disabled. This is a major problem for bluetooth peripheral users as it can cause the system to be unusable without having to use a non-bluetooth peripheral just to re-enable bluetooth. This is completely unrelated to bluetooth discovery, of which is normally disabled in this use-case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688143/+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 1688143] Re: Stop disabling bluetooth!
Wait what? I never set it to launchpad-integration, it was originally kdebluetooth as bluez doesn't show when you search for bluetooth packages... Is bluez part of bluetoothd and what kubuntu uses? -- 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/1688143 Title: Stop disabling bluetooth! Status in bluez package in Ubuntu: New Bug description: Randomly after resuming from sleep, restarting, logging in or opening the screen on a laptop, bluetooth gets disabled. This is a major problem for bluetooth peripheral users as it can cause the system to be unusable without having to use a non-bluetooth peripheral just to re-enable bluetooth. This is completely unrelated to bluetooth discovery, of which is normally disabled in this use-case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688143/+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 1681040] Re: Scaled display resolution is not detected correctly in lightdm display manager
** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)
** Package changed: xorg-server (Ubuntu) => unity-control-center
(Ubuntu)
** Summary changed:
- Scaled display resolution is not detected correctly in lightdm display manager
+ Scaled display resolution is not detected correctly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1681040
Title:
Scaled display resolution is not detected correctly
Status in unity-control-center package in Ubuntu:
Confirmed
Bug description:
Environment:
Ubuntu 16.04.2 LTS
nvidia-375
I have a laptop screen with resolution 3840x2160 and external display with
resolution 3440x1440.
I am scaling laptop display to resolution 1920x1080 with
command nvidia-settings --attach CurrentMetaMode="DPY-0: nvidia-auto-select
@3440x1440 +1920+0 {ViewPortIn=3440x1440, ViewPortOut=3440x1440+0+0}, DPY-3:
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=3840x2160+0+0}"
Bug: Display manager is not detecting scaled resolution correctly. Please see
the attachment.
Caused effect: When focus is on laptop display and pressing Alt + Tab the
application switcher is not shown in center of laptop display but partly in
external display.
$ apt-cache policy lightdm
lightdm:
Installed: 1.18.3-0ubuntu1.1
Candidate: 1.18.3-0ubuntu1.1
---
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: markus 3264 F pulseaudio
/dev/snd/controlC0: markus 3264 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-04-07 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ZBook Studio G3
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic.efi.signed
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset
pnpacpi=off vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
RelatedPackageVersions:
linux-restricted-modules-4.8.0-46-generic N/A
linux-backports-modules-4.8.0-46-generic N/A
linux-firmware1.157.8
Tags: xenial
Uname: Linux 4.8.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/02/2016
dmi.bios.vendor: HP
dmi.bios.version: N82 Ver. 01.15
dmi.board.name: 80D4
dmi.board.vendor: HP
dmi.board.version: KBC Version 11.67
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
dmi.product.name: HP ZBook Studio G3
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1681040/+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 1688143] Re: Stop disabling bluetooth!
** Package changed: launchpad-integration (Ubuntu) => bluez (Ubuntu) -- 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/1688143 Title: Stop disabling bluetooth! Status in bluez package in Ubuntu: New Bug description: Randomly after resuming from sleep, restarting, logging in or opening the screen on a laptop, bluetooth gets disabled. This is a major problem for bluetooth peripheral users as it can cause the system to be unusable without having to use a non-bluetooth peripheral just to re-enable bluetooth. This is completely unrelated to bluetooth discovery, of which is normally disabled in this use-case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688143/+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 1688143] [NEW] Stop disabling bluetooth!
You have been subscribed to a public bug: Randomly after resuming from sleep, restarting, logging in or opening the screen on a laptop, bluetooth gets disabled. This is a major problem for bluetooth peripheral users as it can cause the system to be unusable without having to use a non-bluetooth peripheral just to re-enable bluetooth. This is completely unrelated to bluetooth discovery, of which is normally disabled in this use-case. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- Stop disabling bluetooth! https://bugs.launchpad.net/bugs/1688143 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
** Changed in: network-manager (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/293139 Title: NetworkManager does not use dhclient-exit-hooks.d Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Triaged Status in network-manager package in Debian: New Status in network-manager package in Fedora: Won't Fix Bug description: Binary package hint: network-manager I am running intrepid i386 and amd64 on a handful of systems. On every system, both upgraded and fresh installs, i use a script (first attachment) for updating a DNS record through DNSSEC. Using /etc/network/interfaces or invoking dhclient directly correctly updates the DNS record (second attachment). Using network-manager the DNS record update script doesn't seem to run (third attachment). On a laptop it is inconvenient to constantly reconfigure devices. For desktops, a workaround is to have a dhcp entry in /etc/network/interfaces for the relevant connection. As a side note, the script is designed to work with PPP ip-up.d as well. However, I haven't yet found a way to configure network-manager to dial up to 3G over a bluetooth connected modem. It may apply here similarily though. Wvdial works with the script. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/293139/+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 1688149] [NEW] package account-plugin-google (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también
Public bug reported: Durante la instalación de Gnome3 sobre Ubuntu 16.04 surgió este error. Estoy repitiendo la instalación a fin de verificar si fue un hecho aislado o se trata de un error. During the installation of Gnome3 on Ubuntu 16.04 this error appeared. I am repeating the installation in order to verify if it was an isolated event or it is an error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed May 3 21:15:32 2017 ErrorMessage: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-04-29 (369 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1688149 Title: package account-plugin-google (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: Durante la instalación de Gnome3 sobre Ubuntu 16.04 surgió este error. Estoy repitiendo la instalación a fin de verificar si fue un hecho aislado o se trata de un error. During the installation of Gnome3 on Ubuntu 16.04 this error appeared. I am repeating the installation in order to verify if it was an isolated event or it is an error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed May 3 21:15:32 2017 ErrorMessage: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-04-29 (369 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1688149/+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 1688149] Re: package account-plugin-google (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también e
Al repetir la instalacion el error no se presenta. Puede entonces tratarse de un hecho aislado o un fallo en la secuencia de instalacion. When repeating the installation the error does not occur. It may then be an isolated event or a failure in the installation sequence. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1688149 Title: package account-plugin-google (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: Durante la instalación de Gnome3 sobre Ubuntu 16.04 surgió este error. Estoy repitiendo la instalación a fin de verificar si fue un hecho aislado o se trata de un error. During the installation of Gnome3 on Ubuntu 16.04 this error appeared. I am repeating the installation in order to verify if it was an isolated event or it is an error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed May 3 21:15:32 2017 ErrorMessage: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-04-29 (369 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: intentando sobreescribir `/usr/share/accounts/providers/google.provider', que está también en el paquete kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1688149/+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 1669133] Re: Drop unnecessary rename of dlm -> dlm-controld (binary package)
** Changed in: dlm (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: ocfs2-tools (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1669133 Title: Drop unnecessary rename of dlm -> dlm-controld (binary package) Status in dlm package in Ubuntu: Triaged Status in lvm2 package in Ubuntu: Triaged Status in ocfs2-tools package in Ubuntu: Triaged Bug description: dlm -> dlm-controld transition (will need to be kept through 18.04 for LTS upgraders) - Add transitional dummy binary package to rename back - Drop delta in lvm2 and ocfs2-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1669133/+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 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
** Changed in: systemd (Debian)
Status: Unknown => New
--
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/1685484
Title:
DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
Status in systemd package in Ubuntu:
Confirmed
Status in systemd package in Debian:
New
Bug description:
I think it's regression for
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1578663 in
zesty.
1. NTP servers are send via DHCP and seen by NM:
$ nmcli con show connection1 | grep ntp
DHCP4.OPTION[30]: requested_ntp_servers = 1
DHCP4.OPTION[31]: ntp_servers = 80.50.231.226
217.96.29.26 212.160.106.226
2. timesyncd is using hardcoded default NTP server:
$ systemctl -n 200 status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
`-disable-with-time-daemon.conf
Active: active (running) since Sat 2017-04-22 13:12:23 CEST; 16min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 576 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
Memory: 1.5M
CPU: 20ms
CGroup: /system.slice/systemd-timesyncd.service
`-576 /lib/systemd/systemd-timesyncd
Apr 22 13:12:23 slodki systemd[1]: Starting Network Time Synchronization...
Apr 22 13:12:23 slodki systemd[1]: Started Network Time Synchronization.
Apr 22 13:12:53 slodki systemd-timesyncd[576]: Synchronized to time server
91.189.89.199:123 (ntp.ubuntu.com).
3. There are not other time sync deamons installed:
$ cat
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[Unit]
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService
$ ls -l /usr/sbin/{ntpd,openntpd,chronyd,VBoxService}
ls: cannot access '/usr/sbin/ntpd': No such file or directory
ls: cannot access '/usr/sbin/openntpd': No such file or directory
ls: cannot access '/usr/sbin/chronyd': No such file or directory
ls: cannot access '/usr/sbin/VBoxService': No such file or directory
4. There is only one default timesyncd.conf file with default values:
$ sudo find / -iname \*timesync\*
/etc/systemd/timesyncd.conf
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/dhcp/dhclient-exit-hooks.d/timesyncd
/usr/share/man/man5/timesyncd.conf.d.5.gz
/usr/share/man/man5/timesyncd.conf.5.gz
/usr/share/man/man8/systemd-timesyncd.8.gz
/usr/share/man/man8/systemd-timesyncd.service.8.gz
/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-6NwdRT
/lib/systemd/systemd-timesyncd
/lib/systemd/system/systemd-timesyncd.service
/lib/systemd/system/systemd-timesyncd.service.d
/var/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-jz0q47
$ cat /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.
[Time]
#NTP=
#FallbackNTP=ntp.ubuntu.com
5. DHCP hook installed as /etc/dhcp/dhclient-exit-hooks.d/timesyncd is
not working,
TIMESYNCD_CONF=/run/systemd/timesyncd.conf.d/01-dhclient.conf is not
created.
6. After manually executing steps from hook all works as expected:
$ sudo mkdir -p /run/systemd/timesyncd.conf.d/
$ sudo cat [Time]
> NTP=80.50.231.226 217.96.29.26 212.160.106.226
> EOF
$ sudo systemctl try-restart systemd-timesyncd.service
$ sudo systemctl status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
`-disable-with-time-daemon.conf
Active: active (running) since Sat 2017-04-22 13:47:28 CEST; 2min 6s ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 3094 (systemd-timesyn)
Status: "Synchronized to time server 80.50.231.226:123 (80.50.231.226)."
Tasks: 2
[Touch-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x in Ubuntu
Checking in 17.10 PRIME Synchronization can be enabled & works in UbuntuGnome but doesn't in Ubuntu. Main reason is in UbuntuGnome nvidia_drm.modeset can be enabled, in Ubuntu it can't. ex.'s UbuntuGnome, gdm3 $ sudo cat /sys/module/nvidia_drm/parameters/modeset [sudo] password for doug: Y $ xrandr --verbose Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (0x46) normal (normal left inverted right x axis y axis) 345mm x 194mm Identifier: 0x42 Timestamp: 21140 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: _MUTTER_PRESENTATION_OUTPUT: 0 EDID: 000030e4d902 00150103802313780a15d59e59509826 0e50540001010101010101010101 0101010101017e3680b070381f403020 350059c21019 00fe004c 4720446973706c61790a202000fe 004c503135365746312d544c4232004b PRIME Synchronization: 1 supported: 0, 1 Same machine in Ubuntu sudo cat /sys/module/nvidia_drm/parameters/modeset [sudo] password for doug: N $ xrandr --verbose Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (0x46) normal (normal left inverted right x axis y axis) 345mm x 194mm Identifier: 0x42 Timestamp: 12578 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 000030e4d902 00150103802313780a15d59e59509826 0e50540001010101010101010101 0101010101017e3680b070381f403020 350059c21019 00fe004c 4720446973706c61790a202000fe 004c503135365746312d544c4232004b PRIME Synchronization: 0 supported: 0, 1 So until shown otherwise am adding lightdm ** Summary changed: - PRIME synchronization not working with xserver-1.19.x + PRIME synchronization not working with xserver-1.19.x in Ubuntu ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1674304 Title: PRIME synchronization not working with xserver-1.19.x in Ubuntu Status in lightdm package in Ubuntu: New Status in nvidia-prime package in Ubuntu: Confirmed Bug description: xserver-1.19.x is being proposed for 17.04, currently available in test ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 On 2 separate Optimus laptops there is no sign of it actually working, tearing while using nvidia drivers (375.x) is rampart. Testing with both current 4.10.0-13 & previous 4.9.0-11 kernels. Shows this in kern.log so support is enabled Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver supports precise vblank timestamp But in Xorg.0.log - randr: falling back to unsynchronized pixmap sharing ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 20 07:53:12 2017 InstallationDate: Installed on 2017-03-15 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1674304/+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 1575779] Re: hostnamectl fails under lxd unpriv container
** Merge proposal linked: https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/323588 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1575779 Title: hostnamectl fails under lxd unpriv container Status in apparmor package in Ubuntu: Triaged Bug description: 1. % lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2. % apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy lxd lxd: Installed: 2.0.0-0ubuntu4 Candidate: 2.0.0-0ubuntu4 Version table: *** 2.0.0-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 4. hostnamectl status hangs indefinitely On the host, there are some audit messages for each invocation of hostnamectl [411617.032274] audit: type=1400 audit(1461695563.731:100): apparmor="DENIED" operation="file_lock" profile="lxd- x1_" pid=17100 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none It's related to socket activation. One can workaround this by running systemd-hostnamed in the background first root@x1:~# /lib/systemd/systemd-hostnamed & [1] 2462 root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Apr 27 11:19:27 2016 InstallationDate: Installed on 2016-01-01 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1687129] Re: Needs to allow updates from the ESM archive
Output now that the publication change is live on esm.u.c: $ sudo unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security', 'o=UbuntuESM,a=precise'] Checking: unattended-upgrades ([""]) pkgs that look like they should be upgraded: unattended-upgrades Get:1 https://esm.ubuntu.com/ubuntu/ precise/main unattended-upgrades all 0.76ubuntu1.4 [24.8 kB] Err https://esm.ubuntu.com/ubuntu/ precise/main unattended-upgrades all 0.76ubuntu1.4 Fetched 0 B in 0s (0 B/s) $ This looks like what we want. ** Tags removed: verification-needed ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1687129 Title: Needs to allow updates from the ESM archive Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades source package in Precise: Fix Committed Bug description: [SRU Justification] When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match. [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both. [Test case] 1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades' 2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to enable the ESM archive 3. run 'sudo apt-get update' 4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed. 6. install unattended-upgrades from -proposed. 7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package. [Regression potential] Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+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 1688121] [NEW] KDC/kadmind explicit wildcard listener addresses do not use pktinfo
Public bug reported:
This is fixed in artful in krb5 1.15-2
- upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
- debian: conflated into
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
- debian patch in artful's krb5:
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch
TL;DR when kinit uses udp on an aliased interface address, server
responds with the wrong source IP
On zesty:
a) install krb5-kdc and krb5-admin-server
sudo apt install krb5-kdc krb5-admin-server
when prompted, use EXAMPLE.ORG (all caps) as the default realm
when prompted, select your own IP for the KDC and the Admin servers
b) configure a new realm called EXAMPLE.ORG
sudo krb5_newrealm
use any password of your liking when prompted
c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and
with mandatory PREAUTH:
sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
d) extract the ubuntu principal keytab and time how long it takes to obtain a
ticket:
$ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
$ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real0m0.022s
$ klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: ubu...@example.org
Valid starting Expires Service principal
05/03/2017 21:22:08 05/04/2017 07:22:08 krbtgt/example@example.org
renew until 05/04/2017 21:22:08
e) add another IP to your network interface. For example, this adds 10.0.5.155
to ens3 (it has 10.0.5.55/24 already in my case):
sudo ip addr add 10.0.5.155/24 dev ens3
f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc
and admin server's IP to this new IP you just added in step (e):
[realms]
EXAMPLE.ORG = {
kdc = 10.0.5.155
admin_server = 10.0.5.155
g) Time again how long it takes to obtain a ticket:
$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real0m2.017s
Step (g) shows the bug.
On a more technical level, we can see that the server responds to kinit's UDP
request using an incorrect source IP, therefore kinit never "sees" it. It
quickly times out and switches to TCP, where the server responds using the
correct source IP:
1 0.010.0.5.55 → 10.0.5.155 KRB5 216 AS-REQ
2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error:
KRB5KDC_ERR_PREAUTH_REQUIRED
(2) has the incorrect source ip!
After roughly 1s, kinit switches to tcp and tries again:
3 1.00323150710.0.5.55 → 10.0.5.155 TCP 76 55588 → 88 [SYN] Seq=0
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
4 1.003269692 10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK]
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273
TSecr=3523453804 WS=128
5 1.00330261410.0.5.55 → 10.0.5.155 TCP 68 55588 → 88 [ACK] Seq=1
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
6 1.00354520410.0.5.55 → 10.0.5.155 KRB5 244 AS-REQ
7 1.003567693 10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
8 1.003799664 10.0.5.155 → 10.0.5.55KRB5 326 KRB Error:
KRB5KDC_ERR_PREAUTH_REQUIRED
(continues)
(8) and the whole tcp handshake happens with the correct IP addresses and the
exchange happens and we get the ticket, but not before kinit repeats the
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)
** Affects: krb5 (Ubuntu)
Importance: Undecided
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Description changed:
- upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
- debian: conflated into
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
- debian patch in artful's krb5:
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch
- TL;DR obtaining a ticket (kinit) takes longer when talking to the kdc on
- an aliased interface (i.e. eth0:1)
+ TL;DR when kinit uses udp on an aliased interface, server responds with
+ the wrong source IP
On zesty:
a) install krb5-kdc and krb5-admin-server
sudo apt install krb5-kdc krb5-admin-server
when prompted, use EXAMPLE.ORG (all caps) as the default realm
when prompted, select your own IP for the KDC and the Admin servers
b) configure a new realm called EXAMPLE.ORG
sudo krb5_newrealm
use any password of your liking when prompted
c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and
with mandatory PREAUTH:
sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
d) extract the ubuntu principal keytab and time how long it takes to obtain a
ticket:
$ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
$ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real 0m0.022s
$ klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal:
[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121 filed for (b) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1683237 Title: krb5-user: kinit fails for OTP user when using kdc discovery via DNS Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: In Progress Status in krb5 package in Debian: Fix Released Bug description: Zesty is now affected, please see the debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 Would it be possible to get 1.15.1 (already released upstream) in zesty/zesty-updates? Thanks Jochen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS
This launchpad bug was "overloaded" and is talking about 3 issues: a) kinit fails for OTP user when using kdc discovery via DNS - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 - debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 - debian patch: 0013-Fix-udp_preference_limit-with-SRV-records.patch b) KDC/kadmind explicit wildcard listener addresses do not use pktinfo - no LP bug - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530 - debian: conflated into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 - debian patch: 0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch c) KDC/kadmind may fail to start on IPv4-only systems - no LP bug - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531 - debian: also conflated into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch I'll file separate bugs for (b) and (c) including test cases and then the SRU can address them too. I'm now working on a test case for (a). ** Bug watch added: krbdev.mit.edu/rt/ #8554 http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 ** Bug watch added: krbdev.mit.edu/rt/ #8530 http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530 ** Bug watch added: Debian Bug tracker #860767 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 ** Bug watch added: krbdev.mit.edu/rt/ #8531 http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1683237 Title: krb5-user: kinit fails for OTP user when using kdc discovery via DNS Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: In Progress Status in krb5 package in Debian: Fix Released Bug description: Zesty is now affected, please see the debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 Would it be possible to get 1.15.1 (already released upstream) in zesty/zesty-updates? Thanks Jochen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd
Now trying with @debug instead of @info Slight munging of output to make it diffable, then diff -u: --- v1.debug.trim 2017-05-03 20:28:07.78400 + +++ v2.debug.trim 2017-05-03 20:28:14.03200 + @@ -38,87 +38,6 @@ -> parse_args @ /build/sudo-XX/sudo-1.8.16/src/parse_args.c:172 -> get_net_ifs @ /build/sudo-XX/sudo-1.8.16/src/net_ifs.c:120 <- get_net_ifs @ /build/sudo-XX/sudo-1.8.16/src/net_ifs.c:205 := 3 -<- parse_args @ /build/sudo-XX/sudo-1.8.16/src/parse_args.c:512 := 8 -sudo_mode 8 --> sudo_load_plugins @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:283 --> sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:160 --> sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:112 --> sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:46 -<- sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:104 := 0 -<- sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:137 := true --> sudo_conf_debug_files_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:509 -<- sudo_conf_debug_files_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:535 := (nil) -<- sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:255 := true --> sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:160 --> sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:112 --> sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:46 -<- sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:104 := 0 -<- sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:137 := true --> sudo_conf_debug_files_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:509 -<- sudo_conf_debug_files_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:535 := (nil) -<- sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:255 := true -<- sudo_load_plugins @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:352 := true --> policy_open @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1231 --> format_plugin_settings @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1175 --> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44 -<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 := plugin_path=/usr/lib/sudo/sudoers.so -settings: progname=sudo --> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44 -<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 := progname=sudo -settings: network_addrs=10.0.0.230/255.255.255.0 :::::230/::::::: fe80::1:::/::::: --> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44 -<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 := network_addrs=10.0.0.230/255.255.255.0 :::::230/::::::: fe80::1:::/::::: -settings: plugin_dir=/usr/lib/sudo/ --> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44 -<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 := plugin_dir=/usr/lib/sudo/ -<- format_plugin_settings @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1217 := 0x -<- policy_open @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1261 := 1 --> init_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:121 --> pipe_nonblock @ /build/sudo-XX/sudo-1.8.16/src/exec.c:975 -<- pipe_nonblock @ /build/sudo-XX/sudo-1.8.16/src/exec.c:993 := 0 -<- init_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:154 --> policy_invalidate @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1350 -<- policy_invalidate @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1358 --> sudo_check_suid @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:828 -<- sudo_check_suid @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:872 --> save_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:64 -<- save_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:71 --> sudo_conf_read_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:562 --> sudo_secure_path @ /build/sudo-XX/sudo-1.8.16/lib/util/secure_path.c:43 -<- sudo_secure_path @ /build/sudo-XX/sudo-1.8.16/lib/util/secure_path.c:62 := 0 --> sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:55 -<- sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:118 := 40 --> sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:55 -<- sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:118 := 46 --> sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:55 -<- sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:117 := -1 -<- sudo_conf_read_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:651 := 1 --> get_user_info @
[Touch-packages] [Bug 1687129] Re: Needs to allow updates from the ESM archive
The publication changes are now live on esm.ubuntu.com: 500 https://esm.ubuntu.com/ubuntu/ precise/main i386 Packages release v=12.04,o=UbuntuESM,a=precise,n=precise,l=UbuntuESM,c=main origin esm.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1687129 Title: Needs to allow updates from the ESM archive Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades source package in Precise: Fix Committed Bug description: [SRU Justification] When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match. [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both. [Test case] 1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades' 2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to enable the ESM archive 3. run 'sudo apt-get update' 4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed. 6. install unattended-upgrades from -proposed. 7. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package. [Regression potential] Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+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 1434986] Re: Not working network connection after boot
Good news ! This bug seems to have disappeared since I upgraded my two PC toward Kubuntu 17.04. No problem for several weeks, after two years of problems... In fact, it seems that Kubuntu does not launch anymore dnsmasq. It does not appear in the results of the command: sudo /etc/init.d/network-manager status In my package manager, I see that the dnsmasq package is not installed, but the dnsmasq-base is. Thanks to anyone who solved that ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
Submitted patch in the bug for Debian, waiting for comments.
** Summary changed:
- DHCP exit hook for setting NTP servers doesn't work
+ DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
** Bug watch added: Debian Bug tracker #861769
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861769
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861769
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Status: In Progress => Confirmed
--
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/1685484
Title:
DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
Status in systemd package in Ubuntu:
Confirmed
Status in systemd package in Debian:
Unknown
Bug description:
I think it's regression for
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1578663 in
zesty.
1. NTP servers are send via DHCP and seen by NM:
$ nmcli con show connection1 | grep ntp
DHCP4.OPTION[30]: requested_ntp_servers = 1
DHCP4.OPTION[31]: ntp_servers = 80.50.231.226
217.96.29.26 212.160.106.226
2. timesyncd is using hardcoded default NTP server:
$ systemctl -n 200 status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
`-disable-with-time-daemon.conf
Active: active (running) since Sat 2017-04-22 13:12:23 CEST; 16min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 576 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
Memory: 1.5M
CPU: 20ms
CGroup: /system.slice/systemd-timesyncd.service
`-576 /lib/systemd/systemd-timesyncd
Apr 22 13:12:23 slodki systemd[1]: Starting Network Time Synchronization...
Apr 22 13:12:23 slodki systemd[1]: Started Network Time Synchronization.
Apr 22 13:12:53 slodki systemd-timesyncd[576]: Synchronized to time server
91.189.89.199:123 (ntp.ubuntu.com).
3. There are not other time sync deamons installed:
$ cat
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[Unit]
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService
$ ls -l /usr/sbin/{ntpd,openntpd,chronyd,VBoxService}
ls: cannot access '/usr/sbin/ntpd': No such file or directory
ls: cannot access '/usr/sbin/openntpd': No such file or directory
ls: cannot access '/usr/sbin/chronyd': No such file or directory
ls: cannot access '/usr/sbin/VBoxService': No such file or directory
4. There is only one default timesyncd.conf file with default values:
$ sudo find / -iname \*timesync\*
/etc/systemd/timesyncd.conf
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/dhcp/dhclient-exit-hooks.d/timesyncd
/usr/share/man/man5/timesyncd.conf.d.5.gz
/usr/share/man/man5/timesyncd.conf.5.gz
/usr/share/man/man8/systemd-timesyncd.8.gz
/usr/share/man/man8/systemd-timesyncd.service.8.gz
/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-6NwdRT
/lib/systemd/systemd-timesyncd
/lib/systemd/system/systemd-timesyncd.service
/lib/systemd/system/systemd-timesyncd.service.d
/var/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-jz0q47
$ cat /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.
[Time]
#NTP=
#FallbackNTP=ntp.ubuntu.com
5. DHCP hook installed as /etc/dhcp/dhclient-exit-hooks.d/timesyncd is
not working,
TIMESYNCD_CONF=/run/systemd/timesyncd.conf.d/01-dhclient.conf is not
created.
6. After manually executing steps from hook all works as expected:
$ sudo mkdir -p /run/systemd/timesyncd.conf.d/
$ sudo cat [Time]
> NTP=80.50.231.226 217.96.29.26 212.160.106.226
> EOF
$ sudo systemctl try-restart systemd-timesyncd.service
$ sudo systemctl status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time
[Touch-packages] [Bug 1688022] Re: text randomly scatters in documents
** Description changed: You newer know when your document or template created using ubuntu family fonts will crash. You can save a flawless document and after reopening it within minutes it's crashed. The text is scattered around and you can make it useful again only by changing the size of the font and/or changing font into anything outside the ubuntu family. Sometimes after you change fonts like that and then change the font back to ubuntu everything is ok. - Sometimes the problem can be temporarily solved by logging out from Windows user account/ ubuntu session. But that's not always true. Sometimes when a document is scattered in Open Office - opening it in Libre office shows perfect, flawless document. - It's affecting both: Libre and Open Office programs on both: Windows (XP, Vista,7, 10) and Linux (Ubuntu 12.04 LTS, 14.04 LTS as well as Mint and Xubuntu). It's a problem when creating, editing and reading a file but also when printing it. - The problem occurs when text is scattered - then the printout will be affected as well. When file looks ok - print will be fine. Used printers: HP laser and ink printers and OKI laser printers. + Sometimes the problem can be temporarily solved by logging out from Windows user account/ ubuntu session. But that's not always true. Sometimes when a document is scattered in Open Office - opening it in Libre office shows perfect, flawless document. + It's affecting both: Libre and Open Office programs on both: Windows (XP, Vista,7, 10) and Linux (Ubuntu 12.04 LTS, 14.04 LTS as well as Mint and Xubuntu). It's a problem when creating, editing and reading a file but also when printing it. + The problem occurs when text is scattered - then the printout will be affected as well. When file looks ok - print will be fine. Used printers: HP laser and ink printers and OKI laser printers. It would be nice to be sure how your document will look like in a moment. There are days and weeks without a single error. But then again there are days you can't work because documents simply won't come up without errors. This is the one and only font that makes things like that. I would really like to avoid changing it to another one as I use it in many work related tasks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1688022 Title: text randomly scatters in documents Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: You newer know when your document or template created using ubuntu family fonts will crash. You can save a flawless document and after reopening it within minutes it's crashed. The text is scattered around and you can make it useful again only by changing the size of the font and/or changing font into anything outside the ubuntu family. Sometimes after you change fonts like that and then change the font back to ubuntu everything is ok. Sometimes the problem can be temporarily solved by logging out from Windows user account/ ubuntu session. But that's not always true. Sometimes when a document is scattered in Open Office - opening it in Libre office shows perfect, flawless document. It's affecting both: Libre and Open Office programs on both: Windows (XP, Vista,7, 10) and Linux (Ubuntu 12.04 LTS, 14.04 LTS as well as Mint and Xubuntu). It's a problem when creating, editing and reading a file but also when printing it. The problem occurs when text is scattered - then the printout will be affected as well. When file looks ok - print will be fine. Used printers: HP laser and ink printers and OKI laser printers. It would be nice to be sure how your document will look like in a moment. There are days and weeks without a single error. But then again there are days you can't work because documents simply won't come up without errors. This is the one and only font that makes things like that. I would really like to avoid changing it to another one as I use it in many work related tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1688022/+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 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
** Bug watch added: Debian Bug tracker #537358 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537358 ** Also affects: network-manager (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537358 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/293139 Title: NetworkManager does not use dhclient-exit-hooks.d Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Triaged Status in network-manager package in Debian: Unknown Status in network-manager package in Fedora: Won't Fix Bug description: Binary package hint: network-manager I am running intrepid i386 and amd64 on a handful of systems. On every system, both upgraded and fresh installs, i use a script (first attachment) for updating a DNS record through DNSSEC. Using /etc/network/interfaces or invoking dhclient directly correctly updates the DNS record (second attachment). Using network-manager the DNS record update script doesn't seem to run (third attachment). On a laptop it is inconvenient to constantly reconfigure devices. For desktops, a workaround is to have a dhcp entry in /etc/network/interfaces for the relevant connection. As a side note, the script is designed to work with PPP ip-up.d as well. However, I haven't yet found a way to configure network-manager to dial up to 3G over a bluetooth connected modem. It may apply here similarily though. Wvdial works with the script. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/293139/+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 1380702] Re: No keyboards shortcuts in QT apps
Marking as verification-failed. For some reason d->nativeMenuBar equals -1 and menuBar::isNativeMenuBar() is returning false, so the patch is not working. I will prepare a new upload for 16.04 shortly. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: In Progress Status in Canonical System Image: In Progress Status in sni-qt: New Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Status in qtbase-opensource-src source package in Yakkety: Confirmed Bug description: Impact == This affects all Qt applications on Unity and other desktops which use global menu, either via appmenu-qt5 or via native implementation on Yakkety. Any shortcut is not working if the corresponding action is attached only to the menubar (i.e. and not also to the toolbar). It can be reproduced with almost any application by removing the toolbar (right- clicking on it and deselecting it). Test Case = * Open Qt Assistant; * Press Ctrl+T (this action is not on the toolbar). Expected: a new tab should be opened. Current result: nothing happens. In Yakkety the fix should work both with and without appmenu-qt5. Proposed Fix The proposed fix is a backport of the upstream fix at https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594. Actually just the qshortcut.cpp part would be sufficient, but the other parts make sure it plays fine together with https://cgit.kde.org /plasma-integration.git/commit/?id=aef74e97e2ed462a. Regression Potential The fix is in Zesty for 1½ months now (in upstream even longer), and so far nobody complained. People have verified that the fix works (see comment #63). To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
I have the same problem, I made a new install of Ubuntu Gnome 17.04 and discovered this. Not only Online Accounts but the Thunderbird doesn't work as well. I just found a temporary solution for GOA: https://askubuntu.com/questions/909716/cant-add-google-account-on- ubuntu-gnome-17-04/910180#910180 But not for Thunderbird yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnome-online-accounts package in Arch Linux: New Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd
Some additional info. I enabled sudo debugging by creating /etc/sudo.conf containing: Debug sudo /var/log/sudo-debug all@info Debug sudoers /var/log/sudoers-debug all@info With the newer (non-functioning) sudo, /var/log/sudo-debug contains: May 3 18:55:50 sudo[8003] comparing dev 34817 to /dev/pts/1: match! @ sudo_ttyname_dev() /build/sudo-40pSZP/sudo-1.8.16/src/ttyname.c:336 May 3 18:55:50 sudo[8003] settings: run_shell=true May 3 18:55:50 sudo[8003] settings: progname=sudo May 3 18:55:50 sudo[8003] settings: network_addrs=10.0.0.230/255.255.255.0 :::::230/::::::: fe80::1:::/::::: May 3 18:55:50 sudo[8003] settings: plugin_dir=/usr/lib/sudo/ May 3 18:55:51 sudo[8003] policy plugin returns 0 With the older (working) sudo, /var/log/sudo-debug contains: May 3 19:00:19 sudo[8746] comparing dev 34817 to /dev/pts/1: match! @ sudo_ttyname_dev() /build/sudo-g3ghsu/sudo-1.8.16/src/ttyname.c:336 May 3 19:00:19 sudo[8746] settings: run_shell=true May 3 19:00:19 sudo[8746] settings: progname=sudo May 3 19:00:19 sudo[8746] settings: network_addrs=10.0.0.230/255.255.255.0 :::::230/::::::: fe80::1:::/::::: May 3 19:00:19 sudo[8746] settings: plugin_dir=/usr/lib/sudo/ May 3 19:00:22 sudo[8746] policy plugin returns 1 May 3 19:00:22 sudo[8746] settings: run_shell=true May 3 19:00:22 sudo[8746] settings: progname=sudo May 3 19:00:22 sudo[8746] settings: network_addrs=10.0.0.230/255.255.255.0 :::::230/::::::: fe80::1:::/::::: May 3 19:00:22 sudo[8746] settings: plugin_dir=/usr/lib/sudo/ May 3 19:00:22 sudo[8746] command info from plugin: May 3 19:00:22 sudo[8746] 0: command=/bin/bash May 3 19:00:22 sudo[8746] 1: runas_uid=0 May 3 19:00:22 sudo[8746] 2: runas_gid=0 May 3 19:00:22 sudo[8746] 3: runas_groups=0 May 3 19:00:22 sudo[8746] 4: closefrom=3 May 3 19:00:22 sudo[8746] 5: set_utmp=true May 3 19:00:22 sudo[8746] 6: umask=022 May 3 19:00:22 sudo[8746] executed /bin/bash, pid 8754 May 3 19:00:22 sudo[8746] sudo_ev_add_v1: adding event 0x55e83b06c630 to base 0x55e83b07ea40 May 3 19:00:22 sudo[8746] sudo_ev_add_v1: adding event 0x55e83b078180 to base 0x55e83b07ea40 May 3 19:00:22 sudo[8746] signal pipe fd 10 May 3 19:00:22 sudo[8746] backchannel fd 5 May 3 19:00:22 sudo[8754] exec /bin/bash [/bin/bash] May 3 19:00:22 sudo[8746] sudo_ev_scan_impl: 1 fds ready May 3 19:00:22 sudo[8746] failed to read child status: EOF May 3 19:00:22 sudo[8746] sudo_ev_del_v1: removing event 0x55e83b078180 from base 0x55e83b07ea40 (/var/log/sudoers-debug is not created in either case) Note "policy plugin returns 0" in the first case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1688034 Title: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd Status in sudo package in Ubuntu: New Bug description: ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under CentOS 7) With sudo 1.8.16-0ubuntu1, everything is fine: brian.candler@api-dev:~$ sudo -s [sudo] password for brian.candler: root@api-dev:~# After update to 1.8.16-0ubuntu1.3, it no longer works: brian.candler@api-dev:~$ sudo -k brian.candler@api-dev:~$ sudo -s [sudo] password for brian.candler: brian.candler is not allowed to run sudo on api-dev.int.example.com. This incident will be reported. This is repeatable: downgrade sudo and it works again. Seems very likely related to change made as part of #1607666, which changes how sudo policies are matched, but has unexpected regression. --- Additional info --- The sudo policy in IPA is extremely simple. It has a single rule, which says: - applies to users in groups "system_administrators" and "security_administrators" - applies to any host - applies to any command In LDAP under ou=sudoers tree, the groups are flattened out: # system administrators on all hosts, sudoers, ipa.example.com dn: cn=system administrators on all hosts,ou=sudoers,dc=ipa,dc=example,dc=com sudoRunAsGroup: ALL objectClass: sudoRole objectClass: top sudoUser: brian.candler sudoUser: ... sudoUser: ... list more users sudoUser: ... sudoRunAsUser: ALL sudoCommand: ALL sudoHost: ALL cn: system administrators on all hosts Under cn=sudorules,cn=sudo it refers to the groups rather than the individuals: # 59ffb10a-9c61-11e6-b5b8-00163efd5284, sudorules, sudo, ipa.example.com dn: ipaUniqueID=59ffb10a-9c61-11e6-b5b8-00163efd5284,cn=sudorules,cn=sudo,dc=ipa,dc=example,dc=com ipaSudoRunAsUserCategory: all ipaSudoRunAsGroupCategory: all description: admins have full sudo access on any host they can ssh into cmdCategory: all
[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 Reopened as #1688018 ... it was requested in #1639776 ... just FYI to people finding this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1616742] Re: xdiagnose does nothing in Wayland
I don't know if you noticed, but the only flavors currently installing xdiagnose are Ubuntu (Desktop), Ubuntu Budgie and Ubuntu Kylin, so it's not a very popular utility among flavors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1616742 Title: xdiagnose does nothing in Wayland Status in ubuntu-meta package in Ubuntu: New Status in xdiagnose package in Ubuntu: New Bug description: What happens === 1. Try Ubuntu GNOME 16.10 Beta on a computer using open source graphics drivers (Intel is recommended). 2. On the login screen, select your user name. Before entering your password, click the gear button and choose "GNOME on Wayland". Enter your password and log in. 3. Try to run xdiagnose. 4. Nothing happens What I expected === 1. xdiagnose could be adapted to analyze and report issues with Wayland 2. xdiagnose could explain why it doesn't work on Wayland 3. Otherwise, it would be nice if xdiagnose wouldn't show up in the Activities Overview when Wayland is running but that's more complicated. (Maybe XDG_CURRENT_DESKTOP could be expanded to add Wayland as a string and xdiagnose.desktop could add NotShowIn=Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1616742/+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 1616742] Re: xdiagnose does nothing in Wayland
Timo, that sounds like a good idea. I'd like for us to stop installing xdiagnose by default. Because of how GNOME's Activities Overview works (big app icons without much distraction), xdiagnose would be very prominent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1616742 Title: xdiagnose does nothing in Wayland Status in ubuntu-meta package in Ubuntu: New Status in xdiagnose package in Ubuntu: New Bug description: What happens === 1. Try Ubuntu GNOME 16.10 Beta on a computer using open source graphics drivers (Intel is recommended). 2. On the login screen, select your user name. Before entering your password, click the gear button and choose "GNOME on Wayland". Enter your password and log in. 3. Try to run xdiagnose. 4. Nothing happens What I expected === 1. xdiagnose could be adapted to analyze and report issues with Wayland 2. xdiagnose could explain why it doesn't work on Wayland 3. Otherwise, it would be nice if xdiagnose wouldn't show up in the Activities Overview when Wayland is running but that's more complicated. (Maybe XDG_CURRENT_DESKTOP could be expanded to add Wayland as a string and xdiagnose.desktop could add NotShowIn=Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1616742/+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
