[Desktop-packages] [Bug 2061686] Re: After updating to ubuntu 24.04, WiFi doesn't connect to secured networks at login or resume from sleep
Forgetting and reconnecting to the WiFi networks solves the issue. Fell free to mark this bug as solved if you consider that this workaround invalidates the bug. -- 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/2061686 Title: After updating to ubuntu 24.04, WiFi doesn't connect to secured networks at login or resume from sleep Status in network-manager package in Ubuntu: New Bug description: I updated a Thinkpad T14 AMD Gen 2 from 23.10 to 24.04. Since the update, WiFi doesn't automatically connect at login or when resuming from sleep if the network is secured with a password. It does connect automatically if it finds a remembered open network. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 17:50:40 2024 InstallationDate: Installed on 2022-02-02 (803 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061686/+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 2061912] Re: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04
** Package changed: network-manager (Ubuntu) => linux-lowlatency (Ubuntu) -- 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/2061912 Title: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04 Status in linux-lowlatency package in Ubuntu: New Bug description: After a recent update of packages (in the last couple of hours or so) neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are able to load pages. Gnome Web is the only one that seems to work. Also, apt loads fine. Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:55:41 2024 InstallationDate: Installed on 2022-02-02 (804 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2061912/+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 2061912] [NEW] After a very recent update most browsers are not able to load webpages in Ubuntu 24.04
I could narrow down the problem to linux-lowlatency 6.8.0-25.25.3. Before updating to Ubuntu 24.04 I had the lowlatency kernel installed. When updating it reverted back to generic and the last update installed linux-lowlatency 6.8.0-25.25.3, which seems to have generated the bug. Uninstalling the lowlatency kernel and running on the generic solves the issue. On Tue, Apr 16, 2024 at 7:05 PM Nicolás Abel Carbone < 2061...@bugs.launchpad.net> wrote: > Public bug reported: > > After a recent update of packages (in the last couple of hours or so) > neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are > able to load pages. Gnome Web is the only one that seems to work. Also, > apt loads fine. > > Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. > > ProblemType: Bug > DistroRelease: Ubuntu 24.04 > Package: network-manager 1.46.0-1ubuntu2 > ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 > Uname: Linux 6.8.0-25-lowlatency x86_64 > ApportVersion: 2.28.0-0ubuntu1 > Architecture: amd64 > CRDA: N/A > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Tue Apr 16 18:55:41 2024 > InstallationDate: Installed on 2022-02-02 (804 days ago) > InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) > IpRoute: > default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 > 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 > linkdown > 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 > metric 600 > 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 > linkdown > SourcePackage: network-manager > UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) > nmcli-nm: > RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING > WIFI-HW WIFI WWAN-HW WWAN > ejecutando 1.46.0 conectado Iniciado total activado > activado activado missing activado > > ** Affects: network-manager (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: amd64 apport-bug noble wayland-session > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2061912 > > Title: > After a very recent update most browsers are not able to load webpages > in Ubuntu 24.04 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061912/+subscriptions > > -- Nicolás Abel Carbone Doctor en Física Investigador Asistente CONICET JTP en Facultad de Ciencias Exactas UNCPBA Grupo de Óptica Biomédica - CIFICEN-CONICET-UNCPBA Research Gate <https://epsilonh.com.ar> - epsilon.h <https://epsilonh.com.ar> - Bionirs <http://www.bionirs.com> - Github <https://github.com/nicocarbone> *Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo indique el mail, por favor no se sienta obligado a responder este mensaje fuera de su horario de trabajo habitual.* *My working hours may not be your working hours. Unless otherwise specified in the mail, please do not feel obligated to reply outside of your normal work schedule.* -- 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/2061912 Title: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04 Status in network-manager package in Ubuntu: New Bug description: After a recent update of packages (in the last couple of hours or so) neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are able to load pages. Gnome Web is the only one that seems to work. Also, apt loads fine. Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:55:41 2024 InstallationDate: Installed on 2022-02-02 (804 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP C
[Desktop-packages] [Bug 2061912] [NEW] After a very recent update most browsers are not able to load webpages in Ubuntu 24.04
Public bug reported: After a recent update of packages (in the last couple of hours or so) neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are able to load pages. Gnome Web is the only one that seems to work. Also, apt loads fine. Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:55:41 2024 InstallationDate: Installed on 2022-02-02 (804 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2061912 Title: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04 Status in network-manager package in Ubuntu: New Bug description: After a recent update of packages (in the last couple of hours or so) neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are able to load pages. Gnome Web is the only one that seems to work. Also, apt loads fine. Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:55:41 2024 InstallationDate: Installed on 2022-02-02 (804 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061912/+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 2061686] [NEW] After updating to ubuntu 24.04, WiFi doesn't connect to secured networks at login or resume from sleep
Public bug reported: I updated a Thinkpad T14 AMD Gen 2 from 23.10 to 24.04. Since the update, WiFi doesn't automatically connect at login or when resuming from sleep if the network is secured with a password. It does connect automatically if it finds a remembered open network. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 17:50:40 2024 InstallationDate: Installed on 2022-02-02 (803 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2061686 Title: After updating to ubuntu 24.04, WiFi doesn't connect to secured networks at login or resume from sleep Status in network-manager package in Ubuntu: New Bug description: I updated a Thinkpad T14 AMD Gen 2 from 23.10 to 24.04. Since the update, WiFi doesn't automatically connect at login or when resuming from sleep if the network is secured with a password. It does connect automatically if it finds a remembered open network. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 17:50:40 2024 InstallationDate: Installed on 2022-02-02 (803 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061686/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
@jbicha sorry if I added noise. But the WiFi problem only happens with secured WiFi networks, not open ones. It seemed plausible that they are related, as the password for the WiFi network needs to be retrieved somewhere (the keyring, I assumed). But I will report a different bug report then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gnome-keyring package in Ubuntu: Triaged Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I am having the same problem after upgrading from 23.10 on a Thinkpad T14 AMD Gen 2. Another problem I am having is that WiFi is not automatically connected after log-in. I suppose it is related to this bug, is anyone else having this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gnome-keyring package in Ubuntu: Triaged Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+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 2045772] [NEW] Gnome session freezes a few seconds after starting Meet on Chrome under Wayland
Public bug reported: Since updating to Ubuntu 23.10, every time I start a Google Meet meeting, with the webcam on, in Chrome under Wayland after a few second of working fine the computer freezes and the screen starts flashing every couple of seconds. I can't do anything else but force restart the computer. This problem only happens in Chrome (not Firefox) under Wayland (it works fine on X11). I understand this may be a bug of Chrome. But the desktop shouldn't have an unrecoverable freeze even if an application crashes. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 12:03:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (672 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (68 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages -- 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/2045772 Title: Gnome session freezes a few seconds after starting Meet on Chrome under Wayland Status in gnome-shell package in Ubuntu: New Bug description: Since updating to Ubuntu 23.10, every time I start a Google Meet meeting, with the webcam on, in Chrome under Wayland after a few second of working fine the computer freezes and the screen starts flashing every couple of seconds. I can't do anything else but force restart the computer. This problem only happens in Chrome (not Firefox) under Wayland (it works fine on X11). I understand this may be a bug of Chrome. But the desktop shouldn't have an unrecoverable freeze even if an application crashes. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 12:03:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (672 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045772/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I can confirm @cmmrandau findings. mutter 45.0-3ubuntu 3 does not fix the bug but Martin's workaround works for me. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I can confirm @cmmrandau findings. mutter 45.0-3ubuntu 3 does not fix the bug but Martin's workaround works for me. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2037756] [NEW] Gnome session crashes after resume from suspend
Public bug reported: I upgraded to the Ubuntu 23.10 beta from 23.04. After the upgrade, every time I suspend the laptop and resume from suspend the gnome session crashes and I am returned to the login screen. I am using a Thinkpad T14 gen 2 AMD laptop. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 16:25:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (604 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic 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/2037756 Title: Gnome session crashes after resume from suspend Status in gnome-shell package in Ubuntu: New Bug description: I upgraded to the Ubuntu 23.10 beta from 23.04. After the upgrade, every time I suspend the laptop and resume from suspend the gnome session crashes and I am returned to the login screen. I am using a Thinkpad T14 gen 2 AMD laptop. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 16:25:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (604 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037756/+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 2023500] Re: Ctrl + click and Shift + click don't work to select multiple files
I use list view. I just checked and the bug is not present in icon view, I am sorry I didn't realize it before. I am using a Spanish (latinamerica) layout, keyboard and mouse are the only input methods active. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023500 Title: Ctrl + click and Shift + click don't work to select multiple files Status in nautilus package in Ubuntu: Incomplete Bug description: I am trying to select multiple files in nautilus with keyboard + mouse and none of the default method works. Neither Ctrl + left clicking on each file or Shift + left clicking and selecting the last item work. Selecting using only the mouse by dragging over multiple files do work. I can reproduce this bug in two different PCs running Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 17:05:50 2023 InstallationDate: Installed on 2022-02-02 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-15 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023500/+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 2023500] [NEW] Ctrl + click and Shift + click don't work to select multiple files
Public bug reported: I am trying to select multiple files in nautilus with keyboard + mouse and none of the default method works. Neither Ctrl + left clicking on each file or Shift + left clicking and selecting the last item work. Selecting using only the mouse by dragging over multiple files do work. I can reproduce this bug in two different PCs running Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 17:05:50 2023 InstallationDate: Installed on 2022-02-02 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-15 (57 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar third-party-packages wayland-session ** Summary changed: - Ctrl + click and Shift + click doesn't work to select multiple files + Ctrl + click and Shift + click don't work to select multiple files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023500 Title: Ctrl + click and Shift + click don't work to select multiple files Status in nautilus package in Ubuntu: New Bug description: I am trying to select multiple files in nautilus with keyboard + mouse and none of the default method works. Neither Ctrl + left clicking on each file or Shift + left clicking and selecting the last item work. Selecting using only the mouse by dragging over multiple files do work. I can reproduce this bug in two different PCs running Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 17:05:50 2023 InstallationDate: Installed on 2022-02-02 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-15 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023500/+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 2016925] Re: Firefox window is visually corrupted after upgrading to Ubuntu 23.04
Switching to the beta firefox snap channel solves the issue. -- 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/2016925 Title: Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: New Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 2016925] [NEW] Firefox window is visually corrupted after upgrading to Ubuntu 23.04
Public bug reported: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/2016925/+attachment/5665069/+files/Captura%20desde%202023-04-18%2018-04-09.png -- 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/2016925 Title: Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: New Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 2016387] [NEW] After updating to 23.04, none of the integrated shell extensions work
Public bug reported: After updating to 23.04, none of the integrated shell extensions work. This includes the dock, desktop icons and appindicators, for example. Also, and I think related to this, the Desktop tab on the settings app doesn't work either. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 15 12:38:49 2023 InstallationDate: Installed on 2022-02-02 (436 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Captura desde 2023-04-15 12-40-13.png" https://bugs.launchpad.net/bugs/2016387/+attachment/5664246/+files/Captura%20desde%202023-04-15%2012-40-13.png ** Description changed: - After updating to 23.04, none of the integrated shell extensions work. + After updating to 23.04, none of the integrated shell extensions work. This includes the dock and desktop icons, for example. - Also, and I think related to this, the Appearance on the settings + Also, and I think related to this, the Desktop tab on the settings app doesn't work either. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 15 12:38:49 2023 InstallationDate: Installed on 2022-02-02 (436 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago) ** Description changed: After updating to 23.04, none of the integrated shell extensions work. - This includes the dock and desktop icons, for example. + This includes the dock, desktop icons and appindicators, for example. Also, and I think related to this, the Desktop tab on the settings app doesn't work either. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 15 12:38:49 2023 InstallationDate: Installed on 2022-02-02 (436 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2016387 Title: After updating to 23.04, none of the integrated shell extensions work Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After updating to 23.04, none of the integrated shell extensions work. This includes the dock, desktop icons and appindicators, for example. Also, and I think related to this, the Desktop tab on the settings app doesn't work either. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 15 12:38:49 2023 InstallationDate: Installed on 2022-02-02 (436 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2016387/+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 1992860] [NEW] App grid changes from 8 columns to 6 columns of icons in the middle of the animation
Public bug reported: When doing the three-finger touchpad gesture to reveal the app grid, in the transition between the first screen with the desktop overview and the second screen with the app grid, the app grid starts animating with 8 columns (in a 1920x1080 screen resolution at least) and abruptly changes to 6 columns. See attached video. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 20:02:16 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (253 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-29 (14 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "Video showing the bug" https://bugs.launchpad.net/bugs/1992860/+attachment/5623988/+files/Grabaci%C3%B3n%20de%20pantalla%20desde%202022-10-13%2020-01-41.webm ** Summary changed: - App grid changes from 8 row to 6 rows of icons in the middle of the animation + App grid changes from 8 columns to 6 columns of icons in the middle of the animation -- 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/1992860 Title: App grid changes from 8 columns to 6 columns of icons in the middle of the animation Status in gnome-shell package in Ubuntu: New Bug description: When doing the three-finger touchpad gesture to reveal the app grid, in the transition between the first screen with the desktop overview and the second screen with the app grid, the app grid starts animating with 8 columns (in a 1920x1080 screen resolution at least) and abruptly changes to 6 columns. See attached video. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 20:02:16 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (253 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-29 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992860/+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 1991496] [NEW] Permission denied when trying to open a pdf file form Google Drive
Public bug reported: I logged into Google Drive on Gnome Online Accounts, and I can access my Google Drive files from nautilus. However, when I try to open a pdf file from said folder, I can't open it. I get a "permission denied". Other files open fine. Okular is also able to open the pdf file. See attached screenshot with the error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: evince 43.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 17:27:12 2022 InstallationDate: Installed on 2022-02-02 (242 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: evince UpgradeStatus: Upgraded to kinetic on 2022-09-29 (3 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1991496/+attachment/5620621/+files/Captura%20desde%202022-10-02%2017-27-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1991496 Title: Permission denied when trying to open a pdf file form Google Drive Status in evince package in Ubuntu: New Bug description: I logged into Google Drive on Gnome Online Accounts, and I can access my Google Drive files from nautilus. However, when I try to open a pdf file from said folder, I can't open it. I get a "permission denied". Other files open fine. Okular is also able to open the pdf file. See attached screenshot with the error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: evince 43.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 17:27:12 2022 InstallationDate: Installed on 2022-02-02 (242 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: evince UpgradeStatus: Upgraded to kinetic on 2022-09-29 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1991496/+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 1991393] [NEW] Gnome calculator doesn't follow accent color
Public bug reported: In Ubuntu 22.10 beta, gnome calculator (at least, there may be more affected apps) doesn't follow the accent color selected in Appearance settings. In the attached screenshot you can see how I have the green-teal color selected as accent color in settings but the calculator is using orange. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-calculator 1:43.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 30 09:56:34 2022 InstallationDate: Installed on 2022-02-02 (239 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-calculator UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1991393/+attachment/5620272/+files/Captura%20desde%202022-09-30%2009-56-18.png -- 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/1991393 Title: Gnome calculator doesn't follow accent color Status in gnome-calculator package in Ubuntu: New Bug description: In Ubuntu 22.10 beta, gnome calculator (at least, there may be more affected apps) doesn't follow the accent color selected in Appearance settings. In the attached screenshot you can see how I have the green-teal color selected as accent color in settings but the calculator is using orange. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-calculator 1:43.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 30 09:56:34 2022 InstallationDate: Installed on 2022-02-02 (239 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-calculator UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1991393/+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 1991333] [NEW] Night light is not available in gnome-control-center despite being enabled in quick settings
Public bug reported: In the gnome-control-center, under Monitors->Night light, there is a banner saying that night light is not available and "that may be the result of the graphics driver or that you are using remote desktop" (loosely translated from Spanish, see screenshot). None of that is true and Night light worked fine before updating to 22.10 beta. Moreover, night light was setup to activate at dusk before updating and that seems to be working. It can even be toggled using the quick settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 29 18:17:51 2022 InstallationDate: Installed on 2022-02-02 (239 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1991333/+attachment/5620139/+files/Captura%20desde%202022-09-29%2018-19-32.png -- 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/1991333 Title: Night light is not available in gnome-control-center despite being enabled in quick settings Status in gnome-control-center package in Ubuntu: New Bug description: In the gnome-control-center, under Monitors->Night light, there is a banner saying that night light is not available and "that may be the result of the graphics driver or that you are using remote desktop" (loosely translated from Spanish, see screenshot). None of that is true and Night light worked fine before updating to 22.10 beta. Moreover, night light was setup to activate at dusk before updating and that seems to be working. It can even be toggled using the quick settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 29 18:17:51 2022 InstallationDate: Installed on 2022-02-02 (239 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1991333/+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 1970489] [NEW] Some (eg firefox) snap's modal dialogs don't follow dark-theme preference until log out and log back
Public bug reported: In firefox for example, if I change from dark to light theme or from dark to light, while the main app follow the theme change, the modal dialogs (eg. Save page as...) don't change theme. In the attached screenshot, you can see a dark themed firefox and a light themed modal dialog. If I log out and back in, the modal dialogs now follow the theme correctly. Another app that seems to have the same issue is telegram-desktop. But other, like vscode or cura-slicer (all snaps) work as expected. Initially I thought it was a firefox issue and filed a bug report in bugzilla. You can see the discussion about it here: https://bugzilla.mozilla.org/show_bug.cgi?id=1766339 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:29:50 2022 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: xdg-desktop-portal UpgradeStatus: Upgraded to jammy on 2022-03-18 (39 days ago) ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1970489/+attachment/5584128/+files/Captura%20desde%202022-04-25%2019-23-12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1970489 Title: Some (eg firefox) snap's modal dialogs don't follow dark-theme preference until log out and log back Status in xdg-desktop-portal package in Ubuntu: New Bug description: In firefox for example, if I change from dark to light theme or from dark to light, while the main app follow the theme change, the modal dialogs (eg. Save page as...) don't change theme. In the attached screenshot, you can see a dark themed firefox and a light themed modal dialog. If I log out and back in, the modal dialogs now follow the theme correctly. Another app that seems to have the same issue is telegram-desktop. But other, like vscode or cura-slicer (all snaps) work as expected. Initially I thought it was a firefox issue and filed a bug report in bugzilla. You can see the discussion about it here: https://bugzilla.mozilla.org/show_bug.cgi?id=1766339 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:29:50 2022 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: xdg-desktop-portal UpgradeStatus: Upgraded to jammy on 2022-03-18 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1970489/+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 1970282] [NEW] Flatpak apps are not properly themed if a accent color other than the default is choosed
Public bug reported: If I use any accent color other than the default orange, flatpak apps use the default old adwaita theme. These is specially obvious/important if using the dark variant of the theme, as the flatpak app will use a light theme. I attach screenshots of a flatpak app when using the default accent color and a different accent color, as well as the list of the installed yaru flatpak themes. The used accent color seems to be installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gtk 22.04.4 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 19:09:38 2022 InstallationDate: Installed on 2022-02-02 (82 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yaru-theme UpgradeStatus: Upgraded to jammy on 2022-03-18 (38 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Prussian green accent color" https://bugs.launchpad.net/bugs/1970282/+attachment/5583641/+files/Captura%20desde%202022-04-25%2019-12-02.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1970282 Title: Flatpak apps are not properly themed if a accent color other than the default is choosed Status in yaru-theme package in Ubuntu: New Bug description: If I use any accent color other than the default orange, flatpak apps use the default old adwaita theme. These is specially obvious/important if using the dark variant of the theme, as the flatpak app will use a light theme. I attach screenshots of a flatpak app when using the default accent color and a different accent color, as well as the list of the installed yaru flatpak themes. The used accent color seems to be installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gtk 22.04.4 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 19:09:38 2022 InstallationDate: Installed on 2022-02-02 (82 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yaru-theme UpgradeStatus: Upgraded to jammy on 2022-03-18 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1970282/+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 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04
I am using a AMD-based computer using the radeon open-source graphics drivers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 Status in gnome-session package in Ubuntu: New Bug description: After some recent update to Ubuntu 22.04 dev, X11 is selected by default and there is no longer the option to select the display protocol at login. It seems I am not the only affected: https://askubuntu.com/questions/1402671/ubuntu-no-gear-for- waylaland-x11 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-session 42.0-1ubuntu2 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 22:20:35 2022 InstallationDate: Installed on 2022-02-02 (72 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+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 1969254] [NEW] wayland session not longer an option after recent update on Ubuntu 22.04
Public bug reported: After some recent update to Ubuntu 22.04 dev, X11 is selected by default and there is no longer the option to select the display protocol at login. It seems I am not the only affected: https://askubuntu.com/questions/1402671/ubuntu-no-gear-for-waylaland-x11 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-session 42.0-1ubuntu2 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 22:20:35 2022 InstallationDate: Installed on 2022-02-02 (72 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago) ** Affects: gnome-session (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-session in Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 Status in gnome-session package in Ubuntu: New Bug description: After some recent update to Ubuntu 22.04 dev, X11 is selected by default and there is no longer the option to select the display protocol at login. It seems I am not the only affected: https://askubuntu.com/questions/1402671/ubuntu-no-gear-for- waylaland-x11 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-session 42.0-1ubuntu2 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 22:20:35 2022 InstallationDate: Installed on 2022-02-02 (72 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+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 1968485] [NEW] Logged out of google account on update to Jammy; can't log back in
*** This bug is a duplicate of bug 1966418 *** https://bugs.launchpad.net/bugs/1966418 Public bug reported: After upgrading to Jammy my google account was logged out. When trying to log back in, the pop-up window which should ask for my credentials shows only a white screen (see attached screenshots). Deleting and re-adding the googgle account doesn't work either, with the same issue happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 Uname: Linux 5.17.1-051701-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 12:38:02 2022 InstallationDate: Installed on 2022-02-02 (66 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to jammy on 2022-03-18 (22 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1968485/+attachment/5579023/+files/Captura%20desde%202022-04-10%2012-37-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1968485 Title: Logged out of google account on update to Jammy; can't log back in Status in gnome-online-accounts package in Ubuntu: New Bug description: After upgrading to Jammy my google account was logged out. When trying to log back in, the pop-up window which should ask for my credentials shows only a white screen (see attached screenshots). Deleting and re-adding the googgle account doesn't work either, with the same issue happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 Uname: Linux 5.17.1-051701-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 12:38:02 2022 InstallationDate: Installed on 2022-02-02 (66 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to jammy on 2022-03-18 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1968485/+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 1949598] Re: Wrong resolution on second monitor after resume from suspend
I cannot reproduce the bug on the stock kernel, but the whole resume from suspend process doesn't work reliably on the stock kernel for my config. So, I don't know if the bug is not present or if I don't see it because I never get to that point. I'll keep researching and see if I can reproduce the issue. El mié, 3 de nov. de 2021 a la(s) 23:50, Daniel van Vugt ( 1949...@bugs.launchpad.net) escribió: > Thanks for the bug report. > > Does the same bug occur if you log into 'Ubuntu on Xorg'? > > Does the same bug occur if you run the Ubuntu kernel instead of the > generic one you have installed? > > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1949598 > > Title: > Wrong resolution on second monitor after resume from suspend > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949598/+subscriptions > > -- Nicolás Abel Carbone Doctor en Física - Becario Posdoctoral CIFICEN-CONICET-UNCPBA Research Gate <https://www.researchgate.net/profile/Nicolas_Carbone> epsilon.h <https://epsilonh.com.ar> Bionirs <http://bionirs.com> *Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo indique el mail, por favor no se sienta obligado a responder este mensaje fuera de su horario de trabajo habitual.* *My working hours may not be your working hours. Unless otherwise specified in the mail, please do not feel obligated to reply outside of your normal work schedule.* -- 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/1949598 Title: Wrong resolution on second monitor after resume from suspend Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am running Ubuntu 21.10 on wayland. I have two monitors connected to a AMD 5500xt, one via HDMI and another, the secondary, via DP, with an DP->VGA adaptor. This setup worked just fine on Ubuntu 21.04, also on wayland. After updating to 21.10, often (but not always) the secondary monitor wakes up showing a wrong, lower resolution. Instead of the normal 1280x1024, it starts at 800x600. Despite this, in Gnome Settings the resolution is still reported as 1280x1024. I can solve this issue by changing the resolution in settings and reverting back to 1280x1024. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 Uname: Linux 5.13.0-051300-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 3 11:44:16 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-04 (364 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-03 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949598/+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 1946525] Re: Disks are not being mounted automatically
I am seeing the same behavior on real hardware after upgrading to Ubuntu 21.10. This is what I see on the logs after connecting a TOSHIBA SSD in a SATAtoUSB enclosure (I plugged it two times, at 12:08 and 12:09): 12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1. 12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1. 12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_arm64 /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1. 12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_arm /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1. 12:09:16 mtp-probe: bus: 2, device: 6 was not an MTP device 12:09:16 mtp-probe: bus: 2, device: 6 was not an MTP device 12:09:16 mtp-probe: checking bus 2, device 6: "/sys/devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3" 12:09:16 systemd-udevd: 2-2.3:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3/2-2.3:1.0 0:0' failed with exit code 1. 12:09:16 mtp-probe: bus: 2, device: 6 was not an MTP device 12:09:16 kernel: scsi host9: uas 12:09:16 kernel: usb 2-2.3: SerialNumber: 00123AE3 12:09:12 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper remove snap_qemu-virgil_qemu-virgil /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3 189:132' failed with exit code 1. 12:09:12 kernel: sd 9:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK 12:09:12 kernel: usb 2-2.3: USB disconnect, device number 5 12:08:47 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3 189:132' failed with exit code 1. 12:08:47 kernel: sd 9:0:0:0: [sda] Attached SCSI disk 12:08:47 kernel: sda: sda1 12:08:47 mtp-probe: bus: 2, device: 5 was not an MTP device 12:08:47 systemd-udevd: 2-2.3:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3/2-2.3:1.0 0:0' failed with exit code 1. 12:08:47 mtp-probe: bus: 2, device: 5 was not an MTP device 12:08:47 kernel: sd 9:0:0:0: [sda] Optimal transfer size 33553920 bytes 12:08:47 mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3" 12:08:47 kernel: scsi 9:0:0:0: Direct-Access TOSHIBA THNSNH128GBS HTRA PQ: 0 ANSI: 6 12:08:47 kernel: usb 2-2.3: SerialNumber: 00123AE3 12:08:43 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper remove snap_qemu-virgil_qemu-virgil /devices/pci:00/:00:01.3/:02:00.0/usb2/2-2/2-2.3 189:130' failed with exit code 1. 12:08:43 kernel: sd 9:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK 12:08:43 udisksd: Cleaning up mount point /media/nicolas/SSD128 (device 8:1 no longer exists) 12:08:43 kernel: sd 9:0:0:0: [sda] Synchronizing SCSI cache 12:08:43 kernel: usb 2-2.3: USB disconnect, device number 3 -- 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/1946525 Title: Disks are not being mounted automatically Status in udisks2 package in Ubuntu: Incomplete Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine:
[Desktop-packages] [Bug 1946523] [NEW] Thin line over the top rigth and left corners of GTK3 windows when unfocused
Public bug reported: When a GTK3 window is unfocused a thin line appears over the top corners. It does not appear when the window is focused or in apps that do not use client-side controls. Attached screenshot shows the bug on the calculator and nautilus. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: yaru-theme-gtk 21.10.2 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 16:54:08 2021 InstallationDate: Installed on 2018-02-23 (1322 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to impish on 2021-09-22 (16 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "Captura de pantalla de 2021-10-08 16-53-25.png" https://bugs.launchpad.net/bugs/1946523/+attachment/5531664/+files/Captura%20de%20pantalla%20de%202021-10-08%2016-53-25.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1946523 Title: Thin line over the top rigth and left corners of GTK3 windows when unfocused Status in yaru-theme package in Ubuntu: New Bug description: When a GTK3 window is unfocused a thin line appears over the top corners. It does not appear when the window is focused or in apps that do not use client-side controls. Attached screenshot shows the bug on the calculator and nautilus. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: yaru-theme-gtk 21.10.2 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 16:54:08 2021 InstallationDate: Installed on 2018-02-23 (1322 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to impish on 2021-09-22 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1946523/+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 1946159] [NEW] Games (eg. splitgate) keeps minimizing to dash when Desktop Icons NG is enabled
Public bug reported: Steps to reproduce: * Open a game (splitgate shows the problem, it is free-to-play on Steam) * Alt-tab out of the game * Try to come back to the game Result: The games gains focus for only a second and then is again minimized to dash. The problem goes away if the default Desktop Icons NG extension is disabled. I am running Ubuntu 21.10 beta using Mesa on a Radeon 5500XT, using Wayland. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-desktop-icons-ng 20-0ubuntu1 Uname: Linux 5.14.9-xanmod2 x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 20:16:12 2021 InstallationDate: Installed on 2020-11-04 (335 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: Upgraded to impish on 2021-10-03 (2 days ago) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1946159 Title: Games (eg. splitgate) keeps minimizing to dash when Desktop Icons NG is enabled Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Steps to reproduce: * Open a game (splitgate shows the problem, it is free-to-play on Steam) * Alt-tab out of the game * Try to come back to the game Result: The games gains focus for only a second and then is again minimized to dash. The problem goes away if the default Desktop Icons NG extension is disabled. I am running Ubuntu 21.10 beta using Mesa on a Radeon 5500XT, using Wayland. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-desktop-icons-ng 20-0ubuntu1 Uname: Linux 5.14.9-xanmod2 x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 20:16:12 2021 InstallationDate: Installed on 2020-11-04 (335 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: Upgraded to impish on 2021-10-03 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1946159/+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 1936440] Re: Firefox crashes or hangs at start after update to v90
Refreshing firefox solved the issue. It never happened before on any update. Sorry for the unnecessary bug submit. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1936440 Title: Firefox crashes or hangs at start after update to v90 Status in firefox package in Ubuntu: Invalid Bug description: I just updated firefox to v90 via apt. After update, firefox askted to be restarted. After reopening, it crashed. Now, everytime I open firefox, it hangs with a blank page not accepting any input. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 90.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USUARIO PID ACCESO ORDEN /dev/snd/controlC0: nicolas4235 F pulseaudio BuildID: 20210705185941 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jul 15 19:56:23 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-23 (1238 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) MostRecentCrashID: bp-1914cb38-e57e-48a8-b26f-ee2bb0200804 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=57.0.1/20171129230227 (Out of date) Profile0 (Default) - LastVersion=90.0/20210705185941 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-1914cb38-e57e-48a8-b26f-ee2bb0200804 UpgradeStatus: Upgraded to hirsute on 2021-04-01 (105 days ago) dmi.bios.date: 03/09/2021 dmi.bios.release: 2.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.1 dmi.board.name: 05HM5Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.1:bd03/09/2021:br2.15:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1936440/+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 1936440] [NEW] Firefox crashes or hangs at start after update to v90
Public bug reported: I just updated firefox to v90 via apt. After update, firefox askted to be restarted. After reopening, it crashed. Now, everytime I open firefox, it hangs with a blank page not accepting any input. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 90.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USUARIO PID ACCESO ORDEN /dev/snd/controlC0: nicolas4235 F pulseaudio BuildID: 20210705185941 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jul 15 19:56:23 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-23 (1238 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) MostRecentCrashID: bp-1914cb38-e57e-48a8-b26f-ee2bb0200804 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=57.0.1/20171129230227 (Out of date) Profile0 (Default) - LastVersion=90.0/20210705185941 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-1914cb38-e57e-48a8-b26f-ee2bb0200804 UpgradeStatus: Upgraded to hirsute on 2021-04-01 (105 days ago) dmi.bios.date: 03/09/2021 dmi.bios.release: 2.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.15.1 dmi.board.name: 05HM5Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.15.1:bd03/09/2021:br2.15:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1936440 Title: Firefox crashes or hangs at start after update to v90 Status in firefox package in Ubuntu: New Bug description: I just updated firefox to v90 via apt. After update, firefox askted to be restarted. After reopening, it crashed. Now, everytime I open firefox, it hangs with a blank page not accepting any input. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 90.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USUARIO PID ACCESO ORDEN /dev/snd/controlC0: nicolas4235 F pulseaudio BuildID: 20210705185941 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jul 15 19:56:23 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-23 (1238 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) MostRecentCrashID: bp-1914cb38-e57e-48a8-b26f-ee2bb0200804 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @
[Desktop-packages] [Bug 1923459] [NEW] evince doesn't show filename or PDF title on the title bar
Public bug reported: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "Captura de pantalla de 2021-04-12 10-42-58.png" https://bugs.launchpad.net/bugs/1923459/+attachment/5486925/+files/Captura%20de%20pantalla%20de%202021-04-12%2010-42-58.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1923459 Title: evince doesn't show filename or PDF title on the title bar Status in evince package in Ubuntu: New Bug description: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1923459/+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 1899261] [NEW] gnome 3.38 app's CSD header bar buttons are cropped
Public bug reported: In Gnome 3.38 header bar buttons are taller and usually include both an icon and text label. They are also responsive. Some of this new features seems to broke yaru theme. It is specially obvious in Gnome Web's settings window, but also in Gnome Games. I attach some screenshots of the issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: yaru-theme-gtk 20.10.4 ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13 Uname: Linux 5.8.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 10:32:52 2020 InstallationDate: Installed on 2018-02-23 (959 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to groovy on 2020-10-01 (8 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Gnome Web header" https://bugs.launchpad.net/bugs/1899261/+attachment/5420437/+files/Captura%20de%20pantalla%20de%202020-10-10%2010-31-54.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1899261 Title: gnome 3.38 app's CSD header bar buttons are cropped Status in yaru-theme package in Ubuntu: New Bug description: In Gnome 3.38 header bar buttons are taller and usually include both an icon and text label. They are also responsive. Some of this new features seems to broke yaru theme. It is specially obvious in Gnome Web's settings window, but also in Gnome Games. I attach some screenshots of the issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: yaru-theme-gtk 20.10.4 ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13 Uname: Linux 5.8.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 10:32:52 2020 InstallationDate: Installed on 2018-02-23 (959 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to groovy on 2020-10-01 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1899261/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Vaapi seems to be working for mpv and Firefox under wayland though. Glad to be of help! :) El mié., 20 de may. de 2020 a la(s) 11:21, Olivier Tilloy ( olivier.til...@canonical.com) escribió: > @Nicolás: thanks, that's very useful feedback. > > @Michel: thanks, that's the problem indeed. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816497 > > Title: > [snap] vaapi chromium no video hardware decoding > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions > -- Nicolás Abel Carbone Doctor en Física - Becario Posdoctoral CIFICEN-CONICET-UNCPBA https://www.researchgate.net/profile/Nicolas_Carbone *Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo indique el mail, por favor no se sienta obligado a responder este mensaje fuera de su horario de trabajo habitual.* *My working hours may not be your working hours. Unless otherwise specified in the mail, please do not feel obligated to reply outside of your normal work schedule.* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1878490] Re: Big delay between pressing the applications grid icon in dock and the start of the spring animation
Sorry for the delay. I disabled all extensions but ubuntu-dock (I need to be able to click on the grid apps icon to trigger the bug). The delay it still there. Also, it seems to happen under X11 and under Wayland. Just to be clear: the multi-second delay happens very few times, and may be related to another process eating CPU time and/or I/O. But there is almost always a perceptible delay between pressing the icon and the spring animation, specially if the animation hasn't been triggered for a while. May be around half a second or so. It is not a big deal, but it doesn't feel as smooth as it should be, hence the bug report. -- 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/1878490 Title: Big delay between pressing the applications grid icon in dock and the start of the spring animation Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am sorry if this is already reported elsewhere, I couldn't find it. Sometimes there is a big delay between clicking in the applications grid icon and the start of the spring animation. In the worst cases, this delay can be close to 2 seconds. Usually, after this first delay, subsequent clicks on the grid icon show little to no delay. I am running Ubuntu 20.04 with default extensions on a Dell XPS 13 9360. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 17:56:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (809 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1878490/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I just tried in X11. It seems to be working :) Sadly, most videos in YouTube seem to be av1 so it took me a while to get a vp9 video, but that's another issue altogether. Thanks! LIBVA_MESSAGING_LEVEL=2 snap run chromium /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) Gtk-Message: 10:43:53.358: Failed to load module "appmenu-gtk-module" Gtk-Message: 10:43:53.358: Failed to load module "appmenu-gtk-module" Gtk-Message: 10:43:53.613: Failed to load module "canberra-gtk-module" Gtk-Message: 10:43:53.638: Failed to load module "canberra-gtk-module" libva info: VA-API version 1.7.0 libva info: Trying to open /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva info: va_openDriver() returns 0 [19302:19302:0520/104355.042209:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. libva info: VA-API version 1.7.0 libva info: Trying to open /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva info: va_openDriver() returns 0 [19157:19157:0520/104355.269741:ERROR:browser_switcher_service.cc(238)] XXX Init() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
It doesn't work here. Intel i5-7200u running Ubuntu 20.04 on wayland. Maybe wayland is the issue? $ LIBVA_MESSAGING_LEVEL=2 snap run chromium /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) Gtk-Message: 10:15:51.783: Failed to load module "appmenu-gtk-module" Gtk-Message: 10:15:51.986: Failed to load module "canberra-gtk-module" Gtk-Message: 10:15:52.002: Failed to load module "canberra-gtk-module" [12405:12405:0520/101552.253222:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [12641:12641:0520/101553.290076:ERROR:vaapi_wrapper.cc(482)] vaInitialize failed: unknown libva error El mié., 20 de may. de 2020 a la(s) 09:41, Alain Rouet ( 1816...@bugs.launchpad.net) escribió: > It's working here with an Intel Core i5-7200U CPU (Intel HD 620); > "intel-gpu-top" confirms it is. Both VP9 and h264 are accelerated. CPU > usage is around 20 to 35% while playing a 1080p video on Youtube (VP9), > and a bit higher on Twitch (h264). Though it's way better than with > software decoding. > > $ LIBVA_MESSAGING_LEVEL=2 snap run chromium > Gtk-Message: 12:18:38.213: Failed to load module "canberra-gtk-module" > Gtk-Message: 12:18:38.215: Failed to load module "canberra-gtk-module" > libva info: VA-API version 1.7.0 > libva info: Trying to open > /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so > libva info: Found init function __vaDriverInit_1_7 > libva info: va_openDriver() returns 0 > [14314:14314:0520/121838.333051:ERROR:sandbox_linux.cc(374)] > InitializeSandbox() called with multiple threads in process gpu-process. > libva info: VA-API version 1.7.0 > libva info: Trying to open > /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so > libva info: Found init function __vaDriverInit_1_7 > libva info: va_openDriver() returns 0 > [14175:14175:0520/121838.439652:ERROR:browser_switcher_service.cc(238)] > XXX Init() > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816497 > > Title: > [snap] vaapi chromium no video hardware decoding > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions > -- Nicolás Abel Carbone Doctor en Física - Becario Posdoctoral CIFICEN-CONICET-UNCPBA https://www.researchgate.net/profile/Nicolas_Carbone *Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo indique el mail, por favor no se sienta obligado a responder este mensaje fuera de su horario de trabajo habitual.* *My working hours may not be your working hours. Unless otherwise specified in the mail, please do not feel obligated to reply outside of your normal work schedule.* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointV
[Desktop-packages] [Bug 1878490] Re: Big delay between pressing the applications grid icon in dock and the start of the spring animation
I am still experiencing the bug. It seems that the delay is smaller, but as it is very random is difficult to be sure. -- 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/1878490 Title: Big delay between pressing the applications grid icon in dock and the start of the spring animation Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am sorry if this is already reported elsewhere, I couldn't find it. Sometimes there is a big delay between clicking in the applications grid icon and the start of the spring animation. In the worst cases, this delay can be close to 2 seconds. Usually, after this first delay, subsequent clicks on the grid icon show little to no delay. I am running Ubuntu 20.04 with default extensions on a Dell XPS 13 9360. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 17:56:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (809 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1878490/+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 1878490] Re: Big delay between pressing the applications grid icon in dock and the start of the spring animation
Done, here is the settings.txt Oddly, while doing this I noticed that some extensions that I uninstalled long ago (even before upgrading to 20.04) where marked as active by gsettings. Pop-shell and cast-to-tv for example. I had to manually remove their entries using dconf. I will run in this configuration for a while and see if the bug is still present. ** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878490/+attachment/5372134/+files/settings.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/1878490 Title: Big delay between pressing the applications grid icon in dock and the start of the spring animation Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am sorry if this is already reported elsewhere, I couldn't find it. Sometimes there is a big delay between clicking in the applications grid icon and the start of the spring animation. In the worst cases, this delay can be close to 2 seconds. Usually, after this first delay, subsequent clicks on the grid icon show little to no delay. I am running Ubuntu 20.04 with default extensions on a Dell XPS 13 9360. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 17:56:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (809 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1878490/+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 1878490] Re: Big delay between pressing the applications grid icon in dock and the start of the spring animation
I only had gsconnect enabled (sorry, I forgot about that), all other were disabled and some uninstalled long ago (like pop-shell and cast-to-tv). I disabled gsconnect and I still have the issue. Do I need to uninstall the extensions or disabling them is enough? El jue., 14 de may. de 2020 a la(s) 00:05, Daniel van Vugt ( daniel.van.v...@canonical.com) escribió: > Please start with uninstalling these extensions: > > 'extendedgestu...@mpiannucci.github.com', > 'gsconn...@andyholmes.github.io', > 'user-th...@gnome-shell-extensions.gcampax.github.com', > 'gamem...@christian.kellner.me', > 'cast-to-tv-desktop-ad...@rafostar.github.com', > 'dark-theme-swi...@sorrow.about.alice.pm.me', > 'native-window-placement', > 'pop-sh...@system76.com', > 'places-m...@gnome-shell-extensions.gcampax.github.com' > > then reboot and tell us if the problem still occurs. We need to try > without extensions as a first step because so many bugs are caused by > extensions. > > > ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1156 >https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1156 > > ** Also affects: gnome-shell via >https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1156 >Importance: Unknown >Status: Unknown > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1878490 > > Title: > Big delay between pressing the applications grid icon in dock and the > start of the spring animation > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1878490/+subscriptions > -- Nicolás Abel Carbone Doctor en Física - Becario Posdoctoral CIFICEN-CONICET-UNCPBA https://www.researchgate.net/profile/Nicolas_Carbone *Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo indique el mail, por favor no se sienta obligado a responder este mensaje fuera de su horario de trabajo habitual.* *My working hours may not be your working hours. Unless otherwise specified in the mail, please do not feel obligated to reply outside of your normal work schedule.* -- 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/1878490 Title: Big delay between pressing the applications grid icon in dock and the start of the spring animation Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am sorry if this is already reported elsewhere, I couldn't find it. Sometimes there is a big delay between clicking in the applications grid icon and the start of the spring animation. In the worst cases, this delay can be close to 2 seconds. Usually, after this first delay, subsequent clicks on the grid icon show little to no delay. I am running Ubuntu 20.04 with default extensions on a Dell XPS 13 9360. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 17:56:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (809 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1878490/+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 1878490] [NEW] Big delay between pressing the applications grid icon in dock and the start of the spring animation
Public bug reported: I am sorry if this is already reported elsewhere, I couldn't find it. Sometimes there is a big delay between clicking in the applications grid icon and the start of the spring animation. In the worst cases, this delay can be close to 2 seconds. Usually, after this first delay, subsequent clicks on the grid icon show little to no delay. I am running Ubuntu 20.04 with default extensions on a Dell XPS 13 9360. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 17:56:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (809 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 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 -- 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/1878490 Title: Big delay between pressing the applications grid icon in dock and the start of the spring animation Status in gnome-shell package in Ubuntu: New Bug description: I am sorry if this is already reported elsewhere, I couldn't find it. Sometimes there is a big delay between clicking in the applications grid icon and the start of the spring animation. In the worst cases, this delay can be close to 2 seconds. Usually, after this first delay, subsequent clicks on the grid icon show little to no delay. I am running Ubuntu 20.04 with default extensions on a Dell XPS 13 9360. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 17:56:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (809 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 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/1878490/+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 1864307] Re: Many apps have no icon in Software on Focal
Ok, I understand. I updated from 19.10, so that explains why I have them already. El vie., 8 de may. de 2020 a la(s) 18:25, Matthias Klumpp ( matth...@tenstral.net) escribió: > On a fresh Ubuntu installation, apt-config-icons isn't installed by > default (at least it wasn't when I installed a fresh Ubuntu yesterday, > until I replaced the snap-store with the packaged gnome-software). So > new users who aren't upgrading from a previous Ubuntu version will still > have much less icons than people who get Focal by upgrading from an > older Ubuntu release. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873281). > https://bugs.launchpad.net/bugs/1864307 > > Title: > Many apps have no icon in Software on Focal > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-software/+bug/1864307/+subscriptions > -- Nicolás Abel Carbone Doctor en Física - Becario Posdoctoral CIFICEN-CONICET-UNCPBA https://www.researchgate.net/profile/Nicolas_Carbone *Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo indique el mail, por favor no se sienta obligado a responder este mensaje fuera de su horario de trabajo habitual.* *My working hours may not be your working hours. Unless otherwise specified in the mail, please do not feel obligated to reply outside of your normal work schedule.* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1864307] Re: Many apps have no icon in Software on Focal
@ximion: Sorry, I don't follow. I have both apt-config-icons and appstream installed. I do see the icons for apt apps in snap-store now with the beta version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1864307] Re: Many apps have no icon in Software on Focal
I update to the beta branch and the icons are there. Thanks! :) Is there anything in particular to test? Something I noticed in this branch (a nitpick and, I guess, completely unrelated): the window control icons (minimize, maximize, close) seems to be bolder that before and than any other app using Yaru. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1875018] [NEW] Current/selected line text is barely visible when using yaru-dark
Public bug reported: I am currently using Ubuntu 20.04 with the dark theme (yaru-dark). I have gedit configured to highlight current line. Using yaru and yaru-light this works well, but when using yaru-dark the current line is highlighted with almost white color, masking the white text which become barely visible. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:16:28 2020 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Captura de pantalla de 2020-04-25 10-15-39.png" https://bugs.launchpad.net/bugs/1875018/+attachment/5360271/+files/Captura%20de%20pantalla%20de%202020-04-25%2010-15-39.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1875018 Title: Current/selected line text is barely visible when using yaru-dark Status in gedit package in Ubuntu: New Bug description: I am currently using Ubuntu 20.04 with the dark theme (yaru-dark). I have gedit configured to highlight current line. Using yaru and yaru-light this works well, but when using yaru-dark the current line is highlighted with almost white color, masking the white text which become barely visible. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:16:28 2020 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1875018/+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 1873564] [NEW] Nautilus scrolling is stuttery in 20.04
Public bug reported: Scrolling in nautilus using the touchpad of my laptop (Dell XPS 13) is stuttery, sometimes very stuttery. Compared to scrolling in gnome- settings for example where the scrolling effect is very smooth, the difference is night and day. I don't remember to have this problem in 19.10. The extent of the issue seems a bit random. Sometimes it is a bit stuttery, sometimes it is very choppy. It is never as smooth as gnome- settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 10:46:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'248' b'org.gnome.nautilus.window-state' b'initial-size' b'(932, 931)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-02-23 (784 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873564 Title: Nautilus scrolling is stuttery in 20.04 Status in nautilus package in Ubuntu: New Bug description: Scrolling in nautilus using the touchpad of my laptop (Dell XPS 13) is stuttery, sometimes very stuttery. Compared to scrolling in gnome- settings for example where the scrolling effect is very smooth, the difference is night and day. I don't remember to have this problem in 19.10. The extent of the issue seems a bit random. Sometimes it is a bit stuttery, sometimes it is very choppy. It is never as smooth as gnome- settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 10:46:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'248' b'org.gnome.nautilus.window-state' b'initial-size' b'(932, 931)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-02-23 (784 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873564/+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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
I have 2 indicators running: insync and indicator-cpufreq. I disabled the indicator extension and it still not completely smooth, there are definitely dropped frames. It _may_ be a little better thou, it is difficult to say (is there a way to profile the framerate of the animation?). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872796/+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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Another thing I noticed. I installed Ubuntu 20.04 on another laptop, also with Intel iGPU, but lower resolution screen (1366x768) and the animations _seem_ smoother. Also this is a laptop with less software installed, so overall there are less icons to animate too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872796/+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 1872796] [NEW] gnome-shell animations are stuttery
Public bug reported: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1872796 Title: gnome-shell animations are stuttery Status in gnome-shell package in Ubuntu: New Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872796/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Can confirm it is still not working. I don't like the idea of using a ppa in software as sensitive as a browser. But also, vaapi acceleration makes a really important deference, specially in a laptop. The snap was a great solution, it is a shame it is not longer working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: Confirmed Bug description: Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1869274] Re: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash
Tested in an other PC, with Nvidia graphics (the bug report is from a Intel laptop) and brand new Ubuntu 20.04 and the bug is there too. -- 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/1869274 Title: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash Status in gnome-shell package in Ubuntu: New Bug description: Apologies for the awful title. Steps to reproduce: * Open an app * Minimize it to the tray * Enter and exit overview (Super key) Result: The minimized app will be unminimized but unresponsive. In fact it is even behind conky in my setup. Clicking on the app icon on the dash brings it to focus and restores the functionality of the app. This is a regression, it wasn't happening a couple of days ago before a series of updates to gnome-shell, mutter and gjs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 19:53:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (762 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1869274/+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 1869274] [NEW] Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash
Public bug reported: Apologies for the awful title. Steps to reproduce: * Open an app * Minimize it to the tray * Enter and exit overview (Super key) Result: The minimized app will be unminimized but unresponsive. In fact it is even behind conky in my setup. Clicking on the app icon on the dash brings it to focus and restores the functionality of the app. This is a regression, it wasn't happening a couple of days ago before a series of updates to gnome-shell, mutter and gjs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 19:53:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (762 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1869274 Title: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash Status in gnome-shell package in Ubuntu: New Bug description: Apologies for the awful title. Steps to reproduce: * Open an app * Minimize it to the tray * Enter and exit overview (Super key) Result: The minimized app will be unminimized but unresponsive. In fact it is even behind conky in my setup. Clicking on the app icon on the dash brings it to focus and restores the functionality of the app. This is a regression, it wasn't happening a couple of days ago before a series of updates to gnome-shell, mutter and gjs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 19:53:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (762 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1869274/+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 1868333] Re: Volume and screen brightness sliders are not updated on the status menu
As an additional info: this is a regression after updating to 20.04, the sliders worked fine on 19.10. -- 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/1868333 Title: Volume and screen brightness sliders are not updated on the status menu Status in gnome-shell package in Ubuntu: New Bug description: On boot, the volume and screen brightness sliders on the status menu are at their minimum value, despite both volume and screen brightness being set at a different level (as expected, the same levels they were on last shutdown). Changing volume or brightness with keyboard shortcuts change the setting, but the sliders on the status menu are no updated. The sliders are functional when modified by dragging with the mouse, but their position remains fixed despite changing the settings afterwards by keyboard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 21:34:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (756 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-01 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868333/+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 1868333] [NEW] Volume and screen brightness sliders are not updated on the status menu
Public bug reported: On boot, the volume and screen brightness sliders on the status menu are at their minimum value, despite both volume and screen brightness being set at a different level (as expected, the same levels they were on last shutdown). Changing volume or brightness with keyboard shortcuts change the setting, but the sliders on the status menu are no updated. The sliders are functional when modified by dragging with the mouse, but their position remains fixed despite changing the settings afterwards by keyboard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 21:34:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (756 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-01 (19 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - Volume and screen brightness sliders are not update on the status menu + Volume and screen brightness sliders are not updated on the status menu -- 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/1868333 Title: Volume and screen brightness sliders are not updated on the status menu Status in gnome-shell package in Ubuntu: New Bug description: On boot, the volume and screen brightness sliders on the status menu are at their minimum value, despite both volume and screen brightness being set at a different level (as expected, the same levels they were on last shutdown). Changing volume or brightness with keyboard shortcuts change the setting, but the sliders on the status menu are no updated. The sliders are functional when modified by dragging with the mouse, but their position remains fixed despite changing the settings afterwards by keyboard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 21:34:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (756 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-01 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868333/+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 1866999] Re: gnome-calendar does not sync with Google Calendar
I tried that to no avail. I don't see any event at all on gnome-calendar despite having many in my google account. I also tried logout and then login on Online Accounts in gnome-settings, but calendar is still empty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: New Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+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 1866999] [NEW] gnome-calendar does not sync with Google Calendar
Public bug reported: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) ** Affects: gnome-calendar (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 gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: New Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+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 1865385] Re: eog doesn't appear as an option when opening images in "open with..."
Sorry, I meant to update the bug and keep forgetting. After some update at the beginning of the week (possible gnome-shell 3.34 -> 3.35.92?) eog appears as an option in the menu. Still not the default, thou. ** Summary changed: - eog doesn't appear as an option when opening images in "open with..." + eog is not the default option to open images (jpg, png, svg) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1865385 Title: eog is not the default option to open images (jpg, png, svg) Status in eog package in Ubuntu: Incomplete Bug description: After updating to focal dev, when opening a jpg or png file, it is opened by Gimp instead of eog as it was in eoan. Also, eog doesn't even appear as an option in the "open with..." menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 18:42:07 2020 InstallationDate: Installed on 2018-02-23 (736 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: eog UpgradeStatus: Upgraded to focal on 2020-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1865385/+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 1865385] [NEW] eog doesn't appear as an option when opening images in "open with..."
Public bug reported: After updating to focal dev, when opening a jpg or png file, it is opened by Gimp instead of eog as it was in eoan. Also, eog doesn't even appear as an option in the "open with..." menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 18:42:07 2020 InstallationDate: Installed on 2018-02-23 (736 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: eog UpgradeStatus: Upgraded to focal on 2020-03-01 (0 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - eog doesn't as an option when opening images in "open with..." + eog doesn't appear as an option when opening images in "open with..." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1865385 Title: eog doesn't appear as an option when opening images in "open with..." Status in eog package in Ubuntu: New Bug description: After updating to focal dev, when opening a jpg or png file, it is opened by Gimp instead of eog as it was in eoan. Also, eog doesn't even appear as an option in the "open with..." menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 18:42:07 2020 InstallationDate: Installed on 2018-02-23 (736 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: eog UpgradeStatus: Upgraded to focal on 2020-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1865385/+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 1822356] [NEW] [Ubuntu 19.04] New open windows don't gain focus automatically
Public bug reported: After updating to Ubuntu 19.04 I noticed a papercut: new open windows don't have the focus. For example, if I opened the terminal from the dock in 18.10, I could start writing immediately after it open. In 19.04, I have to click on the terminal window before writing because the focus is elsewhere. It doesn't seem to happen always, but often enough to be annoying and certainly a regression from 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 15:04:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1822356 Title: [Ubuntu 19.04] New open windows don't gain focus automatically Status in gnome-shell package in Ubuntu: New Bug description: After updating to Ubuntu 19.04 I noticed a papercut: new open windows don't have the focus. For example, if I opened the terminal from the dock in 18.10, I could start writing immediately after it open. In 19.04, I have to click on the terminal window before writing because the focus is elsewhere. It doesn't seem to happen always, but often enough to be annoying and certainly a regression from 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 15:04:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822356/+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 1822351] Re: Nautilus does not open after updating to 19.04
Update: Enabling and disabling the search and notification permissions on Settings->Applications->Nautilus solved the problem. I will leave the bug report open as I think there is still a bug involved (maybe related to tracker?). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: New Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+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 1822351] [NEW] Nautilus does not open after updating to 19.04
Public bug reported: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1822351 Title: Nautilus does not open after updating to 19.04 Status in nautilus package in Ubuntu: New Bug description: After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens. I don't really know how to report this bug without any terminal output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:58:12 2019 InstallationDate: Installed on 2018-02-23 (398 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+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 1697373] Re: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland
Still happpening in Ubuntu 18.04. Maybe not that important now that wayland is not the de default session, but nonetheless worth of fixing I think -- 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/1697373 Title: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland Status in xorg-server package in Ubuntu: Triaged Bug description: gnome-shell / gdm / wayland Test Case: 1. Launch netflix in chrome 2. Play a video 3. Wait until the display times out. Expected result The screen does not dim Actual result The display goes black. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 12 09:21:46 2017 DisplayManager: gdm3 InstallationDate: Installed on 2013-09-03 (1377 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1697373/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
Fixed for me. Thank you for your hard work!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Fix Released Status in mesa-demos package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) 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/libglvnd/+bug/1751414/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
I just got the whole mesa stack updated, including libgl1-mesa-glx (ver 18.0.0~rc4-1ubuntu3) and I still don't have gl acceleration, only llvm pipe. Are there any other packages on hold? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) 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/libglvnd/+bug/1751414/+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 1731484] Re: Gnome-shell crashes when trying to display a notification
Sorry for the delay. I'll try to submit the bug upstream. About apport, it just crashes. No error visible on the console. I'll check about the mconnect extension. I'll disable it and see if the crashes continue. El lun., 13 de nov. de 2017 a la(s) 07:01, Sebastien Bacher < seb...@ubuntu.com> escribió: > what apport issue do you get when trying to submit it? > > the journal log also has errors about mconn...@andyholmes.github.io ... > do you get the issue if you disable the "connect" extension? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1731484 > > Title: > Gnome-shell crashes when trying to display a notification > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731484/+subscriptions > -- Nicolás Abel Carbone nicocarb...@gmail.com ncarb...@exa.unicen.edu.ar -- 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/1731484 Title: Gnome-shell crashes when trying to display a notification Status in gnome-shell package in Ubuntu: New Bug description: Gnome-shell crashes often (but not always) when trying to display a notification. I have seen this behavior particularly when Spotify emits a notification for example when starting playback of a playlist or changing songs. The shell recovers itself and no other problems are evident afterwards, but it is very annoying. It seems that once the crash happens it will not repeat until another session is started (after restarting the PC, for example). But it doesn't always happens on the first notification emmited on the session. I manually attach the crash dump, because ubuntu-bug and apport-cli both crashes when trying to submit this bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 10 10:57:49 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (105 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1731484/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
Alright, done. It is bug #1731484. Neither ubuntu-bug nor apport-cli worked, but crashed when trying to submit the .crash file. So, I attached it manually. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Artful: Confirmed Status in gnome-shell source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1731484] [NEW] Gnome-shell crashes when trying to display a notification
Public bug reported: Gnome-shell crashes often (but not always) when trying to display a notification. I have seen this behavior particularly when Spotify emits a notification for example when starting playback of a playlist or changing songs. The shell recovers itself and no other problems are evident afterwards, but it is very annoying. It seems that once the crash happens it will not repeat until another session is started (after restarting the PC, for example). But it doesn't always happens on the first notification emmited on the session. I manually attach the crash dump, because ubuntu-bug and apport-cli both crashes when trying to submit this bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 10 10:57:49 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (105 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages ** Attachment added: "Crash dump" https://bugs.launchpad.net/bugs/1731484/+attachment/5006959/+files/_usr_bin_gnome-shell.120.crash -- 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/1731484 Title: Gnome-shell crashes when trying to display a notification Status in gnome-shell package in Ubuntu: New Bug description: Gnome-shell crashes often (but not always) when trying to display a notification. I have seen this behavior particularly when Spotify emits a notification for example when starting playback of a playlist or changing songs. The shell recovers itself and no other problems are evident afterwards, but it is very annoying. It seems that once the crash happens it will not repeat until another session is started (after restarting the PC, for example). But it doesn't always happens on the first notification emmited on the session. I manually attach the crash dump, because ubuntu-bug and apport-cli both crashes when trying to submit this bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 10 10:57:49 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (105 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1731484/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost
Ok, Daniel, I understand. Should I file a specific bug about the notification-related crash? There are a lot of bug reports with gnome-shell crashes and some of them are probably related to the notifications, but i don't know how to figure out which one is the one I am having. El jue., 9 de nov. de 2017 a la(s) 06:55, Rachel Greenham < 1505...@bugs.launchpad.net> escribió: > It failed to hold true on day 2 anyway, as today the session didn't > survive the overnight sleep. But in any case I re-checked the bug of > mine that was marked a duplicate of this one, and saw as it was during > one of my brief try-outs with wayland, is irrelevant to my current > gnome-session woes, as I'm back on xorg. I had thought this just one of > the family of gnome-shell crashers that was affecting both xorg and > wayland, but seemingly only with displayport monitors. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1711383). > https://bugs.launchpad.net/bugs/1505409 > > Title: > gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from > _XEventsQueued() from XPending() from gdk_check_xpending() > ["Connection to xwayland lost"] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions > -- Nicolás Abel Carbone nicocarb...@gmail.com ncarb...@exa.unicen.edu.ar -- 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/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Artful: Confirmed Status in gnome-shell source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost
Another follow up about this bug: after some more crashes I am realizing that they seem to happen when a notification tries to pop up, like when starting to play a playlist on Spotify or changing the song. Gnome-shell crashes and the notification pop up never appears. Subsequent notifications do work. El mié., 1 de nov. de 2017 a la(s) 11:05, Nicolás Abel Carbone < nicocarb...@gmail.com> escribió: > Follow up form my previous comment: note that the crash only happens in > the first interaction after opening Spotify, further actions doesn't > trigger the crash again. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1720784). > https://bugs.launchpad.net/bugs/1505409 > > Title: > gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from > _XEventsQueued() from XPending() from gdk_check_xpending() > ["Connection to xwayland lost"] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions > -- Nicolás Abel Carbone nicocarb...@gmail.com ncarb...@exa.unicen.edu.ar -- 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/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Artful: Confirmed Status in gnome-shell source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
Follow up form my previous comment: note that the crash only happens in the first interaction after opening Spotify, further actions doesn't trigger the crash again. -- 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/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Artful: Confirmed Status in gnome-shell source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
I think I have found I way to reproduce the crash of gnome-shell, at least in my PC. Almost always opening up Spotify and double-clicking on a playlist so it shuffle-plays results in gnome-shell crashing and recovering a couple of seconds later. -- 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/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Artful: Confirmed Status in gnome-shell source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1710882] Re: Window tiling is not working in gnome-shell under ubuntu session
Nop. It seems to be working fine in the last versions. Sorry I didn't mark this as solved. On Thu, Oct 26, 2017, 11:36 Sebastien Bacher <seb...@ubuntu.com> wrote: > is that still an issue with the current versions? > > ** Changed in: gnome-shell (Ubuntu) >Importance: Undecided => Low > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1710882 > > Title: > Window tiling is not working in gnome-shell under ubuntu session > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1710882/+subscriptions > -- Nicolás Abel Carbone nicocarb...@gmail.com ncarb...@exa.unicen.edu.ar -- 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/1710882 Title: Window tiling is not working in gnome-shell under ubuntu session Status in gnome-shell package in Ubuntu: Incomplete Bug description: After updates on August 14th to ubuntu-session and related packages, window snapping (moving the application window to the edges of the screen to half-maximize or maximize) seems to be deactivated. I tried "gsettings set org.gnome.shell.overrides edge-tiling true" to no avail. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 15 10:49:14 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (18 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1710882/+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 1718443] Re: Nautilus becomes unresponsive for several seconds when cutting or copying a file
I found the culprit: kdeconnect. As suggested here: https://askubuntu.com/questions/897358/nautilus-freezes-on-copy-action-not-during-transfer changing the name of kdeconnect-cli in /usr/bin works as a workaround. ** Also affects: kdeconnect (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1718443 Title: Nautilus becomes unresponsive for several seconds when cutting or copying a file Status in kdeconnect package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: When cutting coping a file (by selecting it and clicking "Cut" or "Copy" on the context menu or by using the Ctrl+X or CTRL+C shortcut) nautilus becomes unresponsive for several seconds. I cannot even move the nautilus window. There doesn't seem to be any spike in CPU usage. After 2 to 4 seconds, nautilus becomes responsive again, with no error message and the operation can be completed by pasting the file in the destination without more issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 11:24:16 2017 InstallationDate: Installed on 2017-07-27 (54 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1718443/+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 1718443] [NEW] Nautilus becomes unresponsive for several seconds when cutting or copying a file
Public bug reported: When cutting coping a file (by selecting it and clicking "Cut" or "Copy" on the context menu or by using the Ctrl+X or CTRL+C shortcut) nautilus becomes unresponsive for several seconds. I cannot even move the nautilus window. There doesn't seem to be any spike in CPU usage. After 2 to 4 seconds, nautilus becomes responsive again, with no error message and the operation can be completed by pasting the file in the destination without more issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 11:24:16 2017 InstallationDate: Installed on 2017-07-27 (54 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Summary changed: - Nautilus becomes unresponsive for several seconds when cutting a file + Nautilus becomes unresponsive for several seconds when cutting or copying a file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1718443 Title: Nautilus becomes unresponsive for several seconds when cutting or copying a file Status in nautilus package in Ubuntu: New Bug description: When cutting coping a file (by selecting it and clicking "Cut" or "Copy" on the context menu or by using the Ctrl+X or CTRL+C shortcut) nautilus becomes unresponsive for several seconds. I cannot even move the nautilus window. There doesn't seem to be any spike in CPU usage. After 2 to 4 seconds, nautilus becomes responsive again, with no error message and the operation can be completed by pasting the file in the destination without more issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 11:24:16 2017 InstallationDate: Installed on 2017-07-27 (54 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1718443/+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 1717923] Re: Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop"
Thank you Jeremy! That did the trick! It seems it is that same bug. Should I mark this bug report as duplicated of some other? -- 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/1717923 Title: Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop" Status in gnome-shell package in Ubuntu: New Bug description: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1717923/+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 1717923] Re: Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop"
This is on real hardware. I am using an hybrid Intel Ironlake Mobile / AMD Redwood notebook. It should boot using the Intel GPU. I have a old crash report in var/crash. I think it is from before the update from 3.25.91 to 3.26.0, I attach it here. ** Attachment added: "gnome-shell crash dump" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717923/+attachment/4952207/+files/_usr_bin_gnome-shell.120.crash -- 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/1717923 Title: Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop" Status in gnome-shell package in Ubuntu: New Bug description: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1717923/+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 1717923] Re: Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop"
Just to be clear: the previous is an old (from last wednesday) crash that happened when trying to enter the wayland session. In that time, after I logged on xorg, a crash report appeared. Since then, in all my last tries, wayland session login failed silently, without a crash report. -- 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/1717923 Title: Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop" Status in gnome-shell package in Ubuntu: New Bug description: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1717923/+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 1717923] [NEW] Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop"
Public bug reported: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Full logs" https://bugs.launchpad.net/bugs/1717923/+attachment/4952137/+files/log%20messages -- 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/1717923 Title: Cannot login to wayland session after update to 3.25.91 - Log error: "Unrecoverable failure in required component org.gnome.Shell.desktop" Status in gnome-shell package in Ubuntu: New Bug description: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1717923/+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 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()
I still cannot login to ubuntu session using wayland. I have mutter 3.26.0-1. Is there a missing piece in the bug or should I report a new bug? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714330 Title: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent() Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99 --- Gnome shell crashes when trying to log in to the wayland ubuntu session. It works fine on Xorg. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Aug 31 11:39:23 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-27 (35 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax PC (0x7fdee0bf9296) ok source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2 meta_monitor_manager_kms_wait_for_flip () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714330/+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 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()
I am still having this bug even after updating mutter to the aforementioned version. A update to gnome-shell is also needed? -- 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/1714330 Title: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent() Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Bug description: Gnome shell crashes when trying to log in to the wayland ubuntu session. It works fine on Xorg. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Aug 31 11:39:23 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-27 (35 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax PC (0x7fdee0bf9296) ok source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2 meta_monitor_manager_kms_wait_for_flip () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714330/+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 1711388] Re: ubuntu-session fails to login after last updates
I found the issue. It was mainly me, but i think something is still missing. As I was updating from early ubuntu GNOME, the ubuntu-desktop metapackage wasn't installed, causing the ubuntu session to silently fail. I think that ubuntu-session should depend on ubuntu-desktop. ** Summary changed: - ubuntu-session fails to login after last updates + ubuntu-session should depend on ubuntu-desktop metapackage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1711388 Title: ubuntu-session should depend on ubuntu-desktop metapackage Status in gnome-session package in Ubuntu: New Bug description: After the updates of August 16th or 17th, I cannot login to the ubuntu session. After entering my credentials, it goes right back to gdm, without any error message. GNOME session works fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu20 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 17 12:07:05 2017 InstallationDate: Installed on 2017-07-27 (21 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1711388/+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 1711388] Re: ubuntu-session fails to login after last updates
Added gdm log ** Attachment added: "gdm log file" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1711388/+attachment/4934380/+files/gdmlog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1711388 Title: ubuntu-session fails to login after last updates Status in gnome-session package in Ubuntu: New Bug description: After the updates of August 16th or 17th, I cannot login to the ubuntu session. After entering my credentials, it goes right back to gdm, without any error message. GNOME session works fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu20 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 17 12:07:05 2017 InstallationDate: Installed on 2017-07-27 (21 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1711388/+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 1711388] [NEW] ubuntu-session fails to login after last updates
Public bug reported: After the updates of August 16th or 17th, I cannot login to the ubuntu session. After entering my credentials, it goes right back to gdm, without any error message. GNOME session works fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu20 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 17 12:07:05 2017 InstallationDate: Installed on 2017-07-27 (21 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1711388 Title: ubuntu-session fails to login after last updates Status in gnome-session package in Ubuntu: New Bug description: After the updates of August 16th or 17th, I cannot login to the ubuntu session. After entering my credentials, it goes right back to gdm, without any error message. GNOME session works fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu20 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 17 12:07:05 2017 InstallationDate: Installed on 2017-07-27 (21 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1711388/+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 1672491] Re: New NetworkManager breaks VPN DNS.
*** This bug is a duplicate of bug 1671606 *** https://bugs.launchpad.net/bugs/1671606 ** This bug has been marked a duplicate of bug 1671606 DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 -- 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/1672491 Title: New NetworkManager breaks VPN DNS. Status in network-manager package in Ubuntu: Confirmed Bug description: Alright, this is going to be a frustrating bug for everyone involved I expect, but here goes. On Ubuntu 16.04, using a non-released VPN client (making this _much_ harder for anyone to reproduce), upgrading the network-manager packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubuntu0.16.04.1 quite handily broke DNS over the VPN. And it broke it really oddly. dnsmasq binds to socket 12 for the new interface, just fine. strace shows that it does the sendto for the DNS request, and that the poll calls are working, just fine. tcpdump shows the response messages, they are coming back from the correct host and port, going to my IP and the port that dnsmasq is sending from. There are no iptables rules involved, nothing is set to deny. dnsmasq is never getting the response packet. The request thus times out. Doing a host or dig directly to the DNS server works just fine. And this is completely reproducible, and goes away the moment I downgrade back to 1.2.2-0ubuntu0.16.04.3. Was there some change to how network-manager handles VPN interfaces/tap0 in the new version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1672491/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
This bug has been fixed a while ago. No need to do any workaround. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Released Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1351916/+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 1591736] Re: Pulseaudio fails to detect card, but shows up in alsa [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal, Headphones]
Hey i figured out it was muroard taking over /dev/snd/*, i think it has a wrong default configuration, maybe i installer it from a --install- suggests some days ago over vlc or something. Im going to check if i can fix it, for the sake of ocd ;) -- 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/1591736 Title: Pulseaudio fails to detect card, but shows up in alsa [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal, Headphones] Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio fails to detect card, only shows "dummy output", anyway alsa recognizes it well. I tried restarting pulseaudio with sudo killall pulseaudio pulseaudio -k and it works, but its annoing to type this command every time i restart the computer, i need a real solution. I thought the problem was in a conflicting starting app, but i have only two cloud clients that never before give me this problem (dropox and mega), and the pulseaudio log didnt give me any useful info, so i dont know what to do now, please help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Jun 12 13:49:22 2016 InstallationDate: Installed on 2016-05-31 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.77 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A1 dmi.board.vendor: HP dmi.board.version: 91.1C dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1C:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2016-06-11T22:26:14.604222 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1591736/+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 1591736] Re: Pulseaudio fails to detect card, but shows up in alsa [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal, Headphones]
Here you have the alsa information script output: http://www.alsa-project.org/db/?f=1b1c830e80ca01fe3ccdb7ff42650c9e92ae9245 -- 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/1591736 Title: Pulseaudio fails to detect card, but shows up in alsa [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal, Headphones] Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio fails to detect card, only shows "dummy output", anyway alsa recognizes it well. I tried restarting pulseaudio with sudo killall pulseaudio pulseaudio -k and it works, but its annoing to type this command every time i restart the computer, i need a real solution. I thought the problem was in a conflicting starting app, but i have only two cloud clients that never before give me this problem (dropox and mega), and the pulseaudio log didnt give me any useful info, so i dont know what to do now, please help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Jun 12 13:49:22 2016 InstallationDate: Installed on 2016-05-31 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.77 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A1 dmi.board.vendor: HP dmi.board.version: 91.1C dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1C:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2016-06-11T22:26:14.604222 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1591736/+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 1591736] [NEW] Pulseaudio fails to detect card, but shows up in alsa [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal, Headphones]
Public bug reported: Pulseaudio fails to detect card, only shows "dummy output", anyway alsa recognizes it well. I tried restarting pulseaudio with sudo killall pulseaudio pulseaudio -k and it works, but its annoing to type this command every time i restart the computer, i need a real solution. I thought the problem was in a conflicting starting app, but i have only two cloud clients that never before give me this problem (dropox and mega), and the pulseaudio log didnt give me any useful info, so i dont know what to do now, please help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Jun 12 13:49:22 2016 InstallationDate: Installed on 2016-05-31 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.77 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A1 dmi.board.vendor: HP dmi.board.version: 91.1C dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1C:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2016-06-11T22:26:14.604222 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1591736 Title: Pulseaudio fails to detect card, but shows up in alsa [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal, Headphones] Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio fails to detect card, only shows "dummy output", anyway alsa recognizes it well. I tried restarting pulseaudio with sudo killall pulseaudio pulseaudio -k and it works, but its annoing to type this command every time i restart the computer, i need a real solution. I thought the problem was in a conflicting starting app, but i have only two cloud clients that never before give me this problem (dropox and mega), and the pulseaudio log didnt give me any useful info, so i dont know what to do now, please help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Jun 12 13:49:22 2016 InstallationDate: Installed on 2016-05-31 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP Pavilion Notebook, Realtek ALC3241, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.77 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A1 dmi.board.vendor: HP dmi.board.version: 91.1C dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1C:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2016-06-11T22:26:14.604222 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
Yaay! i found a workaround! It seems that the mic isn't correctly detected. What i did was: sudo echo options snd-hda-intel model=dell-headset-multi /etc/modprobe.d/snd-hda-intel.conf and the mic started to work after a reboot. if it didn't work for you, you may try replacing dell-headset-multi with headset-mic , alc271-dmic or any other mic model from https://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio-Models.txt that is assigned to your audio card. -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
Are there any news about this bug? I'm using another distro (elementaryOS) right now and it has the same problem too. I'd say there's a missing driver in the kernel but i'm not an expert... -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1400470] [NEW] cannot download photos using shotwell via usb
Public bug reported: I get error message Unable to fetch previews from the camera: Could not claim the USB device (-53) when I try to connect my camera and download photos to the PC using Shotwell. I have also installed gThumb and still same message. ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb Status in shotwell package in Ubuntu: New Bug description: I get error message Unable to fetch previews from the camera: Could not claim the USB device (-53) when I try to connect my camera and download photos to the PC using Shotwell. I have also installed gThumb and still same message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+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 1354067] Re: Auto-Login service for GMail accounts gives Applications can no longer access online account error
Yes, the problem persists. :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1354067 Title: Auto-Login service for GMail accounts gives Applications can no longer access online account error Status in “account-plugins” package in Ubuntu: Confirmed Status in “friends” package in Ubuntu: Invalid Bug description: The auto-login service for GMail accounts gives Applications can no longer access online accounts error everytime it attempts to connect. It also cannot sustain connections for other online services (facebook, yahoo, etc.) and requires me to grant access to the services again and again. I can confirm my passwords are correct. Also, granting access to yahoo mail and facebook works flawlessly, but the GMail 'Grant Access' interface is buggy, and just doesn't work. On entering password and clicking 'Done' it brings back the same screen, as though nothing happened. Over and over again. If you click cancel a few times, it brings you back to the screen with the list of online accounts, while it attempts to connect to the services, in vain. Also, overall the friends service is buggy. It doesn't show me notifications from facebook, nor has it synced events from my google calenders. I cannot tell you when this problem started exactly, neither can i guess what might have caused the problem. If you need some log files, please tell me, i'll upload them asap. I don't have accounts in many of the services listed there, so i might not be able to help you with other services. I really hope there's a solution to this, because its always lovely to see a well polished desktop environment :) I use Ubuntu 14.04 LTS (Trusty Tahr) Version of 'friends' package installed: 0.2.0+14.04.20140217.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: friends-dispatcher 0.2.0+14.04.20140217.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 7 20:47:49 2014 InstallationDate: Installed on 2014-04-20 (108 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: friends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1354067/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
What can I do? Kailang Yang doesn't answer. I've sent 2 mails but he never answers. -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
Kailang doesn't seem to answer... -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
My ALSA info is here http://www.alsa-project.org/db/?f=8f113eebb5c00c5dba5394d088ee4bc9d623afd4 I've sent a mail to Kailang Yang. Still waiting for an answer. I don't know if the fix you say is related to my driver but Takashi Iwai told me that he did a fix and it was included in that kernel version. -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
And i forgot to say that in the sound input window it appears 2 devices (microphone and analog input) but both of them are the same integrated microphone and still the same when i plug in a headset with mic or whatever i do. (This thing have happened since the first day). -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
Some news, i asked Takashi Iwai. He added something to 3.17-rc2 kernel (which is in mainline now). I've downloaded and installed it but my problem continues. What i do now? -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
I asked again Acer Support Team, now they say they can't give me such coefficients. I asked if they know somebody who could give me the coefficients but the anwer was again no. I dont know what to do now, there isn't any way to obtain such information. -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
Acer told me that they dont support linux now... What i should do then? -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
I tried to contact with them in two ways. The first one, posting my problem in Acer Community but it seems that they are so busy to answer. I also tried talking with somebody from Acer using a chat they have but they just solve easy problems like unmute mic, reinstall driver and some basic things. When i asked for more they just say they dont have linux support. There is any other way to know that coefficients? -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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
