[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
I'm also seeing this issue between Chrome and PHPStorm on 22.04.1 LTS -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
** Description changed:
+ https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
+
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
- __b = std::memory_order_relaxed
+ __b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
- priv =
- cx = 0x561efe351c00
- js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
- ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
+ priv =
+ cx = 0x561efe351c00
+ js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
+ ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994010 Title: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps::load() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mozjs102 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994010 Title: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps::load() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gjs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994010 Title: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps::load() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995619] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load() from mozilla::detail::IntrinsicMemoryOps::load() from mozilla
*** This bug is a duplicate of bug 1994010 *** https://bugs.launchpad.net/bugs/1994010 ** Also affects: mozjs102 (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1994010 gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps::load() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995619 Title: gnome-shell crashed with SIGSEGV in std::__atomic_base::load() from mozilla::detail::IntrinsicMemoryOps::load() from mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1995619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Actually the bug just happened to me and now I can see "drmModeAtomicCommit: Invalid argument" in my logs now. So it turns out I am experiencing this bug. I will try the work around posted at the top of the first post: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Bug 1971149 is definitely a duplicate of this one. Please open your own bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Ah sorry I can't find "drmModeAtomicCommit: Invalid argument" in my system log. I think my problem is more like this one here: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
** Tags removed: third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971149] Re: Wayland session: Internal display is black after sleep
*** This bug is a duplicate of bug 1968040 *** https://bugs.launchpad.net/bugs/1968040 I have a similar problem using an external HDMI monitor connected to a laptop. It happens with the blank screen after a period of inactivity (without using the screen lock). After the screen has gone blank due to a period of inactivity, I move the mouse or press a key on the keyboard to wake up both screens. However, 1 of 3 things will happen: 1. The laptop's screen will wake up but the external monitor doesn't wake up. 2. The external monitor will wake up but the laptop's screen doesn't wake up. 3. Both screens will wake up as they should. To get both screens to wake up, I right click on the active screen and click "Display Settings". Click on "Mirror" then back to "Join", then "Apply" then "Revert Settings". The blank screen then realizes it is supposed to be on and it wakes up. The other option is to unplug and re- plug the HDMI cable in, but I got tired of doing this. OS: Ubuntu 22.10 Graphics: Mesa Intel® HD Graphics 5500 (BDW GT2) Windowing System: Wayland Processor: Intel® Core™ i7-5500U × 4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971149 Title: Wayland session: Internal display is black after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
It just happened again, in this case the Dock displayed over the top of the Evolution mail window so I ran the apport shown above. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1961508/+attachment/5641100/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1961508/+attachment/5641099/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1961508/+attachment/5641098/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1961508/+attachment/5641097/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1961508/+attachment/5641096/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
apport information ** Tags added: third-party-packages ** Description changed: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2022-02-18 (328 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + Package: mutter + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: mutter-common 43.0-1ubuntu4 + Tags: wayland-session third-party-packages kinetic + Uname: Linux 5.19.0-28-generic x86_64 + UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1961508/+attachment/5641095/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
To check if this is the bug you are experiencing, look for this repeating in your system log: drmModeAtomicCommit: Invalid argument If it's not mentioned in the log then you should create a new bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002558] Re: The ethernet connection icon has disappeared from both quick settings and the Settings app
** Summary changed: - The ethernet connection icon has disappeared + The ethernet connection icon has disappeared from both quick settings and the Settings app ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2002558 Title: The ethernet connection icon has disappeared from both quick settings and the Settings app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I have a similar problem using an external HDMI monitor connected to a laptop. Not sure if this is related because it happens with the blank screen after a period of inactivity (without using the screen lock). After the screen has gone blank due to a period of inactivity, I move the mouse or press a key on the keyboard to wake up both screens. However, 1 of 3 things will happen: 1. The laptop's screen will wake up but the external monitor doesn't wake up. 2. The external monitor will wake up but the laptop's screen doesn't wake up. 3. Both screens will wake up as they should. To get both screens to wake up, I right click on the active screen and click "Display Settings". Click on "Mirror" then back to "Join", then "Apply" then "Revert Settings". The blank screen then realizes it is supposed to be on and it wakes up. The other option is to unplug and re- plug the HDMI cable in, but I got tired of doing this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
This is still happening on Ubuntu 22.10. I can run apport-collect 1961508 again when it happens again if that helps to get this fixed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000185] Re: Nautilus crashes when returning to search results from a directory
There is no crash file for it in /var/crash and the whoopsie ID plugged into that URL does not return any recent errors. Edit: I just crashed Nautilus again in the same manner mentioned above (it's super easy) and no entries appeared. It's not logging them. It's also worth mentioning that I removed all of the extension packages so they're not what's causing it. I've started using Dolphin as my file manager because I really can't deal with not being able to search directories without everything I'm doing in every Nautilus window and tab closing on me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2000185 Title: Nautilus crashes when returning to search results from a directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000185] Re: Nautilus crashes when returning to search results from a directory
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2000185 Title: Nautilus crashes when returning to search results from a directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002558] Re: The ethernet connection icon has disappeared
Ok! ** Attachment added: "The ethernet connection icon has disappeared" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2002558/+attachment/5641026/+files/Captura%20de%20tela%20de%202023-01-12%2014-58-32.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2002558 Title: The ethernet connection icon has disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2002558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1997996] Re: when in Trash, no dedicated top banner
you also don't have a bar for copy/paste/etc Because it's not the same context / purpose. Here is the trash folder when one might expect a quick access to the special features of such a special folder : [ empty | restore ] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1997996 Title: when in Trash, no dedicated top banner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1997996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
Great, I'm closing the bug now then. I'm unsure what's the cause of the issue but it's not due to gnome-control-center issue, maybe the upgrader log has some clue though? ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1997996] Re: when in Trash, no dedicated top banner
empty and restore actions are easy enough to access Well now it's one or two click further away ( sub-menu in header bar or right click in side-panel. ) so it's not an improvement. The [ empty button ] in banner while looking at what's inside the trash was faster. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1997996 Title: when in Trash, no dedicated top banner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1997996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002290] Re: Poor Arabic rendering in VTE
Hi M.Hanny,
I'm so glad that you're way more familiar with fontconfig quirks as well
as Ubuntu processes than me. I wish you good luck in getting some better
config accepted and made default in Ubuntu!
-
Re lam-alif:
As far as I remember, and
https://en.wikibooks.org/wiki/Arabic/LearnRW/laam-alif tells me: The situation
is:
- The first (right) letter is a Lam (or Laam), U+0644, which looks similar to
English J.
- The second (left) letter is an Alif, U+0627, which looks similar to English I
(vertical bar); or some accented variant thereof (U+0622, U+0623, U+0625, maybe
more, I don't know).
In the terminal, this shows up as if you'd imagine English "IJ" with the
two letters connected at the bottom, i.e., similar to a U. As in the top
row of your screenshot in comment 12.
In gedit, browser etc. they show up in a way that either more resembles
as an "y", or as a shape that reminds me of an upside-down ribbon ,
something like an "8" but with the upper segment cut off. As in the
second row of your screenshot.
I'm glad you confirm what my consultant also said, namely that it's not
terribly bad to go with the not properly ligated version.
At least, it's good enough for now. My BiDi work focused on way more
fundamental things, namely to get the proper (non-reversed) ordering of
letters done. Rendering of Lam-Alif can always be further improved in
the terminal.
-
Re making the RTL paragraph direction (and right alignment) the default:
Unfortunately the locale subsystem (according to my latest memories)
does not specify whether the script is LTR or RTL. One way is to check
the language part of the locale, pretty much like you did, but listing
all the known RTL scripts ("he", and I guess there are some languages
that are somewhat related to Arabic that have their own code, maybe Urdu
and some more??). One caveat, though, is that locale-related env vars
(LANG, LANGUAGE, LC_MESSAGES, LC_ALL) override each other in a certain
order of priority, so probably it's wiser to invoke the `locale` utility
and find the resolved value in its output. (Fun fact: some projects use
gettext as a workaround for the lack of such a field in locales.
Translators have to create a "translated" string containing "ltr" or
"rtl", or "1" or "0", whatever choice of the programmers, to denote the
default direction.)
Another problem is that as the proposal says, no autodetection is the
default, and if an app switches to the other mode it should revert that
setting upon quitting. Which would revert what you do in the shell
startup files. (I'm not aware of any app using these control codes yet,
but we should think in the long term and a few steps ahead.)
I'm not absolutely certain that an autodetected default direction is
better in RTL locales. I'd guess there will be places where it's an
improvement (like "apt" obviously) and places where it's less desired.
At this moment I'm afraid we don't have enough knowledge and experience
to see the pros and cons, more data should be collected first.
Note that according to the BiDi proposal, there are 2x2 possible values for
paragraph direction (in case the terminal is asked to perform BiDi shuffling):
- LTR base dir (no autodetect)
- RTL base dir (no autodetect)
- Autodetect, falling back to LTR base dir
- Autodetect, falling back to RTL base dir
You should also test the other two possibilities, although they will
probably result in more inconsistencies at e.g. shell prompts which may
or may not have Arabic words (e.g. an Arabic path component) in them, or
some might make it outright a pain to type typical Unix commands.
I think further evaluation needs to happen on this topic, it's way too
early to jump into conclusions which mode is the better one. (It should
also be evaluated which apps it's more reasonable to ask to modify their
behavior and switch to the other mode.) Also, if it becomes clear that
it's a big overall advantage to flip the default, IMO it should happen
in the spec and in existing implementations before proper BiDi in
terminals gets too widespread.
Glad to see someone finally actually cares about this BiDi work :)
Thanks a lot for pushing it forward!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/2002290
Title:
Poor Arabic rendering in VTE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
It works, Sebastien! I tried reinstall and open and it didn't work. Than I tried the other 2 lines and then reinstall again and it worked! Thanks again, mate! Fernando El 12/1/23 a las 12:04, Sebastien Bacher escribió: > sudo apt install --reinstall libnm0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002290] Re: Poor Arabic rendering in VTE
Hi Egmont.
For bug 1, yes, fontconfig can be used for this. We even have a special
configuration file at /etc/fonts/conf.d/56-language-selector-ar.conf to
use a different font when the system language is Arabic (Noto Sans
Arabic). I believe it can be tweaked to use a custom Monospace font when
system language is Arabic like this:
monospace
DejaVu Sans Mono
Adding this to the file made the Monospace font change to DejaVu Sans Mono in
some places (e.g Gedit), but the GNOME Terminal was still using Ubuntu Mono for
some reason. I don't know why at the moment.
Perhaps I need to open a thread on Ubuntu Discourse. There are some i18n
guys there last time I remember. I will do that and see how we can
change the default font in the terminal for Arabic.
About lam-alif ligature, if you meant using the letter "alif" + letter
"lam" then they can be displayed in a good shape in the terminal. But if
you meant this one combined letter which has both alif and lam already
together then it is indeed broken in the terminal. However, not so many
Arabic people use this letter, and as a workaround, it can be written as
a normal lam + normal alif in order to be displayed like the first line
in my new attached screenshot. I think it's not a big deal for now.
For bug 2. Wow! Indeed as you said, it works well now and the text is
displayed correctly just like in Gedit. I attached a screenshot.
Is there a way where we can use this "printf '\e[?2501h'" workaround in
the GNOME Terminal in Ubuntu, at least only when the Arabic language is
set for the system by default? If the user is an Arabic-based user, then
it makes sense to offer this advantage for him/her in the terminal I
believe.
For example, we can append this by default to ~/.bashrc:
systemlanguage=${LANG:0:2}
if [ $systemlanguage == "ar" ]; then printf '\e[?2501h'; fi
If the system language is "ar", it will enable the auto-detection of
paragraph direction in the VTE session. What do you think? I can suggest
this in the Ubuntu Discourse too for the i18n guys.
Thank you Egmont for your help!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/2002290
Title:
Poor Arabic rendering in VTE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "VTE with RTL enabled.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5640984/+files/VTE%20with%20RTL%20enabled.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "lam-alif ligature in GNOME Terminal (without, with).png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5640983/+files/lam-alif%20ligature%20in%20GNOME%20Terminal%20%28without%2C%20with%29.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983794] Re: Evolution not deleting autosave files
** Changed in: evolution (Ubuntu) Assignee: Nathan Teodosio (nteodosio) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618363] Re: /dev/urandom not included in chroot, leads to crashes with static key
** Changed in: network-manager-openvpn (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1618363 Title: /dev/urandom not included in chroot, leads to crashes with static key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1618363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
yes, you should fix it, first maybe try to $ sudo apt install --reinstall libnm0 if that doesn't work $ sudo rm /lib/x86_64-linux-gnu/libnm.so.0 $ sudo ln -s libnm.so.0.1.0 /lib/x86_64-linux-gnu/libnm.so.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
Not willingly, Sebastien. Maybe it has something to do with the software back in time (though I don't remember having to recover the system at any point in time so far). Can I make the it point to the correct path? How should I do it? Thanks again for your time and patience! Fernando El 12/1/23 a las 11:31, Sebastien Bacher escribió: > Ok, that's the issue then, that libnm.so.0.1.0.backup.20220225 is weird > ... is that something you remember maybe doing? it should be pointing to > libnm.so.0.1.0 > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
Ok, that's the issue then, that libnm.so.0.1.0.backup.20220225 is weird ... is that something you remember maybe doing? it should be pointing to libnm.so.0.1.0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
lrwxrwxrwx 1 root root 30 ene 11 11:13 /lib/x86_64-linux-gnu/libnm.so.0 -> libnm.so.0.1.0.backup.20220225 El 12/1/23 a las 10:59, Sebastien Bacher escribió: > ls -l /lib/x86_64-linux-gnu/libnm.so.0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1997996] Re: when in Trash, no dedicated top banner
yes, see https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/943 with screenshots, they only display it when autoclean is activated now, empty and restore actions are easy enough to access, you also don't have a bar for copy/paste/etc and it's not blocking user to find those actions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1997996 Title: when in Trash, no dedicated top banner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1997996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002521] Re: Incompatibility issue between g-c-c and libnm0
it's quite weird, and $ ls -l /lib/x86_64-linux-gnu/libnm.so.0 ? it's an issue which seems local to the system but it's unclear what the problem could be -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2002521 Title: Incompatibility issue between g-c-c and libnm0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2002521/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002618] Re: Нет перевода на русский язык. Хочу перевести. Мне это интересно.
deepl.com translation: "There is no translation into Russian. I want to translate it. I'm interested in it." -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2002618 Title: Нет перевода на русский язык. Хочу перевести. Мне это интересно. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2002618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Comment #50 is a kernel bug in the nouveau driver that is not relevant here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
MUTTER_DEBUG_FORCE_KMS_MODE=simple Didn't solve the issue for me. This problem happens only while using the nouveau driver and I have filed a bug here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/2002314 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002618] Re: Нет перевода на русский язык. Хочу перевести. Мне это интересно.
Ошибся все работает. ** Changed in: gimp (Ubuntu) Status: Invalid => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2002618 Title: Нет перевода на русский язык. Хочу перевести. Мне это интересно. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2002618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2002618] [NEW] Нет перевода на русский язык. Хочу перевести. Мне это интересно.
Public bug reported: Нет перевода на русский язык. Хочу перевести. Мне это интересно. ** Affects: gimp (Ubuntu) Importance: Undecided Status: Opinion ** Changed in: gimp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2002618 Title: Нет перевода на русский язык. Хочу перевести. Мне это интересно. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2002618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
