[Bug 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply

A bios update is not always available in a 60 days time life! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860761 Title: Dell XPS 13 - Bios upgrade not working - Always ask for power supply To ma

[Bug 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply

Well, have to wait for next bios update. If it help, attached you will find upower when discharging and charging, around 15 seconds between the 2 output ** Attachment added: "upower.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860761/+attachment/5324168/+files/upower.tx

[Bug 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply

Hi Sebastien. While rebooting to have a clear journalctl output to send you, the updates work and I found why. Battery has to be 100% charged. While still on power, reboot the machine, do the upgrade, reboot and finally the BIOS gets upgraded. After last reboot you can remove the power supply. Sh

[Bug 1860761] [NEW] Dell XPS 13 - Bios upgrade not working - Always ask for power supply

Public bug reported: Each time the notebook starts I'm advised that a new bios upgrade is out: XPS 13 7390 System Update 0.1.3.1 => 0.1.4.0 Problem is that when I ask for update, I always get this message (traduction from french): Not possible to upgrade "XPS 13 7390 System Update": connect powe

[Bug 1801747] Re: External display not recognized, internal one goes to black

More infos. I installed the notebook from scratch with a 16.04.2 image and update to latest 16.04 packages which installed 4.15.0-38 kernel. The laptop has the correct behavior, without entering settings I can switch/duplicate displays with the fn key. So original problem seems not related to kern

[Bug 1801747] Re: External display not recognized, internal one goes to black

Ubuntu 18.10 does have the same problem, Ubuntu 16.04.2 has *NO* problem. From where could I get an 4.4 kernel for 18.04 for testing purpose ? Other infos: when I check in systems, it show me 3 display despite the fact that only 2 are connected: 1. internal display 2. unknown display with resolut

[Bug 1801747] Re: External display not recognized, internal one goes to black

** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this

[Bug 1801747] Re: External display not recognized, internal one goes to black

Err: to read is "I can see the image on one or the other display" ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subs

[Bug 1801747] Re: External display not recognized, internal one goes to black

Behavior is different, Ican't see the image on one or the other display, system now recognize the second screen but as soon as I switch the screens keyboard freezes, mouse icon react but no button working, have to switch off the computer with the on/off button :( Daniel -- You received this bug

[Bug 1801747] Re: External display not recognized, internal one goes to black

Hi Cristian. No update/upgrade, straight HDD format + new install of Ubuntu. I will test the latest kernel. Thanks for your support Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title

[Bug 1798868] Re: Compiz Crashed with SIGSEGV [Radeon]

I have the same problem, needed datas were given at https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/comments/68 Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798868 Title: Compi

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

I did the all stuff again and first crashed gnome-shell then Xwayland. gdm3 is still running with the same PID but gdm-wayland-session PID change after few seconds. Example: 821 ?Ssl0:00 /usr/sbin/gdm3 3911 pts/3S+ 0:00 grep --color=auto gdm3 3935 tty1 Ssl+ 0:00 /usr/

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

Hi, here is the detail of what happend: - remove all files from /var/crash - restart computer, the Ubuntu screen with the dots is shown - when time of greeting appears in /var/crash _usr_bin_Xwayland.124.crash and .lock files - some seconds after appears _usr_bin_gnome-shell.124.crash in this dir

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

I ran lsof, max display lines I saw (sudo lsof |wc -l) are near of 22000. Attached is an lsof runned after I restart gdm3 Daniel ** Attachment added: "lsof_1597150.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+attachment/5185622/+files/lsof_1597150.log -- You received th

[Bug 1790870] Re: No X display - gdm3 crash with segfault

*** This bug is a duplicate of bug 1791023 *** https://bugs.launchpad.net/bugs/1791023 Bug #1791023 is the crash report after having applied the workaround. It's now against gdm3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. ht

[Bug 1790870] Re: No X display - gdm3 crash with segfault

I tried point 2. Here are the links: >From 18.04 version https://errors.ubuntu.com/oops/c20dade6-b1a0-11e8-8fa5-fa163ee63de6 https://errors.ubuntu.com/oops/da31709a-b19f-11e8-8fa5-fa163ee63de6 >From 16.04 version https://errors.ubuntu.com/oops/01680142-9cae-11e8-b517-fa163e0ec2f1 https://errors

[Bug 1790870] Re: No X display - gdm3 crash with segfault

Hi Daniel, I found 2 files: /var/crash/_usr_bin_gnome-shell.124.crash and /var/crash/_usr_bin_Xwayland.124.crash that I sended them with ubuntu- bug but after this I never got new bugs ID :( Two new files appeard with extension .upload and they are empty. There is also a .lock file in this directo

[Bug 1790870] [NEW] No X display - gdm3 crash with segfault

Public bug reported: This desktop was running 16.04.5 version and started few weeks ago to have the desktop crashing. In dmesg I saw compiz segfault at 0 ip [...] error 4. I decide to upgrade to 18.04.1 to solve this problem but it's still there: gnome-shell at 0 ip [...] error 4 In 18.04 i even

[Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 I too have this bug. I use radeon module for 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] Error is compiz[12038]: segfault at 38c ip

[Bug 1778053] Re: No sound in Firefox with HDMI unplugged as 1st peripheral

Even worst: just tried to activate again unplugged HDMI which was then second of the list in pavucontrol, Firefox uses HDMI audio and not the internal audio device ! So only switching off HDMI gives sound back in Firefox. -- You received this bug notification because you are a member of Ubuntu Bu

[Bug 1778053] [NEW] No sound in Firefox with HDMI unplugged as 1st peripheral

Public bug reported: On a computer having HDMI output, when HDMI is shown as unplugged and HDMI Internal Audio is the first device in the list shown via pavucontrol, Firefox doesn't use next available audio device. Chrome or VLC are dealing OK with the same setup. ProblemType: Bug DistroRelease: