[Bug 1456965] [NEW] Shouldn't use CSD under Unity
Public bug reported: The new shotwell version uploaded to wily use GtkHeaderBar dialogs, it shouldn't under Unity (see https://mail.gnome.org/archives/shotwell- list/2015-February/msg0.html) ** Affects: shotwell (Ubuntu) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Confirmed ** Tags: block-proposed ** Changed in: shotwell (Ubuntu) Status: New = Confirmed ** Changed in: shotwell (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1456965 Title: Shouldn't use CSD under Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1456965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453549] Re: Cannot publish to Facebook
** Branch linked: lp:~mardy/shotwell/lp1453549 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453549 Title: Cannot publish to Facebook To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453549] Re: Cannot publish to Facebook
I confirm this bug on vivid, shotwell 0.20.2-0ubuntu3. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453549 Title: Cannot publish to Facebook To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453549] Re: Cannot publish to Facebook
Adding logs. It seems that we correctly get an access token from Online Accounts (we are able to get the user information), but the album creation fails. This might be due to the access token have insufficient permissions or to the publishing code itself needed some update. I'll debug this further. ** Attachment added: shotwell log when atempting postng a picture https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1453549/+attachment/4400865/+files/shotwell.log ** Changed in: shotwell (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453549 Title: Cannot publish to Facebook To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453549] Re: Cannot publish to Facebook
** Also affects: webapps-sprint Importance: Undecided Status: New ** Changed in: webapps-sprint Milestone: None = sprint-9 ** Changed in: webapps-sprint Milestone: sprint-9 = sprint-10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453549 Title: Cannot publish to Facebook To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456965] Re: Shouldn't use CSD under Unity
Using that bug as wily-proposed-wily migration block -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1456965 Title: Shouldn't use CSD under Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1456965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457035] [NEW] gedit scrolling bug
You have been subscribed to a public bug: my system: Ubuntu 14.04.2 LTS x64 (updated) Release:14.04 apt-cache policy gedit gedit: Installed: 3.10.4-0ubuntu4 Candidate: 3.10.4-0ubuntu4 Version table: *** 3.10.4-0ubuntu4 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status reproducing bug: open a text file (with some text inside) highlight some text (e.g. 2-3 lines) scroll up and / or down you will notice that the highlighted text will be copy-pasted randomly in your document. if you can't reproduce the bug this way, try opening a 400 lines .py (python) text file (UTF-8 encoded) with python code inside it. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- gedit scrolling bug https://bugs.launchpad.net/bugs/1457035 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453549] Re: Cannot publish to Facebook
Thanks Alberto! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453549 Title: Cannot publish to Facebook To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457035] [NEW] gedit scrolling bug
Public bug reported: my system: Ubuntu 14.04.2 LTS x64 (updated) Release:14.04 apt-cache policy gedit gedit: Installed: 3.10.4-0ubuntu4 Candidate: 3.10.4-0ubuntu4 Version table: *** 3.10.4-0ubuntu4 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status reproducing bug: open a text file (with some text inside) highlight some text (e.g. 2-3 lines) scroll up and / or down you will notice that the highlighted text will be copy-pasted randomly in your document. if you can't reproduce the bug this way, try opening a 400 lines .py (python) text file (UTF-8 encoded) with python code inside it. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Package changed: pluma (Ubuntu) = gedit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1457035 Title: gedit scrolling bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1457035/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453549] Re: Cannot publish to Facebook
I'm back with more information. The shotwell code is correct, as far as I can tell. The reason why it's failing is because the access token it gets only carries the permissions to see the public profile, and not the permissions to publich photos or videos. Why this happens, I'm not sure. My guess is that the Shotwell application in not properly registered in the Facebook servers to comply with the v2.0 API. As far as I know, only Yorba has access to that key, so there isn't much we can do about it. I've tried playing with the authorization URL (note: you should first remove Shotwell from your profile at https://www.facebook.com/settings?tab=applications): https://www.facebook.com//dialog/oauth?client_id=162702932093redirect_uri=https://www.facebook.com/connect/login_success.htmlresponse_type=tokenscope=publish_actions,user_photos,user_videos and it seems that it always ignores the permissions (scope parameter) we request. Incidentally, I discovered a bug in our Online Accounts integration with Shotwell, which causes the application to retry the authentication forever when the access to the application is revoked from the facebook site. The attached branch fixes this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453549 Title: Cannot publish to Facebook To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1448834] Re: mouse battery not shown after upgrade
This was applied upstream a while ago: http://cgit.freedesktop.org/upower/commit/?id=f8104a112eb ** No longer affects: gnome-power-manager (Ubuntu) ** Changed in: upower (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1448834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877440] Re: [iOS 5] Unhandled Lockdown error (-15)
** No longer affects: upower (Ubuntu) ** No longer affects: libgpod (Ubuntu) ** No longer affects: libplist (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/877440 Title: [iOS 5] Unhandled Lockdown error (-15) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/877440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1454852] Re: Crash at boot
what version of Ubuntu do you use? it looks like it could be fixed in vivid with that commit, http://cgit.freedesktop.org/upower/commit/?id=3a5f3e552 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1454852 Title: Crash at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1454852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)
** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1390120 Title: Manually set time and date reverts to Automatically on restart (Ubuntu Phone) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457054] [NEW] journal is broken in unprivileged LXC and nspawn containers
Public bug reported: Test case - - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ - Boot it. You'll get a lot of errors like [FAILED] Failed to start Journal Service. systemd-journald-audit.socket failed to listen on sockets: Operation not permitted [FAILED] Failed to listen on Journal Audit Socket. - The same happens with systemd-nspawn -b. As a result, the journal isn't working at all. With a fixed systemd package, systemd in the container should realize that it cannot listen to the audit socket (as the kernel doesn't allow that -- the audit subsystem isn't fit for namespaces right now), and sudo journalctl should show the journal and systemd-journald.service should be running. ** Affects: systemd (Ubuntu) Importance: Medium Assignee: Martin Pitt (pitti) Status: In Progress ** Affects: systemd (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Wily) Importance: Medium Assignee: Martin Pitt (pitti) Status: In Progress ** Tags: systemd-boot ** Also affects: systemd (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Wily) Status: New = In Progress ** Changed in: systemd (Ubuntu Wily) Importance: Undecided = Medium ** Changed in: systemd (Ubuntu Wily) Assignee: (unassigned) = Martin Pitt (pitti) ** Tags added: systemd-boot -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1457054 Title: journal is broken in unprivileged LXC and nspawn containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1401207] Re: No 'Select-by-word characters' property
** Branch linked: lp:~menesis/ubuntu/vivid/vte2.91/vivid -- 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/1401207 Title: No 'Select-by-word characters' property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1401207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1244158] Re: GNOME: Modifiers Only keyboard layout switch have no effect
*** This bug is a duplicate of bug 1218322 *** https://bugs.launchpad.net/bugs/1218322 Same story here on 14.10 with Gnome 3.14.3 -- 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/1244158 Title: GNOME: Modifiers Only keyboard layout switch have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1244158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457114] [NEW] package libgtk-3-0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/powerpc-linux-gnu/libgt
Public bug reported: upgrading system, got errors ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgtk-3-0 3.10.8-0ubuntu1.4 ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-smp 3.13.9 Uname: Linux 3.13.0-24-powerpc-smp ppc ApportVersion: 2.14.1-0ubuntu3 Architecture: powerpc Date: Wed May 20 17:49:40 2015 DuplicateSignature: package:libgtk-3-0:3.10.8-0ubuntu1:cannot copy extracted data for './usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-05-12 (8 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release powerpc (20140416.2) SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package powerpc trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1457114 Title: package libgtk-3-0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/powerpc-linux- gnu/libgtk-3.so.0.1000.8' to '/usr/lib/powerpc-linux- gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1457114/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1415458] Re: Add support for MMS group chat
** Changed in: messaging-app (Ubuntu) Status: Fix Released = In Progress ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None = ww22-2015 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1415458 Title: Add support for MMS group chat To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453549] Re: Cannot publish to Facebook
See also: https://bugzilla.gnome.org/show_bug.cgi?id=748991 FWIW, I also hit this under Fedora 21 with shotwell-0.20.2-2.fc21.x86_64 ** Bug watch added: GNOME Bug Tracker #748991 https://bugzilla.gnome.org/show_bug.cgi?id=748991 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453549 Title: Cannot publish to Facebook To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457054] Re: journal is broken in unprivileged LXC and nspawn containers
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu- vividid=8db397eef12d6 ** Changed in: systemd (Ubuntu Wily) Status: In Progress = Fix Committed ** Changed in: systemd (Ubuntu Vivid) Status: Confirmed = In Progress ** No longer affects: lxc (Ubuntu Vivid) ** No longer affects: lxc (Ubuntu Wily) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1457054 Title: journal is broken in unprivileged LXC and nspawn containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1457054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457114] Re: package libgtk-3-0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/powerpc-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/powerpc-linux-gnu/libgtk-
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: gtk+3.0 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1457114 Title: package libgtk-3-0 3.10.8-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/powerpc-linux- gnu/libgtk-3.so.0.1000.8' to '/usr/lib/powerpc-linux- gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1457114/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457054] Re: journal is broken in unprivileged LXC and nspawn containers
Fixed upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=417a7fdc418 http://cgit.freedesktop.org/systemd/systemd/commit/?id=01906c76c However, there's one more detail to fix in unprivileged containers: root@v:/# getpcaps $$ Capabilities for `608': = cap_chown,cap_dac_override,cap_dac_read_search,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_linux_immutable,cap_net_bind_service,cap_net_broadcast,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_ipc_owner,cap_sys_rawio,cap_sys_chroot,cap_sys_ptrace,cap_sys_pacct,cap_sys_admin,cap_sys_boot,cap_sys_nice,cap_sys_resource,cap_sys_tty_config,cap_mknod,cap_lease,cap_audit_write,cap_audit_control,cap_setfcap,cap_syslog,cap_wake_alarm,cap_block_suspend,37+ep The cap_audit_* are a lie, the audit subsystem in current kernels isn't namespace aware and thus unprivileged containers can't have these caps. The failed systemd-journald-audit.socket unit there isn't a big deal, but this should be fixed in LXC. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: Test case - - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ - Boot it. You'll get a lot of errors like - [FAILED] Failed to start Journal Service. - systemd-journald-audit.socket failed to listen on sockets: Operation not permitted - [FAILED] Failed to listen on Journal Audit Socket. + [FAILED] Failed to start Journal Service. + systemd-journald-audit.socket failed to listen on sockets: Operation not permitted + [FAILED] Failed to listen on Journal Audit Socket. - The same happens with systemd-nspawn -b. - As a result, the journal isn't working at all. + As a result, the journal isn't working at all, and you have a bunch of + failed journal related units. With a fixed systemd package, systemd in the container should realize that it cannot listen to the audit socket (as the kernel doesn't allow that -- the audit subsystem isn't fit for namespaces right now), and sudo journalctl should show the journal and systemd-journald.service - should be running. + should be running. These systemd fixes are sufficient for nspawn, but + not completely for unprivileged LXC containers -- there the journal will + start working, but systemd-journald-audit.socket will still keep failing + (this is less important) ** Changed in: lxc (Ubuntu Wily) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1457054 Title: journal is broken in unprivileged LXC and nspawn containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1457054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 938751] Re: jpeg images are washed out or colors are skewed
Using Ubuntu 15.04 and this bug is still there. For an image viewer this is pretty serious. Importance low does not really apply here I think. Bug has been around since 2012. Try it with an image with color #283449. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: jpeg images are washed out or colors are skewed To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 25977] Re: places menu should include the trash as a place
Personally, my bottom panel is full of more important things like the workplace-switcher. I don't interact with my trash bin very often, but that makes it all the more frustrating that it's not in any obvious place. The places menu is exactly where it belongs, since it's implemented as a special folder. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/25977 Title: places menu should include the trash as a place To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/25977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1439220] Re: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this
Reopening this. I get the same message with the version of eog installed from the Ubuntu Wily repository (3.16.2-1). ** Changed in: glib2.0 (Ubuntu) Status: Invalid = New -- 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/1439220 Title: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu- settings.gschema.override'; ignoring override for this key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1439220/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1439220] Re: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this
The same error occurs for the file that ubuntu-gnome-default-settings provides: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/20_ubuntu-gnome-default- settings.gschema.override'; ignoring override for this key. I'll mark this as affecting both ubuntu-settings and ubuntu-gnome- default-settings. ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-gnome-default-settings (Ubuntu) Importance: Undecided Status: New ** No longer affects: glib2.0 (Ubuntu) -- 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/1439220 Title: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu- settings.gschema.override'; ignoring override for this key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1439220/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456965] Re: Shouldn't use CSD under Unity
The dialogs seem to work fine under Unity. I don't think it's worth us patching them - if upstream is fine with them the way they are then we should just leave them. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1456965 Title: Shouldn't use CSD under Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1456965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457054] Re: journal is broken in unprivileged LXC and nspawn containers
To be pedantic, it is not a lie - you have that capability against your own user namespace, Ah, so that says you can do it, but it's never actually going to work? I guess that's just another expression of audit not working in namespaces then.. Unfortunately that will be tough coordinate with the (soon-coming) namespaced audit. Ooh, is that coming? Then I guess we shouldn't bother much, it's not an important problem. For the most part unpriv containers work fine now. ** Changed in: lxc (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1457054 Title: journal is broken in unprivileged LXC and nspawn containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1457054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1401207] Re: No 'Select-by-word characters' property
Word char settings have been resurrected in gnome-terminal 3.16 / vte 0.40 I have compiled vte2.91 version 0.40 and colon (:) is no longer a word char, as was set before. -- 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/1401207 Title: No 'Select-by-word characters' property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1401207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
