Bug#462562: Option PreferredMode not per monitor
In a message of Sun, 27 Jan 2008 20:51:10 +0100, Brice Goglin writes: >I had a bug like this with earlier xserver-xorg-core. The BIOS >PreferredMode of the first output was overriding the xorg.conf >PreferredMode of the next output. Since VGA-0 is listed before DVI-0 >with the ati driver, there's a good chance it's related and that the fix >for my bug was actually incomplete. This does indeed sounds quite similar. If you have some pointers to where in the code I should look, I'll see if I can figure out what's going on. >> xrandr however, shows the + in the proper place for both monitors, so >> at least something is picking up the PreferredMode, it's just not properly >> applied when the initial mode is selected. >> > >Can you send the corresponding xrandr output? I will forward your report >on the upstream bugzilla. This is after I xrandr:d the monitors to their proper best resulutions: Screen 0: minimum 320 x 200, current 2960 x 1050, maximum 2960 x 1680 VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 352mm x 264mm 1280x1024 84.8*+ 85.0 75.0 60.0 2048x1536 60.0 1920x1440 60.0 1856x1392 60.0 1792x1344 60.0 1920x1200 72.8 60.0 1600x1200 75.0 75.0 70.0 65.0 60.0 59.9 1680x1050 60.0 1600x1024 60.0 1400x1050 85.3 74.8 70.0 60.0 1440x900 60.2 1280x960 85.0 60.0 1280x800 60.0 1152x864 85.1 84.8 75.0 74.8 1280x768 60.0 1152x768 54.8 1024x768 84.9 85.0 75.1 75.0 70.1 60.0 43.5 832x62474.6 800x60084.9 85.1 72.2 75.0 60.3 56.2 640x48085.0 84.6 75.0 72.8 72.8 75.0 66.7 60.0 60.0 59.9 720x40087.8 85.0 70.1 640x40085.1 640x35085.1 DVI-0 connected 1680x1050+1280+0 (normal left inverted right x axis y axis) 434mm x 270mm 1680x1050 60.0*+ 1280x1024 75.0 59.9 1280x960 59.9 1152x864 75.0 74.8 1024x768 75.1 60.0 832x62474.6 800x60075.0 60.3 56.2 640x48075.0 60.0 720x40070.1 S-video disconnected (normal left inverted right x axis y axis) /Anders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#462562: Option PreferredMode not per monitor
Processing commands for [EMAIL PROTECTED]: > forwarded 462562 https://bugs.freedesktop.org/show_bug.cgi?id=14267 Bug#462562: Option PreferredMode not per monitor Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=14267. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462562: Option PreferredMode not per monitor
forwarded 462562 https://bugs.freedesktop.org/show_bug.cgi?id=14267 thank you [EMAIL PROTECTED] wrote: > In a message of Sun, 27 Jan 2008 20:51:10 +0100, Brice Goglin writes: > >> I had a bug like this with earlier xserver-xorg-core. The BIOS >> PreferredMode of the first output was overriding the xorg.conf >> PreferredMode of the next output. Since VGA-0 is listed before DVI-0 >> with the ati driver, there's a good chance it's related and that the fix >> for my bug was actually incomplete. >> > > This does indeed sounds quite similar. If you have some pointers to where > in the code I should look, I'll see if I can figure out what's going on. > This should be in hw/xfree86/modes/xf86Crtc.c You might want to look at the commit that fixed my problem is http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commitdiff;h=feac0759522cbdc3e61ccfa373df735903c5cb27 > This is after I xrandr:d the monitors to their proper best resulutions: Thanks. I have forwarded the bug upstream at the URL above. Feel free to add any comment if you think it could help. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 462846 to nvidia-glx
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.13 > reassign 462846 nvidia-glx Bug#462846: compiz: Freeze for a moment when maximizing a Gnometerminal Bug reassigned from package `compiz' to `nvidia-glx'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#72265: Bug #72265: xterm: should shut messages off by default when -e argument given
2008/1/27 Németh Márton <[EMAIL PROTECTED]>: > Hi, > > could you please describe a little bit more what was this problem > about and what does "messages" mean? Messages in this case would be in reference to mesg(1), write(1) and talk(1). If no shell is being invoked for the terminal, receiving messages is not desirable as there's no good way to answer the request in that particular terminal, therefor messages should be turned off automatically. -- Paul Johnson [EMAIL PROTECTED]
Bug#462846: compiz: Freeze for a moment when maximizing a Gnometerminal
Package: compiz Version: 0.6.3~git20071222.061ff159-1 Severity: normal When I maximize a Gnome terminal window the machine basically freezes for about 1 second (sounds stops playing etc.) then it maximizes as normal. I use the wobbly plugin and gtk-window-decorator. By the way I applied a patch I made myself that enables "double-click menu button to close" for the gtk-window-decorator (that's why the version number differs). But it's exactly the same behaviour with an unpatched Compiz. And I have an Nvidia 8600GT using the latest Nvidia driver (169.07) The strange thing is this does not happen for any other applications (as far as I've seen). Thanks! //Marcus -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages compiz depends on: ii compiz- 0.6.3~git20071222.061ff159-malu1 OpenGL window and compositing mana ii compiz- 0.6.3~git20071222.061ff159-malu1 OpenGL window and compositing mana ii compiz- 0.6.3~git20071222.061ff159-malu1 OpenGL window and compositing mana ii compiz- 0.6.3~git20071222.061ff159-malu1 OpenGL window and compositing mana compiz recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462590: xserver-xorg: X-server sometimes stops with: mieqEnequeue: out-of-order valuator event; dropping.
reassign 462590 xserver-xorg-video-ati found 462590 1:6.7.197-1 severity 462590 important thank you spiralnebelverdreher wrote: > There is is similiar bug report from another user filed under number 462127. > (xserver-xorg-nv) > > X sometimes freezes the screen. No keyboard input is accepted (even not > Ctrl+Alt+Backspace or Ctrl+Alt+F2). Mouse ist still moving on the screen. > Events > like pressing the "lid button" or "power button" on the notebook are recorded > in the logfiles, but don't have any effect. Fan speed goes up until > maximum and gives the impression og high CPU load. > > Only a hard power-off is possible. > > Freezing may happen after only few minutes in X mode, or after 2 hours. > Runlevel 3 is no problem at all. > It sounds like a GPU lockup. Did this appear after upgrading xserver-xorg-video-ati to 6.7.197? Does it help if you add Option "BusType" "PCI" to the section Device of xorg.conf? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#462590: xserver-xorg: X-server sometimes stops with: mieqEnequeue: out-of-order valuator event; dropping.
Processing commands for [EMAIL PROTECTED]: > reassign 462590 xserver-xorg-video-ati Bug#462590: xserver-xorg: X-server sometimes stops with: mieqEnequeue: out-of-order valuator event; dropping. Bug reassigned from package `xserver-xorg' to `xserver-xorg-video-ati'. > found 462590 1:6.7.197-1 Bug#462590: xserver-xorg: X-server sometimes stops with: mieqEnequeue: out-of-order valuator event; dropping. Bug marked as found in version 1:6.7.197-1. > severity 462590 important Bug#462590: xserver-xorg: X-server sometimes stops with: mieqEnequeue: out-of-order valuator event; dropping. Severity set to `important' from `grave' > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462441: xserver-xorg: alt key gets stuck
Lionel Elie Mamane wrote: > Ah, I'll check next time it gets stuck. But anyway, note that > according to xev it is not pressed. What I mean is that if I press i, > I get something like > > KeyPress event, serial 31, synthetic NO, window 0x261, > root 0x64, subw 0x0, time 720975848, (99,127), root:(128,213), > state 0x0, keycode 31 (keysym 0x69, i), same_screen YES, > XLookupString gives 1 bytes: (69) "i" > XmbLookupString gives 1 bytes: (69) "i" > XFilterEvent returns: False > > In particular, the "state" is 0x0 and not... 0x80, if I remember well. > I think that's 0x8 instead of 0x80 but it doesn't matter, I got the idea :) >> Does reverting to the previous xserver-xorg-core (git20080105 or so, >> from snapshot.debian.net) fix this problem immediately? >> > > You mean, while it is in "alt stuck", I downgrade and I see if it > solves the problem without restarting any program? > No, I just meant "after downgrading and restarting X, does the obvious disappear?" By the way, can you try without any Xkb config in xorg.conf? (for instance with no xorg.conf at all). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462562: Option PreferredMode not per monitor
Anders Hammarquist wrote: > Package: xserver-xorg-video-ati > Version: 1:6.7.197-1 > Severity: normal > > I have dual monitor setup, one widescreen LCD and an older CRT. Trying to > get different default modes on the two screens appears impossible. The CRT > does apparently not specify a preferred mode in its EDID, and without any > setting in xorg.conf it runs at the same 1680x1050 resolution as the LCD. > > Trying to add an Option PreferredMode to its Monitor section in xorg.conf > resulted in the LCD also running at (the specified) 1280x1024. Adding an > Option PreferredMode to the LCD Monitor section had no effect (it still > ran at 1280x1024). > I had a bug like this with earlier xserver-xorg-core. The BIOS PreferredMode of the first output was overriding the xorg.conf PreferredMode of the next output. Since VGA-0 is listed before DVI-0 with the ati driver, there's a good chance it's related and that the fix for my bug was actually incomplete. > xrandr however, shows the + in the proper place for both monitors, so > at least something is picking up the PreferredMode, it's just not properly > applied when the initial mode is selected. > Can you send the corresponding xrandr output? I will forward your report on the upstream bugzilla. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462692: xorg: after rotation kde panel stuck in place
[EMAIL PROTECTED] wrote: > Package: xorg > Version: 1:7.2-5 > Severity: normal > > Not sure which package the bug belongs to, sorry. > > "xrandr -o left" used to work just fine, but now has developed some > annoying problems. My regular screen size is 1280x1024. After rotation > the KDE panel (which I keep on the bottom edge and autohide) now gets > stuck at the same distance from top edge as before rotation (its > bottom seems to be at 1024 from screen top). It does not autohide, > cannot be moved, and cannot be hidden even using its hide button > (unless it was specifically hidden using this button before rotation; > then just the button stays where it used to be). > > Furthermore, I've noticed that for any window, it is not possible to > get its bottom edge to go below this line (1024 from the top) by > resizing (dragging the bottom edge), and it is not possible to get the > window's top edge to go below this line by moving the window. It is, > however, possible to first move the window such that it straddles the > line and then resize it by dragging its top edge to the screen top. > Thus, full size windows are possible after all, but require this weird > workaround. > If the mouse can go below this 1024 line, and windows appear fine when you successfully move them there, this looks like a KDE bug to me. Can you try with another window manager? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455418: Icons still missing
This issue isn't fixed in the latest version. The problem doesn't seem to be python's version as stated in the changelog, but rather that Constant configuration mentioned by the submitter. After setting DataDir to /usr/share, all icons are shown. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages compizconfig-settings-manager depends on: ii python2.4.4-6An interactive high-level object-o ii python-compizconfig 0.6.0.1-2 Compizconfig bindings for python ii python-support0.7.6 automated rebuilding support for p Versions of packages compizconfig-settings-manager recommends: ii python-sexy 0.1.9-1python language bindings for libse -- no debconf information -- Saludos Gonzalo signature.asc Description: This is a digitally signed message part
Bug#462816: xkb-data: XF86WWW Key broken with cymotion layout
Package: xkb-data Version: 1.1~cvs.20080104.1-1 Severity: normal Hi, seems like one of the X11 upgrades changed to produce the key code 178 for the XF86WWW key. This maps to symbol I32 and thus using the cymotion layout I don't get my mapped action for that key anymore. The cymotion layout currently uses I02 for XF86WWW. I can't say which upgrade exactly broke things. Andreas -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.23 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462108: Incorrect " us" layout keyboard in automatic xorg.conf generation by debconf
Also with the layour defined, the bug is here, i have tried to set the layout to "es" and it appears " es" to the xorg.conf when is generated -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xorg-server: Changes to 'debian-unstable'
debian/changelog |6 +- debian/po/ja.po | 39 +-- 2 files changed, 18 insertions(+), 27 deletions(-) New commits: commit 8d2c79b8231ea63afe5525c5e8077281881f2831 Author: David Nusinow <[EMAIL PROTECTED]> Date: Sun Jan 27 11:21:07 2008 -0500 * Update Japanese translation from Hideki Yamane. closes: #462761 diff --git a/debian/changelog b/debian/changelog index 9a073a3..40243c5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,10 +1,14 @@ xorg-server (2:1.4.1~git20080118-2) UNRELEASED; urgency=low + [ Brice Goglin ] * Add 45_only_XF86_APM_CAPABILITY_CHANGED_for_video_change_acpi_events.diff to prevent XF86_APM_CAPABILITY_CHANGED from being issued for all ACPI events, thanks Sjoerd Simons, closes: #461463. - -- Brice Goglin <[EMAIL PROTECTED]> Fri, 18 Jan 2008 23:27:43 +0100 + [ David Nusinow ] + * Update Japanese translation from Hideki Yamane. closes: #462761 + + -- David Nusinow <[EMAIL PROTECTED]> Sun, 27 Jan 2008 11:18:41 -0500 xorg-server (2:1.4.1~git20080118-1) unstable; urgency=low diff --git a/debian/po/ja.po b/debian/po/ja.po index d3beb5e..0ca2faa 100644 --- a/debian/po/ja.po +++ b/debian/po/ja.po @@ -14,49 +14,35 @@ # msgid "" msgstr "" -"Project-Id-Version: xprint \n" +"Project-Id-Version: xorg-server 2:1.4.1~git20080118-1\n" "Report-Msgid-Bugs-To: [EMAIL PROTECTED]" "POT-Creation-Date: 2007-09-18 20:35+0200\n" -"PO-Revision-Date: 2005-03-26 16:42+0900\n" -"Last-Translator: Hideki Yamane <[EMAIL PROTECTED]>\n" +"PO-Revision-Date: 2008-01-27 19:52+0900\n" +"Last-Translator: Hideki Yamane (Debian-JP) <[EMAIL PROTECTED]>\n" "Language-Team: Japanese <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=EUC-JP\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "Default printer resolution" msgid "Default printer resolution:" -msgstr "�ǥե����ȤǤΥץ��󥿲����٤ˤĤ���" +msgstr "ããã©ã«ãã®ããªã³ã¿è§£å度:" #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "" -#| "By default Xprint assumes a printer resolution of 600dpi. This should be " -#| "fine for the majority of printers today." msgid "" "By default, Xprint assumes a printer resolution of 600 dpi. This should be " "well suited for the majority of printers." msgstr "" -"Xprint �ϡ��ǥե����ȤǤϥץ��󥿤β����٤� 600dpi �Ȥ��Ƥ��ޤ������ߤΥץ���" -"���Ǥϡ��ۤȤ��ɤ����ͤ��ɤ��Ǥ��礦��" +"ããã©ã«ãã§ã¯ãXprint ã¯ããªã³ã¿ã®è§£å度ã 600dpi ã¨ãã¦ãã¾ããã»ã¨ãã©ã®ããªã³" +"ã¿ã§ã¯ãã»ã¨ãã©ãã®å¤ã§è¯ãã§ãããã" #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "" -#| "On certain 1200dpi printers, however, the image might appear squashed in " -#| "the corner of the page, or it might be blown up too large on 300dpi " -#| "printers. If you are experiencing these kinds of printing problems, you " -#| "may want to set the default printer resolution to a more appropriate " -#| "value. See /usr/share/doc/xprint-common/README.printing-problems.gz for " -#| "more details." msgid "" "On certain 1200 dpi printers, however, the image might appear squashed in " "the corner of the page, or it might be blown up too large on 300 dpi " @@ -64,8 +50,9 @@ msgid "" "set the default printer resolution to a more appropriate value. See /usr/" "share/doc/xprint-common/README.printing-problems.gz for more details." msgstr "" -"��������1200dpi �����Υץ��󥿤Ǥϰ������줿�����ϥڡ����ζ��˵ͤ��ư�������" -"�Ƥ��ޤ��ޤ�����300dpi �Υץ��󥿤Ǥ��ç¤ï¿½ï¿½ï¿½Ê¤ê¤¹ï¿½ï¿½ï¿½Æ¤ï¿½ï¿½Þ¤ï¿½ï¿½Þ¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Í¤Ê°ï¿½ï¿½ï¿½" -"�����٤����������ø¤·¤¿ï¿½ï¿½ï¿½ç¡¢ï¿½×¥ï¿½ï¿½ó¥¿¤Î²ï¿½ï¿½ï¿½ï¿½Ù¤ï¿½ï¿½ï¿½ï¿½ï¿½Å¬ï¿½Ú¤ï¿½ï¿½Í¤ï¿½ï¿½Ñ¹ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ê¤ï¿½ï¿½ï¿½" -"���礦�����ܺ٤ˤĤ��Ƥϡ�/usr/share/doc/xprint-common/README.printing-" -"problems.gz �ò»²¾È¤ï¿½ï¿½Æ¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½" +"ãããã1200dpi åºå®ã®ããªã³ã¿ã§ã¯å°å·ãããç»åã¯ãã¼ã¸ã®é ã«è©°ãã¦å°å·ãã" +"ã¦ãã¾ãã¾ããã300dpi ã®ããªã³ã¿ã§ã¯å¤§ãããªãããã¦ãã¾ãã¾ãããã®æ§ãªå°å·" +"æã®åé¡ã«ééããå ´åãããªã³ã¿ã®è§£å度ãããé©åãªå¤ã«å¤æ´ããããªãã§ãããã" +"詳細ã«ã¤ãã¦ã¯ã/usr/share/doc/xprint-common/README.printing-problems.gz " +"ãåç §ãã¦ãã ããã" + -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#462761: xorg-server: [INTL:ja] Update po-debconf template translation (ja.po)
Processing commands for [EMAIL PROTECTED]: > tag 462761 +pending Bug#462761: xorg-server: [INTL:ja] Update po-debconf template translation (ja.po) Tags were: l10n patch Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462761: xorg-server: [INTL:ja] Update po-debconf template translation (ja.po)
tag 462761 +pending thanks On Sun, Jan 27, 2008 at 08:20:09PM +0900, Hideki Yamane (Debian-JP) wrote: > Package: xorg-server > Version: 2:1.4.1~git20080118-1 > Severity: wishlist > Tags: patch l10n > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dear xorg-server maintainers, > > Here's updated Japanese po-debconf template (ja.po) file. > Could you apply it, please? Done. It'll be in the next upload of the xserver. Thank you! - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462761: xorg-server: [INTL:ja] Update po-debconf template translation (ja.po)
Package: xorg-server Version: 2:1.4.1~git20080118-1 Severity: wishlist Tags: patch l10n -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear xorg-server maintainers, Here's updated Japanese po-debconf template (ja.po) file. Could you apply it, please? - -- Regards, Hideki Yamane henrich @ debian.or.jp/samba.gr.jp/iijmio-mail.jp -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHnGjoIu0hy8THJksRAsM+AJ9Cyn4hOG4/zvw6gCuztgg2FX0NRQCglIRC k0pUlPxddSuN99d+MtCGvU4= =4276 -END PGP SIGNATURE- # #Translators, if you are not familiar with the PO format, gettext #documentation is worth reading, especially sections dedicated to #this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # #Some information specific to po-debconf are available at #/usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans # #Developers do not need to manually edit POT or PO files. # # msgid "" msgstr "" "Project-Id-Version: xorg-server 2:1.4.1~git20080118-1\n" "Report-Msgid-Bugs-To: [EMAIL PROTECTED]" "POT-Creation-Date: 2007-09-18 20:35+0200\n" "PO-Revision-Date: 2008-01-27 19:52+0900\n" "Last-Translator: Hideki Yamane (Debian-JP) <[EMAIL PROTECTED]>\n" "Language-Team: Japanese <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Description #: ../xprint-common.templates:2001 msgid "Default printer resolution:" msgstr "デフォルトのプリンタ解像度:" #. Type: string #. Description #: ../xprint-common.templates:2001 msgid "" "By default, Xprint assumes a printer resolution of 600 dpi. This should be " "well suited for the majority of printers." msgstr "" "デフォルトでは、Xprint はプリンタの解像度を 600dpi としています。ほとんどのプリン" "タでは、ほとんどこの値で良いでしょう。" #. Type: string #. Description #: ../xprint-common.templates:2001 msgid "" "On certain 1200 dpi printers, however, the image might appear squashed in " "the corner of the page, or it might be blown up too large on 300 dpi " "printers. If you are experiencing such printing problems, you may want to " "set the default printer resolution to a more appropriate value. See /usr/" "share/doc/xprint-common/README.printing-problems.gz for more details." msgstr "" "しかし、1200dpi 固定のプリンタでは印刷された画像はページの隅に詰めて印刷され" "てしまいますし、300dpi のプリンタでは大きくなりすぎてしまいます。この様な印刷" "時の問題に遭遇した場合、プリンタの解像度をより適切な値に変更したくなるでしょう。" "詳細については、/usr/share/doc/xprint-common/README.printing-problems.gz " "を参照してください。"
Bug#72265: Bug #72265: xterm: should shut messages off by default when -e argument given
Hi, could you please describe a little bit more what was this problem about and what does "messages" mean? Márton Németh
Processed: xterm: mouse pointer during typing
Processing commands for [EMAIL PROTECTED]: > severity 460545 normal Bug#460545: xterm: Provide a way to NOT hide the mouse pointer Severity set to `normal' from `minor' > merge 461019 460545 Bug#460545: xterm: Provide a way to NOT hide the mouse pointer Bug#461019: pointer hidden during typing is not quite (hidden) Merged 460545 461019. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462127: xserver-xorg: X freezes after some time with "mieqEnequeue: out-of-order valuatorevent; dropping"
Citando Brice Goglin : > Emmanuel Hainry wrote: >> After downgrading xserver-xorg-core, I still experienced this freezing. >> I now have also downgraded xserver-xorg-video-nv and so far it has been >> good. >> >> I remarked during the latest freeze (and hopefully last) that the Xorg >> proess was consuming 99% cpu, killing it and restarting it from another >> machine brought it back to freeze immediately. >> > Ok, thanks for testing. > > Which exact xserver-xorg-video-nv version fixed the problem? 2.1.5-1? > Did you reupgrade xserver-xorg-core to the latest since then? > That was 2.1.5-1 yes, but it finally froze too. I have decided to downgrade/revert to the version I had before experiencing this bug, which is xserver-xorg-core 2:1.4.1~git20071119-1 2:1.4 and xserver-xorg-video-nv 1:2.1.6-1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: xterm: mouse pointer during typing
Processing commands for [EMAIL PROTECTED]: > tags 461019 fixed-upstream Bug#461019: pointer hidden during typing is not quite (hidden) Tags were: patch Tags added: fixed-upstream > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: xterm: clearing TAB starting from column 320 or later can cause segmentation fault
Processing commands for [EMAIL PROTECTED]: > retitle 462621 xterm: setting TAB starting from column 320 or later can cause > segmentation fault Bug#462621: xterm: clearing TAB starting from column 320 or later can cause segmentation fault Changed Bug title to `xterm: setting TAB starting from column 320 or later can cause segmentation fault' from `xterm: clearing TAB starting from column 320 or later can cause segmentation fault'. > tags 462621 fixed-upstream Bug#462621: xterm: setting TAB starting from column 320 or later can cause segmentation fault There were no tags set. Tags added: fixed-upstream > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
