[Touch-packages] [Bug 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)
Ok, the mis-directed output seems to be fixed with a kernel 5.2. With the stock 5.0.0-21-generic, disconnecting BT in the Ubuntu gui does not actually disconnect immediately. Instead, the disconnect happens when BT is turned ON again in the gui! (based on my BT headset's synthesized status-change messages, which say nothing when BT is turned OFF in the gui, but say "disconnected" when BT is turned ON in the gui). Thereafter, sound goes to the speakers even though the gui shows the BT headset is connected. I found that power-cycling the headset clears the problem, presumably because of the extraneous connection messages when the headset comes back on. These problem COMPLETELY GO AWAY with kernel 5.2 installed. Now, when I disconnect the headset in the Ubuntu gui, the headset instantly reports being disconnected, and it re-connects propertly when the headset is turned on again in the Ubuntu gui. There are some remaining gui issues where the switch in the gui snaps back by itself to "off" on the first few tries, but after a while the headset connects correctly. I will file a different bugrep about that with a video. In conclusion, it sounds like some kernel bug or api mis-match will be resolved with kernel 5.2, but that won't be shipped for while in Ubuntu. ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 22:59:01 2019 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: Primary Bus: USB BD Address: 48:89:E7:CF:4F:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:14153 acl:154 sco:0 events:971 errors:0 TX bytes:429273 acl:643 sco:0 commands:229 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+subscriptions
[Touch-packages] [Bug 1838181] 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 Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1838181 Title: 3D Application cannot run anymore Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: W6X73EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: console-setup (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: Won't Fix Status in console-setup package in Ubuntu: Expired Bug description: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. [Cause] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838181] Re: 3D Application cannot run anymore
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1838181 Title: 3D Application cannot run anymore Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: W6X73EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838192] Re: X server segfaults immediately at startup
Please resubmit that crash file using this command: ubuntu-bug /PATH/TO/CRASH/FILE and tell us the number of the new bug created. If that doesn't work then please look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Package changed: xorg-server (Ubuntu) => xorg-server-hwe-16.04 (Ubuntu) ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server-hwe-16.04 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838192 Title: X server segfaults immediately at startup Status in linux-hwe package in Ubuntu: Incomplete Status in xorg-server-hwe-16.04 package in Ubuntu: Incomplete Bug description: This system was working perfectly 3 months ago. I turned it off and left it off until yesterday. When I came back to it and turned it on, it worked initially but then the nvidia video card (nvidia GeForce GT 630) decided to die. I replaced the video card with an nvidia GeForce GT 710 and hit this issue. The machine also has integrated Intel graphics which I am not using. The system boots fine, I see BIOS boot messages and linux kernel messages until X tries to start. After it does that, nothing is displayed on screen. If I try to switch to another VT with for example, I get no output then either. Extract from /var/log/Xorg.0.log [20.839] (EE) Backtrace: [20.839] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55ef19ccae0e] [20.839] (EE) 1: /usr/lib/xorg/Xorg (0x55ef19b19000+0x1b5b79) [0x55ef19cceb79] [20.839] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc802cbb000+0x11390) [0x7fc802ccc390] [20.839] (EE) 3: /usr/lib/xorg/Xorg (RRProviderAutoConfigGpuScreen+0x42) [0x55ef19c38232] [20.839] (EE) 4: /usr/lib/xorg/Xorg (InitOutput+0x5bd) [0x55ef19bb1c7d] [20.839] (EE) 5: /usr/lib/xorg/Xorg (0x55ef19b19000+0x582d6) [0x55ef19b712d6] [20.839] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fc802911830] [20.839] (EE) 7: /usr/lib/xorg/Xorg (_start+0x29) [0x55ef19b5b449] [20.839] (EE) [20.839] (EE) Segmentation fault at address 0x130 [20.839] (EE) Fatal server error: [20.839] (EE) Caught signal 11 (Segmentation fault). Server aborting [20.839] (EE) [20.839] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. I am using the nvidia drivers and they seem not to be loading for some reason. I need to use them for vdpau support. Here is where the X server tries to load the nvidia driver, from earlier in the same log file: ... [20.823] (II) xfree86: Adding drm device (/dev/dri/card0) [20.823] (II) xfree86: Adding drm device (/dev/dri/card1) [20.826] (--) PCI: (0:0:2:0) 8086:29c2:8086:5044 rev 2, Mem @ 0x9b40/524288, 0x8000/268435456, 0x9b30/1048576, I/O @ 0 x4430/8 [20.826] (--) PCI:*(0:1:0:0) 10de:128b:1462:8c93 rev 161, Mem @ 0x9a00/16777216, 0x9000/134217728, 0x9800/33554432, I/ O @ 0x3000/128, BIOS @ 0x/131072 [20.826] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere. [20.826] (II) "glx" will be loaded by default. [20.826] (II) LoadModule: "glx" [20.826] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [20.827] (II) Module glx: vendor="X.Org Foundation" [20.827]compiled for 1.19.6, module version = 1.0.0 [20.827]ABI class: X.Org Server Extension, version 10.0 [20.827] (==) Matched nvidia as autoconfigured driver 0 [20.828] (==) Matched nouveau as autoconfigured driver 1 [20.828] (==) Matched intel as autoconfigured driver 2 [20.828] (==) Matched nvidia as autoconfigured driver 3 [20.828] (==) Matched nouveau as autoconfigured driver 4 [20.828] (==) Matched modesetting as autoconfigured driver 5 [20.828] (==) Matched fbdev as autoconfigured driver 6 [20.828] (==) Matched vesa as autoconfigured driver 7 [20.828] (==) Assigned the driver to the xf86ConfigLayout [20.828] (II) LoadModule: "nvidia" [20.829] (WW) Warning, couldn't open module nvidia [20.829] (II) UnloadModule: "nvidia" [20.829] (II) Unloading nvidia [20.829] (EE) Failed to load module "nvidia" (module does not exist, 0) [20.829] (II) LoadModule: "nouveau" [20.829] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [20.830] (II) Module nouveau: vendor="X.Org Foundation" [20.830]
[Touch-packages] [Bug 1838181] Re: 3D Application cannot run anymore
Possibly related from the kernel log: [ 373.840537] [drm] GPU HANG: ecode 9:0:0x85db, in zinc [4585], reason: hang on rcs0, action: reset [ 373.840584] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 383.837062] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 393.821041] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 404.956876] asynchronous wait on fence i915:zinc[4585]/1:11 timed out [ 405.821085] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 415.964886] asynchronous wait on fence i915:zinc[4585]/1:14 timed out [ 419.837025] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 426.972786] asynchronous wait on fence i915:zinc[4585]/1:17 timed out [ 431.841000] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 431.854654] show_signal_msg: 29 callbacks suppressed [ 431.854660] zinc[4585]: segfault at 20 ip 56484167bd9e sp 7fffb80cd2f0 error 4 in zinc[56484159e000+29] [ 431.854672] Code: 48 89 55 e8 48 8b 55 f0 48 8b 45 f8 48 89 d6 48 89 c7 e8 1c 0c 00 00 90 c9 c3 55 48 89 e5 48 89 7d f8 48 89 75 f0 48 8b 45 f0 <48> 8b 10 48 8b 45 f8 48 89 10 90 5d c3 90 55 48 89 e5 48 89 7d f8 [ 744.794676] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 756.798602] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 766.778545] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 782.778425] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 793.822394] asynchronous wait on fence i915:memcheck-amd64-[4688]/1:14 timed out [ 796.794414] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 806.778371] i915 :00:02.0: Resetting rcs0 for hang on rcs0 ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1838181 Title: 3D Application cannot run anymore Status in mesa package in Ubuntu: New Bug description: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: W6X73EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1838181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)
It sounds like the log messages relating to the issue are: Jul 27 22:54:49 hostname gsd-media-keys[2755]: Unable to get default sink ... Jul 27 22:55:04 hostname bluetoothd[1423]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jul 27 22:55:04 hostname bluetoothd[1423]: connect error: Device or resource busy (16) Which suggests it's the kernel that's behaving differently, via PulseAudio. Please try some newer (or older) kernels from: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and tell us which versions, if any, avoid the bug. ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 22:59:01 2019 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: Primary Bus: USB BD Address: 48:89:E7:CF:4F:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:14153 acl:154 sco:0 events:971 errors:0 TX bytes:429273 acl:643 sco:0 commands:229 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)
The strange thing here is that 18.10 and 19.04 use the same versions of bluez and pulseaudio. So I don't think those are going to be the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) Status in bluez package in Ubuntu: New Bug description: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 22:59:01 2019 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: Primary Bus: USB BD Address: 48:89:E7:CF:4F:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:14153 acl:154 sco:0 events:971 errors:0 TX bytes:429273 acl:643 sco:0 commands:229 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: patch ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] 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 1838151 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 Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583840] Re: pulseaudio crashed with SIGSEGV in avahi_client_get_state() from publish_service() from once_callback() from dispatch_defer()
** Summary changed: - pulseaudio crashed with SIGSEGV in avahi_client_get_state() + pulseaudio crashed with SIGSEGV in avahi_client_get_state() from publish_service() from once_callback() from dispatch_defer() ** Tags removed: artful yakkety zesty ** Tags added: disco eoan xenial ** Description changed: https://errors.ubuntu.com/problem/e533a6f758cf595e0b31c717374dfed1acf6b2e9 + https://errors.ubuntu.com/problem/183fda6a99b85219cd01c114e0b5f8d6c3ae1090 + --- Not sure error report popped up on reboot of system... ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:8.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10 Uname: Linux 4.4.0-23-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johndoe3047 F pulseaudio johndoe3120 F panel-6-mixer CurrentDesktop: XFCE Date: Thu May 19 18:39:25 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-03-04 (76 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160229) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: pulseaudio StacktraceTop: avahi_client_get_state () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/pulse-8.0/modules/module-zeroconf-publish.so ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 Title: pulseaudio crashed with SIGSEGV in avahi_client_get_state() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax kismet lpadmin plugdev pulse-access sambashare sudo video dmi.bios.date: 11/28/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0T656F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/28/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 360 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1583840 Title: pulseaudio crashed with SIGSEGV in avahi_client_get_state() from publish_service() from once_callback() from dispatch_defer() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/e533a6f758cf595e0b31c717374dfed1acf6b2e9 https://errors.ubuntu.com/problem/183fda6a99b85219cd01c114e0b5f8d6c3ae1090 --- Not sure error report popped up on reboot of system... ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:8.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10 Uname: Linux 4.4.0-23-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johndoe3047 F pulseaudio johndoe3120 F panel-6-mixer CurrentDesktop: XFCE Date: Thu May 19 18:39:25 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-03-04 (76 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160229) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: pulseaudio StacktraceTop: avahi_client_get_state () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/pulse-8.0/modules/module-zeroconf-publish.so ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 Title: pulseaudio crashed with SIGSEGV in avahi_client_get_state() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax kismet lpadmin plugdev pulse-access sambashare sudo video dmi.bios.date: 11/28/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0T656F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/28/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Touch-packages] [Bug 1690063] Re: pulseaudio crashed with SIGSEGV in avahi_client_is_connected() from avahi_entry_group_reset() from publish_service() from once_callback() from dispatch_defer()
*** This bug is a duplicate of bug 1583840 *** https://bugs.launchpad.net/bugs/1583840 ** This bug has been marked a duplicate of bug 1583840 pulseaudio crashed with SIGSEGV in avahi_client_get_state() from publish_service() from once_callback() from dispatch_defer() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690063 Title: pulseaudio crashed with SIGSEGV in avahi_client_is_connected() from avahi_entry_group_reset() from publish_service() from once_callback() from dispatch_defer() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:8.0-0ubuntu3.2, the problem page at https://errors.ubuntu.com/problem/183fda6a99b85219cd01c114e0b5f8d6c3ae1090 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838217] [NEW] /usr/bin/pulseaudio:11:main_arena:pa_hashmap_get:pa_proplist_gets:publish_service:once_callback
*** This bug is a duplicate of bug 1679744 *** https://bugs.launchpad.net/bugs/1679744 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5f81017bec424af922953d918f2c121c832b0152 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838217 Title: /usr/bin/pulseaudio:11:main_arena:pa_hashmap_get:pa_proplist_gets:publish_service:once_callback Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5f81017bec424af922953d918f2c121c832b0152 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838217] Re: /usr/bin/pulseaudio:11:main_arena:pa_hashmap_get:pa_proplist_gets:publish_service:once_callback
*** This bug is a duplicate of bug 1679744 *** https://bugs.launchpad.net/bugs/1679744 ** This bug has been marked a duplicate of bug 1679744 pulseaudio crashed with SIGSEGV in pa_hashmap_get() from pa_proplist_gets() from publish_service() from once_callback() from dispatch_defer() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838217 Title: /usr/bin/pulseaudio:11:main_arena:pa_hashmap_get:pa_proplist_gets:publish_service:once_callback Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5f81017bec424af922953d918f2c121c832b0152 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637802] Re: ubuntu 14.04 problem between airplane mode and bluetooth
** Tags removed: trusty ** Tags added: bionic xenial ** Changed in: bluez (Ubuntu) Status: Won't Fix => New ** Summary changed: - ubuntu 14.04 problem between airplane mode and bluetooth + Lenovo G400 problem between airplane mode and bluetooth -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1637802 Title: Lenovo G400 problem between airplane mode and bluetooth Status in bluez package in Ubuntu: New Bug description: is very strange because sometime is working but most of the time the bluetooth icon is absent and even if you go in System Settings you can not switch on bluetooth than if you start to play with airplane mode switch and bluetooth switch some time bluetooth comes a life for sometime than it stop for good, anyway to me becomes evident that there is a relation between airplane mode and bluetooth, be so nice finding a solution if posible --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-05-30 (153 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20235 Package: bluez 4.101-0ubuntu13.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=c89a3965-eb84-4899-abe5-01cf184b6981 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Tags: trusty Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN16WW(V1.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G400 dmi.modalias: dmi:bvnLENOVO:bvr78CN16WW(V1.04):bd04/17/2013:svnLENOVO:pn20235:pvrLenovoG400:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG400: dmi.product.name: 20235 dmi.product.version: Lenovo G400 dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1637802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()
Owen, that sounds like bug 1679744. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690051 Title: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c39b5c96e18a9e1b48ea983380914ce29fd79134 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838215] Re: I can't log in with my user and password
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: lightdm (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/lightdm/+question/682397 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1838215 Title: I can't log in with my user and password Status in lightdm package in Ubuntu: Invalid Bug description: First I had the message "No running instance of xfce-4 panel was found", then I rebooted my computer and the menu bar had disappeared, I rebooted again but now I try to loggin and password and the computer returns me to the menu of input user and password as if I had typed wrong my password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Jul 28 17:33:45 2019 InstallationDate: Installed on 2019-07-02 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1838215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838215] Re: I can't log in with my user and password
I use Xubuntu operating system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1838215 Title: I can't log in with my user and password Status in lightdm package in Ubuntu: New Bug description: First I had the message "No running instance of xfce-4 panel was found", then I rebooted my computer and the menu bar had disappeared, I rebooted again but now I try to loggin and password and the computer returns me to the menu of input user and password as if I had typed wrong my password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Jul 28 17:33:45 2019 InstallationDate: Installed on 2019-07-02 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1838215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838215] [NEW] I can't log in with my user and password
Public bug reported: First I had the message "No running instance of xfce-4 panel was found", then I rebooted my computer and the menu bar had disappeared, I rebooted again but now I try to loggin and password and the computer returns me to the menu of input user and password as if I had typed wrong my password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Jul 28 17:33:45 2019 InstallationDate: Installed on 2019-07-02 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1838215 Title: I can't log in with my user and password Status in lightdm package in Ubuntu: New Bug description: First I had the message "No running instance of xfce-4 panel was found", then I rebooted my computer and the menu bar had disappeared, I rebooted again but now I try to loggin and password and the computer returns me to the menu of input user and password as if I had typed wrong my password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Jul 28 17:33:45 2019 InstallationDate: Installed on 2019-07-02 (26 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1838215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637802] Re: ubuntu 14.04 problem between airplane mode and bluetooth
I went up with ubuntu 16.04 than ubuntu 18.04 but the air-plane mode problem did not stop. Every time i start ubuntu airplane mode is on than i switch it off and usually (not every time) bluez goes on -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1637802 Title: ubuntu 14.04 problem between airplane mode and bluetooth Status in bluez package in Ubuntu: Won't Fix Bug description: is very strange because sometime is working but most of the time the bluetooth icon is absent and even if you go in System Settings you can not switch on bluetooth than if you start to play with airplane mode switch and bluetooth switch some time bluetooth comes a life for sometime than it stop for good, anyway to me becomes evident that there is a relation between airplane mode and bluetooth, be so nice finding a solution if posible --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-05-30 (153 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20235 Package: bluez 4.101-0ubuntu13.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=c89a3965-eb84-4899-abe5-01cf184b6981 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Tags: trusty Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN16WW(V1.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G400 dmi.modalias: dmi:bvnLENOVO:bvr78CN16WW(V1.04):bd04/17/2013:svnLENOVO:pn20235:pvrLenovoG400:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG400: dmi.product.name: 20235 dmi.product.version: Lenovo G400 dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1637802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Unfortunatelu no new flavor of Ubuntu is supporting 32 bits anymore. Therefore I had to install Debian 10 (Buster). Wayland at Debian is running without severe problems. This problem also is not existing anymore, because Wyland is no longer using an extra fence register if a dual monitor is used. I suppose this means also at some release of Ubuntu the problem will disappear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in Mesa: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()
I am still getting the crash, but the location of it has changed. Now it dies at txt = avahi_string_list_add_pair(txt, "device", s->name); Thread 4 "avahi-ml" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe5984700 (LWP 5939)] 0x5590f820 in ?? () (gdb) bt #0 0x5590f820 in ?? () #1 0x77657566 in pa_hashmap_get (h=h@entry=0x557ee040, key=key@entry=0x7fffe5faa028) at pulsecore/hashmap.c:182 #2 0x77642901 in pa_proplist_gets (p=0x557ee040, key=key@entry=0x7fffe5faa028 "device.description") at pulse/proplist.c:283 #3 0x7fffe5fa846c in publish_service (api=, service=0x558bc280) at modules/module-zeroconf-publish.c:318 #4 0x773fd578 in once_callback (m=0x559484b8, e=0x55831ac0, userdata=) at pulse/mainloop-api.c:45 #5 0x774002ad in dispatch_defer (m=0x55948460) at pulse/mainloop.c:680 #6 pa_mainloop_dispatch (m=m@entry=0x55948460) at pulse/mainloop.c:889 #7 0x774004de in pa_mainloop_iterate (m=0x55948460, block=, retval=0x0) at pulse/mainloop.c:929 #8 0x77400560 in pa_mainloop_run (m=0x55948460, retval=retval@entry=0x0) at pulse/mainloop.c:944 #9 0x7740e3c9 in thread (userdata=0x55823ae0) at pulse/thread-mainloop.c:100 #10 0x7767e318 in internal_thread_func (userdata=0x55874580) at pulsecore/thread-posix.c:81 #11 0x76b676db in start_thread (arg=0x7fffe5984700) at pthread_create.c:463 #12 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) this is with pulseaudio_11.1-1ubuntu7.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690051 Title: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c39b5c96e18a9e1b48ea983380914ce29fd79134 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838208] [NEW] Wifi stops responding sporadically on lenovo-yoga-720-15ikb
Public bug reported: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session ** Summary changed: - Wifi stops responding sporadically + Wifi stops responding sporadically on lenovo-yoga-720-15ikb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in network-manager package in Ubuntu: New Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited
[Touch-packages] [Bug 1759248] Re: addr2line wrong search path for debug files
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: binutils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1759248
Title:
addr2line wrong search path for debug files
Status in binutils package in Ubuntu:
Confirmed
Bug description:
I cannot make `addr2line` to work. It does look for symbols at three
(*unexisting*) paths:
/usr/bin/*.debug
/usr/bin/.debug/*.debug
/usr/lib/debug/usr/bin/*.debug
But it just seems to ignore the path where all debugging symbols are actually
installed by default:
/usr/lib/debug/.build-id/
I run `addr2line` like this:
addr2line -f -C -e
Am I missing some configuration switch, system option, or anything
similar?
Now some proofs for what I'm stating.
Here, I'll be using the program `screen` as an example:
$ sudo apt-get install screen screen-dbg
$ file /usr/bin/screen
> /usr/bin/screen: setgid ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
2.6.32,
BuildID[sha1]=e9d3cd5073daa6b7365b3787673143edeec589d3, stripped
$ dpkg -L screen-dbg
> /usr/lib/debug/.build-id/e9/d3cd5073daa6b7365b3787673143edeec589d3.debug
Here we empirically found out where the debug symbols for `screen` are:
/usr/lib/debug/.build-id/e9/d3cd5073daa6b7365b3787673143edeec589d3.debug
Now we run `strace addr2line` to see where it tries to access...
# Get any valid object address
$ objdump -T /usr/bin/screen
> 006697e0
# Use the object address in addr2line
$ strace -f addr2line -f -C \
-e /usr/bin/screen 0x006697e0 2>&1 | grep debug
> open("/usr/bin/d3cd5073daa6b7365b3787673143edeec589d3.debug", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/bin/.debug/d3cd5073daa6b7365b3787673143edeec589d3.debug",
O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/debug/usr/bin/d3cd5073daa6b7365b3787673143edeec589d3.debug",
O_RDONLY) = -1 ENOENT (No such file or directory)
Here we see the 3 paths I mentioned earlier, but no signs of the
desired one.
Additional information:
- Ubuntu release
$ lsb_release -rd
> Description: Ubuntu 16.04.4 LTS
Release: 16.04
- Package version
$ apt-cache policy binutils
> binutils:
Installed: 2.26.1-1ubuntu1~16.04.6
Candidate: 2.26.1-1ubuntu1~16.04.6
Version table:
*** 2.26.1-1ubuntu1~16.04.6 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
2.26-8ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- What I expected to happen
I expected that the `strace` command shown avobe would access the debug files
at their actual location:
/usr/lib/debug/.build-id/e9/d3cd5073daa6b7365b3787673143edeec589d3.debug
- What happened instead
The `addr2line` program does look for the debug file at three unexisting
locations:
/usr/bin/*.debug
/usr/bin/.debug/*.debug
/usr/lib/debug/usr/bin/*.debug
but it does not look for the debug file at the correct location.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1759248/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
** Changed in: hud (Ubuntu) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: New Status in unbuntu-fr Scripts - apt: Fix Committed Status in hud package in Ubuntu: Incomplete Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from
[Touch-packages] [Bug 1838192] Re: X server segfaults immediately at startup
Tried booting the system with linux-image-4.4.0-154-generic. X works on this kernel. Tried booting the system with linux-image-4.15.0-47-generic. X works on this kernel. Presumably there is some bad interaction between the nvidia module and 4.15.0-55-generic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838192 Title: X server segfaults immediately at startup Status in xorg package in Ubuntu: New Bug description: This system was working perfectly 3 months ago. I turned it off and left it off until yesterday. When I came back to it and turned it on, it worked initially but then the nvidia video card (nvidia GeForce GT 630) decided to die. I replaced the video card with an nvidia GeForce GT 710 and hit this issue. The machine also has integrated Intel graphics which I am not using. The system boots fine, I see BIOS boot messages and linux kernel messages until X tries to start. After it does that, nothing is displayed on screen. If I try to switch to another VT with for example, I get no output then either. Extract from /var/log/Xorg.0.log [20.839] (EE) Backtrace: [20.839] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55ef19ccae0e] [20.839] (EE) 1: /usr/lib/xorg/Xorg (0x55ef19b19000+0x1b5b79) [0x55ef19cceb79] [20.839] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc802cbb000+0x11390) [0x7fc802ccc390] [20.839] (EE) 3: /usr/lib/xorg/Xorg (RRProviderAutoConfigGpuScreen+0x42) [0x55ef19c38232] [20.839] (EE) 4: /usr/lib/xorg/Xorg (InitOutput+0x5bd) [0x55ef19bb1c7d] [20.839] (EE) 5: /usr/lib/xorg/Xorg (0x55ef19b19000+0x582d6) [0x55ef19b712d6] [20.839] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fc802911830] [20.839] (EE) 7: /usr/lib/xorg/Xorg (_start+0x29) [0x55ef19b5b449] [20.839] (EE) [20.839] (EE) Segmentation fault at address 0x130 [20.839] (EE) Fatal server error: [20.839] (EE) Caught signal 11 (Segmentation fault). Server aborting [20.839] (EE) [20.839] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. I am using the nvidia drivers and they seem not to be loading for some reason. I need to use them for vdpau support. Here is where the X server tries to load the nvidia driver, from earlier in the same log file: ... [20.823] (II) xfree86: Adding drm device (/dev/dri/card0) [20.823] (II) xfree86: Adding drm device (/dev/dri/card1) [20.826] (--) PCI: (0:0:2:0) 8086:29c2:8086:5044 rev 2, Mem @ 0x9b40/524288, 0x8000/268435456, 0x9b30/1048576, I/O @ 0 x4430/8 [20.826] (--) PCI:*(0:1:0:0) 10de:128b:1462:8c93 rev 161, Mem @ 0x9a00/16777216, 0x9000/134217728, 0x9800/33554432, I/ O @ 0x3000/128, BIOS @ 0x/131072 [20.826] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere. [20.826] (II) "glx" will be loaded by default. [20.826] (II) LoadModule: "glx" [20.826] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [20.827] (II) Module glx: vendor="X.Org Foundation" [20.827]compiled for 1.19.6, module version = 1.0.0 [20.827]ABI class: X.Org Server Extension, version 10.0 [20.827] (==) Matched nvidia as autoconfigured driver 0 [20.828] (==) Matched nouveau as autoconfigured driver 1 [20.828] (==) Matched intel as autoconfigured driver 2 [20.828] (==) Matched nvidia as autoconfigured driver 3 [20.828] (==) Matched nouveau as autoconfigured driver 4 [20.828] (==) Matched modesetting as autoconfigured driver 5 [20.828] (==) Matched fbdev as autoconfigured driver 6 [20.828] (==) Matched vesa as autoconfigured driver 7 [20.828] (==) Assigned the driver to the xf86ConfigLayout [20.828] (II) LoadModule: "nvidia" [20.829] (WW) Warning, couldn't open module nvidia [20.829] (II) UnloadModule: "nvidia" [20.829] (II) Unloading nvidia [20.829] (EE) Failed to load module "nvidia" (module does not exist, 0) [20.829] (II) LoadModule: "nouveau" [20.829] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [20.830] (II) Module nouveau: vendor="X.Org Foundation" [20.830]compiled for 1.19.5, module version = 1.0.15 [20.830]Module class: X.Org Video Driver [20.830]ABI class: X.Org Video Driver, version 23.0 [20.830] (II) LoadModule: "intel" [20.830] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [20.830] (II) Module intel: vendor="X.Org Foundation" [20.830]compiled for 1.19.5, module version = 2.99.917 [20.830]Module class: X.Org Video Driver [20.830]ABI class: X.Org Video Driver, version 23.0 ... Steps I have taken: - reinstall
[Touch-packages] [Bug 1838192] Re: X server segfaults immediately at startup
** Attachment added: "crash file" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1838192/+attachment/5279727/+files/_usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838192 Title: X server segfaults immediately at startup Status in xorg package in Ubuntu: New Bug description: This system was working perfectly 3 months ago. I turned it off and left it off until yesterday. When I came back to it and turned it on, it worked initially but then the nvidia video card (nvidia GeForce GT 630) decided to die. I replaced the video card with an nvidia GeForce GT 710 and hit this issue. The machine also has integrated Intel graphics which I am not using. The system boots fine, I see BIOS boot messages and linux kernel messages until X tries to start. After it does that, nothing is displayed on screen. If I try to switch to another VT with for example, I get no output then either. Extract from /var/log/Xorg.0.log [20.839] (EE) Backtrace: [20.839] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55ef19ccae0e] [20.839] (EE) 1: /usr/lib/xorg/Xorg (0x55ef19b19000+0x1b5b79) [0x55ef19cceb79] [20.839] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc802cbb000+0x11390) [0x7fc802ccc390] [20.839] (EE) 3: /usr/lib/xorg/Xorg (RRProviderAutoConfigGpuScreen+0x42) [0x55ef19c38232] [20.839] (EE) 4: /usr/lib/xorg/Xorg (InitOutput+0x5bd) [0x55ef19bb1c7d] [20.839] (EE) 5: /usr/lib/xorg/Xorg (0x55ef19b19000+0x582d6) [0x55ef19b712d6] [20.839] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fc802911830] [20.839] (EE) 7: /usr/lib/xorg/Xorg (_start+0x29) [0x55ef19b5b449] [20.839] (EE) [20.839] (EE) Segmentation fault at address 0x130 [20.839] (EE) Fatal server error: [20.839] (EE) Caught signal 11 (Segmentation fault). Server aborting [20.839] (EE) [20.839] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. I am using the nvidia drivers and they seem not to be loading for some reason. I need to use them for vdpau support. Here is where the X server tries to load the nvidia driver, from earlier in the same log file: ... [20.823] (II) xfree86: Adding drm device (/dev/dri/card0) [20.823] (II) xfree86: Adding drm device (/dev/dri/card1) [20.826] (--) PCI: (0:0:2:0) 8086:29c2:8086:5044 rev 2, Mem @ 0x9b40/524288, 0x8000/268435456, 0x9b30/1048576, I/O @ 0 x4430/8 [20.826] (--) PCI:*(0:1:0:0) 10de:128b:1462:8c93 rev 161, Mem @ 0x9a00/16777216, 0x9000/134217728, 0x9800/33554432, I/ O @ 0x3000/128, BIOS @ 0x/131072 [20.826] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere. [20.826] (II) "glx" will be loaded by default. [20.826] (II) LoadModule: "glx" [20.826] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [20.827] (II) Module glx: vendor="X.Org Foundation" [20.827]compiled for 1.19.6, module version = 1.0.0 [20.827]ABI class: X.Org Server Extension, version 10.0 [20.827] (==) Matched nvidia as autoconfigured driver 0 [20.828] (==) Matched nouveau as autoconfigured driver 1 [20.828] (==) Matched intel as autoconfigured driver 2 [20.828] (==) Matched nvidia as autoconfigured driver 3 [20.828] (==) Matched nouveau as autoconfigured driver 4 [20.828] (==) Matched modesetting as autoconfigured driver 5 [20.828] (==) Matched fbdev as autoconfigured driver 6 [20.828] (==) Matched vesa as autoconfigured driver 7 [20.828] (==) Assigned the driver to the xf86ConfigLayout [20.828] (II) LoadModule: "nvidia" [20.829] (WW) Warning, couldn't open module nvidia [20.829] (II) UnloadModule: "nvidia" [20.829] (II) Unloading nvidia [20.829] (EE) Failed to load module "nvidia" (module does not exist, 0) [20.829] (II) LoadModule: "nouveau" [20.829] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [20.830] (II) Module nouveau: vendor="X.Org Foundation" [20.830]compiled for 1.19.5, module version = 1.0.15 [20.830]Module class: X.Org Video Driver [20.830]ABI class: X.Org Video Driver, version 23.0 [20.830] (II) LoadModule: "intel" [20.830] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [20.830] (II) Module intel: vendor="X.Org Foundation" [20.830]compiled for 1.19.5, module version = 2.99.917 [20.830]Module class: X.Org Video Driver [20.830]ABI class: X.Org Video Driver, version 23.0 ... Steps I have taken: - reinstall xserver-xorg-hwe-16.04, xserver-xorg-core-hwe-16.04, xserver-xorg-video-all-hwe-16.04 and nvidia-384 - rebooted a
[Touch-packages] [Bug 1838192] [NEW] X server segfaults immediately at startup
Public bug reported: This system was working perfectly 3 months ago. I turned it off and left it off until yesterday. When I came back to it and turned it on, it worked initially but then the nvidia video card (nvidia GeForce GT 630) decided to die. I replaced the video card with an nvidia GeForce GT 710 and hit this issue. The machine also has integrated Intel graphics which I am not using. The system boots fine, I see BIOS boot messages and linux kernel messages until X tries to start. After it does that, nothing is displayed on screen. If I try to switch to another VT with for example, I get no output then either. Extract from /var/log/Xorg.0.log [20.839] (EE) Backtrace: [20.839] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55ef19ccae0e] [20.839] (EE) 1: /usr/lib/xorg/Xorg (0x55ef19b19000+0x1b5b79) [0x55ef19cceb79] [20.839] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc802cbb000+0x11390) [0x7fc802ccc390] [20.839] (EE) 3: /usr/lib/xorg/Xorg (RRProviderAutoConfigGpuScreen+0x42) [0x55ef19c38232] [20.839] (EE) 4: /usr/lib/xorg/Xorg (InitOutput+0x5bd) [0x55ef19bb1c7d] [20.839] (EE) 5: /usr/lib/xorg/Xorg (0x55ef19b19000+0x582d6) [0x55ef19b712d6] [20.839] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fc802911830] [20.839] (EE) 7: /usr/lib/xorg/Xorg (_start+0x29) [0x55ef19b5b449] [20.839] (EE) [20.839] (EE) Segmentation fault at address 0x130 [20.839] (EE) Fatal server error: [20.839] (EE) Caught signal 11 (Segmentation fault). Server aborting [20.839] (EE) [20.839] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. I am using the nvidia drivers and they seem not to be loading for some reason. I need to use them for vdpau support. Here is where the X server tries to load the nvidia driver, from earlier in the same log file: ... [20.823] (II) xfree86: Adding drm device (/dev/dri/card0) [20.823] (II) xfree86: Adding drm device (/dev/dri/card1) [20.826] (--) PCI: (0:0:2:0) 8086:29c2:8086:5044 rev 2, Mem @ 0x9b40/524288, 0x8000/268435456, 0x9b30/1048576, I/O @ 0 x4430/8 [20.826] (--) PCI:*(0:1:0:0) 10de:128b:1462:8c93 rev 161, Mem @ 0x9a00/16777216, 0x9000/134217728, 0x9800/33554432, I/ O @ 0x3000/128, BIOS @ 0x/131072 [20.826] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere. [20.826] (II) "glx" will be loaded by default. [20.826] (II) LoadModule: "glx" [20.826] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [20.827] (II) Module glx: vendor="X.Org Foundation" [20.827]compiled for 1.19.6, module version = 1.0.0 [20.827]ABI class: X.Org Server Extension, version 10.0 [20.827] (==) Matched nvidia as autoconfigured driver 0 [20.828] (==) Matched nouveau as autoconfigured driver 1 [20.828] (==) Matched intel as autoconfigured driver 2 [20.828] (==) Matched nvidia as autoconfigured driver 3 [20.828] (==) Matched nouveau as autoconfigured driver 4 [20.828] (==) Matched modesetting as autoconfigured driver 5 [20.828] (==) Matched fbdev as autoconfigured driver 6 [20.828] (==) Matched vesa as autoconfigured driver 7 [20.828] (==) Assigned the driver to the xf86ConfigLayout [20.828] (II) LoadModule: "nvidia" [20.829] (WW) Warning, couldn't open module nvidia [20.829] (II) UnloadModule: "nvidia" [20.829] (II) Unloading nvidia [20.829] (EE) Failed to load module "nvidia" (module does not exist, 0) [20.829] (II) LoadModule: "nouveau" [20.829] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [20.830] (II) Module nouveau: vendor="X.Org Foundation" [20.830]compiled for 1.19.5, module version = 1.0.15 [20.830]Module class: X.Org Video Driver [20.830]ABI class: X.Org Video Driver, version 23.0 [20.830] (II) LoadModule: "intel" [20.830] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [20.830] (II) Module intel: vendor="X.Org Foundation" [20.830]compiled for 1.19.5, module version = 2.99.917 [20.830]Module class: X.Org Video Driver [20.830]ABI class: X.Org Video Driver, version 23.0 ... Steps I have taken: - reinstall xserver-xorg-hwe-16.04, xserver-xorg-core-hwe-16.04, xserver-xorg-video-all-hwe-16.04 and nvidia-384 - rebooted a few times to check for a race condition ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Sun Jul 28 22:23:42 2019 InstallationDate: Installed on 2016-11-12 (988 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display UpgradeStatus: No
[Touch-packages] [Bug 1838178] Re: Please upgrade to version 0.27
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1838178 Title: Please upgrade to version 0.27 Status in exiv2 package in Ubuntu: New Bug description: Skip version 0.26. Version 0.27 is already out with a newer lens db. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1838178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838181] Re: 3D Application cannot run anymore
For information the last update was: $ less /var/log/apt/history.log > Start-Date: 2019-07-28 08:23:57 > Commandline: aptdaemon role='role-commit-packages' sender=':1.107' > Install: xdg-desktop-portal-gtk:amd64 (1.0.2-0ubuntu1.1, automatic), > xdg-desktop-portal:amd64 (1.0.3-0ubuntu0.2, automatic) > Upgrade: language-pack-gnome-fr:amd64 (1:18.04+20190117, 1:18.04+20190718), > gir1.2-gtk-3.0:amd64 (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), > libegl1-mesa-dev:amd64 (18.2.8-0ubuntu0~18.04.2, 19.0.2-1ubuntu1.1~18.04.2), > sane-utils:amd64 (1.0.27-1~experimental3ubuntu2, > 1.0.27-1~experimental3ubuntu2.1), libegl-mesa0:amd64 > (18.2.8-0ubuntu0~18.04.2, 19.0.2-1ubuntu1.1~18.04.2), libgtk-3-common:amd64 > (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), libgtk-3-0:amd64 (3.22.30-1ubuntu3, > 3.22.30-1ubuntu4), libglapi-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libglapi-mesa:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), mesa-common-dev:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libxatracker2:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libegl1-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), language-pack-en:amd64 (1:18.04+20180712, > 1:18.04+20190718), language-pack-fr:amd64 (1:18.04+20190117, > 1:18.04+20190718), libgbm1:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libsane1:amd64 (1.0.27-1~experimental3ubuntu2, > 1.0.27-1~experimental3ubuntu2.1), libgtk-3-bin:amd64 (3.22.30-1ubuntu3, > 3.22.30-1ubuntu4), libwayland-egl1-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgail-3-0:amd64 (3.22.30-1ubuntu3, > 3.22.30-1ubuntu4), libgl1-mesa-dri:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-dri:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-glx:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-glx:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libsane-common:amd64 > (1.0.27-1~experimental3ubuntu2, 1.0.27-1~experimental3ubuntu2.1), > gtk-update-icon-cache:amd64 (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), > mesa-vdpau-drivers:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), mesa-va-drivers:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libglx-mesa0:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libglx-mesa0:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2) > End-Date: 2019-07-28 08:24:59 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838181 Title: 3D Application cannot run anymore Status in xorg package in Ubuntu: New Bug description: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: W6X73EA#ABF
[Touch-packages] [Bug 1838181] [NEW] 3D Application cannot run anymore
Public bug reported: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: W6X73EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** 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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838181 Title: 3D Application cannot run anymore Status in xorg package in Ubuntu: New Bug description: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP
[Touch-packages] [Bug 1838180] [NEW] apps use speakers when bluetooth headset is active (REGRESSION)
Public bug reported: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 22:59:01 2019 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0: Type: Primary Bus: USB BD Address: 48:89:E7:CF:4F:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:14153 acl:154 sco:0 events:971 errors:0 TX bytes:429273 acl:643 sco:0 commands:229 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1838180/+attachment/5279675/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) Status in bluez package in Ubuntu: New Bug description: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04
[Touch-packages] [Bug 1838178] [NEW] Please upgrade to version 0.27
Public bug reported: Skip version 0.26. Version 0.27 is already out with a newer lens db. ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1838178 Title: Please upgrade to version 0.27 Status in exiv2 package in Ubuntu: New Bug description: Skip version 0.26. Version 0.27 is already out with a newer lens db. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1838178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
