[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
This seems to have been fixed as of latest nvidia drivers or recent Ubuntu packages updates, at least I'm not observing it anymore since this weekend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015059] [NEW] Dead zone below the tray icon area
Public bug reported: Since upgrading to Ubuntu 23.04, I have an issue where the zone below tray icons is partly blocked by some transparent dead zone. With AnyDesk open and its tray icon in the bar, clicking below the tray icon (on a window title for example) triggers the click event on the AnyDesk tray icon, and opens the AnyDesk software. With AnyDesk closed (and the tray icon missing), the dead zone is still present, however clicking on it does nothing. You'll find attached a screenshot showcasing the dead zone (marked in orange, it is invisible), I can't click within this dead zone. When I have a maximized window for example, I can't click on the window buttons. I tried resetting all gnome-related dconf settings after upgrading, to no avail. It worked perfectly fine with Ubuntu 22.10. Here are Gnome-related packages versions I currently have installed: ``` $ dpkg -l | grep gnome rc chrome-gnome-shell 10.1-5 all GNOME Shell extensions integration for web browsers ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator1:44.0-1ubuntu1 amd64GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center1:44.0-1ubuntu4 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4 all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0-1
[Desktop-packages] [Bug 2015061] [NEW] Corrupted/missing windows title background when opening windows
Public bug reported: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re- focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator1:44.0-1ubuntu1 amd64GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center1:44.0-1ubuntu4 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4 all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0-1 amd64viewer for the systemd journal ii gnome-mahjongg
[Desktop-packages] [Bug 2015061] Re: Corrupted/missing windows title background when opening windows
apport information ** Tags added: apport-collected ** Description changed: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re- focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0
[Desktop-packages] [Bug 2015061] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660355/+files/GsettingsChanges.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660356/+files/ProcCpuinfoMinimal.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1
[Desktop-packages] [Bug 2015061] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660358/+files/ShellJournal.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660357/+files/ProcEnviron.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660359/+files/monitors.xml.txt -- 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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of journalctl -b0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660743/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of lspci -k Please note that this happens consistently, it's not random or a rare occurrence. After boot, opening Thunderbird for example makes it lack the title bar background immediately. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660750/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Yup, I have seen a few (rare and random this time) crashes when pressing the Activities corner button (or super shortcut key). It indeed restarts quickly after that, but I assumed it was linked to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 Let me know if I can provide any other info or help :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1
[Desktop-packages] [Bug 1767740] [NEW] gnome-shell crashes at startup - segfault in nouveau_dri.sn
Public bug reported: With a live USB stick or a freshly installed version of 18.04, gnome- shell crashes at startup. I get this error in dmesg: gnome-shell[]: segfault at xx ip xx sp xx error 4 in nouveau_dri.so[] The computer is a MacBook Pro with a GeForce 320M GPU. Using the proprietary driver listed in the "additional drivers" tab doesn't work either (I get a black screen at startup with no access to a virtual terminal). Everything was fine on 16.04, with nouveau or nvidia drivers. The only workaround is to blacklist the nouveau driver. I have of course very poor performance then. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 01:34:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro7,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8a41bdcd-9c0e-41b3-8111-94661a72e400 ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0B.1006012305 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0B.1006012305:bd06/01/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Affects: mesa (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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767740 Title: gnome-shell crashes at startup - segfault in nouveau_dri.sn Status in mesa package in Ubuntu: New Bug description: With a live USB stick or a freshly installed version of 18.04, gnome- shell crashes at startup. I get this error in dmesg: gnome-shell[]: segfault at xx ip xx sp xx error 4 in nouveau_dri.so[] The computer is a MacBook Pro with a GeForce 320M GPU. Using the proprietary driver listed in the "additional drivers" tab doesn't work either (I get a black screen at startup with no access to a virtual terminal). Everything was fine on 16.04, with nouveau or nvidia drivers. The only workaround is to blacklist the nouveau driver. I have of course very poor performance then. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 01:34:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: A
[Desktop-packages] [Bug 1767740] Re: gnome-shell crashes at startup - segfault in nouveau_dri.so
** Summary changed: - gnome-shell crashes at startup - segfault in nouveau_dri.sn + gnome-shell crashes at startup - segfault in nouveau_dri.so -- 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/1767740 Title: gnome-shell crashes at startup - segfault in nouveau_dri.so Status in mesa package in Ubuntu: New Bug description: With a live USB stick or a freshly installed version of 18.04, gnome- shell crashes at startup. I get this error in dmesg: gnome-shell[]: segfault at xx ip xx sp xx error 4 in nouveau_dri.so[] The computer is a MacBook Pro with a GeForce 320M GPU. Using the proprietary driver listed in the "additional drivers" tab doesn't work either (I get a black screen at startup with no access to a virtual terminal). Everything was fine on 16.04, with nouveau or nvidia drivers. The only workaround is to blacklist the nouveau driver. I have of course very poor performance then. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 01:34:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro7,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8a41bdcd-9c0e-41b3-8111-94661a72e400 ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0B.1006012305 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0B.1006012305:bd06/01/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1767740/+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 1390709] Re: Wifi doesn't reconnect after waking from sleep
For me it happens on Ubuntu 18.04.
I'm on a surfacebook.
Directly if my pc go sleep, i lost the wifi connection.
I've to restart to have wifi connection.
--
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/1390709
Title:
Wifi doesn't reconnect after waking from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Upgraded from 14.04 to 14.10. Before Wifi would reconnect after waking
up from sleep mode. After Update reconnect fails with wlan0: aborting
authentication with 1c:c6:3c:95:e7:74 by local choice (Reason:
3=DEAUTH_LEAVING).
I worked around this by killing wpa_supplicant with a script in
/etc/pm/sleep.d
#!/bin/sh
case "$1" in
thaw|resume)
{ killall wpa_supplicant ; } 2>/dev/null
;;
*)
;;
esac
exit $?
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu28
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Nov 8 11:43:15 2014
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-19 (567 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
IpRoute:
default via 192.168.138.251 dev wlan0 proto static
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
192.168.138.0/24 dev wlan0 proto kernel scope link src 192.168.138.143
metric 9
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to utopic on 2014-11-07 (0 days ago)
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.8.8connected enabled enabled
enabledenabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390709/+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 1068737] [NEW] Joomla extension Simple MP3 Player doesn't display playlist
Public bug reported: Hello, I added the MP3 Simple Player component to a Joomla 1.5.26 website. http://extensions.joomla.org/extensions/multimedia/multimedia-players/audio-players-a-gallery/8338 You can check it on the website here on the bottom right entitled "A découvrir" : http://asaph-lyon.com/ Its a component working with Flash Player. Unfortunately it doesn't display the playlist at all on Ubuntu 12.04. The Flash Player version is 11.1.102.63 However it works fine on Windows XP or Seven with Flash 11.4.31.110 Thanks for your help and advices... Guillaume ** Affects: flashplugin-nonfree (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1068737 Title: Joomla extension Simple MP3 Player doesn't display playlist Status in “flashplugin-nonfree” package in Ubuntu: New Bug description: Hello, I added the MP3 Simple Player component to a Joomla 1.5.26 website. http://extensions.joomla.org/extensions/multimedia/multimedia-players/audio-players-a-gallery/8338 You can check it on the website here on the bottom right entitled "A découvrir" : http://asaph-lyon.com/ Its a component working with Flash Player. Unfortunately it doesn't display the playlist at all on Ubuntu 12.04. The Flash Player version is 11.1.102.63 However it works fine on Windows XP or Seven with Flash 11.4.31.110 Thanks for your help and advices... Guillaume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1068737/+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 865672] Re: "Adobe Flash Player Settings" dialogue does not respond to mouse clicks
** Description changed:
WORKAROUNDS:
1.
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager06.html#117645
2. Click on the flash window. Now use the keyboard to tab through the
settings dialog. Space to select.
-
ORIGINAL DESCRIPTION:
Adobe flash player is configured on my system to ask before a website sets a
flash cookie, so if a video (eg on youtube) is played, a dialogue box will pop
up asking me whether or not to allow the website to store a cookie on my
machine. However, nothing happens when I click on either 'allow' or 'deny', so
the box stays put and I can't view or control the video playing beneath it.
On this machine I upgraded from 11.04 to 11.10; in 11.04 there was a program
for adjusting the flash player settings in the System Settings control panel,
but that program is no longer there and not accessible via the dash, so there
is no obvious way to just configure flash to allow all cookies and avoid the
dialogue box.
Workaround: using Unity 2D instead
+
+ Notice : the problem has been already corrected two years before :
+ https://bugs.launchpad.net/ubuntu/+source/flashplugin-
+ nonfree/+bug/410407?comments=all
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: firefox 7.0.1+build1+nobinonly-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sean 1362 F pulseaudio
/dev/snd/pcmC0D0p: sean 1362 F...m pulseaudio
BuildID: 20110929002329
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7db8000 irq 44'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,104383ce,0014'
Controls : 12
Simple ctrls : 7
Channel: release
Date: Mon Oct 3 12:51:36 2011
ExecutablePath: /usr/lib/firefox-7.0.1/plugin-container
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232},
Version=2.1.4, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile,
Type=extension, Active=Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
IpRoute:
default via 10.10.88.1 dev wlan0 proto static
10.10.88.0/21 dev wlan0 proto kernel scope link src 10.10.92.255 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929002329 (Running)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (37 days ago)
dmi.bios.date: 10/16/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd10/16/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
** Description changed:
WORKAROUNDS:
1.
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager06.html#117645
2. Click on the flash window. Now use the keyboard to tab through the
settings dialog. Space to select.
ORIGINAL DESCRIPTION:
Adobe flash player is configured on my system to ask before a website sets a
flash cookie, so if a video (eg on youtube) is played, a dialogue box will pop
up asking me whether or not to allow the website to store a cookie on my
machine. However, nothing happens when I click on either 'allow' or 'deny', so
the box stays put and I can't view or control the video playing beneath it.
On this machine I upgraded from 11.04 to 11.10; in 11.04 there was a program
for adjusting the flash player settings in the System Settings control panel,
but that program is no longer there and not accessible via the dash, so there
is no obvious way to just configure flash to allow all cookies and avoid the
dialogue box.
Workaround: using Unity 2D instead
- Notice : the problem has been already corrected two year
[Desktop-packages] [Bug 865672] Re: "Adobe Flash Player Settings" dialogue does not respond to mouse clicks
Yes, it's what I said in "Notice" ;)
--
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/865672
Title:
"Adobe Flash Player Settings" dialogue does not respond to mouse
clicks
Status in Chromium Browser:
New
Status in The Mozilla Firefox Browser:
New
Status in Midori: Webkit Web browser:
Confirmed
Status in Unity Distro Priority:
Fix Released
Status in “adobe-flashplugin” package in Ubuntu:
Triaged
Status in “chromium-browser” package in Ubuntu:
Invalid
Status in “firefox” package in Ubuntu:
Invalid
Status in “midori” package in Ubuntu:
Confirmed
Bug description:
WORKAROUNDS:
1.
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager06.html#117645
2. Click on the flash window. Now use the keyboard to tab through the
settings dialog. Space to select.
ORIGINAL DESCRIPTION:
Adobe flash player is configured on my system to ask before a website sets a
flash cookie, so if a video (eg on youtube) is played, a dialogue box will pop
up asking me whether or not to allow the website to store a cookie on my
machine. However, nothing happens when I click on either 'allow' or 'deny', so
the box stays put and I can't view or control the video playing beneath it.
On this machine I upgraded from 11.04 to 11.10; in 11.04 there was a program
for adjusting the flash player settings in the System Settings control panel,
but that program is no longer there and not accessible via the dash, so there
is no obvious way to just configure flash to allow all cookies and avoid the
dialogue box.
Workaround: using Unity 2D instead
Notice : the problem has been already corrected two years before :
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/410407?comments=all
I'll add that it's perhaps because of Compiz : It works with Unity 2d, KDE,
Gnome-Shell, Gnome-Session-With-No-Effect BUT it affects Ubuntu 3D,
Gnome-Session Fallback and Caito-Dock session
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: firefox 7.0.1+build1+nobinonly-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sean 1362 F pulseaudio
/dev/snd/pcmC0D0p: sean 1362 F...m pulseaudio
BuildID: 20110929002329
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7db8000 irq 44'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,104383ce,0014'
Controls : 12
Simple ctrls : 7
Channel: release
Date: Mon Oct 3 12:51:36 2011
ExecutablePath: /usr/lib/firefox-7.0.1/plugin-container
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232},
Version=2.1.4, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile,
Type=extension, Active=Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
IpRoute:
default via 10.10.88.1 dev wlan0 proto static
10.10.88.0/21 dev wlan0 proto kernel scope link src 10.10.92.255 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929002329 (Running)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (37 days ago)
dmi.bios.date: 10/16/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd10/16/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/865672/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.n
[Desktop-packages] [Bug 865672] Re: "Adobe Flash Player Settings" dialogue does not respond to mouse clicks
** Also affects: compiz
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/865672
Title:
"Adobe Flash Player Settings" dialogue does not respond to mouse
clicks
Status in Chromium Browser:
New
Status in Compiz:
New
Status in The Mozilla Firefox Browser:
New
Status in Midori: Webkit Web browser:
Confirmed
Status in Unity Distro Priority:
Fix Released
Status in “adobe-flashplugin” package in Ubuntu:
Triaged
Status in “chromium-browser” package in Ubuntu:
Invalid
Status in “firefox” package in Ubuntu:
Invalid
Status in “midori” package in Ubuntu:
Confirmed
Bug description:
WORKAROUNDS:
1.
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager06.html#117645
2. Click on the flash window. Now use the keyboard to tab through the
settings dialog. Space to select.
ORIGINAL DESCRIPTION:
Adobe flash player is configured on my system to ask before a website sets a
flash cookie, so if a video (eg on youtube) is played, a dialogue box will pop
up asking me whether or not to allow the website to store a cookie on my
machine. However, nothing happens when I click on either 'allow' or 'deny', so
the box stays put and I can't view or control the video playing beneath it.
On this machine I upgraded from 11.04 to 11.10; in 11.04 there was a program
for adjusting the flash player settings in the System Settings control panel,
but that program is no longer there and not accessible via the dash, so there
is no obvious way to just configure flash to allow all cookies and avoid the
dialogue box.
Workaround: using Unity 2D instead
Notice : the problem has been already corrected two years before :
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/410407?comments=all
I'll add that it's perhaps because of Compiz : It works with Unity 2d, KDE,
Gnome-Shell, Gnome-Session-With-No-Effect BUT it affects Ubuntu 3D,
Gnome-Session Fallback and Caito-Dock session
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: firefox 7.0.1+build1+nobinonly-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sean 1362 F pulseaudio
/dev/snd/pcmC0D0p: sean 1362 F...m pulseaudio
BuildID: 20110929002329
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7db8000 irq 44'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,104383ce,0014'
Controls : 12
Simple ctrls : 7
Channel: release
Date: Mon Oct 3 12:51:36 2011
ExecutablePath: /usr/lib/firefox-7.0.1/plugin-container
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232},
Version=2.1.4, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile,
Type=extension, Active=Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
IpRoute:
default via 10.10.88.1 dev wlan0 proto static
10.10.88.0/21 dev wlan0 proto kernel scope link src 10.10.92.255 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929002329 (Running)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (37 days ago)
dmi.bios.date: 10/16/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd10/16/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/865672/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-package
[Desktop-packages] [Bug 1022291] [NEW] RB does not display the correct album art.
Public bug reported: Open RB, and read a Music, it happens that the album art diplayed is not the good one. * 1: David Guetta is replaced by Madonna where I've an album of Madonna and David Guetta * When I read 2 songs or more of the same band/singer, the second takes the cover of the first (even if the first one is not the correct album art) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1022291 Title: RB does not display the correct album art. Status in “rhythmbox” package in Ubuntu: New Bug description: Open RB, and read a Music, it happens that the album art diplayed is not the good one. * 1: David Guetta is replaced by Madonna where I've an album of Madonna and David Guetta * When I read 2 songs or more of the same band/singer, the second takes the cover of the first (even if the first one is not the correct album art) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1022291/+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 1022291] Re: RB does not display the correct album art.
** Description changed: - Open RB, and read a Music, it happens that the album art diplayed is not the good one. - (for exemple : David Guetta is replaced by Madonna) + Open RB, and read a Music, it happens that the album art diplayed is not + the good one. + + * 1: David Guetta is replaced by Madonna where I've an album of Madonna and David Guetta + * When I read 2 songs or more of the same band/singer, the second takes the cover of the first (even if the first one is not the correct album art) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1022291 Title: RB does not display the correct album art. Status in “rhythmbox” package in Ubuntu: New Bug description: Open RB, and read a Music, it happens that the album art diplayed is not the good one. * 1: David Guetta is replaced by Madonna where I've an album of Madonna and David Guetta * When I read 2 songs or more of the same band/singer, the second takes the cover of the first (even if the first one is not the correct album art) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1022291/+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 1025011] Re: Firebug extension causes firefox to crash (can be triggered by opening HUD)
me it only happen if I launch unity from other tty of the x server. I tried both with no screen variable set and set. -- 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/1025011 Title: Firebug extension causes firefox to crash (can be triggered by opening HUD) Status in The Mozilla Firefox Browser: Confirmed Status in Unity global menubar extension for Firefox and Thunderbird: Fix Committed Status in “firefox” package in Ubuntu: Fix Released Status in “firefox” source package in Natty: Fix Committed Status in “firefox” source package in Oneiric: Fix Committed Status in “firefox” source package in Precise: Fix Committed Status in “firefox” source package in Quantal: Fix Released Bug description: Searching for any text causes Firefox 13.0.1 to crash on Ubuntu 12.04 ( both 32 & 64 bit **1). Test case: 1. Hit ALT to bring up the HUD search box 2. Type one or more words into the textbox. Expected result: 1. HUD appears ready to search 2. Results appear depending on the search term. What actually happens: 1. HUD appears ready to search 2. Results appear, however firefox crashes shortly after. == Additional information == Running firefox in safe mode makes HUD ignore firefox. In this situation Firefox doesn't crash. **1: I can reproduce this bug on 64 bit Ubuntu. Peter Cawkell is experiencing this bug on 32 bit ( see coments ) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1025011/+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 1248116] Re: PulseAudio switch rapidly port making the sound horrible
I confirm : same issue on my brand new PC with Gigabyte Z87X-UD3H motherboard... Solved using hda-jack-retask to disable frontside input/output... not a big deal but definitely not a "solution" ! Raymond : 1/ you should increase the status to "confirmed" ;-) 2/ How can I help you ? More information are required ? -- 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/1248116 Title: PulseAudio switch rapidly port making the sound horrible Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I have a Realtek sound system integrated to the motherboard Gygabyte Z87X-UD3H (http://www.gigabyte.fr/products/product- page.aspx?pid=4481#sp) having problems on Ubuntu 13.10. The sound is jerky. When I open the "Volume control PulseAudio" I can see pulseaudio changing the audio output "Internal Audio Analogic Stereo". The port switch rapidly from "Analogic output" to "Analogic headphones" making a jerky sound. ta tA ta tA ta tA. Do you have a solution to this problem ? King regards Will To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248116/+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 1248116] Re: PulseAudio switch rapidly port making the sound horrible
Thanks ! It works like a charm. No more automatic jack detection but all the jacks are working properly and active simultaneously and the sound is crystal clear. Much better than setting "no presence" with hdajackrestask. in /etc/modprobe.d just add a file hda-jack-detect.conf with the following lines : # This file was added as a workaround to the jack detection issue with a Gigabyte GA-Z87X-UD3H motherboard # If you want to revert the changes, you can simply erase this file and reboot your computer. options snd-hda-intel patch=hda-jack-detect.fw And in /lib/firmware add a file hda-jack-detect.fw with the following lines : [codec] 0x10ec0899 0x1458a002 2 [hint] jack_detect = no Then reboot ! For information : you can check the file /proc/asound/card0/codec* to verify that the [codec] line matches your hardware (vendor-id subsystem-id address) head -n 10 /proc/asound/card0/codec* Codec: Realtek ALC898 Address: 2 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0899 Subsystem Id: 0x1458a002 -- 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/1248116 Title: PulseAudio switch rapidly port making the sound horrible Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I have a Realtek sound system integrated to the motherboard Gygabyte Z87X-UD3H (http://www.gigabyte.fr/products/product- page.aspx?pid=4481#sp) having problems on Ubuntu 13.10. The sound is jerky. When I open the "Volume control PulseAudio" I can see pulseaudio changing the audio output "Internal Audio Analogic Stereo". The port switch rapidly from "Analogic output" to "Analogic headphones" making a jerky sound. ta tA ta tA ta tA. Do you have a solution to this problem ? King regards Will To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248116/+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 1248116] Re: PulseAudio switch rapidly port making the sound horrible
By the way, you will find in attachment the hd-audio driver tracepoints (I've enabled the trace.log while the bug occurs (randomly switch between front output jack and rear output jack), then I've plugged an headphone on the front jack a few seconds later : the erratic switch disappears) ** Attachment added: "trace.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248116/+attachment/3934401/+files/trace.log -- 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/1248116 Title: PulseAudio switch rapidly port making the sound horrible Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I have a Realtek sound system integrated to the motherboard Gygabyte Z87X-UD3H (http://www.gigabyte.fr/products/product- page.aspx?pid=4481#sp) having problems on Ubuntu 13.10. The sound is jerky. When I open the "Volume control PulseAudio" I can see pulseaudio changing the audio output "Internal Audio Analogic Stereo". The port switch rapidly from "Analogic output" to "Analogic headphones" making a jerky sound. ta tA ta tA ta tA. Do you have a solution to this problem ? King regards Will To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248116/+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 1248116] Re: PulseAudio switch rapidly port making the sound horrible
If there is anything else I can do to help solving this issue... don't hesitate to ask ! -- 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/1248116 Title: PulseAudio switch rapidly port making the sound horrible Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I have a Realtek sound system integrated to the motherboard Gygabyte Z87X-UD3H (http://www.gigabyte.fr/products/product- page.aspx?pid=4481#sp) having problems on Ubuntu 13.10. The sound is jerky. When I open the "Volume control PulseAudio" I can see pulseaudio changing the audio output "Internal Audio Analogic Stereo". The port switch rapidly from "Analogic output" to "Analogic headphones" making a jerky sound. ta tA ta tA ta tA. Do you have a solution to this problem ? King regards Will To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248116/+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 1248116] Re: PulseAudio switch rapidly port making the sound horrible
You will find below the hda info in my syslog : grep hda syslog Dec 28 12:53:37 ubuntu kernel: [2.247883] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X Dec 28 12:53:37 ubuntu kernel: [2.664258] hda_intel: Disabling MSI Dec 28 12:53:37 ubuntu kernel: [2.664264] hda-intel :01:00.1: Handle VGA-switcheroo audio client Dec 28 12:53:37 ubuntu kernel: [2.664289] hda-intel :01:00.1: Disabling 64bit DMA Dec 28 12:53:37 ubuntu kernel: [2.667560] hda-intel :01:00.1: Enable delay in RIRB handling Dec 28 14:15:01 ubuntu kernel: [2.734667] hda-intel :00:1b.0: Applying patch firmware 'hda-jack-detect.fw' Dec 28 14:15:01 ubuntu kernel: [2.734777] hda_intel: Disabling MSI Dec 28 14:15:01 ubuntu kernel: [2.734780] hda-intel :01:00.1: Handle VGA-switcheroo audio client Dec 28 14:15:01 ubuntu kernel: [2.734805] hda-intel :01:00.1: Disabling 64bit DMA Dec 28 14:15:01 ubuntu kernel: [2.735424] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X Dec 28 14:15:01 ubuntu kernel: [2.738020] hda-intel :01:00.1: Enable delay in RIRB handling -- 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/1248116 Title: PulseAudio switch rapidly port making the sound horrible Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I have a Realtek sound system integrated to the motherboard Gygabyte Z87X-UD3H (http://www.gigabyte.fr/products/product- page.aspx?pid=4481#sp) having problems on Ubuntu 13.10. The sound is jerky. When I open the "Volume control PulseAudio" I can see pulseaudio changing the audio output "Internal Audio Analogic Stereo". The port switch rapidly from "Analogic output" to "Analogic headphones" making a jerky sound. ta tA ta tA ta tA. Do you have a solution to this problem ? King regards Will To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1248116/+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 950825] Re: LibreOffice quicklists are not translated
We're not far from the final realease and this "little" problem still exists. It's a problem because poeple who want to discover Ubuntu will see this problem ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/950825 Title: LibreOffice quicklists are not translated Status in Ubuntu Translations: Triaged Status in “libreoffice” package in Ubuntu: Confirmed Bug description: The "ubuntu-quicklists.diff" patch does not seem to work properly. For example, if you run "cat /usr/share/applications/libreoffice- calc.desktop" you will see that the "New Spreedsheet" quicklist is translated to "New Spreedsheet" in all languages, whereas correct translations are in the patch. I downloaded the patch from https://launchpad.net/ubuntu/+archive/primary/+files/libreoffice_3.5.0-2ubuntu1.debian.tar.gz (this is the libreoffice version I have). This bug happens only on Precise (quicklists are translated on Oneiric). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.5.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu1 Architecture: i386 CheckboxSubmission: 8cf001b4b1d1f2fddc8b471a28b5eaa6 CheckboxSystem: d89cfecb506be0562834433b44d8bcb5 Date: Fri Mar 9 14:40:08 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111222) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-02-16 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/950825/+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 788403] Re: LibreOffice Calc cannot 'Save File As'
Hi, You're using slashes in the filename, it is not recommended as the slash symbol is considered as directory separator, so Libroffice is trying to save the file as 3.ods in the directory 21-6 in the directory Joshua Fallaw time sheet 5, that don't exist. You should use another separator instead, like '-'. Guillaume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/788403 Title: LibreOffice Calc cannot 'Save File As' Status in “libreoffice” package in Ubuntu: New Bug description: Binary package hint: libreoffice I opened an Excel spreadsheet from my windows partition in LOCalc, modified it, and then tried to save the file on my Ubuntu partition as a LibreOffice file with a different file name. I received the error message: "The folder contents could not be displayed: Error stating file 'path/to/foo': no such file or directory." Of course the file doesn't exist, because I haven't saved it yet! This happens when I save as a .xls or as a libreoffice file type, whether I save it to the host partition or Ubuntu partition. The only way I can save the file is if I save it with the same name to the same partition (ie, 'Save'), which defeats the purpose of 'Save As..' I have included the dmesg log. I do not know where the log file for Calc resides or I'd attach that. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Wed May 25 17:52:47 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-05-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/788403/+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 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
I confirm the same bug on own PC : Fresh install ubuntu-gnome 16.04.1 updated with Gnome 3.20 from ppa:gnome3-team/gnome3-staging Jan 4 16:09:08 PC systemd[1]: Started CUPS Scheduler. Jan 4 16:09:08 PC colord[1309]: (colord:1309): Cd-WARNING **: failed to get session [pid 8407]: Aucun périphérique ou adresse Jan 4 16:15:09 PC gnome-settings-daemon.desktop[2008]: (gnome-settings-daemon:2008): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_Color_LaserJet_MFP_M476dn Jan 4 16:43:23 PC systemd[1]: Started CUPS Scheduler. Jan 4 16:43:23 PC colord[1309]: (colord:1309): Cd-WARNING **: failed to get session [pid 8945]: Aucun périphérique ou adresse Jan 4 16:49:25 PC gnome-settings-daemon.desktop[2008]: (gnome-settings-daemon:2008): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_Color_LaserJet_MFP_M476dn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1635715 Title: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 Status in gnome-settings-daemon package in Ubuntu: New Bug description: The complete errors that are shown together are: Oct 18 08:20:51 localhost systemd[1]: Started CUPS Scheduler. Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_PDF Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial gnome-settings-daemon: Installed: 3.18.2-0ubuntu3.1 Candidate: 3.18.2-0ubuntu3.1 Version table: *** 3.18.2-0ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.2-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages This happens quite frequently and I'm not sure of the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1635715/+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 1394114] [NEW] [SVS13A3W9ES, Realtek ALC275, no sound from internal speaker and very low sound from headset
Public bug reported: Problem: There is no sound from the internal sepaker and it is very low when headset is plugged in. There is a dual boot with windows 8.1 and the sound is working just fine on W8.1. I have tried to: - Update the driver https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS - Play around with sound level in alsamixer ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guta 2564 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 19 10:08:53 2014 InstallationDate: Installed on 2014-11-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guta 2564 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [SVS13A3W9ES, Realtek ALC275, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BZHDH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BZHDH dmi.sys.vendor: Sony Corporation ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1394114 Title: [SVS13A3W9ES, Realtek ALC275, no sound from internal speaker and very low sound from headset Status in “alsa-driver” package in Ubuntu: New Bug description: Problem: There is no sound from the internal sepaker and it is very low when headset is plugged in. There is a dual boot with windows 8.1 and the sound is working just fine on W8.1. I have tried to: - Update the driver https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS - Play around with sound level in alsamixer ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guta 2564 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 19 10:08:53 2014 InstallationDate: Installed on 2014-11-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guta 2564 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [SVS13A3W9ES, Realtek ALC275, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BZHDH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BZHDH dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1394114/+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 1867147] Re: Failed to add UUID: Busy (0x0a)
I have to same error with Ubuntu 20.10 ** Changed in: linux (Ubuntu) Status: Expired => Confirmed ** Package changed: linux (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1867147 Title: Failed to add UUID: Busy (0x0a) Status in bluez package in Ubuntu: Confirmed Bug description: dmesg Bluetooth: hci0: command 0x0c24 tx timeout rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: hci1: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no bluetoothctl Failed to start discovery: org.bluez.Error.InProgress lsusb Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) lshw *-usb descrição: USB controller produto: Cannon Lake PCH USB 3.1 xHCI Host Controller fabricante: Intel Corporation ID físico: 14 informações do barramento: pci@:00:14.0 versão: 10 largura: 64 bits clock: 33MHz capacidades: pm msi xhci bus_master cap_list configuração: driver=xhci_hcd latency=0 recursos: irq:124 memória:eb22-eb22 *-usbhost:0 produto: xHCI Host Controller fabricante: Linux 5.3.0-40-generic xhci-hcd ID físico: 0 informações do barramento: usb@1 nome lógico: usb1 versão: 5.03 capacidades: usb-2.00 configuração: driver=hub slots=16 speed=480Mbit/s *-usb:0 descrição: Interface sem fio bluetooth produto: JL AC69 A10 fabricante: Cambridge Silicon Radio, Ltd ID físico: 1 informações do barramento: usb@1:1 versão: 25.20 capacidades: bluetooth usb-2.00 configuração: driver=btusb maxpower=100mA speed=12Mbit/s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 09:18:43 2020 InstallationDate: Installed on 2019-06-19 (266 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteDesk 800 G4 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=885446d9-2945-4958-a7f0-1eadecf23697 ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q01 Ver. 02.06.03 dmi.board.name: 83E1 dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ01Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4SFF:pvr:rvnHP:rn83E1:rvrKBCVersion07.D2.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 SFF dmi.product.sku: 5ZA60LP#AC4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1867147/+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 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
Here it is ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+attachment/5452757/+files/journalctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1910598 Title: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. Status in caja package in Ubuntu: New Status in udisks2 package in Ubuntu: Incomplete Bug description: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+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 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
Unfortunately, I don't have any crash report for udisk in /var/crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1910598 Title: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. Status in caja package in Ubuntu: New Status in udisks2 package in Ubuntu: Incomplete Bug description: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+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 1912668] [NEW] [Q1U dynamic microphone - AT2020 USB, recording] fails after a while
Public bug reported: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3902:bd03/21/2018:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1912668 Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.mod
[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
Happens very frequently for me also on a vanilla 18.04 (Thinkpad), but only on a small subset of applications. What's strange is that the bug appeared a few days ago after years without problem. I do not use any external peripheral (nothing connected to the laptop except the power supply). An easy solution to solve this without rebooting the whole system is to disable then enable the TouchScreen (disabling alone is not sufficient). Following Paul Müller's steps: - find your TouchScreen input ID with ``xinput`` (in my case ``Melfas LGDisplay Incell Touch id=9`` - ``xinput --disable 9`` - ``xinput --enable 9`` If you want to automate this in a script/alias, you can easily retrieve the ID once you know the name of the TouchScreen: - ``xinput list --id-only 'Melfas LGDisplay Incell Touch'`` -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 1852694] Re: Night Light stuck on Wayland
By "X-Server" I mean standard Xorg. Everything used to work fine a few weeks ago on the same computer (with 19.04, before the upgrade to 19.10... and maybe a bit afterwards). -- 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/1852694 Title: Night Light stuck on Wayland Status in xorg-server package in Ubuntu: New Bug description: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 15 07:43:01 2019 DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2018-07-28 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to eoan on 2019-10-18 (28 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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/xorg-server/+bug/1852694/+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 1852694] [NEW] Night Light stuck on Wayland
Public bug reported: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 15 07:43:01 2019 DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2018-07-28 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to eoan on 2019-10-18 (28 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu wayland-session -- 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/1852694 Title: Night Light stuck on Wayland Status in xorg-server package in Ubuntu: New Bug description: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 15 07:43:01 2019 DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2018-07-28 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Bea
Re: [Desktop-packages] [Bug 1852694] Re: Night Light stuck on Wayland
I tried to file it against Wayland but Apport would'nt let me do it! Le ven. 15 nov. 2019 à 10:00, Timo Aaltonen a écrit : > not logical to file it against the xserver then > > ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1852694 > > Title: > Night Light stuck on Wayland > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > Gnome Night Light stopped working correctly in the Wayland session with > standard Ubuntu. > Night Light does not switch on automatically. I can't switch it on > manyally either (the toggle works well, but the screen doesn't change). > If I log off and log on to an X-Server session, Night Lights works again > normally. For example, it turns on at night - but then stays on all day > (even if the applet disappears as expected) when I go back to my Wayland > session. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: xwayland 2:1.20.5+git20191008-0ubuntu1 > ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 > Uname: Linux 5.3.0-22-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: GNOME > Date: Fri Nov 15 07:43:01 2019 > DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: eoan > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] > InstallationDate: Installed on 2018-07-28 (474 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2b Intel Corp. >Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD > UVC WebCam >Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. UX410UAK > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-22-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 > SourcePackage: xorg-server > UpgradeStatus: Upgraded to eoan on 2019-10-18 (28 days ago) > dmi.bios.date: 11/08/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX410UAK.308 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX410UAK > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: UX > dmi.product.name: UX410UAK > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.99-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core > 2:1.20.5+git20191008-0ubuntu1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20190815-1 > 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/gnome-shell/+bug/1852694/+subscriptions > -- 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/1852694 Title: Night Light stuck on Wayland Status in gnome-shell package in Ubuntu: New Bug description: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature:
[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
I don't know why... The fix worked until yesterday, but the problem has come back! guillaume@massada:~$ dpkg -l |grep -i mutter ii gir1.2-mutter-5:amd64 3.34.1+git20191107-1ubuntu1~19.10.1amd64GObject introspection data for Mutter ii libmutter-5-0:amd64 3.34.1+git20191107-1ubuntu1~19.10.1amd64window manager library from the Mutter window manager ii mutter 3.34.1+git20191107-1ubuntu1~19.10.1amd64Example window manager using GNOME's window manager library ii mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1all shared files for the Mutter window manager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). [ Test case ] - From gnome-control-center display panel, enable the Night Light - Force it on, and ensure that the display color temperature increases [ Regression potential ] Display gamma value might be incorrect Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+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 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
Apologies: it works. But it looks like that GNOME thinks that 8pm is not night here in western Europe, at this time of year! :-D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). [ Test case ] - From gnome-control-center display panel, enable the Night Light - Force it on, and ensure that the display color temperature increases [ Regression potential ] Display gamma value might be incorrect Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+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 1858463] Re: Desktop freezing while SSD under heavy load
Still happening with 20.04 ** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected focal ** Description changed: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: guillaume 1685 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-11 (9 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0a2b Intel Corp. + Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam + Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. UX410UAK + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-25-generic N/A + linux-backports-modules-5.4.0-25-generic N/A + linux-firmware1.187 + Tags: focal wayland-session + Uname: Linux 5.4.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/17/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX410UAK.312 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX410UAK + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ZenBook + dmi.product.name: UX410UAK + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Confirmed Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least
[Desktop-packages] [Bug 1873942] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357334/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357328/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357331/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357323/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357326/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357325/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357327/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357330/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357337/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] [NEW] gnome-screenshot takes a screenshot of the wrong screen
Public bug reported: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected focal ubuntu wayland-session ** Package changed: gnome-screenshot (Ubuntu) => wayland (Ubuntu) ** Tags added: apport-collected ubuntu ** Description changed: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 Install
[Desktop-packages] [Bug 1873942] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357332/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357329/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357322/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357335/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357324/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357336/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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 1873942] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357333/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 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/wayland/+bug/1873942/+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
Re: [Desktop-packages] [Bug 1873942] Re: gnome-screenshot takes a screenshot of the wrong screen
Yes, I can confirm the bug happens only on Wayland. Everything works fine under the standard "Ubuntu" session, or the "Gnome on Xorg" session. (I also noticed something strange under the "Ubuntu on Wayland" session, wich might be related: I can screenshot the left dock and sometimes parts the dock and an unfocused window, but never the focused/current/selected window.) Le mar. 21 avr. 2020 à 11:26, Sebastien Bacher a écrit : > Thank you for your bug report. Is the issue specific to wayland? does it > work if you try under X? > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Triaged > > ** Changed in: gnome-screenshot (Ubuntu) >Status: Confirmed => Invalid > > ** Changed in: gnome-shell (Ubuntu) >Importance: Undecided => Low > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873942 > > Title: > gnome-screenshot takes a screenshot of the wrong screen > > Status in GNOME Shell: > Unknown > Status in gnome-screenshot package in Ubuntu: > Invalid > Status in gnome-shell package in Ubuntu: > Triaged > > Bug description: > I have a dual monitor setup, with the external monitor defined as the > "primary" one (and the laptop one secondary). > When using the Shift + PrtScr shortcut and choosing an area on the > external monitor, the screenshot saved in ~/Pictures shows this area but on > the _laptop_ screen. > (Choosing an area on the laptop screen works OK.) > > I use the vanilla Gnome session (with Wayland), installed with apt. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-screenshot 3.36.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 > Uname: Linux 5.4.0-25-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: GNOME > Date: Mon Apr 20 20:58:46 2020 > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-screenshot > UpgradeStatus: No upgrade log present (probably fresh install) > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: GNOME > DistUpgraded: Fresh install > DistroCodename: focal > DistroRelease: Ubuntu 20.04 > DistroVariant: ubuntu > DkmsStatus: >acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed > GraphicsCard: >Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2b Intel Corp. >Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD > UVC WebCam >Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. UX410UAK > Package: wayland (not installed) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic > root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 > Tags: focal wayland-session ubuntu > Uname: Linux 5.4.0-25-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 04/17/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX410UAK.312 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX410UAK > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook > dmi.product.name: UX410UAK > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dr
[Desktop-packages] [Bug 1894596] [NEW] Night mode stays on
Public bug reported: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- 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/1894596 Title: Night mode stays on Status in gnome-shell package in Ubuntu: New Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
I currently have no Gnome extension activated, apart from "Ubuntu appindicators" (see screenshot "Extensions.png") -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
Extension list (attachment) -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
** Attachment added: "Extensions.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+attachment/5408400/+files/Extensions.png -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+attachment/5409281/+files/journal.txt -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+attachment/5409282/+files/lspci.txt -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
This may have something to do with using an external screen. I usually use only my external screen, with laptop screen/lid closed. I noticed right now that if I open the laptop lid, then color on the external screen goes back to "normal" and color on the laptop screen (defined as secondary, without Gnome shell panel) stays in "orange" mode. -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
Night Light is set to turn on at 10:00 pm and off at 6:00 am. At 7:25 am I noticed the icon had disappeared but the screen was still "orange". Please find as an attachment the results of: lspci -kv > lspci.txt journalctl -b0 > journal.txt -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1864274] Re: crunchy pixels
I've added instructions in the mesa bug on how to correctly set the
environment variable to workaround the issue:
https://gitlab.freedesktop.org/mesa/mesa/issues/2552#note_432595
--
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/1864274
Title:
crunchy pixels
Status in Mesa:
Unknown
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
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}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1864274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Someone is working on adding wideband support to pulseaudio (this currently requires ofono): https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 -- 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 PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New 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/pulseaudio/+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 1869225] [NEW] nm-applet should not attempt to create system-wide WiFi connections for regular users
Public bug reported: When a standard (non-administrator user) selects a WiFi network using the applet, the applet attempts to create a system connection, instead of a user connection, and thus it asks for an administrator user's password. On the other hand, if the same standard user opens the WiFi settings and selects a network there, no admin password is requested, as the connection is created for this user only, not system-wide. This is a workaround I discovered recently (see https://askubuntu.com/a/1163852/375543). This has bitten me several times, as I hand out laptops for new users; when they get home, they try to connect to their network and as I have no other way to help them (before I discovered the workaround), I ended up giving them the administrator password. The applet should not attempt to create a system-wide connection for users that are unable to do it. There is no security implication to implement this, as the users are able to create a connection anyway with the workaround mentioned above. But the improvement in terms of UX would be huge. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1869225 Title: nm-applet should not attempt to create system-wide WiFi connections for regular users Status in network-manager-applet package in Ubuntu: New Bug description: When a standard (non-administrator user) selects a WiFi network using the applet, the applet attempts to create a system connection, instead of a user connection, and thus it asks for an administrator user's password. On the other hand, if the same standard user opens the WiFi settings and selects a network there, no admin password is requested, as the connection is created for this user only, not system-wide. This is a workaround I discovered recently (see https://askubuntu.com/a/1163852/375543). This has bitten me several times, as I hand out laptops for new users; when they get home, they try to connect to their network and as I have no other way to help them (before I discovered the workaround), I ended up giving them the administrator password. The applet should not attempt to create a system-wide connection for users that are unable to do it. There is no security implication to implement this, as the users are able to create a connection anyway with the workaround mentioned above. But the improvement in terms of UX would be huge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1869225/+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 1926153] [NEW] [hostname-M.2, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] Playback problem in terminal
Public bug reported: Hello, When in terminal, with my header on, if I press alternatively the "tab" key or the backspace key when there is no text, I get parasitic noise that come and go, in addition to the error sound. The parasitic noises are most often not loud, but they're here although they definitely shouldn't. Sometimes, it's quite loud too. The bug is not deterministic. Sometimes the tone is higher/lower. Sometimes it disappear on the first time I re-press one key among tab and suppress. Sometimes it requires more key pressing. I'm not sure whether the sound ends up by disapearing after a few retries, or if it just becomes too quiet for me to hear it. The bug doesn't occur when the sound is deactivated I feel like this has something to do with the error sound that is played when I delete and there is no character to delete It is not a big deal in itself. But maybe this very benign symptom hides a more serious issue idk. The sound comes out of my graphic card (nvidia gtx 980 ti) through a Samsung TV. I don't think the problem comes from either the graphic card or the TV, because it only happens in ubuntu, never in windows ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guillaume 1669 F pulseaudio /dev/snd/pcmC1D0c: guillaume 1669 F...m pulseaudio /dev/snd/controlC2: guillaume 1669 F pulseaudio /dev/snd/controlC0: guillaume 1669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 14:04:04 2021 InstallationDate: Installed on 2021-01-06 (110 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia successful Symptom_Card: GM200 High Definition Audio - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [hostname-M.2, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: A320MA-M.2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnA320MA-M.2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320MA-M.2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320MA-M.2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926153 Title: [hostname-M.2, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] Playback problem in terminal Status in alsa-driver package in Ubuntu: New Bug description: Hello, When in terminal, with my header on, if I press alternatively the "tab" key or the backspace key when there is no text, I get parasitic noise that come and go, in addition to the error sound. The parasitic noises are most often not loud, but they're here although they definitely shouldn't. Sometimes, it's quite loud too. The bug is not deterministic. Sometimes the tone is higher/lower. Sometimes it disappear on the first time I re-press one key among tab and suppress. Sometimes it requires more key pressing. I'm not sure whether the sound ends up by disapearing after a few retries, or if it just becomes too quiet for me to hear it. The bug doesn't occur when the sound is deactivated I feel like this has something to do with the error sound that is played when I delete and there is no character to delete It is not a big deal in itself. But maybe this very benign symptom hides a more serious issue idk. The sound comes out of my graphic card (nvidia gtx 980 ti) through a Samsung TV. I don't think the problem comes from either the graphic card or the TV, because it only happens in ubunt
[Desktop-packages] [Bug 2011404] Re: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire
** Tags added: noble -- 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/2011404 Title: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in ubuntu-gnome-meta package in Ubuntu: Confirmed Bug description: Package vanilla-gnome-desktop 0.97 depends on pulseaudio which conflicts with pipewire-alsa and pipewire-audio which in turn are required for upgrading gnome to version 43. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2011404/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I installed wpasupplicant_2.10-2_amd64.deb and libssl1.1_1.1.1m-1_amd64.deb from debian sid. It works. I attached the log from journalctl -b 0 with ubuntu's wpasupplicant package. ** Attachment added: "wpa_supplicant.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5569503/+files/wpa_supplicant.log -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in network-manager package in Ubuntu: Incomplete Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I had edited the .service file but it was deleted when I reinstalled the ubuntu packages :-) The new log is attached. ** Attachment added: "wpa_supplicant.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5569942/+files/wpa_supplicant.log -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in network-manager package in Ubuntu: Incomplete Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
logs with '-ddd' from ubuntu 22.04 beta ** Attachment added: "wpa_supplicant.log" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+attachment/5577253/+files/wpa_supplicant.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Triaged Status in wpa source package in Jammy: Triaged Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 2023044] Re: New thumbnails are missing from file chooser
I've noticed it on 23.10 too. I think that the file picker does not GENERATE thumbnails. If thumbnails are generated beforehands by Nautilus, they get displayed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023044 Title: New thumbnails are missing from file chooser Status in GTK+: New Status in gtk4 package in Ubuntu: Triaged Bug description: Impact -- Thumbnails do not show in the file chooser (provided by gtk4 which is also used by even non-GTK3 apps if they use xdg-desktop-portal-gnome) until the thumbnail is generated by for instance, viewing the folder in Nautilus. This bug is new to Ubuntu 23.04 because GTK 4.10 is the first stable GTK release to support the "grid view" in the filechooser. Test Case - 1. Use Firefox to download an image file. (This test case assumes you're using the default Firefox distributed as a Snap). 2. In Firefox, use the keyboard shortcut Ctrl+O to open the file chooser. 3. Navigate to where the file was downloaded (your Downloads/ folder?) 4. The file should show a thumbnail image Number 4 doesn't happen correctly until you open the folder in Nautilus at least once. Other Info -- I am linking to what upstream considers the master bug for this issue. But a duplicate of the issue is https://gitlab.gnome.org/GNOME/gtk/-/issues/5663 which has a clearer summary. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2023044/+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 2023044] Re: New thumbnails are missing from file chooser
Just found this thread on the issue: https://discussion.fedoraproject.org/t/problem-with-new-file-picker-thumbnails-are-not-loaded/80073 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023044 Title: New thumbnails are missing from file chooser Status in GTK+: New Status in gtk4 package in Ubuntu: Triaged Bug description: Impact -- Thumbnails do not show in the file chooser (provided by gtk4 which is also used by even non-GTK3 apps if they use xdg-desktop-portal-gnome) until the thumbnail is generated by for instance, viewing the folder in Nautilus. This bug is new to Ubuntu 23.04 because GTK 4.10 is the first stable GTK release to support the "grid view" in the filechooser. Test Case - 1. Use Firefox to download an image file. (This test case assumes you're using the default Firefox distributed as a Snap). 2. In Firefox, use the keyboard shortcut Ctrl+O to open the file chooser. 3. Navigate to where the file was downloaded (your Downloads/ folder?) 4. The file should show a thumbnail image Number 4 doesn't happen correctly until you open the folder in Nautilus at least once. Other Info -- I am linking to what upstream considers the master bug for this issue. But a duplicate of the issue is https://gitlab.gnome.org/GNOME/gtk/-/issues/5663 which has a clearer summary. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2023044/+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 2050850] [NEW] Selected encoding not taken into account when saving
Public bug reported:
The file is saved in utf-8 even though I select iso-8859-1 as encoding when
saving.
Steps to reproduce:
1. Create a new file with non-ascii content, eg.: "çéè" (without quotes)
2. In the save dialog, select iso-8859-1 encoding
2. Check file size: it should be 3 bytes, but it is 7. Hexdump:
c3 a7 c3 a9 c3 a8 0a |...|
0007
For instance, c3 a7 is the utf-8 encoding of "ç". The iso-8859-1
encoding of this char is the single byte e7.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-text-editor 45.1-1build1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Jan 23 00:30:01 2024
InstallationDate: Installed on 2018-12-14 (1866 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-text-editor
UpgradeStatus: Upgraded to noble on 2023-11-07 (76 days ago)
** Affects: gnome-text-editor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
** Summary changed:
- Selected encoding not taken into account
+ Selected encoding not taken into account when saving
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-text-editor in Ubuntu.
https://bugs.launchpad.net/bugs/2050850
Title:
Selected encoding not taken into account when saving
Status in gnome-text-editor package in Ubuntu:
New
Bug description:
The file is saved in utf-8 even though I select iso-8859-1 as encoding when
saving.
Steps to reproduce:
1. Create a new file with non-ascii content, eg.: "çéè" (without quotes)
2. In the save dialog, select iso-8859-1 encoding
2. Check file size: it should be 3 bytes, but it is 7. Hexdump:
c3 a7 c3 a9 c3 a8 0a |...|
0007
For instance, c3 a7 is the utf-8 encoding of "ç". The iso-8859-1
encoding of this char is the single byte e7.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-text-editor 45.1-1build1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Jan 23 00:30:01 2024
InstallationDate: Installed on 2018-12-14 (1866 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: gnome-text-editor
UpgradeStatus: Upgraded to noble on 2023-11-07 (76 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2050850/+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 1993800]
openQA test passes. -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in llvm-toolchain-15 package in openSUSE: Fix Released Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1853762] Re: Headphones stop working until pairing again
This may have something to do with another user already being logged in another Gnome Session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+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 1993360] [NEW] [Dell XPS 15 9520] Cannot resume after suspend
Public bug reported: Similar as https://bugs.launchpad.net/ubuntu/+bug/1975454 Cannot resume after suspend when using nvidia card in Performance Mode on x11 ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 00:04:31 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-20 (28 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1993360 Title: [Dell XPS 15 9520] Cannot resume after suspend Status in gnome-shell package in Ubuntu: New Bug description: Similar as https://bugs.launchpad.net/ubuntu/+bug/1975454 Cannot resume after suspend when using nvidia card in Performance Mode on x11 ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 00:04:31 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-20 (28 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993360/+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 1993747] [NEW] Chromium browser "save as" window behaviour
Public bug reported: Hi! I have noticed that on both Ubuntu 22.04 and 22.10, when using a Chromium browser and opening a "save as" window (e.g. to save an image), I can't just push "Enter" and save nor push "Escape" and close the window. I have to click on the "Save" or "Cancel" buttons. All Chromium browsers look impacted. I tested on Chrome (106.0.5249.119), Brave (Version 1.44.112 Chromium: 106.0.5249.119 ) and Edge (Version 106.0.1370.52) tonight on Ubuntu 22.10. It was already the case a few months ago on Ubuntu 22.04 with both Brave (Version 1.39.122 Chromium: 102.0.5005.115) and Edge (Version 102.0.1245.44) - not tested with Chrome. That used to work on previous Ubuntu versions, and still works for other programs such as LibreOffice. Thanks a lot! ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => gtk4 (Ubuntu) ** Package changed: gtk4 (Ubuntu) => meta-gnome3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1993747 Title: Chromium browser "save as" window behaviour Status in meta-gnome3 package in Ubuntu: New Bug description: Hi! I have noticed that on both Ubuntu 22.04 and 22.10, when using a Chromium browser and opening a "save as" window (e.g. to save an image), I can't just push "Enter" and save nor push "Escape" and close the window. I have to click on the "Save" or "Cancel" buttons. All Chromium browsers look impacted. I tested on Chrome (106.0.5249.119), Brave (Version 1.44.112 Chromium: 106.0.5249.119 ) and Edge (Version 106.0.1370.52) tonight on Ubuntu 22.10. It was already the case a few months ago on Ubuntu 22.04 with both Brave (Version 1.39.122 Chromium: 102.0.5005.115) and Edge (Version 102.0.1245.44) - not tested with Chrome. That used to work on previous Ubuntu versions, and still works for other programs such as LibreOffice. Thanks a lot! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1993747/+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 1993864] [NEW] Nautilus extension for gnome-console bad localization
Public bug reported: I've installed the nautilus-extension-gnome-console to have a right click item in Nautilus to open the current folder in Console, but it doesn't match my system language (French) and keeps displaying "Open in Console"). Tested on Ubuntu 22.04 with : - nautilus-extension-gnome-console 42~beta-1 - libnautilus-extension1a:amd64 1:42.2-0ubuntu1 - nautilus 1:42.2-0ubuntu1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1993864 Title: Nautilus extension for gnome-console bad localization Status in mutter package in Ubuntu: New Bug description: I've installed the nautilus-extension-gnome-console to have a right click item in Nautilus to open the current folder in Console, but it doesn't match my system language (French) and keeps displaying "Open in Console"). Tested on Ubuntu 22.04 with : - nautilus-extension-gnome-console 42~beta-1 - libnautilus-extension1a:amd64 1:42.2-0ubuntu1 - nautilus 1:42.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1993864/+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
Re: [Desktop-packages] [Bug 1873942] Re: [wayland] gnome-screenshot takes a screenshot of the wrong screen
I have upgraded to mutter 3.36.2-1ubuntu1~20.04.1 this morning and rebooted. I can confirm this new version fixes the problem for me. Thanks! Le mar. 12 mai 2020 à 22:36, Brian Murray a écrit : > Hello Guillaume, or anyone else affected, > > Accepted mutter into focal-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a > few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed- > focal to verification-done-focal. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-focal. In either case, without details of your testing we will > not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Tags added: verification-needed verification-needed-focal > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873942 > > Title: > [wayland] gnome-screenshot takes a screenshot of the wrong screen > > Status in GNOME Shell: > Unknown > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > I have a dual monitor setup, with the external monitor defined as the > "primary" one (and the laptop one secondary). > When using the Shift + PrtScr shortcut and choosing an area on the > external monitor, the screenshot saved in ~/Pictures shows this area but on > the _laptop_ screen. > (Choosing an area on the laptop screen works OK.) > > I use the vanilla Gnome session (with Wayland), installed with apt. > > [ Impact ] > > gnome-screenshot takes a screenshot of the wrong screen > > [ Test case ] > > In dual monitor setup, use Shift+PrtScr to take a screenshot in an > area in the external monitor. > > The saved area should respect the one you selected > > [ Regression potential ] > > Screenshot or screencasting may have not espected behavior > > > ProblemType: BugDistroRelease: Ubuntu 20.04 > Package: gnome-screenshot 3.36.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 > Uname: Linux 5.4.0-25-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: GNOME > Date: Mon Apr 20 20:58:46 2020 > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bashSourcePackage: gnome-screenshot > UpgradeStatus: No upgrade log present (probably fresh install) > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: GNOME > DistUpgraded: Fresh install > DistroCodename: focalDistroRelease: Ubuntu 20.04 > DistroVariant: ubuntu > DkmsStatus: >acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed > GraphicsCard: >Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2b Intel Corp. >Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor
[Desktop-packages] [Bug 1827727]
See Also: → https://webcompat.com/issues/30522, https://webcompat.com/issues/30529, https://webcompat.com/issues/30530, https://webcompat.com/issues/30534, https://webcompat.com/issues/30536, https://webcompat.com/issues/30539 -- 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/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827727]
See Also: → https://webcompat.com/issues/30556, https://webcompat.com/issues/30561, https://webcompat.com/issues/30562, https://webcompat.com/issues/30563, https://webcompat.com/issues/30564, https://webcompat.com/issues/30565, https://webcompat.com/issues/30566, https://webcompat.com/issues/30571, https://webcompat.com/issues/30572 -- 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/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827727]
See Also: → https://webcompat.com/issues/30576, https://webcompat.com/issues/30578, https://webcompat.com/issues/30584, https://webcompat.com/issues/30588, https://webcompat.com/issues/30600, https://webcompat.com/issues/30603, https://webcompat.com/issues/30637, https://webcompat.com/issues/30638, https://webcompat.com/issues/30643, https://webcompat.com/issues/30645 -- 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/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+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 1838441] [NEW] Metric length units conversion malformed expression
Public bug reported: Version 3.22.1, in Advanced Mode Select Length > Feet and any metric unit that ends with 'metres' (Kilometres, Metres, etc.) Now press 'to' button. It says 'Malformed expression'. It's only a typo because 'Metres' becomes 'meter'. If I correct 'meter' to 'metre' manually, it works fine. Language and Region settings on Ubuntu : English(Canada), Canada ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Calc_bug.gif" https://bugs.launchpad.net/bugs/1838441/+attachment/5280038/+files/Calc_bug.gif -- 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/1838441 Title: Metric length units conversion malformed expression Status in gnome-calculator package in Ubuntu: New Bug description: Version 3.22.1, in Advanced Mode Select Length > Feet and any metric unit that ends with 'metres' (Kilometres, Metres, etc.) Now press 'to' button. It says 'Malformed expression'. It's only a typo because 'Metres' becomes 'meter'. If I correct 'meter' to 'metre' manually, it works fine. Language and Region settings on Ubuntu : English(Canada), Canada To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1838441/+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 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Same! #19 with #24 works! Ubuntu 16.04 ASUS - ROG G502VS laptop nvidia 1070 / driver 390.25 Intel(R) Core(TM) i7-6700HQ CPU Thanks a lot! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+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 959084] Re: empathy-chat consistently uses 9-10 % CPU
I did some testing and this bug only appears when using Ubuntu's adium theme so it's either a theme bug (like some js infinite loop or something) or a webkit-gtk one. I can reproduce this bug on F17 as well. I won't have time to investigate this issue further but the next step could do to try some profiling using Webkit's inspector tool: - gsettings set org.gnome.Empathy.conversation enable-webkit-developer-tools true - Open a chat with the adium theme - Right click and select 'Inspect Element' It would be cool if some webkit(-gtk) could take a look on this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/959084 Title: empathy-chat consistently uses 9-10 % CPU Status in Ubuntu Adium Theme: New Status in Chat app, and Telepathy user interface: Unknown Status in “adium-theme-ubuntu” package in Ubuntu: Triaged Status in “empathy” package in Ubuntu: Triaged Bug description: This may have started since I upgraded my system to 12.04, it was certainly a recent development at around that time. I am using empathy for IRC only, connected to four channels on two servers, though even disabling all accounts does not change this. The empathy- chat process is very consistently at 9% CPU, with spikes at 10% or higher from time to time. I have tested this on mobile broadband, wifi and ethernet. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 09:28:49 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-03-12 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/959084/+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 959084] Re: empathy-chat consistently uses 9-10 % CPU
I don't think we use to have this bug with the previous ubuntu version. So another useful thing to do would be to bisect through the theme history and find which commit introduced this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/959084 Title: empathy-chat consistently uses 9-10 % CPU Status in Ubuntu Adium Theme: New Status in Chat app, and Telepathy user interface: Unknown Status in “adium-theme-ubuntu” package in Ubuntu: Triaged Status in “empathy” package in Ubuntu: Triaged Bug description: This may have started since I upgraded my system to 12.04, it was certainly a recent development at around that time. I am using empathy for IRC only, connected to four channels on two servers, though even disabling all accounts does not change this. The empathy- chat process is very consistently at 9% CPU, with spikes at 10% or higher from time to time. I have tested this on mobile broadband, wifi and ethernet. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.3.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 09:28:49 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-03-12 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/959084/+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 971809] Re: 168c:0032 Wifi connection unstable -- Atheros AR9485 ath9k
The problem is still here with "3.2.0-32-generic #51-Ubuntu SMP Wed Sep
26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux".
--
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/971809
Title:
168c:0032 Wifi connection unstable -- Atheros AR9485 ath9k
Status in “linux” package in Ubuntu:
Triaged
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
Using Ubuntu 12.04 beta 2, wifi connection is really unstable on my Asus UX31.
At the same place, with Windows 7, the connection is stable.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Mon Apr 2 20:58:59 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code
1: Error: Can't obtain connections: settings service is not running.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gfmichaud 1727 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdfe0 irq 53'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0269,10431427,00100100
HDA:80862805,80860101,0010'
Controls : 18
Simple ctrls : 8
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=384ec156-d35e-4d52-9404-4180b3520ddb
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
IpRoute:
default via 192.168.0.254 dev eth1 proto static
169.254.0.0/16 dev eth1 scope link metric 1000
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.30 metric 2
MachineType: ASUSTeK Computer Inc. UX31E
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
Package: network-manager 0.9.4.0-0ubuntu2
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=3698f1d7-5c60-473c-b752-c98e427883f7 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.78
StagingDrivers: rts5139 mei
Tags: precise staging precise
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
dmi.bios.date: 01/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
nmcli-con:
NAME UUID TYPE
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
AndroidGM 52f72e54-c826-4a4a-9619-3fef08de5496
802-11-wireless 1333888153 dim. 08 avril 2012 14:29:13 CEST yes
no /org/freedesktop/NetworkManager/Settings/1
CNGM_WEP 712368a2-4545-4f12-b2cc-f5ecc2394ef9
802-11-wireless 1334253900 jeu. 12 avril 2012 20:05:00 CEST yes
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth1 802-11-wireless connected
[Desktop-packages] [Bug 1044057] Re: empathy no longer allows for extended jabber configuration
The import code isn't run in this log. Are you sure you reset the sanity-cleaning-number gsetting key before ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1044057 Title: empathy no longer allows for extended jabber configuration Status in “empathy” package in Ubuntu: Confirmed Status in “empathy” source package in Quantal: Confirmed Bug description: I have been using Empathy for a longtime, primarily for Jabber to a private network. Recent updates in 12.10 imported my previous settings ok, but I am no longer able to edit those settings because when I click Empathy/Accounts from the global menu, I get the Online Accounts setup, and it doesn't seem to know about my previous setup. Furthermore, if I try to add a jabber account, the account setup is far too limited with only a jabber id and password presented, which prevents me from using empathy with the aforementioned private network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044057/+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 35223] Re: Laptop TFT monitor - brightness level is not saved
Still exists in 12.10 at this point of time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/35223 Title: Laptop TFT monitor - brightness level is not saved Status in Gnome Powermanager: Confirmed Status in “gnome-power-manager” package in Ubuntu: Triaged Status in “gnome-power-manager” source package in Lucid: Triaged Bug description: Every time I restart my computer, the monitors brightness has changed to the maximum possible. Please make it remember the settings. The computer is an IBM Thinkpad X-31 [2673-PXG] laptop. Full specification is available here : http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-58212 PLEASE NOTE: This bug has been filed on the WRONG package. I don't know which package or part of Ubuntu this error is part of. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/35223/+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 971809] Re: 168c:0032 Wifi connection unstable -- Atheros AR9485 ath9k
As confirmed on
http://ubuntuforums.org/showpost.php?p=12296138&postcount=1766 the
problem is still there in kernel 3.6.
What can I do to help ?
I have now been waiting for 8 months, hoping 12.10 will solve this, but it has
not. So I am willing to do what is required to help with solving this issue. My
laptop is almost unusable without Wifi.
--
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/971809
Title:
168c:0032 Wifi connection unstable -- Atheros AR9485 ath9k
Status in “linux” package in Ubuntu:
Triaged
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
Using Ubuntu 12.04 beta 2, wifi connection is really unstable on my Asus UX31.
At the same place, with Windows 7, the connection is stable.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Mon Apr 2 20:58:59 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code
1: Error: Can't obtain connections: settings service is not running.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gfmichaud 1727 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdfe0 irq 53'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0269,10431427,00100100
HDA:80862805,80860101,0010'
Controls : 18
Simple ctrls : 8
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=384ec156-d35e-4d52-9404-4180b3520ddb
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
IpRoute:
default via 192.168.0.254 dev eth1 proto static
169.254.0.0/16 dev eth1 scope link metric 1000
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.30 metric 2
MachineType: ASUSTeK Computer Inc. UX31E
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
Package: network-manager 0.9.4.0-0ubuntu2
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=3698f1d7-5c60-473c-b752-c98e427883f7 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.78
StagingDrivers: rts5139 mei
Tags: precise staging precise
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
dmi.bios.date: 01/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
nmcli-con:
NAME UUID TYPE
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
AndroidGM 52f72e54-c826-4a4a-9619-3fef08de5496
802-11-wireless 1333888153 dim. 08 avril 2012 14:29:13 CEST yes
no /org/freedesktop/NetworkManager/Settings/1
CNGM_WEP 712368a2-4545-4f12-b2cc-f5ecc2394ef9
802-11-wireless 1334253900 jeu. 12 avril 2012 20:05:00 CE
[Desktop-packages] [Bug 971809] Re: 168c:0032 Wifi connection unstable -- Atheros AR9485 ath9k
** Bug watch added: Linux Kernel Bug Tracker #49201
http://bugzilla.kernel.org/show_bug.cgi?id=49201
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=49201
Importance: Unknown
Status: Unknown
--
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/971809
Title:
168c:0032 Wifi connection unstable -- Atheros AR9485 ath9k
Status in The Linux Kernel:
Unknown
Status in “linux” package in Ubuntu:
Triaged
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
Using Ubuntu 12.04 beta 2, wifi connection is really unstable on my Asus UX31.
At the same place, with Windows 7, the connection is stable.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Mon Apr 2 20:58:59 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code
1: Error: Can't obtain connections: settings service is not running.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gfmichaud 1727 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xdfe0 irq 53'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0269,10431427,00100100
HDA:80862805,80860101,0010'
Controls : 18
Simple ctrls : 8
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=384ec156-d35e-4d52-9404-4180b3520ddb
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
IpRoute:
default via 192.168.0.254 dev eth1 proto static
169.254.0.0/16 dev eth1 scope link metric 1000
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.30 metric 2
MachineType: ASUSTeK Computer Inc. UX31E
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
Package: network-manager 0.9.4.0-0ubuntu2
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=3698f1d7-5c60-473c-b752-c98e427883f7 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.78
StagingDrivers: rts5139 mei
Tags: precise staging precise
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
dmi.bios.date: 01/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
nmcli-con:
NAME UUID TYPE
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
AndroidGM 52f72e54-c826-4a4a-9619-3fef08de5496
802-11-wireless 1333888153 dim. 08 avril 2012 14:29:13 CEST yes
no /org/freedesktop/NetworkManager/Settings/1
CNGM_WEP 712368a2-4545-4f12-b2cc-f5ecc2394ef9
802-11-wireless 1334253900 jeu. 12 avril 2012 20:05:00 CEST yes
no /org/freedesktop/NetworkManager/Settings/0
nmc
[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?
It may have something to do with the powersaving modes of some graphic cards, too. On the same laptop, booting with the power plugged in causes this problem, but everyting's fine when the power is plugged off. -- 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/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 1078178] [NEW] Screen doesn not lock (until you do it manually once)
Public bug reported: The screen does not lock even though - the "lock" switch is activated in the "brightness and locking" screen - "lock screen after" is set to "screen turns off" - and "ask for my password..." is checked This problem can be fixed by : - activating manually the lock screen once (ctrl + alt + L) - or typing "nohup gnome-screensaver &" in a terminal so I think the problem is that gnome-screensaver does not start automatically or crashes when it does. Ubuntu 12.10 gnome-screensaver 3.6.0-0ubuntu2 ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1078178 Title: Screen doesn not lock (until you do it manually once) Status in “gnome-screensaver” package in Ubuntu: New Bug description: The screen does not lock even though - the "lock" switch is activated in the "brightness and locking" screen - "lock screen after" is set to "screen turns off" - and "ask for my password..." is checked This problem can be fixed by : - activating manually the lock screen once (ctrl + alt + L) - or typing "nohup gnome-screensaver &" in a terminal so I think the problem is that gnome-screensaver does not start automatically or crashes when it does. Ubuntu 12.10 gnome-screensaver 3.6.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1078178/+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 1078178] Re: Screen doesn not lock (until you do it manually once)
I added "gnome-screensaver" to the startup programs ; this solved the problem. But it should be done by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1078178 Title: Screen doesn not lock (until you do it manually once) Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: The screen does not lock even though - the "lock" switch is activated in the "brightness and locking" screen - "lock screen after" is set to "screen turns off" - and "ask for my password..." is checked This problem can be fixed by : - activating manually the lock screen once (ctrl + alt + L) - or typing "nohup gnome-screensaver &" in a terminal so I think the problem is that gnome-screensaver does not start automatically or crashes when it does. Ubuntu 12.10 gnome-screensaver 3.6.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1078178/+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
