[Bug 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
** Description changed:
+ [Impact]
+ I/O error on blank Samsung SSD
+
+ [Test Case]
+ mkfs.ext4 on SSDs generates no I/O error
+
+ [Fix]
+ 435a05cf8c00 scsi: hisi_sas: Assign NCQ tag for all NCQ commands
+
+ [Regression Risk]
+ Patch restricted to hisi_sas driver.
+
+
"[Steps to Reproduce]
mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error
[Actual Results]
Io error when the first time of mkfs.ext4
[ 745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 776.034612] sas: trying to find task 0x9656953a
[ 776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
[ 776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 776.049635] sas: trying to find task 0x975f5cdf
[ 776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 776.062900] sas: ata5: end_device-4:0: cmd error handler
[ 776.062914] sas: ata5: end_device-4:0: dev error handler
[ 776.062918] sas: ata6: end_device-4:1: dev error handler
[ 776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action
0x6 frozen
[ 776.062924] sas: ata7: end_device-4:2: dev error handler
[ 776.062926] sas: ata8: end_device-4:3: dev error handler
[ 776.070548] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq
dma 512 out
- res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+ res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.090638] ata5.00: status: { DRDY }
[ 776.094290] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq
dma 512 out
- res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+ res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.114399] ata5.00: status: { DRDY }
[ 776.118051] ata5: hard resetting link
[ 776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
[ 776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
[ 776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
[ 776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
[ 776.451784] ata5.00: configured for UDMA/133
[ 776.456043] ata5.00: device reported invalid CHS sector 0
[ 776.461423] ata5.00: device reported invalid CHS sector 0
[ 776.466807] ata5: EH complete
[ 776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
[ 776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 806.740789] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 806.746604] sas: trying to find task 0x975f5cdf
[ 806.746605] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 806.754732] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 806.754733] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 806.761582] sas: trying to find task 0x9656953a
[ 806.761584] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 806.768002] sas: sas_scsi_find_task: task 0x9656953a is done
[ 806.768003] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 806.774852] sas: ata5: end_device-4:0: cmd error handler
[ 806.774864] sas: ata5: end_device-4:0: dev error handler
[ 806.774868] sas: ata6: end_device-4:1: dev error handler
[ 806.774870] ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6
frozen
[ 806.774873] ata5.00: failed command: SEND FPDMA QUEUED
[ 806.774875] sas: ata7: end_device-4:2: dev error handler
[ 806.774878] sas: ata8: end_device-4:3: dev error handler
[ 806.787013] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 0 ncq dma
512 out
- res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+ res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 806.801900] ata5.00: status: { DRDY }
[ 806.805554] ata5.00: failed command: SEND FPDMA QUEUED
[ 806.810674] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 1 ncq dma
512 out
- res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
+ res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 806.825582] ata5.00: status: { DRDY }
[ 806.829237] ata5: hard resetting link
[ 806.834445] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
[ 806.840856] hisi_sas_v3_hw
[Bug 1802013] Re: dulwich fails it's tests on s390x
** Changed in: dulwich (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802013 Title: dulwich fails it's tests on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dulwich/+bug/1802013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()
** Description changed: + [Impact] + Potential NULL-pointer dereference. + + [Test Case] + No known test case, but the issue is clear from code reading. + + [Fix] + 445ee2de112a scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() + + [Regression Risk] + Patch restricted to hisi_sas driver. + + [Bug Description] sas kasan test will produce this out bounds in sas module [Steps to Reproduce] 1) enbale this kasn 2) 3) [Actual Results] 30293.504016] sas: ata464: end_device-2:2:6: dev error handler [30293.504041] sas: ata465: end_device-2:2:7: dev error handler [30293.504059] sas: ata466: end_device-2:2:8: dev error handler [30293.538746] == [30293.550672] BUG: KASAN: slab-out-of-bounds in hisi_sas_debug_I_T_nexus_reset+0xcc/0x250 [30293.558642] Read of size 8 at addr b72e47233540 by task kworker/u193:3/79165 - [30293.566004] + [30293.566004] [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB O 5.1.0-rc1-g7a3fab8-dirty #1 [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B010.01 06/21/2019 [30293.586037] Workqueue: events_unbound async_run_entry_fn [30293.591331] Call trace: [30293.593770] dump_backtrace+0x0/0x1f8 [30293.597419] show_stack+0x14/0x20 [30293.600726] dump_stack+0xc4/0xfc [30293.604032] print_address_description+0x60/0x258 [30293.608716] kasan_report+0x164/0x1b8 [30293.612366] __asan_load8+0x84/0xa8 [30293.615842] hisi_sas_debug_I_T_nexus_reset+0xcc/0x250 [30293.620961] hisi_sas_I_T_nexus_reset+0xc4/0x170 [30293.625562] sas_ata_hard_reset+0x88/0x178 [30293.629646] ata_do_reset.constprop.6+0x80/0x90 [30293.634160] ata_eh_reset+0x71c/0x10e8 [30293.637897] ata_eh_recover+0x3d0/0x1a80 [30293.641804] ata_do_eh+0x50/0xd0 [30293.645020] ata_std_error_handler+0x78/0xa8 [30293.649273] ata_scsi_port_error_handler+0x288/0x930 [30293.654216] async_sas_ata_eh+0x68/0x90 [30293.658040] async_run_entry_fn+0x7c/0x1c0 [30293.662121] process_one_work+0x3c0/0x878 [30293.666115] worker_thread+0x70/0x670 [30293.669762] kthread+0x1b0/0x1b8 [30293.672978] ret_from_fork+0x10/0x18 - [30293.676541] + [30293.676541] [30293.678027] Allocated by task 16690: [30293.681593] __kasan_kmalloc.isra.0+0xd4/0x188 [30293.686018] kasan_kmalloc+0xc/0x18 [30293.689496] __kmalloc_node_track_caller+0x5c/0x98 [30293.694270] devm_kmalloc+0x44/0xb8 [30293.697746] hisi_sas_v3_probe+0x2ec/0x698 [30293.701828] local_pci_probe+0x74/0xf0 [30293.705562] work_for_cpu_fn+0x2c/0x48 [30293.709300] process_one_work+0x3c0/0x878 [30293.713294] worker_thread+0x400/0x670 [30293.717027] kthread+0x1b0/0x1b8 [30293.720241] ret_from_fork+0x10/0x18 - [30293.723801] + [30293.723801] [30293.725287] Freed by task 16227: [30293.728503] __kasan_slab_free+0x108/0x210 [30293.732583] kasan_slab_free+0x10/0x18 [30293.736318] kfree+0x74/0x150 [30293.739276] devres_free+0x34/0x48 [30293.742665] devres_release+0x38/0x60 [30293.746313] devm_pinctrl_put+0x34/0x58 [30293.750136] pinctrl_bind_pins+0x164/0x248 [30293.754214] really_probe+0xc0/0x3b0 [30293.75] driver_probe_device+0x70/0x138 [30293.761944] __device_attach_driver+0xc0/0xe0 [30293.766285] bus_for_each_drv+0xcc/0x150 [30293.770194] __device_attach+0x154/0x1c0 [30293.774101] device_initial_probe+0x10/0x18 [30293.778270] bus_probe_device+0xec/0x100 [30293.782178] device_add+0x5f8/0x9b8 [30293.785658] scsi_sysfs_add_sdev+0xa4/0x310 [30293.789825] scsi_probe_and_add_lun+0xe60/0x1240 [30293.794425] __scsi_scan_target+0x1ac/0x780 [30293.798591] scsi_scan_target+0x134/0x140 [30293.802586] sas_rphy_add+0x1fc/0x2c8 [30293.806234] sas_probe_devices+0x10c/0x1e8 [30293.810313] sas_discover_domain+0x754/0x998 [30293.814567] process_one_work+0x3c0/0x878 [30293.818560] worker_thread+0x70/0x670 [30293.822207] kthread+0x1b0/0x1b8 [30293.825423] ret_from_fork+0x10/0x18 - [30293.828983] + [30293.828983] [30293.830473] The buggy address belongs to the object at b72e47233480 [30293.830473] which belongs to the cache kmalloc-256 of size 256 [30293.842934] The buggy address is located 192 bytes inside of [30293.842934] 256-byte region [b72e47233480, b72e47233580) [30293.854617] The buggy address belongs to the page: [30293.859388] page:7edcb91c8cc0 count:1 mapcount:0 mapping:972e5f000200 index:0x0 [30293.867360] flags: 0xdfffe200(slab) [30293.871533] raw: dfffe200 7edcb915ca48 7edcb93fdc08 972e5f000200 [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() -- You received this bug notification because you are a member of Ubuntu
[Bug 1825778] Re: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825778 Title: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html ** Description changed: + [Impact] + Some SAS devices is gone when recovering + + [Test Case] + No known test case, stress test on SAS deivce. + + [Fix] + e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone and host reset + + [Regression Risk] + Patch restricted to hisi_sas driver. + + "[Steps to Reproduce] 1. Close all the PHYS; - 2. Inject error; - 3. Open one PHY; + 2. Inject error; + 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Fix the conflict between device gone and host reset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()
Patch has been sent for review https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Fix Released ** Changed in: kunpeng920/ubuntu-18.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-19.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-19.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-19.10 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-19.10 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: ubuntu-18.04.5 => None ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853992 Title: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
Patch has been sent for review https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Fix Released ** Changed in: kunpeng920/ubuntu-19.10 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-19.10 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-19.04 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-19.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-18.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920 Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853995 Title: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857307] Re: Wireless wouldn't turn on.
Hi, didn't find something directly related from above WMI events. Could you try following to kernel parameters sets separately: 1. "module_blacklist=wmi": this will disable wmi completely 2. "wmi.debug_event=1 wmi.debug_dump_wdg=1": this will enable wmi debug info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857307 Title: Wireless wouldn't turn on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
Patch has been sent for review ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Disco) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Eoan) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-19.10 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-19.10 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-19.04 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-19.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-18.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920 Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it
Patch has been sent for review ** Changed in: linux (Ubuntu Disco) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-19.04 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-18.04 Status: Triaged => In Progress ** Changed in: kunpeng920 Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it
https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764618] Re: python-API test in ubuntu_lxc will fail on X-kvm kernel
** No longer affects: ubuntu-kernel-tests ** Also affects: python3-lxc (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: python3-lxc (Ubuntu Xenial) Status: New => Confirmed ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764618 Title: python-API test in ubuntu_lxc will fail on X-kvm kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1764618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853992 Title: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853995 Title: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853992] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1853992 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853992 Title: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853995] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1853995 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Eoan) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853995 Title: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857418] Re: KDE Panel disappears after screen lock
This error was reproduced under kernel v5.5-rc3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857418 Title: KDE Panel disappears after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857589] [NEW] fatal error during installation
Public bug reported: fatal error during installation ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 26 00:14:39 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857589 Title: fatal error during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1857589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802013] Re: dulwich fails it's tests on s390x
** Bug watch added: Debian Bug tracker #913037 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913037 ** Also affects: dulwich (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913037 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802013 Title: dulwich fails it's tests on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dulwich/+bug/1802013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857584] [NEW] MySQL X protocol port 33060 listening on network by default
Public bug reported: MySQL Server 8.0 (on Eoan) binds to / listens on *:33060/tcp (MySQL X protocol) by default. For the classic shell it binds to localhost:3306/tcp only, as users will have gotten used to expect. This seems like a potentially dangerous change of defaults - users may not expect the service to start listening on an additional port (33060), and may not expect the MySQL X protocol server to bind to *. By default, no authentication should be possible from the network on the MySQL X protocol (I tested using the debian-sys-maint user and its password, as well as the root user, without a password). Some users may, however, assume that network access is not possible and choose to set simple mysql user passwords (for access from any host). Doing so would certainly involve negligent operation on the users' part, but this does not make it unlikely to happen. Ubuntu should (continue to) come with secure defaults, where services which are more likely to be used locally only (at least initially) should not listen on the network (anywhere but on localhost anyways) by default. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mysql-server 8.0.18-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 26 06:13:34 2019 InstallationDate: Installed on 2019-10-17 (69 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191016.5) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['binlog.01', 'private_key.pem', 'ibdata1', '#innodb_temp', 'mysql.ibd', 'ibtmp1', 'client-key.pem', 'undo_002', 'binlog.02', 'ca.pem', 'ib_logfile1', 'mysql', 'debian-5.7.flag', 'client-cert.pem', 'binlog.index', 'server-cert.pem', 'x.pid', 'undo_001', 'ib_buffer_pool', 'performance_schema', 'auto.cnf', 'public_key.pem', 'ca-key.pem', 'ib_logfile0', 'sys', 'binlog.03', 'server-key.pem'] PackageArchitecture: all SourcePackage: mysql-8.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857584 Title: MySQL X protocol port 33060 listening on network by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1857584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857235] Re: touchpad not working
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Hello Pratik, please try this tool: https://github.com/Cypresslin/alt_my_grub.git git clone https://github.com/Cypresslin/alt_my_grub.git cd alt_my_grub ./alt_my_grub And select the kernel that you want to boot with. After the newer kernel has been released in the future, you can upgrade your system and run this script with "./alt_my_grub -r" again to restore your current setting. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857235 Title: touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17682]
(In reply to hackmmn from comment #279) > Je ne comprend pas mieux l'anglais... J'suis perdu ici. La solution a t-elle > été apporté face à ce bug oui ou non ? Permettez-moi de citer Michael (commentaire 274): "Il n'y a aucune valeur à rouvrir ou à commenter ce bogue. Un bogue a été corrigé ici, donc par définition tous les problèmes qui existent dans Firefox 3.0 ou supérieur ne sont pas ce bogue. Dépôt de nouveaux bogues autonomes mentionnant un site spécifique et un problème spécifique est ce qui doit se produire, même si les symptômes sont similaires à ceux discutés ici (en fait, il y a déjà d'autres bogues déposés). " En bref, le problème auquel ce bug fait référence est corrigé. MAIS, un problème peut toujours exister, donc un nouveau bogue doit être ouvert (et très probablement déjà). Je pense que c'est la raison pour laquelle Bruce et al suivent désormais le bogue 521204 (commentaire 277). J'avais l'habitude de faire beaucoup de commentaires sur ces pages de bogues, mais j'ai appris qu'il est généralement préférable de se pencher en arrière et de regarder les professionnels travaillant réellement sur le problème. Parfois, cela prend du temps car la plupart d'entre eux ont des emplois de jour et des familles, nous devons donc être patients. Non, même après quatre ans de français, je ne suis - malheureusement - pas au courant. J'utilise Google Translate (translate.google.com/). Joyeux Noël. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17682 Title: No more than one page is printed To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/17682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17682]
Je ne comprend pas mieux l'anglais... J'suis perdu ici. La solution a t-elle été apporté face à ce bug oui ou non ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17682 Title: No more than one page is printed To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/17682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17682]
Merci :D ! Joyeux noël à toi également ;) ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17682 Title: No more than one page is printed To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/17682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17682]
[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug is a regression, but please revert this change in case of error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17682 Title: No more than one page is printed To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/17682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857552] Re: [81NX, Realtek ALC285, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857552 Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752994] Re: Xubuntu: Check Disc for Defects Useless
[Expired for xubuntu-artwork (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xubuntu-artwork (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752994 Title: Xubuntu: Check Disc for Defects Useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/752994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842173] Re: ubuntu 18.04.3 install /dev/sda1 could not boot up
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842173 Title: ubuntu 18.04.3 install /dev/sda1 could not boot up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849913] Re: urget resume from s2idle deep error
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849913 Title: urget resume from s2idle deep error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Done. https://gitlab.gnome.org/GNOME/nautilus/issues/1323 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1323 https://gitlab.gnome.org/GNOME/nautilus/issues/1323 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1836960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757823] Re: Please port your package away from Qt 4
** Changed in: qjoypad (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757823 Title: Please port your package away from Qt 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qjoypad/+bug/1757823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857570] [NEW] Delete cluster successfully from the ui but the cluster is still exist
Public bug reported:
1、When I delete a cluster from the ui,it responses a successful message like
"成功: Deleted cluster: cluster."
2、When I refresh the ui,the deleted cluster appears again
3、Error messages for /var/log/messages.There is an execption raised when the
magnum-conductor try to call is_octavia_enabled
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: Failed validating 'type'
in
schema['properties']['identity']['properties']['password']['properties']['user']['properties']['password']:
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: {'type': 'string'}
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: On
instance['identity']['password']['user']['password']:
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: None (HTTP 400)
(Request-ID: req-84ad63c5-8b35-4dc6-b08b-a5556fa0d478)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone Traceback (most recent call last):
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/magnum/common/keystone.py", line 318, in
is_octavia_enabled
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone octavia_svc =
keystone.client.services.list(type='load-balancer')
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneclient/v3/services.py", line 93, in
list
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone **kwargs)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneclient/base.py", line 86, in func
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone return f(*args, **new_kwargs)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneclient/base.py", line 448, in list
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone list_resp = self._list(url_query,
self.collection_key)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneclient/base.py", line 141, in _list
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone resp, body = self.client.get(url,
**kwargs)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 386, in get
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone return self.request(url, 'GET', **kwargs)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 545, in
request
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone resp = super(LegacyJsonAdapter,
self).request(*args, **kwargs)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 248, in
request
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone return self.session.request(url, method,
**kwargs)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneauth1/session.py", line 747, in
request
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone auth_headers =
self.get_auth_headers(auth)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneauth1/session.py", line 1158, in
get_auth_headers
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone return auth.get_headers(self, **kwargs)
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone File
"/usr/lib/python2.7/site-packages/keystoneauth1/plugin.py", line 95, in
get_headers
Dec 25 05:17:28 openstack-magnum-k8s magnum-conductor: 2019-12-25 05:17:28.587
94972 ERROR magnum.common.keystone
[Bug 1857566] [NEW] Gimp crashed when I was using transformation tool
Public bug reported: I was rotating a layer and changing the preview opacity by clicking with the mouse. I was working on a relatively big image at 300dpi. Every time I rotate the layer it crashed if the preview opacity is below than 100%. But it don't crash if the (preview) opacity is 100% or the preview is off. The error is persistent. I'm on kubuntu 19.04 with 6gb of ram. Intel Core i3 processor. Nvidia Gforce GT 610. here a capture of the error: https://youtu.be/eRrl3_do_jo Atached a log file ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Log" https://bugs.launchpad.net/bugs/1857566/+attachment/5315403/+files/Gimp%20crashed%20when%20I%20was%20using%20transformation%20tool -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857566 Title: Gimp crashed when I was using transformation tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1857566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857521] Re: heap-buffer-overflow detected in function process_DQT of jpgqguess.c when running jhead 3.04
** Information type changed from Private Security to Public Security ** Information type changed from Public Security to Private Security ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857521 Title: heap-buffer-overflow detected in function process_DQT of jpgqguess.c when running jhead 3.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jhead/+bug/1857521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857519] Re: Segmentation fault detected in function Get32s of exif.c when running jhead 3.04
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857519 Title: Segmentation fault detected in function Get32s of exif.c when running jhead 3.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jhead/+bug/1857519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Hi Ivanak, while awaiting new kernel, browsing and testing with kernel 5.x, is working in dell xps 9333, here is reference how to enable https://wiki.ubuntu.com/Kernel/LTSEnablementStack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857565] [NEW] package ubuntu-business-defaults 38 failed to install/upgrade: installed ubuntu-business-defaults package post-installation script subprocess returned error exit status 127
Public bug reported: not install package ProblemType: Package DistroRelease: Ubuntu 19.10 Package: ubuntu-business-defaults 38 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 AptOrdering: libiscsi7:amd64: Install NULL: ConfigurePending NULL: RemovePending NULL: ConfigurePending Architecture: amd64 Date: Thu Dec 26 00:02:08 2019 ErrorMessage: installed ubuntu-business-defaults package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2019-12-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: ubuntu-business-defaults Title: package ubuntu-business-defaults 38 failed to install/upgrade: installed ubuntu-business-defaults package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-business-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857565 Title: package ubuntu-business-defaults 38 failed to install/upgrade: installed ubuntu-business-defaults package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-business-defaults/+bug/1857565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856534] Re: Touchpad not working after update
Bug reports aren't for support, for support options please refer to https://discourse.ubuntu.com/t/finding-help/709 I believe kernel linux-image-4.15.0-73-generic (currently in proposed) will move to 'main' on January 5, 2020. For enabling proposed (suggested in comment #13 and others in the bug report 1854798 I believe this is a duplicate of, which will let you use it now) see https://help.ubuntu.com/community/Repositories/Ubuntu and https://wiki.ubuntu.com/Testing/EnableProposed If it solves your issue (best if done before it's live for everyone Jan 5 probably) PLEASE report back here that here it works. If it doesn't work, then it may be you have a unique situation that may need attention its not getting due likely duplicate. Please report that here too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856534 Title: Touchpad not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1857547] [NEW] fmtutil fails with default LANG=C.UTF-8, needs LANG=C
On Wed, 25 Dec 2019, Török Edwin wrote: > Luatex fmtutil fails when LANG=C.UTF-8 (the default): > ``` > > fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/eplain.fmt installed. > fmtutil [ERROR]: running `luatex -ini -jobname=luatex -progname=luatex > luatex.ini fmtutil [ERROR]: return error due to options --strict I cannot reproduce this on Debian: $ export LANG=C.UTF-8 $ fmtutil-sys --byfmt lualatex fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /usr/share/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: writing formats under /var/lib/texmf/web2c fmtutil [INFO]: --- remaking lualatex with luatex fmtutil: running `luatex -ini -jobname=lualatex -progname=lualatex lualatex.ini' ... This is LuaTeX, Version 1.10.0 (TeX Live 2019/Debian) (INITEX) restricted system commands enabled. .. Transcript written on lualatex.log. fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/luatex/lualatex.log fmtutil [INFO]: /var/lib/texmf/web2c/luatex/lualatex.fmt installed. fmtutil [INFO]: disabled formats: 1 fmtutil [INFO]: successfully rebuilt formats: 1 fmtutil [INFO]: not selected formats: 52 fmtutil [INFO]: total formats: 54 fmtutil [INFO]: exiting with status 0 $ Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857547 Title: fmtutil fails with default LANG=C.UTF-8, needs LANG=C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1857547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104617] Re: CMI8738 5.1 center speaker is mute
CMI8738 is not well-supported by alsa. Running with a center channel volume issue (center volume constant, whatever the master volume). I found out that master volume worked only for front/rear channel, not center which stick to its initial value. Pulseaudio volume for separate channel are not effectless. amixer set no gauge for center/lfe, hence impossible to change it. Seems that with this chip, when in 5.1 mic is not available and Mic-in and center/lfe is on the same control. I don't know if alsa is wrong or if CMI8738 is just a crap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/104617 Title: CMI8738 5.1 center speaker is mute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/104617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857271] Re: Focal 440.44-0ubuntu1 PRIME Sync not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857271 Title: Focal 440.44-0ubuntu1 PRIME Sync not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1857271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857563] [NEW] Kubuntu Installation does not allow to set password for Encrypted Volume
Public bug reported: Installing Kubuntu allows to partition the system manually choosing "Manual" in the disk setup dialog. There you can add a new partition. When choosing the type "Volume for Encryption", nothing really happens. Normally the installer should ask for the password for the encrypted volume and then mount it, so it can be used as installation target. Instead it just shows as a crypto partition but the user cannot do anything with it. Steps to reproduce: - Use Kubuntu 19.10 installer on usb stick - in disk setup choose manual (for manual partitioning) - create a new partition with type "Volume for Encryption" - What happens: Volume is created but user cannot set password or configure the volume's mount point - Expected: Here you should somehow be able to enter the volume password for the new volume, then it should be mounted and then you can change the mount point for the installation Importance: this does block a user from using the ui installer to setup an encrypted dual boot. Workaround: use ubuntu installer to setup encrypted system and then install kubuntu-desktop PS: Not sure if this is the right place to report ** Affects: kde-workspace (Ubuntu) Importance: Undecided Status: New ** Description changed: - Installing Kubuntu during disk setup choosing the manual setup does - allow to set the partition "Volume for Encryption". + Installing Kubuntu allows to partition the system manually choosing "Manual" in the disk setup dialog. + There you can add a new partition. When choosing the type "Volume for Encryption", nothing really happens. Normally the installer should ask for the password for the encrypted volume and then mount it, so it can be used as installation target. Instead it just shows as a crypto partition but the user cannot do anything with it. - Normally the installer should ask for the password for the encrypted - volume and then mount it, so it can be used as installation target. - - Steps to reproduce: - - Use Kubuntu 19.10 installer on usb stick - - in disk setup choose manual (for manual partitioning) - - create a new partition with type "Volume for Encryption" - - What happens: Volume is created but user cannot set password or configure the volume's mount point - - Expected: Here you should somehow be able to enter the volume password for the new volume, then it should be mounted and then you can change the mount point for the installation + Steps to reproduce: + - Use Kubuntu 19.10 installer on usb stick + - in disk setup choose manual (for manual partitioning) + - create a new partition with type "Volume for Encryption" + - What happens: Volume is created but user cannot set password or configure the volume's mount point + - Expected: Here you should somehow be able to enter the volume password for the new volume, then it should be mounted and then you can change the mount point for the installation Importance: this does block a user from using the ui installer to setup an encrypted dual boot. Workaround: use ubuntu installer to setup encrypted system and then install kubuntu-desktop - PS: Not sure if this is the right place to report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857563 Title: Kubuntu Installation does not allow to set password for Encrypted Volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1857563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
@ivanak Bug reports aren't for support, for support options please refer to https://discourse.ubuntu.com/t/finding-help/709 For using proposed (comment #13 and others) see https://help.ubuntu.com/community/Repositories/Ubuntu and https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855435] Re: Error: Cannot find module 'resolve-cwd'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: node-webpack (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855435 Title: Error: Cannot find module 'resolve-cwd' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-webpack/+bug/1855435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821632] Re: dmidecode causing system crash
** Changed in: dmidecode (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821632 Title: dmidecode causing system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Hi all, can someone tell me how to fix this issue, its getting annoying. Is it going to be new update on this, im not sure about using the ppa. Is there any other safety way to be patched ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857233] Re: GIMP crashed with a fatal error: fatal error: Segmentation fault
same problem on a different hardware with ISO: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191223) corrado@corrado-HP-p4-ff-1223:~$ inxi -Fx System:Host: corrado-HP-p4-ff-1223 Kernel: 5.3.0-24-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 9.9 Wh condition: 16.5/16.5 Wh (100%) model: 13-42 OA03031 status: Charging CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 2474 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 2469 2: 2488 3: 2395 4: 2395 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.5 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.2.4 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.3.0-24-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 IF: enp8s0 state: up speed: 100 Mbps duplex: full mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 IF: wlp9s0f0 state: down mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 689.33 GiB used: 5.28 GiB (0.8%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB ID-2: /dev/sdb vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB Partition: ID-1: / size: 31.25 GiB used: 5.27 GiB (16.9%) fs: ext4 dev: /dev/sda4 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 67.0 C mobo: 67.0 C Fan Speeds (RPM): N/A Info: Processes: 210 Uptime: 15m Memory: 3.78 GiB used: 1.43 GiB (37.9%) Init: systemd runlevel: 5 Compilers: gcc: 9.2.1 Shell: bash v: 5.0.11 inxi: 3.0.37 corrado@corrado-HP-p4-ff-1223:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857233 Title: GIMP crashed with a fatal error: fatal error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1857233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796081] Re: dpkg frontend locking
I think it can be made to work. I do not know how apt/dpkg is
implemented, but I made an example by Bash:
script.sh file:
#!/bin/bash
#
exec {var}>/tmp/lock
flock -n $var || { echo already locked; exit 1; }
LOCK= /path/to/subscript.sh # edit this path
subscript.sh file:
#!/bin/bash
#
[[ -v LOCK ]] && { kill $PPID; sleep 3; } # kill the caller
exec {var}>/tmp/lock
flock -n $var && echo was not locked || echo was locked
The subscript.sh above kills the caller (if LOCK variable is set in its
environment). The subscript shows the lock is set even thereafter until the
subscript finishes.
Anyway I am missing something: Even if I lock /var/lib/dpkg/lock or
/var/lib/dpkg/lock-frontend this way (instead of locking /tmp/lock),
that does not prevent installing a package by apt install or dpkg
--install. But if I run Synaptic package manager by pkexec
"/usr/sbin/synaptic", it locks the files and prevents installing by apt
or dpkg from outside.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796081
Title:
dpkg frontend locking
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1796081/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857549] Re: no packages found matching ubuntu-release-upgrader-core
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857549 Title: no packages found matching ubuntu-release-upgrader-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1857549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857544] Re: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. You seem to have an invalid configuration setting in your /etc/samba/smb.conf: $ testparm ./smb.conf WARNING: The "syslog" option is deprecated WARNING: Ignoring invalid value 'server' for parameter 'security' Load smb config files from ./smb.conf WARNING: The "syslog" option is deprecated WARNING: Ignoring invalid value 'server' for parameter 'security' Error loading services. The "security" parameter can only have the values "auto", "user", "domain" or "ads". The reason you are seeing this error just now is probably because a samba update triggers a service restart. The other reason your attempts at purging samba didn't help is because the config file /etc/samba/smb.conf is generated by the samba-common package, not samba. I suggest to fix your smb.conf and then try: sudo apt update sudo apt -f install Or purge samba-common, which will remove smb.conf, and start over. ** Changed in: samba (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1857544 Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1857544/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1857544] Re: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. You seem to have an invalid configuration setting in your /etc/samba/smb.conf: $ testparm ./smb.conf WARNING: The "syslog" option is deprecated WARNING: Ignoring invalid value 'server' for parameter 'security' Load smb config files from ./smb.conf WARNING: The "syslog" option is deprecated WARNING: Ignoring invalid value 'server' for parameter 'security' Error loading services. The "security" parameter can only have the values "auto", "user", "domain" or "ads". The reason you are seeing this error just now is probably because a samba update triggers a service restart. The other reason your attempts at purging samba didn't help is because the config file /etc/samba/smb.conf is generated by the samba-common package, not samba. I suggest to fix your smb.conf and then try: sudo apt update sudo apt -f install Or purge samba-common, which will remove smb.conf, and start over. ** Changed in: samba (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857544 Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1857544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838154] Re: Something hinders XFCE performance. >:]
*** This bug is a duplicate of bug 1839716 *** https://bugs.launchpad.net/bugs/1839716 Or counterintuitively scrollbar cannot be graphically most demanding thing ever. >:] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838154 Title: Something hinders XFCE performance. >:] To manage notifications about this bug go to: https://bugs.launchpad.net/wayland/+bug/1838154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838154] Re: Something hinders XFCE performance. >:]
*** This bug is a duplicate of bug 1839716 *** https://bugs.launchpad.net/bugs/1839716 New line speed, I dunno where. https://bugzilla.redhat.com/show_bug.cgi?id=1674486#c65 >:] (basically difference should be amazing, something blows up in scrollbar logic which is unexpected considering this is 2019) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838154 Title: Something hinders XFCE performance. >:] To manage notifications about this bug go to: https://bugs.launchpad.net/wayland/+bug/1838154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857553] [NEW] 18.04 Live Failed to install
Public bug reported: 18.04 Live Failed to install. Seems to think there is problem with CD but the install is from a USB Stick. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 Date: Wed Dec 25 13:34:42 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu ** Attachment added: "only syslog or partman. both cannot be attached." https://bugs.launchpad.net/bugs/1857553/+attachment/5315384/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857553 Title: 18.04 Live Failed to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558899] Re: Recent recipe version of FreeFont were failed to build
Sorry for the very late reply. Just to inform you, i don't do devel snapshots of freefont anymore at all, so this bug can be closed. ** Changed in: fonts-freefont (Ubuntu) Assignee: (unassigned) => DNS (dns) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558899 Title: Recent recipe version of FreeFont were failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1558899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856871] Re: i/o error if next unused loop device is queried
so 2 things come to my mind right now Does the kernel (loop driver) do the right thing by not clear/reset the loop device' stats after the umount/detached operation ? and/or Does parted need to be smarter and not only based is detection on stat() to assume if its a legit device or not to be probed ? Let's circle back on Jan 2020. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856871 Title: i/o error if next unused loop device is queried To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856871] Re: i/o error if next unused loop device is queried
so 2 things come to my mind right now Does the kernel (loop driver) do the right thing by not clear/reset the loop device' stats after the umount/detached operation ? and/or Does parted need to smarter and not only based is detection only on stat() ? Let's circle back on Jan 2020. ** Also affects: parted (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856871 Title: i/o error if next unused loop device is queried To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857552] [NEW] [81NX, Realtek ALC285, Speaker, Internal] No sound at all
Public bug reported: In dual boot machine (lenove S740 laptop) sound is fine on windows side. Headphones work on linux side, but there is no sound at all from speakers on the ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 20:14:17 2019 InstallationDate: Installed on 2019-12-22 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1126 F pulseaudio hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BKCN20WW(V1.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBKCN20WW(V1.02):bd07/15/2019:svnLENOVO:pn81NX:pvrLenovoYogaS740-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaS740-15IRH: dmi.product.family: Yoga S740-15IRH dmi.product.name: 81NX dmi.product.sku: LENOVO_MT_81NX_BU_idea_FM_Yoga S740-15IRH dmi.product.version: Lenovo Yoga S740-15IRH dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857552 Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856871] Re: i/o error if next unused loop device is queried
Ok so in fact the inconsistency is due to "parted" that will try to
probe devices iff the given block device return informations from
stat(), regardless if the block device is available or not.
Seems like the only trigger/criteria is the stat() return. Since the
loop device stat doesn't clear/reset once umounted/detacted, then parted
assume it can go ahead and probe it assuming it is a legit device.
# libparted/arch/linux.c
618 static int
619 _device_stat (PedDevice* dev, struct stat * dev_stat)
620 {
621 PED_ASSERT (dev != NULL);
622 PED_ASSERT (!dev->external_mode);
623
624 while (1) {
625 if (!stat (dev->path, dev_stat)) {
626 return 1;
627 } else {
628 if (ped_exception_throw (
629 PED_EXCEPTION_ERROR,
630 PED_EXCEPTION_RETRY_CANCEL,
631 _("Could not stat device %s - %s."),
632 dev->path,
633 strerror (errno))
634 != PED_EXCEPTION_RETRY)
635 return 0;
636 }
637 }
638 }
Example:
# parted -s $(losetup -f) unit s print
Warning: Error fsyncing/closing /dev/loop18: Input/output error
# stat $(losetup -f)
File: /dev/loop18
Size: 0 Blocks: 0 IO Block: 4096 block special file
Device: 6h/6d Inode: 509 Links: 1 Device type: 7,12
Access: (0660/brw-rw) Uid: (0/root) Gid: (6/disk)
Access: 2019-12-25 13:05:15.543108777 -0500
Modify: 2019-12-25 13:05:15.543108777 -0500
Change: 2019-12-25 13:05:15.543108777 -0500
Birth: -
# parted -s /dev/loop19 unit s print
Error: Could not stat device /dev/loop19 - No such file or directory.
# stat /dev/loop19
stat: cannot stat '/dev/loop19': No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856871
Title:
i/o error if next unused loop device is queried
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850003] Re: /etc/grub.d/10_linux_zfs doesn't skip non-linux zpools
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850003 Title: /etc/grub.d/10_linux_zfs doesn't skip non-linux zpools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1850003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutt
Thanks Daniel. I installed the following packages: libjpeg-turbo8-dbg/eoan,now 2.0.3-0ubuntu1 amd64 [installed] libjpeg8-dbg/eoan,now 8c-2ubuntu8 amd64 [installed] libnvidia-gl-435 does not have any debugging symbols package available. Next time it crashes, I will transmit a better report. That said, I fail to understand how you determined that the libjpeg symbols are required. Searching through the crash report, I only see the following below. How, as a casual user, can I figure out which package I should install to provide a better debugging experience? Thanks again. $ fgrep libjpeg _usr_bin_gnome-shell.1000.crash libjpeg-turbo8 2.0.3-0ubuntu1 libjpeg8 8c-2ubuntu8 7f33dc2b5000-7f33dc2b9000 r--p fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2 7f33dc2b9000-7f33dc2fd000 r-xp 4000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2 7f33dc2fd000-7f33dc337000 r--p 00048000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2 7f33dc337000-7f33dc338000 ---p 00082000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2 7f33dc338000-7f33dc339000 r--p 00082000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2 7f33dc339000-7f33dc33a000 rw-p 00083000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857550] [NEW] Appears as failed connection to internet
Public bug reported: Disappears after debugging procedure and reporting, sometimes with a reboot.Thanks for help ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 25 12:18:23 2019 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1239 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (365 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857550 Title: Appears as failed connection to internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1857550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
Upstream bugreport: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2=2915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676763 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857549] [NEW] no packages found matching ubuntu-release-upgrader-core
Public bug reported: Software updater states upgrade from 18.04 to 19.04 available but would not complete action. See below: Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done root@karl-Inspiron-3521:/home/karl# ppa-purge Command 'ppa-purge' not found, but can be installed with: apt install ppa-purge root@karl-Inspiron-3521:/home/karl# apt install ppa-purge Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: aptitude The following NEW packages will be installed ppa-purge 0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade. Need to get 6,312 B of archives. After this operation, 24.6 kB of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 ppa-purge all 0.2.8+bzr63 [6,312 B] Fetched 6,312 B in 0s (32.1 kB/s) Selecting previously unselected package ppa-purge. (Reading database ... 5278 files and directories currently installed.) Preparing to unpack .../ppa-purge_0.2.8+bzr63_all.deb ... Unpacking ppa-purge (0.2.8+bzr63) ... Setting up ppa-purge (0.2.8+bzr63) ... root@karl-Inspiron-3521:/home/karl# ubuntu-bug ubuntu-release-upgrader-core dpkg-query: no packages found matching ubuntu-release-upgrader-core comm: /var/log/dmesg: No such file or directory root@karl-Inspiron-3521:/home/karl# [6011:6011:1225/160436.017261:ERROR:sandbox_linux.cc(368)] InitializeSandbox() called with multiple threads in process gpu-process. [5974:5993:1225/160436.066023:ERROR:browser_process_sub_thread.cc(217)] Waited 13 ms for network service Opening in existing browser session. Re package version I got this: root@karl-Inspiron-3521:/home/karl# apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 Architecture: amd64 CrashDB: ubuntu Date: Wed Dec 25 16:03:30 2019 InstallationDate: Installed on 2018-11-18 (402 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2019-12-25 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857549 Title: no packages found matching ubuntu-release-upgrader-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857547] [NEW] fmtutil fails with default LANG=C.UTF-8, needs LANG=C
Public bug reported: Luatex fmtutil fails when LANG=C.UTF-8 (the default): ``` fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/eplain.fmt installed. fmtutil [ERROR]: running `luatex -ini -jobname=luatex -progname=luatex luatex.ini https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872012 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: texlive-luatex 2019.20190710-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: LXQt Date: Wed Dec 25 16:15:51 2019 InstallationDate: Installed on 2019-09-01 (115 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857547 Title: fmtutil fails with default LANG=C.UTF-8, needs LANG=C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1857547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857545] Re: Multi-monitor fullscreen - wrong monitor selection
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1857545/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857545 Title: Multi-monitor fullscreen - wrong monitor selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hello, I suffer from the same issue, I also have HP Zbook 15 G6 with Ubuntu 19.10. I installed the latest kernel v5.5-rc3 through ukuu utility. Now, I do not have any sound (nor mic, nor speakers). Here is the output from dmesg: ``` [0.00] Linux version 5.5.0-050500rc3-generic (kernel@kathleen) (gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)) #201912230230 SMP Mon Dec 23 02:33:07 UTC 2019 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500rc3-generic root=UUID=68ba5bbe-cf0c-4d88-8325-9a95b3cceb05 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0005bfff] usable [0.00] BIOS-e820: [mem 0x0005c000-0x0005cfff] reserved [0.00] BIOS-e820: [mem 0x0005d000-0x0009] usable [0.00] BIOS-e820: [mem 0x000a-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x76789fff] usable [0.00] BIOS-e820: [mem 0x7678a000-0x76c89fff] type 20 [0.00] BIOS-e820: [mem 0x76c8a000-0x77a6dfff] reserved [0.00] BIOS-e820: [mem 0x77a6e000-0x77c6dfff] ACPI NVS [0.00] BIOS-e820: [mem 0x77c6e000-0x77d0efff] ACPI data [0.00] BIOS-e820: [mem 0x77d0f000-0x77d0] usable [0.00] BIOS-e820: [mem 0x77d1-0x7e7f] reserved [0.00] BIOS-e820: [mem 0xfe01-0xfe010fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00047d7f] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.60 by HP [0.00] efi: ACPI=0x77d0e000 ACPI 2.0=0x77d0e014 ESRT=0x76f54b98 TPMFinalLog=0x77bf6000 SMBIOS=0x76f53000 MEMATTR=0x72e93018 MPS=0x771d [0.00] SMBIOS 3.1 present. [0.00] DMI: HP HP ZBook 15 G6/860F, BIOS R92 Ver. 01.03.04 11/06/2019 [0.00] tsc: Detected 2600.000 MHz processor [0.001922] tsc: Detected 2599.992 MHz TSC [0.001922] e820: update [mem 0x-0x0fff] usable ==> reserved [0.001924] e820: remove [mem 0x000a-0x000f] usable [0.001929] last_pfn = 0x47d800 max_arch_pfn = 0x4 [0.001932] MTRR default type: write-back [0.001933] MTRR fixed ranges enabled: [0.001934] 0-9 write-back [0.001935] A-B uncachable [0.001936] C-F write-protect [0.001936] MTRR variable ranges enabled: [0.001938] 0 base 008000 mask 7F8000 uncachable [0.001939] 1 base 007C00 mask 7FFC00 uncachable [0.001940] 2 base 20 mask 60 uncachable [0.001941] 3 base 10 mask 70 uncachable [0.001941] 4 base 08 mask 78 uncachable [0.001942] 5 base 40 mask 40 uncachable [0.001943] 6 disabled [0.001943] 7 disabled [0.001944] 8 disabled [0.001944] 9 disabled [0.002421] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.002603] last_pfn = 0x77d10 max_arch_pfn = 0x4 [0.010888] esrt: Reserving ESRT space from 0x76f54b98 to 0x76f54bf8. [0.010899] check: Scanning 1 areas for low memory corruption [0.010903] Using GB pages for direct mapping [0.010905] BRK [0x3c3a01000, 0x3c3a01fff] PGTABLE [0.010907] BRK [0x3c3a02000, 0x3c3a02fff] PGTABLE [0.010908] BRK [0x3c3a03000, 0x3c3a03fff] PGTABLE [0.010938] BRK [0x3c3a04000, 0x3c3a04fff] PGTABLE [0.010940] BRK [0x3c3a05000, 0x3c3a05fff] PGTABLE [0.011032] BRK [0x3c3a06000, 0x3c3a06fff] PGTABLE [0.011056] BRK [0x3c3a07000, 0x3c3a07fff] PGTABLE [0.011085] BRK [0x3c3a08000, 0x3c3a08fff] PGTABLE [0.011129] Secure boot could not be determined [0.011130] RAMDISK: [mem 0x2ef89000-0x337bbfff] [0.011145] ACPI: Early table checksum verification disabled [
[Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
I have tried installing the package from Buster. That has resolved the
crash - the program ended gracefully. However the underlying problem is
still there - devices without interface 0 will not work. I think this is
present in upstream as well.
USB_ModeSwitch log from Wed Dec 25 16:35:30 CET 2019
Use global config file: /etc/usb_modeswitch.conf
Raw parameters: {--switch-mode} {1-11}
Use top device dir /sys/bus/usb/devices/1-11
Check class of first interface ...
No access to interface 0. Exit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676763
Title:
usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
EDIT: the null-pointer bug only exists in Ubuntu, the interface error bug may exist in upstream as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676763 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
Hmmm, it seems that this bug exists *only* in Ubuntu and not in Debian.
Ubuntu source package contains a patch that rewrites the
usb_modeswitch_dispatcher program from Tcl to C. While there must have
been good reasons to do this, there is at least one more bug in the
rewritten version.
On line 422 in file usb_modeswitch_dispatcher.c there is an assignment
of NULL to a char pointer. This pointer is later passed to printf when
forming the usb_modeswitch command. Therefore there should be strdup("")
instead of null pointer, as now usb_modeswitch is launched literally
with "(null)" argument produced by printf.
Would it be possible to remove the rewrite and switch back to Tcl (at
least for new releases of Ubuntu)? It seems that the upstream package
has switched to some lightweight Tcl interpreter (Jim). This could
remove some of the reasons why it had to be rewritten (extra
dependencies, boot time?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676763
Title:
usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838154] Re: Something hinders XFCE performance. >:]
*** This bug is a duplicate of bug 1839716 *** https://bugs.launchpad.net/bugs/1839716 + 25 snapping right /\https://bugs.launchpad.net/xorg-server/+bug/1838154/+attachment/5307318/+files/2019-11-23_20-36-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838154 Title: Something hinders XFCE performance. >:] To manage notifications about this bug go to: https://bugs.launchpad.net/wayland/+bug/1838154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856179] Re: WINE .desktop files are not grouped into a folder on the app screen.
Reported to WINE https://bugs.winehq.org/show_bug.cgi?id=48345 ** Bug watch added: Wine Bugzilla #48345 https://bugs.winehq.org/show_bug.cgi?id=48345 ** Also affects: wine (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856179 Title: WINE .desktop files are not grouped into a folder on the app screen. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857545] [NEW] Multi-monitor fullscreen - wrong monitor selection
Public bug reported: To repeat this bug u need 2 monitors. [1] [2] left right Open google-chrome or visual studio code on the right [2] monitor Press f11 - this is ok - fullscreen on the right [2] monitor Press f11 again before continue, to exit fullscreen mode Now press left mouse button and hold head on the window and bring mouse closer left part of the right [2] monitor. Press f11 - this is bad - fullscreen on the left [1] monitor but window was on the right [2]. Press f11 again before continue, to exit fullscreen mode Now press left mouse button and hold right border of the window to resize it and change width of the window (it does not matter will yoy increase or degreese it) Press f11 - this is ok - fullscreen on the right [2] monitor. Press f11 again before continue, to exit fullscreen mode Press f11 - this is bad - fullscreen on the left [1] monitor. $ uname -a Linux username 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857545 Title: Multi-monitor fullscreen - wrong monitor selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
I think that upgrading the modem firmware (I have Sierra Wireless EM7305) might help, but that does not fix the underlying bug / broken assumptions. ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676763 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
Thank you, Martin, for providing this simple but clever and VERY effective workaround! I can confirm that it works. I'd like to add, that you have to execute this script with 'bash fix_sound.sh'. 'sh fix_sound.sh' doesn't work because debian and ubuntu use dash as non-interactive shell and dash cannot handle that kind of assertion: <<<. Took me a while to realize what the problem was. ^^ Anyway. I'd like to see a real fix here. But in the meantime I can live with that script. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857544] [NEW] package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: It worked at some point, but it stopped working now. I remove, and purged the samba and reinstall them, but it spits out the same error. invoke-rc.d: initscript smbd, action "start" failed. ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded (/etc/init.d/smbd; bad; vendor preset: enabled) Active: failed (Result: exit-code) since 수 2019-12-25 21:58:41 CST; 36ms ago Docs: man:systemd-sysv-generator(8) Process: 14778 ExecStart=/etc/init.d/smbd start (code=exited, status=1/FAILURE) 12월 25 21:58:40 bpi-iot-ros-ai systemd[1]: Starting LSB: start Samba SMB/CIFS daemon (smbd)... 12월 25 21:58:41 bpi-iot-ros-ai smbd[14778]: * Starting SMB/CIFS daemon smbd 12월 25 21:58:41 bpi-iot-ros-ai smbd[14778]:...fail! 12월 25 21:58:41 bpi-iot-ros-ai systemd[1]: smbd.service: Control process exited, code=exited status=1 12월 25 21:58:41 bpi-iot-ros-ai systemd[1]: Failed to start LSB: start Samba SMB/CIFS daemon (smbd). 12월 25 21:58:41 bpi-iot-ros-ai systemd[1]: smbd.service: Unit entered failed state. 12월 25 21:58:41 bpi-iot-ros-ai systemd[1]: smbd.service: Failed with result 'exit-code'. dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu11) ... Processing triggers for systemd (229-4ubuntu21.23) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for ufw (0.35-0ubuntu2) ... Errors were encountered while processing: samba E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 Uname: Linux 3.10.108-BPI-M2U-Kernel armv7l ApportVersion: 2.20.1-0ubuntu2.21 AptOrdering: samba: Install samba: Configure NULL: ConfigurePending Architecture: armhf BothFailedConnect: Yes Date: Wed Dec 25 21:56:41 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 NmbdLog: RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857544 Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1857544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857544] Re: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857544 Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1857544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
Ah, it starts to make sense. usb_modeswitch_dispatcher is called correctly, but it cannot find interface 0 on the device to be switched. However, dmesg contains warning about the same thing: [2.369824] usb 1-11: new high-speed USB device number 5 using xhci_hcd [2.520482] usb 1-11: config 1 has an invalid interface number: 8 but max is 3 [2.520484] usb 1-11: config 1 has no interface number 1 [2.520915] usb 1-11: config 2 has an invalid interface number: 12 but max is 1 [2.520916] usb 1-11: config 2 has an invalid interface number: 13 but max is 1 [2.520917] usb 1-11: config 2 has an invalid interface number: 13 but max is 1 [2.520918] usb 1-11: config 2 has no interface number 0 [2.520919] usb 1-11: config 2 has no interface number 1 [2.521502] usb 1-11: New USB device found, idVendor=1199, idProduct=9041, bcdDevice= 0.06 [2.521503] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [2.521504] usb 1-11: Product: EM7305 [2.521505] usb 1-11: Manufacturer: Sierra Wireless, Incorporated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676763 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Clicking Activities in the corner doesn't work
** Changed in: mutter Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856179] Re: WINE .desktop files are not grouped into a folder on the app screen.
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856179 Title: WINE .desktop files are not grouped into a folder on the app screen. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857338] Re: GIMP Crash during Launching
Keep crashing, already uninstall the GIMP. Instead, install Pinta and it's running smoothly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857338 Title: GIMP Crash during Launching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1857338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support
** Tags added: oem-priority originate-from-1852693 sutton -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857541 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726229] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in main()
*** This bug is a duplicate of bug 1676763 *** https://bugs.launchpad.net/bugs/1676763 I suspect that this bug is a duplicate of #1676763. ** This bug has been marked a duplicate of bug 1676763 usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726229 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1726229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
Very similar crash happens to me on Bionic as well. So far it seems to me that usb_modeswitch_dispatcher is called incorrectly and therefore it crashes when it eventually encounters a NULL pointer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676763 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726229] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in main()
*** This bug is a duplicate of bug 1676763 *** https://bugs.launchpad.net/bugs/1676763 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: usb-modeswitch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726229 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1726229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842281] Re: hbmqtt 0.9.2 does not support python 3.7
hbmqtt has supported Python 3.7 since this commit[1], which was first released in 0.9.3. Since Ubuntu 19.04 reaches end-of-life in a week and hbmqtt 0.9.5 is packaged in Ubuntu 19.10, I believe this bug can be closed. [1] https://github.com/beerfactory/hbmqtt/commit/1af9e7f99cdd05e8e75f7b84efc289563fe87c9b ** Changed in: python-hbmqtt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842281 Title: hbmqtt 0.9.2 does not support python 3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hbmqtt/+bug/1842281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857542] [NEW] lxc-checkpoint needs the criu package
Public bug reported: lxc-checkpoint needs criu to be installed but the criu package is absent in eoan and focal (criu exists in disco and bionic). ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857542 Title: lxc-checkpoint needs the criu package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support
** Changed in: linux (Ubuntu) Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857541 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857541] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1857541 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857541 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857541] [NEW] [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support
Public bug reported: SRU justification: [Impact] The current kernel didn't support multitouch for LG I2C touchscreen. [Fix] Add LG I2C id to hid-multitouch to support it. [Test] Verified on hardware with a positive result. [Regression Potential] Low. Add new I2C id with positive verification. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AaronMa (mapengyu) Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857541 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857540] [NEW] GIMP-CRITICAL: gimp_item_get_image: assertion 'GIMP_IS_ITEM (item)' failed
Public bug reported:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
using babl version 0.1.72 (compiled against version 0.1.72)
using GEGL version 0.4.18 (compiled against version 0.4.18)
using GLib version 2.56.4 (compiled against version 2.56.4)
using GdkPixbuf version 2.36.11 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.40.14 (compiled against version 1.40.14)
using Fontconfig version 2.12.6 (compiled against version 2.12.6)
using Cairo version 1.15.10 (compiled against version 1.15.10)
```
> GIMP-CRITICAL: gimp_item_get_image: assertion 'GIMP_IS_ITEM (item)' failed
Stack trace:
```
# Stack traces obtained from PID 1402 - Thread 1402 #
[New LWP 1405]
[New LWP 1406]
[New LWP 1407]
[New LWP 1408]
[New LWP 1409]
[New LWP 1410]
[New LWP 1411]
[New LWP 1412]
[New LWP 1413]
[New LWP 1415]
[New LWP 1451]
[New LWP 1462]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f83fb27c384 in __libc_read (fd=21, buf=0x7ffde9ba7b20, nbytes=256) at
../sysdeps/unix/sysv/linux/read.c:27
Id Target Id Frame
* 1Thread 0x7f84000aae00 (LWP 1402) "gimp-2.10" 0x7f83fb27c384 in
__libc_read (fd=21, buf=0x7ffde9ba7b20, nbytes=256) at
../sysdeps/unix/sysv/linux/read.c:27
2Thread 0x7f83f1736700 (LWP 1405) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f83f0f35700 (LWP 1406) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7f83f0734700 (LWP 1407) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f83eff33700 (LWP 1408) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f83ef732700 (LWP 1409) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7f83eef31700 (LWP 1410) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f83ee730700 (LWP 1411) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7f83ded49700 (LWP 1412) "gmain" 0x7f83faf8ebf9 in
__GI___poll (fds=0x561631103610, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
10 Thread 0x7f83de548700 (LWP 1413) "gdbus" 0x7f83faf8ebf9 in
__GI___poll (fds=0x561631159330, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
11 Thread 0x7f83b75c0700 (LWP 1415) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
12 Thread 0x7f83b6dbf700 (LWP 1451) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
13 Thread 0x7f83b5dea700 (LWP 1462) "paint" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 13 (Thread 0x7f83b5dea700 (LWP 1462)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f83fbabe77f in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x561630452ccf in ?? ()
No symbol table info available.
#3 0x7f83fbaa0195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f83fb2726db in start_thread (arg=0x7f83b5dea700) at
pthread_create.c:463
pd = 0x7f83b5dea700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140203668711168,
8073677002576571142, 140203668707584, 0, 94653375769680, 140728524766352,
-8139097681309914362, -8138989433986405626}, mask_was_saved = 0}}, priv =
[Bug 1857227] Re: PulseAudio sound disappears on hdmi via stereo output
This problem has been known for 5 years and has not yet been resolved https://github.com/raspberrypi/linux/issues/688 ** Bug watch added: github.com/raspberrypi/linux/issues #688 https://github.com/raspberrypi/linux/issues/688 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857227 Title: PulseAudio sound disappears on hdmi via stereo output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857539] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1857539/+attachment/5315318/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857539] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1857539/+attachment/5315317/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857539] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1857539/+attachment/5315319/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1857539/+attachment/5315307/+files/CoreDump.gz ** Changed in: nautilus (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857539] [NEW] nautilus crashed with SIGSEGV
Public bug reported: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962: mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash focal ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857539] nautilus crashed with SIGSEGV
StacktraceTop: widget_needs_widget_path (widget=0x55e4375bb830) at ../../../../gtk/gtkcsswidgetnode.c:171 gtk_css_widget_node_init_matcher (node=0x55e436d33080, matcher=0x7ffde83d1110) at ../../../../gtk/gtkcsswidgetnode.c:190 gtk_css_node_init_matcher (matcher=0x7ffde83d1110, cssnode=0x55e436d33080) at ../../../../gtk/gtkcssnode.c:1416 gtk_css_node_create_style (cssnode=0x55e436d33080) at ../../../../gtk/gtkcssnode.c:370 gtk_css_node_real_update_style (cssnode=0x55e436d33080, change=12884901887, timestamp=0, style=0x55e437c03c20) at ../../../../gtk/gtkcssnode.c:425 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857536] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857536 Title: Touch pad is not working - Lenovo G50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857335] Re: System volume slider only works between ~90% and 100%.
FWIW, the speaker works fine on a Huawei Mate 30 Pro/Android 10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857335 Title: System volume slider only works between ~90% and 100%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857536] [NEW] Touch pad is not working - Lenovo G50
Public bug reported: Laptop : Lenovo G50 I ran below command to check that touchpad package is available or not, and couldn't find the synaptic touchpad package. Command : cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kadinish 1720 F pulseaudio /dev/snd/controlC1: kadinish 1720 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 16:02:24 2019 InstallationDate: Installed on 2019-12-10 (15 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20351 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=6a5066c3-fbca-4e9c-be14-2af9e25b497b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-25 (0 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857536 Title: Touch pad is not working - Lenovo G50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
