[Bug 138989] Re: [Gutsy] Usability problems in gnome-volume-control
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). See the attached screenshot. Input Source is listed three times, and Capture, Capture 1, and Capture 2 are indistinguishable to me. (The UI also gives me no clue about what the IEC958 tracks are ...) With kernel 2.6.28-ubuntu9, lspci -vv gives: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Device 820a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at ff9f4000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel If I open an upstream bug report, should this be against alsa or gnome- volume-control? ** Attachment added: Screenshot showing Alsa Mixer Preferences for Intel on-board audio hardware http://launchpadlibrarian.net/23886816/Screenshot-1.png -- [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 is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138989] Re: [Gutsy] Usability problems in gnome-volume-control
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 with the Input Source checkboxes in Preferences, between one and three Input Source text fields appear in the Options tab, all indistinguishable but apparently controlling different channels. Unclearing the Input Source checkboxes in Preferences does not remove the entries reliably. - Other usability bugs are present, like the Preferences dialog having checkboxes for not only the expected Line-in, Front Mic, Microphone, but also IEC958 Capture, Capture, Capture 1, Capture 2, and three identical Input Source entries. The hardware itself doesn't appear to have more than the first three input-related sockets. I'll test this on Jaunty, as Lionel requested... -- [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 is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138989] Re: [Gutsy] Usability problems in gnome-volume-control
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 slider in the Recording tab: there is only one, even if all three of Capture, Capture 1, and Capture 2 are checked in the Preferences box. - There are no more erroneous status bar messages. So I'm happy now -- but you're still seeing these issues? Shall we re- open the bug report? Could you perhaps test a Jaunty alpha live CD, like Lionel suggested? And open an upstream bug report if it's still there? -- [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 is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138989] Re: [Gutsy] Usability problems in gnome-volume-control
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 is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: compiz.real crashed with SIGSEGV when attempting to unlock screen
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 affect each other in that way. I'm not saying the bug is invalid, I'm saying that assigning it to gnome-screensaver is invalid and that is all that I changed. It might be an X bug, but it seems most likely to be a compiz bug to me. Ted: Okay, thanks for the clarification! -- compiz.real crashed with SIGSEGV when attempting to unlock screen https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: compiz.real crashed with SIGSEGV when attempting to unlock screen
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 notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: compiz.real crashed with SIGSEGV when attempting to unlock screen
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 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: compiz.real crashed with SIGSEGV when attempting to unlock screen
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 because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131679] Re: compiz.real crashed with SIGSEGV when attempting to unlock screen
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.so #2 0x7f25ae612a46 in ?? () from /usr/lib/compiz/libezoom.so #3 0x7f25ae40bd45 in ?? () from /usr/lib/compiz/libvpswitch.so #4 0x7f25ae0002ba in ?? () from /usr/lib/compiz/libfade.so #5 0x7f25addf8a04 in ?? () from /usr/lib/compiz/libshift.so #6 0x7f25adbe7c28 in ?? () from /usr/lib/compiz/libwobbly.so #7 0x00411b88 in eventLoop () #8 0x0040d059 in main () StacktraceTop: ?? () from /usr/lib/compiz/libworkarounds.so ?? () from /usr/lib/compiz/libworkarounds.so ?? () from /usr/lib/compiz/libezoom.so ?? () from /usr/lib/compiz/libvpswitch.so ?? () from /usr/lib/compiz/libfade.so -- compiz.real crashed with SIGSEGV when attempting to unlock screen https://bugs.launchpad.net/bugs/131679 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 134885] Re: error de hal
*** 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 Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 146812] Re: Gusty Beta: error on startup. Internal Error failed to initialize 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 received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 144044] Re: [gutsy] Failed to initialize 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. -- [gutsy] Failed to initialize HAL https://bugs.launchpad.net/bugs/144044 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 137559] Re: [gutsy] failed to initialize 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. -- [gutsy] failed to initialize hal https://bugs.launchpad.net/bugs/137559 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 134885] Re: error de hal
*** 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/134885 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 127473] Re: Failed To initialize 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. -- Failed To initialize HAL! https://bugs.launchpad.net/bugs/127473 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138989] Re: [Gutsy] Usability problems in gnome-volume-control
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 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 seem to lose the mixer settings (bug - #37736). The most glaring problem is that the Options tab for my HDA - Intel on-board sound chipset (specs below) has three input boxes all - labelled the same (Input Source), but apparently controlling different - capture channels. The status bar output is also incorrect, stating - Volume of right channel on PCM irrespective of the input box selected. + The Options tab in gnome-volume-control has at least two usability + problems: + + (1) The most glaring problem is that the Options tab for HDA Intel on- + board sound chipsets (specs below) has three input boxes all labelled + the same (Input Source), but apparently controlling different capture + channels. + + (2) While on the Options tab, the status bar output is incorrect, saying + Volume of right channel on PCM, which bears no relation to any + selections made. Screenshots attached below. Audio is from the Intel G965 chipset. lspci -vv gives: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 820a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at ff9f4000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied + + I suspect the support from alsa 1.0.14 for the onboard Intel sound + chipset may be better than that from the obsolete version of alsa + (1.0.13) still in Gutsy. Would upgrading alsa fix problem (1) above for + free? -- [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 is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87909] Re: Gnome Volume Control change device function has no effect
** 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 is a bug contact for control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138989] Input Source boxes are unlabeled in gnome-volume-control
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 seem to lose the mixer settings (bug #37736). The most glaring problem is that the Options tab for my HDA Intel on-board sound chipset (specs below) has three input boxes all labelled the same (Input Source), but apparently controlling different capture channels. The status bar output is also incorrect, stating Volume of right channel on PCM irrespective of the input box selected. Screenshots attached below. Audio is from the Intel G965 chipset. lspci -vv gives: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 820a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at ff9f4000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied ** Affects: gnome-media (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 a reboot. One problem is - that the Options tab for my HDA Intel on-board sound chipset (specs + minutes of frustrating trial and error after each reboot or after waking + from suspend, both of which seem to lose the mixer settings. One problem + is that the Options tab for my HDA Intel on-board sound chipset (specs below) has three input boxes all labelled the same (Input Source), but apparently controlling different capture channels. The status bar output is also incorrect, stating Volume of right channel on PCM irrespective of the selection. Screenshots attached below. Audio is from the Intel G965 chipset. lspci -vv gives: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 820a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at ff9f4000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied -- Input Source boxes are unlabelled 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 is a bug contact for gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37736] Re: Microphone bug in Ubuntu HDA_Intel
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 list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138989] Re: Input Source boxes are unlabeled in gnome-volume-control
** 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 unlabelled 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 is a bug contact for gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138989] Re: Input Source boxes are unlabeled in gnome-volume-control
** 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://launchpadlibrarian.net/9248933/Screenshot-Volume%20Control%3A%20HDA%20Intel%20%28Alsa%20mixer%29%20-%20Recording.png ** Summary changed: - Input Source boxes are unlabeled in gnome-volume-control + Input Source boxes are unlabelled in gnome-volume-control ** Description changed: 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 seem to lose the mixer settings. One problem - is that the Options tab for my HDA Intel on-board sound chipset (specs - below) has three input boxes all labelled the same (Input Source), but - apparently controlling different capture channels. The status bar output - is also incorrect, stating Volume of right channel on PCM irrespective - of the selection. + from suspend, both of which seem to lose the mixer settings (bug + #37736). The most glaring problem is that the Options tab for my HDA + Intel on-board sound chipset (specs below) has three input boxes all + labelled the same (Input Source), but apparently controlling different + capture channels. The status bar output is also incorrect, stating + Volume of right channel on PCM irrespective of the input box selected. Screenshots attached below. Audio is from the Intel G965 chipset. lspci -vv gives: 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 820a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at ff9f4000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied -- Input Source boxes are unlabelled 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 is a bug contact for gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 131169] Re: [Gutsy] Move to Another Workspace has no effect
*** 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 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/desktop-bugs
[Bug 131169] Re: [Gutsy] Move to Another Workspace has no effect
*** 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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 131169] Re: [Gutsy] Move to Another Workspace has no effect
*** 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 that that, for him, Interestingly though, the move to another workspace sub menu on the window list context menu is not affected. -- [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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131169] [Gutsy] Move to Another Workspace has no effect
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. This has been the case since I first upgraded to Gutsy about two months ago. I'm surprised I'm the first person to report it so far. Compiz is disabled. I have no proprietary kernel modules loaded (only proprietary firmware for the bcm43xx wireless driver). My graphics hardware is Intel G965 / X3000 at 1680x1050 resolution. I suspect this is a Metacity bug, but I don't know which log files to look at to get more information on the problem. Any ideas? ** Affects: metacity (Ubuntu) Importance: Undecided Status: New -- [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, which is a bug contact for metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 26042] Re: Nautilus crashes trying to copy 4GB file to msdos fs
*** 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 83001] Re: application/mbox should be a sub-class of text/plain?
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
[Bug 83001] [Feisty] nautilus cannot find an application to open certain text files
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: test2.txt Nautilus correctly opens test2.txt but not test1.txt. I'm using amd64 Feisty with LANG=en-US.UTF-8. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Unconfirmed -- [Feisty] nautilus cannot find an application to open certain text files https://launchpad.net/bugs/83001 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 78441] [Feisty] Crash displaying pages in the Amazon Online Reader
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: epiphany-browser (Ubuntu) Importance: Undecided Status: Unconfirmed -- [Feisty] Crash displaying pages in the Amazon Online Reader https://launchpad.net/bugs/78441 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 78441] Re: [Feisty] Crash displaying pages in the Amazon Online Reader
** 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 78441] Re: [Feisty] Crash displaying pages in the Amazon Online Reader
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 bug, IMHO: it allows a buggy plugin to crash the epiphany process. Could it be made more robust against rogue plugins? -- [Feisty] Crash displaying pages in the Amazon Online Reader https://launchpad.net/bugs/78441 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49279] Re: epiphany opens /dev/dsp exclusevely
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 epiphany when /dev/dsp is locked http://librarian.launchpad.net/4938271/about_plugins.html -- epiphany opens /dev/dsp exclusevely https://launchpad.net/bugs/49279 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63297] Re: ssindex crashes
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. ** Attachment added: Crash report from ssindex http://librarian.launchpad.net/4777642/_usr_bin_ssindex.1079.crash -- ssindex crashes https://launchpad.net/bugs/63297 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63297] Re: ssindex crashes
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 (core dumped) ** Attachment added: File that causes ssindex to dump core http://librarian.launchpad.net/4777646/comm_jar_includes.csv -- ssindex crashes https://launchpad.net/bugs/63297 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63297] Re: ssindex crashes
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63297] Re: ssindex crashes
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 those bugs get re-discovered by Edgy users. Then the fixes that 1.7.1 comprises will need to be applied individually, in response to specific reports about bugs that we know exist, wasting the time of users and developers. The only packages that depend on gnumeric are gnumeric-doc gnumeric-plugins-extra beagle so the risk of breakage seems very limited. :) -- ssindex crashes https://launchpad.net/bugs/63297 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63297] Re: ssindex crashes
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/sources/gnumeric/1.7/gnumeric-1.7.1.changes) -- ssindex crashes https://launchpad.net/bugs/63297 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 59796] Re: Evince hangs upon File | Save As in Edgy
** 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/mailman/listinfo/desktop-bugs
[Bug 59796] Evince hangs upon File | Save As in Edgy
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\377, 4) = 4
rt_sigaction(SIGPIPE, {SIG_IGN}, {0xb6fb4a20, [PIPE], SA_RESTART}, 8) = 0
gettimeofday({1157904700, 201232}, NULL) = 0
open(/home/schofield/.config/gtk-2.0/gtkfilechooser.36BSFT,
O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 18
fcntl64(18, F_GETFL)= 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat64(18, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb5741000
_llseek(18, 0, [0], SEEK_CUR) = 0
write(18, gtkfilechooser\n location mod..., 96) = 96
close(18) = 0
munmap(0xb5741000, 4096)= 0
rename(/home/schofield/.config/gtk-2.0/gtkfilechooser.36BSFT,
/home/schofield/.config/gtk-2.0/gtkfilechooser) = 0
write(3, \n\4\2\0\246\2\200\3\31\0\v\0M\0\0\0\0\0\30\0\22e\350\277..., 108) =
108
read(3, 0xbfe84ba0, 32) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(3, \0226\305\27\246\2\200\3\246\2\200\3\0s\316\10\320\20\0..., 32) = 32
read(3, \n\0\305\27\247\2\200\3\0\0\0\0\0\0\0\0\374\23\34\10\240..., 32) = 32
read(3, \n\1\305\27\246\2\200\3\0\0\0\0H\337$\10H\375#\10\230\16..., 32) = 32
read(3, \t\5\305\27\246\2\200\3\0\21\246\10\0\0\0\0\374\23\34\10..., 32) = 32
read(3, \10\0\305\27*\223\177\230M\0\0\0\324\2\200\3\0\0\0\0\233..., 32) = 32
read(3, \10\1\305\27*\223\177\230M\0\0\0\246\2\200\3\324\2\200..., 32) = 32
read(3, \0226\307\27\251\2\200\3\251\2\200\3\0\2\200\3\1\0\0\300..., 32) = 32
read(3, \0226\310\27\252\2\200\3\252\2\200\3\0\2\200\3\1\0\0\300..., 32) = 32
read(3, \0226\311\27\260\2\200\3\260\2\200\3\0\2\200\3\1\0\0\300..., 32) = 32
read(3, \21\23\312\27\251\2\200\3\251\2\200\3\2306\367\277\244..., 32) = 32
read(3, \35\0\313\27!\223\177\230\322\2\200\3\1\0\0\0\5\0\0\0\30..., 32) = 32
read(3, p\0\313\27\1\0\200\3\0\0\0\0\1\0\0\0*\223\177\230!\223..., 32) = 32
read(3, \1\0\314\27\0\0\0\0\0\0\0\0\5\0\0\0\10\0\0\0\0\0\0\0\0..., 32) = 32
clone(child_stack=0xb4cd54e4,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID|CLONE_DETACHED,
parent_tidptr=0xb4cd5be8, {entry_number:6, base_addr:0xb4cd5ba0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}, child_tidptr=0xb4cd5be8) = 29770
stat64(/, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
gettimeofday({1157904700, 209470}, NULL) = 0
gettimeofday({1157904700, 209699}, NULL) = 0
open(/usr/share/icons/Human/16x16/devices/gnome-dev-harddisk.png,
O_RDONLY|O_LARGEFILE) = 18
fstat64(18, {st_mode=S_IFREG|0644, st_size=639, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb5741000
read(18, \211PNG\r\n\32\n\0\0\0\rIHDR\0\0\0\20\0\0\0\20\10\6\0\0..., 4096) =
639
read(18, , 4096) = 0
_llseek(18, 0, [0], SEEK_SET) = 0
read(18, \211PNG\r\n\32\n\0\0\0\rIHDR\0\0\0\20\0\0\0\20\10\6\0\0..., 4096) =
639
close(18) = 0
munmap(0xb5741000, 4096)= 0
gettimeofday({1157905084, 319604}, NULL) = 0
gettimeofday({1157905084, 322171}, NULL) = 0
gettimeofday({1157905084, 326077}, NULL) = 0
SYS_293(0x11, 0x1, 0x842a5d0, 0xb570f7f0, 0xb5713230) = 0
futex(0x811c640, FUTEX_WAIT, 2, NULL
** Affects: evince (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
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/mailman/listinfo/desktop-bugs
[Bug 24970] Re: evince crashes when highlighting text at line end
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 mechanism in place to distribute re-built dependencies for such updates? Is there a more appropriate forum for such questions? -- evince crashes when highlighting text at line end https://launchpad.net/bugs/24970 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24970] Re: evince crashes when highlighting text at line end
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 mechanism in place to distribute re-built dependencies for such updates? Is there a more appropriate forum for such questions? -- evince crashes when highlighting text at line end https://launchpad.net/bugs/24970 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45595] Re: gnome-cups-icon takes up way too much CPU
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 doesn't help, but killing the renegade gnome-cups-icon process does ... -- gnome-cups-icon takes up way too much CPU https://launchpad.net/bugs/45595 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45421] Re: gnome-cups-icon constantly uses 75% of CPU
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-manager, among others. This may or may not be related. Killing gnome-panel doesn't help, but killing the renegade gnome-cups- icon process solves the problem. I've resorted to this about once per week since installing Dapper. -- gnome-cups-icon constantly uses 75% of CPU https://launchpad.net/bugs/45421 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31596] Re: [Dapper] Text is not rendered properly
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
[Bug 31596] Re: [Dapper] Text is not rendered properly
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 above, dated 2006-03-14 12:40:37). -- [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
[Bug 31596] [Dapper] Text is not rendered properly
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 out. See http://archive.ubuntu.com/ubuntu/pool/main/f/fontconfig/fontconfig_2.3.2-1.1ubuntu5.diff.gz I don't know the rationale behind the Ubuntu fontconfig package maintainer's decision to do this, but this is the cause of the incorrect fonts in e.g. evince. The removed lines from the above diff are: !-- - URW provides metric and shape compatible fonts for these 3 Adobe families. - -- -alias - familyTimes/family - acceptfamilyNimbus Roman No9 L/family/accept - /alias -alias - familyHelvetica/family - acceptfamilyNimbus Sans L/family/accept - /alias -alias - familyCourier/family - acceptfamilyNimbus Mono L/family/accept - /alias - One further note --- restoring these lines fixes these three fonts, but not the substitution for the Adobe Symbol font: [EMAIL PROTECTED]:~$ fc-match Symbol DejaVuSans.ttf: DejaVu Sans Book This causes evince to render PDF documents with non-embedded Symbol characters (such as mathematical papers) incorrectly, as in the attached screenshot. So I would also recommend making a Symbol substitution such as alias familySymbol/family acceptfamilyStandard Symbols L/family/accept /alias or an equivalent. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31596] [Dapper] Text is not rendered properly
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/1804065/Screenshot-with-default-xorg-fontconfig.png -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35073] Changing to Human theme requires manual restart of gnome-panel
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 bars (such as in GNOME Terminal) go psychedelic, as if the colour map is wrong. Screenshot attached. I was able to solve this problem by following Sebastien Bacher's advice in response to another bug (#23162): running sudo gtk-update-icon-cache /usr/share/icons/hicolor restarting gnome-panel and then restarting all running GTK applications with crazy colours but this is more effort than it should be. Could Breezy upgraders with a window theme like Clearlooks experience this when they try to change to Human, or will the appropriate caches be refreshed automatically? -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 33102] Pause / Print Screen keys can't be set in Keyboard Shortcuts
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 initially (hence the attempt to fix it using Keyboard Shortcuts). My keyboard is possibly strange in this regard: the Print screen key is shared with Sys req, with one printed on top of the other. The Keyboard Shortcuts applet recognizes Shift Print, but using both Alt and Shift together with Print is registered as Shift Alt Sys_Req... -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35073] Changing to Human theme requires manual restart of gnome-panel
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35073] Changing to Human theme requires manual restart of gnome-panel
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 probably close it as a non-issue... -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31596] [Dapper] Text is not rendered properly
Public bug report changed: https://launchpad.net/malone/bugs/31596 Comment: Adding the following lines to fonts.conf solves the problem: !-- Alias well known Type1 font names to metric-equivalent TrueType fonts -- alias familyTimes/family acceptfamilyFreeSerif/family/accept /alias alias familyHelvetica/family acceptfamilyFreeSans/family/accept /alias alias familyCourier/family acceptfamilyFreeMono/family/accept /alias alias familySymbol/family acceptfamilyStandard Symbols L/family/accept /alias I think these fonts are metrically equivalent to the Adobe fonts. The alias for Symbol is necessary for some PDF files that use Times- compatible math fonts without embedding them. After this change, the command fc-match Times gives: FreeSerif.ttf: FreeSerif Medium instead of: VeraSe.ttf: Bitstream Vera Serif Roman. Then the svn-book.pdf file that Vincent Trouilliez identified as a problem looks fine under evince, as do the others I've tested. I don't think it's necessary to substitute the Microsoft equivalents of these fonts (like SUSE does), even if the msttcorefonts package is installed. Substituting Times New Roman for Times, in particular, look worse than substituting FreeSerif in my humble opinion. See attached screenshots. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31596] [Dapper] Text is not rendered properly
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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31596] [Dapper] Text is not rendered properly
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.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31596] [Dapper] Text is not rendered properly
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 fontconfig seems to substitute Bitstream Charter here for Times; hence the incorrect letter spacing. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
