[Desktop-packages] [Bug 1838181] Re: 3D Application cannot run anymore
linux-generic-hwe-18.04 will switch to 5.0 soon. linux-generic-hwe-18.04-edge can be used to switch to v5.0 kernel right away. -- You received this bug notification because you are a member of Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid ** Summary changed: - apps use speakers when bluetooth headset is active (REGRESSION) + apps use speakers when bluetooth headset is active (regression in kernel 5.0, but 5.2 works) ** Summary changed: - apps use speakers when bluetooth headset is active (regression in kernel 5.0, but 5.2 works) + [Intel 9260] apps use speakers when bluetooth headset is active (regression in kernel 5.0, but 5.2 works) ** Tags added: bluetooth ** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: [Intel 9260] apps use speakers when bluetooth headset is active (regression in kernel 5.0, but 5.2 works) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to pulseaudio 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 -- Mai
[Desktop-packages] [Bug 1838226] [NEW] Hexadecimal numbers ending with AC not working
Public bug reported: This bug affects hexadecimal numbers in "Programming mode": If a hexadecimal line ends with the hexadecimal digits "AC", the calculator interprets this as "Acos" and refuses input. Maybe other combinations of hexadecimal digits have a similar effect. Example: 9A+D7+AC As a work-around "+0" can be added to the line: 9A+D7+AC+0 ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1838226 Title: Hexadecimal numbers ending with AC not working Status in gnome-calculator package in Ubuntu: New Bug description: This bug affects hexadecimal numbers in "Programming mode": If a hexadecimal line ends with the hexadecimal digits "AC", the calculator interprets this as "Acos" and refuses input. Maybe other combinations of hexadecimal digits have a similar effect. Example: 9A+D7+AC As a work-around "+0" can be added to the line: 9A+D7+AC+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1838226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
If any comments are not meant to be on this page then please click "Hide". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). NOTE: Please disregard comments #2 through #5 below, they were intended for a differenb bugrep. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
@Daniel Ach! Sorry, I posted to the wrong bug report. Please disregard comments #2 through #5 (when processing this bug report). ** Description changed: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... - STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: - Speakericon->Bluetoothicon->Gluetooth settings + Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). + + NOTE: Please disregard comments #2 through #5 below, they were intended + for a differenb bugrep. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). NOTE: Please disregard comments #2 through #5 below, they were intended for a differenb bugrep. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724901] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput()
** Also affects: xorg-server-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() + Xorg crashed with SIGSEGV in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() ** Changed in: xorg-server-hwe-16.04 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1724901 Title: Xorg crashed with SIGSEGV in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server-hwe-16.04 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d10c2e09338f4f04f7439218fd0b1fff3abaebd8 --- Launching ubuntu 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Oct 19 13:43:23 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 540M] [1025:0505] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Aspire 5750G ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=65719b3f-c720-46a5-8489-b9a337a5bd78 ro quiet splash vt.handoff=7 Renderer: Software Signal: 6 SourcePackage: xorg-server StacktraceTop: RRProviderAutoConfigGpuScreen () InitOutput () ?? () __libc_start_main (main=0x55bf0e466af0, argc=12, argv=0x7ffd8d73d578, init=, fini=, rtld_fini=, stack_end=0x7ffd8d73d568) at ../csu/libc-start.c:308 _start () Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/09/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd08/09/2012:svnAcer:pnAspire5750G:pvrV1.21:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.21: dmi.product.name: Aspire 5750G dmi.product.version: V1.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724901] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput()
** Summary changed: - Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() + Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() ** Description changed: + https://errors.ubuntu.com/problem/d10c2e09338f4f04f7439218fd0b1fff3abaebd8 + + --- + Launching ubuntu 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Oct 19 13:43:23 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504] - NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 540M] [1025:0505] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504] + NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 540M] [1025:0505] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Aspire 5750G ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=65719b3f-c720-46a5-8489-b9a337a5bd78 ro quiet splash vt.handoff=7 Renderer: Software Signal: 6 SourcePackage: xorg-server StacktraceTop: - RRProviderAutoConfigGpuScreen () - InitOutput () - ?? () - __libc_start_main (main=0x55bf0e466af0, argc=12, argv=0x7ffd8d73d578, init=, fini=, rtld_fini=, stack_end=0x7ffd8d73d568) at ../csu/libc-start.c:308 - _start () + RRProviderAutoConfigGpuScreen () + InitOutput () + ?? () + __libc_start_main (main=0x55bf0e466af0, argc=12, argv=0x7ffd8d73d578, init=, fini=, rtld_fini=, stack_end=0x7ffd8d73d568) at ../csu/libc-start.c:308 + _start () Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/09/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd08/09/2012:svnAcer:pnAspire5750G:pvrV1.21:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.21: dmi.product.name: Aspire 5750G dmi.product.version: V1.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Tags removed: artful ** Tags added: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1724901 Title: Xorg crashed with SIGSEGV in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server-hwe-16.04 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d10c2e09338f4f04f7439218fd0b1fff3abaebd8 --- Launching ubuntu 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3
[Desktop-packages] [Bug 1742101] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() from dix_main() from __libc_start_main()
*** This bug is a duplicate of bug 1724901 *** https://bugs.launchpad.net/bugs/1724901 ** This bug has been marked a duplicate of bug 1724901 Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1742101 Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() from dix_main() from __libc_start_main() Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.19.5-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/d10c2e09338f4f04f7439218fd0b1fff3abaebd8 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/xorg-server/+bug/1742101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to xorg-server 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]com
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packa
[Desktop-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 Desktop Packages, which is subscribed to pulseaudio 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
Your original bug report here was about an assertion failure. If that's no longer happening then this bug should be closed and a new one opened for the remaining problem. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
Still a problem: When BT is turned "Off" in Ubuntu (using the speaker- icon thingie), the BT does not immediately report disconnection; but when BT it turned ON again in Ubuntu, *then* the headset says it lost the connection. (and at that point the original problem is present, where Ubuntu says it is connected to the headset but sounds go to the speakers instead). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs Status in gnome-shell package in Ubuntu: New Bug description: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Thanks for the bug report. If you would like the bug fixed in 18.04 then please click the above link "Nominate for series". ** Tags added: bionic ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #470 https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 Importance: Unknown Status: Unknown ** Tags added: fixed-in-3.31.90 fixed-upstream ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Disco) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
I found that removing the following "fixed" the problem: $HOME/.cache $HOME/.config/pulse $HOME/.config/sound-juicer $HOME/.gconf Don't know what exactly is(was) the problem. However I backed up my homedir first, so I can attach any of the deleted files here if that would be helpful. @devs Please let me know if you want that. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs Status in gnome-shell package in Ubuntu: New Bug description: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height
** Also affects: diodon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1830422
Title:
Shell boxpointer menus don't have scroll buttons when they exceed the
screen height
Status in diodon package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
Opinion
Status in gnome-shell-extension-appindicator package in Ubuntu:
Confirmed
Bug description:
I am using appindicator-1.0 in conjunction with Gtk+2.0 menu. Menu
consist of constant items and many dynamically added items. If the
screen pixel resolution is not so good as it must be then the last
menu items are not visible. Ubuntu 16.04 automatically add top and
bottom bars with "^" and "v" arrows to scroll menu when mouse pointer
is over these bars. But in Linux Ubuntu 18.04 (and 19.04 too) such
scrolling bars are not appearing.
On the other hand menu scrolling is working fine anywhere into usual
GTK window with menu bar (without using appindicator). Ubuntu 16.04
and Ubuntu 18.04 use the same 12.10.1 libappindicator version.
Here is the test c program which illustrates the issue. It works fine
in Linux Ubuntu 16.04 and has the described above problem in Linux
18.04:
#include
#include
#define LOGO_PNG "/home/super/my-project/menu-test/logo.png"
AppIndicator* c_indicator;
GtkWidget* c_menu;
void menu_quit_cb(GtkMenuItem* menuitem, gpointer user_data)
{
gtk_main_quit();
}
int main(int argc, char *argv[])
{
gtk_init(&argc, &argv);
int i;
GtkWidget* item;
char title[128];
c_menu = gtk_menu_new();
item = gtk_menu_item_new_with_label("Quit");
g_signal_connect(item, "activate", G_CALLBACK(menu_quit_cb), NULL);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu),
gtk_separator_menu_item_new());
for (i = 1; i <= 100; ++i) {
snprintf(title, sizeof(title), "Item #%03u", i);
item = gtk_menu_item_new_with_label(title);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
}
//
c_indicator = app_indicator_new("Menu Test", LOGO_PNG,
APP_INDICATOR_CATEGORY_APPLICATION_STATUS);
app_indicator_set_status(c_indicator, APP_INDICATOR_STATUS_ACTIVE);
app_indicator_set_icon(c_indicator, LOGO_PNG);
app_indicator_set_menu(c_indicator, GTK_MENU(c_menu));
gtk_main();
return 0;
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libappindicator1 12.10.1+18.04.20180322.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 21:15:59 2019
InstallationDate: Installed on 2018-07-03 (325 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libappindicator
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/diodon/+bug/1830422/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/158384
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to gnome-shell 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 /org/freedesktop/NetworkManager/Devices/2
[Desktop-packages] [Bug 1067111] Re: Searching within many subfolders freezes Desktop
On ubuntu 18.04 LTS, the system freezes when you write something on nautilus. The search is being made on the main thread, which breaks any possible interaction with nautilus. Users used to the old way of searching a file inside the current folder, will get their system blocked many times because of this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1067111 Title: Searching within many subfolders freezes Desktop Status in nautilus package in Ubuntu: Fix Released Bug description: Linux cyrex 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux GNOME nautilus 3.4.2 If I do a search for jpg file for example within a folder that contains around 5000 folders and each one has about 5000 files the desktop and anything related to Nautilus first starts to take longer to respond. After 10 to 15 minutes the whole system freezes until the search is done. In this case the search took 45 minutes which means that I could not interact with anything at least for 30 minutes. The way I was thinking is that the search should not affect the performance on the Desktop or other Nautilus windows. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 15 17:41:00 2012 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1012x553+207+84'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'184' b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true' InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to quantal on 2012-10-01 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1067111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838200] [NEW] Firefox notifications windows will stay on the display when I open other apps
Public bug reported: You can see video that appears this problem below (in comments). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 19:09:48 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-07-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190726) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1838200 Title: Firefox notifications windows will stay on the display when I open other apps Status in firefox package in Ubuntu: New Bug description: You can see video that appears this problem below (in comments). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 19:09:48 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-07-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190726) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838200] Re: Firefox notifications windows will stay on the display when I open other apps
** Attachment added: "simplescreenrecorder-2019-07-28_19.08.38.mkv" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838200/+attachment/5279738/+files/simplescreenrecorder-2019-07-28_19.08.38.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1838200 Title: Firefox notifications windows will stay on the display when I open other apps Status in firefox package in Ubuntu: New Bug description: You can see video that appears this problem below (in comments). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 19:09:48 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-07-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190726) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832811] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1832811 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in seahorse package in Ubuntu: New Bug description: Seahorse app has crashed ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:02:49 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f21b50c8588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f21b514e02d "!t->dead", file=0x7f21b514e000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f21b514e02d "!t->dead", file=0x7f21b514e000 "glib-watch.c", line=195, function=0x7f21b514e1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1832811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837945] Re: AMD RX 570 Black Screen at boot
Thanks for your feedback. Please post a link here to the upstream bug report once you filed it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1837945 Title: AMD RX 570 Black Screen at boot Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 Problem: Booting from live media OR installed ubuntu fails with a blank, black screen and total system hang. How to reproduce: Using AMDGpu driver and AMD 4th Gen GCN GPU, try to boot Ubuntu 19.04 (or 18.04) Resolution: Manually updating kernel to 5.1 and adding the "amdgpu.dc=0" kernel boot parameter seems to fix the problem. inxi -SGxxx Output: System: Host: Kernel: 5.1.0-050100-generic x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.1 wm: gnome-shell dm: GDM3 3.32.0 Distro: Ubuntu 19.04 (Disco Dingo) Graphics: Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X] driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67df Display: x11 server: X.Org 1.20.4 driver: ati,fbdev unloaded: modesetting,radeon,vesa compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.30.0 5.1.0-050100-generic LLVM 8.0.0) v: 4.5 Mesa 19.0.2 direct render: Yes --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: disco DistroRelease: Ubuntu 19.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:0b31] InstallationDate: Installed on 2019-07-26 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: System manufacturer System Product Name Package: xserver-xorg-video-amdgpu 19.0.1-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=d779e62a-1fa2-404f-97a3-5649f11998c2 ro quiet splash amdgpu.dc=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Tags: disco ubuntu Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5007 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K 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.:bvr5007:bd06/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1837945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838199] [NEW] Firefox ESR in esr/stable channel is never updated by Ubuntu
Public bug reported: Hi, I am encountering a severe issue on several Ubuntu 18.04.2 machines where I have replaced Firefox by Firefox ESR through "Ubuntu Software Center" by selecting esr/stable channel as described in https://ubuntu.com/blog/firefox-esr-60-on-ubuntu After being installed, Firefox ESR is working as expected but it is never updated. I mean Firefox ESR is detecting that a new version is available when starting. Even "Ubuntu Software Center" shows a newer version exists. But when I run either sudo apt-get update sudo apt-get upgrade or "Software Updater", Ubuntu is never updating the Firefox ESR. I have reproduced this on 3 different machines running Ubuntu 18.04.2. I am not sure if it is the right place to submit this problem report. Are you aware of this issue ? Thanks Kind regards ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1838199 Title: Firefox ESR in esr/stable channel is never updated by Ubuntu Status in firefox package in Ubuntu: New Bug description: Hi, I am encountering a severe issue on several Ubuntu 18.04.2 machines where I have replaced Firefox by Firefox ESR through "Ubuntu Software Center" by selecting esr/stable channel as described in https://ubuntu.com/blog/firefox-esr-60-on-ubuntu After being installed, Firefox ESR is working as expected but it is never updated. I mean Firefox ESR is detecting that a new version is available when starting. Even "Ubuntu Software Center" shows a newer version exists. But when I run either sudo apt-get update sudo apt-get upgrade or "Software Updater", Ubuntu is never updating the Firefox ESR. I have reproduced this on 3 different machines running Ubuntu 18.04.2. I am not sure if it is the right place to submit this problem report. Are you aware of this issue ? Thanks Kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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.
[Desktop-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 Desktop 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 few times to
[Desktop-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 upgra
[Desktop-packages] [Bug 1836462] Re: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications
** This bug is no longer a duplicate of bug 1837783 Navigating directly back kills performance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/1836462 Title: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications Status in xdg-user-dirs package in Ubuntu: New Status in xdg-user-dirs package in Fedora: Unknown Bug description: Renaming "Templates" to "# Templates" fixes a lot of speed issues in a range of desktop applications, e.g. file managers, text editors, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
Can you please boot Ubuntu with default kernel, and with kernel parameter `usbcore.dyndbg=+p`, reproduce the issue, and attach dmesg? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/
[Desktop-packages] [Bug 1838184] Re: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1838184 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: xx ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Jul 28 10:49:49 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-12-26 (578 days ago) InstallationMedia: It Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-07-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1838184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838184] [NEW] package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: xx ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Jul 28 10:49:49 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-12-26 (578 days ago) InstallationMedia: It Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-07-28 (0 days ago) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1838184 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: xx ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Jul 28 10:49:49 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-12-26 (578 days ago) InstallationMedia: It Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-07-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1838184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830744] Re: Stuck in 1024x768 resolution. Modeset can't detect VGA EDID on Ivybridge.
Daniel & Launchpad Janitor, Thanks for your response. I am using HP workstation and checking drivers & changing display options doesn't solved the issue. When I installed Manjaro using different hard SSD it gave me proper resolution. Then I updated from 18.04 to 19.04, using updater option. It went to 18.10 first and then 19.04 & That solved the issue and now I am getting full resolution. Thanks for your support and response. Community rocks. ** Changed in: linux (Ubuntu) Status: Expired => Fix Released ** Changed in: xorg-server (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1830744 Title: Stuck in 1024x768 resolution. Modeset can't detect VGA EDID on Ivybridge. Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: Hey Support , I am not able to get resolution of my Monitor which is 1080P, I checked with the cables and its all good. I think drivers are causing this issue. Might need help with that. Regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 28 20:04:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [103c:339a] InstallationDate: Installed on 2019-03-12 (77 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: SGH333S866 dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: SGH333S866 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 SFF dmi.product.sku: QV985AV dmi.sys.vendor: Hewlett-Packard 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~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1~18.04.1 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/1830744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 dmi.product.version:
[Desktop-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 Desktop 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.v
