Public bug reported:
Some information has been provided here:
https://answers.launchpad.net/ubuntu/+source/gnome-
terminal/+question/165573
Basically, the Diamond character in the APL385.ttf font does not scale
correctly when the system
font size changes using, e.g.,
** Attachment added: Screen shot of xterm and gnome-terminal w/same text
https://bugs.launchpad.net/bugs/814796/+attachment/2226545/+files/xtermgnome.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
One possibility is that the APL385.ttf font entry for diamond is either wrong,
or has some subtle problem that causes gnome-terminal to get the scaling wrong.
The font is available here:
www.dyalog.com/downloads/fonts/Apl385.ttf
--
You received this bug notification because you are a member
Attached is a screen shot from Open Office. In that, you can see that
the diamond character displays correctly at different sizes
(i.e., slightly larger than the iota and rho) when using Times New Roman,
but displays much smaller when using the fixed-width font.
From this example, I see that the
I don't particularly care about graphics performance, but definitely DO want
(1) switch-user to work properly (which, at present, crashes my system), and
(2) dual-head support to work properly.
So, I may not need the apparently useless drivers from AMD/ATI, if they are the
root
of the problem,
Well, I now agree that the bug is still there: after a recent update,
if restricted drivers are enabled (ATI fglrx), the system crashes
immediately after System/Logout/Change User or on an
attempt to change users with the Fast User Switch applet.
If restricted drivers are disabled, the user
1. I'm running gnome.
2. I think I installed dual-head this way:
- normal install of 8.10 release
- System/Administration/Hardware Drivers: enable ATI drivers.
3. At this point, I think the system claims that a reboot is needed.
I'm not sure if that is the case...
4. I
No problems with Ubuntu 8.10, so I think we can close this(unless
the failsafe note just above is still relevant?).
Thanks!
--
doesn't handle when edid data can't be parsed [gnome-settings-daemon crashed
with SIGSEGV in configuration_new_current()]
https://bugs.launchpad.net/bugs/215751
You
After a complete install of the released version of Ubuntu 8.10 on another
partition,
this is nearly working perfectly.
The system loses the ATI Catalyst dual-head settings over a reboot, but things
are otherwise good.
BTW, installation of the restricted drivers is very nice now!
I think we
I'm running Intrepid Alpha 3, and just reinstalled the (July 21?) ATI drivers
from scratch.
That produces bug#247376. AIGLX settings don't appear to be relevant.
So, I consider the ATI drivers to be, at this stage,
completely useless for my work. From the looks of the other bug reports hanging
I have enabled http://ddebs/ubuntu.com hardy-updates and hardy-
proposed.
A quick eyeball scan does not show anything new in envy or xorg-drivers.
I have no idea how to properly (safely) update from intrepid. Can you please
give me a hint?
Thanks. R
--
[fglrx] freezes upon Logout or Switch
change users from little-green-man icon hangs system. live ssh from
other box dies then.
--
[fglrx] freezes upon Logout or Switch user [patch]
https://bugs.launchpad.net/bugs/118605
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in
Me, too!
I'm running an ATI HD 3450, with Xinerama enabled and apparently working
properly.
HOWEVER, any attempt to log off, or to change users by either the user
switcher or
little-green-man menu, result in black screens and hang. Hard reset is the only
way out: ctrl-alt-bksp doesn't fix it.
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/16368973/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16368974/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/16368975/Disassembly.txt
** Attachment
This, and several other gnome-ly failures, no longer occur on my system after
I installed recent updates over the weekend. So, that's good news, and we
can close this bug. Thanks!
My system still fails to initialize properly unless I run gnome in failsafe
mode: (the Application/Places/System...)
I think the yelp stuff is already on my box, even though the update procedure
recommended in the DebuggingProgramCrash wiki
wasn't able to find any -dbg or -dbgsym stuff.
The failing components are all running automagically under the gnome hood, so
I'm not sure how to poke it/them to
try to
Hi, James.
Per your request, I've submitted new bugs:
# 215751 gnome-settings-daemon
# 153610 system-config-printer
# 217758 gnome-power-manager
Hope this helps...
Robert
--
gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()
https://bugs.launchpad.net/bugs/210226
You
2008-04-10
Just upgraded a gazillion Hardy components. I was getting gnome-settings-daemon
failures
before (See bug# 210226), but this one looks new to my system.
I'll put a note in 210226 pointing here...
Bob
--
[apport] gnome-power-manager crashed with SIGSEGV in XInternAtom()
2008-04-10
Just installed a brazillion Hardy patches. Now seeing several sorts
of failures:
- repeated gnome-settings-daemon failures (attached)
- gnome-power-manager failure (See Bug #99505 attachment)
- applet.py failure (See Bug #153610).
Bob
--
gnome-settings-daemon crashed with SIGSEGV
Oops. I thought they got attached automagically. Lemme see
if I can find out where they went...
Bob
--
gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()
https://bugs.launchpad.net/bugs/210226
You received this bug notification because you are a member of Ubuntu
Desktop
Hi, James,
I looked around, hoping that there would be error log files in /tmp or
somewhere else obvious, but I don't see anything.
There were several logs generated and sent along, if I believe the
crash button stuff on the gnome menu bar...
If you can tell me where they were sent, I'll dig
Hi, James,
Here are a few crash logs from earlier today. Thanks for pointing me at
/var/crash!
** Attachment added:
_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash
http://launchpadlibrarian.net/13342069/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash
--
** Attachment added:
_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1001.crash
http://launchpadlibrarian.net/13342146/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1001.crash
--
gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()
Here's the dump from /var/crash/_usr_bin_gnome-power-manager.1000.crash
** Attachment added: _usr_bin_gnome-power-manager.1000.crash
http://launchpadlibrarian.net/13342158/_usr_bin_gnome-power-manager.1000.crash
--
[apport] gnome-power-manager crashed with SIGSEGV in XInternAtom()
Still fails as of 2008-04-06, with this day's upgrades.
[EMAIL PROTECTED]:~$ uname -a
Linux rattler 2.6.24-15-generic #1 SMP Fri Apr 4 03:10:59 UTC 2008 x86_64
GNU/Linux
I've observed the following:
1. Some upgrades disable the nvidia graphics driver, dropping me back into
680x480 land.
25 matches
Mail list logo
