@dino99:
I guess this is related to the flash plugin. I only get this error with
installed flash plugin. Maybe the new preview releases from adobe fixes this.
But I doubt it. Maybe it's not Flash's fault at all.
However, to work around the problem:
Do once in terminal: rm -f ~/.xsession-errors*
the * ist just because there is also a file called .xsession-errors.old
if you switch this on/off in your session-properties, in case you want
to view the log file, with this XID-collision flooding, it may happen,
that the .old-file also get's quite big.
maybe the * is too much, but it's not harm
I'm sorry:
The command line is wrong. It works with this line:
sh -c "rm -f ~/.xsession-errors*"
--
Gdk-WARNING **: XID collision, trouble ahead
https://bugs.launchpad.net/bugs/401823
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+
the flooding of .xsession-errors and hd activity/waste is most
annoying for the end user.
here's a workaround:
ALT+F2
gnome-session-properties ENTER
"Add"
Name: remove xsession-errors on login
Command: rm -f .xsession-errors*
Comment: cool
That's it. logout and login.
Note that is should be "r
cover/artwork fetching is broken in lucid again. why not supplie an
alternative cover download location like lastfm? For me broken covers in
rhythmbok is a showstopper bug. really. :) please reopen this bug.
--
coverts fetching broken due to amazon changes
https://bugs.launchpad.net/bugs/421526
Y
@Miguel:
I would suggest starting firefox from a terminal with:
firefox > /dev/null &
I guess ALT+F2 with firefox > /dev/null should work, too.
--
(firefox:24993): Gdk-WARNING **: XID collision, trouble ahead - overeager XID
caching
https://bugs.launchpad.net/bugs/401823
You received this bug n
The critical thing about this bug is, that it floods .xsession-errors
from usually a few kb to megabytes.
Imho, this causes annoying useless disk activity/capacity and probably a
slightly slowdown/overhead.
This should be fixed.
--
(firefox:24993): Gdk-WARNING **: XID collision, trouble ahead -
Sorry, I forgot: This is the output when running firefox from terminal.
The last line "2.4+ kernel w/o ELF notes? -- report this" appears after
waiting for a while not using firefox. When using firefox interface
again after this, the XID collision lines appear again fluently.
--
(firefox:24993):
I also get the following message:
(firefox:1938): Gdk-WARNING **: XID collision, trouble ahead
(firefox:1938): Gdk-WARNING **: XID collision, trouble ahead
(firefox:1938): Gdk-WARNING **: XID collision, trouble ahead
2.4+ kernel w/o ELF notes? -- report this
What's the meaning of the last lin
Thanks everyone, especially @KennoVO for reporting.
Hopefully we don't have to wait till gstreamer-0.11 is releases and this
will just be included in a minor bugfix release of the lame plugin in
gstreamer-0.10.
Great news though. :-)
--
Sound Juicer - MP3 quality doesn't change
https://bugs.lau
The weird thing is, when you check those vbr mp3s created with sound-
juicer in VLC (Ctrl+i there the "statistics"-tab) the vbr-bitrate only
varies around 10 kb/s or even less, up and down. Check at the "Input"
box the values for "Input bitrate" and "Stream bitrate". This is
technically VBR, but no
Oops, my second pipeline (which got me a 5.5 MB file) is wrong above, a
typo. Here's the correct pipeline:
audio/x-raw-int,rate=44100,channels=2 ! lame name=enc mode=0 vbr-
quality=4 vbr-min-bitrate=96 vbr-max-bitrate=320 vbr-mean-bitrate=192
vbr=4 quality=0 ! xingmux ! id3v2mux
With "quality is
@KennoVo: I tried half a day yesterday trying to get different VBR-
mp3-filesizes and came to the same conclusion. Thanks for explaining.
For example I tried this:
audio/x-raw-int,rate=44100,channels=2 ! lame name=enc mode=0 quality=2 vbr=4
vbr-quality=3 ! xingmux ! id3v2mux
then checking with VL
Due mp3 support can not be officially supported (I guess), this really
IS kind of a showstopper bug.
Ripping only CBR mp3s as a workaround is not a good solution. Anyone
know why this is so hard to fix? In feisty this worked fine for me. (or
at least in edgy) I was hoping this would be solved in h
sorry for triple posting.
Here's a workaround: http://ubuntuforums.org/showthread.php?t=76566
There it's also said, that OOo2 makes automatically saves thumbnails into the
document-files. But I guess what we see in nautilus is from tracker.
Launchpad tells me that "tracker" uses Gnome-Bug-Tracke
So and here's the second screenshot with a different background set.
EDIT: Above the correct name of the thumbnail folder must be
~/.thumbnails/normal
** Attachment added: "tracker-odt-thumbnails-nautilus-dark.png"
http://launchpadlibrarian.net/16284432/tracker-odt-thumbnails-nautilus-dark.p
Hi!
I was quiet suprised when suddenly I saw odt-thumbnails in my document
folder. Reinstalling on another system I was not able to reproduce this
behaviour at first.
I figured out, that Tracker is responsible for making the thumbnails of
odt. files. But, I guess, you must run "tracker-preference
The problem in Gutsy is, that you can't select pipelines in sound-juicer which
include "xingmux".
They simply will not appear. This is the bug, I think. Though they are
available in gnome-audio-profiles-properties and active.
"xingmux" is pretty much needed to get correct metadata in VBR-mp3. Th
Can confirm this in Gutsy. Seems to happen with VBR settings. In Gutsy
(for me) there's also the problem, that pipelines including "xingmux"
will not appear to be selected in sound-juicer, though are listed in
gstreamer pipelines.
However, instead auf xingmux I tried ffmux_mpeg (ffmpeg packages) i
Perhaps this is maybe more MOTU-related to lame is not official supported (I
guess) by ubuntu?
Someone should make a thread on ubuntuforums.org.
Though .ogg is superior than .mp3 this bug is quite a showstopper if
someone needs to rip mp3s in an easy way for hardware players and mp3
/usb-sticks (
I guess this is not a problem of nautilus-cd-burner but the error is in hal
(libhal1 or hal1).
Check if you can select in the nautilus-burn dialog an appropiate speed. For me
it isn't possible since Gutsy, only weird speed selections beginning with 9x.
Therefore the error gets produced.
See thi
Still confirmed in Gutsy. (example "yelp man:xorg.conf")
--
manpage rendered wrong
https://bugs.launchpad.net/bugs/50318
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https:
Sorry, I forget something.
The other bug (not the feisty/GUI one), where profiles exist but won't
appear in the proper dialogue, where needed, can be found here:
https://bugs.launchpad.net/sound-juicer/+bug/109849
Both bugs are very familiar but when looking closing are based on
completely differ
Can confirm this behaviour in Gutsy with Sound-juicer. A workaround would be to
install the ffmpeg-packages and editing the gstreamer-pipeline (in Sound-Juicer
or by "gnome-audio-profile-properties") something like this:
"audio/x-raw-int,rate=44100,channels=2 ! lame name=enc quality=2 mode=0 vbr=
@Colin: Thanks! :-)
--
manpage rendered wrong
https://bugs.launchpad.net/bugs/50318
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/d
Ok, thanks. Maybe this bug is also related to the manpages package,
perhaps the error is in the charset there.
--
manpage rendered wrong
https://bugs.launchpad.net/bugs/50318
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-
*bump*
Should I create a new bug on this topic because my intention is not
exactly related to the actual bug report? Though it's quite close to it.
--
manpage rendered wrong
https://bugs.launchpad.net/bugs/50318
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Just ago I asked some people on irc ubuntu. Can now confirm, that this
occurs also on en-US environments. So this is _not_ a locale
configuration issue.
Someone on the irc, tried watching xorg.conf manpage with vi and there
it's the same error there. shows quotation marks (") as \*q
Very strange
can confirm that.
in gnome-terminal by typing "man xorg.conf" everything is fine.
when starting yelp and selecting xorg.conf manpage through search (by clicking)
or typing man:xorg.conf
all the quoation marks (") in this page get converted wrong to the letter Q
Example:
Option "Accel" "boolean"
Sorry forgot something:
Now after Rebooting I experienced, that e.g. services-admin starts without
asking permissions. Then you need to run alacarte menu editor and check the
section >System >Administration and put gksu before these commands:
gksu gdmsetup
gksu users-admin
gksu time-admin
gksu s
For me the error occured when I wanted to disable some services via
"services-admin". Accidentally I unchecked dbus. And since there was the
problem.
Fix:
Run Synaptic (should still work)
Re-Install following packages:
-gnome-system-tools
-system-tools-backend
-dbus
-libdbus-1-3
(or simply all pac
31 matches
Mail list logo
