[Desktop-packages] [Bug 1980718] Re: External monitor not working on Wayland
Hi Daniel, Thank you for your reply Before checking your solution I tested again to be sure the issue still exists and it seems that the issue has been fixed. Since the bug submission there were a few updates that might have fixed it directly or indirectly: * a kernel update * a thunderbolt (docking related) firmware update from Dell Is there any further action required from me to close this issue? Regards -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1980718 Title: External monitor not working on Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I connect the external monitor the image is shown on the external display but it freezes (on both displays); after I unplug the external display the following errors are logged (not sure it is related to the freeze): Jul 5 09:19:39 xps gnome-shell[10252]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed Jul 5 09:19:39 xps gnome-shell[10252]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Jul 5 09:19:39 xps gnome-shell[10252]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed The external display is connected via a thunderbolt port and an adapter to HDMI. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 5 09:21:33 2022 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-07 (696 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-27 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1980718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 also works for me (XPS 9500). Furthermore, it fixes also the Night Light feature. Thank you Daniel! -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Thank you Daniel!
I have added the bug information here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Released
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978534] [NEW] Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument]
Public bug reported: Screen wont wake up using mouse or keyboard. The only way to wake it up is to use CTRL+ALT+F1. The behavior is similar to the one for this bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274 The following is the log while this situation occurs: Jun 14 10:30:13 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:13 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument [ X 300+ of the first 2 lines] Jun 14 10:30:18 xps gnome-shell[3623]: JS ERROR: Failed to open reauthentication channel: Gio.IOErrorEnum: Error receiving data: Connection reset by peer#012_promisify/proto[asyncFunc]/ Warning: Unsupported maximum keycode 708, clipping. Jun 14 10:30:36 xps gnome-shell[12148]: > X11 cannot support keycodes above 255. Jun 14 10:30:36 xps gnome-shell[12148]: Errors from xkbcomp are not fatal to the X server Jun 14 10:30:36 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Object .MetaInputDeviceNative (0x7fb97014c200), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jun 14 10:30:36 xps gnome-shell[3623]: == Stack trace for context 0x56180bd0f4b0 == Jun 14 10:30:36 xps gnome-shell[3623]: #0 56180f536160 i resource:///org/gnome/shell/ui/keyboard.js:1216 (2e077f8a62e0 @ 56) Jun 14 10:30:36 xps gnome-shell[3623]: #1 56180f5360b8 i resource:///org/gnome/shell/ui/keyboard.js:1222 (2e077f8a6330 @ 94) Jun 14 10:30:36 xps gnome-shell[3623]: #2 7ffe1f7901c0 b self-hosted:1181 (10952b4b0a10 @ 454) Jun 14 10:30:36 xps dbus-daemon[3485]: [session uid=1000 pid=3485] Activating service name='org.gnome.ArchiveManager1' requested by ':1.147' (uid=1000 pid=12112 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jun 14 10:30:37 xps gnome-shell[3623]: DING: Detected async api for thumbnails Jun 14 10:30:37 xps gnome-shell[3623]: DING: GNOME nautilus 42.1.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 10:32:00 2022 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-07 (675 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-27 (47 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1978534 Title: Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument] Status in gnome-shell package in Ubuntu: New Bug description: Screen wont wake up using mouse or keyboard. The only way to wake it up is to use CTRL+ALT+F1. The behavior is similar to the one for this bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274 The following is the log while this situation occurs: Jun 14 10:30:13 xps gnome-shell[3623]: Failed to post KMS update:
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
I am using kernel v5.15.0-37 but I am still affected by this bug on my
XPS 15 (9500). Installed mutter is 42.1.
Also, the Night Light is not working (I saw some references in this
thread about this feature).
Is there anything else I must update on my system to have it working
properly?
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Released
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Gnome screen recorder doesn't work on dist-upgraded jammy systems
Hi, I have encountered the same issue after upgrading to Ubuntu 22.04. For me the fix was to reinstall the `gstreamer1.0-pipewire` package. `sudo apt reinstall gstreamer1.0-pipewire` Regards -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1963264 Title: Gnome screen recorder doesn't work on dist-upgraded jammy systems Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
The same happen with my XPS 13. Since a couple of days I have noticed this annoying hiss. I use Ubuntu 19.04. The workaround also fixes the issue for me (amixer -c 0 set 'Headphone Mic Boost',0 1) Regards -- 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
OMFG, being an Ubuntu (patched Nautilus that is) user for more than 9 years I thought this was a bug with 17.10 and patiently waited for a fix ... can't agree more with "complete idiots" This is not a huge, complex and hard to maintain feature that you just decide it is too difficult to support. Is this a mirror of the next "de- generation" of products? OMFG -- 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/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495817] [NEW] Display port stopped working with update to kernel 3.19.0.28
Public bug reported: [ 456.513218] [ cut here ] [ 456.513243] WARNING: CPU: 0 PID: 1557 at /build/linux-5xFjum/linux-3.19.0/drivers/gpu/drm/drm_dp_mst_topology.c:1293 process_single_tx_qlock+0x623/0x690 [drm_kms_helper]() [ 456.513246] fail [ 456.513247] Modules linked in: cdc_mbim cdc_wdm snd_usb_audio cdc_ncm snd_usbmidi_lib usbnet mii overlay binfmt_misc rfcomm bnep nls_iso8859_1 hid_microsoft hid_generic hid_sensor_incl_3d hid_sensor_magn_3d hid_sensor_rotation hid_sensor_gyro_3d hid_sensor_accel_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf industrialio hid_sensor_iio_common hid_sensor_hub uvcvideo videobuf2_vmalloc videobuf2_memops usbhid videobuf2_core v4l2_common videodev media btusb bluetooth arc4 joydev pn544_mei mei_phy pn544 hci hid_multitouch snd_hda_codec_hdmi nfc snd_hda_codec_realtek hid_rmi snd_hda_codec_generic dell_wmi sparse_keymap dell_laptop dcdbas intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm dm_multipath scsi_dh crct10dif_pclmul crc32_pclmul ghash_clmulni_intel [ 456.513298] snd_hda_intel iwlmvm snd_hda_controller aesni_intel snd_hda_codec mac80211 aes_x86_64 snd_hwdep lrw gf128mul glue_helper ablk_helper cryptd snd_pcm snd_seq_midi snd_seq_midi_event i915 serio_raw snd_rawmidi lpc_ich iwlwifi snd_seq snd_seq_device snd_timer cfg80211 drm_kms_helper snd mei_me mei shpchp soundcore drm i2c_algo_bit wmi i2c_hid hid dw_dmac video dw_dmac_core i2c_designware_platform i2c_designware_core snd_soc_sst_acpi spi_pxa2xx_platform soc_button_array dell_rbtn intel_smartconnect mac_hid cuse parport_pc ppdev lp parport autofs4 psmouse ahci libahci [ 456.513345] CPU: 0 PID: 1557 Comm: Xorg Tainted: GW 3.19.0-28-generic #30-Ubuntu [ 456.513347] Hardware name: Dell Inc. XPS 12-9Q33/XPS 12-9Q33, BIOS A08 03/03/2015 [ 456.513349] c0326038 88021367f7f8 817c458f 0007 [ 456.513354] 88021367f848 88021367f838 81076a6a 8802155c44c8 [ 456.513358] 8802155c4608 1000 8802155c4608 000c [ 456.513363] Call Trace: [ 456.513373] [] dump_stack+0x45/0x57 [ 456.513379] [] warn_slowpath_common+0x8a/0xc0 [ 456.513382] [] warn_slowpath_fmt+0x46/0x50 [ 456.513398] [] process_single_tx_qlock+0x623/0x690 [drm_kms_helper] [ 456.513410] [] process_single_down_tx_qlock+0x42/0x150 [drm_kms_helper] [ 456.513422] [] drm_dp_queue_down_tx+0x68/0x80 [drm_kms_helper] [ 456.513435] [] drm_dp_mst_i2c_xfer+0x176/0x290 [drm_kms_helper] [ 456.513464] [] ? drm_mode_create+0x25/0x70 [drm] [ 456.513488] [] ? drm_for_each_detailed_block+0x3d/0x150 [drm] [ 456.513498] [] __i2c_transfer+0x6d/0x220 [ 456.513502] [] i2c_transfer+0x59/0xc0 [ 456.513525] [] drm_do_probe_ddc_edid+0xc9/0x140 [drm] [ 456.513548] [] drm_get_edid+0x2f/0x3f0 [drm] [ 456.513562] [] drm_dp_mst_get_edid+0x8c/0xa0 [drm_kms_helper] [ 456.513603] [] intel_dp_mst_get_modes+0x29/0x50 [i915] [ 456.513616] [] drm_helper_probe_single_connector_modes_merge_bits+0xfe/0x480 [drm_kms_helper] [ 456.513630] [] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper] [ 456.513655] [] drm_mode_getconnector+0x368/0x3e0 [drm] [ 456.513673] [] drm_ioctl+0x1df/0x680 [drm] [ 456.513682] [] do_vfs_ioctl+0x2e0/0x4e0 [ 456.513688] [] ? __sys_recvmsg+0x65/0x80 [ 456.513692] [] SyS_ioctl+0x81/0xa0 [ 456.513696] [] system_call_fastpath+0x16/0x1b [ 456.513699] ---[ end trace 06eba29100be1286 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.17.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 15 09:35:29 2015 DistUpgraded: 2015-04-24 15:17:34,960 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05e3] InstallationDate: Installed on 2013-10-18 (696 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=8ef07bf4-4d18-497d-8186-e7c58ac6004d ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to vivid on 2015-04-24 (143 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8
