Could you please paste how exif prints the date for reference? Using command:
exif --no-fixup the-photo.jpg | grep -i date
(Install exif by "sudo apt-get install exif", if exif is not installed.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
*** This bug is a duplicate of bug 33883 ***
https://bugs.launchpad.net/bugs/33883
** This bug has been marked a duplicate of bug 33883
hidden files not included in directory 'properties'
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
*** This bug is a duplicate of bug 853061 ***
https://bugs.launchpad.net/bugs/853061
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=650284
Importance: Unknown
Status: Unknown
** This bug has been marked a duplicate of bug 853061
New "Open with" in rig
*** This bug is a duplicate of bug 597639 ***
https://bugs.launchpad.net/bugs/597639
** This bug has been marked a duplicate of bug 597639
nautilus crashes on opening folder containing broken symlinks
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
*** This bug is a duplicate of bug 597639 ***
https://bugs.launchpad.net/bugs/597639
According to attachment "List of files in /bin/dir", below symlinks are
invalid.
lrwxrwxrwx 1 root root 15 2011-02-23 18:19 ompi-checkpoint ->
orte-checkpoint
lrwxrwxrwx 1 root root 12
*** This bug is a duplicate of bug 597639 ***
https://bugs.launchpad.net/bugs/597639
The broken symlinks are from openmpi-checkpoint. Bug #797091. Upstream
fix has been included in Oneiric.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
*** This bug is a duplicate of bug 597639 ***
https://bugs.launchpad.net/bugs/597639
Are you sure the mentioned files there are exactly the same as you
previously reported? I mean,
ompi-checkpoint -> orte-checkpoint and orte-checkpoint -> ompi-
checkpoint, forming an invalid endless loop.
I
Close because the exif tag is wrong.
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
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/881655
Title:
Bad date in pictu
The only reference of the "picture_opacity" gconf key is removed by
below commit from Nautilus. Maybe this is not a bug (or feature request)
of Nautilus.
commit 66cd22c908cc73954fad3e261d28ae6a05ea1bc2
Author: Cosimo Cecchi
Date: Sat Oct 9 15:39:14 2010 +0200
background: refactor code into
I am still seeing the crash with Nautilus 3.2.1 on Oneiric.
Minimum steps to reproduce:
$ mkdir /tmp/dbg
$ cd /tmp/dbg
$ ln -s a b
$ ln -s b a
$ nautilus .
Initializing nautilus-gdu extension
Initializing nautilus-dropbox 0.6.8
Segmentation fault
$ apt-cache policy nautilus
nautilus:
Installed:
The bug should have been fixed in upstream according to Nautilus
developers mentioned in anther gnome bug report [1].
1. https://bugzilla.gnome.org/show_bug.cgi?id=607974
** Bug watch added: GNOME Bug Tracker #607974
https://bugzilla.gnome.org/show_bug.cgi?id=607974
--
You received this bug
Could you launch nautilus from gdb, type 'bt' after the crash occurred and
attach the backtrace here?
(Note: needs debug symbols for nautilus installed: sudo apt-get install
nautilus-dbg)
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification b
Do you mean Nautilus crashes by "window closes"?
If yes, could you launch nautilus from gdb, type 'bt' after the crash occurred
and attach the backtrace here?
(Note: needs debug symbols for nautilus installed: sudo apt-get install
nautilus-dbg)
** Changed in: nautilus (Ubuntu)
Status: Ne
*** This bug is a duplicate of bug 879456 ***
https://bugs.launchpad.net/bugs/879456
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #879456, so it is being marked as such. Please look a
I cann't reproduce this with 3.2.1-0ubuntu2 on Oneiric amd64 with Unity
4.24.0-0ubuntu2b1.
Are you running Unity? Which window manager are you using? I'm thinking
this is more like a bug of a "window manager" instead of Nautilus.
--
You received this bug notification because you are a member of
Please submit one bug report for one issue for ease of tracking
progress.
For "bug 2", it is a duplicate of of bug #879456.
--
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/883721
Ti
How about gdb attach to a process?
$ pidof nautilus
8677
$sudo gdb 2>&1 | tee gdb-nautilus.txt
(gdb) attach 8677
(gdb) cont
Continuing.
< reproduce the crash >
(gdb) backtrace full
https://wiki.ubuntu.com/X/Backtracing#Backtrace_with_gdb
--
You received this bug notification because you are a m
Please make sure you only used sudo when starting gdb. Nautilus should
not be started with sudo.
If you don't use sudo, for gdb attach to work, you'll have to disable ptrace
protection. Using this command,
$ echo 0 > /proc/sys/kernel/yama/ptrace_scope
More details, please see:
https://wiki.ubu
Now I reproduced the crash. Attached is tracktrace.
** Attachment added: "backtrace of SIGABORT"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/884059/+attachment/2583289/+files/backtrace-nautilus-884059.txt
** Description changed:
- Nautilus crashes with a middle click on a Desktop
*** This bug is a duplicate of bug 817861 ***
https://bugs.launchpad.net/bugs/817861
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https
*** This bug is a duplicate of bug 817861 ***
https://bugs.launchpad.net/bugs/817861
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #817861, so it is being marked as such. Please look a
*** This bug is a duplicate of bug 879456 ***
https://bugs.launchpad.net/bugs/879456
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #879456, so it is being marked as such. Please look a
Is this still reproducible by you? Could you provide a backtrace by gdb
attaching to the nautilus process?
An example gdb session like following: (you need type in the part after
"$" or "(gdb)" till line ends.)
$ pidof nautilus
8677
$ sudo gdb 2>&1 | tee gdb-nautilus.txt
(gdb) attach 8677
(gdb) c
I am having the same issue.
Found a workaround: changing the "Insert date/time" plugin preference to
something else, and revert back, then insert date/time works as
expected, even with a newly started gedit.
To change the plugin preference:
Menu Edit -> Preference -> plugins tab -> select insert
*** This bug is a duplicate of bug 840765 ***
https://bugs.launchpad.net/bugs/840765
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #840765, so it is being marked as such. Please look a
*** This bug is a duplicate of bug 865115 ***
https://bugs.launchpad.net/bugs/865115
Move to package nautilus-open-terminal based on backtrace:
#0 0x7ffa1a6fa8be in gconf_client_get () from /usr/lib/libgconf-2.so.4
#1 0x7ffa1a6fadb0 in gconf_client_get_bool () from /usr/lib/libgconf
--
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/920356
Title:
gnome-settings-daemon crashed on g_logv
To manage notifications about this bug go to:
https://bugs.launch
Public bug reported:
I only see this once. It happened after the system waked up for a while.
backtrace:
#0 0x7f407866bb3b in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7f407866bd12 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f4079101823 in ?? ()
Public bug reported:
Evince crashed when viewing a PDF and adjusting the window size, (adjust
the zoom level set to "fit page width").
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.1.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic x8
--
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/809436
Title:
evince crashed with SIGSEGV in sse2_composite_add_n___ca()
To manage notifications about this bug go to:
https:/
** Attachment added: "Example PDF triggers the crash"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/809436/+attachment/2205449/+files/auug97.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs
Several other PDF files had crashed evince before. Attached is one of
them.
I haven't found a valid way to reproduce the crash. It happens rather
common sometimes, but rarely otherwise.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
32 matches
Mail list logo
