[Desktop-packages] [Bug 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
I've prepared a patch like suggested by @pjb1008 but I wasn't able to build a package with this patch. EDIT: But I can confirm that adding the option "--socket" to the luatex command fixes the issue. ** Attachment added: "fix_for_lua-socket_2058409" https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/2058409/+attachment/5761573/+files/fix_for_lua-socket_2058409 ** Package changed: texlive-base (Ubuntu) => context (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2058409 Title: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found Status in context package in Ubuntu: Confirmed Bug description: Before 3 weeks at least it was possible to install texlive-full without any issues. Now this is not possible anymore. So the bug was probably introduced with one of the latest updates. How to reproduce: Install package texlive-full $ apt install texlive-full Install hangs: texlive-lang-japanese (2021.20220204-1) wird eingerichtet ... context (2021.03.05.20220211-1) wird eingerichtet ... Running mtxrun --generate. This may take some time... done. Pregenerating ConTeXt MarkIV format. This may take some time... Related running processes: root 18747 0.4 0.0 13936 7456 pts/2Ss+ 17:47 0:01 /usr/bin/dpkg --status-fd 43 --configure --pending root 20584 0.0 0.0 2892 960 pts/2S+ 17:48 0:00 /bin/sh /var/lib/dpkg/info/context.postinst configure root 20592 0.0 0.0 2892 1064 pts/2S+ 17:48 0:00 /bin/sh /usr/bin/luatools --make cont-en root 20593 0.1 0.9 92868 79952 pts/2S+ 17:48 0:00 texlua /usr/bin/mtxrun --script base --make cont-en root 20596 0.0 0.0 2892 1004 pts/2S+ 17:48 0:00 sh -c /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv root 20597 0.0 0.3 40816 28684 pts/2S+ 17:48 0:00 /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv Run luatex manually: # /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian) (INITEX) system commands enabled. (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv (/usr/share/texmf/tex/context/base/mkiv/context.mkiv (/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) (/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) (/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua Macros / Basic Lua Libraries<+ /usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua Macros / Libraries<+ /usr/share/texmf/tex/context/base/mkiv/util-str.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tab.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fil.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sac.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sto.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-pck.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-prs.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fmt.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-dim.lua><+ /usr/share/texmf/tex/context/base/mkiv/trac-set.lua><+
[Desktop-packages] [Bug 2058831] [NEW] package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2054716 *** https://bugs.launchpad.net/bugs/2054716 Public bug reported: Errors were encountered while processing: polkitd colord update-manager pkexec gamemode-daemon fprintd gnome-initial-setup gdm3 packagekit update-notifier modemmanager gamemode libgamemode0:amd64 policykit-1 libpam-fprintd:amd64 ubuntu-desktop packagekit-tools rtkit gnome-control-center aptdaemon python3-aptdaemon ubuntu-desktop-minimal network-manager software-properties-common network-manager-pptp brltty gstreamer1.0-packagekit network-manager-pptp-gnome python3-aptdaemon.gtk3widgets network-manager-openvpn apturl language-selector-gnome network-manager-gnome software-properties-gtk network-manager-config-connectivity-ubuntu network-manager-openvpn-gnome Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Mar 24 00:32:06 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-03-23 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-03-24 (0 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2058831 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: Errors were encountered while processing: polkitd colord update-manager pkexec gamemode-daemon fprintd gnome-initial-setup gdm3 packagekit update-notifier modemmanager gamemode libgamemode0:amd64 policykit-1 libpam-fprintd:amd64 ubuntu-desktop packagekit-tools rtkit gnome-control-center aptdaemon python3-aptdaemon ubuntu-desktop-minimal network-manager software-properties-common network-manager-pptp brltty gstreamer1.0-packagekit network-manager-pptp-gnome python3-aptdaemon.gtk3widgets network-manager-openvpn apturl language-selector-gnome network-manager-gnome software-properties-gtk network-manager-config-connectivity-ubuntu network-manager-openvpn-gnome Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Mar 24 00:32:06 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-03-23 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-03-24 (0 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2058831/+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 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
This worked at least until 13th of March -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2058409 Title: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found Status in texlive-base package in Ubuntu: New Bug description: Before 3 weeks at least it was possible to install texlive-full without any issues. Now this is not possible anymore. So the bug was probably introduced with one of the latest updates. How to reproduce: Install package texlive-full $ apt install texlive-full Install hangs: texlive-lang-japanese (2021.20220204-1) wird eingerichtet ... context (2021.03.05.20220211-1) wird eingerichtet ... Running mtxrun --generate. This may take some time... done. Pregenerating ConTeXt MarkIV format. This may take some time... Related running processes: root 18747 0.4 0.0 13936 7456 pts/2Ss+ 17:47 0:01 /usr/bin/dpkg --status-fd 43 --configure --pending root 20584 0.0 0.0 2892 960 pts/2S+ 17:48 0:00 /bin/sh /var/lib/dpkg/info/context.postinst configure root 20592 0.0 0.0 2892 1064 pts/2S+ 17:48 0:00 /bin/sh /usr/bin/luatools --make cont-en root 20593 0.1 0.9 92868 79952 pts/2S+ 17:48 0:00 texlua /usr/bin/mtxrun --script base --make cont-en root 20596 0.0 0.0 2892 1004 pts/2S+ 17:48 0:00 sh -c /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv root 20597 0.0 0.3 40816 28684 pts/2S+ 17:48 0:00 /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv Run luatex manually: # /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian) (INITEX) system commands enabled. (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv (/usr/share/texmf/tex/context/base/mkiv/context.mkiv (/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) (/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) (/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua Macros / Basic Lua Libraries<+ /usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua Macros / Libraries<+ /usr/share/texmf/tex/context/base/mkiv/util-str.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tab.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fil.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sac.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sto.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-pck.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-prs.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fmt.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-dim.lua><+ /usr/share/texmf/tex/context/base/mkiv/trac-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/luat-log.lua><+ /usr/share/texmf/tex/context/base/mkiv/trac-inf.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-deb.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tpl.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-seq.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sta.lua><+
[Desktop-packages] [Bug 2058409] [NEW] Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
Public bug reported: Before 3 weeks at least it was possible to install texlive-full without any issues. Now this is not possible anymore. So the bug was probably introduced with one of the latest updates. How to reproduce: Install package texlive-full $ apt install texlive-full Install hangs: texlive-lang-japanese (2021.20220204-1) wird eingerichtet ... context (2021.03.05.20220211-1) wird eingerichtet ... Running mtxrun --generate. This may take some time... done. Pregenerating ConTeXt MarkIV format. This may take some time... Related running processes: root 18747 0.4 0.0 13936 7456 pts/2Ss+ 17:47 0:01 /usr/bin/dpkg --status-fd 43 --configure --pending root 20584 0.0 0.0 2892 960 pts/2S+ 17:48 0:00 /bin/sh /var/lib/dpkg/info/context.postinst configure root 20592 0.0 0.0 2892 1064 pts/2S+ 17:48 0:00 /bin/sh /usr/bin/luatools --make cont-en root 20593 0.1 0.9 92868 79952 pts/2S+ 17:48 0:00 texlua /usr/bin/mtxrun --script base --make cont-en root 20596 0.0 0.0 2892 1004 pts/2S+ 17:48 0:00 sh -c /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv root 20597 0.0 0.3 40816 28684 pts/2S+ 17:48 0:00 /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv Run luatex manually: # /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian) (INITEX) system commands enabled. (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv (/usr/share/texmf/tex/context/base/mkiv/context.mkiv (/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) (/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) (/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua Macros / Basic Lua Libraries<+ /usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua Macros / Libraries<+ /usr/share/texmf/tex/context/base/mkiv/util-str.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tab.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fil.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sac.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sto.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-pck.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-prs.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fmt.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-dim.lua><+ /usr/share/texmf/tex/context/base/mkiv/trac-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/luat-log.lua><+ /usr/share/texmf/tex/context/base/mkiv/trac-inf.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-deb.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tpl.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-seq.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sta.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sbx.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-soc-imp-reset.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-soc-imp-socket.lua>/usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found: no field package.preload['socket.core'] no file '/usr/local/share/lua/5.3/socket/core.lua' no file
[Desktop-packages] [Bug 1930769] Re: When enabled, Firefox AppArmor profile prevents U2F devices from working
I was also affected by this bug (on Ubuntu 22.04.2 LTS with the latest
Firefox 112.0.1 from ppa:mozillateam). I don't want to use the snap
version of Firefox.
After digging around in AppArmor audit mode and inspecting the logs I noticed
that torbrowser (also based on Firefox) has a set of rule in its profile that
seem to resolve the issue:
/etc/apparmor.d/usr.bin.firefox
```
# u2f (tested with Yubikey 4)
/sys/class/ r,
/sys/bus/ r,
/sys/class/hidraw/ r,
/run/udev/data/c24{7,9}:* r,
/dev/hidraw* rw,
# Yubikey NEO also needs this:
/sys/devices/**/hidraw/hidraw*/uevent r,
```
(I am not sure to what extend other tokens need different rules.)
--
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/1930769
Title:
When enabled, Firefox AppArmor profile prevents U2F devices from
working
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Summary:
If you enable the apparmor profile that comes in Ubuntu's Firefox
package, it prevents USB U2F tokens from being used.
To reproduce:
1. Obtain a USB FIDO/U2F token - such as a Yubikey; and a clean
install of Ubuntu 20.04 with Firefox installed, but the AppArmor
profile for firefox disabled (As is the default).
2. Confirm the correct function of your U2F token - such as at
https://demo.yubico.com/webauthn-technical
3. Enable the AppArmor profile with the following command, then
restart firefox.
sudo aa-enforce /etc/apparmor.d/usr.bin.firefox
4. Repeat your test of your U2F token. You will find Firefox is unable
to access your U2F token. Any accounts you need U2F to log into are
now inaccessible.
5. Disabling the apparmor profile and restarting firefox will make U2F
work again.
To work around:
Edit /etc/apparmor.d/usr.bin.firefox and replace these lines:
# Doesn't seem to be required, but noisy. Maybe allow 'r' for 'b*' if
needed.
# Possibly move to an abstraction if anything else needs it.
deny /run/udev/data/** r,
Instead allowing access to udev data, and to hidraw devices:
/run/udev/data/** r,
/dev/hidraw[0-9] rw,
I haven't checked the security implications of this change; some might
feel it grants overly broad access. Chromium, which in 20.04 is
delivered as a snap, includes udev rules (70-snap.chromium.rules)
which I suspect grant access in a device-id-whitelisted way.
This is me resubmitting #1930768 this time with all the info attached.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 88.0.1+build1-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mtandy 1757 F pulseaudio
/dev/snd/controlC1: mtandy 1757 F pulseaudio
BuildID: 20210504152106
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 3 23:34:55 2021
ForcedLayersAccel: False
IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2021-05-31 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
IpRoute:
default via 192.168.0.1 dev enp3s0 proto dhcp metric 100
169.254.0.0/16 dev enp3s0 scope link metric 1000
192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.2 metric 100
MostRecentCrashID: bp-4122b123-9c74-4baf-b817-c8a771171216
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:352
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=88.0.1/20210504152106 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2202
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/11/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2021-06-03T23:25:44.143815
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
Yes, this is a very required feature. When working with (or presenting to) external displays, it is necessary to: - see time - have access to calendar - Some apps are missing top bars. Very appreciated. -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
Verified Oracle image build by building Jammy image using livecd-rootfs from source (https://launchpad.net/ubuntu/+source/livecd- rootfs/2.765.13). I checked that fwupd was still installed (required for Oracle bare-metal), and the modemmanager and udisk2 are not installed. I won't change the "verification-needed-jammy" tag yet as AWS will be checked too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Committed Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]
I can confirm that switching from wayland to xorg is a valid workaround on Ubuntu 22.04, which is still affected by this bug. -- 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/1934579 Title: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()] Status in nautilus package in Ubuntu: Triaged Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+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 1992478] [NEW] NNTP client becomes stuck when connecting to Public-Inbox servers
Public bug reported: In jammy 1:102.2.2+build1-0ubuntu0.22.04.1 broke access to nntp servers. It's fixed upstream already, see https://bugzilla.mozilla.org/show_bug.cgi?id=1786203 In the meantime 'mailnews.nntp.jsmodule = false' fixes the problem for me, but please backport the related fix. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1992478 Title: NNTP client becomes stuck when connecting to Public-Inbox servers Status in thunderbird package in Ubuntu: New Bug description: In jammy 1:102.2.2+build1-0ubuntu0.22.04.1 broke access to nntp servers. It's fixed upstream already, see https://bugzilla.mozilla.org/show_bug.cgi?id=1786203 In the meantime 'mailnews.nntp.jsmodule = false' fixes the problem for me, but please backport the related fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1992478/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
Hi Alberto, I'm glad to hear that there is some progress. Happy to test patches if you need feedback on something. -- 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/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER Status in snapd: In Progress Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Users with home directories in /home/$USER can run snap application, but users in /home/users/$USER can't. nate@WorkstationC:~$ snap --version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-22-generic nate@WorkstationC:~$ echo $HOME /home/users/nate nate@WorkstationC:~$ which hello-world /snap/bin/hello-world nate@WorkstationC:~$ hello-world cannot create nate data directory: /home/users/nate/snap/hello-world/27: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
With the revert, the network-manager ADT tests work again. https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/n/network-manager/20220505_053118_fb2db@/log.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Also affects: network-manager (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
This seems to be related to: "rfkill: make new event layout opt-in" in the -28 kernel. When I revert that a local reproduction run starts to work again. However I never got the same error pattern as in the ADT logs (those seem to get random data back from trying to read the MAC address). So a little doubt remains. -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] [NEW] network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
Public bug reported: This is a scripted bug report about ADT failures while running network- manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER Status in snapd: Confirmed Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in lxd package in Ubuntu: New Bug description: Users with home directories in /home/$USER can run snap application, but users in /home/users/$USER can't. nate@WorkstationC:~$ snap --version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-22-generic nate@WorkstationC:~$ echo $HOME /home/users/nate nate@WorkstationC:~$ which hello-world /snap/bin/hello-world nate@WorkstationC:~$ hello-world cannot create nate data directory: /home/users/nate/snap/hello-world/27: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
How can this be sitting around here for 3 years unassigned with *high* priority? And then apparently it's not even considered a blocker for replacing Firefox in Ubuntu 22.04 with the snap. Is it really that hard to fix or is just nobody paying attention to it? ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER Status in snapd: Confirmed Status in firefox package in Ubuntu: New Status in lxd package in Ubuntu: New Bug description: Users with home directories in /home/$USER can run snap application, but users in /home/users/$USER can't. nate@WorkstationC:~$ snap --version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-22-generic nate@WorkstationC:~$ echo $HOME /home/users/nate nate@WorkstationC:~$ which hello-world /snap/bin/hello-world nate@WorkstationC:~$ hello-world cannot create nate data directory: /home/users/nate/snap/hello-world/27: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+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 1967844] Re: firefox snap does not work with home directories outside of /home
*** This bug is a duplicate of bug 1776800 *** https://bugs.launchpad.net/bugs/1776800 I know that there are workarounds with bind-mounts and whatnot, but workarounds are not a feasible solution for a LTS release. -- 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/1967844 Title: firefox snap does not work with home directories outside of /home Status in firefox package in Ubuntu: New Bug description: Firefox version information below. I don't think replacing the deb version with the snap was a good idea. If your home directory is outside of /home (quite common for central home directories on a file server mounted via NFS or some other way for example) you cannot use Firefox in Ubuntu 22.04 anymore. $ firefox Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. This is a long standing issue and should have been addressed before replacing the deb with the snap version imho. --- $ snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/products/firefox license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable refresh-date: today at 10:17 CEST channels: latest/stable:98.0.2-12022-03-24 (1154) 162MB - latest/candidate: 99.0-2 2022-03-31 (1188) 163MB - latest/beta: 100.0b1-1 2022-04-05 (1200) 163MB - latest/edge: 100.0a1 2022-04-05 (1201) 179MB - esr/stable: 91.7.1esr-2 2022-03-14 (1116) 161MB - esr/candidate:91.8.0esr-1 2022-03-30 (1184) 161MB - esr/beta: ↑ esr/edge: ↑ installed: 98.0.2-1 (1154) 162MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967844/+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 1967844] [NEW] firefox snap does not work with home directories outside of /home
Public bug reported: Firefox version information below. I don't think replacing the deb version with the snap was a good idea. If your home directory is outside of /home (quite common for central home directories on a file server mounted via NFS or some other way for example) you cannot use Firefox in Ubuntu 22.04 anymore. $ firefox Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. This is a long standing issue and should have been addressed before replacing the deb with the snap version imho. --- $ snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/products/firefox license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable refresh-date: today at 10:17 CEST channels: latest/stable:98.0.2-12022-03-24 (1154) 162MB - latest/candidate: 99.0-2 2022-03-31 (1188) 163MB - latest/beta: 100.0b1-1 2022-04-05 (1200) 163MB - latest/edge: 100.0a1 2022-04-05 (1201) 179MB - esr/stable: 91.7.1esr-2 2022-03-14 (1116) 161MB - esr/candidate:91.8.0esr-1 2022-03-30 (1184) 161MB - esr/beta: ↑ esr/edge: ↑ installed: 98.0.2-1 (1154) 162MB - ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967844 Title: firefox snap does not work with home directories outside of /home Status in firefox package in Ubuntu: New Bug description: Firefox version information below. I don't think replacing the deb version with the snap was a good idea. If your home directory is outside of /home (quite common for central home directories on a file server mounted via NFS or some other way for example) you cannot use Firefox in Ubuntu 22.04 anymore. $ firefox Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. This is a long standing issue and should have been addressed before replacing the deb with the snap version imho. --- $ snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/products/firefox license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable refresh-date: today at 10:17 CEST channels: latest/stable:98.0.2-12022-03-24 (1154) 162MB - latest/candidate: 99.0-2 2022-03-31 (1188) 163MB - latest/beta: 100.0b1-1 2022-04-05 (1200) 163MB - latest/edge: 100.0a1 2022-04-05 (1201) 179MB - esr/stable: 91.7.1esr-2 2022-03-14 (1116) 161MB - esr/candidate:91.8.0esr-1 2022-03-30 (1184) 161MB - esr/beta: ↑ esr/edge: ↑ installed: 98.0.2-1 (1154) 162MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967844/+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 1821765] Re: [snap] Missing icon in indicator
Just asking if this is the problem I have: I have Chromium as a favorite in my gnome panel on the left side. After some time the indication of the running Chromium windows disappears (like no Chromium is running at all - clicking the shortcut on the left just opens a new window). When pressing ALT+TAB all other Chromium windows are there. I have this behavior on multiple systems running Ubuntu 21.10 amd64. -- 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/1821765 Title: [snap] Missing icon in indicator Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium is adding an appindicator, which has a missing icon when running from the snap. I've confirmed with the deb that it shows the chromium icon there. I'm not sure what setting makes it display the appindicator, I've had it there for years so must be some setting I have that is being synced. The only extensions I have installer are: * The Great Suspender * Google Drive * Google Calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1821765/+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 1954770] [NEW] the tracker is killing the nvm drive
Public bug reported: The tracker service is continuously writing and deleting more than 20G of 120GB partition (only 20G left). I do some development on this system but this what I create and delete is < 1MB per hour and tracker writes 20G per a few seconds! For now I solve it by using .nomedia files, but... Creating .nomedia files everywhere is not a solution. Whenever I forget to create it my drive is under high writing pressure. Please, create an option in the settings for settings up this tool and optionally turning it off. E.g. an option to select tree of folder that should not be indexed would be enough for me. Description:Ubuntu 20.04.3 LTS Release:20.04 tracker-miner-fs: 2.3.3-2, http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages I expect that indexing service will not take more space than the actual data that is changing. Instead changing the small chunks of files cause non proportionally higher writing on the disk (TBW on NVMe). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tracker-miner-fs 2.3.3-2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 14 13:09:39 2021 ExecutablePath: /usr/libexec/tracker-miner-fs InstallationDate: Installed on 2021-05-21 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: tracker-miners UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tracker-miners (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 tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1954770 Title: the tracker is killing the nvm drive Status in tracker-miners package in Ubuntu: New Bug description: The tracker service is continuously writing and deleting more than 20G of 120GB partition (only 20G left). I do some development on this system but this what I create and delete is < 1MB per hour and tracker writes 20G per a few seconds! For now I solve it by using .nomedia files, but... Creating .nomedia files everywhere is not a solution. Whenever I forget to create it my drive is under high writing pressure. Please, create an option in the settings for settings up this tool and optionally turning it off. E.g. an option to select tree of folder that should not be indexed would be enough for me. Description: Ubuntu 20.04.3 LTS Release: 20.04 tracker-miner-fs: 2.3.3-2, http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages I expect that indexing service will not take more space than the actual data that is changing. Instead changing the small chunks of files cause non proportionally higher writing on the disk (TBW on NVMe). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tracker-miner-fs 2.3.3-2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 14 13:09:39 2021 ExecutablePath: /usr/libexec/tracker-miner-fs InstallationDate: Installed on 2021-05-21 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: tracker-miners UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1954770/+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 1933188] [NEW] package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returne
Public bug reported: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1933188 Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post- installation script subprocess returned error exit status 2 Status in fprintd package in Ubuntu: New Bug description: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933188/+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 1928089] [NEW] package firefox 88.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: Extrahierte Daten für »./usr/lib/firefox/libxul.so« können nicht nach »/usr/lib/firefox/l
Public bug reported: Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/firefox_88.0.1+build1-0ubuntu0.20.04.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 88.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefan 1448 F pulseaudio BuildID: 20210415204500 CasperMD5CheckResult: skip Channel: Unavailable Date: Tue May 11 15:16:19 2021 ErrorMessage: Extrahierte Daten für »./usr/lib/firefox/libxul.so« können nicht nach »/usr/lib/firefox/libxul.so.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms ForcedLayersAccel: False InstallationDate: Installed on 2021-04-24 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.178.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.178.0/24 dev eno1 proto kernel scope link src 192.168.178.51 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 88.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: Extrahierte Daten für »./usr/lib/firefox/libxul.so« können nicht nach »/usr/lib/firefox/libxul.so.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20d dmi.board.asset.tag: Default string dmi.board.name: B460M DS3H V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20d:bd03/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3HV2:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3HV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: H470 MB dmi.product.name: B460MDS3HV2 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- 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/1928089 Title: package firefox 88.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: Extrahierte Daten für »./usr/lib/firefox/libxul.so« können nicht nach »/usr/lib/firefox/libxul.so.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms Status in firefox package in Ubuntu: New Bug description: Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/firefox_88.0.1+build1-0ubuntu0.20.04.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 88.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefan 1448 F pulseaudio BuildID: 20210415204500 CasperMD5CheckResult: skip Channel: Unavailable Date: Tue May 11 15:16:19 2021 ErrorMessage: Extrahierte Daten für »./usr/lib/firefox/libxul.so« können nicht nach »/usr/lib/firefox/libxul.so.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms ForcedLayersAccel: False InstallationDate: Installed on 2021-04-24 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.178.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.178.0/24 dev eno1 proto kernel scope link src 192.168.178.51 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 RunningIncompatibleAddons: False SourcePackage: firefox Title: package
Re: [Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
apt-get -y install alsa-tools cat > /lib/firmware/hda-jack-retask.fw << 'EOFFW' [codec] 0x10ec0235 0x17aa3826 0 [pincfg] 0x17 0x90170111 [verb] 0x01 0x0716 0x04 0x01 0x0717 0x04 0x01 0x0715 0x04 EOFFW cat > /etc/modprobe.d/hda-jack-retask.conf << 'EOFCONF' options snd-hda-intel power_save=0 power_save_controller=N patch=hda-jack-retask.fw EOFCONF 29.03.2021 19:49:49 Diogo André Cardoso Pereira <1553...@bugs.launchpad.net>: > How do you guys modify the files ? Im new to linux so i dont have no idea > what to do, i just install sudo apt get install hdajackretask,so what to do > next? > Also i dont find the files mentioned anywhere, im probably making this all > wrong XD > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1553685 > > Title: > Lenovo Y700-17ISK subwoofer doesn't work > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M > 4GB) > Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, > kernel 4.4.0-10-generic, nvidia 361.28) > > Problem: Notebook subwoofer doesn't work. > > Judging from alsa-info.sh output, there is no pin declared for the bass > output by BIOS. > Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-10-generic 4.4.0-10.25 > ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 > Uname: Linux 4.4.0-10-generic x86_64 > ApportVersion: 2.20-0ubuntu3 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: aljosa 1776 F pulseaudio > CurrentDesktop: Unity > Date: Sun Mar 6 11:02:21 2016 > HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 > InstallationDate: Installed on 2016-03-05 (0 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) > MachineType: LENOVO 80Q0 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed > root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 > RelatedPackageVersions: > linux-restricted-modules-4.4.0-10-generic N/A > linux-backports-modules-4.4.0-10-generic N/A > linux-firmware 1.156 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/31/2016 > dmi.bios.vendor: LENOVO > dmi.bios.version: CDCN30WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: Allsparks 7A > dmi.board.vendor: LENOVO > dmi.board.version: NO DPK > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo ideapad Y700-17ISK > dmi.modalias: > dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: > dmi.product.name: 80Q0 > dmi.product.version: Lenovo ideapad Y700-17ISK > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware
[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Hi there. I'm quite new to launchpad and don't know if my behavior is the right way now. I experience this same problem on actually five Lenovo P15s with Ubuntu 20.04 running on kernel 5.8.0-44-generic. My problem is, that I can't hand out those systems to our developers in their remote-offices until this is solved or worked around in any way and also that one of those laptops is my own one :-/ The "login to nirvana" occurs on every boot now, as far as the notebook is connected to its tb-dock and the lid is closed. What really concerns me is, that there is no way to "wake up" the system from the power down state. I tried a lot, but I have to hard-power-down them, otherwise they don't come up anymore. Has anyone found a workaround for this, until the problem is solved by the developers? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.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/gnome-settings-daemon/+bug/1841826/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Same problem: - Kernel: 5.8.0-41-generic - OS: Ubuntu 20.04.02 LTS - Headset: Sennheiser MB Pro 2 I can switch to HSP but even audio output won't work at all. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
I have the same errors in the syslog file and I am using Logitech mouse MX Master: Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27). Jan 21 17:46:54 sbelishki gnome-shell[4582]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Regards -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
@Timo Aaltonen What is the expected date for this patch to be merged with a main branch or whatever. So I could get it with "apt update"? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Drag and drop files from Desktop to Nautilus freezes gnome-shell in Ubuntu 20.10. There is no way to recover without killing gnome-shell externally or rebooting. [Test Case] 1. Create a file in ~/Desktop 2. Open a nautilus (Files) window of a different directory. 3. Drag the new file from the desktop into the nautilus (Files) window. The shell should not become unresponsive. Also, the drag is expected to fail and snap back. That's a different issue (bug 1813441) not being fixed here. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading. [Other Info] Patch is in bug 1898005. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+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 222208]
(In reply to clemens from comment #79) > 11 years of not resolving this bug? Just close it then and be a man about it. > > My (horrible) solution is an AutoHotkey script which keeps feeding the > password (stored in the AutoHotkey script) into the login dialog A better workaround is to use the Saved Password Editor. After you entered the password you'll get the thunderbird password prompt with username and password filled and only have to hit enter. See here: https://addons.mozilla.org/de/thunderbird/addon/saved-password-editor/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/08 Title: user-id and password not sent automatically for rss-feed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird This is a bug I have seen for quite some time. I am in the "make hardy the best release there ever was"-mood today and have brought myself to really reporting every single bit of problem I have put off for so long so somebody with the needed skills has a chance to fix it. I subscribe to an RSS feed hosted on a password-protected https-site in Thunderbird. TB works fine but periodically asks me for the password although I have marked "save password with password manager" in the dialog. In fact, the necessary fields are displayed filled in, but the pop-up comes back to me from time to time and I have to hit the OK button. I have set up a test installation which is exactly the same as the one I am having problems with at https://clients.leggewie.biz/tester/. The ssl-certificate is from cacert.org, so your browser might throw that up at first. The user you need to get in is tb-tester and the password is launchpad. The RSS feed is at https://clients.leggewie.biz/tester/index.php?title=Special:Recentchanges=rss When you susbscribe to that in TB and save the login credentials, you should have TB nagging you from time to time to with a login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/08/+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 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost
Thanks for fixing this! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576454 Title: Superfluous Xsession.d script: 60x11-common_localhost Status in xorg package in Ubuntu: Fix Released Bug description: Both of these scripts do the same thing, and both are installed by x11-common: /etc/X11/Xsession.d/35x11-common_xhost-local /etc/X11/Xsession.d/60x11-common_localhost 35x11-common_xhost-local is present in debian, while 60x11-common_localhost is not. I suspect the latter should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost
Attached a patch against https://salsa.debian.org/xorg- team/xorg/-/tree/ubuntu; not sure if this is the right repo, but it does have the offending change/file. ** Patch added: "0001-Revert-Seems-when-this-was-renamed-it-fell-out-of-gi.patch" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+attachment/5419480/+files/0001-Revert-Seems-when-this-was-renamed-it-fell-out-of-gi.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576454 Title: Superfluous Xsession.d script: 60x11-common_localhost Status in xorg package in Ubuntu: Confirmed Bug description: Both of these scripts do the same thing, and both are installed by x11-common: /etc/X11/Xsession.d/35x11-common_xhost-local /etc/X11/Xsession.d/60x11-common_localhost 35x11-common_xhost-local is present in debian, while 60x11-common_localhost is not. I suspect the latter should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost
... or maybe not, since I don't see the file in the Debian git repo (from the Vcs-Git field in from debian/control from the Ubuntu source): https://salsa.debian.org/xorg-team/xorg/-/tree/debian- unstable/debian/local/Xsession.d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576454 Title: Superfluous Xsession.d script: 60x11-common_localhost Status in xorg package in Ubuntu: Confirmed Bug description: Both of these scripts do the same thing, and both are installed by x11-common: /etc/X11/Xsession.d/35x11-common_xhost-local /etc/X11/Xsession.d/60x11-common_localhost 35x11-common_xhost-local is present in debian, while 60x11-common_localhost is not. I suspect the latter should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost
I think both files come from Debian. I did an 'apt-get source x11-common' and I see that debian/x11-common.install installs stuff from debian/local/Xsession.d. I see both files there: stefan@spuiu-vm:~/src/ubuntu/xorg-7.7+19ubuntu14$ grep -rn xhost debian/local/Xsession.d/ debian/local/Xsession.d/35x11-common_xhost-local:3:# If xhost (from x11-xserver-utils) is installed, use it to give access debian/local/Xsession.d/35x11-common_xhost-local:5:# Unlike other uses of xhost, this is safe since the kernel can check debian/local/Xsession.d/35x11-common_xhost-local:8:if type xhost >/dev/null 2>&1; then debian/local/Xsession.d/35x11-common_xhost-local:9: xhost +si:localuser:$(id -un) || : debian/local/Xsession.d/60x11-common_localhost:3:[ -x /usr/bin/xhost ] && [ -x /usr/bin/id ] && debian/local/Xsession.d/60x11-common_localhost:4:xhost +si:localuser:`id -un` > /dev/null -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576454 Title: Superfluous Xsession.d script: 60x11-common_localhost Status in xorg package in Ubuntu: Confirmed Bug description: Both of these scripts do the same thing, and both are installed by x11-common: /etc/X11/Xsession.d/35x11-common_xhost-local /etc/X11/Xsession.d/60x11-common_localhost 35x11-common_xhost-local is present in debian, while 60x11-common_localhost is not. I suspect the latter should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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 1898981] [NEW] x11-common: duplicate calls to xhost in /etc/X11/Xsession.d scripts
Public bug reported: Hi, While debugging a different issue (see https://askubuntu.com/questions/1280861/black-screen-after-18-04-20-04-1 -upgrade-on-virtualbox), I was trying to understand who runs 'xhost +si:localuser:' and found the scripts in /etc/X11/Xsession.d. There I noticed there are 2 scripts who end up calling xhost like this, with slightly different tweaks: stefan@spuiu-vm:~$ grep -rn xhost /etc/X11/Xsession.d/ /etc/X11/Xsession.d/35x11-common_xhost-local:3:# If xhost (from x11-xserver-utils) is installed, use it to give access /etc/X11/Xsession.d/35x11-common_xhost-local:5:# Unlike other uses of xhost, this is safe since the kernel can check /etc/X11/Xsession.d/35x11-common_xhost-local:8:if type xhost >/dev/null 2>&1; then /etc/X11/Xsession.d/35x11-common_xhost-local:9: xhost +si:localuser:$(id -un) || : /etc/X11/Xsession.d/60x11-common_localhost:3:[ -x /usr/bin/xhost ] && [ -x /usr/bin/id ] && /etc/X11/Xsession.d/60x11-common_localhost:4:xhost +si:localuser:`id -un` > /dev/null It looks to me like one of them could be easily deleted. I'd vote for keeping the first one, 'type ' seems a tad more sensible than '-x /usr/bin/', and also the first one makes sure there's no error exit status. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-common 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 8 09:29:46 2020 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2020-10-07 14:26:33,076 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-06-12 (2309 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: 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 MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=10a5a28d-f5fd-4e54-b4f5-ae3421877df4 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-07 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Oct 8 09:26:12 2020 xserver.configfile: default xserver.errors: Failed to load module "vboxvideo" (module does not exist, 0) Failed to load module "vboxvideo" (module does not exist, 0) modeset(0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1898981 Title: x11-common: duplicate calls to xhost in /etc/X11/Xsession.d scripts Status in xorg package in Ubuntu: New Bug description: Hi, While debugging a different issue (see https://askubuntu.com/questions/1280861/black-screen- after-18-04-20-04-1-upgrade-on-virtualbox), I was trying to understand who runs 'xhost +si:localuser:' and found the scripts in /etc/X11/Xsession.d. There I noticed there are 2
[Desktop-packages] [Bug 1892348] [NEW] cups samba authetication dialog closes too early
Public bug reported: Using network printers with samba authentication on Ubuntu 20.04 the authentication dialog is shown only a very short time and closes unexpectedly. But authentication works with noninteractive authentication using specifying username and password as part of the samba address. The interactive authentication dialog worked in Ubuntu 18.04 correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 12:57:13 2020 InstallationDate: Installed on 2020-07-07 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QF00AYGE Papersize: a4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QF00AYGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QF00AYGE:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QF00AYGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QF00AYGE dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1892348 Title: cups samba authetication dialog closes too early Status in cups package in Ubuntu: New Bug description: Using network printers with samba authentication on Ubuntu 20.04 the authentication dialog is shown only a very short time and closes unexpectedly. But authentication works with noninteractive authentication using specifying username and password as part of the samba address. The interactive authentication dialog worked in Ubuntu 18.04 correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 12:57:13 2020 InstallationDate: Installed on 2020-07-07 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QF00AYGE Papersize: a4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QF00AYGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QF00AYGE:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QF00AYGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QF00AYGE dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892348/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
DisplayLink offers a patch for the XServer: https://www.displaylink.org/forum/showthread.php?t=67148 Applying the patch on my Dell XPS running Ubuntu 20.04.1 seems to fix the problem. -- 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/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Sorry this sucks guys - when is it going to get fixed? Ubuntu 20.04 also stopped working for me since the transition to snap happend - all kerberos and gssapi authentications no longer work -- 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/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in chromium-browser package in Ubuntu: Confirmed Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+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 1883206] Re: Persistent high CPU load (~80%)
Looks like it is related to an extension. Haven't had a problem since I disabled all of them. This bug can be closed. Once I identify the extension causing the CPU load I'll report an issue on its github page. -- 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/1883206 Title: Persistent high CPU load (~80%) Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome shell has a persistent high CPU load that make using the PC painful. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1883206/+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 1883206] [NEW] Persistent high CPU load (~80%)
Public bug reported: gnome shell has a persistent high CPI load that make using the PC painful. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1883206 Title: Persistent high CPU load (~80%) Status in gnome-shell package in Ubuntu: New Bug description: gnome shell has a persistent high CPI load that make using the PC painful. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1883206/+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 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
This update works for me https://launchpad.net/~sergiodj/+archive/ubuntu/samba-bug1872476-v2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: Incomplete Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+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 1083565] Re: avahi malfunctions on a machine connected to the network via multiple interfaces
Please have a look at the upstream bug: https://github.com/lathiat/avahi/issues/117 ** Bug watch added: github.com/lathiat/avahi/issues #117 https://github.com/lathiat/avahi/issues/117 -- 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/1083565 Title: avahi malfunctions on a machine connected to the network via multiple interfaces Status in avahi package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I have a router making up one local NAT network connected to the internet. The router allows to connect both wired and wireless. My laptops are configured to use both wired and wireless. So I can walk around with them and also connect to the quicker wired network if they are on the desk. Problem is that when the laptops are on my desk and I plug in the network cables they stay connected on wireless and so they get connected twice, wired and wireless, with two IP addresses, appearing as two computers for the router and all other computers in the network. Most things still simply work, like accessing the internet from the laptops, SSHing to another computer, ... what causes problems is Bonjour/mDNS. Avahi broadcasts available services (I have shared CUPS printers on the laptops) into the network, using the host name of the machine assigned on installation, for example "till-lenovo". As the broadcasts go through two interfaces there is a service name conflict and it seems that Avahi tries to overcome it by using host names like "till-lenovo-1", "till-lenovo-2", ... When the laptop keeps running one sees in the "avahi-discover" output on another machine the entries from the laptop, but with host names (and so the service names) changing from time to time. This leads to a client with a print queue pointing to a printer shared by the laptop via the printer's Bonjour service name cannot print any more. I have done a short test and Avahi stops adding numbers to the original host name when turning off wireless on the laptop so that it connects only through the wired network. One way of fixing (or working around?) the problem would be a change in network-manager to automatically turn off wireless if the computer is connected to a wired network and switching wireless back on when the network cable gets disconnected. This would probably also solve problems with other server functionality. --->> http://somapills.net Another solution would be a change in Avahi, somehow recognizing that the broadcasts through the two interfaces come from the same computer and so they can (and should) have the same service names, or recognizing that the two interfaces go into the same network and therefore broadcast only through one of them, stopping the broadcasting through the weaker one (the wireless in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1083565/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
I am adding the block-proposed-bionic before this falls in between cracks. Right now we ended up in a situation where the nvidia-440 modules were added to the kernel lrm package build but the version used for the nvidia-390 modules was not updated to the proposed version. The hope is that having the meta from the driver package held back in proposed is less risk than releasing user-space for everything and not having the right modules in lrm. ** Tags added: block-proposed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR)
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I have the same issue since upgrading to Ubuntu 19.10. SQLYog (with Wine and X11) became almost unusable. Only 1 of 10 attempts work. For the moment, I use Heidi SQL (with Wine) where only 50% fail. Simply pressing Ctrl-C repeatedly does not work for me because When I press Ctrl-C multiple times, then both SQLYog and HeidiSQL sometimes freeze for a minute, sometimes they freeze until I kill them hardly. I cannot switch to Wayland because then the screen sharing function of Skype would not work, which I also need every day. I hope that this will be fixed in the next LTS release. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 518966] Re: Wrong pitch and crackling sound with 5.1 output on Extigy USB card
I can confirm that there seems to be a regression in the alsa audio
driver. I was trying this soundcard directly with alsa and get
distoreted audio and rumble in *some* apps.
--
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/518966
Title:
Wrong pitch and crackling sound with 5.1 output on Extigy USB card
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
Binary package hint: pulseaudio
Since i upgraded to Karmic, my 5.1 sound output on my creative labs extigy
USB card is broken.
The previous release did work with alsa, and was working fine.
Now with Pulseaudio, the sound is only working correctly with stereo output,
with 5.1, the sound is crackling, and the pitch is too high.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Extigy [Sound Blaster Extigy], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jean-luc 2681 F pulseaudio
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xfe9fc000 irq 29'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100100'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Extigy'/'Creative Technology Ltd. Sound Blaster Extigy at
usb-:00:1a.0-2, full speed'
Mixer name : 'USB Mixer'
Components : 'USB041e:3000'
Controls : 23
Simple ctrls : 17
Date: Mon Feb 8 19:48:40 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: alsa-driver
Uname: Linux 2.6.31-19-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/518966/+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 1862169] Re: rhythmbox crashed with SIGSEGV in build_flavored_key()
Confirmed to be fixed. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1862169 Title: rhythmbox crashed with SIGSEGV in build_flavored_key() Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1862169/+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 1862169] Re: rhythmbox crashed with SIGSEGV in build_flavored_key()
** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1862169 Title: rhythmbox crashed with SIGSEGV in build_flavored_key() Status in rhythmbox package in Ubuntu: Confirmed Bug description: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1862169/+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 1862169] [NEW] rhythmbox crashed with SIGSEGV in build_flavored_key()
Public bug reported: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6: movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: rhythmbox (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-crash focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1862169 Title: rhythmbox crashed with SIGSEGV in build_flavored_key() Status in rhythmbox package in Ubuntu: Confirmed Bug description: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1862169/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I tried it, however, no sound from my subwoofer. During a sound check, just a very faint swoosh can be heared. Nevertheless - nice try! Thank you! regards, HSS -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1855434] Re: Vino VNC connection has wrong keyboard layout
The problem seems to get worse, as in 90% of the cases the above mentioned sudo dpkg-reconfigure keyboard-configuration does not fix the problem anymore. I have to cycle reboots for 10-20 times until I get the correct mapping. Any help is appreciated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1855434 Title: Vino VNC connection has wrong keyboard layout Status in vino package in Ubuntu: New Bug description: After upgrading a machine from 16.04.3 LTS to 18.04.3 Vino VNC connections use the wrong keyboard layout. By default I use "DE" keyboard layout. If I connect from another 18.04.3 machine to said vino on the upgraded 18.04.3 machine, the keyboard layout seems to be "kind of" US, not other keys are as well not correct. I can only fix this by running sudo dpkg-reconfigure keyboard-configuration in a console (pressing Enter all the way through and confirm settings) and rebooting. If I connect to vino VNC after issueing this command and rebooting, the layout is correct until next reboot. Then I have to issue this command again and so on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Dec 6 12:52:22 2019 InstallationDate: Installed on 2017-12-29 (707 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: vino UpgradeStatus: Upgraded to bionic on 2019-10-29 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1855434/+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 1852863] Re: Don't know
Thank you very much, i will try your Proposal and thank you for your help best wishes stefan Am 06.12.19 um 07:19 schrieb Daniel van Vugt: > Also, you won't get working graphics while 'nomodeset' is on your kernel > command line. Unless you need it as a workaround that word 'nomodeset' > should be removed. > -- 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/1852863 Title: Don't know Status in mutter package in Ubuntu: Incomplete Bug description: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Nov 16 11:58:52 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852863/+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 1855434] [NEW] Vino VNC connection has wrong keyboard layout
Public bug reported: After upgrading a machine from 16.04.3 LTS to 18.04.3 Vino VNC connections use the wrong keyboard layout. By default I use "DE" keyboard layout. If I connect from another 18.04.3 machine to said vino on the upgraded 18.04.3 machine, the keyboard layout seems to be "kind of" US, not other keys are as well not correct. I can only fix this by running sudo dpkg-reconfigure keyboard-configuration in a console (pressing Enter all the way through and confirm settings) and rebooting. If I connect to vino VNC after issueing this command and rebooting, the layout is correct until next reboot. Then I have to issue this command again and so on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Dec 6 12:52:22 2019 InstallationDate: Installed on 2017-12-29 (707 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: vino UpgradeStatus: Upgraded to bionic on 2019-10-29 (38 days ago) ** Affects: vino (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1855434 Title: Vino VNC connection has wrong keyboard layout Status in vino package in Ubuntu: New Bug description: After upgrading a machine from 16.04.3 LTS to 18.04.3 Vino VNC connections use the wrong keyboard layout. By default I use "DE" keyboard layout. If I connect from another 18.04.3 machine to said vino on the upgraded 18.04.3 machine, the keyboard layout seems to be "kind of" US, not other keys are as well not correct. I can only fix this by running sudo dpkg-reconfigure keyboard-configuration in a console (pressing Enter all the way through and confirm settings) and rebooting. If I connect to vino VNC after issueing this command and rebooting, the layout is correct until next reboot. Then I have to issue this command again and so on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Dec 6 12:52:22 2019 InstallationDate: Installed on 2017-12-29 (707 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: vino UpgradeStatus: Upgraded to bionic on 2019-10-29 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1855434/+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 1852863] Re: Don't know
In the appendix, an image of the screen in which the PC's crotch hangs. I hope, this might be helpfull. Thank you On 16.11.19 22:48, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. You may find it helpful > to read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > > At a minimum, we need: > 1. The specific steps or actions you took that caused you to encounter the > problem. > 2. The behavior you expected. > 3. The behavior you actually encountered (in as much detail as possible). > Thanks! > > ** Changed in: xorg (Ubuntu) > Status: New => Incomplete > ** Attachment added: "IMG_20190716_205949.jpg" https://bugs.launchpad.net/bugs/1852863/+attachment/5306320/+files/IMG_20190716_205949.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852863 Title: Don't know Status in xorg package in Ubuntu: Incomplete Bug description: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Nov 16 11:58:52 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852863/+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 1852863] [NEW] Don't know
Public bug reported: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Nov 16 11:58:52 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852863 Title: Don't know Status in xorg package in Ubuntu: New Bug description: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1851936] [NEW] Existing user profile won't load after upgrapde
Public bug reported:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing firefox
profile won't load on starting, instead application wants new default
profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44 metric
100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
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:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
** Affects: firefox (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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
Existing user profile won't load after upgrapde
Status in firefox package in Ubuntu:
New
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
Re: [Desktop-packages] [Bug 1843164] Re: gnome-terminal starts, but shows no window
I think the lesson here might be to leave Ubuntu 19... Thanks On Mon, 9 Sep 2019 at 05:35, Daniel van Vugt wrote: > I think gnome-terminal has other odd dependencies like it needs to > receive information about the login session and bus before it is willing > to display. For this reason I would recommend 'xterm' instead if you > need a working shell via ssh. > > ** Changed in: gnome-terminal (Ubuntu) >Status: New => Confirmed > > ** Changed in: gnome-terminal (Ubuntu) >Importance: Undecided => Medium > > ** Summary changed: > > - gnome-terminal starts, but shows no window > + gnome-terminal starts, but shows no window when launched from SSH > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1843164 > > Title: > gnome-terminal starts, but shows no window when launched from SSH > > Status in gnome-terminal package in Ubuntu: > Confirmed > > Bug description: > I am starting gnome-terminal on the command line (SSH). It displays > nothing and does not show the terminal window. This is a v-server > using VNC and Ubuntu 19. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-terminal 3.32.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 > Uname: Linux 5.0.0-25-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > Date: Sun Sep 8 11:42:23 2019 > SourcePackage: gnome-terminal > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843164/+subscriptions > -- Stefan Reich BotCompany.de // Java-based operating systems -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1843164 Title: gnome-terminal starts, but shows no window when launched from SSH Status in gnome-terminal package in Ubuntu: Confirmed Bug description: I am starting gnome-terminal on the command line (SSH). It displays nothing and does not show the terminal window. This is a v-server using VNC and Ubuntu 19. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Sep 8 11:42:23 2019 SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843164/+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 1843164] Re: gnome-terminal starts, but shows no window
Edit 2: $DISPLAY is correctly set to :1 (VNC). Other GUI programs start fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1843164 Title: gnome-terminal starts, but shows no window Status in gnome-terminal package in Ubuntu: New Bug description: I am starting gnome-terminal on the command line (SSH). It displays nothing and does not show the terminal window. This is a v-server using VNC and Ubuntu 19. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Sep 8 11:42:23 2019 SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843164/+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 1843164] [NEW] gnome-terminal starts, but shows no window
Public bug reported: I am starting gnome-terminal on the command line (SSH). It displays nothing and does not show the terminal window. This is a v-server using VNC and Ubuntu 19. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Sep 8 11:42:23 2019 SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1843164 Title: gnome-terminal starts, but shows no window Status in gnome-terminal package in Ubuntu: New Bug description: I am starting gnome-terminal on the command line (SSH). It displays nothing and does not show the terminal window. This is a v-server using VNC and Ubuntu 19. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Sep 8 11:42:23 2019 SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843164/+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 1843164] Re: gnome-terminal starts, but shows no window
Oh, also the windowless gnome-terminal process never exits until I press Ctrl+C. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1843164 Title: gnome-terminal starts, but shows no window Status in gnome-terminal package in Ubuntu: New Bug description: I am starting gnome-terminal on the command line (SSH). It displays nothing and does not show the terminal window. This is a v-server using VNC and Ubuntu 19. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Sep 8 11:42:23 2019 SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1843164/+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 1825626] Re: nvLock: client timed out, taking the lock
Did anyone try setting __GL_MaxFramesAllowed=1 as discussed in https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 ? It helped me to get rid of the lockups on manjaro (didn't try on ubuntu though) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1202 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 -- 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/1825626 Title: nvLock: client timed out, taking the lock Status in gnome-desktop: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+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 1840508] [NEW] eog crashes if new files are written to the directory it is reading from
Public bug reported: If eog is called to read a png file from a directory like: eog mydirectory/picture.png while new png images are frequently added to this directory, eog crashes with random errors, e. g.: (eog:4447): GLib-WARNING **: 00:00:37.123: Accessing a sequence while it is being sorted or searched is not allowed (eog:4447): GLib-WARNING **: 00:00:37.124: Accessing a sequence while it is being sorted or searched is not allowed malloc(): memory corruption Aborted (core dumped) This happens only if the files are written to the same directory. If the files are written to different directories, it opens it without error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 16 23:52:32 2019 InstallationDate: Installed on 2019-06-08 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1840508 Title: eog crashes if new files are written to the directory it is reading from Status in eog package in Ubuntu: New Bug description: If eog is called to read a png file from a directory like: eog mydirectory/picture.png while new png images are frequently added to this directory, eog crashes with random errors, e. g.: (eog:4447): GLib-WARNING **: 00:00:37.123: Accessing a sequence while it is being sorted or searched is not allowed (eog:4447): GLib-WARNING **: 00:00:37.124: Accessing a sequence while it is being sorted or searched is not allowed malloc(): memory corruption Aborted (core dumped) This happens only if the files are written to the same directory. If the files are written to different directories, it opens it without error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 16 23:52:32 2019 InstallationDate: Installed on 2019-06-08 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1840508/+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 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
I have upgraded from 16.04 to 18.04 and I am missing the top bar on multiple monitors. I would like to have this feature by default. -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: Incomplete Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+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 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks)
Does anyone have a workaround? -- 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/1809737 Title: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks) Status in Onboard: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: Onboard 1.4.1 crashes the entire Desktop if I selected any alternate character from pop-up [bishop@fringe ~]$ ls /usr/share/xsessions/ xfce.desktop [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP XFCE [bishop@fringe ~]$ echo $XDG_SESSION_TYPE x11 [bishop@fringe ~]$ cat /etc/*-release Fedora release 29 (Twenty Nine) NAME=Fedora VERSION="29 (Twenty Nine)" ID=fedora VERSION_ID=29 VERSION_CODENAME="" PLATFORM_ID="platform:f29" PRETTY_NAME="Fedora 29 (Twenty Nine)" ANSI_COLOR="0;34" LOGO=fedora-logo-icon CPE_NAME="cpe:/o:fedoraproject:fedora:29" HOME_URL="https://fedoraproject.org/; DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/; SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help; BUG_REPORT_URL="https://bugzilla.redhat.com/; REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=29 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=29 PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy; Fedora release 29 (Twenty Nine) Fedora release 29 (Twenty Nine) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1809737/+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 543183]
Probably relates to bug 454036 and should be platform all
--
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/543183
Title:
Updating system certificates requires rebuild
Status in Mozilla Firefox:
Confirmed
Status in firefox package in Ubuntu:
Triaged
Status in firefox package in Fedora:
Won't Fix
Bug description:
Binary package hint: firefox
Hi,
Updating the list of trusted root certificate authorities across all users of
a system seems requires rebuilding a library. Non-root certificates may
similarly be impacted.
update-ca-certificates could be a mechanism to update the root
certificates used by firefox.
On a corporate install of firefox, currently the only options to adding an
internal root certificate authority are to:
* Hack it into the user creation script to extract a pre-created profile,
and update all the existing users profile directory. This bypasses the random
profile directory creation.
* Re-compile the shared library (.so) containing the root certificate
authorities (extra maintenance for dealing with ubuntu package updates).
* Have every user of the system go through a manual process of adding the
root certificate (most users don't know how).
* Use a plugin extension for firefox (do any exist?) that is automatically
used by all users (can this be done?)
* Have the root certificate signed at great expense by an external root
certificate authority already included. CaCert integration would lower the cost
but that seems far away, and is still an external authority. These root
certificates also might be limited to a single domain (wildcard certificate?)
or have other limitations ("low" expiry?, contractual restrictions...).
It seems unlikely that Mozilla will move away from having the root
certificates stored in the shared library as it would take some
control away from them. The shared libary method makes it harder for
malicious changes to be made, but only by adding the barier of
recompilation and installation of a shared library.
Thanks,
Drew Daniels
Resume: http://www.boxheap.net/ddaniels/resume.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/543183/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection
I'm on ubuntu 18.10 and I get random drops but if I disconnect and reconnect from the UI, it works. This isn't happening on my laptop which runs 18.04 also on cable connection. -network description: Ethernet interface product: I211 Gigabit Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@:07:00.0 logical name: enp7s0 version: 03 serial: e0:d5:5e:a0:55:0f size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.4.0-k duplex=full firmware=0. 6-1 ip=192.168.0.108 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:38 memory:f760-f761 ioport:f000(size=32) memory:f762-f7623fff -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably
[Desktop-packages] [Bug 1795021] Re: gsd-xsettings high memory usage
Hi Team, I have the same problem on old and on a brand new installation: Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic top - 07:31:47 up 19:36, 1 user, load average: 1.07, 1.51, 1.28 Tasks: 233 total, 1 running, 182 sleeping, 0 stopped, 0 zombie %Cpu(s): 23.3 us, 5.4 sy, 0.0 ni, 70.8 id, 0.1 wa, 0.0 hi, 0.3 si, 0.0 st KiB Mem : 8078524 total, 2984196 free, 2415156 used, 2679172 buff/cache KiB Swap: 2097148 total, 2097148 free,0 used. 5104796 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1253 gogroop+ 20 0 1478224 992.9m 17552 S 0.0 12.6 7:07.67 /usr/lib/gnome-settings-daemon/gsd-xsettings 1099 gogroop+ 20 0 4015020 399532 155588 S 0.0 4.9 1:41.92 /usr/bin/gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795021 Title: gsd-xsettings high memory usage Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795021/+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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
... a fresh install of Ubuntu desktop 18.10 (forgot to mention that in post above) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Released Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
I get directed to this issue when I try to install nvidia-driver-390 in a fresh install. The kernel module compile fails with things like this: ```Building for 4.18.0-16-generic Building for architecture x86_64 Building initial module for 4.18.0-16-generic ERROR (dkms apport): There was a segmentation fault when trying to build the module Error! Bad return status for module build on kernel: 4.18.0-16-generic (x86_64) Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information.``` The make log contains some dangerous sounding compiler panics: ``` cc -Wp,-MD,/var/lib/dkms/nvidia/390.116/build/nvidia/.nv_uvm_interface.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/8/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -Iubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -mrecord-mcount -I/var/lib/dkms/nvidia/390.116/build/common/inc -I/var/lib/dkms/nvidia/390.116/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"390.116\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Wno-sign-compare -Wno-format-extra-args -Werror=undef -I/var/lib/dkms/nvidia/390.116/build/nvidia -DNV_BUILD_MODULE_INSTANCES=0 -DNVIDIA_UNDEF_LEGACY_BIT_MACROS -UDEBUG -U_DEBUG -DNDEBUG -DMODULE -DKBUILD_BASENAME='"nv_uvm_interface"' -DKBUILD_MODNAME='"nvidia"' -c -o /var/lib/dkms/nvidia/390.116/build/nvidia/nv_uvm_interface.o /var/lib/dkms/nvidia/390.116/build/nvidia/nv_uvm_interface.c In file included from ./include/linux/dynamic_debug.h:6, from ./include/linux/printk.h:357, from ./include/linux/kernel.h:14, from ./include/linux/list.h:9, from ./include/linux/preempt.h:11, from ./include/linux/spinlock.h:51, from /var/lib/dkms/nvidia/390.116/build/common/inc/nv-lock.h:16, from /var/lib/dkms/nvidia/390.116/build/common/inc/nv-linux.h:19, from /var/lib/dkms/nvidia/390.116/build/nvidia/nv-report-err.c:24: ./include/linux/jump_label.h: In function 'static_key_true': ./include/linux/jump_label.h:147:2: internal compiler error: Segmentation fault return !arch_static_branch(key, true); ^~ Please submit a full bug report, with preprocessed source if appropriate. See for instructions.``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Released Bug description: SRU Request:
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
This should also be fixed in the PPA: ppa:graphics-drivers/ppa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 0 upgraded, 14 newly installed, 6 to
[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
I did at least check the dkms install step on a trusty VM with lts- xenial kernel installed and the nvidia-304 driver installed. That did succeed. Similar testing for nvidia-340 and -384 but those were done for xenial VMs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 1730451] Re: MemoryError while verifying backup
I received a pretty similar error and thought I'd share my workaround. It may be OT but people are bound to come across this bug when they google. The process would look like the backup was working (and for < 200MB and a small number of files it did) - but larger folders would do up to 4 MemoryErrors before they would time out. I received the error with the main version (I believe it was 0.7.12) as well as with a more recent version (0.7.18.2). My workaround was that I would MOUNT the remote folder (with sshfs) before executing my backup against the mounted folder. The commands remained otherwise unchanged. I've since done a full 100GB backup with > 400K files successfully. Former statement: duplicity full --encrypt-key="XXX" /source/files scp://a...@server.provider.com/files Working statement: duplicity full --encrypt-key="XXX" /source/files file:///mnt/destination/files Curious indeed. Hope this helps anyone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1730451 Title: MemoryError while verifying backup Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Released Bug description: While trying to verify a backup (launched from deja-dup), I receive the following error. My system currently shows 11G of RAM available plus 23G of swap. Possibly related to #1720159? Traceback (most recent call last): File "/usr/bin/duplicity", line 1546, in with_tempdir(main) File "/usr/bin/duplicity", line 1540, in with_tempdir fn() File "/usr/bin/duplicity", line 1391, in main do_backup(action) File "/usr/bin/duplicity", line 1468, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 731, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 763, in get_fileobj_iter manifest = backup_set.get_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, in get_manifest return self.get_local_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, in get_local_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in from_string for match in vi_iterator: MemoryError ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: duplicity 0.7.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 6 10:50:12 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-03 (1190 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: duplicity UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1730451/+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 1817441] [NEW] lirc ITE8713 not working
Public bug reported: On Zotac ZBOX NANO AQ01 remote control with in build ir receiver does not work. $ irw # gives not output at all $ mode2 -d /dev/lirc0 # gives output $ sudo dpkg-reconfigure lirc # Windows Media Center Transceivers/Remotes (all) chosen $ sudo systemctl status lirc ● lirc.service - LSB: Starts LIRC daemon. Loaded: loaded (/etc/init.d/lirc; generated) Active: active (running) since Sun 2019-02-24 00:48:21 CET; 17min ago Docs: man:systemd-sysv-generator(8) Process: 6693 ExecStart=/etc/init.d/lirc start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 3976) CGroup: /system.slice/lirc.service └─6706 /usr/sbin/lircd --output=/run/lirc/lircd --device=/dev/lirc0 Feb 24 00:48:21 keksdose systemd[1]: Starting LSB: Starts LIRC daemon Feb 24 00:48:21 keksdose lirc[6693]: * Loading LIRC modules Feb 24 00:48:21 keksdose lirc[6693]:...done. Feb 24 00:48:21 keksdose lirc[6693]: * Starting remote control daemon(s) : Feb 24 00:48:21 keksdose lircd-0.9.0[6706]: lircd(default) ready, using /run/lirc/lircd Feb 24 00:48:21 keksdose lirc[6693]:...done. Feb 24 00:48:21 keksdose systemd[1]: Started LSB: Starts LIRC daemon.. Feb 24 00:48:24 keksdose lircd-0.9.0[6706]: accepted new client on /run/lirc/lircd Feb 24 00:48:50 keksdose lircd-0.9.0[6706]: removed client $ sudo ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event4) with: Name: ITE8713 CIR transceiver Driver: ite-cir, table: rc-rc6-mce lirc device: /dev/lirc0 Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp Enabled protocols: lirc bus: 25, vendor/product: 1283:, version: 0x Repeat delay = 500 ms, repeat period = 125 ms ** Affects: lirc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1817441 Title: lirc ITE8713 not working Status in lirc package in Ubuntu: New Bug description: On Zotac ZBOX NANO AQ01 remote control with in build ir receiver does not work. $ irw # gives not output at all $ mode2 -d /dev/lirc0 # gives output $ sudo dpkg-reconfigure lirc # Windows Media Center Transceivers/Remotes (all) chosen $ sudo systemctl status lirc ● lirc.service - LSB: Starts LIRC daemon. Loaded: loaded (/etc/init.d/lirc; generated) Active: active (running) since Sun 2019-02-24 00:48:21 CET; 17min ago Docs: man:systemd-sysv-generator(8) Process: 6693 ExecStart=/etc/init.d/lirc start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 3976) CGroup: /system.slice/lirc.service └─6706 /usr/sbin/lircd --output=/run/lirc/lircd --device=/dev/lirc0 Feb 24 00:48:21 keksdose systemd[1]: Starting LSB: Starts LIRC daemon Feb 24 00:48:21 keksdose lirc[6693]: * Loading LIRC modules Feb 24 00:48:21 keksdose lirc[6693]:...done. Feb 24 00:48:21 keksdose lirc[6693]: * Starting remote control daemon(s) : Feb 24 00:48:21 keksdose lircd-0.9.0[6706]: lircd(default) ready, using /run/lirc/lircd Feb 24 00:48:21 keksdose lirc[6693]:...done. Feb 24 00:48:21 keksdose systemd[1]: Started LSB: Starts LIRC daemon.. Feb 24 00:48:24 keksdose lircd-0.9.0[6706]: accepted new client on /run/lirc/lircd Feb 24 00:48:50 keksdose lircd-0.9.0[6706]: removed client $ sudo ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event4) with: Name: ITE8713 CIR transceiver Driver: ite-cir, table: rc-rc6-mce lirc device: /dev/lirc0 Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp Enabled protocols: lirc bus: 25, vendor/product: 1283:, version: 0x Repeat delay = 500 ms, repeat period = 125 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1817441/+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 1740180]
Mozilla/5.0 (Windows NT 6.1; rv:67.0) Gecko/20100101 Firefox/67.0 (20190219094627) Reproducible using the latest Nightly build on Windows 7 x84 with the following error in the browser console "SecurityError: Permission denied to get property "href" on cross-origin object" -- 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/1740180 Title: Firefox stops loading Farmville 2 and hangs. Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. Farmville 2 hangs while loading. Never plays. The Adobe Flash Player is properly installed. Has also been re- installed. Ditto for FireFox. Does not matter if using Ubuntu 16.04 or 17.10. Farmville 2 via Facebook in Firefox hangs. Also will not work if run from the Zynga URL (the makers of Farmville 2. Other Facebook games work well. Try "Pearl's Perils." Happy to help with testing if you like. This has been tested on both desktops and laptops. Thanks, Ken Wagner ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Dec 26 15:59:05 2017 InstallationDate: Installed on 2017-03-06 (295 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ken2466 F pulseaudio /dev/snd/pcmC0D0p: ken2466 F...m pulseaudio /dev/snd/controlC0: ken2466 F pulseaudio /dev/snd/controlC2: ken2466 F pulseaudio BuildID: 20180614184508 Channel: beta CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-03-28 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.0.1 dev enp2s0 proto static metric 100 default via 192.168.1.1 dev wlx7cdd908b43ea proto static metric 600 169.254.0.0/16 dev wlx7cdd908b43ea scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx7cdd908b43ea proto kernel scope link src 192.168.1.2 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: LP-PPA-mozillateam-firefox-next] PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use) RunningIncompatibleAddons: False SubmittedCrashIDs: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 bp-481cf9ec-efcd-4900-93aa-4e8940180512 bp-ad49167e-7776-4ff5-8acc-5adb50180421 bp-08f026d0-e273-45fb-b355-c70ae0180402 Tags: xenial third-party-packages beta-channel Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M.
[Desktop-packages] [Bug 241937]
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 (20170915100121) This issue is verified as fixed with the latest Nightly build on 9/15/2017. -- 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/241937 Title: Handle tabs like other gnome apps Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox-3.0 I have noticed that dragging tabs in Firefox does not work like in other gnome apps. Basically, you can drag tabs along the tab bar to change their order, like in so many gnome apps. But you can also drag them up and down: if you accidentally drag them up and drop them on the bookmark bar, you add a bookmark for it. and if you accidentally drag it down to the browser area, you load that page again. As you can see in the attached screenshot, the "good" area is quite small compared to the "bad" areas, so it's actually very easy to miss and drop the tab on a wrong place, and perform an action you didn't want. I propose that tabs in Firefox should behave just like gnome apps, and be able to move only left or right. If you don't agree because you like being able to easily adding a bookmark or loading a page, think that the same exact effect can be achieved by dragging the favicon instead of the tab. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/241937/+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 1791409] Re: LIRC not working on Ubuntu 18.04
I can confirm the issue on Ubuntu 18.04 Server. If there is a fixed upstream version, what is needed to see an updated package in Ubuntu? Is there anything I can help with? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 Status in lirc package in Ubuntu: Confirmed Bug description: It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is not working correctly. The usual configuration menu to select your remote does not come up after installing the package. Saw some other mentions of this issue as well on the forums: https://ubuntuforums.org/showthread.php?t=2396923 This handy blog post shows a workaround of installing an older version (0.9.0) from xenial to get it to work: https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in- ubuntu-18-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+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 1814387] Re: swithching workspace by scrolling on edge of Dock (left side bar)
No I don't have "dash to dock" installed (never heard of it before) No, I don't scroll on the application button, it is just exactly the same behavior. It works on the complete pixel line at the edge. The similar bug could be actually the same, if you assume that the dock is a layer of 2 rectangles where the upper one (which contains the program shortcuts) is a bit too small on both sides. I have really no knowledge about how it is implemented, so it could be sth totally different. requested output: ii gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 all Ubuntu Dock for GNOME Shell (I've removed some whitespaces) -- 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/1814387 Title: swithching workspace by scrolling on edge of Dock (left side bar) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: If you position the mouse corsor on the edge of Dock and scroll, you can switch the workspace, which behaves equivalent to the scrolling on the "Show Applications" button in the corner. I've reproduced it on other Ubuntu 18 installations of friends (all 3 I tested, at least one was a fresh installation from the official iso). It is not important where Dock is or whether a window or the desktop is next to it. Program shortcuts have also no effect, because they end before it. It works with a single or 2 monitors on all instances of Dock. I use Ubuntu 18.04.1 LTS with all updates (via apt upgrade) installed and observed it for several months now. (After starting apport for this I updated again and nothing changed, no restart) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 2 16:10:48 2019 DistUpgraded: 2018-10-01 14:59:21,229 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:2300] Subsystem: CLEVO/KAPOK Computer GM107M [GeForce GTX 860M] [1558:2300] InstallationDate: Installed on 2017-03-18 (685 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Notebook W230SS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=907d4e48-c148-454e-aa8a-7adb74d51fb2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-01 (124 days ago) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 1 13:12:45 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1814387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1814387] [NEW] swithching workspace by scrolling on edge of Dock (left side bar)
Public bug reported: If you position the mouse corsor on the edge of Dock and scroll, you can switch the workspace, which behaves equivalent to the scrolling on the "Show Applications" button in the corner. I've reproduced it on other Ubuntu 18 installations of friends (all 3 I tested, at least one was a fresh installation from the official iso). It is not important where Dock is or whether a window or the desktop is next to it. Program shortcuts have also no effect, because they end before it. It works with a single or 2 monitors on all instances of Dock. I use Ubuntu 18.04.1 LTS with all updates (via apt upgrade) installed and observed it for several months now. (After starting apport for this I updated again and nothing changed, no restart) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 2 16:10:48 2019 DistUpgraded: 2018-10-01 14:59:21,229 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:2300] Subsystem: CLEVO/KAPOK Computer GM107M [GeForce GTX 860M] [1558:2300] InstallationDate: Installed on 2017-03-18 (685 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Notebook W230SS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=907d4e48-c148-454e-aa8a-7adb74d51fb2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-01 (124 days ago) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 1 13:12:45 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dock ubuntu ui -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814387 Title: swithching workspace by scrolling on edge of Dock (left side bar) Status in xorg package in Ubuntu: New Bug description: If you position the mouse corsor on the edge of Dock and scroll, you can switch the workspace, which behaves equivalent to the scrolling on the "Show Applications" button in the corner. I've reproduced it on other Ubuntu 18 installations of friends (all 3 I tested, at least one was a fresh installation from the official iso). It is not important where Dock is or whether a window or the desktop is next to it. Program shortcuts have also no effect, because they end before it. It works with a single or 2 monitors on all instances of Dock. I use Ubuntu 18.04.1 LTS with all updates (via apt upgrade) installed and observed it for several months now. (After starting apport for this I updated again and nothing changed, no restart) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Hi Alberto, just wanted to let you know that I made a new and clean install of Ubuntu 18.10 and now switching to Intel GPU works from the start. Thank you so much for your work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Or should I maybe try to make a clean install of 18.10 as you said that it should be fixed in it and maybe I just have some stuff from 18.04 still here that does not work and I am not experienced enough to find it? I just thought that there would be a way to make it work here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Alberto, thank you for your answer. I have answerd your question on the Discord where you have also asked for testing. (https://discourse.ubuntu.com/t/call-for-testing-nvidia-prime-in-ubuntu-18-04-and-18-10/8207/4) Sorry for my lack of understanding, but I am not quite sure what the problem is. How do I install it from the Ubuntu archive? I just upgraded from 18.04 and it is still not working. Again, I am really sorry for my stupid questions. But I would love it so much to finally solve it :) Best, Stefan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Additional: If I try sudo prime-select intel, this is what I get: Info: selecting the intel profile Failed to disable unit: Unit file nvidia-fallback.service does not exist. Traceback (most recent call last): File "/usr/local/bin/prime-select", line 334, in switcher.enable_profile(arg) File "/usr/local/bin/prime-select", line 124, in enable_profile self._trigger_prime_sock() File "/usr/local/bin/prime-select", line 183, in _trigger_prime_sock sock.connect(self._prime_sock_addr) FileNotFoundError: [Errno 2] No such file or directory I don't know what this means. Best, Stefan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Hi Alberto, I was having this issues for a long time and since I am not a very experienced user I thought to just wait for 18.10 and that it would be fixed there automatically. So today I upgraded and still face the same problem. I cannot even open the Nvidia x server settings. Could you maybe help me, as this is really annoying with the bad battery-life. Should I also follow your steps in 18.10 or is it somewhat different now? I would really appreciate help :) Best, Stefan PS: I would be happy to provide further information if neccessary -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1798090] Re: Xenial update of thunderbird seems to have broken lightning/gdata provider
I am not convinced this is a ducplicate of bug #1797945. If I read that report correctly it is about upgraded Thunderbird with the external add- ons used. I *do* have both lightning and gcal provider from the Ubuntu archive (repeating from the description): xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) ** This bug is no longer a duplicate of bug 1797945 Lightning incompatible with Thunderbird 60.2.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider Status in thunderbird package in Ubuntu: Confirmed Bug description: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (1559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181010142946 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-12-27 (658 days ago) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ZH77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZH77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798090/+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 1798090] Re: Xenial update of thunderbird seems to have broken lightning/gdata provider
Above is from apt upgrade log. So both went from 1:52.9.* to 1:60.2* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider Status in thunderbird package in Ubuntu: Confirmed Bug description: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (1559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181010142946 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-12-27 (658 days ago) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ZH77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZH77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798090/+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 1798090] [NEW] Xenial update of thunderbird seems to have broken lightning/gdata provider
Public bug reported: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (1559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181010142946 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-12-27 (658 days ago) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ZH77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZH77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: thunderbird (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 thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider Status in thunderbird package in Ubuntu: New Bug description: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite
[Desktop-packages] [Bug 1793481] [NEW] package libgles1 (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1« zu überschreiben, welches auch in Paket nvidia
Public bug reported: upgrade failed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 20 10:58:27 2018 ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1« zu überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1« zu überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1793481 Title: package libgles1 (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1« zu überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist Status in libglvnd package in Ubuntu: New Bug description: upgrade failed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 20 10:58:27 2018 ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1« zu überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1« zu überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793481/+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 1414116] Re: OfficeJet G55 communication error
Hi, in the meantime I have moved the printer to a separate print server box, running a self-compiled version of hplip without issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1414116 Title: OfficeJet G55 communication error Status in hplip package in Ubuntu: Incomplete Bug description: All, printing with my OfficeJet G55 stopped working. In fact, I can setup the printer and it does start printing, but randomly stop printing somewhere within the first page, the jobs remains in the queue with status "processing". syslog (infinitely) repeats the following messages Jan 23 19:22:09 stefan hp[9864]: io/hpmud/mlc.c 760: invalid MlcCreditRequestReply: cmd=7f, result=4 Jan 23 19:22:09 stefan hp[9864]: io/hpmud/musb.c 1679: invalid MlcCreditRequest from peripheral until the job is deleted manually. I get the impression that the problem becomes worse with larger amount of data: Printing in "Draft" mode usually allow printing the full page, with "Normal" it stops at about half a page, "High quality" prints only a few lines. I tried downgrading to the 'trusty' packages which does not solve the problem. Further downgrading is not possible due to dependency issues. Any ideas are greatly appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1414116/+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 1789474] Re: Unable to boot without radeon.dpm=0
Hi, I have attached the file. ** Attachment added: "previous_boot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1789474/+attachment/5183048/+files/previous_boot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1789474 Title: Unable to boot without radeon.dpm=0 Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After selecting Ubuntu in the grub menu, I am greeted with a black screen that flashes text and the computer reboots. This keeps happening until I edit the boot parameters and add radeon.dpm=0. I tried to fix the issue by installing a newer version of the kernel and installing the Oibaf's PPA, but the issue persisted. Created a new bug without the PPA as instructed here: https://bugs.launchpad.net/ubuntu/+bug/1786647 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 19:59:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/linux/+bug/1789474/+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 1788598] Re: Xorg crash
** Changed in: xorg-server (Ubuntu) Status: Incomplete => In Progress -- 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/1788598 Title: Xorg crash Status in xorg-server package in Ubuntu: In Progress Bug description: The bug was already in the previous edition of Ubuntu (17.10) using awesome window manager. After upgrading to Ubuntu 18.04 and switched to xmonad the problem still occurs. It seems currently that the crash occurs randomly. Sometimes not at all for a day, sometimes after only a few minutes three times in a row. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: openafs .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Thu Aug 23 13:11:40 2018 DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] InstallationDate: Installed on 2017-10-10 (316 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HR002RGE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago) dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR002RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR002RGE dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788598/+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 1448985] Re: llvmpipe i386 crashes when running on qemu64 cpu
Since we no longer produce i386 images, this would be hard to reproduce.
I could imagine the issue still exists but nobody is or will care.
Essentially a difference of what features are reported via cpuid and
what actually is implemented in the cpu emulation. Will close at least
the Ubuntu side.
** Changed in: llvm-toolchain-3.6 (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: qemu (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1448985
Title:
llvmpipe i386 crashes when running on qemu64 cpu
Status in QEMU:
Incomplete
Status in llvm-toolchain-3.6 package in Ubuntu:
Won't Fix
Status in qemu package in Ubuntu:
Won't Fix
Bug description:
STEPS TO REPRODUCE:
1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all
updates (it is a host system).
2. Download one (or all) isos:
* Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM =
a8a14f1f92c1ef35dae4966a2ae1a264).
* Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM =
4a3c4b8421af51c29c84fb6f4b3fe109)
* Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM =
6ea04093b767ad6778aa245d53625612)
3. Boot one (or all) isos with as QEMU-KVM guest with the following
commands:
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware
* or from usb-creator-gtk via "Test disk" button
4. Click on "Try Ubuntu"
EXPECTED RESULTS:
ISO is booted to Unity desktop, user can test and use it.
ACTUAL RESULTS:
In 14.04 and 14.10 guests can see empty purple desktop or purple desktop
with two shortcuts ("Examples" and "Install Ubuntu ...").
15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740).
The reason for this is that unity requires gfx acceleration which is
done via llvmpipe on non accelerated gfx chipsets (as VMs use by
default). The error message is hidden away but is:
LLVM ERROR: Do not know how to split the result of this operator!
The cause is that KVM VMs by default use the qemu64 cpu model which
seems to be inconsistent in some way between claimed features and
actual results when using those features. A work-around for running
i386 isos is to use a cpu model like core2duo or kvm64.
This bug should be confirmed and fixed.
Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1448985/+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 1789474] [NEW] Unable to boot without radeon.dpm=0
Public bug reported: After selecting Ubuntu in the grub menu, I am greeted with a black screen that flashes text and the computer reboots. This keeps happening until I edit the boot parameters and add radeon.dpm=0. I tried to fix the issue by installing a newer version of the kernel and installing the Oibaf's PPA, but the issue persisted. Created a new bug without the PPA as instructed here: https://bugs.launchpad.net/ubuntu/+bug/1786647 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 19:59:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1789474 Title: Unable to boot without radeon.dpm=0 Status in gnome-shell package in Ubuntu: New Bug description: After selecting Ubuntu in the grub menu, I am greeted with a black screen that flashes text and the computer reboots. This keeps happening until I edit the boot parameters and add radeon.dpm=0. I tried to fix the issue by installing a newer version of the kernel and installing the Oibaf's PPA, but the issue persisted. Created a new bug without the PPA as instructed here: https://bugs.launchpad.net/ubuntu/+bug/1786647 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 19:59:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1789474/+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 1788235] Re: lirc broken on 18.04
I've tried the workaround, and it worked for me as described. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Confirmed Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+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 1788235] Re: lirc broken on 18.04
I can confirm the issue on a recently fresh installed Ubuntu Server 18.04. The goal was to transform the installation to a HTPC running kodi and tvheadend (hts). Here are some links to guys who had the same experience and offer a workaround until the fix of the package. Same experience: https://forum.kodi.tv/showthread.php?tid=333904 Workaround: https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-ubuntu-18-04/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Confirmed Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+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 1754458] Re: nm-applet symbol not displayed on mate (18.04)
** Also affects: mate-indicator-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) Status in ubuntu-mate: Confirmed Status in indicator-application package in Ubuntu: New Status in mate-indicator-applet package in Ubuntu: New Status in network-manager-applet package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: New Bug description: After upgrading to Ubuntu 18.04, the network manager applet symbol isn't displayed any longer. The other functionality (asking for credentials) is working. I also see other symbols. aptitude show network-manager-gnome Paket: network-manager-gnome Version: 1.8.10-2ubuntu1 Neu: ja Zustand: Installiert stdout/stderr: Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module" ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/6: No ModemManager support (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is not available for modem at /org/freedesktop/ModemManager1/Modem/6 (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on widget which has a parent ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 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 CurrentDesktop: MATE Date: Thu Mar 8 21:27:56 2018 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) WpaSupplicantLog: nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+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 1788796] Re: Xorg crashed with SIGSEGV in miPointerSetPosition()
*** This bug is a duplicate of bug 1762219 *** https://bugs.launchpad.net/bugs/1762219 The bug #1762219 seems to not exist. -- 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/1788796 Title: Xorg crashed with SIGSEGV in miPointerSetPosition() Status in xorg-server package in Ubuntu: New Bug description: related to #994921 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: openafs .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Mon Aug 20 11:11:17 2018 DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1523633505 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] InstallationDate: Installed on 2017-10-10 (317 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HR002RGE ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/stefan ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f7c36d6de16:mov(%rax),%rax PC (0x7f7c36d6de16) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/drivers/modesetting_drv.so ?? () ?? () ?? () miPointerSetPosition () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: Upgraded to bionic on 2018-07-06 (48 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR002RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR002RGE dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788796/+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 1788598] Re: Xorg crash
Thanks for getting back on this so fast. I followed the proposed steps: 1. `ubuntu-bug _usr_lib_xorg_Xorg.1000.crash` reported the bug, but closed silently. I did not get a new bug ID. Where can I find it? 2. On that page I can find crashes from 2017, but none from after the upgrade to Ubuntu 18.04. 3. I followed the steps and was able to use `sudo apport-cli -c _usr_lib_xorg_Xorg.1000.crash` to upload the crash as a bug here: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788796 -- 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/1788598 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug was already in the previous edition of Ubuntu (17.10) using awesome window manager. After upgrading to Ubuntu 18.04 and switched to xmonad the problem still occurs. It seems currently that the crash occurs randomly. Sometimes not at all for a day, sometimes after only a few minutes three times in a row. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: openafs .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Thu Aug 23 13:11:40 2018 DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] InstallationDate: Installed on 2017-10-10 (316 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HR002RGE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago) dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR002RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR002RGE dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788598/+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 1788598] Re: Xorg crash
** Attachment added: "apport's /var/crash/_usr_lib_xorg_Xorg.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1788598/+attachment/5179697/+files/_usr_lib_xorg_Xorg.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1788598 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: The bug was already in the previous edition of Ubuntu (17.10) using awesome window manager. After upgrading to Ubuntu 18.04 and switched to xmonad the problem still occurs. It seems currently that the crash occurs randomly. Sometimes not at all for a day, sometimes after only a few minutes three times in a row. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: openafs .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Thu Aug 23 13:11:40 2018 DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] InstallationDate: Installed on 2017-10-10 (316 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HR002RGE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago) dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR002RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR002RGE dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1788598/+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 1788598] [NEW] Xorg crash
Public bug reported: The bug was already in the previous edition of Ubuntu (17.10) using awesome window manager. After upgrading to Ubuntu 18.04 and switched to xmonad the problem still occurs. It seems currently that the crash occurs randomly. Sometimes not at all for a day, sometimes after only a few minutes three times in a row. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: openafs .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Thu Aug 23 13:11:40 2018 DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] InstallationDate: Installed on 2017-10-10 (316 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HR002RGE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago) dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR002RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR002RGE dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu ** Attachment added: "apport log file" https://bugs.launchpad.net/bugs/1788598/+attachment/5179678/+files/apport.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1788598 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: The bug was already in the previous edition of Ubuntu (17.10) using awesome window manager. After upgrading to Ubuntu 18.04 and switched to xmonad the problem still occurs. It seems currently that the crash occurs randomly. Sometimes not at all for a day, sometimes after only a few minutes three times in a row. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: openafs .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Thu Aug 23 13:11:40 2018 DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus:
[Desktop-packages] [Bug 1788598] Re: Xorg crash
** Attachment removed: "apport's /var/crash/_usr_lib_xorg_Xorg.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1788598/+attachment/5179697/+files/_usr_lib_xorg_Xorg.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1788598 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: The bug was already in the previous edition of Ubuntu (17.10) using awesome window manager. After upgrading to Ubuntu 18.04 and switched to xmonad the problem still occurs. It seems currently that the crash occurs randomly. Sometimes not at all for a day, sometimes after only a few minutes three times in a row. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: openafs .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Thu Aug 23 13:11:40 2018 DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] InstallationDate: Installed on 2017-10-10 (316 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HR002RGE ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago) dmi.bios.date: 05/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR002RGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR002RGE dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1788598/+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
