This bug was fixed in the package gjs - 1.71.1-1
---
gjs (1.71.1-1) experimental; urgency=medium
* New upstream release:
- New JavaScript features! This version of GJS is based on SpiderMonkey 91
For more information, look them up on MDN or devdocs.io
- It's now possib
This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
72~ubuntu2
---
gnome-shell-extension-ubuntu-dock (72~ubuntu2) jammy; urgency=medium
[ Marco Trevisan (Treviño) ]
* schemas/10_ubuntu-dock.gschema.override: Remove hardcoded theme
* debian/rules: Also provide a
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: gjs (Ubuntu)
Importance: Medium => High
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Opinion => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960898
Title:
Wayland sessions crash with Gjs:ERROR:../gi
** Changed in: gjs (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-gjs-1.71.2 fixed-upstream
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: gjs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gjs (Ubuntu)
Importance: Undecided => Medium
** Changed in: gjs (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gjs (Ubuntu)
Status: New => In Progress
--
AlderHorst, thanks for the feedback.
So gjs in this case should definitely not crash, and I've fixed it there
[1] (will prepare a package soon).
I'm quite curious to understand how is possible that Gio would emit a
null device in such case, but that's another issue I'll have to handle.
I'll try
May importante. I use Wireguard and have a mounted sft there. Since my update
to 21.10 it do not work anymore.
Goal here is to have imediately after login a mounted drive.
I never found a recommended way how to automount a network drive in Ubuntu.
$HOME/.local/share/systemd/user/
contain a .mou
1.) Did first test from Marco trevisan
2.) after that I run 'gsettings set org.gnome.shell.extensions.dash-to-dock
show-mounts true'
3.) than restarted to Wayland
4.) got back to xorg exported the data with journalctl -b0 >Journal.txt
5.) this file is around 3MB in size so I compacted it to journa
This bug shouldn't be given High priority. There are no other reports of
it, even on errors.ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960898
Title:
Wayland sessions crash with Gjs:ER
Once you've enabled the mount point again, could you please tell me what
are you mountable devices?
In any case it would be helpful if you could manually edit (just use
sudo with your editor) the file /usr/share/gnome-
shell/extensions/ubuntu-d...@ubuntu.com/locations.js so that it contains
at aro
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960898
Title:
Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool
InterfacePrototype::has_instance_impl
#5 "gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts
false" helped. Login now work.
Thanks a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960898
Title:
Wayland sessions cras
14 matches
Mail list logo