[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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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.txt -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. Should this be the correct behavior ? Daniel -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 power supply. Battery can be full, notebook connected on power supply, doesn't matter, will not upgrade. Daniel Ubuntu 18.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-software 3.28.1-0ubuntu4.18.04.14 ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18 Uname: Linux 4.15.0-1066-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 09:15:31 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (47 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 kernel version. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 resolution 1024 x 768 (4:3) 800 x 600 (4:3) 848 x 480 (16:9) ! 3. external display with correct informations (Brand, model, ) I also discover that starting the laptop with the display connected, shows me the splash image on both displays as it should. Problem arise on greeting image. From here I see "No input signal" and the external display goes black. Daniel PS: perhaps bug 1723025? could be identical but from my side, I can start with or without external display, it's only when I use the fn switch key that problem arise. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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: Compiz Crashed with SIGSEGV [Radeon] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1798868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart severine@JS-PC:~$ sudo ps ax|grep gdm3 821 ?Ssl0:00 /usr/sbin/gdm3 4486 tty1 Ssl+ 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart 4551 pts/3S+ 0:00 grep --color=auto gdm3 severine@JS-PC:~$ sudo ps ax|grep gdm3 821 ?Ssl0:00 /usr/sbin/gdm3 4662 tty1 Ssl+ 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart 4811 pts/3S+ 0:00 grep --color=auto gdm3 After a while, around 20~30 min, gdm-wayland-session is no more running Attached is the log file before I killed gdm3 Do you not prefer that I send you the gnome-shell and Xwayland crash files ? Daniel ** Attachment added: "lsof_1597150.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+attachment/5185963/+files/lsof_1597150.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597150 Title: 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() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 directory - after a long time, eg 15min, no other crash - I ran lsof and killed gdm3 PID with kill -9 (attached lsof file) - appears in /var/crash _usr_lib_xorg_Xorg.0.crash If the log fiel is still unusable I could perhaps try the command you told me yesterday: ubuntu-bug _usr_bin_Xwayland.124.crash ubuntu-bug _usr_bin_gnome-shell.124.crash Please advice. Daniel ** Attachment added: "lsof_1597150.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+attachment/5185946/+files/lsof_1597150.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597150 Title: 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() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597150 Title: 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() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. https://bugs.launchpad.net/bugs/1790870 Title: No X display - gdm3 crash with segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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.ubuntu.com/oops/8380e58a-9ca5-11e8-add5-fa163e54c21f https://errors.ubuntu.com/oops/2a8c663e-9a57-11e8-aaf2-fa163ef911dc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790870 Title: No X display - gdm3 crash with segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 directory. Where did I do something wrong ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790870 Title: No X display - gdm3 crash with segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 don't get the desktop, only the mouse indicator is visible, disappearing from time to time (seems on each crash). Attached is the output of an radeontool dump. The desktop is unusable in graphic mode. Daniel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Wed Sep 5 14:40:14 2018 DistUpgraded: 2018-09-05 13:03:08,966 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2016-03-03 (916 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160227) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=8c2df27f-cbc4-4c8d-a4f1-dc7994b41016 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago) dmi.bios.date: 04/18/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.22 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8312220 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.22:bd04/18/2007:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Sep 5 08:36:00 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 inputHP WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "regdump_broke.txt" https://bugs.launchpad.net/bugs/1790870/+attachment/5184947/+files/regdump_broke.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790870 Title: No X display - gdm3 crash with segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1790870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 7f2dbc01a2c9 sp 7fff9bbce640 error 4 I installed ubuntu-gnome-desktop but this failed too with a segfault What I find out is that after a long time, flashing is stopping but desktop is not complete (eg not all icons nor launcher are displayed). >From this time mouse or keyboard are responding but after a while everything is frozen. Another think: if I remove linux-modules-extra from lets say 4.4.0-124-generic kernel, the problem disappear! No luck for me, I need this package for my network card ;) I installed the xenial-proposed repo which gave 4.4.0-132 kernel, problem is still there. Attached is the file from /var/crash Thanks to find a solution, computer is unusable :( Daniel ** Attachment added: "_usr_bin_compiz.1000.crash" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+attachment/5173795/+files/_usr_bin_compiz.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1741447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778053 Title: No sound in Firefox with HDMI unplugged as 1st peripheral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1778053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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: Ubuntu 16.04
Package: firefox 60.0.2+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dh 2959 F pulseaudio
/dev/snd/controlC1: dh 2959 F pulseaudio
BuildID: 20180607194748
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Jun 21 14:21:57 2018
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20130203-1
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IncompatibleExtensions:
Français Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-10-13 (1711 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
20130203-13:50
MostRecentCrashID: bp-d82a4599-b0db-421e-a6f9-ec0d41180518
Plugins: Shockwave Flash -
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so
(browser-plugin-freshplayer-pepperflash)
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=fr_FR
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.0.2/20180607194748 (In use)
RelatedPackageVersions: browser-plugin-freshplayer-pepperflash
0.3.5-1~webupd8~trusty~3
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-d82a4599-b0db-421e-a6f9-ec0d41180518
bp-e2fac577-1120-4fb7-a01d-c8b062161102
bp-e938d96b-66a8-483e-8cae-d8f072161031
UpgradeStatus: Upgraded to xenial on 2016-10-05 (623 days ago)
dmi.bios.date: 12/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A23
dmi.board.name: 0JNYGR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA23:bd12/15/2017:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0JNYGR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778053
Title:
No sound in Firefox with HDMI unplugged as 1st peripheral
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1778053/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
