[Desktop-packages] [Bug 1874197] Re: [nvidia] gnome-control-center crashed with SIGSEGV in _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit() from gtk_css_node_reposition() from g
** Summary changed: - [nvidia] gnome-control-center crashed with SIGSEGV in _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit() from gtk_css_node_reposition() from gtk_css_node_set_parent() + [nvidia] gnome-control-center crashed with SIGSEGV in _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit() from gtk_css_node_reposition() from gtk_css_node_set_parent() [when changing fractional scaling settings] ** Tags added: xrandr-scaling -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874197 Title: [nvidia] gnome-control-center crashed with SIGSEGV in _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit() from gtk_css_node_reposition() from gtk_css_node_set_parent() [when changing fractional scaling settings] Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.36.1-1ubuntu5, the problem page at https://errors.ubuntu.com/problem/9656f23d90d503b639e655ad762264d522f4f8d3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874197/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1876031] [NEW] When enable "Extended Error Log Support" , it could not boot into OS
Public bug reported: Use 3 version 18.04,19.04 and 20.04 Ubuntu OS, and enable "Extended Error Log Support" with kernel 5.4.35, 5.5.7, and 5.6.6. BUT after update kernel, it could not boot into OS. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1876031 Title: When enable "Extended Error Log Support" , it could not boot into OS Status in evince package in Ubuntu: New Bug description: Use 3 version 18.04,19.04 and 20.04 Ubuntu OS, and enable "Extended Error Log Support" with kernel 5.4.35, 5.5.7, and 5.6.6. BUT after update kernel, it could not boot into OS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1876031/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
Yes, #3 sounds sensible. it is worth having a try. -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 837794] Re: Failing to Restart after submitting a crash report
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/837794 Title: Failing to Restart after submitting a crash report Status in firefox package in Ubuntu: Expired Bug description: Firefox 6.0 from http://ppa.launchpad.net/mozillateam/firefox-stable/ubuntu maverick main Ubuntu 10.10 When Firefox crashes, the crash report tool automatically loads. I have selected Firefox to restart upon completion of submitting the crash report The crash report submits successfully, the crash report tool closes, but Firefox does not restart I have to restart Firefox manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/837794/+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 802366] Re: FF: uses 60% CPU just to show the "Download" progress
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/802366 Title: FF: uses 60% CPU just to show the "Download" progress Status in firefox package in Ubuntu: Expired Bug description: To reproduce: 1. Fresh Firefox 2. Find a big file with unknown size 3. Right-click "Save As" 4. The download window appears 5. Firefox is now using 60% CPU just to update that Gtk Progress bar Ideally the CPU load should be no more than for wget doing the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/802366/+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 1074452] Re: Can't reload "He's dead, Jim" web page with right-click
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1074452 Title: Can't reload "He's dead, Jim" web page with right-click Status in chromium-browser package in Ubuntu: Expired Bug description: More than half of my tabs end up with the message "He's dead, Jim" at any given time with Chromium-browser. Regular pages allow a reload from a menu that is brought up with a right-click. No such menu pops up when right clicking on a "He's dead" page. Steps to produce: use chromium-browser a few minutes until a "He's dead, Jim" page pops up, right click -- no menu The same menu that is brought up on a regular page with a right click ought to also be brought up on a "He's dead" page. Please add the menu to "He's dead" pages. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 2 20:25:43 2012 Desktop-Session: DESKTOP_SESSION = Lubuntu XDG_CONFIG_DIRS = /etc/xdg/lubuntu/:/etc/xdg/xdg-Lubuntu:/etc/xdg XDG_DATA_DIRS = /etc/xdg/lubuntu:/usr/share/Lubuntu:/usr/local/share/:/usr/share/:/usr/share:/usr/share/gdm:/var/lib/menu-xdg DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda2 ext4 73G 6.9G 62G 10% /\nudev devtmpfs 474M 4.0K 474M 1% /dev\ntmpfs tmpfs 193M 868K 192M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 483M 340K 482M 1% /run/shm\nnone tmpfs 100M 16K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda24.7M 230K 4.4M5% /\nudev 119K 539 118K1% /dev\ntmpfs 121K 454 121K1% /run\nnone 121K 4 121K1% /run/lock\nnone 121K 7 121K1% /run/shm\nnone 121K12 121K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2012-10-16 (17 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121015) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme = b'' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1074452/+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 847708] Re: "Restart Firefox" button in crash dialog does not restart Firefox but just exits instead
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/847708 Title: "Restart Firefox" button in crash dialog does not restart Firefox but just exits instead Status in firefox package in Ubuntu: Expired Bug description: When Firefox crashes, the crash dialog (allowing submission of a report upstream) has a "Restart Firefox" button. Clicking that button does not, as far as I can tell, restart Firefox; instead, the crash dialog closes, and I have to restart Firefox myself. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 6.0.2+build2+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic-pae 2.6.38.8 Uname: Linux 2.6.38-11-generic-pae i686 Architecture: i386 Date: Mon Sep 12 12:01:33 2011 FirefoxPackages: firefox 6.0.2+build2+nobinonly-0ubuntu0.11.04.1 flashplugin-installer N/A adobe-flashplugin 10.3.183.4-0natty1 icedtea-plugin N/A ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_US.UTF-8 LC_MESSAGES=en_GB.utf8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to natty on 2011-01-18 (236 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/847708/+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 889059] Re: Regression: Firefox enforces middlemouse.contentLoadURL to false.
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/889059 Title: Regression: Firefox enforces middlemouse.contentLoadURL to false. Status in firefox package in Ubuntu: Expired Bug description: When I've upgraded my ubuntu and got firefox 7.0.1 I've unexpectedly lost the possibility to paste URLs directly into browser window. That possibility is more than very useful as I don't have to do lot of things - exactly to load some URL into current non-empty tab I have to: 1) select URL; 2) press Ctrl+C; 3) click on URL line in browser; 4) select all in there; 5) press Ctrl+V; 6) press 'Enter'. With that possibility it's very-very simple: 1) select URL; 2) middle-click in browser window - yes, that's all. And now I cannot do that because config variable middlemouse.contentLoadURL changed it's default to false (and I think it's ubuntu-specific default, the same version 7.0.1 in debian-testing have it true as it always been) and it's even worse - even when I open about:config and toggle it, it works as it should be but as soon I close firefox and start it again that value is reset to false again and that means I should set it manually each time I start firefox! I've fixed that weird bug by downgrading firefox to version from natty. Fix it back, please! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/889059/+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 954311] Re: Default zoom applied to Elements panel's icons but not code, breaking arrowheads' function
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/954311 Title: Default zoom applied to Elements panel's icons but not code, breaking arrowheads' function Status in chromium-browser package in Ubuntu: Expired Bug description: Steps to reproduce: 1. Start Chromium with new (temporary) profile 2. Go to chrome://settings/advanced 3. Set Page zoom to 500% 4. For any page with content, open the Elements panel 5. Try to expand/shrink elements What happens: With the expanding/shrinking arrowheads zoomed 500%, but with code still at default zoom, it's extremely difficult to hit the arrowhead in the right spot to expand/shrink elements. Depending on the selected Page zoom level the actual hotspot may even fall completely outside the arrowhead graphic (to the left from it). What I expect to happen: For the arrowheads and the code to both follow the Page zoom setting or ignore it, and either way, for the arrowhead graphic to function as the actual hotspot for expanding/shrinking elements. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 17.0.963.79~r125985-0ubuntu1 Uname: Linux 3.3.0-030300rc4-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: 09ae689090491ca53449589269e4bfd8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Tue Mar 13 20:18:13 2012 Desktop-Session: DESKTOP_SESSION = ubuntu-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2012-03-13 (0 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/954311/+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 963226] Re: firefox always shows tab bar
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
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/963226
Title:
firefox always shows tab bar
Status in firefox package in Ubuntu:
Expired
Bug description:
I have "Always show the tab bar" turned off in preferences, which
should make the tab bar disappear when there is only one tab. However,
more than half the time Firefox chooses to display the tab bar anyway.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: firefox 11.0+build1-0ubuntu0.11.10.1
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: charles1288 F pulseaudio
/dev/snd/controlC0: charles1288 F pulseaudio
BuildID: 20120310010316
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf5e0 irq 44'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,104d4600,0014'
Controls : 14
Simple ctrls : 9
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xf004 irq 45'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,104d4600,00100200'
Controls : 4
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Channel: release
Date: Fri Mar 23 09:49:49 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: ShareMeNot - ID=shareme...@franziroesner.com,
Version=1.11, minVersion=3.6, maxVersion=10.*, Location=app-profile,
Type=extension, Active=Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric
2
Profiles: Profile0 (Default) - LastVersion=11.0/20120310010316 (Running)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to oneiric on 2011-10-05 (170 days ago)
dmi.bios.date: 10/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1140Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEC390X:pvrC607C15E:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCEC390X
dmi.product.version: C607C15E
dmi.sys.vendor: Sony Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/963226/+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 943443] Re: Freezes up then I reboot It will come but it's slow doing anything else
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/943443 Title: Freezes up then I reboot It will come but it's slow doing anything else Status in firefox package in Ubuntu: Expired Bug description: This started 3-4 days ago .I'm 72 years old and don't know a lot about a PC I have had good luck with this program you boy's did a good job coming with this .You asked what package this happen in.I use Firefox ;I just turn on my PC.I use Charter for my intenet they keep changing the speed on the internet,they say it is fast.As for the speed all I know is it is faster than it used to be.Sorry I don't know more to tell you .Thanks and God Bless. PS If you need to call me my Phone number is 865-5771394 .My address is 635 Mize Rd ,Seymour Tn 37865 once again Thanks . ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.3 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic i686 Architecture: i386 Date: Wed Feb 29 11:42:30 2012 FirefoxPackages: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.3 flashplugin-installer N/A adobe-flashplugin N/A icedtea-plugin N/A InstallationMedia: Pinguy OS 11.04.1 32-Bit - Release i386 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/943443/+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 899556] Re: Chromium doesn't block third-party cookies properly
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/899556 Title: Chromium doesn't block third-party cookies properly Status in chromium-browser package in Ubuntu: Expired Bug description: If I select "block third-party cookies" in the Chromium configuration, and I am logged into Facebook, and I visit a webpage with an embedded Facebook applet, I can see my friends in this applet. If I block cookies completely, I see only random people in the applet. I deduce from this that the blocking of third-party cookies is not properly working in Chromium. I use Lubuntu 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/899556/+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 1097125] Re: chromium-browser has min/max/close buttons at upper right
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1097125 Title: chromium-browser has min/max/close buttons at upper right Status in chromium-browser package in Ubuntu: Expired Bug description: In prior releases of chromium-browser, the minimize/maximize/close cluster of 3 buttons were always at the upper left as per Ubuntu standard layout. In Ubuntu 12.10, for some reason, this 3 button cluster has been moved to the upper right. It is disturbing. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 ChromiumPrefs: can't open profile /home/peterzay/.config/chromium/Default/Preferences Date: Mon Jan 7 22:45:02 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-01-04 (3 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1097125/+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 1073456] Re: Chat for Google extension unable to change window titles
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1073456 Title: Chat for Google extension unable to change window titles Status in chromium-browser package in Ubuntu: Expired Bug description: as described in : http://productforums.google.com/forum/#!searchin/chat/Chat$20windows$20not$20showing$20the$20expected$20titles/chat/aCCpmPYi00s/x8rv5LUvBLQJ when using the Google Chrome Extension for Google Chat installed on Chromium (as provided by Ubuntu 12.10 version 22.0.1229.94~r161065-0ubuntu1), the window titles are not getting updated to the expected values (Chat for the main window, and each user name for the private chats). to reproduce : 1) install chromium 2) install chat for google (https://chrome.google.com/webstore/detail/chat-for-google/nckgahadagoaajjgafhacjanaoiihapd?utm_source=chrome-ntp-icon) 3) click on the icon and login to google chat services (using a gmail or google for apps account) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1073456/+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 1269092] Re: "Aw Snap!" from chromium-browser v31 because needs updated chromium-codecs-ffmpeg
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1269092 Title: "Aw Snap!" from chromium-browser v31 because needs updated chromium- codecs-ffmpeg Status in chromium-browser package in Ubuntu: Expired Bug description: I'm on an ARM system, but I'm guessing this could happen on x86 or x64 too. I start with a stock raring (13.04) install that does not have the raring-updates debian package location in /etc/apt/sources.list. I install xubuntu-desktop and chromium-browser. The last package also installs a chromium-codecs-ffmpeg package. Without the updates I get version 25 of the browser. I want the latest stable (v31), but upgrading some packages breaks my graphics driver (hidden in a mesa library I heard). So I add the raring-updates location and only upgrade "chromium-browser". This also grabbed the chromium language package, but it did not upgrade chromium-codecs-ffmpeg. Afterwards if I try to view google.com, about a second after the page loads I get an "Aw Snap!" and the chromium log has this. ... [24337:24337:0113/180942:VERBOSE1:ffmpeg_stubs.cc(467)] Couldn't load av_frame_unref, dlerror() says: [24337:24337:0113/180942:VERBOSE1:ffmpeg_stubs.cc(472)] Couldn't load av_frame_free, dlerror() says: /usr/lib/chromium-browser/libffmpegsumo.so: undefined symbol: av_frame_free [24337:24337:0113/180942:VERBOSE1:ffmpeg_stubs.cc(597)] Couldn't load av_buffer_create, dlerror() says: /usr/lib/chromium-browser/libffmpegsumo.so: undefined symbol: av_buffer_create [24337:24337:0113/180942:VERBOSE1:ffmpeg_stubs.cc(607)] Couldn't load av_buffer_get_opaque, dlerror() says: /usr/lib/chromium-browser/libffmpegsumo.so: undefined symbol: av_buffer_get_opaque [24337:24339:0113/180942:VERBOSE1:ipc_sync_channel.cc(385)] Canceling pending sends [24337:24337:0113/180942:VERBOSE1:ipc_sync_channel.cc(385)] Canceling pending sends ... But if I manually also upgrade chromium-codecs-ffmpeg to the latest version I can view google.com fine. I assume this means there is a missing dependency for the newer version of the ffmpeg codecs pack in the current chromium-browser package. I've tried to grab dependency information for chromium-browser below. $ apt-cache showpkg chromium-browser ... Dependencies: 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 - gconf-service (0 (null)) libasound2 (2 1.0.16) libatk1.0-0 (2 1.12.4) libc6 (2 2.15) libcairo2 (2 1.6.0) libcomerr2 (2 1.01) libcups2 (2 1.4.0) libdbus-1-3 (2 1.2.14) libexpat1 (2 2.0.1) libfontconfig1 (2 2.9.0) libfreetype6 (2 2.3.9) libgcc1 (2 1:4.4.0) libgconf-2-4 (2 2.31.1) libgcrypt11 (2 1.4.5) libgdk-pixbuf2.0-0 (2 2.22.0) libglib2.0-0 (2 2.35.9) libgnome-keyring0 (2 2.22.2) libgnutls26 (2 2.12.17-0) libgssapi-krb5-2 (2 1.6.dfsg.2) libgtk2.0-0 (2 2.24.0) libk5crypto3 (2 1.6.dfsg.2) libkrb5-3 (2 1.6.dfsg.2) libnspr4 (18 2:4.9-2~) libnspr4-0d (2 1.8.0.10) libnss3 (2 2:3.14.3) libpango1.0-0 (2 1.22.0) libstdc++6 (2 4.6) libudev1 (2 183) libx11-6 (2 2:1.4.99.1) libxcomposite1 (2 1:0.3-1) libxcursor1 (4 1.1.2) libxdamage1 (2 1:1.1) libxext6 (0 (null)) libxfixes3 (0 (null)) libxi6 (2 2:1.2.99.4) libxrender1 (0 (null)) libxss1 (0 (null)) libxtst6 (0 (null)) zlib1g (2 1:1.1.4) xdg-utils (0 (null)) chromium-codecs-ffmpeg-extra (18 0.6) chromium-codecs-ffmpeg (2 0.6) dpkg (2 1.15.6) webaccounts-chromium-extension (0 (null)) unity-chromium-extension (0 (null)) chromium-browser-l10n (0 (null)) chromium-browser-inspector (0 (null)) chromium-browser-inspector (0 (null)) I'm not sure how to read the values listed for the version required of chromium-codecs-ffmpeg (0.6?), but the package that I end up with after the upgrade looks to be version 31 like the browser proper, and I'd guess they should be in sync with each other. $ apt-cache showpkg chromium-codecs-ffmpeg Package: chromium-codecs-ffmpeg Versions: 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 (/var/lib/apt/lists/ports.ubuntu.com_dists_raring-updates_universe_binary-armhf_Packages) (/var/lib/dpkg/status) Description Language: File: /var/lib/apt/lists/ports.ubuntu.com_dists_raring_universe_binary-armhf_Packages MD5: e9d73e814a08298b16cf36187c847fde Description Language: en File: /var/lib/apt/lists/ports.ubuntu.com_dists_raring_universe_i18n_Translation-en MD5: e9d73e814a08298b16cf36187c847fde 25.0.1364.160-0ubuntu3 (/var/lib/apt/lists/ports.ubuntu.com_dists_raring_universe_binary-armhf_Packages) Description Language: File: /var/lib/apt/lists/ports.ubuntu.com_dists_raring_universe_binary-armhf_Packages
[Desktop-packages] [Bug 1875745] Re: Waffle button on dock doesn't do anything in wayland session
Please remember to run: apport-collect 1875745 We need a new collection because the bug was assigned to the wrong package the first time, so it attached the wrong files. -- 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/1875745 Title: Waffle button on dock doesn't do anything in wayland session Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using the waffle button menu on the dock when in a wayland session nothing happens ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 21:14:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 500 [8086:2212] InstallationDate: Installed on 2020-04-23 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper Ezbook X3 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03 dmi.board.asset.tag: Default string dmi.board.name: P313P dmi.board.vendor: Jumper dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Ezbook dmi.product.name: Ezbook X3 dmi.product.sku: 1809100 dmi.product.version: Default string dmi.sys.vendor: Jumper version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875745/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
I am concerned about this: Jack: Installed - Yes (/usr/bin/jackd) Running - No If jackd was already running when pulseaudio tried to start then it might have failed to open the ALSA devices. Please uninstall jackd if you can, and the reboot. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1875964] Re: Happened after apt upgrade
Normally I would ask you to explain what the exact problem is. But in this case it seems you have the 'oibaf' PPA installed, which is not supported and is known to be buggy. Please remove the oibaf PPA from your system and then open new bugs for any problems you still have. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1875964 Title: Happened after apt upgrade Status in xorg package in Ubuntu: Invalid Bug description: I likely had already previously done a bunch of upgrades without restarting (even though the file that indicated a restart was required existed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 23:48:16 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (prog-if 00 [VGA controller]) Subsystem: Dell Mars XTX [Radeon HD 8790M] [1028:05be] InstallationDate: Installed on 2018-05-16 (714 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E6540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=ae4fb2b2-cc1b-48f5-a617-95f1ef6e9418 ro nomodeset splash radeon.modeset=0 radeon.cik_support=0 radeon.ci_support=0 amdgpu.si_support=1 amdgpu.cik=1 amdgpu.dc=1 amdgpu.dpm=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2004261830.fd7f37~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004290730.35ee6b~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2004290730.35ee6b~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0+git2004151930.384539~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git2004211930.846b53~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git2004030730.5444ca~oibaf~b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875964/+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 1875966] Re: Dock settings can not be set to only one monitor
*** This bug is a duplicate of bug 1866088 *** https://bugs.launchpad.net/bugs/1866088 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1866088, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1866088 Problems with the Dock setting of "Show on" in the Appearance tab -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875966 Title: Dock settings can not be set to only one monitor Status in gnome-control-center package in Ubuntu: New Bug description: In the gnome-settings panel it is not possible to set the dock to being displayed on only one monitor after the option "all screens" has been selected once. After selecting a specific monitor the setting immideately buggs back to "all screens". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 22:48:55 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-11-07 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875966/+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 1730612] Re: Enable Remote desktop feature during build
Prerequisites: bug 1802533, bug 1802614 -- 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/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: Triaged Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+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 1875925] Re: gnome-remote-desktop has no settings entry in gnome-control-center
*** This bug is a duplicate of bug 1730612 *** https://bugs.launchpad.net/bugs/1730612 Thanks for the bug report. It seems we already have bug 1730612 requesting this feature where it would be implemented. So this is a duplicate of bug 1730612. ** This bug is no longer a duplicate of bug 1802614 [MIR] gnome-remote-desktop ** This bug has been marked a duplicate of bug 1730612 Enable Remote desktop feature during build -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875925 Title: gnome-remote-desktop has no settings entry in gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I try to use VNC with gnome-remote-desktop but they do not appear in settings https://wiki.gnome.org/Projects/Mutter/RemoteDesktop#Enabling https://gitlab.gnome.org/jadahl/gnome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875925/+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 1875957] Re: Random freezes for 1 second
Weirdly your kernel is using the nvidia-440 driver, but Xorg is using the 'modeset' driver. That might be the problem. Certainly it's what I would try to fix first... Can you try uninstalling and reinstalling the Nvidia driver? ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1875957 Title: Random freezes for 1 second Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The gnome DE and some programs such as Telegram randomly freeze for ca a second and then recover again. This occurs ~5 times every minute. There are however applications which do work flawlessly, such as overwatch over lutris. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 22:16:49 2020 DistUpgraded: 2020-04-24 10:02:52,848 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] InstallationDate: Installed on 2019-11-07 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=45a49275-be6c-418c-86a5-c57794b70427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1875957/+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 1875925] Re: gnome-remote-desktop has no settings entry in gnome-control-center
*** This bug is a duplicate of bug 1802614 *** https://bugs.launchpad.net/bugs/1802614 I don't think this is a bug in gnome-control-center. The option would be hidden while we don't release the feature. So that is covered by bug 1802614. ** This bug has been marked a duplicate of bug 1802614 [MIR] gnome-remote-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875925 Title: gnome-remote-desktop has no settings entry in gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I try to use VNC with gnome-remote-desktop but they do not appear in settings https://wiki.gnome.org/Projects/Mutter/RemoteDesktop#Enabling https://gitlab.gnome.org/jadahl/gnome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875925/+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 1875908] Re: Fractional scaling does not work in Wayland session
*** This bug is a duplicate of bug 1871864 *** https://bugs.launchpad.net/bugs/1871864 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1871864, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1871864 Toggle "Fractional Scaling" does nothing on wayland -- 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/1875908 Title: Fractional scaling does not work in Wayland session Status in xorg-server package in Ubuntu: New Bug description: Toggle the Fractional Zoom slider. In any position, only 100% and 200% are available. On an X11 session, everything works correctly. Checked on 2 systems (Laptop and installation in VirtualBox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875908/+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 1875899] Re: cannot detect VGA but in first install and live session it can detect
The problem is that you have the 'nomodeset' kernel parameter, so the graphics driver won't work. Please: 1. Remove the 'nomodeset' kernel parameter from /etc/default/grub 2. sudo update-grub 3. sudo reboot and if you have any further problems after that then open a new bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- 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/1875899 Title: cannot detect VGA but in first install and live session it can detect Status in Ubuntu: Invalid Bug description: cannot detect VGA but in first install and live session it can detect ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 21:04:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 4291HD1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=b30f4199-d472-4c2f-9fe9-a410f286058a ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291HD1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4291HD1:pvrThinkPadX220:rvnLENOVO:rn4291HD1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 4291HD1 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875899/+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 1875912] Re: Selected audio output always USB device as default, but no control
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1875912 Title: Selected audio output always USB device as default, but no control Status in pulseaudio package in Ubuntu: Incomplete Bug description: Upon login in Ubuntu 20.04, the selected audio device will always be my USB device (in this case a Schiit Modi 3 DAC). However, the audio will be played from my motherboard's default line-out through my desktop speakers (the desired and last used audio device). The issue then is that gnome and pulse audio seem to believe that the selected device is the USB DAC, and the volume controls no longer have any affect on the output volume. To regain control of the volume, I have to open up the Settings panel and select the Line-out device. This happens on every boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 10:49:08 2020 InstallationDate: Installed on 2019-10-31 (180 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-29 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-04-29T10:34:28.863415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875912/+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 1875292] Re: Double click on window titlebar pass through to what's below
** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1875292 Title: Double click on window titlebar pass through to what's below Status in mutter package in Ubuntu: New Bug description: Hi, This is simple to reproduce and I experienced this also on 19.10. First, make sure you have enabled "double-click on top bar of window to minimize" feature, I'm using that because its easy and fast for me to minimize the window. 1. Make sure you have any folder (like home) or file on desktop but in Big size and Top-Center location of desktop (I have many folders and files which are on top-center location so when I click double-click on topbar of window, issue appears) 2. Open Files for example 3. Double-click on top bar of window to minimize it 4. Observe issue (make sure you double-clicked on top bar but to be folder or file behind it exactly.. because thats the point, when folder or file is behind that bar where you perform double-click, it will minimize the window + open that folder or file Actual result: Window minimized + folder opened Expected result: Just window minimized ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:17:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875292/+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 1875892] Re: Display Interfaces Not Detected
Your mini-DP and HDMI ports are probably connected to the Nvidia GPU so this is something of a bug in the Nvidia driver, or a misconfiguration. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (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/1875892 Title: [nvidia][Lenovo P51] Mini-DP and HDMI ports are missing Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: My laptop (Lenovo ThinkPad P51) has 2 display interfaces. One mini-dp and one HDMI. But none of them is shown in xrandr, and my external display connected through mini-dp is not detected also. When I used LiveCD, the external monitor works normally. The above situation happens when my boot from SSD with the fully-installed system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 21:37:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics P630 [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics P630 [17aa:224d] Subsystem: Lenovo GM206GLM [Quadro M2200 Mobile] [17aa:224d] InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=05a90498-4cfc-4877-8f08-b096eb36e91b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET77W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET77W(1.51):bd02/10/2020:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1875892/+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 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]
** Description changed:
+ [Impact]
+
+ Wayland apps fail to start in focal with:
+
+ error 7: failed to import supplied dmabufs: Unsupported buffer format
+ 808669784
+
+ [Test Case]
+
+ Just run: es2gears_wayland
+
+ [Regression Potential]
+
+ Medium/unknown. The fix is quite new.
+
+ [Other Info]
+
When attempting to run es2gears_wayland against GNOME Shell, it fails
with:
EGL_VERSION = 1.5
- vertex shader info:
- fragment shader info:
- info:
+ vertex shader info:
+ fragment shader info:
+ info:
[destroyed object]: error 7: failed to import supplied dmabufs: Unsupported
buffer format 808669784
The full wayland protocol trace is:
[3104432.914] -> wl_display@1.get_registry(new id wl_registry@2)
[3104432.972] -> wl_disp...@1.sync(new id wl_callback@3)
[3104433.139] wl_display@1.delete_id(3)
[3104433.175] wl_registry@2.global(1, "wl_drm", 2)
[3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
[3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id
[unknown]@4)
[3104433.285] wl_registry@2.global(3, "wl_shm", 1)
[3104433.316] wl_registry@2.global(4, "wl_output", 2)
[3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
[3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
[3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager",
1)
[3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
[3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
[3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
[3104433.513] wl_registry@2.global(11, "wl_shell", 1)
[3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
[3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
[3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
[3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
[3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
[3104433.699] wl_registry@2.global(16, "wl_seat", 5)
[3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
[3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
[3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
[3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
[3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
[3104433.875] wl_registry@2.global(22,
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
[3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
[3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
[3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
[3104433.991] wl_callb...@3.done(3421)
[3104436.266] -> wl_display@1.get_registry(new id wl_registry@3)
[3104436.279] -> wl_disp...@1.sync(new id wl_callback@6)
[3104436.647] wl_display@1.delete_id(6)
[3104436.672] wl_registry@3.global(1, "wl_drm", 2)
[3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
[3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
[3104436.780] wl_registry@3.global(3, "wl_shm", 1)
[3104436.790] wl_registry@3.global(4, "wl_output", 2)
[3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
[3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
[3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager",
1)
[3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
[3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
[3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
[3104436.925] wl_registry@3.global(11, "wl_shell", 1)
[3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
[3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
[3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
[3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
[3104436.990] wl_registry@3.global(16, "wl_seat", 5)
[3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
[3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
[3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
[3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
[3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
[3104437.066] -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id
[unknown]@8)
[3104437.083] wl_registry@3.global(22,
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
[3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1)
[3104437.111] wl_registry@3.global(24, "gtk_text_input_manager", 1)
[3104437.125] wl_registry@3.global(26, "wl_eglstream_controller", 1)
[3104437.140] wl_callb...@6.done(3421)
[3104437.146] -> wl_disp...@1.sync(new id wl_callback@6)
[3104437.333] wl_display@1.delete_id(6)
[3104437.339] wl_drm@7.device("/dev/dri/card0")
[3104437.408] -> wl_drm@7.authenticate(1)
[3104437.413] wl_drm@7.format(808669761)
[3104437.438] wl_drm@7.format(808669784)
[Desktop-packages] [Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
At least in Firefox you can use Ctrl + L to access a location -- 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/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Invalid Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+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 1875243] Re: Unexpressed dependency between gnome-control-center and mutter-common
** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/977 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875243 Title: Unexpressed dependency between gnome-control-center and mutter-common Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: Ubuntu Release: 20.04 Package Version: 1:3.36.1-1ubuntu5 Steps to reproduce: Pre-requisite: Ubuntu system with gnome-control-center installed but not mutter-common (ex: Regolith 1.4/20.04) 1. launch gnome-control-center from terminal 2. navigate to display tab Observed behaviour: (gnome-control-center:54513): GLib-GIO-ERROR **: 13:49:43.782: Settings schema 'org.gnome.mutter' is not installed (core dumped) Expected behaviour: no crash Once I install the package mutter-common, the crash does not occur and I am able to use gnome-control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1875243/+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 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
I'm afraid I do have to add my voice to this particular complaint as most packages I install with snap seem to have fundamental problems accessing the file system however it's configured with multiple mount points, sim links etc. I've already removed many snap apps and reinstalled with apt which is much more reliable. Not being able to find a file path in Chromium or even be able to type in the path when you want to upload a file is a bit ridiculous to be honest. -- 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/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Invalid Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+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 1874856] Re: Unwanted mouse trail
Hmm, sounds like we still don't accelerated support for GTX 10 series (Pascal) chips in nouveau. So that's an inconclusive test. Thanks though. ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1874856 Title: Unwanted mouse trail Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Moving mouse leaves a trail of squares for a few seconds on a fresh 20.04 install. This happens with proprietary nvidia 440 drivers as well as nouveau on my GeFOrce GTX 1050 mobile. Could be related to my submission https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1874819 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 17:59:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1a10] InstallationDate: Installed on 2020-04-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. X580VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580VD.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X580VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Apr 24 16:45:55 2020 xserver.configfile: default xserver.errors: NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver NVIDIA(G0): Failing initialization of X screen systemd-logind: failed to release device: Device not taken systemd-logind: failed to release device: Device not taken modeset(0): failed to set mode: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874856/+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 1874856] Re: Unwanted mouse trail
Though that contradicts what you said at the top of the bug: > This happens with proprietary nvidia 440 drivers as well as nouveau on my GeFOrce GTX 1050 mobile. Can you please clarify which is true? ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1874856 Title: Unwanted mouse trail Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Moving mouse leaves a trail of squares for a few seconds on a fresh 20.04 install. This happens with proprietary nvidia 440 drivers as well as nouveau on my GeFOrce GTX 1050 mobile. Could be related to my submission https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1874819 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 17:59:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1a10] InstallationDate: Installed on 2020-04-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. X580VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580VD.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X580VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Apr 24 16:45:55 2020 xserver.configfile: default xserver.errors: NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver NVIDIA(G0): Failing initialization of X screen systemd-logind: failed to release device: Device not taken systemd-logind: failed to release device: Device not taken modeset(0): failed to set mode: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874856/+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 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462)
I would guess that option exposes DOS-era VGA support, which is still used by operating systems before they boot. While that shouldn't affect the operation of Linux after it has booted, it might, if it changes the default dithering mode on the hardware and Linux doesn't change it after that. Now I'm guessing too much. -- 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/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462) Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: The primary monitor, Microstep 24", is capable of 144 Hz refresh rate and I do use that regularly in Windows 10. When I set the rate to anything higher than 60 Hz (120 or 144) I get a wrong pixel pattern. See attached photos. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:06:45 2019 DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390] InstallationDate: Installed on 2010-10-12 (3317 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun May 13 18:05:25 2018 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::03:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+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 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]
** Changed in: mesa (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-upstream ** Tags added: fixed-in-mesa-20.1 -- 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/1868520 Title: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010] Status in Mesa: Fix Released Status in MPV: Unknown Status in Mutter: Fix Released Status in mesa package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Won't Fix Bug description: When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3) [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1) [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1) [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1) [3104436.990] wl_registry@3.global(16, "wl_seat", 5) [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1) [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1) [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1) [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1) [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3) [3104437.066] -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id [unknown]@8) [3104437.083] wl_registry@3.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1) [3104437.111] wl_registry@3.global(24, "gtk_text_input_manager", 1) [3104437.125] wl_registry@3.global(26, "wl_eglstream_controller", 1) [3104437.140]
[Desktop-packages] [Bug 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462)
Update: in the motherboard settings, under I/O, there's an option "Video Option ROM Type". This bug occurs when the value is set to UEFI. When the value is set to Legacy, the bug does not occur. There's a third possible value, "Disabled" or similar, which I did not try. Excuse me ignorance. I know the value of a LAN adapter option ROM — booting from network. But what is the value of a video card option ROM, please? And since this motherboard does not have an integrated video card, what does this option pertain to, please? -- 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/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462) Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: The primary monitor, Microstep 24", is capable of 144 Hz refresh rate and I do use that regularly in Windows 10. When I set the rate to anything higher than 60 Hz (120 or 144) I get a wrong pixel pattern. See attached photos. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:06:45 2019 DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390] InstallationDate: Installed on 2010-10-12 (3317 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun May 13 18:05:25 2018 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::03:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+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 1867668] Re: Visual artifacts in Gnome Shell when using the 'intel' Xorg driver
I'm not sure what's creating that file causing the problems: /etc/X11/xorg.conf.d/20-intel.conf Maybe you've experimented with a PPA in the past that modified your graphics packages? You can also find out by running: dpkg -S /etc/X11/xorg.conf.d/20-intel.conf Anyway, the point is that config file should not exist on a clean Ubuntu system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell when using the 'intel' Xorg driver Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1875868] Re: Ubuntu 20.04 visual glitches
*** This bug is a duplicate of bug 1867668 *** https://bugs.launchpad.net/bugs/1867668 Thanks for the log. It shows you're using the old unmaintained intel driver: Apr 29 15:25:43 PCBRUANT /usr/lib/gdm3/gdm-x-session[22649]: (II) intel: Driver for Intel(R) HD Graphics Apr 29 15:25:43 PCBRUANT /usr/lib/gdm3/gdm-x-session[22649]: (II) intel: Driver for Intel(R) Iris(TM) Graphics Apr 29 15:25:43 PCBRUANT /usr/lib/gdm3/gdm-x-session[22649]: (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics ... So this is a duplicate of bug 1867668. To fix it just modify your Xorg config to not load the 'intel' driver and load 'modeset' instead. Deleting your Xorg config file should also achieve that. And if you can also remove the package 'xserver-xorg-video-intel' to prevent it from being accidentally used. ** This bug has been marked a duplicate of bug 1867668 Visual artifacts in Gnome Shell when using the 'intel' Xorg driver -- 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/1875868 Title: Ubuntu 20.04 visual glitches Status in mutter package in Ubuntu: Incomplete Bug description: This bug report is a clean report based off of this one: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875730. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 13:25:24 2020 InstallationDate: Installed on 2019-09-19 (222 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875868/+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 1799213] Re: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
*** This bug is a duplicate of bug 1755305 *** https://bugs.launchpad.net/bugs/1755305 ** This bug has been marked a duplicate of bug 1755305 .xsession-errors filled with entries -- 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/1799213 Title: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Ubuntu 18.10, network-manager-gnome 1.8.18-2 Every three minutes or less, the applet writes to stderr these messages: (nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-WARNING **: 08:09:47.668: Can't set a parent on widget which has a parent (nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-WARNING **: 08:10:50.639: Can't set a parent on widget which has a parent Steps to reproduce: - install network-manager-gnome, add the nm-applet to the panel - wait Expected outcome: - not filling up error logs Seen outcome: - filling up error logs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager-gnome 1.8.18-2ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Oct 22 08:08:37 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-06-05 (869 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.111 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager-applet UpgradeStatus: Upgraded to cosmic on 2018-10-21 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b ethernet 1540209985 Mon 22 Oct 2018 08:06:25 AM EDT yes -999 no/org/freedesktop/NetworkManager/Settings/1 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp5s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1799213/+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 1750889] Re: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland
*** This bug is a duplicate of bug 1691678 *** https://bugs.launchpad.net/bugs/1691678 I use gnome on xorg on Ubuntu 20.04, and I see the scrollbar sticking out past the bottom of the window also. The scrollbar also sticks out to the right, as in the screenshot posted here. So I don't think this is a Wayland issue, but is an issue with the theme itself. This does not happen with the Yaru theme. -- 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/1750889 Title: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When using a clean GNOME session (with Adwaita theme) in combination with Wayland, the scrollbar in GNOME Terminal looks weird (see screenshot 1). The window also looks like it does not have a focus, but it does. Clicking anywhere on the menu bar fixes the focus issue, but the scrollbar still looks weird (see screenshot 2). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+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 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem
Please try previous kernel like the one in the 18.04, that means old kernel + 20.04 rootfs, does the noise disappear? -- 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/1875828 Title: [HDA-Intel - HDA Intel PCH, playback] Hum problem Status in alsa-driver package in Ubuntu: New Bug description: On upgrading from Ubuntu 18LTS to 20.04LTS I find that if I stop playing sound 5 seconds after stopping any correctly playing sounds (video / music / radio / system ) a loud hum starts in both speakers. This is volume independent. Before the speakers would just turn off automatically and go into standby mode. expected action...stop playing a sound and speakers go silent current action .. stop playing a sound and 5 seconds later speakers go from silent to a loud volume independent hum ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adrian 2706 F pulseaudio /dev/snd/pcmC0D0p: adrian 2706 F...m pulseaudio /dev/snd/controlC1: adrian 2706 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 10:13:38 2020 InstallationDate: Installed on 2018-05-20 (709 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB Audigy Fx) - HDA Creative Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 11/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: H110M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: 7438200-003 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-71004 dmi.product.sku: MBB-71004 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
It is better now with v2, but the driver fails at the machine driver initialization stage: [3.349857] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [3.349860] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
The driver looks good: APLAY List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: CX20561 Analog [CX20561 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: CX20561 Digital [CX20561 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 ARECORD List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CX20561 Analog [CX20561 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 But there is no valid sound card in the pulseaudio, could you please upload the log of pulseaudio. -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+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 1875908] Re: Fractional scaling does not work in Wayland session
** Package changed: ubuntu => xorg-server (Ubuntu) -- 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/1875908 Title: Fractional scaling does not work in Wayland session Status in xorg-server package in Ubuntu: New Bug description: Toggle the Fractional Zoom slider. In any position, only 100% and 200% are available. On an X11 session, everything works correctly. Checked on 2 systems (Laptop and installation in VirtualBox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1875908/+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 1875993] [NEW] yaru-theme-icon missing and blurred icons
Public bug reported: I am using Arc menu in default layout and look so have noticed that some categories are missing icons, namely Internet, Office and Utilities. They are instead drawn from Adwaita or highcolor. Also the Variety wallpaper manager installed from your repository has a badly blurred appearance on dash-to-panel compared to the status icons next to it. Please look into these as they are things that should and could be addressed in yaru-theme-icon preferably. yaru-theme-icon: Version - yaru-theme (20.04.6) focal lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: blurred icon missing theme yaru ** Description changed: I am using Arc menu in default layout and look so have noticed that some categories are missing icons, namely Internet, Office and Utilities. They are instead drawn from Adwaita or highcolor. Also the Variety wallpaper manager installed from your repository has a - badly blurred appearance on the panel compared to the status icons next - to it. + badly blurred appearance on dash-to-panel compared to the status icons + next to it. Please look into these as they are things that should and could be addressed in yaru-theme-icon preferably. yaru-theme-icon: Version - yaru-theme (20.04.6) focal lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1875993 Title: yaru-theme-icon missing and blurred icons Status in yaru-theme package in Ubuntu: New Bug description: I am using Arc menu in default layout and look so have noticed that some categories are missing icons, namely Internet, Office and Utilities. They are instead drawn from Adwaita or highcolor. Also the Variety wallpaper manager installed from your repository has a badly blurred appearance on dash-to-panel compared to the status icons next to it. Please look into these as they are things that should and could be addressed in yaru-theme-icon preferably. yaru-theme-icon: Version - yaru-theme (20.04.6) focal lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1875993/+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 1875908] [NEW] Fractional scaling does not work in Wayland session
You have been subscribed to a public bug: Toggle the Fractional Zoom slider. In any position, only 100% and 200% are available. On an X11 session, everything works correctly. Checked on 2 systems (Laptop and installation in VirtualBox). ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment focal wayland -- Fractional scaling does not work in Wayland session https://bugs.launchpad.net/bugs/1875908 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. -- 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 1875991] [NEW] Screen unlocks without password
Public bug reported: I think this might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1870803 however, I can't find out to add my machine information to it. A little more information I can add - not sure if it's the same for original reporter - when I first log into my account I get some sort of notification about gnome-screensaver not being enabled because gnome isn't installed; or something to that effect. This started upon upgrade to Focal. TLDR: If I lock my account using the gnome-menu, then press ctrl+alt+F7, it immediately goes to my session without needing to type a password, bypassing all security. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Apr 29 16:25:35 2020 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2016-04-29 (1461 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to focal on 2020-03-19 (41 days ago) ** Affects: gnome-screensaver (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-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1875991 Title: Screen unlocks without password Status in gnome-screensaver package in Ubuntu: New Bug description: I think this might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1870803 however, I can't find out to add my machine information to it. A little more information I can add - not sure if it's the same for original reporter - when I first log into my account I get some sort of notification about gnome-screensaver not being enabled because gnome isn't installed; or something to that effect. This started upon upgrade to Focal. TLDR: If I lock my account using the gnome-menu, then press ctrl+alt+F7, it immediately goes to my session without needing to type a password, bypassing all security. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Apr 29 16:25:35 2020 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2016-04-29 (1461 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to focal on 2020-03-19 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1875991/+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 1870803] Re: LightDM unlocks without Password
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1870803 Title: LightDM unlocks without Password Status in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: When doing `dm-tool lock` the screen locks. Then pressing CTRL+ALT+F7 immediately returns me to my Session without any need to type the password. When logging in mutliple users I can switch between the users with CTRL+ALT+F7 and CTRL+ALT+F8 without needing any of the users passwords. I tested this with both lightdm-gtk-greeter and slick-greeter and the behavior is the same for both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Sat Apr 4 17:05:51 2020 SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870803/+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 1870803] Re: LightDM unlocks without Password
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1870803 Title: LightDM unlocks without Password Status in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: When doing `dm-tool lock` the screen locks. Then pressing CTRL+ALT+F7 immediately returns me to my Session without any need to type the password. When logging in mutliple users I can switch between the users with CTRL+ALT+F7 and CTRL+ALT+F8 without needing any of the users passwords. I tested this with both lightdm-gtk-greeter and slick-greeter and the behavior is the same for both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Sat Apr 4 17:05:51 2020 SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870803/+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 1875989] [NEW] [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description:Ubuntu 20.04 LTS Release:20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to
[Desktop-packages] [Bug 1875985] Re: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4
** Summary changed: - [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all + [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4 -- 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/1875985 Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4 Status in alsa-driver package in Ubuntu: New Bug description: VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" Running it in the flavour of Xubuntu. Just like in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux". Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again. With 4.15.0-99-generic I do see a signal on the meters of the sound/volume control app, but physically there is no sound on either internal speakers nor on the headphones. With 4.15.0-96-generic everything is back to normal. My touchpad is working though (#1875916 seems to suggest that the touchpad stops working with 4.15.0-99-generic). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio CurrentDesktop: XFCE Date: Wed Apr 29 23:45:15 2020 InstallationDate: Installed on 2016-10-20 (1287 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago) dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.03.00 dmi.board.name: 0RJ0RW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.03.00:bd05/26/2016:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn0RJ0RW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-5368 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875985/+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 1875985] [NEW] [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4
Public bug reported: VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" Running it in the flavour of Xubuntu. Just like in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux". Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again. With 4.15.0-99-generic I do see a signal on the meters of the sound/volume control app, but physically there is no sound on either internal speakers nor on the headphones. With 4.15.0-96-generic everything is back to normal. My touchpad is working though (#1875916 seems to suggest that the touchpad stops working with 4.15.0-99-generic). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio CurrentDesktop: XFCE Date: Wed Apr 29 23:45:15 2020 InstallationDate: Installed on 2016-10-20 (1287 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago) dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.03.00 dmi.board.name: 0RJ0RW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.03.00:bd05/26/2016:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn0RJ0RW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-5368 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875985 Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4 Status in alsa-driver package in Ubuntu: New Bug description: VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" Running it in the flavour of Xubuntu. Just like in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux". Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again. With 4.15.0-99-generic I do see a signal on the meters of the sound/volume control app, but physically there is no sound on either internal speakers nor on the headphones. With 4.15.0-96-generic everything is back to normal. My touchpad is working though (#1875916 seems to suggest that the touchpad stops working with 4.15.0-99-generic). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio CurrentDesktop: XFCE Date: Wed Apr 29 23:45:15 2020 InstallationDate: Installed on 2016-10-20 (1287 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago) dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.03.00 dmi.board.name: 0RJ0RW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Followed the instruction in #11. Comment out dsp_driver=1 in alsa- base.conf. Restart. * Full dmesg in the attached file. * alsa-info: http://alsa- project.org/db/?f=021d92b6074d91fbbbae580104b68a751c07a968 pavucontrol shows "Dummy output". ** Attachment added: "dmesg_5.4.0-25_v2.log" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5363731/+files/dmesg_5.4.0-25_v2.log -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1626731]
(In reply to Bhaskar Chowdhury from comment #21) > I have compiled the 5.6.7 on Gentoo and the integrated camera is not working > . This is what I am getting in dmesg: > > root@Gentoo_18:03:11_Wed Apr 29:~ # dmesg | grep Camera > [ 11.356371] usb 2-8: Product: Integrated Camera > [ 11.873007] uvcvideo: Found UVC 1.00 device Integrated Camera (04ca:703c) > [ 11.891268] uvcvideo 2-8:1.0: Entity type for entity Camera 1 was not > initialized! > [ 11.891384] input: Integrated Camera: Integrated C as > /devices/pci:00/:00:14.0/usb2/2-8/2-8:1.0/input/input14 1. Create a new bug report as yours has almost nothing to do with this one. 2. Perform bisect regression testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1626731/+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 1874856] Re: Unwanted mouse trail
Mouse trail is gone with nouveau, but desktop is very very slow in all three modes XOrg, Gnome Classic, and Ubuntu. I had to switch back to 440 to be able to work. Switching drivers was only possible via CLI. The mouse trail is only apparent on the background, not inside application windows. -- 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/1874856 Title: Unwanted mouse trail Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Moving mouse leaves a trail of squares for a few seconds on a fresh 20.04 install. This happens with proprietary nvidia 440 drivers as well as nouveau on my GeFOrce GTX 1050 mobile. Could be related to my submission https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1874819 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 17:59:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1a10] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1a10] InstallationDate: Installed on 2020-04-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. X580VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=5df76c33-718b-436b-8b59-9a33dafbff4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580VD.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX580VD.315:bd03/08/2018:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X580VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Apr 24 16:45:55 2020 xserver.configfile: default xserver.errors: NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver NVIDIA(G0): Failing initialization of X screen systemd-logind: failed to release device: Device not taken systemd-logind: failed to release device: Device not taken modeset(0): failed to set mode: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874856/+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 1768178] Re: color scheme Solarized Dark is incorrect
** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion -- 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/1768178 Title: color scheme Solarized Dark is incorrect Status in gnome-terminal package in Ubuntu: Opinion Bug description: Original Solarized Dark looks different. Thereis the pull request on Github that fixes that - https://github.com/GNOME/gnome- terminal/pull/6 I'm not author of patch and don't checked it, but there is project that change color scheme to correct, it described here - https://github.com/Anthony25/gnome-terminal-colors- solarized/tree/master/colors/dark Here is built-in palette collected with gsettings get: ['#2E3436', '#CC', '#4E9A06', '#C4A000', '#3465A4', '#75507B', '#06989A', '#D3D7CF', '#555753', '#EF2929', '#8AE234', '#FCE94F', '#729FCF', '#AD7FA8', '#34E2E2', '#EC'] Here is correct palette: ['#070736364242', '#DCDC32322F2F', '#8585', '#B5B58989', '#26268B8BD2D2', '#D3D336368282', '#2A2AA1A19898', '#E8E8D5D5', '#2B2B3636', '#CBCB4B4B1616', '#58586E6E7575', '#65657B7B8383', '#838394949696', '#6C6C7171C4C4', '#9393A1A1A1A1', '#FDFDF6F6E3E3'] I asked the question about long codes - https://github.com/Anthony25 /gnome-terminal-colors-solarized/issues/76, but anyway it matches original scheme perfectly. I created bug at launchpad because Gnome restricted creating bugs for non-gnome developers in their guide https://wiki.gnome.org/Apps/Terminal/ReportingBugs and point to distribution bug tracker. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 1 07:49:18 2018 InstallationDate: Installed on 2018-04-29 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/usr/bin/zsh 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/1768178/+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 1626731]
I have compiled the 5.6.7 on Gentoo and the integrated camera is not working . This is what I am getting in dmesg: root@Gentoo_18:03:11_Wed Apr 29:~ # dmesg | grep Camera [ 11.356371] usb 2-8: Product: Integrated Camera [ 11.873007] uvcvideo: Found UVC 1.00 device Integrated Camera (04ca:703c) [ 11.891268] uvcvideo 2-8:1.0: Entity type for entity Camera 1 was not initialized! [ 11.891384] input: Integrated Camera: Integrated C as /devices/pci:00/:00:14.0/usb2/2-8/2-8:1.0/input/input14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1626731/+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 1875966] [NEW] Dock settings can not be set to only one monitor
Public bug reported: In the gnome-settings panel it is not possible to set the dock to being displayed on only one monitor after the option "all screens" has been selected once. After selecting a specific monitor the setting immideately buggs back to "all screens". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 22:48:55 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-11-07 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) ** Affects: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875966 Title: Dock settings can not be set to only one monitor Status in gnome-control-center package in Ubuntu: New Bug description: In the gnome-settings panel it is not possible to set the dock to being displayed on only one monitor after the option "all screens" has been selected once. After selecting a specific monitor the setting immideately buggs back to "all screens". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 22:48:55 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-11-07 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875966/+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 1875964] [NEW] Happened after apt upgrade
Public bug reported: I likely had already previously done a bunch of upgrades without restarting (even though the file that indicated a restart was required existed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 23:48:16 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (prog-if 00 [VGA controller]) Subsystem: Dell Mars XTX [Radeon HD 8790M] [1028:05be] InstallationDate: Installed on 2018-05-16 (714 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E6540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=ae4fb2b2-cc1b-48f5-a617-95f1ef6e9418 ro nomodeset splash radeon.modeset=0 radeon.cik_support=0 radeon.ci_support=0 amdgpu.si_support=1 amdgpu.cik=1 amdgpu.dc=1 amdgpu.dpm=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2004261830.fd7f37~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004290730.35ee6b~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2004290730.35ee6b~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0+git2004151930.384539~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git2004211930.846b53~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git2004030730.5444ca~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1875964 Title: Happened after apt upgrade Status in xorg package in Ubuntu: New Bug description: I likely had already previously done a bunch of upgrades without restarting (even though the file that indicated a restart was required existed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 23:48:16 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (prog-if 00 [VGA controller]) Subsystem: Dell Mars XTX [Radeon HD 8790M] [1028:05be] InstallationDate: Installed on 2018-05-16 (714 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E6540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=ae4fb2b2-cc1b-48f5-a617-95f1ef6e9418 ro nomodeset splash radeon.modeset=0 radeon.cik_support=0 radeon.ci_support=0 amdgpu.si_support=1 amdgpu.cik=1 amdgpu.dc=1 amdgpu.dpm=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc.
[Desktop-packages] [Bug 1875745] Re: Waffle button on dock doesn't do anything in wayland session
I'm clicking within the button -- 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/1875745 Title: Waffle button on dock doesn't do anything in wayland session Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using the waffle button menu on the dock when in a wayland session nothing happens ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 21:14:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 500 [8086:2212] InstallationDate: Installed on 2020-04-23 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper Ezbook X3 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rz1ysp@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_rz1ysp ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.WP313P.1809100.NHNAUHL03 dmi.board.asset.tag: Default string dmi.board.name: P313P dmi.board.vendor: Jumper dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP313P.1809100.NHNAUHL03:bd11/05/2019:svnJumper:pnEzbookX3:pvrDefaultstring:rvnJumper:rnP313P:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Ezbook dmi.product.name: Ezbook X3 dmi.product.sku: 1809100 dmi.product.version: Default string dmi.sys.vendor: Jumper version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875745/+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 1875960] [NEW] package nvidia-340 (not installed) failed to install/upgrade: Versuch, »/lib/udev/rules.d/71-nvidia.rules« zu überschreiben, welches auch in Paket nvidia-kernel-
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 29 22:23:23 2020 ErrorMessage: Versuch, »/lib/udev/rules.d/71-nvidia.rules« zu überschreiben, welches auch in Paket nvidia-kernel-common-390 390.132-0ubuntu2 ist InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: Versuch, »/lib/udev/rules.d/71-nvidia.rules« zu überschreiben, welches auch in Paket nvidia-kernel-common-390 390.132-0ubuntu2 ist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (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 nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1875960 Title: package nvidia-340 (not installed) failed to install/upgrade: Versuch, »/lib/udev/rules.d/71-nvidia.rules« zu überschreiben, welches auch in Paket nvidia-kernel-common-390 390.132-0ubuntu2 ist Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 29 22:23:23 2020 ErrorMessage: Versuch, »/lib/udev/rules.d/71-nvidia.rules« zu überschreiben, welches auch in Paket nvidia-kernel-common-390 390.132-0ubuntu2 ist InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: Versuch, »/lib/udev/rules.d/71-nvidia.rules« zu überschreiben, welches auch in Paket nvidia-kernel-common-390 390.132-0ubuntu2 ist 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/1875960/+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 1869653] Re: Sync scowl 2019.10.06-1 (main) from Debian unstable (main)
scowl (2019.10.06-1) unstable; urgency=medium * New upstream release (Closes: #952736) * Deprecate reprized for reprised (Closes: #952653) * Use up to 70 wordlists for hunspell (Closes: #933544) * Distribute all scowl files as utf-8 (Closes: #775480) -- Don Armstrong Sat, 29 Feb 2020 20:07:46 -0800 ** Changed in: scowl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to scowl in Ubuntu. https://bugs.launchpad.net/bugs/1869653 Title: Sync scowl 2019.10.06-1 (main) from Debian unstable (main) Status in scowl package in Ubuntu: Fix Released Bug description: Please sync scowl 2019.10.06-1 (main) from Debian unstable (main) This version adds various new words to the English dictionaries, and fixes bugs. It has not been updated since April 2018. Changelog entries since current focal version 2018.04.16-1: scowl (2019.10.06-1) unstable; urgency=medium * New upstream release (Closes: #952736) * Deprecate reprized for reprised (Closes: #952653) * Use up to 70 wordlists for hunspell (Closes: #933544) * Distribute all scowl files as utf-8 (Closes: #775480) -- Don Armstrong Sat, 29 Feb 2020 20:07:46 -0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/1869653/+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 1875957] [NEW] Random freezes for 1 second
Public bug reported: The gnome DE and some programs such as Telegram randomly freeze for ca a second and then recover again. This occurs ~5 times every minute. There are however applications which do work flawlessly, such as overwatch over lutris. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 22:16:49 2020 DistUpgraded: 2020-04-24 10:02:52,848 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] InstallationDate: Installed on 2019-11-07 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=45a49275-be6c-418c-86a5-c57794b70427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance 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/1875957 Title: Random freezes for 1 second Status in xorg package in Ubuntu: New Bug description: The gnome DE and some programs such as Telegram randomly freeze for ca a second and then recover again. This occurs ~5 times every minute. There are however applications which do work flawlessly, such as overwatch over lutris. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip
[Desktop-packages] [Bug 1616650] Re: snap refresh while command is running may cause issues
I have the exact problem with Chromium that Olivier described in #7. I see this issue as it affects Chromium especially important in April 2020 for two reasons: 1. With the global pandemic and the rise of working from home, a stable and reliable browser is more important than ever. 2. Ubuntu 20.04 has been released. This is the first LTS with Chromium as a snap. The number of people running into this issue will greatly increase. -- 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/1616650 Title: snap refresh while command is running may cause issues Status in snapd: In Progress Status in chromium-browser package in Ubuntu: Confirmed Bug description: In testing a desktop snap that saves state in $HOME on close, I noticed that if I snap refresh the snap while the command is running that it will try to save its state to the previous snap version's data directory. For the snap I was testing (a browser), this resulted in a very poor user experience (the browser on restart complained about an improper shutdown). What is happening is that: 1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something like /home/user/snap/foo/x1. The security policy correctly allows writes to SNAP_USER_DATA 2. on snap refresh to 'x2', the security policy for the snap is updated for the running process such that /home/user/snap/foo/x1 is readonly and /home/user/snap/foo/x2 is read/write 3. the command in '1's environment is not changed and HOME (as well as SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path 4. the command tries to shutdown gracefully and save state to the 'x1' HOME and security policy blocks it Snappy's design for rollbacks relies on the previous SNAP_DATA and SNAP_USER_DATA directories not being writable and IMHO we should not change the policy to make other snap version's data dirs writable. The design of the snappy state engine ensures (among other things) that there is only ever one security policy in place for the snap. In snappy 15.04 this problem was (intentionally) avoided because we used snap security policy that was versioned such that the new policy would not apply until the next app invocation. Gustavo and Zygmunt, you both advocated strongly for only one version of the policy on disk and loaded in the kernel and I recall bringing up this type of bug as a counter-argument, and if IIRC for daemons we said that snapd could simply restart them (makes perfect sense). Have you thought of the mechanism for restarting non-daemons? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+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 1866841] Re: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell-extension-prefs
** Tags removed: verification-needed ** Tags added: unmetdeps ** Changed in: gnome-shell (Ubuntu Focal) Importance: Undecided => Medium -- 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/1866841 Title: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell- extension-prefs Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Fix Committed Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+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 1874285] Re: [SRU] libreoffice 6.4.3 for focal
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1874285 Title: [SRU] libreoffice 6.4.3 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 6.4.3 is in its third bugfix release of the 6.4 line. For a list of fixed bugs compared to 6.4.3 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.3/RC2#List_of_fixed_bugs (that's a total of 58 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 58 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1874285/+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 1875240] Re: vbetool: mmap /dev/zero: Operation not permitted Failed to initialise LRMI (Linux Real-Mode Interface).
Mistakes were made. (a) sudo mount -o remount,exec /dev Works. The mistake made was rebooting before testing vbetool. Solution: sudo mount -o remount,exec /dev vbetool dpms force off sudo mount -o remount,noexec /dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vbetool in Ubuntu. https://bugs.launchpad.net/bugs/1875240 Title: vbetool: mmap /dev/zero: Operation not permitted Failed to initialise LRMI (Linux Real-Mode Interface). Status in vbetool package in Ubuntu: New Bug description: Upgrade from 18.04 to 20.04 As root. mmap /dev/zero: Operation not permitted Failed to initialise LRMI (Linux Real-Mode Interface). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vbetool 1.1-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Apr 26 15:20:56 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vbetool UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vbetool/+bug/1875240/+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 1868520] Re: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010]
** Changed in: mesa Status: New => Fix Released -- 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/1868520 Title: Clients fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010] Status in Mesa: Fix Released Status in MPV: Unknown Status in Mutter: Fix Released Status in mesa package in Ubuntu: In Progress Status in mutter package in Ubuntu: Won't Fix Bug description: When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3) [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1) [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1) [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1) [3104436.990] wl_registry@3.global(16, "wl_seat", 5) [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1) [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1) [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1) [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1) [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3) [3104437.066] -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id [unknown]@8) [3104437.083] wl_registry@3.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104437.096] wl_registry@3.global(23, "zwp_text_input_manager_v3", 1) [3104437.111] wl_registry@3.global(24, "gtk_text_input_manager", 1) [3104437.125] wl_registry@3.global(26, "wl_eglstream_controller", 1) [3104437.140] wl_callb...@6.done(3421) [3104437.146] -> wl_disp...@1.sync(new id wl_callback@6)
[Desktop-packages] [Bug 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled
On Xenial the patch serves its intended purpose. I built IBus for Xenial with ubuntu-disable-trigger.patch disabled and then installed. That made the UI component show up for setting shortcut for "Next input method". It defaults to Space, but changing it to e.g. Space affects this dconf value: $ gsettings get org.freedesktop.ibus.general.hotkey triggers ['space'] But on Unity that shortcut is not effective. It's overridden by the shortcut set in Text Entry: $ gsettings get org.gnome.desktop.wm.keybindings switch-input-source ['space'] So it's indeed a dead-end for users who happen to play with ibus-setup. OTOH, that UI component is shown on GNOME too, and it's just as much a dead-end there. If we think the issue is important enough, we should figure out a smarter way to hide that UI component IMO. Also on GNOME. And preferably upstream. Let's drop the patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870945 Title: ubuntu-disable-trigger.patch is effectively not enabled Status in Unity: New Status in ibus package in Ubuntu: In Progress Bug description: ubuntu-disable-trigger.patch has effectively not been enabled since XDG_CURRENT_DESKTOP was turned into a list of values instead of a single value. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1870945/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 I have a similar big, with this same video card, when starting in Ubuntu 20.04, it is no more than the login screen, how do I report? -- 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/1870779 Title: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060) Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login right after installation, but after a few reboots a black screen is displayed after login. I'm able to switch to a tty and tried to collect information with ubuntu-bug, but I am not sure if that help. I'm happy to provide further information if needed. I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the same. 19.10 works without any problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 4 14:05:01 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7] InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5675 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.7 dmi.board.name: 0477DV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.7 dmi.modalias: dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7: dmi.product.family: Inspiron dmi.product.name: Inspiron 5675 dmi.product.sku: 07EE dmi.product.version: 1.3.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.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.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1874696] Re: shift-alt-TAB can cause strange sound lag
^ Something distorts sound if you shift-alt-TAB instead of alt-TAB. Does that make sense? ** Summary changed: - shift-alt-TAB can cause strange sound lag + sound gets distorted with shift-alt-TAB -- 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/1874696 Title: sound gets distorted with shift-alt-TAB Status in gnome-shell package in Ubuntu: Incomplete Bug description: Is is it possible that shift-alt-TAB can create strange sound lag while alt-TAB doesn't? Sometimes it is noticeable that sounds lags if you this key combo which shouldn't be the case. :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874696/+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 1875445] Re: Volume slider doesn't produce sound
Hello, I narrowed down the trigger of the bug: it happens right after I log in my discord account(https://discordapp.com/) in Firefox (using Chromium instead of Firefox doesn't trigger the bug). -- 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/1875445 Title: Volume slider doesn't produce sound Status in gnome-settings-daemon package in Ubuntu: New Bug description: Hello, In Ubuntu 20.04: After system boot there is sound and when I adjust volume with the slide (top right corner of the screen) it produces default sound. About 10 minutes (may be related to loading of certain s/w) later during the same session the slider stops producing sound when I adjust volume. System sound is still present. I also noticed that in Settings->Sound two more entries appear in "Volume levels": 1. Speech-dispatcher-dummy; 2. Speech-dispatcher-espeak-ng. These two entries are not present there right after system boot when everything works fine. I also see these errors in Logs: "sof-audio-pci :00:1f.3: error: no reply expected, received 0x0". This bug is reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-settings-daemon 3.36.0-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1875445/+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 1875949] [NEW] Firefox ignores `--window` option
Public bug reported: Firefox ignores the `--window` option, when `--private-window` is specified, an instance is running. Instead, the behavior depends on an address being passed. To reproduce: - run `firefox --private-window &` - run `firefox --window --private-window` -> a new window opens; this is ok - run `firefox --window --private-window ubuntu.com` -> a tab opens in the latest window, which is not ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 75.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saverio1746 F pulseaudio BuildID: 20200403170909 Channel: Unavailable CurrentDesktop: MATE Date: Wed Apr 29 19:05:16 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:736 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:736 Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=75.0/20200403170909 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) 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 ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1875949 Title: Firefox ignores `--window` option Status in firefox package in Ubuntu: New Bug description: Firefox ignores the `--window` option, when `--private-window` is specified, an instance is running. Instead, the behavior depends on an address being passed. To reproduce: - run `firefox --private-window &` - run `firefox --window --private-window` -> a new window opens; this is ok - run `firefox --window --private-window ubuntu.com` -> a tab opens in the latest window, which is not ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 75.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saverio1746 F pulseaudio BuildID: 20200403170909 Channel: Unavailable CurrentDesktop: MATE Date: Wed Apr 29 19:05:16 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:736 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto
[Desktop-packages] [Bug 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Unfortunately the workaround is temporary. I rebooted and the emoji are
gone again.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
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:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
[Desktop-packages] [Bug 1874047] Re: 20.04 - Software Boutique - No Filter drop-down placement
** Changed in: ubuntu-mate Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1874047 Title: 20.04 - Software Boutique - No Filter drop-down placement Status in Ubuntu MATE: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Bug description: Open the Software Boutique and click on 'Sound and Video' and then click on the drop-down curently set to 'No Filter'. Expected result: menu of options opens immediately below. Actual result: menu for filters appears way off to the right, and below, outside of the application window. Problem reported originally by lqlarry here - https://ubuntu- mate.community/t/software-boutique-filter-menu/21546 I have confirmed that it affects more than 1 person. Ubuntu-MATE RC1 installed and updated from daily since start of Alpha test (clean install at that time). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874047/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
revision 1119 is not up-to-date, the latest for amd64 is now 1135. -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1875292] Re: Double click on window titlebar pass through to what's below
PS. I wanted also to mention that issue is not reproducible if I set to minimize window on Scroll Click.. so just with double-click way. -- 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/1875292 Title: Double click on window titlebar pass through to what's below Status in mutter package in Ubuntu: Incomplete Bug description: Hi, This is simple to reproduce and I experienced this also on 19.10. First, make sure you have enabled "double-click on top bar of window to minimize" feature, I'm using that because its easy and fast for me to minimize the window. 1. Make sure you have any folder (like home) or file on desktop but in Big size and Top-Center location of desktop (I have many folders and files which are on top-center location so when I click double-click on topbar of window, issue appears) 2. Open Files for example 3. Double-click on top bar of window to minimize it 4. Observe issue (make sure you double-clicked on top bar but to be folder or file behind it exactly.. because thats the point, when folder or file is behind that bar where you perform double-click, it will minimize the window + open that folder or file Actual result: Window minimized + folder opened Expected result: Just window minimized ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:17:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875292/+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 1875292] Re: Double click on window titlebar pass through to what's below
Hi Daniel, Here is attached video.. In the video you'll see that sometimes it failed to reproduce issue, thats because I double-clicked in the lower part of window topbar.. I suppose. ** Attachment added: "steps to reproduce" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875292/+attachment/5363615/+files/issue.mkv -- 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/1875292 Title: Double click on window titlebar pass through to what's below Status in mutter package in Ubuntu: Incomplete Bug description: Hi, This is simple to reproduce and I experienced this also on 19.10. First, make sure you have enabled "double-click on top bar of window to minimize" feature, I'm using that because its easy and fast for me to minimize the window. 1. Make sure you have any folder (like home) or file on desktop but in Big size and Top-Center location of desktop (I have many folders and files which are on top-center location so when I click double-click on topbar of window, issue appears) 2. Open Files for example 3. Double-click on top bar of window to minimize it 4. Observe issue (make sure you double-clicked on top bar but to be folder or file behind it exactly.. because thats the point, when folder or file is behind that bar where you perform double-click, it will minimize the window + open that folder or file Actual result: Window minimized + folder opened Expected result: Just window minimized ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:17:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875292/+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 1875845] Re: keyring cannot be unlocked if used fingerprint to login gnome session
Attached is 'journalctl -b 0' log. I boot up my laptop, seeing the GDM then selected my user and swipe my fingerprint to login. After seeing the desktop, I launched "Passwords and Keys" to try to unlock it. But it failed. I performed the swipe finger to unlock around "Apr 30 00:33:xx". ** Attachment added: "20200430-journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1875845/+attachment/5363607/+files/20200430-journalctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1875845 Title: keyring cannot be unlocked if used fingerprint to login gnome session Status in gnome-keyring package in Ubuntu: Incomplete Bug description: I upgraded to Ubuntu 20.04 and setup the fingerprint login. Today when I tried to launch remmina it didn't show up for a long time. I launch Gnome Password and Keys > Passwords > Login I see there's a button to click to unlock. Clicking the unlock button is still waiting forever. A moment later I logout current session and type in the user password to login. Then I could launch remmina and unlock the Gnome Password and Keys. System info ❯ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ~ ❯ apt-cache policy gnome-keyring gnome-keyring: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://ftp.cuhk.edu.hk/pub/Linux/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1875845/+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 1874285] Re: [SRU] libreoffice 6.4.3 for focal
Upgraded libreoffice from 1:6.4.2-0ubuntu3 to 1:6.4.3-0ubuntu0.20.04.1 from focal-proposed in a clean and up-to-date focal amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1874285 Title: [SRU] libreoffice 6.4.3 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 6.4.3 is in its third bugfix release of the 6.4 line. For a list of fixed bugs compared to 6.4.3 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.3/RC2#List_of_fixed_bugs (that's a total of 58 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 58 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1874285/+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 1733321] Autopkgtest regression report (network-manager/1.20.4-2ubuntu2.3)
All autopkgtests for the newly accepted network-manager (1.20.4-2ubuntu2.3) for eoan have finished running. The following regressions have been reported in tests triggered by the package: systemd/242-7ubuntu3.7 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#network-manager [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally
[Desktop-packages] [Bug 1875243] Re: Unexpressed dependency between gnome-control-center and mutter-common
Upstream Issue ID: 977 Link: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/977 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #977 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/977 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875243 Title: Unexpressed dependency between gnome-control-center and mutter-common Status in gnome-control-center package in Ubuntu: Triaged Bug description: Ubuntu Release: 20.04 Package Version: 1:3.36.1-1ubuntu5 Steps to reproduce: Pre-requisite: Ubuntu system with gnome-control-center installed but not mutter-common (ex: Regolith 1.4/20.04) 1. launch gnome-control-center from terminal 2. navigate to display tab Observed behaviour: (gnome-control-center:54513): GLib-GIO-ERROR **: 13:49:43.782: Settings schema 'org.gnome.mutter' is not installed (core dumped) Expected behaviour: no crash Once I install the package mutter-common, the crash does not occur and I am able to use gnome-control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875243/+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 1875899] Re: cannot detect VGA but in first install and live session it can detect
Thank you for taking the time to report this bug and help 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) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1875899 Title: cannot detect VGA but in first install and live session it can detect Status in xorg package in Ubuntu: Incomplete Bug description: cannot detect VGA but in first install and live session it can detect ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 21:04:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 4291HD1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=b30f4199-d472-4c2f-9fe9-a410f286058a ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291HD1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4291HD1:pvrThinkPadX220:rvnLENOVO:rn4291HD1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 4291HD1 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875899/+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 1875925] Re: gnome-remote-desktop has no settings entry in gnome-control-center
gnome-remote-desktop isn't in main and gnome-shell isn't built with it in Ubuntu, see bug #1802614 which might have to do with the issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875925 Title: gnome-remote-desktop has no settings entry in gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I try to use VNC with gnome-remote-desktop but they do not appear in settings https://wiki.gnome.org/Projects/Mutter/RemoteDesktop#Enabling https://gitlab.gnome.org/jadahl/gnome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875925/+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 1875862] Re: Display freeze quite often
** Package changed: xorg (Ubuntu) => linux (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/1875862 Title: Display freeze quite often Status in linux package in Ubuntu: New Bug description: From syslog: Apr 29 13:41:44 tower kernel: [20711.955797] i915 :00:02.0: Resetting rcs0 for hang on rcs0 This seems to happen 1-10 times per day. Not sure is this something related to PyCharm usage, but 80% of cases I have PyCharm in use when display freezes. Freeze is 7-8seconds and then again display is updates. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 13:50:04 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0871] InstallationDate: Installed on 2020-01-02 (118 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Precision 3630 Tower ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=59681403-f9c5-46a9-8ddc-7708e2d422dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.name: 0Y2K8N dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.2:bd11/25/2019:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0Y2K8N:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 3630 Tower dmi.product.sku: 0871 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875862/+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 1875925] Re: gnome-remote-desktop has no settings entry in gnome-control-center
Thank you for taking the time to report this bug and help 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: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875925 Title: gnome-remote-desktop has no settings entry in gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I try to use VNC with gnome-remote-desktop but they do not appear in settings https://wiki.gnome.org/Projects/Mutter/RemoteDesktop#Enabling https://gitlab.gnome.org/jadahl/gnome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875925/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red
No problems to date. It's been installed for a couple of months. On 4/29/20 9:08 AM, Tim Hockin wrote: > How is the Radeon 5450 - any problems with it? I may have to go the > same route. > > On Tue, Apr 28, 2020 at 10:20 PM Paul Collinsworth > wrote: >> I replaced the Nvidia video card in my system and the problem seems to >> have gone with it. >> >> I had seen an improvement with the Nvidia card after switching from the >> digital video output to the on-card VGA output, but over a period of a >> couple of weeks or so, the video degraded again. >> >> The new card is a VisionTek Radeon 5450. >> >> >> On 4/28/20 1:42 PM, Tim Hockin wrote: >>> I just filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712 >>> which feels like it might be similar? >>> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1875712). >> https://bugs.launchpad.net/bugs/1860483 >> >> Title: >>[nouveau, GeForce 7300 LE] screen background overlaid with scan type >>artifact in red >> >> Status in linux package in Ubuntu: >>Confirmed >> Status in mesa package in Ubuntu: >>Confirmed >> Status in mutter package in Ubuntu: >>Confirmed >> Status in xserver-xorg-video-nouveau package in Ubuntu: >>Confirmed >> >> Bug description: >>My desktop has both it's usual items in place; toolbar on left and >>desktop icons distributed around the screen. Then there's what appears >>to be a bunch of scan line, raster line artifacts, in red, laid over >>my normal background, which is a star field photo on what is >>ordinarily a black field. >> >>ProblemType: Bug >>DistroRelease: Ubuntu 18.04 >>Package: xorg 1:7.7+19ubuntu7.1 >>ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 >>Uname: Linux 4.15.0-74-generic x86_64 >>.tmp.unity_support_test.0: >> >>ApportVersion: 2.20.9-0ubuntu7.9 >>Architecture: amd64 >>CompositorRunning: None >>CurrentDesktop: ubuntu:GNOME >>Date: Tue Jan 21 13:04:20 2020 >>DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading >>DistroCodename: bionic >>DistroVariant: ubuntu >>ExtraDebuggingInterest: Yes >>GraphicsCard: >> NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if >> 00 [VGA controller]) >> Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] >>InstallationDate: Installed on 2016-08-19 (1249 days ago) >>InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 >> (20160719) >>MachineType: Dell Inc. Inspiron 531 >>ProcEnviron: >> PATH=(custom, no user) >> XDG_RUNTIME_DIR= >> LANG=en_US.UTF-8 >> SHELL=/bin/bash >>ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic >> root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet >> splash vt.handoff=1 >>SourcePackage: xorg >>Symptom: display >>UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) >>dmi.bios.date: 11/09/2007 >>dmi.bios.vendor: Dell Inc. >>dmi.bios.version: 1.0.7 >>dmi.board.name: 0RY206 >>dmi.board.vendor: Dell Inc. >>dmi.board.version: ��� >>dmi.chassis.type: 3 >>dmi.chassis.vendor: Dell Inc. >>dmi.chassis.version: Chassis Version >>dmi.modalias: >> dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: >>dmi.product.name: Inspiron 531 >>dmi.product.version: 00 >>dmi.sys.vendor: Dell Inc. >>version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 >>version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 >>version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 >>version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 >>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: Wed Oct 3 10:41:28 2018 >>xserver.configfile: default >>xserver.devices: >> inputPower Button KEYBOARD, id 6 >> inputPower Button KEYBOARD, id 7 >> inputDell Dell USB Keyboard KEYBOARD, id 8 >> inputLogitech USB Trackball MOUSE, id 9 >>xserver.logfile: /var/log/Xorg.0.log >>xserver.version: 2:1.18.4-0ubuntu0.8 >>xserver.video_driver: nouveau >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- 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/1860483 Title: [nouveau, GeForce 7300 LE] screen
[Desktop-packages] [Bug 1875912] Re: Selected audio output always USB device as default, but no control
Thank you for your bug report, it sounds similar to bug #1866194. Could you try if moving your ~/.config/pulse directory and restarting the session workaround the issue? Could be useful to report it upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/ if you could -- 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/1875912 Title: Selected audio output always USB device as default, but no control Status in pulseaudio package in Ubuntu: New Bug description: Upon login in Ubuntu 20.04, the selected audio device will always be my USB device (in this case a Schiit Modi 3 DAC). However, the audio will be played from my motherboard's default line-out through my desktop speakers (the desired and last used audio device). The issue then is that gnome and pulse audio seem to believe that the selected device is the USB DAC, and the volume controls no longer have any affect on the output volume. To regain control of the volume, I have to open up the Settings panel and select the Line-out device. This happens on every boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 10:49:08 2020 InstallationDate: Installed on 2019-10-31 (180 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-29 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-04-29T10:34:28.863415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875912/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
I'm still seeing the problem. tarantula!root# snap refresh All snaps up to date. tarantula!root# snap list | grep chromium chromium 81.0.4044.1221119 latest/stable canonical*- -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
The distorted audio sounds like a different issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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 1875925] [NEW] gnome-remote-desktop has no settings entry in gnome-control-center
Public bug reported: I try to use VNC with gnome-remote-desktop but they do not appear in settings https://wiki.gnome.org/Projects/Mutter/RemoteDesktop#Enabling https://gitlab.gnome.org/jadahl/gnome-remote-desktop ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875925 Title: gnome-remote-desktop has no settings entry in gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: I try to use VNC with gnome-remote-desktop but they do not appear in settings https://wiki.gnome.org/Projects/Mutter/RemoteDesktop#Enabling https://gitlab.gnome.org/jadahl/gnome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875925/+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 1875913] Re: Sound - "Output Device" changes when modifying the "Configuration" from Stereo Output to any other option
Thank you for your bug report, it sounds similar to bug #1866194. Could you try if moving your ~/.config/pulse directory and restarting the session workaround the issue? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1875913 Title: Sound - "Output Device" changes when modifying the "Configuration" from Stereo Output to any other option Status in gnome-control-center package in Ubuntu: Incomplete Bug description: After updating the output audio device from a USB device to the motherboard's Line Out then changing the configuration from "Analog Stereo Output" to "Analog Surround 2.1 Output", the Output Device is switched back to the USB Device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 11:03:52 2020 InstallationDate: Installed on 2019-10-31 (180 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875913/+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 1874047] Re: 20.04 - Software Boutique - No Filter drop-down placement
The issue should be fixed in https://launchpad.net/ubuntu/+source/webkit2gtk/2.28.2-0ubuntu0.20.04.1 ** Changed in: webkit2gtk (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1874047 Title: 20.04 - Software Boutique - No Filter drop-down placement Status in Ubuntu MATE: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Bug description: Open the Software Boutique and click on 'Sound and Video' and then click on the drop-down curently set to 'No Filter'. Expected result: menu of options opens immediately below. Actual result: menu for filters appears way off to the right, and below, outside of the application window. Problem reported originally by lqlarry here - https://ubuntu- mate.community/t/software-boutique-filter-menu/21546 I have confirmed that it affects more than 1 person. Ubuntu-MATE RC1 installed and updated from daily since start of Alpha test (clean install at that time). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874047/+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 1874973] Re: New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink()
*** This bug is a duplicate of bug 1864901 *** https://bugs.launchpad.net/bugs/1864901 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1874973 Title: New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink() Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since my upgrade from 19.10 to 20.04 on every start a _new_ /snap/chromium/[digit]/bin/chromium.launcher instance is launched and never-ending. It spawns a "sleep 60" child process. Five time starting (and stopping!) chromium = 5 processes 2823981 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832707 ?S 0:00 | \_ sleep 60 2824647 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831803 ?S 0:00 | \_ sleep 60 2825134 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831953 ?S 0:00 | \_ sleep 60 2825521 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832057 ?S 0:00 | \_ sleep 60 2832767 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832771 ?S 0:00 \_ sleep 60 The sleep 60 clearly indicates a problem in the check_current_symlink() function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874973/+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 1875717] Re: Opening file from Samba share results in Document in Use
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Critical ** Changed in: libreoffice (Ubuntu) Importance: Critical => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531 however this only occurs when Libre Office is on OS with LxQt desktop. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Again this occurs only on machines with LXQt desktop. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red
How is the Radeon 5450 - any problems with it? I may have to go the same route. On Tue, Apr 28, 2020 at 10:20 PM Paul Collinsworth wrote: > > I replaced the Nvidia video card in my system and the problem seems to > have gone with it. > > I had seen an improvement with the Nvidia card after switching from the > digital video output to the on-card VGA output, but over a period of a > couple of weeks or so, the video degraded again. > > The new card is a VisionTek Radeon 5450. > > > On 4/28/20 1:42 PM, Tim Hockin wrote: > > I just filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712 > > which feels like it might be similar? > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1875712). > https://bugs.launchpad.net/bugs/1860483 > > Title: > [nouveau, GeForce 7300 LE] screen background overlaid with scan type > artifact in red > > Status in linux package in Ubuntu: > Confirmed > Status in mesa package in Ubuntu: > Confirmed > Status in mutter package in Ubuntu: > Confirmed > Status in xserver-xorg-video-nouveau package in Ubuntu: > Confirmed > > Bug description: > My desktop has both it's usual items in place; toolbar on left and > desktop icons distributed around the screen. Then there's what appears > to be a bunch of scan line, raster line artifacts, in red, laid over > my normal background, which is a star field photo on what is > ordinarily a black field. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 > Uname: Linux 4.15.0-74-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.9 > Architecture: amd64 > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Jan 21 13:04:20 2020 > DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 > [VGA controller]) > Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] > InstallationDate: Installed on 2016-08-19 (1249 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: Dell Inc. Inspiron 531 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic > root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet > splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) > dmi.bios.date: 11/09/2007 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.0.7 > dmi.board.name: 0RY206 > dmi.board.vendor: Dell Inc. > dmi.board.version: ��� > dmi.chassis.type: 3 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: > dmi.product.name: Inspiron 531 > dmi.product.version: 00 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 > 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: Wed Oct 3 10:41:28 2018 > xserver.configfile: default > xserver.devices: >inputPower Button KEYBOARD, id 6 >inputPower Button KEYBOARD, id 7 >inputDell Dell USB Keyboard KEYBOARD, id 8 >inputLogitech USB Trackball MOUSE, id 9 > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.4-0ubuntu0.8 > xserver.video_driver: nouveau > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- 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/1860483 Title: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: My desktop has
[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
Does any of you have distorted audio together with this bug? I'm attaching a sample audio file to show what my system sounds like sometimes. Original sound: https://www.youtube.com/watch?v=wDdyn4Kbffs ** Attachment added: "bad-sound3.m4a" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5363560/+files/bad-sound3.m4a -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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
