[Bug 1638473] Re: Blank screen after running oem-config
Confirming this does not happen to Ubuntu on the same machine, but does happen to Kubuntu. BTW: it does not happen when installing and then using it right away, but only if running an OEM-installation, then just rebooting and configuring or first pulling an image, writing back and configuring. So I suppose it is somehow caused by the OEM configuration for Kubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638473 Title: Blank screen after running oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638473] Re: Blank screen after running oem-config
Problem does NOT appear when selecting auto-logon in OEM-config on Dell Latitude E5410 in release 17.04. ** Description changed: + (See problem description with a virtual machine at the end) + Set up system to install with OEM-setup in German with no updates nor 3rd party software. Installed all available updates before preparing for OEM, shutting down and pulling a disk image with Clonezilla. After running graphical oem-config the system boots into a blank screen instead of the graphical login screen from SDDM. SDDM service is loaded, active, running. Text consoles are working, where the below apport-cli report and X-server log is from. Restoring from a disk image with Clonezilla shows the same brhavior. nomodeset does not help. Last working release was 14.04 LTS. + Installing Kubuntu without OEM works fine on the same machine and boots into SDDM. + + ProblemType: Bug + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + Date: Wed Nov 2 07:33:20 2016 + DistroRelease: Ubuntu 16.04 + HookError_source_ubiquity: + Traceback (most recent call last): +File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook + symb['add_info'](report, ui) +File "/usr/share/apport/package-hooks/source_ubiquity.py", line 60, in add_info + syslog = report['UbiquitySyslog'] +File "/usr/lib/python3.5/collections/__init__.py", line 986, in __getitem__ + raise KeyError(key) + KeyError: 'UbiquitySyslog' + + InstallationDate: Installed on 2016-10-31 (1 days ago) + InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + JournalErrors: + -- Logs begin at Mi 2016-11-02 06:55:19 CET, end at Mi 2016-11-02 07:30:01 CET. -- + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: RSDP 0x000FE300 24 (v02 DELL ) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: XSDT 0xCAFFDE18 7C (v01 DELL CBX3 06222004 MSFT 00010013) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: FACP 0xCAF87D98 F4 (v04 DELL CBX3 06222004 MSFT 00010013) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: DSDT 0xCAF55018 00885D (v02 INT430 SYSFexxx 1001 INTL 20090903) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: FACS 0xCAFE4E40 40 + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: FACS 0xCAFE4D40 40 + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: APIC 0xCAFFCF18 CC (v02 DELL CBX3 06222004 MSFT 00010013) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: TCPA 0xCAFE5D18 32 (v02 ) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0xCAF88A98 0002F9 (v01 DELLTP TPM 3000 INTL 20090903) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: MCFG 0xCAFE5C98 3C (v01 DELL SNDYBRDG 06222004 MSFT 0097) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: HPET 0xCAFE5C18 38 (v01 A M I PCHHPET 06222004 AMI. 0003) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: BOOT 0xCAFE5B98 28 (v01 DELL CBX3 06222004 AMI 00010013) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0xCAF6C018 000804 (v01 PmRef Cpu0Ist 3000 INTL 20090903) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0xCAF6B018 000996 (v01 PmRef CpuPm3000 INTL 20090903) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: DMAR 0xCAF87C18 E8 (v01 INTEL SNB 0001 INTL 0001) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SLIC 0xCAF75C18 000176 (v03 DELL CBX3 06222004 MSFT 00010013) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: 4 ACPI AML tables successfully acquired and loaded + Nov 02 06:55:19 username-Latitude-E6420 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' + Nov 02 06:55:19 username-Latitude-E6420 kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) + Nov 02 06:55:19 username-Latitude-E6420 kernel: #2 #3 + Nov 02 06:55:19 username-Latitude-E6420 kernel: PCCT header not found. + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: Dynamic OEM Table Load: + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0x880127FB3000 000727 (v01 PmRef Cpu0Cst 3001 INTL 20090903) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: Dynamic OEM Table Load: + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0x880127810C00 000303 (v01 PmRef ApIst3000 INTL 20090903) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: Dynamic OEM Table Load: + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0x880127FBAC00 000119 (v01 PmRef ApCst3000 INTL 20090903) + Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150930/hwxface-580) + Nov 02
[Bug 1638473] Re: Blank screen after running oem-config
Problem persists on Dell Latitude E5410 in release 17.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638473 Title: Blank screen after running oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638473] Re: Blank screen after running oem-config
It would have been nice to not replace my findings originally identified on hardware and replace it with virtual. Simply adding your findings would have been much more useful. Finding different hardware working fine does not make the problem disappear on hardware. And following that logic, as Darin had no failing setup, VMs would also not be affected? The last version this worked for me was 14.04. Had this problem on Dell Latitude E6400, E5410 and E6420. Tested now on a Dell Latitude E6400. It did not work with 16.04.1-desktop-amd64, so I freshly downloaded 16.04.2-desktop-amd64 and 16.10-desktop-amd64 for this bug (SHA256 OK, burnt to DVD with verification). It shows the same blank screen after running the OEM wizard, both from the installed OEM installation (by rebooting from disk after creating an image) AND from the restored CloneZilla image. Rebooting also shows a blank screen. When pressing Ctrl-Alt-Del or the power button the Kubuntu image is displayed, before rebooting/powering off. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1638473 Title: Blank screen after running oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1638473] Re: Blank screen after running oem-config
This happens on Dell Latitude E6400 and E6420. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638473 Title: Blank screen after running oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638473] Re: Blank screen after running oem-config
** Summary changed: - Blank screen after running oem-config in some virtual machine setups + Blank screen after running oem-config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638473 Title: Blank screen after running oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638473] Re: Blank screen after running oem-config
This bug seems to happen especially with Kubuntu: Tested with Ubuntu 16.04.1 + newest updates on the same system and working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638473 Title: Blank screen after running oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638473] [NEW] Blank screen after running oem-config
Public bug reported: Set up system to install with OEM-setup in German with no updates nor 3rd party software. Installed all available updates before preparing for OEM, shutting down and pulling a disk image with Clonezilla. After running graphical oem-config the system boots into a blank screen instead of the graphical login screen from SDDM. SDDM service is loaded, active, running. Text consoles are working, where the below apport-cli report and X-server log is from. Restoring from a disk image with Clonezilla shows the same brhavior. nomodeset does not help. Last working release was 14.04 LTS. Installing Kubuntu without OEM works fine on the same machine and boots into SDDM. ProblemType: Bug ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 2 07:33:20 2016 DistroRelease: Ubuntu 16.04 HookError_source_ubiquity: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_ubiquity.py", line 60, in add_info syslog = report['UbiquitySyslog'] File "/usr/lib/python3.5/collections/__init__.py", line 986, in __getitem__ raise KeyError(key) KeyError: 'UbiquitySyslog' InstallationDate: Installed on 2016-10-31 (1 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: -- Logs begin at Mi 2016-11-02 06:55:19 CET, end at Mi 2016-11-02 07:30:01 CET. -- Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: RSDP 0x000FE300 24 (v02 DELL ) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: XSDT 0xCAFFDE18 7C (v01 DELL CBX3 06222004 MSFT 00010013) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: FACP 0xCAF87D98 F4 (v04 DELL CBX3 06222004 MSFT 00010013) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: DSDT 0xCAF55018 00885D (v02 INT430 SYSFexxx 1001 INTL 20090903) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: FACS 0xCAFE4E40 40 Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: FACS 0xCAFE4D40 40 Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: APIC 0xCAFFCF18 CC (v02 DELL CBX3 06222004 MSFT 00010013) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: TCPA 0xCAFE5D18 32 (v02 ) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0xCAF88A98 0002F9 (v01 DELLTP TPM 3000 INTL 20090903) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: MCFG 0xCAFE5C98 3C (v01 DELL SNDYBRDG 06222004 MSFT 0097) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: HPET 0xCAFE5C18 38 (v01 A M I PCHHPET 06222004 AMI. 0003) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: BOOT 0xCAFE5B98 28 (v01 DELL CBX3 06222004 AMI 00010013) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0xCAF6C018 000804 (v01 PmRef Cpu0Ist 3000 INTL 20090903) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0xCAF6B018 000996 (v01 PmRef CpuPm3000 INTL 20090903) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: DMAR 0xCAF87C18 E8 (v01 INTEL SNB 0001 INTL 0001) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SLIC 0xCAF75C18 000176 (v03 DELL CBX3 06222004 MSFT 00010013) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: 4 ACPI AML tables successfully acquired and loaded Nov 02 06:55:19 username-Latitude-E6420 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Nov 02 06:55:19 username-Latitude-E6420 kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) Nov 02 06:55:19 username-Latitude-E6420 kernel: #2 #3 Nov 02 06:55:19 username-Latitude-E6420 kernel: PCCT header not found. Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: Dynamic OEM Table Load: Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0x880127FB3000 000727 (v01 PmRef Cpu0Cst 3001 INTL 20090903) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: Dynamic OEM Table Load: Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0x880127810C00 000303 (v01 PmRef ApIst3000 INTL 20090903) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: Dynamic OEM Table Load: Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: SSDT 0x880127FBAC00 000119 (v01 PmRef ApCst3000 INTL 20090903) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150930/hwxface-580) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150930/hwxface-580) Nov 02 06:55:19 username-Latitude-E6420 kernel: ACPI: Enabled 2 GPEs in block 00 to 3F Nov 02 06:55:19 username-Latitude-E6420 kernel: i804
