gnome-volume-control is vastly improved in Jaunty. The Volume Control
Preferences menu now lists whether each 'track' pertains to "Playback",
"Recording", "Switches", or "Options".
The Alsa mixer still has too many options in the Preferences menu for my
on-board Intel audio hardware (see below). S
I was wrong. Not only is this not fixed, it is not even consistent in
Hardy.
- Checking and unchecking various checkboxes in the Volume Control
Preferences dialog causes additional sliders to appear in the Playback,
Recording and Options tabs somewhat randomly. For example, after some
fiddling wit
ethanay: I was the OP. With the same hardware as before, under Hardy
(gnome-volume-control 2.22.0, alsa 1.0.16-0ubuntu4):
- I now see only one Input Source box in the Options tab (even though the
Preferences box contains three checked "Input Source" checkboxes).
- The same is true for the Capture
This has been fixed since Hardy. Closing.
** Changed in: gnome-media (Ubuntu)
Status: New => Fix Released
--
[Gutsy] Usability problems in gnome-volume-control
https://bugs.launchpad.net/bugs/138989
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
The bug was, it seems, accidentally marked "invalid" for compiz, when it
should only be "invalid" for gnome-screensaver.
** Changed in: compiz (Ubuntu)
Status: Invalid => Confirmed
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
As Ted Gould points out, this seems to be a bug with compiz or X, not
gnome-screensaver.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Invalid
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug
On Mon, 2008-02-04 at 06:59 +, Ted Gould wrote:
> No, I marked it invalid because it doesn't make sense that there is
> something gnome-screensaver could do would crash compiz. Even if there
> was, that's a bug with compiz not gnome-screensaver. They're at the
> wrong places in the stack to a
Ted, have you really marked a segfault bug with 22 duplicates as
"invalid" because you personally have not experienced it on your
particular hardware?
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification bec
I also get a SIGSEGV on Hardy amd64 when resuming from suspend with an
Intel G965 graphics card. I presume it's the same bug. My stack trace
is:
Stacktrace:
#0 0x7f25ae818f33 in ?? () from /usr/lib/compiz/libworkarounds.so
#1 0x7f25ae819dfa in ?? () from /usr/lib/compiz/libworkarounds.
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
Failed To initialize HAL!
https://bugs.launchpad.net/bugs/127473
You received this bug notification because you are a member
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug is no longer a duplicate of bug 127473
Failed To initialize HAL!
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
error de hal
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug is no longer a duplicate of bug 146812
Gusty Beta: error on startup. "Internal Error" "failed to initialize HAL!"
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug is no longer a duplicate of bug 146812
Gusty Beta: error on startup. "Internal Error" "failed to initialize HAL!"
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
Gusty Beta: error on startup. "Internal Error" "failed to initialize HAL!"
https://bugs.launchpad.net/bugs/146812
You receive
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug has been marked a duplicate of bug 127473
Failed To initialize HAL!
--
error de hal
https://bugs.launchpad.net/bugs/134885
You received this bug notification because you are a member of Ubuntu
D
This affects Gutsy. I've clarified the original report.
** Summary changed:
- Input Source boxes are unlabelled in gnome-volume-control
+ [Gutsy] Usability problems in gnome-volume-control
** Description changed:
Binary package hint: gnome-media
- I find that the correct mixer settings are
** Attachment added: "Recording tab showing separate capture channels (Capture,
Capture 1, Capture 2). These are also poorly labelled (what are Capture 1 and
Capture 2?) but at least they are distinct. Do these correspond to the three
"Input Source" boxes in the Options tab?"
http://launchp
** Attachment added: "Options tab in gnome-volume-control showing identical,
uninformative labels of "Input Source" for different channels"
http://launchpadlibrarian.net/9248929/Screenshot-Volume%20Control%3A%20HDA%20Intel%20%28Alsa%20mixer%29%20-%20Options.png
--
Input Source boxes are unl
This bug is still present on Gutsy (which currently has alsa-
base-1.0.13-3ubuntu1).
--
Microphone bug in Ubuntu HDA_Intel
https://bugs.launchpad.net/bugs/37736
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing l
Public bug reported:
Binary package hint: gnome-media
I find that the correct mixer settings are extremely difficult to arrive
at using gnome-volume-control -- the process often takes me several
minutes of frustrating trial and error after each reboot or after waking
from suspend, both of which s
** Summary changed:
- sound problem in Audigy 2
+ Gnome Volume Control change device function has no effect
--
Gnome Volume Control change device function has no effect
https://bugs.launchpad.net/bugs/87909
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 121796 ***
https://bugs.launchpad.net/bugs/121796
Kamus: sorry, s/when now/when not/
--
[Gutsy] Move to Another Workspace has no effect
https://bugs.launchpad.net/bugs/131169
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
*** This bug is a duplicate of bug 121796 ***
https://bugs.launchpad.net/bugs/121796
Kamus: this bug is present even when now using desktop effects on Gutsy.
--
[Gutsy] Move to Another Workspace has no effect
https://bugs.launchpad.net/bugs/131169
You received this bug notification because y
*** This bug is a duplicate of bug 121796 ***
https://bugs.launchpad.net/bugs/121796
Sebastien: Are you sure this is a duplicate of bug #121796? Its
description seems completely different to me. Indeed, the original
submitter of bug #132372 (which _does_ seem to be a duplicate of
#121796) says
Public bug reported:
Binary package hint: metacity
Right-clicking a window's title bar and choosing Move to Another
Workspace has no effect for me in Gutsy. This is true for all
applications (not just Synaptic as in bug 36443). Choosing "Move to
Workspace Left" or "... Right" works as expected. T
Good work!
Should the shared-mime (upstream) bug report also be closed?
--
application/mbox should be a sub-class of text/plain?
https://launchpad.net/bugs/83001
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
*** This bug is a duplicate of bug 70535 ***
** This bug has been marked a duplicate of bug 70535
nautilus crashes when copying a 4G file on a vfat volume
--
Nautilus crashes trying to copy >4GB file to msdos fs
https://launchpad.net/bugs/26042
--
desktop-bugs mailing list
desktop-bugs@list
Public bug reported:
Binary package hint: nautilus
Nautilus 2.17.90 refuses to open certain text files, claiming:
"Error: no application found
Cannot open /home/me/file.txt: No application is known for this kind of file."
A test case:
echo "From Dostoevsky:" > test1.txt
echo "In Dostoevsky:" >
Ah, libflashplayer.so appears in the stack trace, so a likely culprit is
my Adobe plugin. (But after removing libflash0c2, libflash-swfplayer,
and libflash-mozplugin, I can't reproduce the crash. Perhaps these
conflict with the Adobe plugin. Damned Flash.)
Epiphany-browser still has the following
** Attachment added: "Crash report from Epiphany 2.17.4-0-ubuntu1"
http://librarian.launchpad.net/5631763/_usr_bin_epiphany.1079.crash
--
[Feisty] Crash displaying pages in the Amazon Online Reader
https://launchpad.net/bugs/78441
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
h
Public bug reported:
Binary package hint: epiphany-browser
I can repeatably crash epiphany-browser by loading the following page:
http://www.amazon.com/gp/reader/080583270X/ref=sib_dp_pt/102-6275526-9992103
#reader-link
and switching to other windows.
Crash report attached.
** Affects: epipha
I'm seeing this problem right now under Edgy. I notice I have lots of
evil multimedia plugins installed (w32codecs and gstreamer0.10-plugins-
good, -bad, and -ugly). I'll remove as many as possible and see if I can
isolate which one is locking /dev/dsp...
** Attachment added: "about:plugins under
Matt Zimmerman has said that he has already discussed a potential
upgrade to 1.7.1 privately with Gauvain Pocentek and Jani Monoses and
decided against it because it would require updates to libraries used by
other packages (presumably libgsf 1.14.2 etc., described in
http://ftp.gnome.org/pub/GNOME
Sorry Jani, didn't see your comment before. I can't see any other Edgy-
specific bug reports in LP that are fixed by 1.7.1. But 1.7.1 does fix a
long list of bugs reported in bugzilla.gnome.org, as the release notes
describe.
If we keep 1.7.0 in for Edgy, it's only a matter of time before more of
There's a whole raft of bug fixes in 1.7.1:
http://www.gnome.org/projects/gnumeric/announcements/1.7/gnumeric-1.7.1.html
I've emailed mdz and cjwatson to request an exception to the upstream
version freeze.
--
ssindex crashes
https://launchpad.net/bugs/63297
--
desktop-bugs mailing list
deskt
Here is the file comm_jar_includes.csv that causes ssindex to crash.
It's a plain text file, not comma separated data.
Running:
[EMAIL PROTECTED] ssindex -i comm_jar_includes.csv
gives:
Reading
file:///home/schofield/mozilla-thunderbird-1.5.0.7/debian/comm_jar_includes.csv
Segmentation fault (
I can confirm this bug. I have 1.5GB of memory free and I've just seen a
crash message from ssindex caused by beagled. My kern.log shows nothing
untoward.
Crash report attached. The file comm_jar_includes.csv being indexed is
from the Thunderbird source code tree. I'll attached this file too
below
Public bug reported:
Binary package hint: evince
With the attached PDF file is loaded, after choosing File | Save As, then
hitting the Cancel button, Evince hangs in Edgy.
The end of the strace is:
write(16, "gtk-events-2/clicked\0\0\0\0\0\0\0\0\0\0\0\0"..., 128) = 128
read(16, "\377\377\377\
** Attachment added: "PDF file that causes Evince to hang as described above."
http://librarian.launchpad.net/4213531/3695904.PDF
--
Evince hangs upon File | Save As in Edgy
https://launchpad.net/bugs/59796
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
Why is rebuilding the deps a hack?
If there's something fragile about it, couldn't we just back out the
003_refcount patch for Dapper, and issue an update later? I assume
libpoppler will need several security updates throughout Dapper's
support period. Won't some of these break ABI? Is there a
Why is rebuilding the deps a hack?
If there's something fragile about it, couldn't we just back out the
003_refcount patch for Dapper, and issue an update later? I assume
libpoppler will need several security updates throughout Dapper's
support period. Won't some of these break ABI? Is there a
Bug #45595 is a duplicate of this. But I think bug #45406 might be
unrelated.
I can confirm that gnome-cups-icon sometimes eats CPU cycles. On my
system (with Dapper) it's 100% right now. I've just done a dist-
upgrade, which installed new versions of gnome-panel , gnome-panel-data,
and update-
This is a duplicate of bug #45421.
I can confirm that gnome-cups-icon sometimes eats CPU cycles. On my
system (with Dapper) it's 100% right now. I've just done a dist-
upgrade, which installed new versions of gnome-panel , gnome-panel-data,
and update-manager, among others. Killing gnome-panel
I'd still be interested to know why the upstream fontconfig developers
substitute the URW Nimbus fonts for Adobe Times etc rather than substituting
the free UCS outline fonts (FreeSerif, FreeSans etc.) I think these are closer
to the Adobe fonts, and look very respectable (see the screenshot a
Yes, the font matching is much better now. Well done!
--
[Dapper] Text is not rendered properly
https://launchpad.net/bugs/31596
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/31596
- Changed attachments:
Added: Screenshot of evince rendering a PDF with non-embedded fonts
with the font substitutions for Adobe Times etc restored to fontconfig defaults
http://librarian.launchpad.net/1804
Public bug report changed:
https://launchpad.net/malone/bugs/31596
Comment:
Actually, it seems that fonts.conf supplied with the upstream fontconfig
package does something similar, substituting the URW Nimbus fonts for
Times, Helvetica, and Courier, but that the Ubuntu package comments
these lines
Public bug report changed:
https://launchpad.net/malone/bugs/35073
Comment:
Mark Shuttleworth, in person! You're doing a fine service to the world
by sponsoring and being so personally involved in Ubuntu.
Anyway ... the bug. I haven't been able to reproduce it since
restarting. So we can proba
Public bug report changed:
https://launchpad.net/malone/bugs/35073
- Changed attachments:
Added: Crazy colour map when changing from Clearlooks to Human theme
http://librarian.launchpad.net/1735996/human-crazy-colours.png
--
desktop-bugs mailing list
desktop-bugs@lists.ubun
Public bug report changed:
https://launchpad.net/malone/bugs/33102
Comment:
I can confirm this on my desktop too. Note that even though the "Take a
screenshot" key is initially assigned to Print, and Alt-Print is
assigned to take a screenshot for the current window, neither worked for
me initiall
Public bug reported:
https://launchpad.net/malone/bugs/35073
Affects: ubuntu-artwork (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
Changing icon theme from Clearlooks to Ubuntu Human in Dapper makes the
colours in gnome-panel and some menu
Public bug report changed:
https://launchpad.net/malone/bugs/31596
- Changed attachments:
Added: Screenshot with substitution of Microsoft fonts
http://librarian.launchpad.net/1724230/Screenshot-with-msttcorefonts.png
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.
Public bug report changed:
https://launchpad.net/malone/bugs/31596
- Changed attachments:
Added: Screenshot with suggested font config
http://librarian.launchpad.net/1724206/Screenshot-with-suggested-font-config.png
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.co
Public bug report changed:
https://launchpad.net/malone/bugs/31596
- Changed attachments:
Added: Current font config
http://librarian.launchpad.net/1724196/Screenshot-with-current-font-config.png
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubun
Public bug report changed:
https://launchpad.net/malone/bugs/31596
Comment:
Adding the following lines to fonts.conf solves the problem:
Times
FreeSerif
Helvetica
FreeSans
Public bug report changed:
https://launchpad.net/malone/bugs/31596
Comment:
The bug is still present as of 2006-03-07. It seems to occur with PDF files
that use fonts such as Times Roman without embedding them. Here is an example:
www.latex-project.org/papers/xo-pfloat.pdf
Dapper's fontconfi
56 matches
Mail list logo
