I think to trigger the bug (using gnome-music) you need a music
collection where it needs to try and look up at least some album
artwork. If you have an empty music library gnome-music will start fine
because the gnutls code is never invoked.
--
You received this bug notification because you are
Submitted upstream:
https://bugs.documentfoundation.org/show_bug.cgi?id=122075
** Bug watch added: Document Foundation Bugzilla #122075
https://bugs.documentfoundation.org/show_bug.cgi?id=122075
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Right - I have managed to force over my libreoffice to using ps (uncheck
the 'PDF as standard print job format' option, click Okay, and let lo
restart).
When in 'PS' mode, you are correct that the bug as I have described does not
manifest. I conclude that it only manifests when in 'PDF' mode.
Hmmm - somewhat curious that your setup is locked into ps and mine is
pdf with no apparent way of switching.
But in step 6-c it is important to click on a file name in the chooser,
and then edit it in the type in field. The bug doesn't manifest if you
just edit the name type in field to the
Okay - your print defaults are to 'print to ps' rather than 'print to
pdf'.
So to recreate the steps you can either:
a) Go to Tools -> Options -> Print -> and enable 'PDF as standard print
job format, then re-run the steps
OR
b) wherever in my steps I say 'pdf' or filename.pdf, change to 'ps'
>I think the bug happens when the dialogue self-flips the type selector
to 'Portable Document Format'.
Yep ... if I manually flip the type selector to 'Portable Document
Format' it loses my desired file name and pseudo-randomly selects a pdf
file from the list of files in the folder.
So there
This screenshot manages to show the problem.
Here I have typed in the 'Name' field 'test_2.pdf' when I already have
that filename in my folder (as well as the dummy sample.pdf). I then
press Enter, expecting to get the confirmation dialogue box asking about
overwriting the file.
The confirmation
Public bug reported:
This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3
installed).
Under certain conditions print to file over-writes an existing pdf file
in the chosen folder which doesn't match the name chosen by the user
(and without any warning or confirmation dialog).
Public bug reported:
gnome-music gives segmentation fault on startup in Cosmic Cuttlefish
release.
gbd on core file gives:
(gdb) bt
#0 0x in ?? ()
#1 0x7f6446dc74d0 in gnutls_aead_cipher_encryptv ()
from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
#2 0x7f6446d94ed7 in
Yep - I'm on Ubuntu 18.04 using gnome-shell/wayland 3.28 and confirm it
is now working okay
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732454
Title:
Reply to message composer window opens
Public bug reported:
In evolution, open a message which opens a 'message reader' window.
In that window press the 'Reply' button - this opens a new 'message
composer' window in which to type the reply
In 17.10 running under gnome-shell, the composer window is opened, but
it also seems that the
Upgraded to evolution 3.22.3 and the bug seems to have fixed itself - so this
report can be closed.
Thankyou
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640862
Title:
evolution crashes when
Apologies for the confusion in my reporting.
I've installed webkit2gtk 2.14.2-0ubuntu1 in yakkety-proposed but still
get the same crash in evolution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is most likely the same as
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1631682
Still getting an X 'BadDamage' error:
(evolution:21365): Gdk-ERROR **: The program 'evolution' received an X Window
System error.
This probably reflects a bug in the program.
Hi Ablenzo
Its highly unorthodox as a method ... but in this case it gets us out of
a hole.
- Use packages.ubuntu.com to find the gstreamer1.0-plugins-ugly package from
the Trusty series
- From that page, 'Downloads' section near the bottom, you can click on 'i386'
or 'amd64' link (depending
Installing version 1.2.2 of gstreamer1.0-plugings-ugly in saucy (by
using the latest package from Trusty archive) fixes the problem on my
system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245097
My (32 bit) system is showing the same behaviour, and totem gives the
following error message each time:
** (totem:7505): CRITICAL **: gst_video_decoder_allocate_output_frame:
assertion 'frame-output_buffer == NULL' failed
A quick trawl on upstream gstreamer lead me to:
I would be very surprised if the Dell BIOS update changed anything.
Actually this bug can now be closed. Good bluetooth work was done in the
kernel, which made it into the 3.10 tree. So Ubuntu 13.10 installations
won't have this bug.
--
You received this bug notification because you are a
I have this problem too, but my totem depends on gstreamer1.0, not 0.10.
Could the problem be upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=688803
apparently fixed, though I don't think the code has trickled into the ubuntu
repos
** Bug watch added: GNOME Bug Tracker #688803
Libreoffice needs proper dataprovider support. As well as 'export pdf'
(which would make my life much easier), operations like
'Insert-Picture-From File' should be logged as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected quantal running-unity
** Description changed:
Linux kernels after 3.2 introduced battery status reporting for devices
such as bluetooth keyboards and mouse.
Unfortunately there is an issue when such input devices are removed:
- a
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519730/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519731/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519732/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519733/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519734/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519735/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519736/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519737/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519738/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519739/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519740/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519741/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519742/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1117608/+attachment/3519743/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Note the truncated device paths for the removal of the input/event
devices, which comes after the removal of the 'hci' device.
The correct order should work from the bottom up of the tree (so hci
device removed last).
** Attachment added: udevadm monitor report
Here is a snippet of kern.log after a resume, with printk added to
hidp_session() and hidp_get_raw_report().
When the connection is taken down, hidp_session() exists its main loop (prints
'out of loop' message).
It then does a hid_destroy_device() ... which invokes sysfs removal of the
input
Vince
Do you know what the actual fix was upstream? As far as I can tell, 3.7
kernels still had this problem (in fact still a problem using 3.8).
The failed battery report is not necessarily a problem per se, but under
certain situations (e.g. resume from suspend) can cause a kernel OOPS
--
This bug is because of kernel upstream bug
https://bugzilla.kernel.org/show_bug.cgi?id=52471
All the info is in that bug report, including 2 patches to fix it.
In short form, the (doomed to fail by timeout) battery status reporting
injects a 5 second delay in keyboard device removal. Due to
Public bug reported:
Linux kernels after 3.2 introduced battery status reporting for devices
such as bluetooth keyboards and mouse.
Unfortunately there is an issue when such input devices are removed:
- a battery status report is requested
- this fails, because the device is being removed
cat /proc/version_signature
Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117608
Title:
bluetooth incorrectly removes input devices
To manage notifications
** Attachment added: lspci log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1117608/+attachment/3517643/+files/lspci.log
** Bug watch added: Linux Kernel Bug Tracker #52471
http://bugzilla.kernel.org/show_bug.cgi?id=52471
--
You received this bug notification because you are a
Upstream bug is https://bugzilla.kernel.org/show_bug.cgi?id=52471
Note two patches proposed there, which if applied together fix the
problem (I have fixed it on my 3.8-rc6 kernel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe this bug is the real root cause of
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1075478
Xorg is not at fault, it is racy code (plus the hideous 5 second
timeout) in the kernel
** Bug watch added: Linux Kernel Bug Tracker #50541
Note also the race conditions in the bluetooth code can also lead to a kernel
OOPS, as reported in
https://bugzilla.kernel.org/show_bug.cgi?id=50541
Removing the 5 second delay avoids that race condition however.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=50541
** Bug watch added: Linux Kernel Bug Tracker #50541
http://bugzilla.kernel.org/show_bug.cgi?id=50541
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tried a 3.7 kernel, and the problem still exists
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053794
Title:
crash on resume. Linux 3.5.0-15-generic
To manage notifications about this bug go
Apparently upstream this is fixed in 3.6.1 maintenance release. Can this
be built and released in Ubuntu main?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055497
Title:
Signature inserted twice
Attached is a cut from syslog on my system: the crash happens when I try
to enter the password from my bluetooth keyboard just after a resume
from suspend.
** Attachment added: crash log from my system
While I would still like to see this fixed, I have found a workaround
(that at least works in 12.10):
- In compizconfig-settings, enable the 'Extra WM Actions' plugin
- in the options for this plugin, enable a bindkey for the 'Toggle
always on top' option (I chose ctrl-F9)
Now you can open the
Echoing #15, the multi-monitor spec has(had) a concept of 'projection
mode', i.e. where the 2nd monitor was known to be used for projection
and thus special conditions would be useful. I have long thought that
one of the special conditions of a 'projection mode' would be to not
have the unity top
Jakob
There is a trade-off between 'locate' and 'tracker'.
locate:
+ will actually find more files than other solutions, including files not in
your home directory (and not owned by you)
- Issue with encrypted home directory (?)
- relies on a daemon which by default runs just once a day
This is surely a bug in gstreamer. Pitivi can't open such videos either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993937
Title:
Totem can't play some FLV videos encoded by H.264 codec
To
Public bug reported:
A multimonitor setup, with an application 'maximised' on one monitor.
- Lock the screen and shut the laptop lid, or suspend the laptop.
- Unlock (bring out of suspend, unlock).
Now see the maximised application is still maximised, but on the other
monitor! In other words
Libreoffice 3.5.3 (recently in the Ubuntu Precise repos) fixes this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/545346
Title:
[upstream] [3.3] Sound is Duplicated and produces echo
To manage
Public bug reported:
When dragging a window from one monitor to another, frequently the mouse
and the dragged window become separated. I would guess this is an affect
of the deliberate 'barrier' between the two monitors.
This is not necessarily a request to remove the barrier, but the mouse
Precise is now shipping tracker 0.14, so this bug is fixed.
** Changed in: tracker (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947392
Title:
apport information
** Tags added: apport-collected compiz-0.9 precise ubuntu
** Description changed:
Have two monitors arranged side by side. Some applications when used
maximised in the right hand monitor, display their menus split across
the two monitors.
Not all applications do
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/974900/+attachment/3028335/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028336/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028337/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028338/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: GdmLog.gz
https://bugs.launchpad.net/bugs/974900/+attachment/3028339/+files/GdmLog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: GdmLog1.gz
https://bugs.launchpad.net/bugs/974900/+attachment/3028340/+files/GdmLog1.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: GdmLog2.gz
https://bugs.launchpad.net/bugs/974900/+attachment/3028341/+files/GdmLog2.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: GraphicsCard.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028342/+files/GraphicsCard.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028343/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028344/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028345/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028346/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028347/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028348/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028349/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028350/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028351/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028352/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: XorgConf.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028353/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
apport information
** Attachment added: XorgLog.gz
https://bugs.launchpad.net/bugs/974900/+attachment/3028354/+files/XorgLog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: XorgLogOld.gz
https://bugs.launchpad.net/bugs/974900/+attachment/3028355/+files/XorgLogOld.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028356/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
apport information
** Attachment added: peripherals.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028357/+files/peripherals.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028358/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
apport information
** Attachment added: xinput.txt
https://bugs.launchpad.net/bugs/974900/+attachment/3028359/+files/xinput.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Menus
** Attachment added: Screenshot showing split menus
https://bugs.launchpad.net/bugs/974900/+attachment/3014295/+files/Screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974900
Title:
Public bug reported:
Have two monitors arranged side by side. Some applications when used
maximised in the right hand monitor, display their menus split across
the two monitors.
Not all applications do this.
gnome-terminal (with panel menus disabled) - is OK
libreoffice - is BAD
I don't know
This patch fixes all the autostart files. Note I've included even the
ones we don't currently care about should that change in the future.
** Patch added: Patch to fix autostart desktop files
Public bug reported:
The xdg autostart .desktop for tracker all have 'OnlyShowIn' statements
which do not include Unity. Some Unity users who install tracker wont
get these services started automatically.
** Affects: tracker (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
See upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=671314 and
discussion starting at http://mail.gnome.org/archives/tracker-
list/2012-March/msg3.html
The net effect is for tracker to not index a file's contents if tracker-extract
process is not running at the
@Raffaele @Mikkel: Someone already has - see
http://hoheinzollern.wordpress.com/2011/11/21/unity-tracker-lens/
Oh for this to be released and integrated!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With reference to comment #42, the issue described in that comment matches the
problem I reported in
https://bugs.launchpad.net/unity/+bug/907464 which is now marked as a duplicate
of this bug.
The two bugs are obviously related, but not necessarily exact
duplicates, at least in my view.
--
Yes - its a corner case that maybe needs to be related to the
http://design.canonical.com/the-toolkit/unity-multi-monitor-interactions
spec, particularly section 2.12 'Top bar and Global Menu'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm failing to suspend due to gvfsd-trash. Note in my case I am using
nfs mounts. I haven't tried disabling these and seeing if suspend is any
better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Re #53, I have compiled from source the a-l-m and tried the 'retrieve
from past' feature.
Unfortunately no matter what I do it says '0 events inserted', and no
extra files then seem to be visible.
I then tried the 'history.py' script that Seif kindly referenced on a
blog post of his a while
Hacked a bit more ...
The 'crawler' code in a-l-m has a bug comparing a timestamp in the form
of a string with another in the form of a float. Thats why it always
inserts 0 events (timestamp test always fails). It also has a potential
divide by zero bug if there are zero 'valid_uris'.
Correcting
'Last used window' would be a simpler algorithm - but still annoying if
you actually want to get to an obscured window (wihich wasn't the last
used).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It is now fixed in the 2.6.38.7 upstream stable release also - so will
be trickly into the stock Natty kernel in the not too distant future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/763227
Bug is logged upstream as https://bugzilla.kernel.org/show_bug.cgi?id=35042
It has a simple fix already in 2.6.39- kernels, though a better fix is in the
works.
I don't know if there will be plans to propose a fix for an upcoming
2.6.38.stable.
** Bug watch added: Linux Kernel Bug Tracker
Wrt to comment #23, I remember over a year ago in blog-posts or wherever
some communication between Seif of Zeitgeist fame and the Tracker people
about integration/linking together. There was talk of one of them
pushing events to the other.
Certainly if Tracker pushed an event to Zeitgeist
Public bug reported:
Binary package hint: virtualbox-ose
The udev rules shipped by virtualbox-ose apply a RUN script on usb interfaces
and devices. However the rules specify
RUN=
rather than
RUN+=
so all other scripts added by previous rules get usurped.
This means things like my scanner
I still find comments #10, #11, and #15 sum up the situ well - if 'the
main way users are expected to search' is purely zeitgeist powered, and
zeitgeist only ever relies on data-providers, then those searches are
going to fall short of users expectations.
So one way or another the user needs
1 - 100 of 131 matches
Mail list logo
