[Desktop-packages] [Bug 1881060] Re: Screen lock tiggers segfault
cue,
Please open your own bug by running:
ubuntu-bug gnome-shell
--
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/1881060
Title:
Screen lock tiggers segfault
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
When I try to lock my screen (via termial/shortcut/menu icon) it the
screen flashes and screen lock fails to occur.
Error is:
[ 1174.050313] traps: gnome-shell[10135] general protection fault
ip:7f2facd9429a sp:7fff2117e168 error:0 in libc-2.31.so[7f2facc32000+178000]
[ 1196.611454] audit: type=1400 audit(1590639386.013:66): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="ippusbxd" pid=10567 comm="apparmor_parser"
[ 1196.611941] audit: type=1400 audit(1590639386.013:67): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="libreoffice-oopslash" pid=10570
comm="apparmor_parser"
[ 1196.612169] audit: type=1400 audit(1590639386.013:68): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="libreoffice-senddoc" pid=10578 comm="apparmor_parser"
[ 1196.612858] audit: type=1400 audit(1590639386.013:69): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action"
pid=10568 comm="apparmor_parser"
[ 1196.612860] audit: type=1400 audit(1590639386.013:70): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=10568
comm="apparmor_parser"
[ 1196.612862] audit: type=1400 audit(1590639386.013:71): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=10568
comm="apparmor_parser"
[ 1196.612864] audit: type=1400 audit(1590639386.013:72): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/{,usr/}sbin/dhclient" pid=10568
comm="apparmor_parser"
[ 1196.612889] audit: type=1400 audit(1590639386.013:73): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/sbin/cups-browsed" pid=10580
comm="apparmor_parser"
[ 1196.612924] audit: type=1400 audit(1590639386.013:74): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/ibus/ibus-engine-hangul" pid=10573
comm="apparmor_parser"
[ 1196.612967] audit: type=1400 audit(1590639386.013:75): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/bin/man" pid=10575 comm="apparmor_parser"
[ 1204.310516] show_signal: 54 callbacks suppressed
[ 1204.310517] traps: gnome-shell[10411] general protection fault
ip:7f6abd8f5252 sp:7ffd36f07f50 error:0 in libst-1.0.so[7f6abd8d5000+4c000]
[ 1430.333121] gnome-shell[10731]: segfault at 0 ip 7fcaa88bf252 sp
7ffe59aa07a0 error 4 in libst-1.0.so[7fcaa889f000+4c000]
[ 1430.333132] Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b
87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20
4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f
[ 1672.006542] traps: gnome-shell[11770] general protection fault
ip:7f56cd40229a sp:7ffc6a2aeb18 error:0 in libc-2.31.so[7f56cd2a+178000]
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-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 May 27 21:21:38 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-11-25 (184 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881060/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang
** Summary changed: - gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() + gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [usually with the dash-to-panel extension] -- 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/184 Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [usually with the dash-to-panel extension] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Seems to be reproducible Suspend the computer Start the computer from suspend Start chrome gmail. Has happened two times ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat May 9 20:00:47 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-04-16 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: mov(%rax),%r12 PC (0x7fe1b40c4252) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- 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/1879287 Title: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly) Status in linux package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I've recently installed Ubuntu on a laptop that has a Ryzen APU (with Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first issue that this kind of setup gives on a fresh install is that that PRIME render offloading doesn't work, I presume that Ubuntu currently sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia but that's another separate issue. As a workaround I created an Xorg configuration (attached in this report) that sets up both GPUs (with the appropiate BusIDs), after such configuration is applied the system boots fine with AMD integrated graphics being used and the ability to switch to Nvidia with PRIME render off-loading. The problem comes when I try to use the computer the next day, then it gives me a black screen without having the ability to switch to a tty, the boot log doesn't throw any errors I just see a black screen after Xorg tries to start. I can make it work again by entering in recovery mode, logging into a root console and switching between "nvidia" and "on-demand" modes using prime-select (I set it up to "on-demand" profile after installing Ubuntu). For the moment I cannot provide any relevant logs since it's now working fine (and I don't remember seeing any errors on Xorg logs), also I don't really know where to look for this kind of issues. My system information: -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) -RAM: 8 GB -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4) -Xorg 1.20.8-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881060] Re: Screen lock tiggers segfault
Hi again,
I have to add now that it only worked once. The second time I manually
triggered the lock screen the same behavior went back. I also
deactivated the Workspace-Matrix extension and it did not help.
So there is more happening under the hood.
Sorry for the confusion.
--
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/1881060
Title:
Screen lock tiggers segfault
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
When I try to lock my screen (via termial/shortcut/menu icon) it the
screen flashes and screen lock fails to occur.
Error is:
[ 1174.050313] traps: gnome-shell[10135] general protection fault
ip:7f2facd9429a sp:7fff2117e168 error:0 in libc-2.31.so[7f2facc32000+178000]
[ 1196.611454] audit: type=1400 audit(1590639386.013:66): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="ippusbxd" pid=10567 comm="apparmor_parser"
[ 1196.611941] audit: type=1400 audit(1590639386.013:67): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="libreoffice-oopslash" pid=10570
comm="apparmor_parser"
[ 1196.612169] audit: type=1400 audit(1590639386.013:68): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="libreoffice-senddoc" pid=10578 comm="apparmor_parser"
[ 1196.612858] audit: type=1400 audit(1590639386.013:69): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action"
pid=10568 comm="apparmor_parser"
[ 1196.612860] audit: type=1400 audit(1590639386.013:70): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=10568
comm="apparmor_parser"
[ 1196.612862] audit: type=1400 audit(1590639386.013:71): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=10568
comm="apparmor_parser"
[ 1196.612864] audit: type=1400 audit(1590639386.013:72): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/{,usr/}sbin/dhclient" pid=10568
comm="apparmor_parser"
[ 1196.612889] audit: type=1400 audit(1590639386.013:73): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/sbin/cups-browsed" pid=10580
comm="apparmor_parser"
[ 1196.612924] audit: type=1400 audit(1590639386.013:74): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/ibus/ibus-engine-hangul" pid=10573
comm="apparmor_parser"
[ 1196.612967] audit: type=1400 audit(1590639386.013:75): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/bin/man" pid=10575 comm="apparmor_parser"
[ 1204.310516] show_signal: 54 callbacks suppressed
[ 1204.310517] traps: gnome-shell[10411] general protection fault
ip:7f6abd8f5252 sp:7ffd36f07f50 error:0 in libst-1.0.so[7f6abd8d5000+4c000]
[ 1430.333121] gnome-shell[10731]: segfault at 0 ip 7fcaa88bf252 sp
7ffe59aa07a0 error 4 in libst-1.0.so[7fcaa889f000+4c000]
[ 1430.333132] Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b
87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20
4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f
[ 1672.006542] traps: gnome-shell[11770] general protection fault
ip:7f56cd40229a sp:7ffc6a2aeb18 error:0 in libc-2.31.so[7f56cd2a+178000]
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-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 May 27 21:21:38 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-11-25 (184 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881060/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1881241] [NEW] My HP laserjet 1018 stopped printing from Ubuntu 18.04
Public bug reported: I originally installed 16.04 on my newly acquired Dell Studio 2 months ago. I then installed my HP Laserjet 1018 and it ran well. I upgraded to 18.04 and the printer continued to work well until this morning when it decided not to work. I have checked the cables which all work. I do have an HP 6300 connected and it works when the same cable is plugged into it. The 1018 printer is switched on. I did switch 1018 on and off and it resets. I even ran a test page on the printer but cannot print test page from laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic i686 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Fri May 29 07:17:56 2020 InstallationDate: Installed on 2020-03-16 (73 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) Lpstat: device for hplaserjet: hp:/usb/HP_LaserJet_1018?serial=KP1E25R device for Officejet-6300-series: hp:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4 device for Officejet-6300-series-Fax: hpfax:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4 MachineType: Dell Inc. Studio 1555 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Officejet-6300-series-Fax.ppd', '/etc/cups/ppd/hplaserjet.ppd', '/etc/cups/ppd/Officejet-6300-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Officejet-6300-series-Fax.ppd: Permission denied grep: /etc/cups/ppd/hplaserjet.ppd: Permission denied grep: /etc/cups/ppd/Officejet-6300-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=631b51e9-3538-4ead-a72b-e2f2a3e59676 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0C234M dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/03/2009:svnDellInc.:pnStudio1555:pvrA07:rvnDellInc.:rn0C234M:rvrA07:cvnDellInc.:ct8:cvrA07: dmi.product.name: Studio 1555 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug bionic i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1881241 Title: My HP laserjet 1018 stopped printing from Ubuntu 18.04 Status in cups package in Ubuntu: New Bug description: I originally installed 16.04 on my newly acquired Dell Studio 2 months ago. I then installed my HP Laserjet 1018 and it ran well. I upgraded to 18.04 and the printer continued to work well until this morning when it decided not to work. I have checked the cables which all work. I do have an HP 6300 connected and it works when the same cable is plugged into it. The 1018 printer is switched on. I did switch 1018 on and off and it resets. I even ran a test page on the printer but cannot print test page from laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic i686 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Fri May 29 07:17:56 2020 InstallationDate: Installed on 2020-03-16 (73 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) Lpstat: device for hplaserjet: hp:/usb/HP_LaserJet_1018?serial=KP1E25R device for Officejet-6300-series: hp:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4 device for Officejet-6300-series-Fax: hpfax:/usb/Officejet_6300_series?serial=CN87AFV0DG04M4 MachineType: Dell Inc. Studio 1555 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Officejet-6300-series-Fax.ppd', '/etc/cups/ppd/hplaserjet.ppd', '/etc/cups/ppd/Officejet-6300-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Officejet-6300-series-Fax.ppd: Permission denied grep: /etc/cups/ppd/hplaserjet.ppd: Permission denied grep: /etc/cups/ppd/Officejet-6300-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=631b51e9-3538-4ead-a72b-e2f2a3e59676 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0C234M dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias:
[Desktop-packages] [Bug 1881060] Re: Screen lock tiggers segfault
Hi there,
the deactivation of the following extensions solved the issue at my
Ubuntu 20.4 system:
'workspace-indica...@gnome-shell-extensions.gcampax.github.com',
'panel-...@berend.de.schouwer.gmail.com'
I have 14 further extensions including workspace-matrix.
They all work well.
May it help and thanx to you all!
cheers
--
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/1881060
Title:
Screen lock tiggers segfault
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
When I try to lock my screen (via termial/shortcut/menu icon) it the
screen flashes and screen lock fails to occur.
Error is:
[ 1174.050313] traps: gnome-shell[10135] general protection fault
ip:7f2facd9429a sp:7fff2117e168 error:0 in libc-2.31.so[7f2facc32000+178000]
[ 1196.611454] audit: type=1400 audit(1590639386.013:66): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="ippusbxd" pid=10567 comm="apparmor_parser"
[ 1196.611941] audit: type=1400 audit(1590639386.013:67): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="libreoffice-oopslash" pid=10570
comm="apparmor_parser"
[ 1196.612169] audit: type=1400 audit(1590639386.013:68): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="libreoffice-senddoc" pid=10578 comm="apparmor_parser"
[ 1196.612858] audit: type=1400 audit(1590639386.013:69): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action"
pid=10568 comm="apparmor_parser"
[ 1196.612860] audit: type=1400 audit(1590639386.013:70): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=10568
comm="apparmor_parser"
[ 1196.612862] audit: type=1400 audit(1590639386.013:71): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=10568
comm="apparmor_parser"
[ 1196.612864] audit: type=1400 audit(1590639386.013:72): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/{,usr/}sbin/dhclient" pid=10568
comm="apparmor_parser"
[ 1196.612889] audit: type=1400 audit(1590639386.013:73): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/sbin/cups-browsed" pid=10580
comm="apparmor_parser"
[ 1196.612924] audit: type=1400 audit(1590639386.013:74): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/lib/ibus/ibus-engine-hangul" pid=10573
comm="apparmor_parser"
[ 1196.612967] audit: type=1400 audit(1590639386.013:75): apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/bin/man" pid=10575 comm="apparmor_parser"
[ 1204.310516] show_signal: 54 callbacks suppressed
[ 1204.310517] traps: gnome-shell[10411] general protection fault
ip:7f6abd8f5252 sp:7ffd36f07f50 error:0 in libst-1.0.so[7f6abd8d5000+4c000]
[ 1430.333121] gnome-shell[10731]: segfault at 0 ip 7fcaa88bf252 sp
7ffe59aa07a0 error 4 in libst-1.0.so[7fcaa889f000+4c000]
[ 1430.333132] Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b
87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20
4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f
[ 1672.006542] traps: gnome-shell[11770] general protection fault
ip:7f56cd40229a sp:7ffc6a2aeb18 error:0 in libc-2.31.so[7f56cd2a+178000]
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-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 May 27 21:21:38 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-11-25 (184 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881060/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
** Also affects: oem-priority/bionic Importance: Undecided Status: New ** No longer affects: oem-priority/bionic ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** No longer affects: oem-priority/bionic ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881235] [NEW] package yaru-theme-sound 20.04.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: I wanted to install whatsdesk from the snap store and system reported the following error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: yaru-theme-sound 20.04.7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 29 07:19:03 2020 Dependencies: DuplicateSignature: package:yaru-theme-sound:20.04.7 Setting up liblirc-client0:amd64 (0.10.1-6.1ubuntu1.1) ... dpkg: error processing package yaru-theme-sound (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all 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.2ubuntu0.1 SourcePackage: yaru-theme Title: package yaru-theme-sound 20.04.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (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 yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1881235 Title: package yaru-theme-sound 20.04.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in yaru-theme package in Ubuntu: New Bug description: I wanted to install whatsdesk from the snap store and system reported the following error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: yaru-theme-sound 20.04.7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 29 07:19:03 2020 Dependencies: DuplicateSignature: package:yaru-theme-sound:20.04.7 Setting up liblirc-client0:amd64 (0.10.1-6.1ubuntu1.1) ... dpkg: error processing package yaru-theme-sound (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all 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.2ubuntu0.1 SourcePackage: yaru-theme Title: package yaru-theme-sound 20.04.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1881235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584716] Re: Text corruption in various Gnome apps since Xenial upgrade
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1584716 Title: Text corruption in various Gnome apps since Xenial upgrade Status in xorg package in Ubuntu: Expired Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 Since the Ubuntu Xenial upgrade, I've had various instances of text corruption. I use a gnome-shell session. I (think) see this only if the laptop has suspended and restored. I'm using the intel graphics driver from ppa:oibaf/graphics-drivers (in a failed attempt to try and upgrade myself out of the issue), but it was happening before changing to a custom PPA. This affects such a wide array of parts of the desktop that I suspect it's likely to be a basic X11 driver or GTK-level bug. Screenshots attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1584716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome
[Expired for ssh-askpass-fullscreen (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ssh-askpass-fullscreen (Ubuntu) Status: Incomplete => Expired -- 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/1843201 Title: Unity in Wayland prompts for keyboard focus on each run of ssh- askpass-gnome Status in gnome-shell package in Ubuntu: Won't Fix Status in ssh-askpass-fullscreen package in Ubuntu: Expired Status in unity package in Ubuntu: Invalid Bug description: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869443] Re: libvte attempts to overwrite file in package libvte-common
[Expired for vte2.91 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vte2.91 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1869443 Title: libvte attempts to overwrite file in package libvte-common Status in vte2.91 package in Ubuntu: Expired Bug description: libvte-2.91-0 0.60.0-2ubuntu1 from focal-proposed tries to install /usr/lib/systemd/user/vte-spawn-.scope.d/defaults.conf which is already provided by libvte-2.91-common 0.60.0-2ubuntu1 and fails. Steps to reproduce: 1. sudo apt install libvte-2.91-common 2. sudo apt install libvte-2.91-0 Expected results: libvte-2.91 installs. Actual results: Preparing to unpack .../libvte-2.91-0_0.60.0-2ubuntu1_amd64.deb ... Unpacking libvte-2.91-0:amd64 (0.60.0-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libvte-2.91-0_0.60.0-2ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/systemd/user /vte-spawn-.scope.d/defaults.conf', which is also in package libvte-2.91-common 0.60.0-2ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libvte-2.91-0_0.60.0-2ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Workaround: $ sudo dpkg -i --force-overwrite /var/cache/apt/archives/libvte-2.91-0_0.60.0-2ubuntu1_amd64.deb $ sudo apt --fix-broken install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1869443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880991] Re: [nvidia] Xorg freeze
I don't know about 19:32:32 but it sounds like Xorg might have crashed around 19:44:04 and 20:25:10. So please repeat the steps in comment #2. Also if you can find your Xorg.log file from when a crash/freeze happened then please attach that. -- 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/1880991 Title: [nvidia] Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: Sometimes there is an X11 freeze. Usually it happens when I connect to a Zoom conference, but latest (and at least one previous) it happened when I wasn't using Zoom. The symptoms were same: still image, but mouse cursor could be moved. I can switch to another terminal (ctrl+alt+f1), when I return to the GUI, there is only black screen with moving mouse cursor. I can only restart lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed May 27 19:49:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-29-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2020-05-09 (17 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgxubuntu-root ro iommu=soft quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: 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 20.0.4-2ubuntu1 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/xorg-server/+bug/1880991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880991] Re: [nvidia] Xorg freeze
The freeze was about May 27 19:32:32, when I had opened software- properties utility. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880991/+attachment/5378155/+files/journalctl.log -- 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/1880991 Title: [nvidia] Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: Sometimes there is an X11 freeze. Usually it happens when I connect to a Zoom conference, but latest (and at least one previous) it happened when I wasn't using Zoom. The symptoms were same: still image, but mouse cursor could be moved. I can switch to another terminal (ctrl+alt+f1), when I return to the GUI, there is only black screen with moving mouse cursor. I can only restart lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed May 27 19:49:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-29-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2020-05-09 (17 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgxubuntu-root ro iommu=soft quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: 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 20.0.4-2ubuntu1 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/xorg-server/+bug/1880991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881212] Re: Blank Screen initiates then fails
Thanks for the bug report. This sounds like gnome-shell has crashed and is being restarted: > Whilst it is blanking, any running applications show their windows (which is not usual) but it appears gnome-shell and the window manager are not running (no dash and no window decorations). When gnome-shell crashes the apps are still running on the bare Xorg server so it looks different. -- 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/1881212 Title: Blank Screen initiates then fails Status in Ubuntu: Incomplete Bug description: Blank Screen initiates after timeout (usually 5 minutes but set to 1 minute to replicate this bug), screen goes blank on both laptop and external Dell, but immediately comes back on. Whilst it is blanking, any running applications show their windows (which is not usual) but it appears gnome-shell and the window manager are not running (no dash and no window decorations). Disconnecting external monitor exhibits the same Blank Screen failure on the laptop screen. I have turned Automatic Screen Lock off for now to remove that as a cause. I have also had intermittent failure of gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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: Fri May 29 09:07:11 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-31-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2020-02-25 (93 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QFCTO1WW ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-01 (27 days ago) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFCTO1WW:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFCTO1WW dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th 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 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/+bug/1881212/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881212] Re: Blank Screen initiates then fails
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1881212 Title: Blank Screen initiates then fails Status in Ubuntu: Incomplete Bug description: Blank Screen initiates after timeout (usually 5 minutes but set to 1 minute to replicate this bug), screen goes blank on both laptop and external Dell, but immediately comes back on. Whilst it is blanking, any running applications show their windows (which is not usual) but it appears gnome-shell and the window manager are not running (no dash and no window decorations). Disconnecting external monitor exhibits the same Blank Screen failure on the laptop screen. I have turned Automatic Screen Lock off for now to remove that as a cause. I have also had intermittent failure of gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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: Fri May 29 09:07:11 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-31-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2020-02-25 (93 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QFCTO1WW ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-01 (27 days ago) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFCTO1WW:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFCTO1WW dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th 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 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/+bug/1881212/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881199] Re: [SoundCore mini, playback] No sound at all from Rhythmbox
Please try: cd ~/.config rm -rf pulse and the log out and in again. ** 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/1881199 Title: [SoundCore mini, playback] No sound at all from Rhythmbox Status in pulseaudio package in Ubuntu: Incomplete Bug description: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW 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:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
There is no fix for this bug yet. If you would like to discuss it then please do so with the developers at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2467 -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881190] Re: dock missing
You don't seem to have the dock enabled. You have: 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'places-m...@gnome-shell-extensions.gcampax.github.com', 'ubuntu-appindicat...@ubuntu.com', 'window-l...@gnome-shell-extensions.gcampax.github.com', 'workspace-indica...@gnome-shell-extensions.gcampax.github.com', 'windowsnaviga...@gnome-shell-extensions.gcampax.github.com', 'drive-m...@gnome-shell-extensions.gcampax.github.com' Unfortunately I can't recommend a simple GUI option to fix this that works in Ubuntu 18.04 because the old GUI is buggy (bug 1718850) and the new GUI is missing (gnome-shell-extension-prefs). Please try: sudo apt install --reinstall gnome-shell-extension-ubuntu-dock and if that didn't work after a reboot then you will need to edit your gsettings: org.gnome.shell enabled-extensions and add 'ubuntu-d...@ubuntu.com'. Alternatively, if you can then please just install Ubuntu 20.04 (https://releases.ubuntu.com/20.04/). ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1881190 Title: dock missing Status in gnome-shell package in Ubuntu: Incomplete Bug description: The dock missed after a reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 28 20:44:15 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-18 (496 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
Please push out a fix for this ASAP, once this tight loop is hit the machine becomes an unusable 100% CPU using mess. I know of several others suffering exactly the same bug. For me this can be reproduced by having a terminal using half the screen (using CMD+LEFT), then switching to fullscreen (F11) and back (F11). Repeating this some number of times triggers this tight loop of 100% CPU usage. After that, it's difficult to get window focus and windows are slow to respond to anything. To recover I use `killall -3 gnome-shell`, which allows Gnome to restart but then has the delightful affect of throwing windows around the screen randomly and forgetting there are multiple monitors. -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver
** Tags added: bionic ** Summary changed: - Support kernel 5.4 Intel sound driver + Support kernel 5.4 Intel sound driver on bionic -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
** 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/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Confirmed Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 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.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/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800763] Re: After installing the package with version 340.107, the system won't start
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Invalid -- 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/1800763 Title: After installing the package with version 340.107, the system won't start Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Bug description: On Ubuntu 18.10, after installing the 340.107 driver, the system hangs with the last line showing [OK] Started GNOME Display Manager. I'm not able to change to another TTY, the system is completely locked. After forced restart, entered recovery mode, with root terminal, and removed the driver, and then the systems starts using the Nouveau drivers. The GPU is a nVidia GeForce 9500GT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1800763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881062] Re: Mouse pointer disappeared after upgrade
I am sorry that I forgot the files from dmesg and Xorg.0.log. And right after sending this bug report I read some articles in AskUbuntu. I installed Ubuntu by UEFI mode when the bug happened, and I found no use of UEFI for me. Then I reinstalled by Legacy mode and meantime I erased everything when I found email from here. I regret why I didn't put those files on Google drive or somewhere... -- 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/1881062 Title: Mouse pointer disappeared after upgrade Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Mouse vendor: Elecom Mouse name: Deft M-DT20R S/N 99011158 S/N 9700261B I have two sets of this model and both are not working any more. Wireless USB mouse stopped working after 'sudo apt upgrade' on 0:00 UTC 28th May 2020. I also upgraded BIOS of ThinkStation P500 from A4KT89US to A4KTA7US just an hour before the upgrade. However I plugged in an old wired Elecom USB mouse and this is working. And also I tried another wireless USB mouse Logicool M570, this model is working except the left-click or right-click (means unstable). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03: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: .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 28 13:14:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2020-05-25 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 30A6S45A16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=822191be-6b70-4841-97dc-e4c008d418b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: A4KTA7AUS dmi.board.name: 102F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN 3425060692537 dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrA4KTA7AUS:bd04/13/2020:svnLENOVO:pn30A6S45A16:pvrThinkStationP500:rvnLENOVO:rn102F:rvrSDK0J40705WIN3425060692537:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: ThinkStation P500 dmi.product.name: 30A6S45A16 dmi.product.sku: LENOVO_MT_30A6_BU_Think_FM_ThinkStation P500 dmi.product.version: ThinkStation P500 dmi.sys.vendor: LENOVO 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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/linux/+bug/1881062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
This bug was fixed in the package wpa - 2:2.9-1ubuntu7 --- wpa (2:2.9-1ubuntu7) groovy; urgency=medium * debian/patches/git_roaming_interface.patch: - backport upstream fix 'dbus: Move roam metrics to the correct interface', should reduces the number of events (lp: #1879087) -- Sebastien Bacher Wed, 20 May 2020 19:03:27 +0200 ** Changed in: wpa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Fix Released Status in wpa package in Debian: New Bug description: * Impact wpa ships an invalid network-manager configuration that triggers warnings * Test case $ journalctl | grep no-mac-addr-change should not have errors listed * Regression potential the change removes configurations which are not needed (since they set the value to the same one as the default) and in the wrong section, it shouldn't have any visible impact Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity
This bug was fixed in the package wpa - 2:2.9-1ubuntu7 --- wpa (2:2.9-1ubuntu7) groovy; urgency=medium * debian/patches/git_roaming_interface.patch: - backport upstream fix 'dbus: Move roam metrics to the correct interface', should reduces the number of events (lp: #1879087) -- Sebastien Bacher Wed, 20 May 2020 19:03:27 +0200 ** Changed in: wpa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Incomplete Bug description: * Impact extra roaming events are been generated * Test case check the output of `journalctl -lu wpa_supplicant`, it should have warnings dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 the roaming events should not be too frequent * Regression potential check that wifi connection keep working correctly -- When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
** Package changed: ubuntu => xorg (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/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in xorg package in Ubuntu: New Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 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.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/xorg/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881213] [NEW] System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
You have been subscribed to a public bug: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 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.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 fonts kubuntu ubuntu -- System hangs at reboot or poweroff. kworker blocked at dp_altmode_work https://bugs.launchpad.net/bugs/1881213 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1881212] [NEW] Blank Screen initiates then fails
Public bug reported: Blank Screen initiates after timeout (usually 5 minutes but set to 1 minute to replicate this bug), screen goes blank on both laptop and external Dell, but immediately comes back on. Whilst it is blanking, any running applications show their windows (which is not usual) but it appears gnome-shell and the window manager are not running (no dash and no window decorations). Disconnecting external monitor exhibits the same Blank Screen failure on the laptop screen. I have turned Automatic Screen Lock off for now to remove that as a cause. I have also had intermittent failure of gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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: Fri May 29 09:07:11 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-31-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2020-02-25 (93 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QFCTO1WW ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-01 (27 days ago) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFCTO1WW:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFCTO1WW dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th 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 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881212 Title: Blank Screen initiates then fails Status in xorg package in Ubuntu: New Bug description: Blank Screen initiates after timeout (usually 5 minutes but set to 1 minute to replicate this bug), screen goes blank on both laptop and external Dell, but immediately comes back on. Whilst it is blanking, any running applications show their windows (which is not usual) but it appears gnome-shell and the window manager are not running (no dash and no window decorations). Disconnecting external monitor exhibits the same Blank Screen failure on the laptop screen. I have turned Automatic Screen Lock off for now to remove that as a cause. I have also had intermittent failure of gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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: Fri May 29 09:07:11 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-31-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard:
[Desktop-packages] [Bug 1583538] Re: Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.
Late to the party, but my case is even weirder. Works when playing multiplayer on a server, "No OpenGL context found in the current thread." when creating a new local single player world. -- 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/1583538 Title: Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread. Status in Libertine: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: User reports error when attempting to start applications that use OpenGL when using the desktop personality. See traceback below. Time: 2016-05-18 21:26 Description: Initializing game java.lang.ExceptionInInitializerError at bcc.ar(SourceFile:620) at bcc.an(SourceFile:428) at bcc.a(SourceFile:377) at net.minecraft.client.main.Main.main(SourceFile:124) Caused by: java.lang.NullPointerException at org.lwjgl.opengl.LinuxDisplay.getAvailableDisplayModes(LinuxDisplay.java:947) at org.lwjgl.opengl.LinuxDisplay.init(LinuxDisplay.java:738) at org.lwjgl.opengl.Display.(Display.java:138) ... 4 more A detailed walkthrough of the error, its code path and all known details is as follows: --- -- Head -- Stacktrace: at bcc.ar(SourceFile:620) at bcc.an(SourceFile:428) -- Initialization -- Details: Stacktrace: at bcc.a(SourceFile:377) at net.minecraft.client.main.Main.main(SourceFile:124) -- System Details -- Details: Minecraft Version: 1.9.2 Operating System: Linux (amd64) version 4.4.0-22-generic Java Version: 1.8.0_91, Oracle Corporation Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 144126120 bytes (137 MB) / 252248064 bytes (240 MB) up to 3194421248 bytes (3046 MB) JVM Flags: 5 total; -Xmx3G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn256M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 Launched Version: 1.9.2 LWJGL: 2.9.4 OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread. GL Caps: Using VBOs: No Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Packs: Current Language: ~~ERROR~~ NullPointerException: null Profiler Position: N/A (disabled) CPU: To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1583538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860734] Re: Drop firefox.sh shell script
Closing this as likely superseded by trying to move to snaps/flatpak. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1860734 Title: Drop firefox.sh shell script Status in firefox package in Ubuntu: Invalid Bug description: Firefox does a much better job than 5 years ago in handling profiles (https://support.mozilla.org/en-US/kb/profile-manager-create-remove- switch-firefox-profiles) The last time a a firefox.sh changes were mentioned in the changelog was Mon, 12 Jan 2015. Is there any reason I'm missing to drop it for Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1860734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880785] Re: Cannot enable 'Lock screen on suspend'
Possibly worth noting-- I have the default keyboard shortcut set to lock the screen (Super + L). Using that keyboard shortcut does nothing. However, I am able to lock the screen by selecting 'Lock' from the gnome-shell menu on the top navigation bar. -- 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/1880785 Title: Cannot enable 'Lock screen on suspend' Status in gnome-shell package in Ubuntu: New Bug description: I am trying to make my laptop lock the screen upon unsuspending. I have made sure that the setting is enabled in 'Settings > Privacy > Screen lock > Lock screen on suspend', but my laptop opens without a lock screen when I open it or press a key. This only started since upgrading to Ubuntu 20.04. Previously, I would have a locked screen and be prompted for a password upon unsuspending. $ gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend true $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.2-1ubuntu1~20.04.1 Version table: *** 3.36.2-1ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 21:28:39 2020 DisplayManager: lightdm DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-07-16 (680 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-23 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
Hi, i just found out that if i try to click *a lot* of times in connection button i can connect the second time. the only message in log was not really in the same time when i tried to connect or disconnect D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC0 is accessible: no D: [pulseaudio] module-udev-detect.c: Suspending all sinks and sources of card alsa_card.pci-_00_1f.3. Just for test, i paired another kind of bluetooth device, a gamepad controller, and i was able to connect and disconect normally every time (without this bug) -- 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/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
Hi! i'm sorry for taking so long to reply, i lost the email notification in spam. Well, I did that. There is a log of log messages there, but nothing when i tried to connect again (i was checking with tail -f). ** Attachment added: "a.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5378092/+files/a.txt -- 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/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly
This is happening on Wifi and VPN for me... Ethernet works fine. -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881200] [NEW] onboard defaults to tablet mode
Public bug reported: I am using onboard on arch Linux with i3 on a convertible laptop. I have "Auto-show when editing text" enabled as well as "Auto-show only in tablet mode". The acpid service is enabled with systemd and works properly. onboard is started when logging in through "exec --no- startup-id onboard" within the i3 configs. When first started, onboard automatically assumes it is in tablet mode and will auto-show the keyboard when editing text. Once the computer is flipped into tablet mode and flipped back into laptop mode, onboard doesn't automatically show, which is the expected behavior. I assume this is because onboard doesn't receive an initial acpid message telling it it is starting in laptop mode, so it assumes tablet mode initially. Having a setting to specify whether to start in tablet or laptop mode could fix this issue. ** Affects: onboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1881200 Title: onboard defaults to tablet mode Status in onboard package in Ubuntu: New Bug description: I am using onboard on arch Linux with i3 on a convertible laptop. I have "Auto-show when editing text" enabled as well as "Auto-show only in tablet mode". The acpid service is enabled with systemd and works properly. onboard is started when logging in through "exec --no- startup-id onboard" within the i3 configs. When first started, onboard automatically assumes it is in tablet mode and will auto-show the keyboard when editing text. Once the computer is flipped into tablet mode and flipped back into laptop mode, onboard doesn't automatically show, which is the expected behavior. I assume this is because onboard doesn't receive an initial acpid message telling it it is starting in laptop mode, so it assumes tablet mode initially. Having a setting to specify whether to start in tablet or laptop mode could fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1881200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881199] [NEW] [SoundCore mini, playback] No sound at all from Rhythmbox
Public bug reported: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW 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:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st 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/1881199 Title: [SoundCore mini, playback] No sound at all from Rhythmbox Status in pulseaudio package in Ubuntu: New Bug description: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO
[Desktop-packages] [Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
Here is a screenshot presenting what it happening. I'm loading webpages and watching a livestream on Twitch, and nothing is showing up on the Monitor. I have restarted the PC multiple times since I noticed that, but I think it started happening after the upgrade to Ubuntu 20.04 (GNOME 3.36). ** Attachment added: "Screenshot of the software." https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1881197/+attachment/5378066/+files/Captura%20de%20tela%20de%202020-05-28%2017-56-29.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1881197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881197] [NEW] No network usage info presented, always 0 bytes/s.
Public bug reported: 1) Description: Ubuntu 20.04 LTS Release:20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) ** Affects: gnome-system-monitor (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-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1881197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881175] Re: nautilus doesnt start
Thank you for your bug report, could you include a 'journalctl -b 0' log after getting the issue? ** Changed in: nautilus (Ubuntu) Status: New => Incomplete ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1881175 Title: nautilus doesnt start Status in nautilus package in Ubuntu: Incomplete Bug description: for an unknown cause nautilus does not want to start, after a reboot it works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 20:01:29 2020 InstallationDate: Installed on 2020-01-14 (135 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-12 (16 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880679] Re: a
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1880679 Title: a Status in xorg package in Ubuntu: New Bug description: b ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:11:42 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 5.3.0-46-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-51-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-53-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2020-02-16 (99 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20KGS95F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=fc676807-153f-4991-8967-03aee78f1c55 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS95F00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: EP26487 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KGS95F00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS95F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS95F00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO 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/xorg/+bug/1880679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881139] Re: [80XL, Realtek Generic, Mic, Internal] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1881139 Title: [80XL, Realtek Generic, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: ubuntu-bug tested the microphone and everything is good but i have to sound when i want to speack using skype or what's app. microphone does not work inside the applications. regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nima 14089 F pulseaudio /dev/snd/pcmC0D0p: nima 14089 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 19:25:50 2020 InstallationDate: Installed on 2020-04-24 (34 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 successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nima 14089 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [80XL, Realtek Generic, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN29WW:bd09/30/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881190] [NEW] dock missing
Public bug reported: The dock missed after a reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 28 20:44:15 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-18 (496 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881190 Title: dock missing Status in gnome-shell package in Ubuntu: New Bug description: The dock missed after a reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 28 20:44:15 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-18 (496 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873514] Re: Ubuntu uses insecure FreeRDP version
Thanks. I deliberately wasn't going to use cairo instead of libswscale as I read it may cause performance issues for image scaling. I didn't test it so some testing is needed to see if it matters or is even used with guacamole. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1873514 Title: Ubuntu uses insecure FreeRDP version Status in freerdp2 package in Ubuntu: Confirmed Bug description: FreeRDP has been released some days ago and fixes several security issues as can be seen at https://github.com/FreeRDP/FreeRDP/blob/2.0.0/ChangeLog. However Ubuntu and in particular 20.04 does not yet provide the released version but uses an outdated version. Please upgrade to the released version of FreeRDP before releasing 20.04. Thanks, Joachim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1873514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873996] Re: DevTools does not open at 84.0.4115.5
** Branch linked: lp:~chromium-team/chromium-browser/bionic-dev
--
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/1873996
Title:
DevTools does not open at 84.0.4115.5
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
https://bugs.chromium.org/p/chromium/issues/detail?id=1072187
Steps to reproduce the problem:
1. Ctrl+Shift+I or right-click, click Inspect
2. Navigate to chrome://inspect/#pages, click inspect
3.
What is the expected behavior?
DevTools to open
What went wrong?
DevTools does not open.
Did this work before? Yes Chromium 83
Chrome version: 84.0.4115.5 Channel: dev
$ chromium-browser --temp-profile
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:600:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:787:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.511: Theme parsing
error: gtk.css:1096:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1096:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1099:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4428:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4428:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4499:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4549:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing error:
gtk.css:4549:12: Expected a string.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open i915 (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: i915
MESA-LOADER: failed to open kms_swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[21919:21919:0421/034207.195874:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.195989:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.197368:ERROR:CONSOLE(70)] "Uncaught TypeError:
Cannot read property 'setInspectedTabId' of undefined", source:
devtools://devtools/bundled/devtools_compatibility.js (70)
** Message: 03:42:21.246:
[Desktop-packages] [Bug 1873996] Re: DevTools does not open at 84.0.4115.5
Some progress at last: using the Node.js binary downloaded by the
chromium build tools (third_party/node/update_node_binaries) generates a
complete devtools_resources.pak, as opposed to using the older, system-
wide binary (/usr/bin/node).
This patch (https://bazaar.launchpad.net/~chromium-team/chromium-browser
/bionic-dev/view/head:/debian/patches/node-use-system-wide.patch) is
what causes the build to use the system-wide version. We could probably
use nodejs-mozilla instead, which is at version 12.16.1 in
{xenial,bionic}-{security,updates}.
--
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/1873996
Title:
DevTools does not open at 84.0.4115.5
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
https://bugs.chromium.org/p/chromium/issues/detail?id=1072187
Steps to reproduce the problem:
1. Ctrl+Shift+I or right-click, click Inspect
2. Navigate to chrome://inspect/#pages, click inspect
3.
What is the expected behavior?
DevTools to open
What went wrong?
DevTools does not open.
Did this work before? Yes Chromium 83
Chrome version: 84.0.4115.5 Channel: dev
$ chromium-browser --temp-profile
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:600:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:787:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.511: Theme parsing
error: gtk.css:1096:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1096:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1099:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4428:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4428:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4499:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4549:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing error:
gtk.css:4549:12: Expected a string.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open i915 (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: i915
MESA-LOADER: failed to open kms_swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[21919:21919:0421/034207.195874:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime'
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
The problem persists in Ubuntu 20.04 as well.
I attempted to investigate this issue a little further, found that it is
caused by a race condition between gvfsd and ibus-daemon, and filed a
bug report upstream: https://gitlab.gnome.org/GNOME/gvfs/-/issues/481
My current workaround is hack, but it works:
Add this line to the [Service] section in /usr/lib/systemd/user/gvfs-
daemon.service:
ExecStartPre=bash -c "for i in echo {1..20} ; do ps ax | grep -q
\"^${USER}\b.*[i]bus-daemon\" || sleep 0.1 ; done"
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #481
https://gitlab.gnome.org/GNOME/gvfs/-/issues/481
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1779890
Title:
Nautilus does not use a valid Kerberos ticket when accessing Samba
share
Status in gvfs package in Ubuntu:
Confirmed
Bug description:
Nautilus prompts for username and password when accessing a Samba
share on a network drive, despite having a perfectly valid unexpired
Kerberos ticket. The Kerberos ticket is obtained automatically at
logon by authentication against a Samba Active Directory server (Samba
AD-DC).
Accessing the same Samba share with the same Kerberos ticket via
"smbclient //host/sharename -k" works fine.
One known workaround is: "nautilus -q", and then "killall gvfsd".
After that, accessing the Samba share with Nautilus works normally as
it should.
I did not experience this issue in Ubuntu 16.04. It appears that a
regression was introduced somewhere between 16.04 and 18.04.
The issue is quite annoying and confusing for the users who are used
to accessing Samba shares on the network drive without being prompted
for their username and password.
The issue appears to manifest itself usually not on the first access
to a Samba share, but on subsequent accesses after a system reboot or
upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry
file before user login appears to fix the issue for the current user
session, but then the problem reappears upon subsequent user logins or
after a system reboot.
Nemo appears to have the same problem as Nautilus.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs-daemons 1.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 3 11:12:06 2018
ExecutablePath: /usr/lib/gvfs/gvfsd
InstallationDate: Installed on 2018-04-27 (66 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
LANG=en_CA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873514] Re: Ubuntu uses insecure FreeRDP version
You can get untested packages in the security team PPA here: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1873514 Title: Ubuntu uses insecure FreeRDP version Status in freerdp2 package in Ubuntu: Confirmed Bug description: FreeRDP has been released some days ago and fixes several security issues as can be seen at https://github.com/FreeRDP/FreeRDP/blob/2.0.0/ChangeLog. However Ubuntu and in particular 20.04 does not yet provide the released version but uses an outdated version. Please upgrade to the released version of FreeRDP before releasing 20.04. Thanks, Joachim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1873514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881175] [NEW] nautilus doesnt start
Public bug reported: for an unknown cause nautilus does not want to start, after a reboot it works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 20:01:29 2020 InstallationDate: Installed on 2020-01-14 (135 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-12 (16 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1881175 Title: nautilus doesnt start Status in nautilus package in Ubuntu: New Bug description: for an unknown cause nautilus does not want to start, after a reboot it works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 20:01:29 2020 InstallationDate: Installed on 2020-01-14 (135 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-12 (16 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
The 'pcscd' group was used in a previous/old version of pcsc-lite. It should not be used anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 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: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873514] Re: Ubuntu uses insecure FreeRDP version
Thanks much appreciated. I've got a development build from the freerdp- daily PPA but it's pretty clear that the symbols still need appropriate mapping. The Debian build has some it for the 2.1.0 build they started. It's clearly some kind of backwards compatibility logic but I'm unclear on intent. I'm still trying to figure out if the new freerdp2-2.1.1 package really should have libswscale support. That is desirable to the guacamole package but it is unclear if that package will need the support in freerdp2. I suspect it would be easy to add with a libswscale-dev build require to freerdp2's packaging and it should pick it up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1873514 Title: Ubuntu uses insecure FreeRDP version Status in freerdp2 package in Ubuntu: Confirmed Bug description: FreeRDP has been released some days ago and fixes several security issues as can be seen at https://github.com/FreeRDP/FreeRDP/blob/2.0.0/ChangeLog. However Ubuntu and in particular 20.04 does not yet provide the released version but uses an outdated version. Please upgrade to the released version of FreeRDP before releasing 20.04. Thanks, Joachim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1873514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881160] [NEW] /usr/lib/libreoffice/program/soffice.bin:11:sd::DrawViewShell::GetMenuStateSel:sd::DrawViewShell::GetMenuState:SfxShell::CallState:SfxDispatcher::FillState_:SfxB
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.3-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/fe2f7df75423766c84c41e4c3ccadebf515e3f46 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/. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic disco eoan focal yakkety -- 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/1881160 Title: /usr/lib/libreoffice/program/soffice.bin:11:sd::DrawViewShell::GetMenuStateSel:sd::DrawViewShell::GetMenuState:SfxShell::CallState:SfxDispatcher::FillState_:SfxBindings::Update_Impl Status in libreoffice package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.3-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/fe2f7df75423766c84c41e4c3ccadebf515e3f46 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/libreoffice/+bug/1881160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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%
After more than one month, what is the state of this bug? -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter 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 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
@Ludovic Rousseau (ludovic-rousseau-gmail) You are right, but they share the same source package https://packages.ubuntu.com/source/focal/pcsc-cyberjack . For me here the main question is - which application creates `pcscd` group first time? Or it should be created by user manually on first time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 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: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 Thank you Simon Déziel you saved my life!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
The issue should be reassigned to libifd-cyberjack6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 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: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
On old system I see that `pcscd` group GID was 145. So the simple command below will fix the issue: ``` sudo groupadd -g 145 pcscd ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 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: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
** Changed in: ubuntu-drivers-common (Ubuntu Groovy) Status: Fix Released => Confirmed -- 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/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-drivers-common source package in Groovy: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? EDIT: bug confirmed as affecting the following Intel wireless adapter cards, and assumedly more to come: Intel Wi-Fi 6 AX200 Intel Dual Band Wireless-AC 3165 Intel Dual Band Wireless-AC 7260 Intel Dual Band Wireless-AC 8260 Intel Wireless-AC 9260 Also for reference here are the specs of Intel adapter cards: ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1859308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881142] [NEW] Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
Public bug reported: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 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: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcsc-cyberjack (Ubuntu) Importance: Undecided Status: New ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Also affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal
[Desktop-packages] [Bug 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems
Steve: I already have a commit that gets rid of dpkg-architecture, and removes the dependency. -- 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/1880564 Title: ubuntu-drivers-common now pulls in build tools on end-user systems Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Focal: Triaged Bug description: In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of build-essential on upgrades (or just binutils and make and patch if you pass --no-install-recommends). This needs to be reverted and fixed differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743179] Re: package libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 failed to install/upgrade: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current
** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1743179 Title: package libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 failed to install/upgrade: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in mesa package in Ubuntu: Invalid Bug description: I dont know further about this issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 13 15:21:58 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 libglapi-mesa 17.2.4-0ubuntu1~16.04.2 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libgles2-mesa:amd64:17.2.4-0ubuntu1~16.04.2 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libgles2-mesa:amd64 (--configure): package libgles2-mesa:amd64 is not ready for configuration ErrorMessage: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current status 'half-installed') GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81eb] InstallationDate: Installed on 2017-12-01 (43 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed root=UUID=4a5683fe-8ecb-454c-a223-c9217cacacfd ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: mesa Title: package libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 failed to install/upgrade: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.41:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jan 14 09:23:45 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1671 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1743179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730065] Re: Hedgewars crashing starting a game on artful
assuming it's fixed by now ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1730065 Title: Hedgewars crashing starting a game on artful Status in mesa package in Ubuntu: Invalid Bug description: After I upgraded to Artful I noticed the Hedgewars game crashing while starting a new game. After some debugging I found this happens in the following library: Program received signal SIGSEGV, Segmentation fault. 0xb0fd2a75 in ?? () from /usr/lib/i386-linux-gnu/dri/i965_dri.so It is from libgl1-mesa-dri package (version 17.2.2-0ubuntu1). So I decided to roll this package back to previous version. I downloaded and installed the following packages from Zesty: - libgl1-mesa-dri_17.0.3-1ubuntu1_i386.deb - libegl1-mesa_17.0.3-1ubuntu1_i386.deb - libgbm1_17.0.3-1ubuntu1_i386.deb - libllvm4.0_4.0-1ubuntu1_i386.deb And this solved the issue. Below some technical details. Please let me know if you need something else. Distro: Ubuntu 17.10 Architecture: i386 MachineType: Acer Extensa 5620 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (primary) [1025:011f] Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1025:011f] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1730065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749449] Re: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which i
I believe this was a bug in apt/dpkg ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1749449 Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1 -mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 Status in mesa package in Ubuntu: Invalid Bug description: Error occurred when running the software updater this morning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 14 08:00:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-32-generic, x86_64: installed DuplicateSignature: package:libgl1-mesa-dri:17.2.8-0ubuntu0~16.04.1 Unpacking libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1) over (17.2.8-0ubuntu0~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] [1002:682b] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Pegatron Venus LE [Radeon HD 8830M] [1b0a:90f3] InstallationDate: Installed on 2014-09-06 (1256 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: HP 510-p127c ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=3dd39524-3a29-4831-9f5a-6decde86d996 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: mesa Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: CNV64609PD dmi.board.name: 822A dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV64609PD dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.14:bd10/07/2016:svnHP:pn510-p127c:pvr:rvnHP:rn822A:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p127c dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 xserver.bootTime: Sun Jan 28 01:00:43 2018 xserver.configfile: default xserver.errors: RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748667] Re: package libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar
me neither ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1748667 Title: package libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in mesa package in Ubuntu: Invalid Bug description: nothing i know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 7 06:24:32 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ErrorMessage: problemas de dependencias - se deja sin configurar GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Trinity [Radeon HD 7600G] [1025:0756] InstallationDate: Installed on 2018-02-02 (8 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire V5-551 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: mesa Title: package libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd09/06/2012:svnAcer:pnAspireV5-551:pvrV2.06:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire V5-551 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 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 xserver.bootTime: Sat Feb 10 16:25:08 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1748667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
I can confirm this bug on a life-system xubuntu 20.04. In addition to the increase of one month in date modified, sometimes the date accessed shows "1979-12-31 00:00:00" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: New Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831762] Re: package tex-common 6.04 failed to install%2rade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tex-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1831762 Title: package tex-common 6.04 failed to install%2rade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: Confirmed Bug description: An upgrade from Ubuntu 16 to Ubuntu 18 was blocked by this package failing to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: tex-common: Configure texlive-generic-recommended: Configure texlive-latex-base: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 5 10:35:51 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-07-16 (2149 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-06-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1831762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857197] Re: an update only did a partial a year ago. have had nothing but problems since package tex-common 6.09 failed to install/upgrade: installed tex-common package post-i
*** This bug is a duplicate of bug 1746865 *** https://bugs.launchpad.net/bugs/1746865 ** This bug has been marked a duplicate of bug 1746865 package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1857197 Title: an update only did a partial a year ago. have had nothing but problems since package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: I love Ubuntu but would like to have one as close to windows as possible with features and ease of use so the wife and kids won't complain and abandon it so much. I've had nothing but problems for the last year since I did an update. Patches haven't worked. I might resort to the nuclear option and just burn a new ISO and reformat my hard drive, losing all my files over the years and start from scratch. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Dec 21 14:21:44 2019 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2012-09-20 (2648 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1857197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835052] Re: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1831762 *** https://bugs.launchpad.net/bugs/1831762 ** This bug has been marked a duplicate of bug 1831762 package tex-common 6.04 failed to install%2rade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1835052 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: I had that error when upgrading from 16.04 to 18.04. Upgrade has been discontinued. What should I do to upgrade to 18.04? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jul 2 14:38:49 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-01-19 (1989 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-07-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1835052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881131] Re: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1746865 *** https://bugs.launchpad.net/bugs/1746865 ** This bug has been marked a duplicate of bug 1746865 package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1881131 Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Report from installation ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 28 04:03:25 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-04 (2946 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.6.12ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-22 (553 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1881131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839304] Re: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1746865 *** https://bugs.launchpad.net/bugs/1746865 ** This bug has been marked a duplicate of bug 1746865 package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1839304 Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Don't know much about it. It just came up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tnef: Install tex-common: Configure lmodern: Configure tnef: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 6 20:36:49 2019 DpkgHistoryLog: Start-Date: 2019-08-06 20:36:35 Commandline: apt-get install tnef Requested-By: drshred (1000) Install: tnef:amd64 (1.4.12-1.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-04 (2651 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-22 (258 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1839304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881129] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug
** Tags removed: need-duplicate-check -- 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/1881129 Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug Status in lightdm package in Ubuntu: New Bug description: u ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: lubuntu-desktop: Purge lubuntu-default-session: Purge lubuntu-core: Purge lubuntu-default-settings: Purge lightdm: Purge Architecture: i386 Date: Thu May 28 13:54:09 2020 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2014-09-27 (2069 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=marleen autologin-user-timeout=0 autologin-session=lightdm-autologin LightdmGreeterLog: ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.24 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1881129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881131] [NEW] package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1746865 *** https://bugs.launchpad.net/bugs/1746865 Public bug reported: Report from installation ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 28 04:03:25 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-04 (2946 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.6.12ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-22 (553 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1881131 Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Report from installation ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 28 04:03:25 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-04 (2946 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.6.12ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-22 (553 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1881131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881129] [NEW] package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug
Public bug reported: u ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: lubuntu-desktop: Purge lubuntu-default-session: Purge lubuntu-core: Purge lubuntu-default-settings: Purge lightdm: Purge Architecture: i386 Date: Thu May 28 13:54:09 2020 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2014-09-27 (2069 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=marleen autologin-user-timeout=0 autologin-session=lightdm-autologin LightdmGreeterLog: ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.24 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- 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/1881129 Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug Status in lightdm package in Ubuntu: New Bug description: u ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: lubuntu-desktop: Purge lubuntu-default-session: Purge lubuntu-core: Purge lubuntu-default-settings: Purge lightdm: Purge Architecture: i386 Date: Thu May 28 13:54:09 2020 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2014-09-27 (2069 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=marleen autologin-user-timeout=0 autologin-session=lightdm-autologin LightdmGreeterLog: ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.24 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1881129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881122] [NEW] [Ubuntu Audio Settings] Audio device switching not working correctly
Public bug reported: In Ubuntu 18.04 switching between audio devices worked flawlessly. After upgrading to 20.04 not so much: When I try to switch between Logitech G930 and Soundblaster X-FI Audio devices, either the system sounds and/or programs which are already started do not playback any sounds. In some cases, system sounds (incl. the sound test) do not play, but programs do. It is really weird and I have a hard time reproducing the issue as well as the solution. Sometimes I play around with alsamixer and switch between the selected sound devices there and afterwards switch the device in the settings panel. It then more often than not works again as intended. If you have any suggestions on how to run down further details for this bug to enable you to bugfix this, tell me and I will try to provide further info. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 14:36:05 2020 InstallationDate: Installed on 2020-02-13 (105 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful Symptom_Card: G930 - Logitech G930 Headset Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - Logitech G930 Headset, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881122 Title: [Ubuntu Audio Settings] Audio device switching not working correctly Status in alsa-driver package in Ubuntu: New Bug description: In Ubuntu 18.04 switching between audio devices worked flawlessly. After upgrading to 20.04 not so much: When I try to switch between Logitech G930 and Soundblaster X-FI Audio devices, either the system sounds and/or programs which are already started do not playback any sounds. In some cases, system sounds (incl. the sound test) do not play, but programs do. It is really weird and I have a hard time reproducing the issue as well as the solution. Sometimes I play around with alsamixer and switch between the selected sound devices there and afterwards switch the device in the settings panel. It then more often than not works again as intended. If you have any suggestions on how to run down further details for this bug to enable you to bugfix this, tell me and I will try to provide further info. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 14:36:05 2020 InstallationDate: Installed on 2020-02-13 (105 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful Symptom_Card: G930 - Logitech G930 Headset Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - Logitech G930 Headset, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock
[Desktop-packages] [Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color in artful
This happened to me just now on a fresh installation of 20.04. Exactly as reported - first attempt at calibration with a Spyder 3 fails, on the second attempt gnome-control-center crashes hard. -- 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/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color in artful Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Fresh install of Artful, using gnome-session to access vanilla GNOME session on Wayland (also tried on xorg). Attempting to calibrate monitors through Gnome Control Center->Devices->Color. All attempts ended at the point where I was asked to put the device onto the monitor, with the error: Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device. Syslog: Sep 24 12:19:31 desktop kernel: [ 262.849675] usb 3-6: new full-speed USB device number 7 using xhci_hcd Sep 24 12:19:32 desktop kernel: [ 262.990880] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:19:32 desktop kernel: [ 262.990882] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:19:32 desktop kernel: [ 262.990884] usb 3-6: Product: colormunki Sep 24 12:19:32 desktop kernel: [ 262.990885] usb 3-6: Manufacturer: X-Rite Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop gnome-shell[876]: drmModeSetCursor2 failed with (Permission denied), drawing cursor with OpenGL from now on Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) I attempted to fix the permissions error for /dev/dri/card0. Current permissions: rwh@desktop:~$ ls -l /dev/dri/card0 crw-rw+ 1 root video 226, 0 Sep 24 12:15 /dev/dri/card0 Tried adding my user to video group, which made no difference. Then made file world r/w: rwh@desktop:~$ sudo chmod o+rw /dev/dri/card0 Which fixed that problem. Now, in the calibrate wizard, on the second step (Display Type) I am offered three options (LCD, CRT, Projector) where I only saw LCD previously. However, the calibration step failed the same as before. Syslog: Sep 24 12:36:46 desktop kernel: [ 1298.430546] usb 3-6: new full-speed USB device number 12 using xhci_hcd Sep 24 12:36:46 desktop kernel: [ 1298.571756] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:36:46 desktop kernel: [ 1298.571759] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:36:46 desktop kernel: [ 1298.571760] usb 3-6: Product: colormunki Sep 24 12:36:46 desktop kernel: [ 1298.571762] usb 3-6: Manufacturer: X-Rite Sep 24 12:36:46 desktop pulseaudio[953]: message repeated 3 times: [ W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Sep 24 12:36:47 desktop gnome-control-c[5206]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:36:47 desktop gnome-control-c[5206]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:37:21 desktop dbus-daemon[4121]: Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' Sep 24 12:37:21 desktop systemd[3601]: Starting Color management helper... Sep 24 12:37:21 desktop dbus-daemon[4121]: Successfully activated service 'org.freedesktop.ColorHelper'
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
I am on Ubuntu FF 20.04 using office 2010 via wine-stable 5.0, my system is fully updated. The issue still persists when I am copying and pasting any text within word 2010, with an interesting twist. Copying and pasting works most of the times, but when I copy a portion of text within Word 2010 using ctrl+C then delete it and try paste it, it always fails. As if by deleting the text I just copied from the page I would also delete its copy in the clipboard. When I am in Unity (yeah, I still love and use Unity, even on 20.04) everything works as intended: you copy a portion of the text and can always paste it, no matter what you do to the original text. Hope this helps, this bug is so very annoying. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881115] [NEW] desktop - no shift-delete, non localized menu
Public bug reported: Hi, i've noticed 2 problems on desktop (gnome-flashback), which is imho handled by nautilus... - contextmenu (rightclick) is not localized (german environment, menu is english) - shift-delete does nothing, in menu there is only "move to trash" (+open +properties), no way to delete files without trash regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Thu May 28 14:12:30 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-04-27 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1881115 Title: desktop - no shift-delete, non localized menu Status in nautilus package in Ubuntu: New Bug description: Hi, i've noticed 2 problems on desktop (gnome-flashback), which is imho handled by nautilus... - contextmenu (rightclick) is not localized (german environment, menu is english) - shift-delete does nothing, in menu there is only "move to trash" (+open +properties), no way to delete files without trash regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Thu May 28 14:12:30 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-04-27 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
MS teams & magnet: links both just throw up a "xdg-open" prompt but nothing happens when you "allow". This should be fixed and released now, right ? -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853008] Re: Chromium-browser from snap is not opening xdg-open
*** This bug is a duplicate of bug 1776873 *** https://bugs.launchpad.net/bugs/1776873 MS Teams also has this problem. -- 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/1853008 Title: Chromium-browser from snap is not opening xdg-open Status in chromium-browser package in Ubuntu: Confirmed Bug description: I've Zoom messenger installed and in previous Ubuntu instalation I had chromium probably not from snap store. Now I'm on fresh Ubuntu 19.10 and zoom links opened in the chromium from snap store are showing prompt to open xdg-open, but after clicking it to open, nothing happens - the website is unable to launch the Zoom transmission. xdg is installed, /usr/share/applications/Zoom.desktop is available ``` Name=Zoom Comment=Zoom Video Conference Exec=/usr/bin/zoom %U Icon=Zoom.png Terminal=false Type=Application Encoding=UTF-8 Categories=Network;Application; StartupWMClass=Zoom MimeType=x-scheme-handler/zoommtg;application/x-zoom; X-KDE-Protocols=zoommtg Name[en_US]=Zoom ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880411] Re: Support both Super keys simultaneously on org.gnome.mutter overlay-key
Yes, thanks for adding this to mutter's gitlab issue tracker. -- 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/1880411 Title: Support both Super keys simultaneously on org.gnome.mutter overlay-key Status in Mutter: Unknown Status in gnome-tweaks package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: The right super key doesn't show the overlay. Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver
** Description changed: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot + + * install updated linux-firmware and pulseaudio +$ sudo add-apt-repository ppa:kchsieh/training +$ sudo apt-get update +$ sudo apt install linux-firmware +$ sudo apt install pulseaudio +$ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 -- 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/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver
** Changed in: pulseaudio (Ubuntu) Assignee: Kai-Chuan Hsieh (kchsieh) => (unassigned) ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) ** Description changed: [Impact] - * Some Intel platform bionic user audio function will be broken after + * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 - * pulseaudio can't find working profile, since card name is changed in + * pulseaudio can't find working profile, since card name is changed in kernel 5.4 - [Test Case] - * install kernel 5.4 and check audio function -$ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 -$ sudo apt-get update -$ sudo apt install linux-header-5.4.0-31-generic -$ sudo apt install linux-image-generic-hwe-18.04-wip -$ sudo reboot + * install kernel 5.4 and check audio function + $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 + $ sudo apt-get update + $ sudo apt install linux-header-5.4.0-31-generic + $ sudo apt install linux-image-generic-hwe-18.04-wip + $ sudo reboot - * test items -1. check internal speaker/mic to playback and record audio -2. plug headset and check headset functions -3. plug HDMI from external monitor/TV, and check audio functions -4. 1, 2, 3 works fine after resume from S3 -5. 1, 2, 3 works fine after resume from S2idle + * test items + 1. check internal speaker/mic to playback and record audio + 2. plug headset and check headset functions + 3. plug HDMI from external monitor/TV, and check audio functions + 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] - * The updated pulseaudio breaks audio function on old kernel + * The updated pulseaudio breaks audio function on old kernel [Scope] - * Need for bionic only + * Need for bionic only [Bug Discussion] - - * https://bugs.launchpad.net/timbuktu/+bug/1880632 - * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 + + * https://bugs.launchpad.net/timbuktu/+bug/1880632 + * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 -- 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/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- 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/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from S3 5. 1, 2, 3 works fine after resume from S2idle [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver
** Also affects: oem-priority Importance: Undecided Status: New -- 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/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from S3 5. 1, 2, 3 works fine after resume from S2idle [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 599125] Re: [mach64] unsupported Rage Mobility P/M AGP 2x
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/599125 Title: [mach64] unsupported Rage Mobility P/M AGP 2x Status in mesa package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-ati I tried to use a Microsoft Windows program through Wine. I got the below error messages: - err:winediag:X11DRV_WineGL_InitOpenglInfo The Mesa OpenGL driver is using software rendering, most likely your OpenGL drivers haven't been installed correctly fixme:d3d_caps:wined3d_guess_card No card selector available for GL vendor 4 and card vendor . fixme:win:EnumDisplayDevicesW ((null),0,0x32e250,0x), stub! fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x19e078,0x19e000): stub fixme:bitblt:client_side_dib_copy potential optimization: client-side color-index mode DIB copy fixme:bitblt:client_side_dib_copy potential optimization: client-side color-index mode DIB copy fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0xdece40,0xc8df78): stub fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0xdece40,0xc8df78): stub - ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 CurrentDmesg: Date: Sun Jun 27 21:56:43 2010 DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type InstallationMedia: Xubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Sony Corporation PCG-FX301(FR) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=cc325b47-77d9-4b57-98af-0db1393969c6 ro quiet splash ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati dmi.bios.date: 07/04/2001 dmi.bios.vendor: Sony Corporation dmi.bios.version: R0104K5 dmi.board.name: QII-Project dmi.board.vendor: Sony Corporation dmi.board.version: 1A dmi.chassis.asset.tag: 962C8394A0505800 dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnSonyCorporation:bvrR0104K5:bd07/04/2001:svnSonyCorporation:pnPCG-FX301(FR):pvr01:rvnSonyCorporation:rnQII-Project:rvr1A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: PCG-FX301(FR) dmi.product.version: 01 dmi.sys.vendor: Sony Corporation glxinfo: Error: [Errno 2] Aucun fichier ou dossier de ce type system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/599125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 573196] Re: Launch command "cairo-dock -O" : ubuntu's session crashes and restarts
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/573196 Title: Launch command "cairo-dock -O" : ubuntu's session crashes and restarts Status in mesa package in Ubuntu: Invalid Bug description: Architecture: i386 DistroRelease: Ubuntu 10.04 Package: 2.1.4-0beta1-20100426-0ubuntu1~ppa0~lucid ProblemType: Session crash ProcCmdline: cairo-dock -O Window Manager: Compiz Desktop Environment: Gnome Video Card: Ati M R X300 So, when I launch the command "cairo-dock -O" (-O for use indirect rendering), ubuntu's session crashes and restarts. On the contrary, "cairo-dock -c" works properly (the dock appears correctly with cairo backend) and "cairo-dock -o" too but with some graphical problems (openGL backend, other bug with ati driver). You can found different logs (/var/log/Xorg.0* , /var/log/Xorg.failsafe.log* and ~/.xsession-errors*) here --> http://dl.free.fr/pu0g0saQK Thanks ! --- Architecture: i386 CurrentDmesg: [ 39.502144] ppdev: user-space parallel port driver [ 40.816175] b44: eth0: Link is up at 100 Mbps, full duplex. [ 40.816179] b44: eth0: Flow control is off for TX and off for RX. [ 40.816456] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 51.504027] eth0: no IPv6 routers present DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type MachineType: Acer, inc. Aspire 1650 Package: mesa (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: root=UUID=310300e1-4cf9-4c18-aefa-7ed72b740cca ro quiet splash vga=771 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en LANG=fr_FR.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-21-generic i686 UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 08/31/05 dmi.bios.vendor: Acer dmi.bios.version: 3A33 dmi.board.name: Crane II dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: , Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr3A33:bd08/31/05:svnAcer,inc.:pnAspire1650:pvrNotApplicable:rvnAcer,Inc.:rnCraneII:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 1650 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic --- Architecture: i386 CurrentDmesg: [ 39.502144] ppdev: user-space parallel port driver [ 40.816175] b44: eth0: Link is up at 100 Mbps, full duplex. [ 40.816179] b44: eth0: Flow control is off for TX and off for RX. [ 40.816456] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 51.504027] eth0: no IPv6 routers present DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type MachineType: Acer, inc. Aspire 1650 Package: mesa (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: root=UUID=310300e1-4cf9-4c18-aefa-7ed72b740cca ro quiet splash vga=771 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en LANG=fr_FR.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-21-generic i686 UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 08/31/05 dmi.bios.vendor: Acer dmi.bios.version: 3A33 dmi.board.name: Crane II dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: , Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr3A33:bd08/31/05:svnAcer,inc.:pnAspire1650:pvrNotApplicable:rvnAcer,Inc.:rnCraneII:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 1650 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/573196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681129] Re: debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch
** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1681129 Title: debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch Status in mesa package in Ubuntu: Invalid Bug description: Running debsums on my machine report that /usr/lib/x86_64-linux- gnu/old.libgbm.so.1.0.0 has changed. Sadly even running "apt-get install --reinstall libgbm1-lts-wily:amd64 libgbm1:amd64" does not fix the problem. (BTW, I cannot report this against the libgbm1 package, because Launchpad is saying that '"libgbm1" does not exist in Ubuntu.') ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgbm1 10.1.3-0ubuntu0.6 [modified: usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0] ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 8 11:44:48 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: isgx, 0.10, 4.2.0-27-generic, x86_64: installed (WARNING! Diff between built and installed module!) isgx, 0.10, 4.2.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06fd] InstallationDate: Installed on 2016-05-02 (340 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Inspiron 13-7359 ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=bc09f41a-6b3d-47f9-b01d-9ac1dce625eb ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0110N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0110N8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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 xserver.bootTime: Thu Feb 23 08:37:58 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 34381 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1681129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054624] Re: compiz crashed with SIGILL in llvm_pipeline_generic() from llvm_middle_end_linear_run() from vsplit_segment_simple_linear() from vsplit_run_linear() from draw_pt_a
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1054624 Title: compiz crashed with SIGILL in llvm_pipeline_generic() from llvm_middle_end_linear_run() from vsplit_segment_simple_linear() from vsplit_run_linear() from draw_pt_arrays() from draw_vbo() Status in mesa package in Ubuntu: Invalid Bug description: Running from virtualbox - immediately after login ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: compiz-core 1:0.9.8.2+bzr3377-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 37.342717] init: plymouth-stop pre-start process (1230) terminated with status 1 Date: Sat Sep 22 11:16:18 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120922) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: Compiz ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-15-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 Signal: 4 SourcePackage: compiz StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so Title: compiz crashed with SIGILL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8.2+bzr3377-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120917.7cfd42ce-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.8-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1054624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 696427] Re: Unity visual glitches and freeze (libgl1-dri-mesa-experimental)
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/696427 Title: Unity visual glitches and freeze (libgl1-dri-mesa-experimental) Status in Mesa: New Status in Nouveau Xorg driver: New Status in Unity: Incomplete Status in mesa package in Ubuntu: Invalid Status in unity package in Ubuntu: Incomplete Bug description: Binary package hint: unity Using Nouveau drivers and libgl1-dri-mesa-experimental package on a Nvidia 250GTS I get visual artefacts in Unity and a total freeze of the system (I've to hard reset PC). Sorry for low quality images but print screen doesn't work! ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.2.8-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 Uname: Linux 2.6.37-11-generic i686 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/allscreens/options/active_plugins' Date: Sun Jan 2 10:19:28 2011 MachineType: System manufacturer System Product Name PciDisplay: 02:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) ProcEnviron: LANGUAGE=it_IT:it:en_GB:en LANG=it_IT.UTF-8 LC_MESSAGES=it_IT.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=0a53d971-02eb-421b-8e6c-a3b9a0033ad2 ro vt.handoff=7 splash quiet ProcVersionSignature_: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 RelatedPackageVersions: xserver-xorg 1:7.5+6ubuntu6 libgl1-mesa-glx 7.9+repack-1ubuntu3 libdrm2 2.4.22-2ubuntu1 xserver-xorg-video-intel 2:2.13.901-2ubuntu2 xserver-xorg-video-ati 1:6.13.2-1ubuntu2 SourcePackage: unity XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 05/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N78 SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd05/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer glxinfo: Error: [Errno 2] No such file or directory system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-11-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/696427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 905972] Re: cheese crashed with SIGSEGV in parseOptInfoAttr()
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/905972 Title: cheese crashed with SIGSEGV in parseOptInfoAttr() Status in mesa package in Ubuntu: Invalid Bug description: Additional information foor the Cheese crash report. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Dec 18 15:43:28 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: System Manufacturer System Name ProcCmdline: cheese RelatedPackageVersions: cheese3.2.0-0ubuntu2 cheese-common 3.2.0-0ubuntu2 SegvAnalysis: Segfault happened at: 0x723a126: mov0x19c(%eax),%eax PC (0x0723a126) ok source "0x19c(%eax)" (0x019c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so intelMakeCurrent () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: cheese crashed with SIGSEGV in intelMakeCurrent() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/28/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4BGL-VM ACPI BIOS Revision 1006 Beta 002 dmi.board.name: P4BGL-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4BGL-VMACPIBIOSRevision1006Beta002:bd11/28/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4BGL-VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 04c8:0720 Konica Corp. Digital Color Camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/905972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately
** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/455954 Title: [K8M800] AntSpotlight screensaver causes system to lock up immediately Status in linux package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in xserver-xorg-video-openchrome package in Ubuntu: Fix Released Bug description: Note: this bug just reappeared in Xubuntu 11.10. I filed this as a new bug #871471. Binary package hint: xscreensaver Selecting AntSpotlight in either xscreensaver or Gnome Screensaver causes this system to freeze immediately. Ubuntu version and kernel version, etc. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.10 DISTRIB_CODENAME=karmic DISTRIB_DESCRIPTION="Ubuntu karmic (development branch)" Linux cupid 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux model name: Mobile AMD Sempron(tm) Processor 2800+ At the moment, neither xscreensaver nor Gnome Screensaver is installed, but the package containing this screensaver (xscreensaver- gl) is still installed. (I am about to remove it). Since memory may be an issue, I'll enclose a copy of /proc/meminfo ProblemType: Bug Architecture: i386 Date: Mon Oct 19 18:07:43 2009 DistroRelease: Ubuntu 9.10 Package: xscreensaver-gl 5.08-0ubuntu5 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: xscreensaver Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (gnome-settings-daemon:2256): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:2332): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:2313): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/455954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 292010] Re: opengl error with i830_vtbl.c:465: i830_emit_state: Assertion `0' failed.
** Changed in: mesa (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/292010 Title: opengl error with i830_vtbl.c:465: i830_emit_state: Assertion `0' failed. Status in mesa package in Ubuntu: Won't Fix Bug description: Binary package hint: libgl1-mesa-dri this happens with my own OpenGL program on 8.10. I have been porting the program from Windows and from a more capable graphics card to Ubuntu and not so powerful Intel graphics chip, so it is quite possible that my program still has bugs in it. Still this failure is not proper way for OpenGL to behave. I probably should go with this directly to Mesa people? Eero [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:12bc] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:12bc] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/292010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 565658] Re: Desktop effects do not work because of software rendering
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/565658 Title: Desktop effects do not work because of software rendering Status in mesa package in Ubuntu: Invalid Bug description: Binary package hint: xorg When I am trying to run compiz manually, it complains about fatal error: software rendering. In Xorg.0.log I see (WW) RADEON(0): Direct rendering disabled But, strange enough, glxinfo says direct rendering: Yes Most probably Xorg.0.log is right, because the display is somewhat slow and desktop effects cannot be enabled. In 9.10 everything was fine. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-powerpc64-smp 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-powerpc64-smp ppc64 Architecture: powerpc Date: Sat Apr 17 23:51:33 2010 DkmsStatus: Error: [Errno 2] No such file or directory ProcCmdLine: root=/dev/sda3 ro ramdisk_size=8192 quiet splash ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: xserver-xorg 1:7.5+5ubuntu1 libgl1-mesa-glx 7.7.1-1ubuntu2 libdrm2 2.4.18-1ubuntu3 xserver-xorg-video-ati 1:6.13.0-1ubuntu5 xserver-xorg-video-nouveau N/A SourcePackage: xorg Symptom: display system: distro: Ubuntu codename: lucid architecture: ppc64 kernel: 2.6.32-21-powerpc64-smp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/565658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057309] Re: gnome-control-center crashed with SIGSEGV in intelDestroyContext()
** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1057309 Title: gnome-control-center crashed with SIGSEGV in intelDestroyContext() Status in mesa package in Ubuntu: Invalid Bug description: gnome-control-center crashed when i upgrade ubuntu from 12.04 into 12.10 beta ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu15 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Thu Sep 27 14:33:24 2012 Disassembly: => 0x37838dff: Cannot access memory at address 0x37838dff ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: gnome-control-center ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_US:en LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x37838dff:Cannot access memory at address 0x37838dff PC (0x37838dff) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () intelDestroyContext () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so Title: gnome-control-center crashed with SIGSEGV in intelDestroyContext() UpgradeStatus: Upgraded to quantal on 2012-09-25 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: gnome-session[1326]: WARNING: Session 'gnome' runnable check failed: Child process exited with code 1 (gnome-settings-daemon:1441): color-plugin-WARNING **: failed to get edid: unable to get EDID for output (gnome-panel:1603): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed (gnome-settings-daemon:1441): color-plugin-WARNING **: unable to get EDID for xrandr-VGA1: unable to get EDID for output (gnome-panel:1603): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.17-0ubuntu1 indicator-datetime 12.10.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1057309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060986] Re: kwin_opengl_test crashed with SIGSEGV in r600_bind_blend_state_internal()
** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1060986 Title: kwin_opengl_test crashed with SIGSEGV in r600_bind_blend_state_internal() Status in mesa package in Ubuntu: Invalid Bug description: kwin_opengl_test crashed with SIGSEGV in r600_bind_ps_state() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: kde-window-manager-common 4:4.9.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 16:01:36 2012 ExecutablePath: /usr/lib/kde4/libexec/kwin_opengl_test InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: /usr/lib/kde4/libexec/kwin_opengl_test SegvAnalysis: Segfault happened at: 0xb6d2cce6 :mov (%eax),%eax PC (0xb6d2cce6) ok source "(%eax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: kde-workspace StacktraceTop: r600_bind_ps_state (ctx=0x9d78090, state=0x0) at r600_state_common.c:866 r600_create_context (screen=0x9d737c8, priv=0x0) at r600_pipe.c:312 st_api_create_context (stapi=0xb7146380 , smapi=0x9d734c8, attribs=0xbfccdc14, error=0xbfccdc10, shared_stctxi=0x0) at ../../../../src/mesa/state_tracker/st_manager.c:633 dri_create_context (api=API_OPENGL, visual=0x9d76280, cPriv=0x9d737a8, major_version=1, minor_version=0, flags=0, error=0xbfccdcdc, sharedContextPrivate=0x0) at dri_context.c:119 dri2CreateContextAttribs (screen=screen@entry=0x9d73410, api=api@entry=0, config=config@entry=0x9d76280, shared=shared@entry=0x0, num_attribs=num_attribs@entry=0, attribs=attribs@entry=0x0, error=error@entry=0xbfccdcdc, data=data@entry=0x9d77d60) at ../../../../src/mesa/drivers/dri/common/dri_util.c:287 Title: kwin_opengl_test crashed with SIGSEGV in r600_bind_ps_state() UpgradeStatus: Upgraded to quantal on 2012-09-12 (21 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev root sambashare sudo www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1060986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130175] Re: [8xx mesa] Unity can't start on laptop
** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1130175 Title: [8xx mesa] Unity can't start on laptop Status in Compiz: New Status in mesa package in Ubuntu: Won't Fix Bug description: Unity can't start on laptop on 13.04 and there are no windows borders on windows. If I boot into Gnome2 without compiz - everything is normal. Ubuntu 12.10 Unity is working normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Tue Feb 19 17:16:11 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0071] Subsystem: Acer Incorporated [ALI] Device [1025:0071] InstallationDate: Installed on 2013-02-19 (0 days ago) InstallationMedia: 13.04-x86 13.04 - Release i386 Lsusb: Bus 001 Device 002: ID 8564:1000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer TravelMate 2350 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=4a347fe8-6dd7-4d1c-a8b7-59532b55ebaa ro noresume ipv6.disable=1 SourcePackage: xorg Symptom: display UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number of failed request: 32 Current serial number in output stream: 33 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2005 dmi.bios.vendor: Acer dmi.bios.version: V1.70 dmi.board.name: TravelMate 2350 dmi.board.vendor: Acer dmi.board.version: A0 dmi.chassis.asset.tag: modem dmi.chassis.type: 8 dmi.chassis.vendor: Acer dmi.chassis.version: A1 dmi.modalias: dmi:bvnAcer:bvrV1.70:bd01/03/2005:svnAcer:pnTravelMate2350:pvr290:rvnAcer:rnTravelMate2350:rvrA0:cvnAcer:ct8:cvrA1: dmi.product.name: TravelMate 2350 dmi.product.version: 290 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Tue Feb 19 16:59:39 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1130175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042211] Re: [quantal] [regression] [i915] Corrupted display, desktop and menus don't repaint correctly using Mesa 9.0 (8.0.4 works)
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1042211 Title: [quantal] [regression] [i915] Corrupted display, desktop and menus don't repaint correctly using Mesa 9.0 (8.0.4 works) Status in Compiz: Invalid Status in Mesa: Invalid Status in compiz package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: WORKAROUND: Download and install the old Mesa 8.0.4 packages for quantal from: https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1 or add the Unity staging PPA: sudo add-apt-repository ppa:unity-team/staging ORIGINAL DESCRIPTION: After installing the latest updates on Quantal, desktop fails to repaint correctly: - moving a window leave trails - plain color is displayed instead of custom background - menus are flickering ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8+bzr3319-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2 Uname: Linux 3.5.0-12-generic i686 ApportVersion: 2.5.1-0ubuntu2 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Aug 27 10:38:41 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209) MachineType: ASUSTeK Computer INC. 1015PE PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-12-generic root=UUID=014cdf46-1d84-4e78-a68e-5d6de3419ad9 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/31/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu2 version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1042211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180646] Re: cairo-dock rendering issues using openGL backend on intel GPU
** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: what is this bug ? when i had ubuntu 11.10 , i had a big slow motion that affect even the youtube videos and overall performance . and the error was the opengl, i know that because its version name was missing on 11.10 , any way after upgrade to 12.04 i though the error gone, and it does , my laptop was 10x faster . but i can't run cairo-dock in opengl mode !!!. the ghost came back :( old ubuntu 11.10 bug http://imageshack.us/photo/my-images/259/xorg.png/ new ubuntu 12.04 bug (the one i have right now ) http://imageshack.us/photo/my-images/844/screenshotfrom201305160.png/ my additional drivers pic here before upgrade from ubuntu 11.10 to 12.04 http://img94.imageshack.us/img94/8410/delldrivers.png after the upgrade http://imageshack.us/photo/my-images/39/screenshotfrom201305160.png/ - i have posted on the cairo-dock forums and they responded that this a common eror on hd 4000 and they sent me that link https://bugs.freedesktop.org/show_bug.cgi?id=55036 i looked at it and i found """Component:Drivers/DRI/i965""" i have read some on the report uploaded and i feel like i have mix between i915 and i965 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-43.68-generic 3.2.42 Uname: Linux 3.2.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None Date: Thu May 16 05:17:18 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0569] InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 MachineType: Dell Inc. Inspiron 5520 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-43-generic root=UUID=8b64b4b3-8de9-43d7-b1c8-7f9ff701ac70 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-05-05 (10 days ago) dmi.bios.date: 08/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 04G65K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/13/2012:svnDellInc.:pnInspiron5520:pvrA09:rvnDellInc.:rn04G65K:rvrA02:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 5520 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1~precise version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.0.1-0ubuntu1~precise version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1~precise version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.0-0ubuntu0~precise1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1307709] Re: webbrowser-app does not start in Unity 8 preview session
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1307709 Title: webbrowser-app does not start in Unity 8 preview session Status in Oxide: Fix Released Status in mesa package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: The webbrowser app does not start when invoked from the Dash in Unity8 in the preview session. Upon clicking the icon the screen quickly flickers and returns to the Dash. You can get some more information when running the terminal app. You can make this app usable by uncommenting X-Ubuntu-StageHint=SideStage. From the terminal, run: webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop This takes me back to the Dash, return to the terminal to find: libEGL warning: unsupported platform (null) libEGL warning: unsupported platform (null) Segmentation fault (core dumped) I am attaching one of the crash dumps To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1307709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1404696] Re: No vdpau for the utopic xstack in trusty
** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1404696 Title: No vdpau for the utopic xstack in trusty Status in mesa package in Ubuntu: Won't Fix Bug description: Hello, I have tested the utopic xstack in trusty in the Canonical X Staging ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging?field.series_filter=trusty . It installs fine with; LC_ALL=C apt-get install -V libglapi-mesa-lts-utopic libgl1-mesa-glx- lts-utopic xserver-xorg-lts-utopic xserver-xorg-input-all-lts-utopic xserver-xorg-video-all-lts-utopic libgl1-mesa-dri-lts-utopic libglapi- mesa-lts-utopic:i386 libgl1-mesa-dri-lts-utopic:i386 libgl1-mesa-glx- lts-utopic:i386 libgles2-mesa-lts-utopic libglapi-mesa-lts-utopic mesa-vdpau-drivers-lts-utopic libegl1-mesa-drivers-lts-utopic libwayland-egl1-mesa-lts-utopic But under vdpauinfo there are no decoder capabilities for a AMD Radeon 5550 (r600); Decoder capabilities: name level macbs width height --- With stock xstack; Decoder capabilities: name level macbs width height --- MPEG1 0 9216 2048 1152 MPEG2_SIMPLE 3 9216 2048 1152 MPEG2_MAIN3 9216 2048 1152 H264_BASELINE41 9216 2048 1152 H264_MAIN41 9216 2048 1152 H264_HIGH41 9216 2048 1152 VC1_SIMPLE1 9216 2048 1152 VC1_MAIN 2 9216 2048 1152 VC1_ADVANCED 4 9216 2048 1152 The total output of vdpauinfo is attached. Best regards, Bernhard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1404696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 534719] Re: [unichrome] netbook-launcher assert failure: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed.
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/534719 Title: [unichrome] netbook-launcher assert failure: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed. Status in Mesa: Unknown Status in mesa package in Ubuntu: Invalid Status in netbook-launcher package in Ubuntu: Invalid Status in mesa package in Debian: Fix Released Bug description: Binary package hint: netbook-launcher Started Lucid Alpha3 Netbook Edition (i386) on a VIA Epia system, booted from USB stick. It booted and can be used basically, but the whole "desktop" area does not react to clicks, and after a few minutes running it the Apport symbol came up for this crash. No idea what really caused this or what the netbook-launcher does. Currently, the "desktop" can be displayed but still does not react to clicks. ProblemType: Crash Architecture: i386 AssertionMessage: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed. Date: Mon Mar 8 22:33:57 2010 DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory ExecutablePath: /usr/bin/netbook-launcher GConfNonDefault: /apps/netbook-launcher/disable_single_instance=false /apps/netbook-launcher/force_low_graphics=false LiveMediaBuild: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100224.3) MachineType: VIA Technologies, Inc. VT8623-8235 Package: netbook-launcher 1:2.1.13-0ubuntu1 ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname-netbook.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de console-setup/layoutcode?=de ProcCmdline: netbook-launcher --show-favorites ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic RelatedPackageVersions: xserver-xorg 1:7.5+1ubuntu8 libgl1-mesa-glx 7.7-3ubuntu1 libdrm2 2.4.18-1ubuntu2 xserver-xorg-video-intel 2:2.9.1-1ubuntu6 Signal: 6 SourcePackage: netbook-launcher StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 __assert_fail () from /lib/tls/i686/cmov/libc.so.6 viaSwapOutWork () from /usr/lib/dri/unichrome_dri.so Title: netbook-launcher assert failure: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed. Uname: Linux 2.6.32-14-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/19/2004 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: EPIA-M dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd05/19/2004:svnVIATechnologies,Inc.:pnVT8623-8235:pvr:rvn:rnEPIA-M:rvr:cvn:ct3:cvr: dmi.product.name: VT8623-8235 dmi.sys.vendor: VIA Technologies, Inc. glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu architecture: i686kernel: 2.6.32-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/534719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
