[Bug 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch() ["bwrap: setting up uid map: Permission denied" ; "Failed to fully launch
Based on Marco's comment above, I suspect we need to add an AppArmor
profile for gnome-shell-portal-helper.
Using the example in that blog post, this would be the simplest possible
policy:
abi ,
include
/usr/libexec/gnome-shell-portal-helper flags=(default_allow) {
userns,
}
Write that to a file, then load it into the kernel with "sudo
apparmor_parser -r filename". That will persist until you reboot the
system.
If this does indeed solve the problem, then we need to look at adding a
policy to gnome-shell-portal-helper in the main packaging. It'd be worth
looping in the security team, since they would probably want something a
little more than this 5 line version.
--
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/2051574
Title:
gnome-shell-portal-helper crashed with SIGTRAP in
waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch() ["bwrap:
setting up uid map: Permission denied" ; "Failed to fully launch dbus-
proxy: Child process exited with code 1"]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051574/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
@Jonas: If KDE is launching apps in the same way gnome-shell was, it is inherently racy. It needs to make sure the child process is in the new cgroup before executing the application. Doing the cgroup move after the app is already running causes problems if the application itself wants to configure cgroups, and could let child processes of the app itself escape the cgroup if they are created before the launcher tries to move the app. -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
I did a search through the KDE bug tracker, and it looks like someone reported the same root problem back in 2020: https://bugs.kde.org/show_bug.cgi?id=423756 ** Bug watch added: KDE Bug Tracking System #423756 https://bugs.kde.org/show_bug.cgi?id=423756 -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
I've filed https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565 upstream to cover the gnome-shell problem. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6565 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565 Importance: Unknown Status: Unknown -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
> So, I feel snapd tracker should somewhat be able to track that an app > changed its cgroup and move it back to what it belongs, but as discussed > in https://github.com/systemd/systemd/issues/26925 there's nothing > telling us that right now. There is no "snapd tracker". It's the "snap run" code that moves itself to a new cgroup before setting up the sandbox, dropping privileges, and executing the confined application. At that point, it has no permission to talk to systemd. It's basically working like "systemd-run --scope" would: it sets up the environment appropriately and then lets the app take over. -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
Another idea for how to synchronise the StartTransientUnit call without resorting to passing pipe file descriptors to the child: we could simply have the child_setup_func call kill(getpid(), SIGSTOP). The parent process can now do the cgroup move at its leisure, and then send a SIGCONT to the child to let it continue to the exec() call. -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
@Batuhan: it's different code, but looks to be the same type of problem: https://github.com/KDE/kio/blob/5bda428992cbd168fc1898661d80a089a8217449/src/gui/systemd/scopedprocessrunner.cpp#L13-L41 It's moving the process to a new cgroup after the application has started executing (so happens without any synchronisation with what the application is doing). -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I've created https://github.com/snapcore/snapd/pull/12627 as a proposed fix for the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
Okay. In a clean Lunar VM with glib 2.75.3 installed and ibus enabled as
described in the bug description, I could reproduce the input problems
in Firefox. I saw the following AppArmor denial in the dmesg logs:
[ +0.343553] audit: type=1400 audit(1678248386.012:62):
apparmor="DENIED" operation="connect" profile="snap.firefox.firefox"
name="/home/james/.cache/ibus/dbus-THbBfRNt" pid=2398 comm="pool-
firefox" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
I edited /var/lib/snapd/apparmor/profiles/snap.firefox.firefox and added
the following rule:
@{HOME}/.cache/ibus/dbus-* rw,
After reloading the policy with "apparmor_parser -r
.../snap.firefox.firefox", keyboard input worked again. So that confirms
my guess about the cause of the problem. This is something we can fix
via a snapd update.
Longer term, we should get these snaps using ibus's portal interface,
which is both more secure (i.e. suitable to allow in the desktop
interface) and should be immune to future changes of this type.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2008279
Title:
glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
IBus is turned on
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
This seems like the most likely culprit: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3005 This basically means that code that would have created an abstract namespace socket in glib 2.74.x now creates a regular unix domain socket in 2.75.x. We have AppArmor rules in snapd's desktop-legacy interface granting access to the abstract namespace socket in $XDG_CACHE_HOME, but nothing for the equivalent regular socket: https://github.com/snapcore/snapd/blob/d5f47ca71fcd8a884072e75391a7e55d9ec9d145/interfaces/builtin/desktop_legacy.go#L142-L149 I still need to verify this is the actual cause, but if so it should be relatively simple to update snapd's AppArmor rules to allow access to this socket. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I think last time we had problems like this it was due to changes in the location of the socket for ibus's private D-Bus bus. Looking into the glib diffs for clues. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
> Is there any option to do this via portals - ie can evince use > org.freedesktop.portal.OpenURI to open the URI? Would then this > allow to avoid going via xdg-open? Evince is using g_app_info_launch_default_for_uri(), which can use the portal interface: https://gitlab.gnome.org/GNOME/evince/-/blob/main/shell/ev- window.c#L6775-6778 However, it only does this as a fallback if no desktop file supports the URI. This is intended to allow a confined app to handle some file types within the sandbox before falling back to portals for everything else. In the case of Evince running on the host system and seeing all the desktop files in /usr/share/applications and other locations, it likely won't ever call the portal API. It'd be possible to code in explicit portal API calls, but it isn't something that Evince packaged as a flatpak or snap would need. So it might end up as a distro patch we'd be on the hook to maintain forever. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I've updated the description with the SRU bug template. I think this includes all the relevant info? ** Description changed: - I'm trying to run chromium installed via snap in Ubuntu 20.10 when - running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + [Impact] - > chromium + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap +confined X11 applications, due to gnome-shell no longer listening on an +abstract socket for connections. + + * The fix, which has been accepted into upstream's gnome-3-38 branch +reverts the change removing the abstract socket, and fixes the bug that +prompted it's removal. + + [Test Case] + + * Start with a stock Ubuntu 20.10 desktop install. + + * At the GDM login screen, after selecting your user account use the gear +icon to select the "Ubuntu on Wayland" session, and log in. + + * Ensure Chromium is installed by running "sudo snap install chromium". + + * Try to run "chromium" from the terminal. Without the fix, it will fail +with the error "Unable to open X display". With the fix applied, it +will launch as normal. + + [Regression Potential] + + * The patch modifies the logic gnome-shell uses to launch Xwayland. So +there is a potential that the change could break X11 application +support on the Wayland session. + + * The default configuration for gnome-shell is to launch Xwayland on +session start, so it should be immediately obvious if there are +problems. + + * In addition to checking snapped X11 apps like Chromium, verify that a +few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). + + [Other Info] + + * Running "ss -xlp | grep Xwayland" should show that it is listening on +both "/tmp/.X11-unix/X0" (the regular unix domain socket) and +"@/tmp/.X11-unix/X0" (the abstract socket). + + --- + I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + + > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] - * Users who select the Wayland session on Ubuntu 20.10 cannot run snap -confined X11 applications, due to gnome-shell no longer listening on an -abstract socket for connections. + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap + confined X11 applications, due to gnome-shell no longer listening on an + abstract socket for connections. - * The fix, which has been accepted into upstream's gnome-3-38 branch -reverts the change removing the abstract socket, and fixes the bug that -prompted it's removal. + * The fix, which has been accepted into upstream's gnome-3-38 branch + reverts the change removing the abstract socket, and fixes the bug that + prompted it's removal: + +https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] - * Start with a stock Ubuntu 20.10 desktop install. + * Start with a stock Ubuntu 20.10 desktop install. - * At the GDM login screen, after selecting your user account use the gear -icon to select the "Ubuntu on Wayland" session, and log in. + * At the GDM login screen, after selecting your user account use the gear + icon to select the "Ubuntu on Wayland" session, and log in. - * Ensure Chromium is installed by running "sudo snap install chromium". + * Ensure Chromium is installed by running "sudo snap install chromium". - * Try to run "chromium" from the terminal. Without the fix, it will fail -with the error "Unable to open X display". With the fix applied, it -will launch as normal. + * Try to run "chromium" from the terminal. Without the fix, it will fail + with the error "Unable to open X display". With the fix applied, it + will launch as normal. [Regression Potential] - * The patch modifies the logic gnome-shell uses to launch Xwayland. So -there is a potential that the change could break X11 application -support on the Wayland session. + * The patch modifies the logic gnome-shell uses to launch Xwayland. So + there is a potential that the change could break X11
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I had a go at fixing this in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 -- taking the patches from that MR and applying them to the Groovy mutter source package gave me a Wayland session that supported X11 snaps again. It is probably worth waiting for a review from upstream before going further. I've done the testing they asked for with the "autostart- xwayland" feature enabled, so hopefully that will come soon. -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
I've filed https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 upstream about this regression. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1454 https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 -- 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/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
Looking at the reasoning behind that change, Mutter introduced lazy initialisation of Xwayland: binding the two sockets, and starting Xwayland when someone connected to the abstract namespace socket. Flatpak apps apparently can't speak to the abstract namespace socket, so would hang forever when started since the connection to the non-abstract /tmp/.X11-unix socket was never accepted. Rather than fixing the initialisation logic to start Xwayland on connect to either socket, they dropped the abstract namespace socket. I'll talk to the snapd folks about it, but this sounds like it should be dealt with on the Mutter side. ** Changed in: mutter (Ubuntu) Status: Invalid => Confirmed -- 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/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1424 is definitely the culprit here. Snaps depend on access to the abstract namespace socket to function correctly. Inside the sandboxes, snaps see a private /tmp that is under their complete control. So there is no /tmp/.X11-unix directory there. They can see the abstract namespace socket though, which the client libraries will use automatically. -- 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/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867080] Re: No mouse cursor drawn in Wayland session
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080/+attachment/5335924/+files/lspci.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/1867080 Title: [radeon] No mouse cursor drawn in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1867080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867080] [NEW] No mouse cursor drawn in Wayland session
Public bug reported: When I upgraded my desktop yesterday, I could no longer see the mouse cursor on the screen. It still responded to mouse clicks (e.g. context menu on right click, pushing the mouse to the top left and left clicking went to spread mode, etc). This only seems to affect the Wayland session: when I switched back to X11 the mouse cursor was visible again. I also noticed that the mouse cursor is absent on the GDM login screen, which I understand is also a Wayland based gnome-shell session. I tried reproducing the bug on my laptop, but the mouse cursor shows just fine there. The main differences between the systems are the GPU (radeon vs. intel) and number of monitors (dual screen vs. single). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 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-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 10:28:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2013-10-29 (2325 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1867080 Title: No mouse cursor drawn in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865371] Re: Mouse Cursor or Touchpad indicator/pointer not working
I noticed something like this on my desktop system after upgrading. It only seems to affect Wayland sessions (i.e. GDM login screen and Ubuntu on Wayland). The mouse still works (i.e. desktop responds to clicks), but no cursor is drawn. Everything seems fine on my laptop though. The main differences between the two systems are: 1. Radeon graphics on the desktop vs. Intel on the laptop 2. dual monitors on the desktop 3. The desktop is using a "Thinkpad Compact USB Keyboard" as the mouse (i.e. single USB device exposing two HID interfaces). Given that the reporter here is using an AMD APU, I wonder if this is an interaction between gnome-shell and the radeon driver? -- 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/1865371 Title: Mouse Cursor or Touchpad indicator/pointer not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Is there some way gnome-software can inform the plugin that it is performing a non-interactive operation? If so, then the plugin could use snapd_client_set_allow_interaction() to suppress any potential pokit dialogs from the operation. It wouldn't allow the operation to succeed, but it also wouldn't leave the user with an authentication dialog open when they unlock their screen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811707] Re: gnome-calculator snap does not respect shell theme
If you are running an X session, then you are running into a different issue. The set of circumstances that lead to the problem on Wayland (different gsettings defaults inside and outside of confinement) do not apply to X11 where the theme is exposed by the host over XSETTINGS (so sees the default of the host system). I'd suggest filing a new bug with more details if you're on an X11 session. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1811707 Title: gnome-calculator snap does not respect shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1811707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816436] Re: gnome-terminal window shrinks when changing tabs
At didrocks' request, I've also filed this here: https://github.com/ubuntu/yaru/issues/1196 ** Bug watch added: github.com/ubuntu/yaru/issues #1196 https://github.com/ubuntu/yaru/issues/1196 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1816436 Title: gnome-terminal window shrinks when changing tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816436/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816436] [NEW] gnome-terminal window shrinks when changing tabs
Public bug reported: I am using gnome-terminal 3.31.90-1ubuntu1 on a Disco desktop. If I create a gnome-terminal window and add a second tab, the window will shrink by one line each time I switch tabs. This seems to be theme related, since it happens with Yaru but not with Adwaita. Some aspects of my configuration that seem to be relevant: 1. Using yaru-theme-gtk version 19.04 2. Under the org.gnome.desktop.interface gsettings schema, I have scaling-factor set to 1 and text-scaling-factor set to 1.5 This may lead to some widgets size being dictated by the text height where they might be governed by min-height otherwise. I suspect that the height notebook tabs are changing when changing from selected to unselected state, and gnome-terminal then tries to resize the window to align to the terminal character grid. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1816436 Title: gnome-terminal window shrinks when changing tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816436/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810755] [NEW] xdg-document-portal 1.0.2-1ubuntu1 crashes when trying to save to a non-existant file
*** This bug is a duplicate of bug 1810757 *** https://bugs.launchpad.net/bugs/1810757 Public bug reported: When using the desktop portal API to save a file, the xdg-document- portal service crashes if we try to save to a new file name. Steps to reproduce: 1. On an Ubuntu 18.10 system, install the test-snapd-portal-client snap: snap install --edge test-snapd-portal-client 2. run the save-file test: test-snapd-portal-client save-file "foo" 3. in the file chooser, select a file name that does not exist. Actual results: The command exits with the following error (eliding the traceback): ConnectionAbortedError: [Errno 103] Software caused connection abort: '/run/user/1000/doc/eca716d3/xyz.txt' Furthermore, "systemctl --user status xdg-document-portal.service" reports the following error: Jan 07 17:38:06 scruffy xdg-document-portal[30685]: error: Invalid id snap.test-snapd-portal-client: Names must contain at least 2 periods Jan 07 17:38:06 scruffy xdg-document-portal[30685]: error: ** Jan 07 17:38:06 scruffy xdg-document-portal[30685]: xdg-desktop-portal:ERROR:document-portal/document-portal-fuse.c:206:xdp_inode_destroy: assertion failed: (inode->dir_fd == -1) Expected results: The file should be created with the contents "foo". The problem is not present with xdg-desktop-portal 1.0.3. I suspect the fix is one of these extra patches alexl suggested we take: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop- portal/+bug/1691649/comments/10 ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1810757 /usr/libexec/xdg-document-portal:6:g_assertion_message:g_assertion_message_expr:xdp_inode_destroy:xdp_inode_unref_internal:xdp_inode_unref_internal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1810755 Title: xdg-document-portal 1.0.2-1ubuntu1 crashes when trying to save to a non-existant file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1810755/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Looking at the gnome-shell JS code referenced by the stack trace, it appears it is indeed disabling extensions when locking the screen. The screenShield.js code handles the lock screen, and pushes and pops a "session mode" of "lock-screen". In sessioMode.js, the "lock-screen" mode is defined with allowExtensions=false. Finally, extensionSystem.js watches session mode changes and calls the various extension enable/disable callbacks as needed. So somehow ubuntu-dock has a stale window in Transparency._trackedWindows that triggers an exception while trying to disable the dock when locking the screen. It fails to fully disable the dock, so it displays over the top of the lock screen. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
The above stack trace seems to be tied to this other message:
Nov 16 11:41:38 scruffy gnome-shell[5626]: Object Meta.WindowActor
(0x560d5092bb00), has been already deallocated — 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.
The error seems to be on the disconnect() call in
Transparency.disable():
for (let key of this._trackedWindows.keys())
this._trackedWindows.get(key).forEach(id => {
key.disconnect(id);
});
this._trackedWindows.clear();
Presumably the remainder of the clean-up performed by this function and
its callers is not performed, leaving the shell in an inconsistent
state.
I'm still not sure why gnome-shell is trying to disable the extension.
Does it disable extensions when locking the screen?
--
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/1769383
Title:
Ubuntu dock/launcher is shown on the lock screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I noticed this behaviour on my Ubuntu 18.10 system. It is running the Wayland session, and I only have the ubuntu-d...@ubuntu.com and ubuntu- appindicat...@ubuntu.com extensions installed (i.e. no upstream dash-to- dock). I looked in the journal and found the attached GJS stack trace, which seems to be triggered by the disable() call. I haven't been manually enabling/disabling extensions, so don't know why the code path would have been triggered. It might mean some crud was left behind though. ** Attachment added: "stacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1769383/+attachment/5213307/+files/stacktrace.txt -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793298] [NEW] snapd-glib changes needed for pulseaudio snap policy module xenial backport
Public bug reported: The xenial backport of the fix for 1781428 malfunctioned due to the use of snapd-glib behaviour introduced after the version included in xenial: namely auto-connection (and reconnection) to the snapd socket that was introduced in snapd-glib 1.24. With the policy module loaded, Pulse Audio will contact snapd to check the interfaces plugged by a client in order to decide whether to provide access to the microphone. As the Pulse Audio daemon is long lived, it is not uncommon for the socket connection to be disconnected (either due to a timeout, or because snapd is upgraded while the user is logged in). So simply adding a snapd_client_connect() call at module initialisation time is not sufficient. The specific snapd-glib calls that could be affected are: * snapd_client_list_one_async * snapd_client_get_interfaces_async ** Affects: snapd-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1793298 Title: snapd-glib changes needed for pulseaudio snap policy module xenial backport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1793298/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774560] Re: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
bionic-proposed has a 3.28.2 package, so this should be resolved for that release shortly. -- 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/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774560] [NEW] xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
Public bug reported: When running on a Wayland session, if xdg-desktop-portal-gtk is asked to display a window on behalf of a Wayland app, it gets disconnected from gnome-shell with one of these messages: Gdk-Message: 09:49:31.837: Lost connection to Wayland compositor. Gdk-Message: 09:50:28.438: Error 71 (Protocol error) dispatching to Wayland display. Running it with WAYLAND_DEBUG=1, the underlying error message that GDK seems to eat is: [3471970.531] wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") That is, when it tries to associate the dialog box with the confined application's window. It seems the underlying bug is in in Mutter: https://gitlab.gnome.org/GNOME/mutter/issues/138 According to duflu, the patch referenced in that bug report has been merged for 3.28.2 and 3.29.2. It seems like a candidate to backport to bionic if we want portals to work on the (non-default) Wayland session. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1661590] Re: GNOME Software only supports running one application from a snap
@simosx: I gave this another test on a clean xenial VM with the same gnome-software version as you. Each time it launched the main "libreoffice" command (showing a window asking to open recent files or create a new document in one of the libreoffice applications). gnome-software continues running when you close the window, so is it possible you were still running the old version when you saw the failure? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1661590 Title: GNOME Software only supports running one application from a snap To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1661590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1690280] Re: Classic confined snaps don't install
** Description changed: [Impact] Apps that use classic confinement show up in search results but don't install. [Test Case] 1. Open GNOME Software 2. Search for a classic snap, e.g. "atom" 3. Install snap Expected result: Either: a) Snap is installed b) Snap is not installed and error given c) Snap is installed but user needs to provide some sort of confirmation since it is not confined. Observed result: Snap is not installed, no error given. + + [Regression Potential] + Patch changes the code path used to request installation of all snap packages. Ensure that strict confined snaps continue to be installed with correct confinement. + + For example, try installing "ohmygiraffe" via gnome-software, then run + "snap info ohmygiraffe" from a terminal. The "installed:" line should + not include the word "classic". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1690280] Re: Classic confined snaps don't install
Here's a debdiff for the Xenial package update based on Robert's work. I don't have upload rights to upload it myself. ** Patch added: "gnome-software_3.20.5-0ubuntu0.16.04.7_3.20.5-0ubuntu0.16.04.8.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1690280/+attachment/5032747/+files/gnome-software_3.20.5-0ubuntu0.16.04.7_3.20.5-0ubuntu0.16.04.8.diff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721735] Re: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed
I've got an (as yet unmerged) snapd branch to help with this: https://github.com/snapcore/snapd/pull/4055 It got a review yesterday, so should go in the next snapd release. This is basically doing (1), returning a Forbidden error when the user dismisses the dialog. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1721735 Title: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1721735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
Snapd side changes: https://github.com/snapcore/snapd/pull/4061 It looks like snapd-glib might need a change too, since it looks like this will still be mapped to SNAPD_ERROR_FAILED in parse_result() (I think falling back to treating 401 as SNAPD_AUTH_DATA_REQUIRED will do). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1724316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
Yep. There is code to prevent refreshing the macaroon if the user has changed their password since it was created: http://bazaar.launchpad.net/~canonical-isd-hackers/canonical-identity- provider/trunk/view/head:/src/identityprovider/auth.py#L661 This should help in reproducing the bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1724316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1724316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
Discussion started here: https://forum.snapcraft.io/t/handling-invalid-credentials/2526 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
So further investigation, the "cannot authenticate to snap store: " part of the error is only added by snapd for an unexpected error: https://github.com/snapcore/snapd/blob/master/store/auth.go#L190-L204 I believe this is being called via the refreshDischarges() method, intended to keep the store macaroon up to date. This is called by any snapd API that talks to the store, so it isn't surprising we'd hit it during gnome-software start up. I wonder if changing your Ubuntu One password would be enough for the store to refuse to refresh the macaroon? So it looks like the fix probably requires the following: 1. snapd to handle the INVALID_CREDENTIALS response from the store and produce an error response that snapd-glib can distinguish. 2. snapd-glib to handle this error case and map it to one of its error codes (either a new one, or fold it into invalid-auth-data?) 3. if snapd-glib produces a new error code, for gnome-software's snap plugin to map this to an appropriate error code. The end result should be for gnome-software to call the /v2/login end point again, probably passing its existing macaroon so it updates the existing snapd user rather than creating another (i.e. what would happen to paid snaps for a discarded snapd user ID when it comes time to refresh?). I'll follow up with the snappy team to verify that this is the way forward. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
The "Provided email/password is not correct." part of the error message appears to be coming through straight from the store. This most likely means you logged in to gnome-software using Ubuntu One credentials at some point in the past, and the credentials snapd has stored are no longer valid. It might be possible to reproduce this by logging in in gnome-software (currently possible by cancelling the polkit dialog), stopping snapd, editing /var/lib/snapd/state.json to tamper with the store-macaroon value and starting snapd again. I'll need to verify if this happens. The "Sorry, something went wrong" comes from gnome-software itself, and indicates that the error could not be classified as one of the GS_PLUGIN_ERROR_* error codes. The code in gnome-software's snap plugin specifically checks for various authentication related error conditions (SNAPD_ERROR_AUTH_DATA_REQUIRED and SNAPD_ERROR_AUTH_DATA_REQUIRED in particular), but that clearly isn't being hit. So I think there are two possibilities here: 1. libsnapd-glib isn't returning the correct error type for this case 2. snapd isn't providing enough info to libsnapd-glib to decode the error -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722195] Re: no policy kit auth dialog to install or remove a snap
I set up a clean VM running up to date artful, which includes snapd-2.28.5+17.10 (so no copying of policy files or changing channel for core snap), and couldn't reproduce this. I started gnome-software, and tried to install the Hiri snap and got the expected polkit prompt. I did get the following message though: Unable to install Hiri Failed to read from snapd: Error receiving data: Connection reset by peer Snapd restarted during the install, presumably after it installed the core snap, so this seems like another variation of bug 1718170. If you got a polkit prompt from the command line "snap" utility but not in gnome-software, that would indicate that it was not sending the X -Allow-Interaction header. We added that in snapd-glib 1.19, and you've got 1.23 installed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1722195 Title: no policy kit auth dialog to install or remove a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1722195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
Changing the gnome-control-center task to low priority, since the restart loop is gone with the new whoopsie-preferences that has landed in the archive. The gnome-control-center change is nice, but I don't think it is critical to releasing 17.10 any more. ** Changed in: gnome-control-center (Ubuntu) Importance: Medium => Low ** Changed in: whoopsie-preferences (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- 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/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
** Also affects: whoopsie-preferences (Ubuntu) Importance: Undecided Status: New -- 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/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
So I think I've got things sorted out by (a) switching to call SetReportCrashes async to avoid blocking the UI, and (b) not calling SetReportCrashes if we're asked to set it to the current (cached) value of the property. I've noticed that if whoopsie-preferences exits while the privacy panel is open, I get a bit of a bounce when toggling the switch next. This seems to be due to whoopsie-preferences sending out a stray change notification signal on start up: method call time=1507538340.672978 sender=:1.1499 -> destination=com.ubuntu.WhoopsiePreferences serial=30 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false signal time=1507538340.756225 sender=:1.1507 -> destination=(null destination) serial=9 path=/com/ubuntu/WhoopsiePreferences; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "com.ubuntu.WhoopsiePreferences" array [ dict entry( string "ReportMetrics" variant boolean true ) dict entry( string "ReportCrashes" variant boolean true ) ] array [ ] method call time=1507538340.756590 sender=:1.1499 -> destination=:1.1507 serial=31 path=/com/ubuntu/WhoopsiePreferences; interface=org.freedesktop.DBus.Properties; member=GetAll string "com.ubuntu.WhoopsiePreferences" method call time=1507538340.757395 sender=:1.1499 -> destination=com.ubuntu.WhoopsiePreferences serial=32 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true signal time=1507538341.034321 sender=:1.1507 -> destination=(null destination) serial=14 path=/com/ubuntu/WhoopsiePreferences; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "com.ubuntu.WhoopsiePreferences" array [ dict entry( string "ReportCrashes" variant boolean false ) ] array [ ] method call time=1507538341.035076 sender=:1.1499 -> destination=:1.1507 serial=33 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false So essentially whoopsie-preferences is sending out an unsolicited PropertiesChanged signal on startup with the initial values before processing the SetReportCrashes method call. Then gnome-control-center responds by trying to match the switch state leading to the bounce. So I guess I'll have to dive into the whoopsie-preferences code to see if I can silence the stray signal. -- 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/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
This is definitely a gnome-control-center bug rather than whoopsie. I can reproduce it like so: 1. open gnome-control-center, and select the privacy panel. 2. ensure that problem reporting is turned on. 3. wait for whoopsie-preferences to exit on timeout (or manually kill it). I then see traffic like the following on the system bus: method call time=1507286449.661622 sender=:1.325 -> destination=:1.336 serial=96 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false method call time=1507286449.918969 sender=:1.325 -> destination=:1.336 serial=97 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true method call time=1507286450.216068 sender=:1.325 -> destination=:1.336 serial=98 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false method call time=1507286450.529908 sender=:1.325 -> destination=:1.336 serial=99 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true ... which continues until I kill gnome-control-center. Whoopsie relaunching is a direct consequence of these D-Bus method calls coming from gnome- control-center. It looks like the logic controlling the GtkSwitch gets into a loop when whoopsie-preferences stops. The D-Bus method calls are synchronous, so this also ends up locking the UI. I'll have a look into this properly next week. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- 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/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend
** Bug watch added: Red Hat Bugzilla #1448962 https://bugzilla.redhat.com/show_bug.cgi?id=1448962 ** Also affects: libinput (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1448962 Importance: Unknown Status: Unknown -- 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/1715479 Title: Touchpad won't stay disabled after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715479/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend
While looking around for code that might resume the touchpad, I noticed that the libinput master code was a bit different to the version we ship: there's a tp_resume_conditional() function that checks sendevents. And checking the history shows up this patch: https://cgit.freedesktop.org/wayland/libinput/commit/src?id=53d53dd18ef14484d632421027cd7b6130013cf0 Fedora is also shipping this as a patch against their libinput-1.8.2 in Fedora 27: https://src.fedoraproject.org/rpms/libinput/blob/f27/f/0001-touchpad- don-t-resume-a-disabled-touchpad.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1715479 Title: Touchpad won't stay disabled after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1715479/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend
So, I don't think there is any problem on the gnome-control-center side: it just sets the org.gnome.desktop.peripherals.touchpad/send-events GSetting key to disabled, and that is persisting over sleeps. The code in mutter watches this key, and calls MetaInputSettings::set_send_events() on each touchpad device, and ensures it is called on each new input device. https://git.gnome.org/browse/mutter/tree/src/backends/meta-input- settings.c#n667 In a Wayland session, this calls libinput_device_config_send_events_set_mode(): https://git.gnome.org/browse/mutter/tree/src/backends/native/meta-input- settings-native.c#n36 The touchpad implementation of this is found here: https://cgit.freedesktop.org/wayland/libinput/tree/src/evdev-mt- touchpad.c#n3089 ... which calls tp_suspend: https://cgit.freedesktop.org/wayland/libinput/tree/src/evdev-mt- touchpad.c#n1670 Which will either leave the touchpad enabled to support soft buttons, or call evdev_device_suspend() otherwise, which closes the underlying device. Looking in /proc, gnome-shell definitely doesn't have the touchpad evdev device open when I disable the touchpad, but somehow opens it again after resume. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1715479 Title: Touchpad won't stay disabled after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1715479/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698035] Re: FFe: gnome-control-center lacks any replacement for unity-control-center's Diagnostics tab for managing crash reports
I've sent our patch upstream to see if we can get a version of it included. I suspect it'll need some changes in order to be acceptable, assuming they want it. So I'll try to address that as needed. ** Bug watch added: GNOME Bug Tracker #788216 https://bugzilla.gnome.org/show_bug.cgi?id=788216 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=788216 Importance: Unknown Status: Unknown -- 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/1698035 Title: FFe: gnome-control-center lacks any replacement for unity-control- center's Diagnostics tab for managing crash reports To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1698035/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698035] Re: gnome-control-center lacks any replacement for unity-control-center's Diagnostics tab for managing crash reports
** Branch linked: lp:~jamesh/gnome-control-center/ubuntu-whoopsie- support -- 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/1698035 Title: gnome-control-center lacks any replacement for unity-control-center's Diagnostics tab for managing crash reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1698035/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1581713] Re: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package
The snapd side of things has been committed. Both on master: https://github.com/snapcore/snapd/commit/44611140566f6e6aa2a3b583e0b2970b69c8f53f ... and the release/2.28 branch: https://github.com/snapcore/snapd/commit/69a00bc4f4e54d7e0312c253b46b97fca834b736 Together with the already released snapd-glib 1.19, this version of snapd will let you install snaps via gnome-software without an Ubuntu One account. Instead you'll get a graphical prompt for your local password, similar to when installing debs. ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1581713 Title: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1581713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704162] Re: Add on/off switch for network connectivity check
** Bug watch added: GNOME Bug Tracker #785117 https://bugzilla.gnome.org/show_bug.cgi?id=785117 ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=785117 Importance: Unknown Status: Unknown -- 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/1704162 Title: Add on/off switch for network connectivity check To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1704162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1690280] Re: Classic confined snaps don't install
** Bug watch added: GNOME Bug Tracker #784773 https://bugzilla.gnome.org/show_bug.cgi?id=784773 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=784773 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1661590] Re: GNOME Software only supports running one application from a snap
** Bug watch added: GNOME Bug Tracker #784600 https://bugzilla.gnome.org/show_bug.cgi?id=784600 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=784600 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1661590 Title: GNOME Software only supports running one application from a snap To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1661590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1661590] Re: GNOME Software only supports running one application from a snap
I put together a gnome-software patch to use the extra info from mvo's snapd change: https://code.launchpad.net/~jamesh/gnome-software/+git/gnome- software/+ref/pick-launch-app It still only supports running one application, but it now favours apps that provide a desktop file, and the snap's main app as a tie breaker. For Libreoffice, this reliably picks the main "libreoffice" binary. It also launches the app via the desktop file if available, so we don't have to guess whether it needs a terminal in that case. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1661590 Title: GNOME Software only supports running one application from a snap To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1661590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1690280] Re: Classic confined snaps don't install
I've made some simple UI changes in the following branch forked from ubuntu-master, based on Robert's patch: https://code.launchpad.net/~jamesh/gnome-software/+git/gnome- software/+ref/classic-snap-install This adds a warning message at the top of the details list when viewing an snap that is not using strict confinement. If we get the text of this right, then this could be enough. Currently it reads: This third party package is not sandboxed. It will have access to your documents. Thinking about it, this warning is equally valid for strictly confined snaps that connect to the home interface. I don't think there is a way to identify such apps based on the metadata returned by "find" API requests though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1690280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1621002] Re: Mediascanner2 test failure on yakkety/{armhf, arm64, ppc64el} with latest dbus-cpp
This is looking like a case of the code being miscompiled under
optimisation. To reproduce, build mediascanner2 using the
"RelWithDebInfo" build type and then run:
./test/test_dbus --gtest_filter=*filter_codec
The test program segfaults when calling Variant::as() on a
variant that should have been initialised by reading out of a
Message::Reader.
When compiling with the "Debug" build type, the test program completes
without error.
I can probably solve the immediate problem in mediascanner2 by disabling
optimisation for the affected file.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1621002
Title:
Mediascanner2 test failure on yakkety/{armhf,arm64,ppc64el} with
latest dbus-cpp
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1621002/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1621002] [NEW] Mediascanner2 test failure on yakkety/{armhf, arm64, ppc64el} with latest dbus-cpp
Public bug reported:
When trying to build a new mediascanner2 release, tests failed on a
number of architectures when building under Yakkety. Some relevant
logs:
https://launchpadlibrarian.net/281862518/buildlog_ubuntu-yakkety-armhf.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
https://launchpadlibrarian.net/282074929/buildlog_ubuntu-yakkety-arm64.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
https://launchpadlibrarian.net/281862178/buildlog_ubuntu-yakkety-ppc64el.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz
The failure is occurring in code not touched by the changes in the silo,
and I suspect that this is related to dbus-cpp or possibly GCC 6.
The segfault doesn't occur on x86, but I was able to reproduce it on my
Chromebook. Attached is a stacktrace from the test_dbus test program.
** Affects: dbus-cpp (Ubuntu)
Importance: Undecided
Status: New
** Affects: mediascanner2 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "stacktrace.log"
https://bugs.launchpad.net/bugs/1621002/+attachment/4736062/+files/stacktrace.log
** Also affects: dbus-cpp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1621002
Title:
Mediascanner2 test failure on yakkety/{armhf,arm64,ppc64el} with
latest dbus-cpp
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1621002/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
I'm not convinced my bug is the same as this one. That said, the changes in the latest dbus-cpp package don't look particularly ABI compatible, which may be the cause of this bug: https://launchpadlibrarian.net/279409841/dbus- cpp_5.0.0+15.10.20151022.1-0ubuntu5_5.0.0+16.10.20160809-0ubuntu1.diff.gz In particular, it adds and removes members from core::dbus::Object, and that type appears to be referenced by a few methods implemented by libdbus-cpp (so this isn't entirely a header-only type). If the applications start working with the old libdbus-cpp.so.5, it is quite possible that they can also be made to work by recompiling them. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
I'm not sure if it is related, but I've encountered test failures in my mediascanner2 silo for dbus-cpp code that previously ran without issue: https://launchpadlibrarian.net/281863370/buildlog_ubuntu-yakkety- arm64.mediascanner2_0.112+16.10.20160831-0ubuntu1_BUILDING.txt.gz It also failed on armhf, powerpc, and ppc64el, but passed on i386, amd64 and s390x. The branches in the silo make no changes to the code being run by the failing tests. I'll report back after I've investigated further. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
One last comment: I tried downloading upstream pygobject 3.20.0 (which was released two days ago), and the scopes run fine using the Xenial typelib. So I think the underlying problem is that we've got a problem of version skew, with the versions of gobject-introspection and pygobject currently in Xenial being incompatible. We either need to downgrade gobject- introspection (and rebuild typelibs for any affected packages), or upgrade pygobject. ** Also affects: pygobject (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1526877] Re: Dbus errors in the console when closing the music-app
For what it is worth, I managed to catch a segfault on shutdown of music-app (i.e. swiping vertically in the app spread) on the phone. I couldn't get a usable apport crash dump, but managed to catch it in gdb. This is with libdbus-cpp 4.3.0+15.04.20151126-0ubuntu1 and libmedia-hub- client 4.0.0+15.04.20151209-0ubuntu1 installed. ** Attachment added: "stacktrace.txt" https://bugs.launchpad.net/music-app/+bug/1526877/+attachment/4536742/+files/stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1526877 Title: Dbus errors in the console when closing the music-app To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1526877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1526877] Re: Dbus errors in the console when closing the music-app
This sounds a lot like bug 1422304, by the look of it. Both QtDBus and dbus-cpp make use of libdbus. Libdbus provides a dbus_shutdown() function that will release various internal global state, which can be used to remove those allocation from the report valgrind produces when analysing your program. Normally applications shouldn't have a need to call it. Anything allocated (connections, method calls, etc) before the call to shutdown can not be used after the call, which is what the _dbus_current_generation assertions are about. dbus-cpp makes a call to dbus_shutdown() as an atexit handler. Unfortunately, Qt hasn't cleaned up its connections at this time, leading to errors. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1526877 Title: Dbus errors in the console when closing the music-app To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1526877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1323681] [NEW] Package description is out of date, claiming this is a header-only dbus-binding
Public bug reported: dbus-cpp includes a library, yet the package description still claims it is a header-only dbus-binding. This should be updated to reflect the current state of the package. ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1323681 Title: Package description is out of date, claiming this is a header-only dbus-binding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1323681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1204599] Re: Unity does not pick up changes to ~/.local/share/applications if it doesn't exist when Unity starts
We use libgnome-menu to build the applications index and watch for changes, so that is where the bug probably resides. The configuration we use is in /etc/xdg/menus/unity-lens- applications.menu and uses the DefaultAppDirs/ directive to pick applications directories rather than specify them manually. Perhaps it only checks for these default directories once on startup, rather than watching the parents of missing default dirs? ** Also affects: gnome-menus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1204599 Title: Unity does not pick up changes to ~/.local/share/applications if it doesn't exist when Unity starts To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/1204599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 381252] [NEW] Font thumbnailer never thumbnails any fonts in Jaunty
Public bug reported: Binary package hint: gnome-control-center gnome-control-center provides a font thumbnailer for Nautilus (gnome- thumbnail-font), but it never manages to produce any thumbnails. The fix for bug 339417 introduced some resource limits to the thumbnailer, but these appear to be set too low. The commit says it limits runtime to 30 seconds, but the code is actually limiting it to 30 microseconds. I've also reported this bug upstream at http://bugzilla.gnome.org/show_bug.cgi?id=584107 ** Affects: gnome-control-center Importance: Unknown Status: Unknown ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #584107 http://bugzilla.gnome.org/show_bug.cgi?id=584107 ** Also affects: gnome-control-center via http://bugzilla.gnome.org/show_bug.cgi?id=584107 Importance: Unknown Status: Unknown -- Font thumbnailer never thumbnails any fonts in Jaunty https://bugs.launchpad.net/bugs/381252 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37828] Re: Text rendered incorrectly in presence of ligatures and justified text
Relinking bug watches. ** Changed in: firefox Importance: Undecided = Unknown Bugwatch: None = Mozilla Bugzilla #331716 Status: Fix Released = Unknown ** Changed in: firefox (Debian) Importance: Undecided = Unknown Bugwatch: None = Debian Bug tracker #362569 Status: Fix Released = Unknown -- Text rendered incorrectly in presence of ligatures and justified text https://bugs.launchpad.net/bugs/37828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37828] Re: Text rendered incorrectly in presence of ligatures and justified text
This bug is certainly not invalid, so please don't mark it as such. There was ample evidence of the problem. The firefox in Hardy is not exhibiting this bug. Firefox does appear to be using ligatures for editable text for fonts that have them. It does not appear to be using ligatures for other text, so the rendering problems on pages that combine fonts-with-ligatures and justified text are gone. Therefore I'm marking the bug fix released. Having Firefox use the available ligatures would be nice, but is not required (it is another problem and probably best tracked upstream). This is enough to allow Ubuntu's default fonts to contain ligatures without causing rendering errors. ** Changed in: firefox (Ubuntu) Status: Invalid = Fix Released -- Text rendered incorrectly in presence of ligatures and justified text https://bugs.launchpad.net/bugs/37828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37828] Re: Text rendered incorrectly in presence of ligatures and justified text
John: the upstream tasks are there to track related activity in related bug trackers. Unlinking them and changing the statuses just gives an incorrect view of their status there. If you think the upstream firefox task should be closed, bring that up at bugzilla.mozilla.org. Same goes for the Debian bug. Kasper: I hadn't realised that firefox 2 was still found in Hardy. I guess it would make sense for a firefox 3 task to be marked fixed and a firefox 2 task open or invalid (if it was decided that no fix would be forthcoming). -- Text rendered incorrectly in presence of ligatures and justified text https://bugs.launchpad.net/bugs/37828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37828] Re: Text rendered incorrectly in presence of ligatures and justified text
John: there are obviously ligatures in the the DejaVu font in Hardy (you can see other GTK apps using them). We can also see that Firefox is not misrendering justified text anymore, so it does look like it has been fixed. We knew that the Firefox guys were rewriting the text rendering code for 3.0 (see previous comments), so it isn't surprising that the bug is now fixed in Hardy. -- Text rendered incorrectly in presence of ligatures and justified text https://bugs.launchpad.net/bugs/37828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 101876] Re: [apport] totem crashed with SIGSEGV in strlen()
Set status from imported bug 176873 ** Changed in: libmms Status: Unknown = Fix Released -- [apport] totem crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/101876 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 133124] Re: MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo
Chris: looking at the stack trace, your crash looks like a different bug. The first few stack frames look similar to bug 103880 though. -- MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo https://bugs.launchpad.net/bugs/133124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for libcairo in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 139468] Re: [gutsy] Totem fullscreen changes monitor refresh rate
The following Gnome bug report is probably relevant: http://bugzilla.gnome.org/show_bug.cgi?id=472494 I realise that the original reporter does not have a dual head system, but I bet the same code is responsible for his symptoms. -- [gutsy] Totem fullscreen changes monitor refresh rate https://bugs.launchpad.net/bugs/139468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 139468] Re: [gutsy] Totem fullscreen changes monitor refresh rate
I have run into similar problems (using totem-gstreamer 2.20.0-0ubuntu1 on Gutsy/AMD64). I have a dual monitor setup configured using xrandr. When switching to fullscreen mode in totem, the output to my secondary monitor was disabled. When exiting fullscreen mode, the second monitor remained powered off until I reactivated it with the xrandr command line tool with a command like: xrandr --output DVI-0 --auto --left-of VGA-0 I also had to fix up my panels, which had all moved to the first monitor. Something that would best be avoided ... So it would seem that Totem is changing the video mode (not sure if it is via RANDR or XFree86-VidModeExtension -- it is linked to both client libraries), but not returning to the original mode. -- [gutsy] Totem fullscreen changes monitor refresh rate https://bugs.launchpad.net/bugs/139468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 123281] Re: gimp won't start, crash in fbFetch_x8r8g8b8()
Bug #133124 is another firefox bug that is likely to be a duplicate of this one. The investigation I did seems to match what has been found out here with a few extra details: 1. The bug is not triggered on x86. 2. The bug is not triggered when the X server was set to 24 bit depth, but does at 16 bits. 3. The following patch to ubuntulooks avoids the crash (and Gimp runs with this patch): http://launchpadlibrarian.net/9497723/ubuntulooks_0.9.12-6-progressbar-fix.patch I agree that this is probably a bug in Cairo, so it is probably still possible to trigger the crash with the ubuntulooks patch applied -- this just stops the theme engine from triggering it. I guess the firefox bugs should be marked as duplicates of this one. -- gimp won't start, crash in fbFetch_x8r8g8b8() https://bugs.launchpad.net/bugs/123281 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 133124] Re: MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo
** Also affects: ubuntulooks (Ubuntu) Importance: Undecided Status: New -- MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo https://bugs.launchpad.net/bugs/133124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for libcairo in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 133124] Re: MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo
After noticing the ubuntulooks_draw_progressbar_trough() call in Søren's stack trace, I tried switching to another theme. While the Human control theme causes Firefox to crash on startup, Firefox runs without problems with the Clearlooks and ClearlooksClassic control themes (which ubuntulooks is based on). So the problem most likely exists in one of the differences between clearlooks and ubuntulooks. -- MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo https://bugs.launchpad.net/bugs/133124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for libcairo in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 133124] Re: MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo
Another data point: I was running my X server in 16-bit graphics mode. If I switched to 24-bit, the Firefox loads correctly with the Human theme. My x86 laptop has no problems in either 16-bit or 24-bit depths. So the requirements to reproduce seem to be: * x86-64 * 16-bit depth * Human control theme (== ubuntulooks theme engine) Does that match anyone else's observations? -- MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo https://bugs.launchpad.net/bugs/133124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for libcairo in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 133124] Re: MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo
Attached is a patch against the ubuntulooks engine's ubuntulooks_progressbar_create_cell() to create a Cairo surface of the same type as the target rather than an RGB24 image surface. With this patch applied, Firefox runs starts fine with the Human theme. The RGB24 image surface was what tipped me off to try different bit depths above. By making the pattern match the target surface's format, the composite fallback routine should be avoided. It is worth noting that while this patch cleared up the crash for me, the bug probably still exists in Cairo's fallback compositing routines. Hopefully there is enough information here to produce a simpler test case though. ** Attachment added: ubuntulooks_0.9.12-6-progressbar-fix.patch http://launchpadlibrarian.net/9497723/ubuntulooks_0.9.12-6-progressbar-fix.patch -- MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo https://bugs.launchpad.net/bugs/133124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for libcairo in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37828] Re: Text rendered incorrectly in presence of ligatures and justified text
Bruce: there are a few things to keep in mind here: 1. The pango patch is not part of Mozilla's builds. That said, most Linux distros apply the patch since upstream Firefox fails to render a number of languages they care about. 2. The version of Firefox in Gutsy uses the same rendering engine as the one in Dapper (Gecko 1.8). 3. The Mozilla guys have been working on complex text rendering (using Pango on Linux) for Gecko 1.9, but that won't reach users til Firefox 3.0. It seems that no one with the knowledge to fix the existing Pango patch to handle ligatures has the time to do so. -- Text rendered incorrectly in presence of ligatures and justified text https://bugs.launchpad.net/bugs/37828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 133124] Re: MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo
If the proprietary nvidia drivers hide the problem, it is probably because of differences in the extensions or visuals/pixel formats supported by the two drivers. In a number of cases, Cairo provides fallbacks if the X server doesn't support a particular feature. So it is likely that different code paths are being executed when run under the different drivers. For reference, I am seeing the same crash on my AMD64 system which has an ATI Radeon 9200 SE (using the Free drivers). -- MASTER [GUTSY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from libcairo https://bugs.launchpad.net/bugs/133124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for libcairo in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120214] Re: Faulty reporting of free space with Sony Ericsson z710
This bug was fixed in the 0.4 release. ** Changed in: gnome-vfs-obexftp (upstream) Status: Fix Committed = Fix Released -- Faulty reporting of free space with Sony Ericsson z710 https://bugs.launchpad.net/bugs/120214 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120214] Re: Faulty reporting of free space with Sony Ericsson z710
I've committed a fix for this in r46. The capability parser now notes if valid free and used space values appeared for a memory type, and the VFS method will not report a free space value if none exist for the selected memory type. This should fix the file copying problem on your Z710. I am still interested in data from your older phone for the test suite, if you can provide it. ** Changed in: gnome-vfs-obexftp (upstream) Importance: Undecided = High Assignee: (unassigned) = James Henstridge Status: Unconfirmed = Fix Committed -- Faulty reporting of free space with Sony Ericsson z710 https://bugs.launchpad.net/bugs/120214 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120214] Re: Faulty reporting of free space with Sony Ericsson z710
Karel: thanks for the folder listing data. I'll add it to the test suite. As for the problem with attempts to remove system folders, could you report a new bug? If it is a bug in the phone though, I can't guarantee that it'll be fixable though. Marcin: It is good to hear that the patch fixes the problem for you. Would you be able to attach capability and folder listing data to this bug so I can add it to the test suite? -- Faulty reporting of free space with Sony Ericsson z710 https://bugs.launchpad.net/bugs/120214 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120214] Re: Faulty reporting of free space with Sony Ericsson z710
Matthias: in the previous bug, you mentioned that your previous phone (a Sony Ericsson K610) worked correctly with the existing code. Do you still have access to this phone? If so, would you mind running a similar set of obexftp commands on it and attaching the output? I want to collect the output of a variety of phones as part of a test suite so that I can make sure that the folder-listing and capability parsing code doesn't regress. -- Faulty reporting of free space with Sony Ericsson z710 https://bugs.launchpad.net/bugs/120214 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
Matthias: I don't think your problem is related to this bug report -- this one is about distinguishing what volume a particular directory resides on and returning the appropriate free space. Your one sounds more like faulty reporting of free space. I've heard of a few other people having trouble with Sony phones, but don't have the hardware to debug it. If you would like to help me debug the problem, I suggest opening a new bug report. I've got a few commands you could run to collect data that would be useful in tracking down the problems. -- Free Space on Phone's SD Card Incorrect in Nautilus https://bugs.launchpad.net/bugs/116912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120214] Re: Faulty reporting of free space with Sony Ericsson z710
** Also affects: gnome-vfs-obexftp (upstream) Importance: Undecided Status: Unconfirmed -- Faulty reporting of free space with Sony Ericsson z710 https://bugs.launchpad.net/bugs/120214 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120214] Re: Faulty reporting of free space with Sony Ericsson z710
Could you provide the following as attachments? obexftp --bluetooth $BDADDR --capability obexftp --bluetooth $BDADDR --list obexftp --bluetooth $BDADDR --list Memory Stick obexftp --bluetooth $BDADDR --chdir Memory Stick --list Each should result in an XML file being printed. The output of --capability is the one that should include the free space value. The last two should give the same result, but may differ if the phone has a few bugs. -- Faulty reporting of free space with Sony Ericsson z710 https://bugs.launchpad.net/bugs/120214 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120214] Re: Faulty reporting of free space with Sony Ericsson z710
Thank you for that info. From the capability list returned, we have: Memory MemTypeDEV/MemType Location/Telefonminne/Location /Memory Memory MemTypeMemory Stick/MemType Location/Memory Stick/Location /Memory Neither of which have a Free element, which would be used to determine the free space. The fact that you are seeing zero free space probably means that this error condition is not being handled properly (i.e. it should be handled as I don't know how much free space there is rather than there is 0 free space). -- Faulty reporting of free space with Sony Ericsson z710 https://bugs.launchpad.net/bugs/120214 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
Fixed in the 0.3 release. ** Changed in: gnome-vfs-obexftp (upstream) Status: Fix Committed = Fix Released -- Free Space on Phone's SD Card Incorrect in Nautilus https://bugs.launchpad.net/bugs/116912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120146] /usr/share/doc/gnome-vfs-obexftp/copyright has inaccurate authors list
Public bug reported: Binary package hint: gnome-vfs-obexftp In the first two releases of gnome-vfs-obexftp, I hadn't bothered to update the AUTHORS file from what was in osso-gnome-vfs-extras. I have since fixed this in the 0.3 release to include a credit for the author of the included osso-gwobex library, and contributors to gnome- vfs-obexftp itself (currently myself and Bastien Nocera). When producing new packages, could you update the package copyright file to reflect this? ** Affects: gnome-vfs-obexftp (Ubuntu) Importance: Undecided Status: Unconfirmed -- /usr/share/doc/gnome-vfs-obexftp/copyright has inaccurate authors list https://bugs.launchpad.net/bugs/120146 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
I've made the above change, which seems to work at the GNOME-VFS level:
import gnomevfs
bda = '00:0E:ED:...'
def free_space(path):
... uri = gnomevfs.URI('obex://[%s]%s' % (bda, path))
... return gnomevfs.get_volume_free_space(uri)
...
free_space('/')
4802560L
free_space('/Images/')
4802560L
free_space('/Memory%20card/')
26442752L
However, I am still seeing 4.6MB free space when browsing Memory card
in Nautilus, so there is probably something else I need to do to get it
working in Nautilus.
** Changed in: gnome-vfs-obexftp (upstream)
Status: Confirmed = In Progress
--
Free Space on Phone's SD Card Incorrect in Nautilus
https://bugs.launchpad.net/bugs/116912
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
Just tried restarting Nautilus again, and things started working. Nautilus now shows 25.2MB free on the memory card, and it let me copy a file to the memory card that wouldn't fit on the phone's memory. So this bug will be fixed for the 0.3 release (provided you have a Nokia phone, or one that provides the same data in folder listings). ** Changed in: gnome-vfs-obexftp (upstream) Status: In Progress = Fix Committed -- Free Space on Phone's SD Card Incorrect in Nautilus https://bugs.launchpad.net/bugs/116912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
** Changed in: gnome-vfs-obexftp (upstream) Importance: Undecided = Medium -- Free Space on Phone's SD Card Incorrect in Nautilus https://bugs.launchpad.net/bugs/116912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
Daniel: I haven't yet set up a place to report bugs in gnome-vfs- obexftp. I should probably register it on Launchpad ... The obexftp method is just using the free space number for the first memory type. I notice the bug on my phone: it is returning the free space for the phone even though I have an MMC card. Looking at a directory listing (obexftp --bluetooth ... --list), I see that it does tell me the memory type for each item in the root directory: ?xml version=1.0? !DOCTYPE folder-listing SYSTEM obex-folder-listing.dtd [ !ATTLIST folder mem-type CDATA #IMPLIED ] folder-listing version=1.0 folder name=Memory card user-perm=RW mem-type=MMC/ folder name=Images created=19800101T08 user-perm=R mem-type=DEV/ folder name=Video clips created=19800101T08 user-perm=R mem-type=DEV/ folder name=Music files created=19800101T08 user-perm=R mem-type=DEV/ folder name=Graphics created=19800101T08 user-perm=R mem-type=DEV/ folder name=Tones created=19800101T08 user-perm=R mem-type=DEV/ folder name=Recordings created=19800101T08 user-perm=R mem-type=DEV/ /folder-listing So with this listing, I should be using the DEV free space value for /Images, but the MMC free space value for /Memory card. I've got no idea if there is a more direct way to work this out than listing the parent folder to find the memory type. So the bug does look fixable, which is good. The alternative would have been to remove the free space calculation code ... -- Free Space on Phone's SD Card Incorrect in Nautilus https://bugs.launchpad.net/bugs/116912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
I just had a look at the OBEX spec, and it seems that this mem-type attribute is not part of the standard. In fact, the inclusion of this attribute in folder listings is the subject of one of Nokia's patent applications (http://www.freepatentsonline.com/20060095537.html), so it is probably not found on other manufacturers phones. -- Free Space on Phone's SD Card Incorrect in Nautilus https://bugs.launchpad.net/bugs/116912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 116912] Re: Free Space on Phone's SD Card Incorrect in Nautilus
** Also affects: gnome-vfs-obexftp (upstream) Importance: Undecided Status: Unconfirmed ** Changed in: gnome-vfs-obexftp (upstream) Assignee: (unassigned) = James Henstridge Status: Unconfirmed = Confirmed -- Free Space on Phone's SD Card Incorrect in Nautilus https://bugs.launchpad.net/bugs/116912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-vfs-obexftp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102296] Re: Bug in Screenshot during using Google Earth
Rejecting malone bug task, and refiling on gnome-utils in Ubuntu (the package containing gnome-panel-screenshot). ** Also affects: gnome-utils (Ubuntu) Importance: Undecided Status: Unconfirmed ** Changed in: malone (upstream) Status: Unconfirmed = Rejected -- Bug in Screenshot during using Google Earth https://bugs.launchpad.net/bugs/102296 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-utils in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
