Re: [Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
Hi There! Your PPA worked for me. Thanks a lot for this. Regards, Anubhav On Fri, May 1, 2020 at 11:45 PM Kai-Heng Feng wrote: > Please test PPA here: > https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1875032). > https://bugs.launchpad.net/bugs/1876065 > > Title: > After unplug headphones and plug them again no sound can be heard > > Status in pulseaudio package in Ubuntu: > Confirmed > > Bug description: > After startup with headset plugged in they play sound nicely - no > issue. When they are unplugged, the sound is switched to the speaker > (laptop) - all good. However, when I plug the headset back there is no > sound. I see the app on pavucontrol, the volume is fine - everything > looks fine except there is no sound. I dumped output of "pactl list" > command on startup (headset plugged), after unplugging the headset, > and when it is plugged back. From the comparison of these outputs, it > looks like the source has got muted after the headset is plugged. > > Source #1 > State: RUNNING > Name: alsa_input.pci-_00_1f.3.analog-stereo > Description: Built-in Audio Analog Stereo > Driver: module-alsa-card.c > Sample Specification: s16le 2ch 44100Hz > Channel Map: front-left,front-right > Owner Module: 7 > Mute: yes > > Attached three outputs: > headset-in.txt - after startup with headset plugged - all fine. > headset-out.txt - after unplugged headset - sound through the speaker - > all fine. > headset-back.txt - after plugged headset back - no sound. > > Any help greatly appreciated. > > Regards, > Roman > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions > -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Confirmed Bug description: After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876256] Re: SRU the current 3.36.2 stable update
** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu Focal) Assignee: (unassigned) => Sebastien Bacher (seb128) -- 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/1876256 Title: SRU the current 3.36.2 stable update Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: In Progress Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential Nothing specific to test in this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875625] Re: Libreoffice help not accessible
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1875625 Title: Libreoffice help not accessible Status in libreoffice package in Ubuntu: Confirmed Bug description: I have a completely fresh install of Ubuntu 20.04 using Gnome 3.36.1. Libreoffice Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 Within all four packages (Calc, Writer, Draw and Impress), if I press F1 for the help screens, I expect the help screens to appear however I receive the following message:- Object not accessible. The object cannot be accessed due to insufficient user rights. I started Libreoffice in safe mode and the help screens also did not load. I also double checked a "live" session and the help screens were also inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
This bug was fixed in the package network-manager - 1.22.10-1ubuntu3 --- network-manager (1.22.10-1ubuntu3) groovy; urgency=medium * No-change rebuild to bump Groovy version number. network-manager (1.22.10-1ubuntu2) focal; urgency=medium * d/t/killswitches-no-urfkill - Call udevadm settle before nmcli radio wifi To make sure that change is updated. (LP: #1733321) -- Dan Streetman Thu, 30 Apr 2020 07:47:49 -0400 ** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but t
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
This bug was fixed in the package gnome-control-center - 1:3.36.2-1ubuntu1 --- gnome-control-center (1:3.36.2-1ubuntu1) groovy; urgency=medium * New upstream version rebased on Debian (lp: #1876256) * debian/patches/0001-sound-Fix-translation-of-System-Sounds.patch, debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch, debian/patches/git-info-crash-on-nvidia.patch, debian/patches/git-nongnome-segfault.patch: - removed, included in the new version -- Sebastien Bacher Fri, 01 May 2020 09:10:17 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Bug description: * Impact the settings segfault when trying to set up a livepatch account * Test case $ gnome-control-center info-overview $ gnome-control-center online-accounts add google -> shouldn't segfault check also for error reports on https://errors.ubuntu.com/problem/cfae777005d1d918049ddbf3ad3977adc2e272b0 * Regression potential the change could introduce a small leak, that's better than a segfault though --- problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() 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-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873883] Re: Impossible to discern which is the primary monitor in dock positioning
This bug was fixed in the package gnome-control-center - 1:3.36.2-1ubuntu1 --- gnome-control-center (1:3.36.2-1ubuntu1) groovy; urgency=medium * New upstream version rebased on Debian (lp: #1876256) * debian/patches/0001-sound-Fix-translation-of-System-Sounds.patch, debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch, debian/patches/git-info-crash-on-nvidia.patch, debian/patches/git-nongnome-segfault.patch: - removed, included in the new version -- Sebastien Bacher Fri, 01 May 2020 09:10:17 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- 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/1873883 Title: Impossible to discern which is the primary monitor in dock positioning Status in gnome-control-center package in Ubuntu: Fix Released Bug description: In gnome the primary monitor is quite important as it's the one where the overview will be shown. So when selecting where to put the dock in appearance settings, this should be mentioned in order to make sure where it will be showing, and this is more important when there are multiple monitors with the same name. [ Impact ] It may be impossible to understand what monitor we refer to in ubuntu's appearance settings pane [ Test case ] Run: env NO_AT_BRIDGE=1 HOME=/tmp/TEST_HOME \ XDG_RUNTIME_DIR=/tmp/.tmp-runtime-dir \ XDG_SESSION_TYPE=wayland \ MUTTER_DEBUG_NUM_DUMMY_MONITORS=3 \ dbus-run-session gnome-shell --nested --wayland In that nested view with three fake monitors, run gnome-control-center and go in the "Appearance" view. In the combo-box it's impossible to understand to what monitor we're applying the dock "show in" setting, nor what it is currently the primary monitor - The monitors should be marked by numbers and while this view is showing the shell should mark each monitor the same way [ Regression potential ] Strings might be shown not properly in RTL languages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873890] Re: Appearence pane shows monitors also when they are disabled
This bug was fixed in the package gnome-control-center - 1:3.36.2-1ubuntu1 --- gnome-control-center (1:3.36.2-1ubuntu1) groovy; urgency=medium * New upstream version rebased on Debian (lp: #1876256) * debian/patches/0001-sound-Fix-translation-of-System-Sounds.patch, debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch, debian/patches/git-info-crash-on-nvidia.patch, debian/patches/git-nongnome-segfault.patch: - removed, included in the new version -- Sebastien Bacher Fri, 01 May 2020 09:10:17 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- 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/1873890 Title: Appearence pane shows monitors also when they are disabled Status in gnome-control-center package in Ubuntu: Fix Released Bug description: [ Impact ] When multiple monitors are available but only a subset of them are enabled, the ubuntu's g-c-c panel still shows them all, giving the option to move the launcher to such monitor, even if that is not possible. [ Test case ] Run: env NO_AT_BRIDGE=1 HOME=/tmp/TEST_HOME \ XDG_RUNTIME_DIR=/tmp/.tmp-runtime-dir \ XDG_SESSION_TYPE=wayland \ MUTTER_DEBUG_NUM_DUMMY_MONITORS=3 \ dbus-run-session gnome-shell --nested --wayland From such nested window, use g-c-c display panel to disable one or multiple fake monitors. Go in the Appearance panel - Only the enabled monitors should be visible in the "Show on" combo box If only one monitor is enabled the combo box should not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876256] Re: SRU the current 3.36.2 stable update
This bug was fixed in the package gnome-control-center - 1:3.36.2-1ubuntu1 --- gnome-control-center (1:3.36.2-1ubuntu1) groovy; urgency=medium * New upstream version rebased on Debian (lp: #1876256) * debian/patches/0001-sound-Fix-translation-of-System-Sounds.patch, debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch, debian/patches/git-info-crash-on-nvidia.patch, debian/patches/git-nongnome-segfault.patch: - removed, included in the new version -- Sebastien Bacher Fri, 01 May 2020 09:10:17 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1876256 Title: SRU the current 3.36.2 stable update Status in gnome-control-center package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential Nothing specific to test in this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866088] Re: Problems with the Dock setting of "Show on" in the Appearance tab
This bug was fixed in the package gnome-control-center - 1:3.36.2-1ubuntu1 --- gnome-control-center (1:3.36.2-1ubuntu1) groovy; urgency=medium * New upstream version rebased on Debian (lp: #1876256) * debian/patches/0001-sound-Fix-translation-of-System-Sounds.patch, debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch, debian/patches/git-info-crash-on-nvidia.patch, debian/patches/git-nongnome-segfault.patch: - removed, included in the new version -- Sebastien Bacher Fri, 01 May 2020 09:10:17 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1866088 Title: Problems with the Dock setting of "Show on" in the Appearance tab Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Bug description: I use a laptop with external monitor in a dual display set-up. The "Screen Display" tab of Settings application correctly shows: Display 1 as the built-in display Display 2 as the external monitor If I go to the new "Appearance" tab I see that the Dock is set to display on the Built-in display but it is actually being displayed on the external monitor. If I change this setting to display on the external monitor it displays on the laptop's built-in display. Once set to "All displays" the setting can not be unset and the dock insists on being displayed on both the laptop's built-in display and the external monitor. I used the Dconf editor to set org.gnome.shell.extensions.dash-to-dock.multi-monitor to off to correct the problem although the settings application again shows that the dock is being displayed on the built-in display when in fact it is being shown on the external monitor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 15:20:47 2020 InstallationDate: Installed on 2019-05-17 (292 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-11-08 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1866088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Kai, What do you think on #21, it's a regression or not? -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
For what I observed (both focal and bionic), I'm not sure (and I think it's not) it's a regression, due the the bug it's already there before this patch. And I tried one hp dm, one hp sff, one hp laptop and one dell laptop, only can be reproduced in Dell laptop. For what I observed: [[[1:11.1-1ubuntu7.5]]] Before I plugged headset there is only one device shown on input device, which is 1. Internal Microphone - Built-in Audio After I plugged headset into the jack, dialog shown up, I choice "headset", then three input device shown up, which are: 1. Headset Microphone - Built-in Audio 2. Internal Microphone - Built-in Audio 3. Microphone - Built-in Audio [[[1:11.1-1ubuntu7.6]]] Before I plugged headset there are two devices shown on input device, which are 1. Headset Microphone - Built-in Audio 2. Internal Microphone - Built-in Audio After I plugged headset into the jack, dialog shown up, I choice "headset", then three input device shown up, which are: 1. Headset Microphone - Built-in Audio 2. Internal Microphone - Built-in Audio 3. Microphone - Built-in Audio [[[result]]] No matter which cases, once you choice (3. Microphone - Built-in Audio), then there is no headset output audio. Select others, the audio output came back. -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864997] Re: System is running in low graphics mode
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1864997 Title: System is running in low graphics mode Status in xorg-server package in Ubuntu: Expired Bug description: Hi, I am receiving this error while booting System is running in low graphics mode. I am using Intel core gen 2 graphic card on my lenevo L430 Thinkpad, runnin gon 64 bit Linux Xenial 16.04 (LTS). Kindly help. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 CurrentDesktop: Unity Date: Thu Feb 27 17:42:25 2020 DistUpgraded: 2018-02-07 11:07:14,401 DEBUG /openCache(), new cache size 86347 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21f7] InstallationDate: Installed on 2017-01-23 (1129 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 2466CV8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-174-generic root=UUID=88cc2d85-ce2f-4456-b022-dedcdd8398b9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-02-07 (750 days ago) dmi.bios.date: 06/20/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G3ET36WW(1.10) dmi.board.asset.tag: Not Available dmi.board.name: 2466CV8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ET36WW(1.10):bd06/20/2012:svnLENOVO:pn2466CV8:pvrThinkPadL430:rvnLENOVO:rn2466CV8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2466CV8 dmi.product.version: ThinkPad L430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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: Thu Feb 27 17:37:28 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9020 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865373] Re: Authentication Prompt cut off
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/1865373 Title: Authentication Prompt cut off Status in gnome-shell package in Ubuntu: Expired Bug description: Every time the "Authentication Required" prompt pops up, the right side is cut off short. My resolution is currently set to 1600x900 on a 1920x1080 13." screen. The same thing happened at native resolution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 14:40:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081b] InstallationDate: Installed on 2020-02-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200229) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_evtvik@/vmlinuz-5.4.0-14-generic root=ZFS=rpool/ROOT/ubuntu_evtvik ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Quite some investigations you did there ironincoder, don't forget to post here if you manage to get the speakers going. ;) I was actually wondering where the correct place to post and get codec issues fixed is, because this probably isn't the place? Is there a bug tracker for Alsa? -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=
[Desktop-packages] [Bug 1876416] [NEW] Xorg freeze
Public bug reported: I have been using the operating system for the past week,and i have seen lot of problem with it.when i am turning on the computer sometimes its black screen and does not open.sometime when i open and browsing the system was suddenly hangs and does not turn off.even after i turn of the power the computer not shutting down .it would be grade if someone could help . " i was trying to fix using "nomodeset" but it does not work for me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 08:28:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2020-04-20 (11 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic false-gpu-hang freeze 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/1876416 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I have been using the operating system for the past week,and i have seen lot of problem with it.when i am turning on the computer sometimes its black screen and does not open.sometime when i open and browsing the system was suddenly hangs and does not turn off.even after i turn of the power the computer not shutting down .it would be grade if someone could help . " i was trying to fix using "nomodeset" but it does not work for me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 08:28:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2020-04-20 (11 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.
[Desktop-packages] [Bug 1876415] [NEW] Fonts in the GNOME shell not shown.
Public bug reported: GNOME does not show any text in the DE itself. Examples of text that is missing: The activities button on the top left, date and time, text of notifications, authentication dialogs, the telegram icon not displaying the number of unread messages, searches in the search bar. The text however is drawn in applications that are not an integral part of the shell itself, such as the settings application, terminals, Firefox, Rhythmbox, GNOME System montior. The bug appeared seemingly out of nowhere, can be worked around though pretty easily by chainging the fonts of the user interface in the GNOME tweak tool. The problem reappears, if the user interface fonts are changed back to the fonts which were not appearing on the screen originally. Changing the font size does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 04:28:41 2020 DistUpgraded: 2020-04-24 10:02:52,848 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-26-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-28-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] InstallationDate: Installed on 2019-11-07 (176 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=45a49275-be6c-418c-86a5-c57794b70427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (7 days ago) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Missing fonts in the calendar, clock and the notifications." https://bugs.launchpad.net/bugs/1876415/+attachment/5364816/+files/Bildschirmfoto%20von%202020-05-02%2004-49-19.png -- 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/1876415 Title: Fonts in the GNOME shell not shown. Status in xorg package in Ubuntu: New Bug description: GNOME does not show any text in the DE itself. Examples of text that is missing: The activities button on the top left, date and time, text of notifications, authentication dialogs, the telegram icon not dis
[Desktop-packages] [Bug 1825766] Re: search results don't match apt search
@stuardo: The reason for Guake being missing is that the `guake.desktop` file in `/usr/share/applications` is a symbolic link *and* the application doesn't ship a metainfo file. This is forbidden: https://wiki.debian.org/AppStream/Guidelines The .desktop file being a symlink results in Guake basically not being seen by the metadata generator at all. To fix this, either the .desktop file needs to be an actual file, and not a symlink, or a metainfo file[1] has to be shipped with this package. Ideally both. The reason this package is missing is simply a result of nobody caring enough to submit a patch or do a bit of work to make this app show up for a few years now (it never was in the catalog, as far as I can tell). Maybe a good case for a patch submission? ;-) [1]: https://www.freedesktop.org/software/appstream/metainfocreator/#/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1825766 Title: search results don't match apt search Status in gnome-software package in Ubuntu: New Bug description: searching for "guake" does not show the "guake" package, but if I search it via apt, I do see it available. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 17:39:19 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled
This bug was fixed in the package ibus - 1.5.22-4ubuntu1 --- ibus (1.5.22-4ubuntu1) groovy; urgency=medium * Merge from Debian unstable, remaining changes: - d/p/ubuntu-forward-panel-properties.patch (for Unity) - d/control: Build-Depend on gnome-pkg-tools (for translations) - d/rules: Use dh_translations when built on Ubuntu * Dropped patches: - d/p/ubuntu-disable-trigger.patch (LP: #1870945) - d/p/ubuntu-unicode-keybinding.patch (discussed at https://github.com/ibus/ibus/issues/2163) - d/p/git-Use-WAYLAND_DISPLAY-on-Wayland-sessions.patch (equivalent patch now in Debian) * Dropped breaks for older libglib2.0-0 versions - No equivalent in Debian; not needed post 20.04 * Build-Depend on gnome-pkg-tools instead of dh_translations * d/rules: Use dh_translations in Ubuntu -- Gunnar Hjalmarsson Thu, 30 Apr 2020 09:43:00 +0200 ** Changed in: ibus (Ubuntu) Status: In Progress => Fix Released ** Bug watch added: github.com/ibus/ibus/issues #2163 https://github.com/ibus/ibus/issues/2163 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870945 Title: ubuntu-disable-trigger.patch is effectively not enabled Status in Unity: New Status in ibus package in Ubuntu: Fix Released Bug description: ubuntu-disable-trigger.patch has effectively not been enabled since XDG_CURRENT_DESKTOP was turned into a list of values instead of a single value. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1870945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata
This bug was fixed in the package thunderbird - 1:68.7.0+build1-0ubuntu4 --- thunderbird (1:68.7.0+build1-0ubuntu4) groovy; urgency=medium * Do not install an xpm icon - debian/rules -- Olivier Tilloy Wed, 29 Apr 2020 19:20:23 +0200 ** Changed in: thunderbird (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1639863 Title: Firefox and Thunderbird don't appear in the (new) appstream metadata Status in firefox package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Fix Released Bug description: The new generator doesn't understand symlinks unfortunately, so Firefox and Thunderbird don't appear. http://appstream.staging.ubuntu.com/zesty/main/issues/firefox.html laney@nightingale> ls /usr/share/pixmaps/firefox.png lrwxrwxrwx 1 root root 46 Oct 25 15:34 /usr/share/pixmaps/firefox.png -> ../../lib/firefox/browser/icons/mozicon128.png To make them work, /usr/share/pixmaps/firefox.png should be a real file. It could either be a copy of the file, or /usr/lib/firefox/browser/icons/mozicon128.png could be a symlink. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876076] Re: SRU the current 3.36.2 stable update
This bug was fixed in the package gnome-desktop3 - 3.36.2-1ubuntu2 --- gnome-desktop3 (3.36.2-1ubuntu2) groovy; urgency=medium * debian/patches/git_wallclock_fix.patch: - backport an upstream fix for a test issue due to a translation change, fixes the build -- Sebastien Bacher Thu, 30 Apr 2020 15:05:31 +0200 ** Changed in: gnome-desktop3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1876076 Title: SRU the current 3.36.2 stable update Status in gnome-desktop3 package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.36.2 * Regression potential The update only includes translations changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1876076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876352] Re: App Grid icons out of alignment when opening from overview
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1876352 Title: App Grid icons out of alignment when opening from overview Status in Dash to dock: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819919] Re: Too much information in File Systems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- 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/1819919 Title: Too much information in File Systems Status in Gnome System Monitor: Fix Released Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: Previous versions of File Systems only showed my two harddrives, and was pretty useful. In Ubuntu 18.04 gnome-system-monitor > File Systems now shows 35 lines of uninteresting lines, like /var/lib/snapd ... I tried switching from Snap- to classic apt-based version, with these commands: sudo snap remove gnome-system-monitor sudo apt-get install gnome-system-monitor I got the good old System Files back, showing just the two hard drives of interest to me, but "snap remove gnome-system-monitor" removed a lot of extra packages, so my shortcuts stopped working, and possibly other stuff as well. I had to revert to snap-based gnome-system- monitor to get them working again. How can I get the previous and useful File Systems back, only showing my two hard drives? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1819919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819919] Re: Too much information in File Systems
Sorry for bumping an old issue, but the "fix" released on upstream seems to be the "nuclear" option of completely removing `snap`... which might not work for everyone. :( -- 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/1819919 Title: Too much information in File Systems Status in Gnome System Monitor: Fix Released Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: Previous versions of File Systems only showed my two harddrives, and was pretty useful. In Ubuntu 18.04 gnome-system-monitor > File Systems now shows 35 lines of uninteresting lines, like /var/lib/snapd ... I tried switching from Snap- to classic apt-based version, with these commands: sudo snap remove gnome-system-monitor sudo apt-get install gnome-system-monitor I got the good old System Files back, showing just the two hard drives of interest to me, but "snap remove gnome-system-monitor" removed a lot of extra packages, so my shortcuts stopped working, and possibly other stuff as well. I had to revert to snap-based gnome-system- monitor to get them working again. How can I get the previous and useful File Systems back, only showing my two hard drives? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1819919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
I can confirm this is not working on Bionic. vainfo output: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 error: failed to resolve wl_drm_interface(): /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit -- 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/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
I also just experienced this same bug on fresh install of Focal 20.04. I don't have Yubikey. Since the appearance of the window is delayed from whatever triggers it, I don't know what the cause is. The behavior is as other describes, a orphaned window on top left corner of screen, clicking the window results in whatever is underneath being clicked. Logging out and relogging makes the window disappear. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in gnome-shell package in Ubuntu: Confirmed Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I also encouter this problem. Each time someone share a zoom link, chronium cannot open it. This is kind of annoying since it is happenning all day long at each meeting. I'm thinking about using a different browser just because this bug does not seem importantenough to be solved. I hope someone takes the time to fix this. -- 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 1876304] Re: package libvdpau1 (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: libvdpau (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1876304 Title: package libvdpau1 (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi Status in libvdpau package in Ubuntu: Invalid Bug description: ubuntudan kubuntuya geçiş işlemi sırasında hata aldım ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvdpau1 (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri May 1 16:22:06 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1670] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:1670] MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=93809286-4ed8-4ff5-b01b-3a40f17ccd3a ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libvdpau Title: package libvdpau1 (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1670 dmi.board.vendor: Hewlett-Packard dmi.board.version: 09.4C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd01/24/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn1670:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: A1Q19EA#AB8 dmi.product.version: 06921220461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1876304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876382] Re: Ubuntu 20.04 Fractional scaling
** 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/1876382 Title: Ubuntu 20.04 Fractional scaling Status in xorg package in Ubuntu: New Bug description: I have 2 screens 1 x 1440 x 2560 (2k) 1 x 3840 x 2160 (4k) I just upgraded to ubuntu 20.04 (From 19.10). I have tried to use the fractional scaling option and it seem its not working. When setting the fractional scaling on the 4k monitor (to 125% or 150%) it glitches out (Goes black) and when it comes back it has set the scaling to 200% and changed the screen positions to be on top of one another, Seems there is no way for me to set the correct scaling. Just for information purposes I am currently using the nvidia-435 driver (I have also tried with the nvidia-440-driver) to no avail ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) 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 1 22:00:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6183] InstallationDate: Installed on 2020-01-15 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:0892 Logitech, Inc. OrbiCam Bus 001 Device 003: ID 1b1c:1b20 Corsair Corsair STRAFE RGB Gaming Keyboard Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370P D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=bd37a70e-316f-4716-a253-481f8f785d18 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: Z370P D3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370PD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370PD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370P D3 dmi.product.sku: Default string dmi.product.version: Default string 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/+bug/1876382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876383] Re: issues with full screen videos
** 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/1876383 Title: issues with full screen videos Status in xorg package in Ubuntu: New Bug description: When watching MP4 clips using the default app (videos) I have a display issue. When clicking on the full screen button here is what happens: 1- screen goes blank for a few seconds 2- a new videos window opens up with displaying the move but it it is not maximized or in full screen 3- The original maximized window stays in the background with a still picture ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 17:21:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068] InstallationDate: Installed on 2020-04-24 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0070.2018.1019.1503 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0070.2018.1019.1503:bd10/19/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831392] Re: input-libinput-hwe 0.28.1-1 touchpad cursor jumpy and inaccurate
Same on Ubuntu 20.04. input-libinput 0.29.0-1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1831392 Title: input-libinput-hwe 0.28.1-1 touchpad cursor jumpy and inaccurate Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: After upgrading x to hwe touchpad cursor is jumpy and inaccurate. Ubuntu 18.04.02 (4.18.0-20-generic) thinkpad x240 libinput 1.10.4-1 input-libinput-hwe 0.28.1-1 I assume that my earlier version was 0.27.1-1. It was working smoothly. I don't want to change touchpad drivers to synaptic because only libinput supports multi touch gesture on my hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1831392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876352] Re: App Grid icons out of alignment when opening from overview
** Changed in: dash-to-dock Status: Unknown => New -- 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/1876352 Title: App Grid icons out of alignment when opening from overview Status in Dash to dock: New Status in gnome-shell package in Ubuntu: New Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876382] [NEW] Ubuntu 20.04 Fractional scaling
You have been subscribed to a public bug: I have 2 screens 1 x 1440 x 2560 (2k) 1 x 3840 x 2160 (4k) I just upgraded to ubuntu 20.04 (From 19.10). I have tried to use the fractional scaling option and it seem its not working. When setting the fractional scaling on the 4k monitor (to 125% or 150%) it glitches out (Goes black) and when it comes back it has set the scaling to 200% and changed the screen positions to be on top of one another, Seems there is no way for me to set the correct scaling. Just for information purposes I am currently using the nvidia-435 driver (I have also tried with the nvidia-440-driver) to no avail ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) 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 1 22:00:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6183] InstallationDate: Installed on 2020-01-15 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:0892 Logitech, Inc. OrbiCam Bus 001 Device 003: ID 1b1c:1b20 Corsair Corsair STRAFE RGB Gaming Keyboard Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370P D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=bd37a70e-316f-4716-a253-481f8f785d18 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: Z370P D3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370PD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370PD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370P D3 dmi.product.sku: Default string dmi.product.version: Default string 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Ubuntu 20.04 Fractional scaling https://bugs.launchpad.net/bugs/1876382 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 1876383] [NEW] issues with full screen videos
You have been subscribed to a public bug: When watching MP4 clips using the default app (videos) I have a display issue. When clicking on the full screen button here is what happens: 1- screen goes blank for a few seconds 2- a new videos window opens up with displaying the move but it it is not maximized or in full screen 3- The original maximized window stays in the background with a still picture ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 17:21:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068] InstallationDate: Installed on 2020-04-24 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0070.2018.1019.1503 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0070.2018.1019.1503:bd10/19/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- issues with full screen videos https://bugs.launchpad.net/bugs/1876383 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 1876393] Re: LibreOffice Help do not open, error msg "...lack of user rights"
This error - libreoffice help does not open - occurs in other flavors like Ubuntu Mate, Budgie, Kubuntu ... -- 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/1876393 Title: LibreOffice Help do not open, error msg "...lack of user rights" Status in libreoffice package in Ubuntu: New Bug description: I am using Ubuntu 20.04 in Portuguese - Brazil. When a try to open LibreOffice Help, I receive a error message in Portuguese: "O objeto não acessível. O objeto não pode ser acessado devido a falta de direitos do usuário". Translating this message to english: "the object is not accessible. the object cannot be accessed due to lack of user rights.". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 20:26:40 2020 InstallationDate: Installed on 2020-04-23 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1876393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876393] [NEW] LibreOffice Help do not open, error msg "...lack of user rights"
Public bug reported: I am using Ubuntu 20.04 in Portuguese - Brazil. When a try to open LibreOffice Help, I receive a error message in Portuguese: "O objeto não acessível. O objeto não pode ser acessado devido a falta de direitos do usuário". Translating this message to english: "the object is not accessible. the object cannot be accessed due to lack of user rights.". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 20:26:40 2020 InstallationDate: Installed on 2020-04-23 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1876393 Title: LibreOffice Help do not open, error msg "...lack of user rights" Status in libreoffice package in Ubuntu: New Bug description: I am using Ubuntu 20.04 in Portuguese - Brazil. When a try to open LibreOffice Help, I receive a error message in Portuguese: "O objeto não acessível. O objeto não pode ser acessado devido a falta de direitos do usuário". Translating this message to english: "the object is not accessible. the object cannot be accessed due to lack of user rights.". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 20:26:40 2020 InstallationDate: Installed on 2020-04-23 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1876393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 997934]
(In reply to Xisco Faulí from comment #11) > Changing priority back to 'medium' since the number of duplicates is lower > than 5 Should the number of different people who comment to an issue count towards 5? Thank you -- 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/997934 Title: [Upstream] Spell checking doesn't warn users if the selected dictionary isn't installed, but rather returns a potentially incorrect result Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: This has been the case since Beta 2. To reproduce: 1) Type out a load of rubbish on the keyboard as well as a few correctly spelled words. I used "vmw;qbjk aoeuasnth aoeu house in the street" 2) Press F7 to initiate the spell check. Actual Result: The spell check notifies the user of completion without any recognition of errors. Expected Result: The spell check should highlight each misspelled word and offer alternatives. WORKAROUND: Open the dash and run Language Support 2) Under the 'Language' tab, choose another variant of English and drag it above the US English so it takes precedence. 3) Click "Apply System-wide" and log out. On logging back in, spell check will work. Not reproducible in Xubuntu 32-bit. lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.3-0ubuntu1 Candidate: 1:3.5.3-0ubuntu1 Version table: *** 1:3.5.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Fri May 11 08:53:51 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328) ProcEnviron: LANGUAGE=en_IE:en TERM=xterm PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/997934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825766] Re: search results don't match apt search
Still an issue in Ubuntu 20.04. Following @ximion's explanation, Guake
IS a GUI application that should be listed in gnome-software. "Ubuntu
Sofware", when searching for "guake" shows
- electerm ("guake" in description)
- guake-cl (change colour)
- guake indicator
So, if it lists related apps but not the app itself, it confuses the
user. The fallback was to open a term and `apt install guake`. Any non
technical user, will give up.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1825766
Title:
search results don't match apt search
Status in gnome-software package in Ubuntu:
New
Bug description:
searching for "guake" does not show the "guake" package, but if I
search it via apt, I do see it available.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 21 17:39:19 2019
InstallationDate: Installed on 2019-04-21 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InstalledPlugins:
gnome-software-plugin-flatpak N/A
gnome-software-plugin-snap3.30.6-2ubuntu3
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876304] Re: package libvdpau1 (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi
** 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 libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1876304 Title: package libvdpau1 (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi Status in libvdpau package in Ubuntu: New Bug description: ubuntudan kubuntuya geçiş işlemi sırasında hata aldım ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvdpau1 (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri May 1 16:22:06 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1670] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:1670] MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=93809286-4ed8-4ff5-b01b-3a40f17ccd3a ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libvdpau Title: package libvdpau1 (not installed) failed to install/upgrade: dpkg-deb --fsys-tarfile alt süreci 2 hatalı çıkış kodu ile sona erdi UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1670 dmi.board.vendor: Hewlett-Packard dmi.board.version: 09.4C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd01/24/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn1670:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: A1Q19EA#AB8 dmi.product.version: 06921220461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1876304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876305] Re: Open Gl error
** 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/1876305 Title: Open Gl error Status in xorg package in Ubuntu: New Bug description: Not able to run Paraview it shows the OpenGl error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:02:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0441] InstallationDate: Installed on 2020-04-28 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Vostro 3500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=1532e72e-3f77-4b25-b954-43bbc1c813d0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 058DK5 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn058DK5:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Vostro 3500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2004301830.057275~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005010730.60912f~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
I had the on Ubuntu 19.10 (and have it still on Ubuntu 20.04). I agree that I see it more frequently in LibreOffice Writer, but I see it elsewhere. Unstable clipboard behavior is unhappy making. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875106] Re: System irresponsive after 2-finger horizontal scroll over dock
The requested log file follows attached. The steps I followed were: 1 -
reboot the system, 2 - start IMWheel (open terminal and manually running
the command "imwheel"), 3 - two finger scrolling over the side dock (to
reproduce the bug), 4 - lock/unlock screen and restart gnome-shell
("Alt+F2 r") (to regain control of the system), 5 - dumping 'journalctl
-b 0' to the attached file.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1875106/+attachment/5364740/+files/journalctl.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1875106
Title:
System irresponsive after 2-finger horizontal scroll over dock
Status in gnome-shell package in Ubuntu:
Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Incomplete
Bug description:
If I do a two-finger horizontal scrolling on top of the dock/sidebar,
the system becomes almost completely irresponsive: no response to
keyboard, only the mouse cursor moves, but clicking anywhere has no
effect. I have to close the laptop lid to force suspend, so I can
control the system again.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
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: ubuntu:GNOME
Date: Sat Apr 25 23:52:51 2020
InstallationDate: Installed on 2019-07-03 (297 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876384] Re: Gnome 3.36 flickering framebuffer line above status bar
I can suppress the behavior temporarily by switching the resolution of making any changes to the Display settings that cause a refresh (e.g. change to a lower resolution). Simply discarding the changes will give a working session. Reloading the GNOME session will only very briefly affect the phenomenon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1876384 Title: Gnome 3.36 flickering framebuffer line above status bar Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I'm encountering this problem in both Ubuntu 20.04 and Pop OS 20.04. When I boot the default X11 session on my AMD graphics card 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] I get a 1 pixel line above the Gnome status bar that flickers seemingly with screen refreshes and shows parts of the current frame buffer. You can sometimes tell that parts of my open browser window (bookmarks bar) are being displayed there. If the screen and applications on display are very quiet there isn't much movement but when I move the mouse or hover over (browser) elements that are seemingly refreshed periodically the line flashes and redraws with content from the screen. When I don't move the mouse or do much at all the flickering dies down after a while because there is not much refresh going on. During regular use though, the whole thing is super annoying. This is showing the behavior, this site open in Firefox, typing the words. "this is me typing this comment right now." https://youtu.be/j1JI5ST0ZkM This exact problem occured to me on a fresh install of Ubuntu 20.04 via USB media. For a bit it's fine and then this corruption happens. The video is taken from a POP_OS 20.04 installation on the same machine that shows the exact same behavior for the AMD GPU after a fresh install. If I switch to Wayland this never happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1876384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873266] Re: [nvidia] with x11 fractional scaling enabled, cannot change main monitor after setting scaling for monitors
** Summary changed: - [nvidia] cannot change main monitor after setting scaling for monitors + [nvidia] with x11 fractional scaling enabled, cannot change main monitor after setting scaling for monitors -- 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/1873266 Title: [nvidia] with x11 fractional scaling enabled, cannot change main monitor after setting scaling for monitors Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard- reboot (though I could probably try switching ttys, etc). This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-05 (287 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: nvidia-graphics-drivers-440 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Tags: focal package-from-proposed Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876384] [NEW] Gnome 3.36 flickering framebuffer line above status bar
Public bug reported: I'm encountering this problem in both Ubuntu 20.04 and Pop OS 20.04. When I boot the default X11 session on my AMD graphics card 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] I get a 1 pixel line above the Gnome status bar that flickers seemingly with screen refreshes and shows parts of the current frame buffer. You can sometimes tell that parts of my open browser window (bookmarks bar) are being displayed there. If the screen and applications on display are very quiet there isn't much movement but when I move the mouse or hover over (browser) elements that are seemingly refreshed periodically the line flashes and redraws with content from the screen. When I don't move the mouse or do much at all the flickering dies down after a while because there is not much refresh going on. During regular use though, the whole thing is super annoying. This is showing the behavior, this site open in Firefox, typing the words. "this is me typing this comment right now." https://youtu.be/j1JI5ST0ZkM This exact problem occured to me on a fresh install of Ubuntu 20.04 via USB media. For a bit it's fine and then this corruption happens. The video is taken from a POP_OS 20.04 installation on the same machine that shows the exact same behavior for the AMD GPU after a fresh install. If I switch to Wayland this never happens. ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Description changed: - I'm encountering this problem in both Ubuntu 20.04 and Pop OS 20.04. + I'm encountering this problem in both Ubuntu 20.04 and Pop OS 20.04. When I boot the default X11 session on my AMD graphics card 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] - - I get a 1 pixel line above the Gnome status bar that flickers seemingly with screen refreshes and shows parts of the current frame buffer. You can clearly tell that parts of my open browser window are being displayed there. If the screen and applications on display are very quiet there isn't much movement but when I move the mouse or hover over (browser) elements that are seemingly refreshed periodically the line flashes and redraws with content from the screen. + I get a 1 pixel line above the Gnome status bar that flickers seemingly + with screen refreshes and shows parts of the current frame buffer. You + can sometimes tell that parts of my open browser window (bookmarks bar) + are being displayed there. If the screen and applications on display are + very quiet there isn't much movement but when I move the mouse or hover + over (browser) elements that are seemingly refreshed periodically the + line flashes and redraws with content from the screen. When I don't move the mouse or do much at all the flickering dies down after a while because there is not much refresh going on. During regular use though, the whole thing is super annoying. This is showing the behavior, this site open in Firefox, typing the words. "this is me typing this comment right now." https://youtu.be/j1JI5ST0ZkM ** Description changed: I'm encountering this problem in both Ubuntu 20.04 and Pop OS 20.04. When I boot the default X11 session on my AMD graphics card 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] I get a 1 pixel line above the Gnome status bar that flickers seemingly with screen refreshes and shows parts of the current frame buffer. You can sometimes tell that parts of my open browser window (bookmarks bar) are being displayed there. If the screen and applications on display are very quiet there isn't much movement but when I move the mouse or hover over (browser) elements that are seemingly refreshed periodically the line flashes and redraws with content from the screen. When I don't move the mouse or do much at all the flickering dies down after a while because there is not much refresh going on. During regular use though, the whole thing is super annoying. This is showing the behavior, this site open in Firefox, typing the words. "this is me typing this comment right now." https://youtu.be/j1JI5ST0ZkM + + This exact problem occured to me on a fresh install of Ubuntu 20.04 via + USB media. For a bit it's fine and then this corruption happens. The + video is taken from a POP_OS 20.04 installation on the same machine that + shows the exact same behavior for the AMD GPU after a fresh install. ** Description changed: I'm encountering this problem in both Ubuntu 20.04 and Pop OS 20.04. When I boot the default X11 session on my AMD graphics card 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] I get a 1 pixel line above the Gnome status bar that flickers seemingly with screen refreshes and shows pa
[Desktop-packages] [Bug 1876379] Re: Screen is broken into triangles
Another screen shot, just because it is pretty ** Attachment added: "Screenshot from 2020-04-28 14-15-56.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876379/+attachment/5364697/+files/Screenshot%20from%202020-04-28%2014-15-56.png -- 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/1876379 Title: Screen is broken into triangles Status in xorg package in Ubuntu: New Bug description: After a new install of 20.04 the console display is broken into odd distortions and triangles and weird colours. I'm guessing the window manager is not working well with the graphic card, since it was fine up to the point of the automatic login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 16:28:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=23a40263-d349-4d43-af42-f18938d91ff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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:bd06/01/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: stem manufacturer 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/+source/xorg/+bug/1876379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
In a virtual machine I can reproduce this by installing pulseaudio and docker.io. I'm attaching a Vagrantfile that reproduces the issue for me. :; vagrant up :; vagrant ssh -t -- journalctl -u rtkit-daemon ** Attachment added: "vagrantfile to reproduce issue" https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+attachment/5364696/+files/Vagrantfile -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Incomplete Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876379] [NEW] Screen is broken into triangles
Public bug reported: After a new install of 20.04 the console display is broken into odd distortions and triangles and weird colours. I'm guessing the window manager is not working well with the graphic card, since it was fine up to the point of the automatic login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 16:28:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=23a40263-d349-4d43-af42-f18938d91ff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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:bd06/01/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: stem manufacturer 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 corruption focal ubuntu ** Attachment added: "Screenshot from 2020-05-01 16-30-30.png" https://bugs.launchpad.net/bugs/1876379/+attachment/5364677/+files/Screenshot%20from%202020-05-01%2016-30-30.png -- 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/1876379 Title: Screen is broken into triangles Status in xorg package in Ubuntu: New Bug description: After a new install of 20.04 the console display is broken into odd distortions and triangles and weird colours. I'm guessing the window manager is not working well with the graphic card, since it was fine up to the point of the automatic login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 16:28:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=23a40263-d349-4d43-af42-f18938d91ff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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:bd06/01/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VM:rvrRev1.xx:cvnChassisManufacture:ct3:c
[Desktop-packages] [Bug 1841274] Re: update to 2.3.0
** Changed in: ilmbase (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ilmbase in Ubuntu. https://bugs.launchpad.net/bugs/1841274 Title: update to 2.3.0 Status in ilmbase package in Ubuntu: Fix Released Bug description: The new version includes a soname change and is still in experimental in Debian, no real reason to update now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1841274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841276] Re: Update to 2.3
** Changed in: openexr (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1841276 Title: Update to 2.3 Status in openexr package in Ubuntu: Fix Released Bug description: The new version is in Debian experimental and requires a transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1841276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841295] Re: Update to 2.3.0?
** Changed in: cups (Ubuntu) Status: Triaged => Fix Released -- 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/1841295 Title: Update to 2.3.0? Status in cups package in Ubuntu: Fix Released Bug description: There is a new cups version out, likely not for this cycle though? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1841295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841780] Re: Update to 6.0
** Changed in: brltty (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1841780 Title: Update to 6.0 Status in brltty package in Ubuntu: Fix Released Bug description: It's current in Debian NEW and included a soname change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1841780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876377] [NEW] Crackling sound on focal
Public bug reported: When I turn the screen reader on, I hear a lot of hissing and crackling noise every time the screen reader says something. I don't have this hissing noise with any other application. I also don't get this crackling noise when I use spd-say. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: orca 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 22:30:09 2020 InstallationDate: Installed on 2020-05-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: orca UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: orca (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 orca in Ubuntu. https://bugs.launchpad.net/bugs/1876377 Title: Crackling sound on focal Status in orca package in Ubuntu: New Bug description: When I turn the screen reader on, I hear a lot of hissing and crackling noise every time the screen reader says something. I don't have this hissing noise with any other application. I also don't get this crackling noise when I use spd-say. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: orca 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 22:30:09 2020 InstallationDate: Installed on 2020-05-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: orca UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1876377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855315] Re: Please upgrade it to 2019 on Ubuntu 18.04 LTS
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: texlive-base (Ubuntu) Importance: Undecided => Wishlist ** Changed in: texlive-base (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1855315 Title: Please upgrade it to 2019 on Ubuntu 18.04 LTS Status in texlive-base package in Ubuntu: Fix Released Bug description: Please upgrade it to 2019 on Ubuntu 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1855315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570
** Tags removed: upgrade-software-version ** Changed in: usbutils (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hwdata (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ptouch-driver in Ubuntu. https://bugs.launchpad.net/bugs/1604036 Title: Upgrade printer-driver-ptouch to support Brother QL-570 Status in hwdata package in Ubuntu: Fix Released Status in ptouch-driver package in Ubuntu: Fix Released Status in usbutils package in Ubuntu: Fix Released Status in hwdata source package in Xenial: New Status in ptouch-driver source package in Xenial: Triaged Status in usbutils source package in Xenial: New Bug description: Please, upgrade printer-driver-ptouch to support Brother QL-570 P-touch Label Printer. See https://bitbucket.org/philpem/printer- driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt (motivate maintainers of printer-driver-ptouch to bump their version number and release a version that supports QL-570) and also upgrade usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1604036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825593] Re: Display scale and layout not remembered when X11 Fractional Scaling is enabled
Hello people So the bug report https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860 is closed, and this post you said it's not a suitable thread. (and at the same time gnome refuses to fix it and Ask Ubuntu closes the bug). Am I the only one that feels like chasing our own tail? -- 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/1825593 Title: Display scale and layout not remembered when X11 Fractional Scaling is enabled Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: After upgrading to 19.04, I enabled the experimental 'x11-randr- fractional-scaling' setting. If I set scaling to 125, 150, or 200%, the setting is remembered and used the next time I log in. If I set scaling to 100%, however, the next time I log in the scaling switches back to 200% automatically. I only want to use fractional scaling for external monitors. Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI screen. Pretty standard configuration. I have my DisplaySize set to 294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0. I have been unable to find an appropriate combination of settings where 168 DPI is respected for accurate font rendering, while at the same time not scaling up the rest of the UI to unusable proportions. Fractional scaling seems to be the only way to adjust some Gnome UI elements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536158] Re: Upgrade to 1.1.1 that was released in March 2016
** Changed in: alsa-driver-2.6.28-12 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1536158 Title: Upgrade to 1.1.1 that was released in March 2016 Status in alsa-driver package in Ubuntu: Fix Released Status in alsa-driver-2.6.28-12 package in Ubuntu: Fix Released Bug description: Please, upgrade to 1.1.1 that was released in March 2016, see http://www.alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1536158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852860] Re: Display settings not saved across sessions if fractional scaling is used
*** This bug is a duplicate of bug 1825593 *** https://bugs.launchpad.net/bugs/1825593 The other bug report says that this should be the correct thread. Which is the correct thread to follow? -- 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/1852860 Title: Display settings not saved across sessions if fractional scaling is used Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am using: - Ubuntu 19.10 - Nvidia gtx1080 - nvidia xserver installed - two 4k monitors I changed the scaling and order of monitors in Ubuntu Display settings. However when I reboot or logout/login the display settings reset and i have to set them all over again each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797064] Re: Update to 2.9.8
https://bugs.launchpad.net/ubuntu/+source/libxml2/2.9.10+dfsg-5 ** Changed in: libxml2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1797064 Title: Update to 2.9.8 Status in libxml2 package in Ubuntu: Fix Released Bug description: The new version is in Debian experimental only, why? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1797064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789660] Re: Update to 1.8 when it is in unstable
** Changed in: gspell (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gspell in Ubuntu. https://bugs.launchpad.net/bugs/1789660 Title: Update to 1.8 when it is in unstable Status in gspell package in Ubuntu: Fix Released Bug description: The new version requires enchant 2 which is an API/ABI incompatible version, that's not for this cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gspell/+bug/1789660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758459] Re: Getting transmission 2.93 in Bionic
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: transmission (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1758459 Title: Getting transmission 2.93 in Bionic Status in transmission package in Ubuntu: Fix Released Status in transmission package in Debian: Fix Released Bug description: As referenced on #1752940 some trackers have started blacklisting Transmission versions below 2.93 on the basis that they have no way of telling if an older version has been patched for CVE-2018-5702 or not. Can we try to get 2.93 in Bionic before the final freeze, especially since this is an LTS and 2.92 is starting to get old (Apr 9, 2016). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876346] Re: Documents cannot be opened in desktop UI on storage device
** Package changed: ubuntu => gvfs (Ubuntu) -- 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/1876346 Title: Documents cannot be opened in desktop UI on storage device Status in gvfs package in Ubuntu: New Bug description: I have an external storage that I access by my local network (Datatank Gateway - Freecom). I had Ubuntu 18.04 version and I could access to this external device without problems. I could move all files from-to the external device and open and execute them properly. I upgraded to 20.04 Ubuntu version and it stopped to access to this device. Then I changed smb.conf file adding the line: "client min protocol = NT1" and then I got access to the device. I can see the folders and subfolders, but all icons are folders, even the .xls or .doc or .pdf are shown as folders. I cannot transfer them from external device to any of my internal folders in my pc. I can read some of them, like .doc, but I have to select manually what program I need to execute to read it. .pdf files can also be read. But .xls or .pgn or .mp3 cannot be read. An error message appear saying "Content cannot be shown. It is not a folder". In summary I have access to me external device but I cannot manage normally any of the files inside my external device, as I did before with ubuntu version 18.04. All icons appear as folders regardless it is a real folder or a file. I woudl appreciate to assist to solve thsi problem. Thank you Leopoldo Soria ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs 1.44.1-1ubuntu1 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: ubuntu:GNOME Date: Fri May 1 19:13:04 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gvfs Symptom: storage Title: Documents cannot be opened in desktop UI on storage device UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871805] Re: --wait option not working as expected (3.28)
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Tags removed: upgrade-software-version ** Changed in: gnome-terminal (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-terminal (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1871805 Title: --wait option not working as expected (3.28) Status in gnome-terminal package in Ubuntu: Fix Released Bug description: Dear Maintainers, We have developed a program that it launches a new gnome-terminal with a ssh tunnel connection. Basically, the program forwards a local port to the destination address and opens a new terminal with a ssh connection to the local port: gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" The problem comes when we need to know when this gnome-terminal session has finished, in order to end the tunnel process. As you might know, the gnome-terminal command fires up gnome-terminal-server which it might be already running. Who handles the "ssh" connection is the gnome-terminal-server and not the gnome-terminal command, thus our program receives and exit code just after executing the previous command. In previous version there was the --disable-factory option, but unfortunately now is deprecated. Because of this type of problem it was added the --wait flag which was introduced in 3.27.1: gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" Nevertheless, there's a bug in this version. More information: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16 You can reproduced by launching a new gnome-terminal with the --wait flag from a gnome-terminal session and try to close it via a window operation. In that version --wait only works if with the exit command in the opened session. As mentioned in the linked URL this is solved in version >= 3.36 which also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that there are multiple issues referring the --disable-factory deprecated option, those could be closed as the new --wait option has the same behavior. Shall we update the libvte version used by gnome? The last libvte version has the proper child exit SIGNAL handler which solves the described issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840127] Re: Update to 0.15.0
https://bugs.launchpad.net/ubuntu/+source/liborcus/0.15.3-3build2 ** Changed in: liborcus (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liborcus in Ubuntu. https://bugs.launchpad.net/bugs/1840127 Title: Update to 0.15.0 Status in liborcus package in Ubuntu: Fix Released Bug description: The new version is in Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liborcus/+bug/1840127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840146] Re: Don't update to 5.1.8 or newer
The new version landed since, https://bugs.launchpad.net/ubuntu/+source/giflib/5.1.9-1 ** Changed in: giflib (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/1840146 Title: Don't update to 5.1.8 or newer Status in giflib package in Ubuntu: Fix Released Bug description: It's only in Debian experimental and they recommend not updating it, see https://salsa.debian.org/debian/giflib/commit/fa219f750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1840146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876348] Re: macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen.
** 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/1876348 Title: macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen. Status in xorg package in Ubuntu: New Bug description: System suspend does not work on Macbook air2009-2010. (MBair 2.1) System hangs indefinitely in a black screen. May or may not be related, power manager won't charge battery to 100%. 95% seems to be the upper limit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 1 19:54:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0870] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00ab] InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Apple Inc. MacBookAir2,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA21.88Z.0075.B03.0811141325 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D88C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D88C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA21.88Z.0075.B03.0811141325:bd11/14/08:svnAppleInc.:pnMacBookAir2,1:pvr1.0:rvnAppleInc.:rnMac-F42D88C8:rvr:cvnAppleInc.:ct10:cvrMac-F42D88C8: dmi.product.family: MacBook dmi.product.name: MacBookAir2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876369] Re: garbled/frozen screen after waking from sleep mode
** 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/1876369 Title: garbled/frozen screen after waking from sleep mode Status in xorg package in Ubuntu: New Bug description: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power- off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876348] [NEW] macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen.
You have been subscribed to a public bug: System suspend does not work on Macbook air2009-2010. (MBair 2.1) System hangs indefinitely in a black screen. May or may not be related, power manager won't charge battery to 100%. 95% seems to be the upper limit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 1 19:54:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0870] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00ab] InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Apple Inc. MacBookAir2,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA21.88Z.0075.B03.0811141325 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D88C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D88C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA21.88Z.0075.B03.0811141325:bd11/14/08:svnAppleInc.:pnMacBookAir2,1:pvr1.0:rvnAppleInc.:rnMac-F42D88C8:rvr:cvnAppleInc.:ct10:cvrMac-F42D88C8: dmi.product.family: MacBook dmi.product.name: MacBookAir2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen. https://bugs.launchpad.net/bugs/1876348 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 1876346] [NEW] Documents cannot be opened in desktop UI on storage device
You have been subscribed to a public bug: I have an external storage that I access by my local network (Datatank Gateway - Freecom). I had Ubuntu 18.04 version and I could access to this external device without problems. I could move all files from-to the external device and open and execute them properly. I upgraded to 20.04 Ubuntu version and it stopped to access to this device. Then I changed smb.conf file adding the line: "client min protocol = NT1" and then I got access to the device. I can see the folders and subfolders, but all icons are folders, even the .xls or .doc or .pdf are shown as folders. I cannot transfer them from external device to any of my internal folders in my pc. I can read some of them, like .doc, but I have to select manually what program I need to execute to read it. .pdf files can also be read. But .xls or .pgn or .mp3 cannot be read. An error message appear saying "Content cannot be shown. It is not a folder". In summary I have access to me external device but I cannot manage normally any of the files inside my external device, as I did before with ubuntu version 18.04. All icons appear as folders regardless it is a real folder or a file. I woudl appreciate to assist to solve thsi problem. Thank you Leopoldo Soria ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs 1.44.1-1ubuntu1 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: ubuntu:GNOME Date: Fri May 1 19:13:04 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gvfs Symptom: storage Title: Documents cannot be opened in desktop UI on storage device UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Documents cannot be opened in desktop UI on storage device https://bugs.launchpad.net/bugs/1876346 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs 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 1876369] [NEW] garbled/frozen screen after waking from sleep mode
You have been subscribed to a public bug: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power-off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 focal ubuntu -- garbled/frozen screen after waking from sleep mode https://bugs.launchpad.net/bugs/1876369 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 1827282] Re: package sgml-base 1.29 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sgml-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/1827282 Title: package sgml-base 1.29 failed to install/upgrade: triggers looping, abandoned Status in sgml-base package in Ubuntu: Confirmed Bug description: No se ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sgml-base 1.29 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:45:03 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-04-16 (1110 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.0 SourcePackage: sgml-base Title: package sgml-base 1.29 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1827282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875845] Re: keyring cannot be unlocked if used fingerprint to login gnome session
@Marco, there is also a bug there which isn't a wishlist, the keyring in that case should prompt for a password like it does when using autologin The first log has that error though 'NetworkManager[958]: [1588178035.3236] agent-manager: agent[8102b0d78d474c3c,:1.238/org.gnome.Shell.NetworkAgent/1000]: > gnome-shell[2812]: pushModal: invocation of begin_modal failed gnome-shell[2812]: keyringPrompt: Failed to show modal dialog. Dismissing prompt request' Which seems to indicate that prompting was requested by failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1875845 Title: keyring cannot be unlocked if used fingerprint to login gnome session Status in GNOME Keyring: Unknown Status in gnome-keyring package in Ubuntu: Triaged Bug description: I upgraded to Ubuntu 20.04 and setup the fingerprint login. Today when I tried to launch remmina it didn't show up for a long time. I launch Gnome Password and Keys > Passwords > Login I see there's a button to click to unlock. Clicking the unlock button is still waiting forever. A moment later I logout current session and type in the user password to login. Then I could launch remmina and unlock the Gnome Password and Keys. System info ❯ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ~ ❯ apt-cache policy gnome-keyring gnome-keyring: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://ftp.cuhk.edu.hk/pub/Linux/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1875845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876279] Re: Xorg freeze
Thanks, the shell log has no error, did you have the issue in this session? Could you get the journal log from a session which had the bug? -- 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/1876279 Title: Xorg freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am the beginner with Linux and Ubuntu.And some Android habit that I can't give up . So I just try to classify my application with click on the button of "Show Application ", and drag all the LibreOffice application in one folder like Android does, but I find out that it usually frozen when I trying to leave the folder ,you may try click the folder and out frequently, and it frozen, the result is come from my experiment, I'm not sure I am the only person who encounter this problem. The situation was the screen stopped at "Show Application", but "spotify" still playing the song at the background. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 18:29:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0567] MachineType: Acer TravelMate 8481 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=44a3c145-e212-4d4e-b563-ad4206dfe924 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA41_HS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnAcer:bvrV2.06:bd10/28/2011:svnAcer:pnTravelMate8481:pvrV2.06:rvnAcer:rnBA41_HS:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.06: dmi.product.name: TravelMate 8481 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal package-from-proposed Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
*** This bug is a duplicate of bug 1872476 *** https://bugs.launchpad.net/bugs/1872476 I have read the explication of Sergio Durigan Junior in bug 1872476 and I am convinced now that there is a problem in Samba and not in GIO. So I shall mark this bug as a duplicate of 1872476 now. Thanks, Sergio! ** This bug has been marked a duplicate of bug 1872476 Shared files are shown as folders -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: Incomplete Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876352] Re: App Grid icons out of alignment when opening from overview
After some further help from the upstream bug ticket it looks like this is an issue with the Ubuntu Dock (dash-to-dock). If you disable that extension this issue no longer occurs. ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1199 https://github.com/micheleg/dash-to-dock/issues/1199 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1199 Importance: Unknown Status: Unknown ** No longer affects: 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/1876352 Title: App Grid icons out of alignment when opening from overview Status in Dash to dock: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
I have the same problem. However, I'm able to record audio (with internal mic) using audacity. Also, plugged in microphone/phones work ok. -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874973] Re: New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink()
*** This bug is a duplicate of bug 1864901 *** https://bugs.launchpad.net/bugs/1864901 This problem exists for my setup too. snap2.44.3 snapd 2.44.3 series 16 ubuntu 16.04 kernel 4.15.0-15-generic name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 21:41 +03 channels: latest/stable:81.0.4044.129 2020-04-29 (1135) 161MB - latest/candidate: 81.0.4044.129 2020-04-28 (1135) 161MB - latest/beta: 83.0.4103.23 2020-04-25 (1125) 163MB - latest/edge: 84.0.4128.3 2020-04-29 (1136) 164MB - installed: 81.0.4044.129(1135) 161MB - This problem and other problems doesn't exist for firefox snap idk what is different for chromium. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1874973 Title: New, never-ending chromium.launcher process on every chromium start since [Focal 20.04/Snap] due to check_current_symlink() Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since my upgrade from 19.10 to 20.04 on every start a _new_ /snap/chromium/[digit]/bin/chromium.launcher instance is launched and never-ending. It spawns a "sleep 60" child process. Five time starting (and stopping!) chromium = 5 processes 2823981 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832707 ?S 0:00 | \_ sleep 60 2824647 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831803 ?S 0:00 | \_ sleep 60 2825134 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2831953 ?S 0:00 | \_ sleep 60 2825521 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832057 ?S 0:00 | \_ sleep 60 2832767 ?S 0:00 \_ /bin/sh /snap/chromium/1119/bin/chromium.launcher 2832771 ?S 0:00 \_ sleep 60 The sleep 60 clearly indicates a problem in the check_current_symlink() function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
I tried the update in a virtual machine. It seems to work. The files on the NAS are no more shown as empty folders even if they are mounted via GIO. But it is not the same machine where the bug had occurred before, so I must go on testing to be shure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: Incomplete Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876352] [NEW] App Grid icons out of alignment when opening from overview
Public bug reported: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2730 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2730 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2730 Importance: Unknown Status: Unknown -- 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/1876352 Title: App Grid icons out of alignment when opening from overview Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875032] Re: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- 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/1875032 Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: This problem only occurs when I plug my headphone and choose Headphone in option. If I choose Headset, though plugging either headphone or headset, it works perfectly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prm1856 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 20:05:01 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2018-09-28 (575 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prm1856 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) dmi.bios.date: 05/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 03NJH0 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd05/29/2019:svnDellInc.:pnVostro3470:pvr:rvnDellInc.:rn03NJH0:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3470 dmi.product.sku: 0869 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873384] Re: [Dell Inspiron 5577] Headphone has no sound out
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- 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/1873384 Title: [Dell Inspiron 5577] Headphone has no sound out Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Computer: Dell inspiron 15 5577 Gaming intel i5 7300HQ version System: Kubuntu 20.04 Bug: Plug-in headphone has no sound out, meanwhile computer's speaker is okay when unplugged the headphone. Additional information: Headphone is okay when kubuntu 18.04.3 is installed on the computer. Alsamixer is checked and headphone are not mute. Headphone plugin state can be correctly detected, and speaker can automatically mute until headphone unplugged. External usb soundcard is usable with headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.12 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 11:14:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherlockholmes 1242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) MachineType: Dell Inc. Inspiron 5577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- 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/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875714] Re: No sound from headphones
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- 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/1875714 Title: No sound from headphones Status in alsa-driver package in Ubuntu: New Bug description: Hi, I upgraded to focal and since then I have the following problems with my audio on my laptop: 1. If I start my laptop with my headphones pluged-in I initially have sound from my headphones, If I unplug my headphones speakers work normally. But when insert my headphone again the sound stops from the speakers but I have no sound from my headphones. To "fix" the problem I have to go to the kde systemsettings and in "audio" settings in the advanced tab change the profile to something else and then restore the option. If I start the laptop WITHOUT the headphones pluged-in then everything works as it should. I have deleted the ~./config/pulse folder but it changes nothing. 2. If the computer starts WITHOUT headphones and the computer goes into hibernation when it wakes I get a static noise from the speakers (although the headphones are plugined-in) I have to reboot the computer in order to fix this. Kind Regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 21:37:41 2020 InstallationDate: Installed on 2018-11-22 (523 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-04-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Confirmed Bug description: After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875091] Re: opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2"
Replacing mesa-opencl-icd with the version from Ubuntu 19.10 (mesa- opencl-icd_19.2.8-0ubuntu0~19.10.3_amd64.deb) is enough to make things work. -- 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/1875091 Title: opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2" Status in mesa package in Ubuntu: New Bug description: Both luxmark and leelaz, the two OpenCL applications I have, fail at runtime with the same error, looking for "amdgpu_cs_query_reset_state2" in /usr/lib/x86_64-linux-gnu/gallium- pipe/pipe_radeonsi.so This is on a system with a relatively new AMD GPU, freshly upgraded from 18.04. Leela zero worked correctly in 18.04, and I've tried various compiler options, openCL config and such with no success. I don't know about luxmark but installed it to test. Since it reports the same error, I think it's a bug to report here. Platform Name Clover Device Name AMD Radeon (TM) RX Graphics (POLARIS11, DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1) Device Name AMD RAVEN (DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1) 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev c0) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
Okay, so now looking back at this bug, I see that when I have Focal with X11 and the 440 nvidia drivers enabled, I can set scaling to integer multiples without problems, but enabling fractional scaling and then using a fractional scaling results in the black screen problem mentioned in this bug as well as this in the system journal: gnome-control-c[6913]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors overlap ** Summary changed: - [nvidia] all monitor scaling fails due to overlapping monitors + [nvidia] fractional monitor scaling fails due to overlapping monitors -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors Status in mutter package in Ubuntu: New Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
It seems to be the same problem as bug 1872476, but there it seems to affect samba. I found that samba 4.11.7 alone works fine and that the bug only occurs if the samba shares are mounted with gio mount. Therefore I suppose it is a gio bug. Before installing a patched samba version in my system I would like to know what has been done there. A patched samba can be quite a security risk. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: Incomplete Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
Daniel, I just turned off fractional scaling and I no longer have this problem, so for me at least with nvidia drivers and focal, I don't see this bug and instead see 1825593 as you mentioned. -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Mutter: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873266] Re: [nvidia] cannot change main monitor after setting scaling for monitors
Also, if I disable Fractional Scaling, it now works to use/apply these settings in any order -- 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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard- reboot (though I could probably try switching ttys, etc). This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-05 (287 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: nvidia-graphics-drivers-440 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Tags: focal package-from-proposed Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi everybody, On my asus, the sound come back after a standby. Good luck Le ven. 1 mai 2020 à 17:30, Filippo Saglimbeni <1742...@bugs.launchpad.net> a écrit : > Hi everyone! > Asus Zenbook UX533FTC has the same problem with Ubuntu 20.04 with Windows > 10 in dual boot. > > 00-00: ALC294 Analog : ALC294 Analog : playback 1 : capture 1 > > uname -r > 5.4.0-26-generic > > No sound at all. It's a good while I'm stuck on this... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1742852 > > Title: > [hostname, Realtek ALC294, Speaker, Internal] No sound at all after > windows update > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > After a windows update I lost all the sound on my ubuntu machine. It's > the second time that this happends. > My sound is unmuted and at a loud level and nothing is comming out of my > speakers. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 > Uname: Linux 4.13.0-26-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gbergeron 2408 F pulseaudio > gbergeron 3656 F alsamixer > CurrentDesktop: Unity > Date: Thu Jan 11 22:21:23 2018 > InstallationDate: Installed on 2017-11-29 (43 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio >/dev/snd/controlC0: gbergeron 2408 F pulseaudio > gbergeron 3656 F alsamixer > Symptom_Jack: Speaker, Internal > Symptom_Type: No sound at all > Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/23/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX430UAR.203 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX430UAR > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: UX > dmi.product.name: UX430UAR > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version
[Desktop-packages] [Bug 1873266] Re: [nvidia] cannot change main monitor after setting scaling for monitors
Yes, 'Fractional Scaling' is enabled, sorry I should have specified. I am unable to actually use fractional scaling however due to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042 ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard- reboot (though I could probably try switching ttys, etc). This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-05 (287 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: nvidia-graphics-drivers-440 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Tags: focal package-from-proposed Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876281] Re: 20.4 - ssh/sftp - bookmark not working
thanks for giving the shortcut...but it should be visible in GUI (afair was in 18.4) tested in separate VM, it looks like in default ubuntu gnome-session it works (tested only with IP). IP was also not working in gnome-flashback giving the error "the name:1.373 was not provided by any .service files", but only from top-menu (seems to work from inside nautilus). Can't get the other mounting-error back (tried name from .ssh/config and IP) at the moment -- 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/1876281 Title: 20.4 - ssh/sftp - bookmark not working Status in nautilus package in Ubuntu: Incomplete Bug description: Hi, i want to try to create a bookmark from an sshfs-folder mounted by nautilus in Ubuntu 20.04. - enable Address-bar in nautilus (found no way to do it via gui): gsettings set org.gnome.nautilus.preferences always-use-location-entry true - connect to a ssh/sftp-share by entering address: e.g. ssh://192.168.0.10 - connection worked - now i try to add a bookmark for it by make rightclick on mounted-filesystem in the left list - bookmark created and visible in locations menu on gnome-flashback and inside nautilus - i can access the bookmark while i'm connected...but if i reboot the bookmark does not work anymore...only display error that it's not mounted. on 18.4 it will be mounted again (asking credentionals before of course). regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 1 13:02:17 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 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: 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/1876281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi everyone! Asus Zenbook UX533FTC has the same problem with Ubuntu 20.04 with Windows 10 in dual boot. 00-00: ALC294 Analog : ALC294 Analog : playback 1 : capture 1 uname -r 5.4.0-26-generic No sound at all. It's a good while I'm stuck on this... -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
https://github.com/libimobiledevice/libimobiledevice/issues/941 ** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #941 https://github.com/libimobiledevice/libimobiledevice/issues/941 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Ok, so this is progress. Building against gnutls fixes the trust pairing, but breaks file transfers. I rebuild the same source with openssl vs gnutls and that's exactly what I see. With openssl I have to re-pair every time I plug in but with gnutls, the file transfers don't work. The official ubuntu build uses gnutls so that's why we see the behaviour we do, and why the git version ubuntu uses should be new enough - it is with openssl. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
I've upgraded to 20.04 and have checked out the installed versions. For now, I was able to get it working "just" by upgrading libimobiledevice to the latest git and building against gnutls (using openssl resulted in it needing to re-trust every time I plug in because the TLS information it is saving is wrong, somehow). The other libraries are new enough now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1068605] Re: List of session type does not fit on screen with many window managers installed
Solved this on my testing Ubuntu 20.04 LTS VM by installing greeter from MATE: ``` sudo apt-get purge arctica-greeter arctica-greeter-guest-session sudo apt-get purge kylin-greeter ukui-greeter sudo apt-get autoremove --purge sudo apt-get install --reinstall ubuntu-mate-lightdm-theme ``` (see https://askubuntu.com/a/1233695/66509 ) ** Tags added: bionic eoan focal xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1068605 Title: List of session type does not fit on screen with many window managers installed Status in unity-greeter package in Ubuntu: Triaged Bug description: Please see the attached screenshot. The system has many window managers installed because it is a public lab machine with a many users that have different preferences. In order to change the session, one is supposed to confirm his selection by pressing the button at the bottem. However, the button hardly fits on the screen, in fact, one has to guess the purpose of the lowest button. On option would be to have the list of managers in a scroll box. --- Desired resolution: - Vertically middle align the desktop environment switcher with the back button when there are more than 6 desktop environments in the menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1068605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876279] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1876279/+attachment/5364551/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876279 Title: Xorg freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am the beginner with Linux and Ubuntu.And some Android habit that I can't give up . So I just try to classify my application with click on the button of "Show Application ", and drag all the LibreOffice application in one folder like Android does, but I find out that it usually frozen when I trying to leave the folder ,you may try click the folder and out frequently, and it frozen, the result is come from my experiment, I'm not sure I am the only person who encounter this problem. The situation was the screen stopped at "Show Application", but "spotify" still playing the song at the background. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 18:29:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0567] MachineType: Acer TravelMate 8481 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=44a3c145-e212-4d4e-b563-ad4206dfe924 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA41_HS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnAcer:bvrV2.06:bd10/28/2011:svnAcer:pnTravelMate8481:pvrV2.06:rvnAcer:rnBA41_HS:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.06: dmi.product.name: TravelMate 8481 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal package-from-proposed Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875435] Re: Re-logging occurs continuously during ubuntu operation
after above i install nvidia 440.82 driver but restarted again ** Attachment added: "journalctl5.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1875435/+attachment/5364553/+files/journalctl5.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1875435 Title: Re-logging occurs continuously during ubuntu operation Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I thought that I had some kind of problem with the video driver and all the detailed logs are contained here https://forums.developer.nvidia.com/t/ubuntu-kernel-v5-6-v5-7-for-hp-omen-17t-bc000-gforce-rtx2080-unstable-driver-nvidia-linux-x86-64-440-82-run/120027/25 But I installed ubuntu 20.04 and the problem is repeated not only on new kernels ubuntu 5.6 and 5.7.0-rc but also on kernel 5.4 with the Nouveau driver The system constantly logs onto the standard screen and requires a password to close all current programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1875435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876276] Re: Consider to include python-glade2 package into 20.04 LTS (focal) repositories as it is a dependency of many other packages
(forgot to mention the list was actually from 19.10) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1876276 Title: Consider to include python-glade2 package into 20.04 LTS (focal) repositories as it is a dependency of many other packages Status in pygtk package in Ubuntu: Incomplete Bug description: The python-gtk2 along with python-glade2 are still widely used by many applications. So it would be good if you include these packages into the focal repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1876276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
