[Bug 2072318] [NEW] xdg_desktop_portal_gtk crashing while trying to access unreadable region
Public bug reported:
Description:Ubuntu 24.04 LTS
Release:24.04
xdg-desktop-portal-gtk:
Installed: 1.15.1-1build2
Candidate: 1.15.1-1build2
Version table:
*** 1.15.1-1build2 500
500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
expected to happen: no crashes
what happened instead: crashes
updated system with sudo apt-get update and the sudo apt-get upgrade. since
then xdg-desktop-portal-gtk crashes while trying to access unreadable region,
even when restarting. always produces exactly two internal errors to pop up
(seems to be standard for ubuntu). According to stacktrace "No symbol table
info available"
Full crash report is available as attachment
SegvAnalysis:
Segfault happened at: 0x73937e26c313: mov(%r8,%rdx,1),%edx
PC (0x73937e26c313) ok
source "(%r8,%rdx,1)" (0xca30a56fb4f8) not located in a known VMA region
(needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
SourcePackage: xdg-desktop-portal-gtk
Stacktrace:
#0 0x73937e26c313 in ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
No symbol table info available.
#1 0x73937e26cf6e in ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
No symbol table info available.
#2 0x73937e26d5a5 in FcPatternGetString () from
/lib/x86_64-linux-gnu/libfontconfig.so.1
No symbol table info available.
#3 0x73937db2d4b2 in ?? () from /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
No symbol table info available.
#4 0x73937db2d70f in ?? () from /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
No symbol table info available.
#5 0x73937db30ca9 in pango_fc_font_map_cache_clear () from
/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
No symbol table info available.
#6 0x73937e6643c8 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
No symbol table info available.
#7 0x73937eba12fa in g_closure_invoke () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#8 0x73937ebd0a50 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#9 0x73937ebc1591 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#10 0x73937ebc17c1 in g_signal_emit_valist () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#11 0x73937ebc1883 in g_signal_emit () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#12 0x73937ebad2e4 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#13 0x73937ebb08b3 in g_object_notify_by_pspec () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#14 0x73937e305407 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
No symbol table info available.
#15 0x73937e35ec6e in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
No symbol table info available.
#16 0x73937ee1c5b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#17 0x73937ee7b717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#18 0x73937ee1cf77 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#19 0x5699478affcd in ?? ()
No symbol table info available.
#20 0x73937e0621ca in __libc_start_call_main
(main=main@entry=0x5699478afe30, argc=argc@entry=1,
argv=argv@entry=0x7fff964c7048) at ../sysdeps/nptl/libc_start_call_main.h:58
self =
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140735714979912,
-3263321772113277836, 1, 0, 95216330470224, 127077327396864,
-3263321772127957900, -3859713833729667980}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x1, 0x7fff964c7040}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 1}}}
not_first_call =
#21 0x73937e06228b in __libc_start_main_impl (main=0x5699478afe30, argc=1,
argv=0x7fff964c7048, init=, fini=,
rtld_fini=, stack_end=0x7fff964c7038) at ../csu/libc-start.c:360
No locals.
#22 0x5699478b00f5 in ?? ()
No symbol table info available.
StacktraceAddressSignature:
[Bug 2064192] Re: Unable to resize windows
*** This bug is a duplicate of bug 2064177 *** https://bugs.launchpad.net/bugs/2064177 Same here, as with others on Electron based apps such as VS Code. -- 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/2064192 Title: Unable to resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2064192] Re: Unable to resize windows
*** This bug is a duplicate of bug 2064177 *** https://bugs.launchpad.net/bugs/2064177 Just fixed mine by turning off "Auto Login" -- 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/2064192 Title: Unable to resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()
Any workaround for this? -- 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() 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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
New install of ubuntu 24.04, causes this issue -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()
Issue present on installed today 24.04, during initial boot -- 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() 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@u-jjohansen: ``` $ sudo dmesg | grep DENIED [ 20.729222] audit: type=1400 audit(1714359674.872:42): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/usr/local/share/" pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 20.743227] audit: type=1400 audit(1714359674.886:43): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 20.743368] audit: type=1400 audit(1714359674.886:44): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 20.743817] audit: type=1400 audit(1714359674.886:45): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 20.743821] audit: type=1400 audit(1714359674.886:46): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 496.181770] audit: type=1400 audit(1714360150.324:49): apparmor="DENIED" operation="change_onexec" class="file" info="label not found" error=-2 profile="unconfined" name="ubuntu_pro_apt_news" pid=2609 comm="(python3)" [ 526.667987] audit: type=1400 audit(1714360181.273:50): apparmor="DENIED" operation="change_onexec" class="file" info="label not found" error=-2 profile="unconfined" name="ubuntu_pro_apt_news" pid=2767 comm="(python3)" [ 554.736942] audit: type=1400 audit(1714360209.342:51): apparmor="DENIED" operation="change_onexec" class="file" info="label not found" error=-2 profile="unconfined" name="ubuntu_pro_apt_news" pid=3216 comm="(python3)" [ 2204.153512] audit: type=1400 audit(1714361858.768:60): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8056 comm="snap-confine" capability=12 capname="net_admin" [ 2204.153520] audit: type=1400 audit(1714361858.768:61): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8056 comm="snap-confine" capability=38 capname="perfmon" [ 2205.965365] audit: type=1107 audit(1714361860.578:62): pid=1389 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/login1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.2" pid=8056 label="snap.firefox.firefox" peer_pid=1382 peer_label="unconfined" [ 2206.032369] audit: type=1107 audit(1714361860.647:63): pid=1389 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.83" pid=8056 label="snap.firefox.firefox" peer_pid=8746 peer_label="unconfined" [ 2206.032740] audit: type=1107 audit(1714361860.647:64): pid=1389 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.83" pid=8056 label="snap.firefox.firefox" peer_pid=8746 peer_label="unconfined" [ 2206.331239] audit: type=1400 audit(1714361860.946:65): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini" pid=8056 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 2990.682061] audit: type=1400 audit(1714362645.300:66): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini" pid=12989 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 2991.168924] audit: type=1107 audit(1714362645.787:67): pid=1389 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/login1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.2" pid=12989 label="snap.firefox.firefox" peer_pid=1382 peer_label="unconfined" [ 2991.217994] audit: type=1107 audit(1714362645.836:68): pid=1389 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.107" pid=12989 label="snap.firefox.firefox" peer_pid=13639 peer_label="unconfined" [ 2991.218729] audit: type=1107 audit(1714362645.837:69): pid=1389 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1"
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@u-jjohansen: Also, I'm having this Thunderbird problem going on simultaneously -- https://forum.snapcraft.io/t/unexplained-thunderbird-already-running- but-is-not-responding-message/39990 -- which might be related to the issues from my Chrome comments? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@u-jjohansen: Yes, live environment only. Sorry, I thought I'd included that in my first comment but now I see that I neglected to do so. I added an EDIT: to my first comment to make it clear. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@jjohansen: ``` $ sudo aa-status apparmor module is loaded. 56 profiles are loaded. 54 profiles are in enforce mode. /snap/snapd/21465/usr/lib/snapd/snap-confine /snap/snapd/21465/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper libreoffice-senddocists=!/rofs/etc/apparmor.d). libreoffice-soffice//gpg libreoffice-xpdfimport rsyslogd snap-update-ns.chromium snap-update-ns.cups snap-update-ns.firefox snap-update-ns.firmware-updater snap-update-ns.thunderbird snap.chromium.chromedriver snap.chromium.chromium snap.chromium.hook.configure snap.cups.accept snap.cups.cancel snap.cups.cups-browsed snap.cups.cupsaccept snap.cups.cupsctl snap.cups.cupsd snap.cups.cupsdisable snap.cups.cupsenable snap.cups.cupsfilter snap.cups.cupsreject snap.cups.cupstestppd snap.cups.driverless snap.cups.gs snap.cups.ippeveprinter snap.cups.ippfind snap.cups.ipptool snap.cups.lp snap.cups.lpadmin snap.cups.lpc snap.cups.lpinfo snap.cups.lpoptions snap.cups.lpq snap.cups.lpr snap.cups.lprm snap.cups.lpstat snap.cups.reject snap.firefox.firefox snap.firefox.geckodriver snap.firefox.hook.configure snap.firefox.hook.connect-plug-host-hunspell snap.firefox.hook.disconnect-plug-host-hunspell snap.firefox.hook.post-refresh snap.firmware-updater.firmware-notifier snap.firmware-updater.firmware-updater snap.firmware-updater.firmware-updater-app snap.firmware-updater.hook.configure snap.thunderbird.hook.configure snap.thunderbird.thunderbird 2 profiles are in complain mode. libreoffice-oosplash libreoffice-soffice 0 profiles are in prompt mode. 0 profiles are in kill mode. 0 profiles are in unconfined mode. 31 processes have profiles defined. 31 processes are in enforce mode. /usr/sbin/rsyslogd (1472) rsyslogd /snap/chromium/2828/usr/lib/chromium-browser/chrome (77339) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome_crashpad_handler (77395) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome_crashpad_handler (77397) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (77401) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (77402) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (77404) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (77433) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (77441) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (77443) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (78308) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (78968) snap.chromium.chromium /snap/chromium/2828/usr/lib/chromium-browser/chrome (79729) snap.chromium.chromium /usr/bin/dash (18605) snap.cups.cups-browsed /usr/bin/dash (18912) snap.cups.cups-browsed /usr/bin/sleep (92417) snap.cups.cups-browsed /usr/bin/dash (18607) snap.cups.cupsd /snap/cups/1044/sbin/cupsd (18745) snap.cups.cupsd /snap/firefox/4173/usr/lib/firefox/firefox (50912) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (51554) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (51573) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (52145) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (52713) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (52829) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (57517) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (59890) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (84921) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (85070) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (87511) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (93200) snap.firefox.firefox /snap/firefox/4173/usr/lib/firefox/firefox (93235) snap.firefox.firefox 0 processes are in complain mode. 0 processes are in prompt mode. 0 processes are in kill mode. 0 processes are unconfined but have a profile defined. 0 processes are in mixed mode. ``` ``` $ sudo systemctl status apparmor Warning: The unit file, source configuration file or drop-ins of apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload units. ○ apparmor.service - Load AppArmor profiles Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Sun 2024-04-28 20:01:04 PDT; 1 day 12h ago Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Apr 28 20:01:02 lubuntu
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I seem to have the same apparmor problem with Chrome under Lubuntu
24.04. From "$ journalctl | grep apparmor | grep chrome" I got
info="Userns create restricted - failed to find unprivileged_userns
profile" (among other things). And it's been reproduced by another as
the following relates.
Can anyone help? Much more detail below. And you can email me:
d...@riseup.net.
Prior Lubuntu versions, I wget'd the latest Chrome deb from Google and
installed it via sudo dpkg -i. Usually it worked quite well. Now with
Lubuntu 24.04, I downloaded the latest Chrome deb the same way on Apr.
28, 2024, but Chrome's not working.
If I run /usr/bin/google-chrome or /usr/bin/google-chrome-stable:
```
$ google-chrome
[55151:55151:0428/224255.271437:FATAL:credentials.cc(127)] Check failed: . :
Permission denied (13)
Trace/breakpoint trap (core dumped)
```
or
```
$ google-chrome-stable
[55166:55166:0428/224300.689874:FATAL:credentials.cc(127)] Check failed: . :
Permission denied (13)
Trace/breakpoint trap (core dumped)
```
Meanwhile, $ sudo netstat -antvp shows active connections to multiple
IPs associated with Google, presumably because I tried multiple times to
get Chrome to launch.
Then,
```
$ ls /etc/apparmor.d
1password firefox lxc-stop rootlesskit
scide usr.bin.redshift
Discord flatpak lxc-unshare rpm
signal-desktop usr.bin.tcpdump
MongoDB_Compass force-complain lxc-usernsexec rssguard
slack usr.lib.libreoffice.program.oosplash
QtWebEngineProcess geary mmdebstrap rsyslog.d
slirp4netnsusr.lib.libreoffice.program.senddoc
abi github-desktop msedge runc
steam usr.lib.libreoffice.program.soffice.bin
abstractionsgoldendict nautilus sbuild
stress-ng usr.lib.libreoffice.program.xpdfimport
brave ipa_verify notepadqqsbuild-abort
surfshark usr.lib.snapd.snap-confine.real
buildah kchmviewer nvidia_modprobe sbuild-adduser
systemd-coredump usr.sbin.cups-browsed
busybox keybase obsidian sbuild-apt
thunderbirdusr.sbin.cupsd
cam lc-compliance opam sbuild-checkpackages
toybox usr.sbin.rsyslogd
ch-checkns libcamerify operasbuild-clean
trinityuwsgi-core
ch-run linux-sandbox pageedit sbuild-createchroot
tunables vdens
chrome local plasmashell sbuild-destroychroot tup
virtiofsd
codeloupe podman sbuild-distupgrade
tuxedo-control-center vivaldi-bin
crunlsb_release polypane sbuild-hold
ubuntu_pro_apt_newsvpnns
devhelp lxc-attach privacybrowser sbuild-shell
unix-chkpwdwpcom
element-desktop lxc-create qcam sbuild-unhold
unprivileged_userns
epiphanylxc-destroy qmapshacksbuild-update
userbindmount
evolution lxc-execute qutebrowser sbuild-upgrade
usr.bin.man
```
and
```
$ cat /etc/apparmor.d/chrome
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"
abi ,
include
profile chrome /opt/google/chrome/chrome flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
```
This didn't work either:
```
$ /opt/google/chrome/chrome
[0429/105700.793962:WARNING:chrome_main_linux.cc(80)] Read channel stable from
/opt/google/chrome/CHROME_VERSION_EXTRA
[66808:66808:0429/105700.802212:FATAL:credentials.cc(127)] Check failed: . :
Permission denied (13)
Trace/breakpoint trap (core dumped)
```
Note that I also ran this:
```
$ journalctl | grep apparmor | grep chrome
Apr 28 21:22:42 lubuntu kernel: audit: type=1400 audit(1714364562.824:140):
apparmor="STATUS" operation="profile_replace" profile="unconfined"
name="snap.chromium.chromedriver" pid=19182 comm="apparmor_parser"
Apr 28 22:04:11 lubuntu kernel: audit: type=1400 audit(1714367051.521:200):
apparmor="DENIED" operation="userns_create" class="namespace" info="Userns
create restricted - failed to find unprivileged_userns profile" error=-13
profile="unconfined" pid=46114 comm="chrome" requested="userns_create"
denied="userns_create" target="unprivileged_userns"
```
Someone else reproduced this, following these steps:
```
1. figured out what version of apparmor contained the fix
2. booted the live image
3. checked that the version of apparmor on the live image was greater than
or equal to the version with the fix
4.
[Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore
Thanks for the reply Nathan. Right, so I am targeting all the supported Ubuntu series now. You are right, it should go to the development release first, before SRUing the changes. I asked because it was not clear to me what series are affected. ** Also affects: xdg-desktop-portal-gtk (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gtk (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gtk (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gtk (Ubuntu Mantic) Importance: Undecided Assignee: Nathan Teodosio (nteodosio) Status: Confirmed -- 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/2039187 Title: Thunderbird doesn't accept URI attachments anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
I no longer see the window grouping issue with Slack snap 4.34.121 on Ubuntu 22.04.3. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
This is in the general sponsorship queue, do you need help to get those uploads sponsored? Or is there someone with upload rights working with you on this? In case you already have someone to sponsor the uploads, please, unsubscribe ~ubuntu-sponsors. After a quick look at the latest debdiff proposed by Matthew, I would suggest to use version 3.3.0-1ubuntu0.1 in Jammy. Right now, we have version 3.3.0-1 in the release pocket, and using version 3.3.0-1ubuntu1 might make some users think that this delta was introduced during the development cycle, and using 3.3.0-1ubuntu0.1 makes more explicit the fact that this was introduced after the release via a SRU. This is just my 2 cents, what was proposed would work out well, it is more a semantic thing that I like to follow when adding a delta via SRU to a package that used to be a sync from Debian. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2017452] [NEW] On run, nautilus opens two windows instead of one
Public bug reported: Narrative: I boot into a live Lubuntu operating system -- either 22.10 or 23.04; bug is the same in both -- and open up the terminal where I run 'sudo apt update && sudo apt install nautilus' Next I use the "Superkey + R" keyboard shortcut to open up the dialog to run a program. I run 'nautilus' and two windows open, both for the Home directory. The two windows are identical except they are visually separated from one another slightly on the screen. Expected behavior is to open just one window to my home folder. Currently I'm running Lubuntu 23.04 but same bug happens in Lubuntu 22.10 $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 Source package is presumably 'nautilus' $ apt-cache policy nautilus nautilus: Installed: 1:44.0-1ubuntu2 Candidate: 1:44.0-1ubuntu2 Version table: *** 1:44.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I expected running nautilus to open up one window to my Home directory but instead it opens two. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: LXQt Date: Sun Apr 23 21:57:33 2023 GsettingsChanges: LiveMediaBuild: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar nautilus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2017452 Title: On run, nautilus opens two windows instead of one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2017452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923033] Re: Archive manager drag to extract doesn't work on Gnome with Wayland
This bug also happens to me on 22.04 using Wayland. There are some visual elements that tell the user the file is going to get drag extracted (if you hover the drag over a folder it reacts properly) but no extraction is made -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1923033 Title: Archive manager drag to extract doesn't work on Gnome with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1923033/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04
*** This bug is a duplicate of bug 1969243 *** https://bugs.launchpad.net/bugs/1969243 This also happens to me on my AMD laptop, this is why we use backups! Can't live without the gestures. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969245] [NEW] scroll on dock shows workspaces OSD with missing information
Public bug reported: Description: When I scroll on the dock to change workspaces, it displays the new OSD for switching a workspace, but the white circles that display the current workspace are shown on a dark gray and the OSD's animation is missing. What should happen: The OSD should display the correct animation you would see if you type Super/Win + Alt + Left/Right Arrow Or no OSD at all. Replicate it: Scroll on dock. Hardware info: Asus Vivobook 14 Ryzen 5 3500U & Radeon Graphics. Ubuntu 22.04 Beta (15/04/2022) Package version (output of apt-cache policy): apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Instalados: 72~ubuntu4 Candidato: 72~ubuntu5 Tabla de versión: 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages *** 72~ubuntu4 100 100 /var/lib/dpkg/status ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: 22.04 bug jammy ui ** Tags added: 22.04 bug jammy ui -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1969245 Title: scroll on dock shows workspaces OSD with missing information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969244] [NEW] ubuntu dock's right click menu switches position when the dock is hidden
Public bug reported: Description: When ubuntu-dock is set to autohide and in hidden state (happens on panel and dock mode) When you go to right-click an icon to access its menu, the dock hides again and the menu stays open but when you click it the menu updates its position to be closer to the dock, leading to miss clicks and a worse user experience. What should happen: The dock should stay visible while you interact with the menu. Replicate it: Set your dock to autohide and then, trigger the autohide (like maximizing a window), reach for one of the icons and right-click it. Hardware info: Asus Vivobook 14 Ryzen 5 3500U & Radeon Graphics. Ubuntu 22.04 Beta (15/04/2022) Package version (output of apt-cache policy): apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Instalados: 72~ubuntu4 Candidato: 72~ubuntu5 Tabla de versión: 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages *** 72~ubuntu4 100 100 /var/lib/dpkg/status ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: 22.04 bug gnome-shell-extension-ubuntu-dock jammy ui ** Tags added: ui ** Tags added: jammy ** Tags added: 22.04 bug gnome-shell-extension-ubuntu-dock -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1969244 Title: ubuntu dock's right click menu switches position when the dock is hidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886672] Re: Second screen is not always made to awaken when using multiple displays. Desktop is multiple display, but only laptop screen is on while second screen sometimes remains off
hello, I need help with the same error. In my case use a laptop and a extra monitor. When lock the system, the screen of the laptop is freezes. I am running the 3.36.8 gnome version con ubuntu 20.4 Focal. Is a clean installation. in the path /.local/share/gnome-shell only have this application_state gnome-overrides-migrated notifications -- 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/1886672 Title: Second screen is not always made to awaken when using multiple displays. Desktop is multiple display, but only laptop screen is on while second screen sometimes remains off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
*** This bug is a duplicate of bug 184 *** https://bugs.launchpad.net/bugs/184 hello, I need help with the same error. In my case use a laptop and a extra monitor. When lock the system, the screen of the laptop is freezes. I am running the 3.36.8 gnome version con ubuntu 20.4 Focal. Is a clean installation. in the path /.local/share/gnome-shell only have this application_state gnome-overrides-migrated notifications thanks -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)
I'm here to say that I'm having the same issue. Until this evening, I was using Debian 10 with KDE, but I installed Ubuntu 20.04 a few hours ago. I use a laptop with a external keyboard connected on it and my laptop have a numeric keyboard and my external keyboard don't, so I always use the laptop keyboard to insert numbers. However, each time I swap the keyboard, my computer frozen. Also, I have a mouse with several buttons and two of them are configured as "PgUp" and "PgDn" because I find it more practical over there. However, unfortunately, I can't use it properly because the computer crashes every time I press a button. However, I think it's worth mentioning that mouse buttons that belong to the mouse (like click and scroll) don't have this problem. In short, if I switch keyboards, whether it's laptop, external or mouse buttons, my computer freezes. -- 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/108 Title: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Updated to the 460 drivers and it works with modeset=1. With modeset=1 and 450, it wasn't working. I have a Quadro K2000 and a 2080 Super dual gpu, single monitor setup. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
@seb128, yes. It is still in issue on 20.04 (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/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
Removing the snap version and installing the deb version fixed the issue for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
Hello, I have this problem on my Ubuntu VMs (since 19.04). However, my Debian 10 VMs are not affected. I hope this bug will be fixed before the LTS. This graphics bug makes my VMs unusable. Thank you. -- 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/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)
You're a hero - thank you! $ sudo apt-get install libsane1/bionic libsane-common/bionic sane-utils/bionic Reading package lists... Done Building dependency tree Reading state information... Done Selected version '1.0.27-1~experimental3ubuntu2' (Ubuntu:18.04/bionic [amd64]) for 'libsane1' Selected version '1.0.27-1~experimental3ubuntu2' (Ubuntu:18.04/bionic [all]) for 'libsane-common' Selected version '1.0.27-1~experimental3ubuntu2' (Ubuntu:18.04/bionic [amd64]) for 'sane-utils' The following packages were automatically installed and are no longer required: linux-headers-4.15.0-45 linux-headers-4.15.0-45-generic linux-image-4.15.0-45-generic linux-modules-4.15.0-45-generic linux-modules-extra-4.15.0-45-generic Use 'sudo apt autoremove' to remove them. Suggested packages: hplip unpaper The following NEW packages will be installed libsane1 sane-utils The following packages will be DOWNGRADED: libsane-common 0 to upgrade, 2 to newly install, 1 to downgrade, 0 to remove and 0 not to upgrade. Need to get 2,547 kB of archives. After this operation, 7,216 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libsane-common all 1.0.27-1~experimental3ubuntu2 [274 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libsane1 amd64 1.0.27-1~experimental3ubuntu2 [2,089 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 sane-utils amd64 1.0.27-1~experimental3ubuntu2 [185 kB] Fetched 2,547 kB in 1s (2,937 kB/s) Preconfiguring packages ... dpkg: warning: downgrading libsane-common from 1.0.27+git20180317-xenial0 to 1.0.27-1~experimental3ubuntu2 (Reading database ... 242195 files and directories currently installed.) Preparing to unpack .../libsane-common_1.0.27-1~experimental3ubuntu2_all.deb ... Unpacking libsane-common (1.0.27-1~experimental3ubuntu2) over (1.0.27+git20180317-xenial0) ... Selecting previously unselected package libsane1:amd64. Preparing to unpack .../libsane1_1.0.27-1~experimental3ubuntu2_amd64.deb ... Unpacking libsane1:amd64 (1.0.27-1~experimental3ubuntu2) ... Selecting previously unselected package sane-utils. Preparing to unpack .../sane-utils_1.0.27-1~experimental3ubuntu2_amd64.deb ... Unpacking sane-utils (1.0.27-1~experimental3ubuntu2) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Setting up libsane-common (1.0.27-1~experimental3ubuntu2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for udev (237-3ubuntu10.15) ... Processing triggers for systemd (237-3ubuntu10.15) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Setting up libsane1:amd64 (1.0.27-1~experimental3ubuntu2) ... Setting up sane-utils (1.0.27-1~experimental3ubuntu2) ... Adding user saned to group scanner Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10.15) ... Processing triggers for ureadahead (0.100.0-20) ... $ Then: $ sudo apt install gnome-control-center Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: colord libcolord-gtk1 libnss-myhostname Suggested packages: colord-sensor-argyll realmd rygel | rygel-tracker The following NEW packages will be installed colord gnome-control-center libcolord-gtk1 libnss-myhostname 0 to upgrade, 4 to newly install, 0 to remove and 0 not to upgrade. Need to get 1,874 kB of archives. After this operation, 6,031 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 colord amd64 1.3.3-2build1 [196 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libcolord-gtk1 amd64 0.1.26-2 [17.1 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 gnome-control-center amd64 1:3.28.2-0ubuntu0.18.04.2 [1,627 kB] Get:4 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-myhostname amd64 237-3ubuntu10.15 [34.4 kB] Fetched 1,874 kB in 1s (2,827 kB/s) Selecting previously unselected package colord. (Reading database ... 206764 files and directories currently installed.) Preparing to unpack .../colord_1.3.3-2build1_amd64.deb ... Unpacking colord (1.3.3-2build1) ... Selecting previously unselected package libcolord-gtk1:amd64. Preparing to unpack .../libcolord-gtk1_0.1.26-2_amd64.deb ... Unpacking libcolord-gtk1:amd64 (0.1.26-2) ... Selecting previously unselected package gnome-control-center. Preparing to unpack .../gnome-control-center_1%3a3.28.2-0ubuntu0.18.04.2_amd64.deb ... Unpacking gnome-control-center (1:3.28.2-0ubuntu0.18.04.2) ... Selecting previously unselected package libnss-myhostname:amd64. Preparing to unpack .../libnss-myhostname_237-3ubuntu10.15_amd64.deb ... Unpacking libnss-myhostname:amd64 (237-3ubuntu10.15) ... Setting up libcolord-gtk1:amd64 (0.1.26-2) ... Processing triggers for
[Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)
Thanks. Yes, I had installed a ppa for simple-scan a long time ago to fix a scanner issue but I thought I'd gotten rid of it. I have also just deleted all the ppas to do with that under /etc/apt/sources.list.d. But I still can't get gnome-control-center to run or be installed: The following packages have unmet dependencies. gnome-control-center : Depends: colord (>= 0.1.30) E: Unable to correct problems, you have held broken packages. Do you have any idea how I can fix this please? I'm at a loss here. -- 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/1821809 Title: gnome-control-center won't install: Depends: colord (>= 0.1.30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)
Also, shouldn't the user at least see an error message if you click on the Settings icon but nothing appears to happen? -- 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/1821809 Title: gnome-control-center won't install: Depends: colord (>= 0.1.30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)
I don't think this is exactly the same as https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1762256 because when I try installing the tree of dependencies I get slightly different errors... $ sudo apt install colord Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. colord : Depends: libsane1 (>= 1.0.24) but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo apt install libsane1 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libsane1 : Depends: libsane-common (= 1.0.27-1~experimental3ubuntu2) but 1.0.27+git20180317-xenial0 is to be installed Recommends: sane-utils (>= 1.0.27-1~experimental3ubuntu2) E: Unable to correct problems, you have held broken packages. -- 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/1821809 Title: gnome-control-center won't install: Depends: colord (>= 0.1.30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821809] [NEW] gnome-control-center won't install: Depends: colord (>= 0.1.30)
Public bug reported: This bug looks similar to https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/1762256. I noticed Settings has gone missing from my ubuntu 18.04. When I click on the spanner icon under the power icon in the top right nothing appears to happen. Attempting to install it fails with: $ sudo apt install gnome-control-center [sudo] password for lucas: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. gnome-control-center : Depends: colord (>= 0.1.30) E: Unable to correct problems, you have held broken packages. This may have come about as a side-effect of trying to install simple- scan. I raised a question about that at https://askubuntu.com/q/1108407/103266 but it never got fixed. I couldn't resolve the error "Unable to correct problems, you have held broken packages". Any suggestions welcome, please. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center (not installed) ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 21:15:46 2019 InstallationDate: Installed on 2017-09-03 (569 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1821809 Title: gnome-control-center won't install: Depends: colord (>= 0.1.30) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog
Same problem here. I'm using Ubuntu 18.10 LiveCD and from time to time my Ubuntu just freezes and when it happens my pendrive LED blinks like crazy. It's hard to recover from it, but yesterday I did. The log it at the post below. Here's my post about it: https://unix.stackexchange.com/questions/483898 /my-shell-script-to-periodically-free-some-memory-up-with-ubuntu-18-10 -livecd-wit#_=_ -- 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/1588009 Title: "libinput bug: timer offset negative" keeps coming up in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1588009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753070] Re: Cannot restore default alert sound (Ubuntu bell)
Actually, I forgot to mention one thing that I've noticed: When I first switched the alert sound it was to 'drip'. Since then if I try to set default again, it'll set the drip sound. But if I set another like bark or glass or whatever, it'll play the default sound + the selected one, and if the selected is the default, it plays the default sound + the drip. -- 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/1753070 Title: Cannot restore default alert sound (Ubuntu bell) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753070] Re: Cannot restore default alert sound (Ubuntu bell)
Having the same issue here. .-/+oooo+/-. lucas@bionic `:+ss+:` -+ssyy+- OS: Ubuntu 18.04.1 LTS x86_64 .ossdMMMNyo. Host: Inspiron 7472 /ssshdmmNNmmyNhss/ Kernel: 4.15.0-36-generic +shmydMMMNy+ Uptime: 9 hours, 1 min /hNMMMyhhhmNMMMNh/Packages: 2370 .dMMMNhsshNMMMd. Shell: bash 4.4.19 +hhhyNMMNyyNMMMysss+ Resolution: 1920x1080 ossyNMMMNyMMhsshmmmhssso DE: GNOME 3.28.3 ossyNMMMNyMMhsshmmmhssso WM: GNOME Shell +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: United-Ubuntu-Dark [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Paper [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel i7-8550U (8) @ 4.000GHz .ossdMMMNyo. GPU: Intel Integrated Graphics -+syyy+- GPU: NVIDIA GeForce MX150 `:+ss+:` Memory: 5533MiB / 15937MiB .-/+oooo+/-. lucas@bionic:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 Model name: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz -- 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/1753070 Title: Cannot restore default alert sound (Ubuntu bell) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730149] Re: No option to set a 2nd display as mirrored in Ubuntu 17.10
This turns out not to be a bug, but simply a different (and, it turns out, a much improved) interface for the same purposes. I apologize for the haste (also, I could not find a way to simply rescind it). ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/gnome-control-center/+question/660501 -- 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/1730149 Title: No option to set a 2nd display as mirrored in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730149] [NEW] No option to set a 2nd display as mirrored in Ubuntu 17.10
Public bug reported: Up to rel 17.04, we were able to choose the mode for a second display as either "mirrored" or "extended". With rel 17.10, it always defaults to "extended". ** 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/1730149 Title: No option to set a 2nd display as mirrored in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717272] Re: HiDPI settings reset on logout
Running Ubuntu Budgie 17.10 Beta 1 with Gnome 3.26 and the issue is still there. -- 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/1717272 Title: HiDPI settings reset on logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710319] [NEW] package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: This is in Ubuntu 16.04 LTS on my 64bit Intel Celeron CPU 900 @ 2.2GHz. Not sure what the deal is actually since the update status shows up to date. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evince-common 3.18.2-1ubuntu4.1 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 11 21:31:05 2017 DpkgHistoryLog: Start-Date: 2017-08-11 21:30:43 Requested-By: lucastoshi (1000) Upgrade: update-manager-core:amd64 (1:16.04.7, 1:16.04.8), update-manager:amd64 (1:16.04.7, 1:16.04.8), python3-update-manager:amd64 (1:16.04.7, 1:16.04.8) DuplicateSignature: package:evince-common:3.18.2-1ubuntu4.1 Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... dpkg: error processing package evince-common (--configure): package evince-common is not ready for configuration ErrorMessage: package evince-common is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-12-10 (244 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: evince Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1710319 Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1710319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1659300] [NEW] File Conflict dialogue resizes depending on thumbnail size
Public bug reported: (wishlist) When copying/moving files and there is a name conflict, the dialogue shows some information about the two conflicting files, e.g., name, size, modification time, and an icon (for most file types) or thumbnail (for images or videos). This thumbnail uses the aspect ratio of the images/video, which might be different for different files in the directory. Thus, when there are multiple conflicting files in one copy/move operation, the size of the File Conflict dialogue can change for each conflict. This means that the buttons (e.g., "Cancel", "Skip", "Replace") change their position. Users that resolve conflicts by clicking those buttons then have to constantly move the mouse cursor even if they want to hit e.g. "Skip" for some files in a row. This problem can be solved by fixing the space taken up by the thumbnails, that is, always use the maximum size. Of course, the displayed thumbnail does not need to change (it should still use the correct aspect ratio) - it just needs to be embedded in a background- coloured box of fixed size. Ubuntu 14.04 and 16.04 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1659300 Title: File Conflict dialogue resizes depending on thumbnail size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1659300/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] Re: nautilus does not recognize any server type
Totally my fault! Now I remember, when I first installed 16.04 I removed it as it was chewing up CPU time and battery and it was not clear to me for what it is needed. Now I know what I need it for! Sorry to have burdened you. It is well behaved now though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] Re: nautilus does not recognize any server type
** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+attachment/4728445/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] Re: nautilus does not recognize any server type
yup! that did it, after reboot. you are the best! Strange that this was not installed by default with 16.04. As I said, I did a clean install. At any rate. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] Re: nautilus does not recognize any server type
by the way, thanks for your help on this! just in case, some more data points: sudo gvfs-mount ftp://ftp.debian.net Error mounting location: volume doesn't implement mount nad in case it matters: mount | grep gvfs gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] Re: nautilus does not recognize any server type
just in case sudo gvfs-mount ftp://ftp.debian.net Error mounting location: volume doesn't implement mount in case it matters: mount | grep gvfs gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] Re: nautilus does not recognize any server type
gvfs-mount ftp://ftp.debian.net Error mounting location: Location is not mountable -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] Re: nautilus does not recognize any server type
That is what I was afraid of. dmesg -w does not report anything new when I get the error message. Any other way of reporting syslog that would be helpful? dpkg -l |grep gvfs ii gvfs:amd64 1.28.2-1ubuntu1~16.04.1 amd64userspace virtual filesystem - GIO module ii gvfs-bin1.28.2-1ubuntu1~16.04.1 amd64userspace virtual filesystem - binaries ii gvfs-common 1.28.2-1ubuntu1~16.04.1 all userspace virtual filesystem - common data files ii gvfs-daemons1.28.2-1ubuntu1~16.04.1 amd64userspace virtual filesystem - servers ii gvfs-fuse 1.28.2-1ubuntu1~16.04.1 amd64userspace virtual filesystem - fuse server ii gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1 amd64userspace virtual filesystem - private libraries PS: I did install sshfs after the new install to no avail. Not sure that matters. Also tested if this is a permission issue by running the same as guest user. Same problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617107] [NEW] nautilus does not recognize any server type
Public bug reported: Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus with ssh, sftp, nsf, dav, really anything I can think of gives "This file server type is not recognized." Error message appears as soon as : is entered, e.g. "ssh:". ssh and sftp work just fine from the command line. using nautilus version "Files 3.14.3" ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1617107 Title: nautilus does not recognize any server type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574617] Re: External monitor keeps going blank
I found a way to reproduce it. It happens when the mouse pointer jumps between the two displayport monitors. If I keep moving the mouse between the two monitors it happens each couple of seconds. If I disable the vga monitor. The problem is gone... I have no idea of what is happening but at least know that disabling the vga monitor solves the issue for me. Hopefully someone will find out what is happening. -- 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/1574617 Title: External monitor keeps going blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1574617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574617] Re: External monitor keeps going blank
I have the same problem happening after the upgrade from 15.10 to 16.04. I have a Dell Latitude E7450 plugged into a dock with 3 external monitors (I'm not using the notebook display). After the upgrade by some reason two of the monitors randomly blanks and come back after 1 or 2 seconds. I couldn't find a way to reproduce the problem, it is random. The interesting thing is that 1 of the 3 monitors never does that, the one that is using a VGA cable. The other two are using DisplayPort. -- 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/1574617 Title: External monitor keeps going blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1574617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573846] [NEW] package systemd 225-1ubuntu9.1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: sub-processo script pre-removal instalado re
Public bug reported: up date pacht ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 225-1ubuntu9.1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Apr 22 19:58:46 2016 DpkgTerminalLog: A preparar para desempacotar .../systemd_229-4ubuntu4_amd64.deb ... A desconfigurar udev (225-1ubuntu9.1) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack): sub-processo script pre-removal instalado retornou estado de saída de erro 2 DuplicateSignature: package:systemd:225-1ubuntu9.1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:sub-processo script pre-removal instalado retornou estado de saída de erro 2 ErrorMessage: sub-processo script pre-removal instalado retornou estado de saída de erro 2 InstallationDate: Installed on 2015-05-31 (327 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. QX310/QX410/QX510/SF310/SF410/SF510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-52-generic root=UUID=47ee2f93-17a9-458a-983e-af3535a8a76a ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu2 SourcePackage: systemd Title: package systemd 225-1ubuntu9.1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 2 UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev' UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 05/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 05MX.M008.20110525.SCY dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: QX310/QX410/QX510/SF310/SF410/SF510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 05MX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr05MX.M008.20110525.SCY:bd05/25/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnQX310/QX410/QX510/SF310/SF410/SF510:pvr05MX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnQX310/QX410/QX510/SF310/SF410/SF510:rvr05MX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: QX310/QX410/QX510/SF310/SF410/SF510 dmi.product.version: 05MX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1573846 Title: package systemd 225-1ubuntu9.1 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1573846/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1439955] [NEW] systemd breaks nfs root on vivid
Public bug reported: The initramfs boot script try to mount the root filesystem into /root and look for a /sbin/init file inside that folder. systemd installs /sbin/init as a link to /lib/systemd/systemd, which the initramfs scripts can't find (because the link is an absolute path and the root is mounted under /root). Making that link a relative path fixes the problem (i.e. making it ../lib/systemd/systemd). Please, see /usr/share/initramfs-tools/scripts/nfs for the affected script. I believe this should be fixed before the release of 15.04, as it breaks all nfs root installs. ** Affects: systemd (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/1439955 Title: systemd breaks nfs root on vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1277641] Re: German keyboard layout loses tilde dead key
Hi all, Just to let you know that this also affected me. German (legacy) solved my problem. Cheers, Lucas -- 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/1277641 Title: German keyboard layout loses tilde dead key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1277641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1284369] Re: Rhythmbox won't launch: Rhythmbox-CRITICAL **: Timeout was reached
Whatever the issue was, it no longer exsists. I'm not sure what to mark this as so I'll just mark it as invalid since it seemingly fixed itself. ** Changed in: rhythmbox (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1284369 Title: Rhythmbox won't launch: Rhythmbox-CRITICAL **: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1284369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1284369] [NEW] Rhythmbox won't launch: Rhythmbox-CRITICAL **: Timeout was reached
Public bug reported: I noticed this issue today. I launched Rhythmbox and it opened. I navigated through the appropriate windows to play a song, double clicked on the song, and it didn't start playing. It seemingly stoped operating so I killed it with xkill. At this point now it no longer launches. when I try to launch it from the terminal to see if I can get any information regarding the issue it says after several seconds: Rhythmbox-CRITICAL **: Timeout was reached And exits. I can launch it in the guest account which I believe means it's likely an issue with my exsisting settings. Ubuntu Release: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 uname -a: Linux lucas-Inspiron-5520 3.13.0-12-generic #32-Ubuntu SMP Fri Feb 21 17:45:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Package details rhythmbox: Installed: 3.0.1-1ubuntu10 Candidate: 3.0.1-1ubuntu10 Version table: *** 3.0.1-1ubuntu10 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 24 18:09:28 2014 InstallationDate: Installed on 2013-10-03 (144 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: rhythmbox UpgradeStatus: Upgraded to trusty on 2013-11-26 (90 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug rhythmbox trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1284369 Title: Rhythmbox won't launch: Rhythmbox-CRITICAL **: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1284369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246272] Re: Keyboard layout changing randomly in 13.10 (saucy)
Hello, Sebastian. Any news about this bug? -- 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/1246272 Title: Keyboard layout changing randomly in 13.10 (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1257796] [NEW] Evince has menus with inverted colors
Public bug reported: Menus of Evince have inverted colors. See the attached screenshot. This bug started when I updated Lubuntu from raring to saucy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Wed Dec 4 16:41:33 2013 InstallationDate: Installed on 2013-05-21 (196 days ago) InstallationMedia: Lubuntu 13.04 Raring Ringtail - Release i386 (20130423.1) MarkForUpload: True SourcePackage: evince UpgradeStatus: Upgraded to saucy on 2013-10-18 (46 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug i386 saucy third-party-packages ** Attachment added: Evince menu with inverted colors https://bugs.launchpad.net/bugs/1257796/+attachment/3923199/+files/Screenshot%20from%202013-12-04%2011%3A14%3A04.png -- 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/1257796 Title: Evince has menus with inverted colors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1257796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246272] Re: Keyboard layout changing randomly in 13.10 (saucy)
For me it also happens randomly during the session, even after re- setting keyboard layout many times. Alt-tabbing Skype with with, let's say, Firefox is sure it will happen. -- 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/1246272 Title: Keyboard layout changing randomly in 13.10 (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246272] Re: Keyboard layout changing randomly in 13.10 (saucy)
Hi. Just to confirm I still get the issue changing keybinding. -- 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/1246272 Title: Keyboard layout changing randomly in 13.10 (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246272] Re: Keyboard layout changing randomly in 13.10 (saucy)
Hello Sebastien :) I'm using plain Ubuntu, i.e. Unity. Since it's hard to reproduce the random changes I can't tell you if another keybinding do any better, I'll be trying trying. But I noted after boot the layout is always wrong. -- 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/1246272 Title: Keyboard layout changing randomly in 13.10 (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246272] [NEW] Keyboard layout changing randomly in 13.10 (saucy)
Public bug reported: Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps changing from pt_br to what I think is en_us. It seems random so I don't know what trigger this, but sometimes just alt-tabbing is enough to mess with keyboard layout in one of the windows. I already removed the en_us from my keyboard sources, double checked the use of one source for all windows, and even removed accelerators to switch between layouts but none have worked. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 30 09:12:48 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-20 (163 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug keyboard saucy -- 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/1246272 Title: Keyboard layout changing randomly in 13.10 (saucy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1246272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1242450] Re: No UbuntuOne options in Nautilus
I have the same problem. And it is a serious problem because frequently use Ubuntu One -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1242450 Title: No UbuntuOne options in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1242450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1179100] Re: Crash when Rhythmbox reaches end of a song
Resetting the gsettings for rhythmbox fixed this issue with me. $: gsettings reset-recursively org.gnome.rhythmbox -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1179100 Title: Crash when Rhythmbox reaches end of a song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1179100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 825401] Re: Shotwell cannot publish to Facebook. Server redirect URL contained no session description
Hmm...it sounds like this may be more than just a login/logout issue. Facebook may have labeled the Shotwell Connect application untrusted in connection to your account (especially if you tried to login from a blacklisted IP). The way to correct this issue is to first log out of Facebook in Shotwell. Next, open your browser, navigate to Facebook and open up the Apps panel, then deauthorize the Shotwell Connect application. Finally, open Shotwell and try logging into Facebook again. This should trigger a clean login in which all new account/application bindings are established. -- 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/825401 Title: Shotwell cannot publish to Facebook. Server redirect URL contained no session description To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/825401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 919385] Re: Feature request: zoom out
Hi Rob, I don't think we're interested in implementing this functionality at this time. That said, if you'd like, feel free to open a ticket for it upstream at http://redmine.yorba.org. If you were to submit a patch attached to the ticket, we might consider it! Thanks, Lucas -- 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/919385 Title: Feature request: zoom out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/919385/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 802466] Re: shotwell doesn't work with google's 2-step verification
Hi David, It's now been nearly two years since the this was reported and the proposed solution is '50%' finished. By 50% finished, do you mean that the Picasa Connector uses OAuth but the YouTube Connector, as yet, does not? About this, I can only say that we're working on it. Keep in mind that we at Yorba (the upstream developers of Shotwell) have very limited resources. On the upside, the YouTube OAuth migration may be something that gets done within the next few weeks. We've prioritized the development of this feature because we're not sure how long the legacy ClientLogin API we've been using will still function. Lucas -- 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/802466 Title: shotwell doesn't work with google's 2-step verification To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/802466/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 919385] Re: Feature request: zoom out
Shotwell isn't an image viewer, it's a photo manager with an optional direct-editing mode targeted at touching up single photos quickly. If we were to allow zoom-out in Shotwell, the image would become progressively smaller, no longer filling the whole of the photo viewing canvas. What you'd end up with would be a small photo with a huge amount of blank space around it. What would be the use case for this? Just my two cents. Lucas -- 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/919385 Title: Feature request: zoom out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/919385/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159829] Re: A photo's date can not be set in 1900
This is ticketed upstream here: http://redmine.yorba.org/issues/6669 -- 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/1159829 Title: A photo's date can not be set in 1900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1159829/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159821] Re: 12:00:00 is considered as 12 PM and not 12 AM
In the US interpretation of 24 hour time, midnight is zero hour and the twelfth hour is noon. If they were both 12, how could you differentiate between them without an am/pm suffix, and the whole point of 24 hour time is that there is no am/pm suffix so all ambiguity is resolved. How is calling midnight zero hour a problem? -- 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/1159821 Title: 12:00:00 is considered as 12 PM and not 12 AM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1159821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159883] Re: Wishlist : should be able to delete photo date and time
This is ticketed upstream here: http://redmine.yorba.org/issues/6671 -- 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/1159883 Title: Wishlist : should be able to delete photo date and time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1159883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159866] Re: The find function does not correctly handle special characters
This is ticketed upstream here: http://redmine.yorba.org/issues/6670 -- 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/1159866 Title: The find function does not correctly handle special characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1159866/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1159821] Re: Menus of a time set to 12:00:00 are initialised at 00:00:00
Okay. The problem is much clearer now. Ticketed upstream here: http://redmine.yorba.org/issues/6672. -- 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/1159821 Title: Menus of a time set to 12:00:00 are initialised at 00:00:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1159821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153365] [NEW] evolution crashed with SIGABRT in raise()
Public bug reported: Just happens randomly when using evolution.Using raring ringtail with the latest evolution from the repos. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: evolution 3.6.2-0ubuntu3 Uname: Linux 3.9.0-030900rc1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 11 05:02:29 2013 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2013-03-09 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130222) MarkForUpload: True ProcCmdline: evolution ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: evolution StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evolution crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace raring ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1153365 Title: evolution crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1153365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1130101] Re: gvfsd-mtp crashed with SIGSEGV in g_object_unref()
I get this error when trying to read from files I already wrote to my nexus 4. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1130101 Title: gvfsd-mtp crashed with SIGSEGV in g_object_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1130101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 850840] Re: file-roller crashed with SIGSEGV in g_simple_async_result_complete()
I experienced this issue on Ubuntu 13.04 Daily, while extracting an iso file from a tar.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/850840 Title: file-roller crashed with SIGSEGV in g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/850840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1103747] Re: Totem could not startup.
** Description changed: When Launching Totem, it displays a window saying: Totem could not startup. Some necessary plug-ins are missing. Make sure that the program is correctly installed. So I launched it from the terminal in hopes of recieving a more detailed message for reporting and I recieved the following message: lucas@lucas-Inspiron-5520:~$ totem ** (totem:13625): WARNING **: Element 'cluttersink' is missing, verify your installation (totem:13625): Gtk-WARNING **: A floating object was finalized. This means that someone called g_object_unref() on an object that had only a floating reference; the initial floating reference is not owned by anyone and must be removed with g_object_ref_sink(). Additional Information: Ubuntu Release: Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 uname -a: Linux lucas-Inspiron-5520 3.8.0-1-generic #5-Ubuntu SMP Fri Jan 18 15:23:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Package details totem: - Installed: 3.6.3-0ubuntu2 - Candidate: 3.6.3-0ubuntu2 - Version table: - *** 3.6.3-0ubuntu2 0 - 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.6.3-0ubuntu2 + Candidate: 3.6.3-0ubuntu2 + Version table: + *** 3.6.3-0ubuntu2 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + 100 /var/lib/dpkg/status + + Package details + gstreamer0.10-audiosink: + Installed: (none) + Candidate: (none) + Version table: + gstreamer0.10-qapt: + Installed: (none) + Candidate: 1.9.65-0ubuntu1 + Version table: + 1.9.65-0ubuntu1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + libgstreamer0.10-0-dbg: + Installed: (none) + Candidate: 0.10.36-1ubuntu2 + Version table: + 0.10.36-1ubuntu2 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + gstreamer0.10-plugins-bad: + Installed: 0.10.23-7ubuntu2 + Candidate: 0.10.23-7ubuntu2 + Version table: + *** 0.10.23-7ubuntu2 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + 100 /var/lib/dpkg/status + gstreamer0.10-plugins-bad-multiverse-dbg: + Installed: (none) + Candidate: 0.10.21-1 + Version table: + 0.10.21-1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/multiverse amd64 Packages + gstreamer0.10-plugins-farsight: + Installed: (none) + Candidate: (none) + Version table: + gstreamer0.10-plugins-ugly: + Installed: 0.10.19-2 + Candidate: 0.10.19-2 + Version table: + *** 0.10.19-2 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + 100 /var/lib/dpkg/status + gstreamer0.10-plugins-ugly-dbg: + Installed: (none) + Candidate: 0.10.19-2 + Version table: + 0.10.19-2 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + gstreamer0.10-fluendo-mp3: + Installed: 0.10.15.debian-1ubuntu1 + Candidate: 0.10.15.debian-1ubuntu1 + Version table: + *** 0.10.15.debian-1ubuntu1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + 100 /var/lib/dpkg/status + gstreamer0.10-plugins-good-dbg: + Installed: (none) + Candidate: 0.10.31-3+nmu1ubuntu1 + Version table: + 0.10.31-3+nmu1ubuntu1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + gstreamer0.10-plugins-ugly-doc: + Installed: (none) + Candidate: 0.10.19-2 + Version table: + 0.10.19-2 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + gstreamer0.10-alsa: + Installed: 0.10.36-1.1ubuntu1 + Candidate: 0.10.36-1.1ubuntu1 + Version table: + *** 0.10.36-1.1ubuntu1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + 100 /var/lib/dpkg/status + gstreamer0.10-packagekit: + Installed: (none) + Candidate: 0.7.6-2 + Version table: + 0.7.6-2 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + gstreamer0.10-plugins-good-doc: + Installed: (none) + Candidate: 0.10.31-3+nmu1ubuntu1 + Version table: + 0.10.31-3+nmu1ubuntu1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + gstreamer0.10-ffmpeg-dbg: + Installed: (none) + Candidate: 0.10.13-5 + Version table: + 0.10.13-5 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages + gstreamer0.10-plugins-bad-multiverse: + Installed: (none) + Candidate: 0.10.21-1 + Version table: + 0.10.21-1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/multiverse amd64 Packages + gstreamer0.10-gconf: + Installed: 0.10.31-3+nmu1ubuntu1 + Candidate: 0.10.31-3+nmu1ubuntu1 + Version table: + *** 0.10.31-3+nmu1ubuntu1 0 + 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + 100
[Bug 1103747] [NEW] Totem could not startup.
Public bug reported: When Launching Totem, it displays a window saying: Totem could not startup. Some necessary plug-ins are missing. Make sure that the program is correctly installed. So I launched it from the terminal in hopes of recieving a more detailed message for reporting and I recieved the following message: lucas@lucas-Inspiron-5520:~$ totem ** (totem:13625): WARNING **: Element 'cluttersink' is missing, verify your installation (totem:13625): Gtk-WARNING **: A floating object was finalized. This means that someone called g_object_unref() on an object that had only a floating reference; the initial floating reference is not owned by anyone and must be removed with g_object_ref_sink(). Additional Information: Ubuntu Release: Description:Ubuntu Raring Ringtail (development branch) Release:13.04 uname -a: Linux lucas-Inspiron-5520 3.8.0-1-generic #5-Ubuntu SMP Fri Jan 18 15:23:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Package details totem: Installed: 3.6.3-0ubuntu2 Candidate: 3.6.3-0ubuntu2 Version table: *** 3.6.3-0ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Wed Jan 23 18:03:32 2013 InstallationDate: Installed on 2013-01-16 (7 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-23 (0 days ago) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1103747 Title: Totem could not startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1103747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 448492] Re: Media player device error: LIBMTP_Send_Representative_Sample():...
I have the same problem here with ubuntu 12.04, Rhythmbox 2.96 and a samsung YP-k3, the error message is LIBMTP_Send_Representative_Sample(): could not get object info. , don't know how to get the error log :S, and the files are playable on the device, the only problem is the infinite pop-up error windows.. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/448492 Title: Media player device error: LIBMTP_Send_Representative_Sample():... To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/448492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1091565] Re: slideshow doesn't work with multiple events
Ticketed upstream here: http://redmine.yorba.org/issues/6148 -- 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/1091565 Title: slideshow doesn't work with multiple events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1091565/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1080591] Re: shotwell fails to authenticate with non-primary address
Hi Ketil, Are you using the Ubuntu Online Accounts control panel to set up your Google account or are you configuring it directly in Shotwell? Note that since you're running Quantal, unless you built and installed Shotwell from source, the default build of Shotwell that comes with Quantal has been patched downstream to use the Ubuntu Online Accounts system for Google authentication. Hence, this could be a bug either with Shotwell or with Ubuntu Online Accounts. Lucas -- 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/1080591 Title: shotwell fails to authenticate with non-primary address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1080591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1080140] Re: Move to the rubbish bin always fails
Shotwell's Rubbish Bin or Trash Can (depending on whether you're using US or Commonwealth English) is distinct from the system rubbish bin. This is to say, Shotwell has its own Rubbish Bin. To view the contents of Shotwell's private Rubbish Bin, select Rubbish Bin (or Wastebasket, or Trash, depending on the regional variant of English in use on your system) from the Shotwell sidebar. Once you've switched to viewing the Rubbish Bin Contents, to permanently delete the files in Shotwell's private Rubbish Bin, click Empty Rubbish Bin (or however it is localized on your system) on the Shotwell toolbar. -- 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/1080140 Title: Move to the rubbish bin always fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1080140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1070031] Re: Rhythmbox freezes at startup
*** This bug is a duplicate of bug 1010619 *** https://bugs.launchpad.net/bugs/1010619 Some here, zwaardmeester solution worked for me. Thanks! Just to say, the correct path is ~/local/share/rhythmbox ... there is a little mistake there! :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1070031 Title: Rhythmbox freezes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1070031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1073823] Re: Shotwell does not link movies to events when migrating existing collection
During import from the camera card, shotwell is able to gather information about the video files When Shotwell is able to gather video metadata, have you connected the camera directly to the computer or have you simply mounted the camera's memory card (say, via an internal SD card reader on your computer) without connecting the camera itself? I ask because, when Shotwell talks directly with cameras, communication is mediated via libgphoto2, a standard Linux camera access library. In some cases libgphoto2 is able to gather metadata that Shotwell itself cannot. -- 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/1073823 Title: Shotwell does not link movies to events when migrating existing collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1073823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1073823] Re: Shotwell does not link movies to events when migrating existing collection
Hi melenzb, Reading date and time metadata out of video files to classify them into events is much harder than reading the same information out of photo files. Nevertheless, Shotwell can do this for a number of video formats (see, for example, this ticket [http://redmine.yorba.org/issues/3057] in the Shotwell bug tracking system). What kind of video files (both container format and CODEC) are you seeing that Shotwell can't read metadata from? Lucas ** Changed in: shotwell (Ubuntu) Status: New = Incomplete -- 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/1073823 Title: Shotwell does not link movies to events when migrating existing collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1073823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1050793] Re: does not check response from fb assumes it is html/xml
This issue has been fixed upstream; see upstream bug report #5822 here: http://redmine.yorba.org/issues/5822. Shotwell versions 0.13.1 and later include much more robust guards against malformed response data from web servers. ** Changed in: shotwell (Ubuntu) Status: In Progress = Fix Committed ** Changed in: shotwell (Ubuntu Quantal) Status: In Progress = Fix Committed -- 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/1050793 Title: does not check response from fb assumes it is html/xml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1050793/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1002537] Re: Shotwell Send To Email doesn't attach multiple photos
This has been fixed upstream (see http://redmine.yorba.org/issues/5822). Shotwell versions 0.13.1 and later no longer exhibit this problem. ** Changed in: shotwell (Ubuntu Quantal) Status: In Progress = Fix Committed ** Changed in: shotwell (Ubuntu Raring) Status: In Progress = Fix Committed -- 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/1002537 Title: Shotwell Send To Email doesn't attach multiple photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1002537/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 893326] Re: Shotwell does not delete files it claims to...
@Jan: The upstream ticket is still open. Unfortunately we weren't able to fix this problem in Shotwell 0.13.x. But rest assured: RAW file handling is a top priority for the upcoming Shotwell 0.14. -- 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/893326 Title: Shotwell does not delete files it claims to... To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/893326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065328] Re: Incorrect Picture Pixbuf Displayed
This issue is known upstream and is ticketed here: http://redmine.yorba.org/issues/5986 In the meantime, a workaround is this: whenever you switch your library, wipe out your ~/.cache/shotwell directory. This will cause Shotwell to generate new thumbnails appropriate for the current library. -- 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/1065328 Title: Incorrect Picture Pixbuf Displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1065328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1047859] Re: Upon starting shotwell, gsettings-data-convert crash with signal 5
I've ticketed this upstream here: http://redmine.yorba.org/issues/5983 -- 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/1047859 Title: Upon starting shotwell, gsettings-data-convert crash with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1047859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1060352] Re: German Transalation: Senden An - Senden an...
This bug is known upstream and has been fixed in Shotwell trunk: http://redmine.yorba.org/issues/5931 -- 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/1060352 Title: German Transalation: Senden An - Senden an... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1060352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035067] Re: Shotwell doesn't use 24-hour clock
Hi Benji, Is there any reason why you have a mixed-language environment on your computer? This is to say, your LANG environment variable specifies US English as your system language but you're using German numbers, dates, and times. Much more worryingly, your LC_MESSAGES environment variable is totally out of whack with all of your your other language collation (e.g. LC_xxx) variables. LC_MESSAGES specifies US English but all your other LC_xxx variables specify German. This is likely your problem. Lucas -- 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/1035067 Title: Shotwell doesn't use 24-hour clock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1035067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1034432] Re: Shotwell doesn't show options (Rotate, Enhance etc) when opening Maximised
This is a Unity problem, not a Shotwell one. I've searched in vain to find the related Unity bug. Perhaps Sebastien can chime in here? -- 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/1034432 Title: Shotwell doesn't show options (Rotate, Enhance etc) when opening Maximised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1034432/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1029894] Re: Shotwell drag and drop does not work.
This ticket really should be marked invalid -- and I say this as an upstream Shotwell dev. Shotwell can be run in two modes. One of these modes is library mode, where Shotwell manages a library of photos, allowing tagging, events, etc. However, Shotwell can also be invoked in direct edit mode, where Shotwell is invoked on a single image to allow quick re-touching, etc. In the video, Shotwell is running in direct edit mode. Drag and drop has never been supported in direct edit mode, since the whole point of direct edit mode is to directly edit a single photo. Drag and drop only works in library mode for importing and exporting photos to and from the Shotwell library. So Shotwell is functioning as designed. If drag drop in direct edit mode is a desired feature in Shotwell, that should be opened as a feature request on our upstream bug tracker at http://redmine.yorba.org. -- 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/1029894 Title: Shotwell drag and drop does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1029894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1025598] Re: shotwell doesn't get the new pictures since a few days
We've ticketed this upstream here: http://redmine.yorba.org/issues/5566 -- 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/1025598 Title: shotwell doesn't get the new pictures since a few days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1025598/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 862692] Re: Shotwell keeps saving when adding metatags into modified files
Fix committed upstream. ** Changed in: shotwell (Ubuntu) Status: Confirmed = Fix Committed -- 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/862692 Title: Shotwell keeps saving when adding metatags into modified files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/862692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1025119] Re: Exporting photos fails due to file error
Hi TZ, I'm one of the Shotwell devs. To resolve your problem, I think you should do two things. First, Shotwell 0.11.6 is now nearly a year old. The current version of Shotwell is 0.12.3. So simply upgrading Shotwell may solve your problem. You can learn more about how to upgrade here: http://www.yorba.org/shotwell/install.html. If upgrading doesn't fix your problem, then we'll need some diagnostic information about why these files are not being exported. Shotwell includes a built-in logging facility. To learn how to enable diagnostic logging, see the I found a bug in Shotwell. How can I report it? section of the Shotwell FAQ here: http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ. When Shotwell is run with logging on, it will produce a log file that you can attach to this ticket. Lucas ** Changed in: shotwell (Ubuntu) Status: New = Incomplete -- 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/1025119 Title: Exporting photos fails due to file error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1025119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1016859] Re: shotwell crashes on startup
Hi Roland, We'd like to open an upstream bug for this issue, but in order to do that, we really need both a stack trace at the time of the crash and the Shotwell log file. To learn how to generate these two diagnostic files, see the I found a bug in Shotwell. How can I report it? section of the Shotwell FAQ here: http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ. Lucas -- 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/1016859 Title: shotwell crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1016859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1009678] Re: Shotwell will not successfully start, via command line, or via it's menu item
Hi Les, Shotwell 0.11.6 is an older version of Shotwell. I think your problem can be solved by upgrading to the latest version, 0.12.3. Instructions can be found here: http://www.yorba.org/shotwell/install/ Lucas -- 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/1009678 Title: Shotwell will not successfully start, via command line, or via it's menu item To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1009678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990725] Re: Shotwell will not detect mts moviefiles on memory card
Hi Sebastien, I'm not sure why your MTS videos aren't being enumerated. But they're not, and this bug can't be marked as fix verified until they are. That said, the fix we implemented to correct this bug cannot cause a regression because it only expands the number of directories that Shotwell searches for video files. You can examine the changeset for the fix here: http://redmine.yorba.org/projects/shotwell/repository/revisions/7b0340f9b6c4fda7bab1c9efc00bd22ccac6672a/diff/src/camera/ImportPage.vala and confirm this yourself. Therefore, it is our strong preference that this bug be marked as failed verification without regression so as not to delay the distribution of the 0.12.3 update, particularly because the 0.12.3 update corrects a critical issue that causes data loss (i.e. Shotwell deletes tags at random, lp: #999108) and the fix for this latter, more serious issue has been verified. As another data point on the stability of 0.12.3, we ship Shotwell as a source tarball (see http://yorba.org/shotwell/install/) for users on other distros. Traffic on the mailing list confirms that users are building 0.12.3 from source -- on other distros as well as on Ubuntu -- and we've received no reports of any regression in video detection. Since 0.12.3 was released on May 9 and has been running in the wild for over two weeks now, we'd expect to hear about any regression that might've occurred. Just to re-iterate, from our perspective, the best way to go here is to mark this bug as failed verification without regression. We'll fix this bug in the 0.13 cycle, but we don't think its verification failure should delay the push of the 0.12.3 update. Of course, you guys have your own perspectives and considerations, so you may want to do something different. We'll help in any way we can. Take care, Sebastien! All of us at Yorba look forward to linking up with you guys again at GUADEC this summer! Cheers, Lucas -- 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/990725 Title: Shotwell will not detect mts moviefiles on memory card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/990725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990725] Re: Shotwell will not detect mts moviefiles on memory card
I'm still interested to see the lumix camera case fixed and wanting to provide debug infos We're very interested in fixing this too. We reopened the upstream bug (http://redmine.yorba.org/issues/5160) two days ago. Clinton will be get you a patch with some diagnostic printouts in a few days. Lucas -- 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/990725 Title: Shotwell will not detect mts moviefiles on memory card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/990725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 909254] Re: Shotwell completely freezes upon start
Changed setting from incomplete to confirmed since a user other than the original reporter has both encountered the problem and attached a sample file. Because this involves a soft lockup of Shotwell, we've upped the priority on the upstream bug here: http://redmine.yorba.org/issues/4541 ** 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/909254 Title: Shotwell completely freezes upon start To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/909254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
