xorg-server_1.3.0.0.dfsg-12lenny2_i386.changes ACCEPTED
Mapping testing-security to testing-proposed-updates. Accepted: xdmx-tools_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xdmx-tools_1.3.0.0.dfsg-12lenny2_i386.deb xdmx_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xdmx_1.3.0.0.dfsg-12lenny2_i386.deb xnest_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xnest_1.3.0.0.dfsg-12lenny2_i386.deb xorg-server_1.3.0.0.dfsg-12lenny2.diff.gz to pool/main/x/xorg-server/xorg-server_1.3.0.0.dfsg-12lenny2.diff.gz xorg-server_1.3.0.0.dfsg-12lenny2.dsc to pool/main/x/xorg-server/xorg-server_1.3.0.0.dfsg-12lenny2.dsc xprint-common_1.3.0.0.dfsg-12lenny2_all.deb to pool/main/x/xorg-server/xprint-common_1.3.0.0.dfsg-12lenny2_all.deb xprint_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xprint_1.3.0.0.dfsg-12lenny2_i386.deb xserver-xephyr_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xserver-xephyr_1.3.0.0.dfsg-12lenny2_i386.deb xserver-xorg-core-dbg_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xserver-xorg-core-dbg_1.3.0.0.dfsg-12lenny2_i386.deb xserver-xorg-core_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xserver-xorg-core_1.3.0.0.dfsg-12lenny2_i386.deb xserver-xorg-dev_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xserver-xorg-dev_1.3.0.0.dfsg-12lenny2_i386.deb xvfb_1.3.0.0.dfsg-12lenny2_i386.deb to pool/main/x/xorg-server/xvfb_1.3.0.0.dfsg-12lenny2_i386.deb Override entries for your package: xdmx-tools_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 xdmx_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 xnest_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 xorg-server_1.3.0.0.dfsg-12lenny2.dsc - source x11 xprint-common_1.3.0.0.dfsg-12lenny2_all.deb - optional x11 xprint_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 xserver-xephyr_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 xserver-xorg-core-dbg_1.3.0.0.dfsg-12lenny2_i386.deb - extra x11 xserver-xorg-core_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 xserver-xorg-dev_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 xvfb_1.3.0.0.dfsg-12lenny2_i386.deb - optional x11 Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of xorg-server_1.3.0.0.dfsg-12lenny2_i386.changes
xorg-server_1.3.0.0.dfsg-12lenny2_i386.changes uploaded successfully to localhost along with the files: xorg-server_1.3.0.0.dfsg-12lenny2.dsc xorg-server_1.3.0.0.dfsg-12lenny2.diff.gz xprint-common_1.3.0.0.dfsg-12lenny2_all.deb xserver-xorg-core_1.3.0.0.dfsg-12lenny2_i386.deb xserver-xorg-dev_1.3.0.0.dfsg-12lenny2_i386.deb xdmx_1.3.0.0.dfsg-12lenny2_i386.deb xdmx-tools_1.3.0.0.dfsg-12lenny2_i386.deb xnest_1.3.0.0.dfsg-12lenny2_i386.deb xvfb_1.3.0.0.dfsg-12lenny2_i386.deb xserver-xephyr_1.3.0.0.dfsg-12lenny2_i386.deb xprint_1.3.0.0.dfsg-12lenny2_i386.deb xserver-xorg-core-dbg_1.3.0.0.dfsg-12lenny2_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libxfont override disparity
On 11267 March 1977, Julien Cristau wrote: >> libxfont-dev_1.3.1-2_i386.deb: package says section is libdevel, override >> says x11. >> libxfont1-dbg_1.3.1-2_i386.deb: package says section is libdevel, override >> says x11. >> libxfont1_1.3.1-2_i386.deb: package says section is libs, override says x11. > I think the package is right here, please change the override to match. Done. -- bye Joerg If the autobuilder tells me that my package failed to build from source, it's probably doing that on some obscure architecture I don't have access to. pgpt8lURwNyUj.pgp Description: PGP signature
Bug#459803: 1:6.7.198~git20080117.6bd510a2-1 correctly detects monitors
I can confirm that 1:6.7.198~git20080117.6bd510a2-1, from experimental, correctly detects a connected monitor on the LVDS output, which allows normal operation of the driver to occur. (The previous version detected no monitors and thus errored out) Matthew W. S. Bell signature.asc Description: This is a digitally signed message part
xorg-server: Changes to 'ubuntu'
ChangeLog| 624 ++ Xext/EVI.c | 15 Xext/cup.c | 3 Xext/sampleEVI.c | 29 Xext/security.c | 4 Xext/shm.c | 50 Xi/chgfctl.c | 7 Xi/chgkmap.c | 13 Xi/chgprop.c | 10 Xi/grabdev.c | 12 Xi/grabdevb.c| 10 Xi/grabdevk.c| 9 Xi/selectev.c| 11 Xi/sendexev.c| 14 debian/changelog | 102 + debian/control | 2 debian/patches/105_reduce_wakeups_from_smart_scheduler.diff | 146 ++ debian/patches/138_fedora_xserver-1.3.0-default-dpi.patch| 12 debian/patches/14_default_screen_section.diff| 16 debian/patches/40_default_dpi_96.patch | 21 debian/patches/42_dont_break_grab_and_focus_for_window_when_redirecting.diff | 35 debian/patches/series| 4 dix/dixfonts.c | 7 hw/kdrive/ephyr/ephyr.c | 1 hw/xfree86/common/xf86MiscExt.c | 4 os/io.c | 2 xkb/xkbUtils.c | 1 27 files changed, 1062 insertions(+), 102 deletions(-) New commits: commit 7bd58d2b4cae24d25d23f6c360622bca835319aa Author: Timo Aaltonen <[EMAIL PROTECTED]> Date: Sat Jan 19 20:38:50 2008 +0200 105_reduce_wakeups_from_smart_scheduler.diff: Patch from upstream to reduce wakeups and improve battery life. Remove the DPI patch for real this time, conflicts with the upstream commit that was pulled. diff --git a/debian/changelog b/debian/changelog index cac7b6c..4993dd1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +xorg-server (2:1.4.1~git20080118-1ubuntu2) hardy; urgency=low + + * Remove the DPI patch for real this time, conflicts with the upstream +commit that was pulled. + * 105_reduce_wakeups_from_smart_scheduler.diff: +Patch from upstream to reduce wakeups and improve battery life. + + -- Timo Aaltonen <[EMAIL PROTECTED]> Sat, 19 Jan 2008 20:26:41 +0200 + xorg-server (2:1.4.1~git20080118-1ubuntu1) hardy; urgency=low * Merge with Debian unstable, remaining changes: diff --git a/debian/patches/105_reduce_wakeups_from_smart_scheduler.diff b/debian/patches/105_reduce_wakeups_from_smart_scheduler.diff new file mode 100644 index 000..aa9a04d --- /dev/null +++ b/debian/patches/105_reduce_wakeups_from_smart_scheduler.diff @@ -0,0 +1,146 @@ +From: Arjan van de Ven <[EMAIL PROTECTED]> +Date: Sun, 28 Oct 2007 08:37:52 + (+0100) +Subject: reduce wakeups from smart scheduler +X-Git-Url: http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commitdiff;h=2338d5c9914e2a43c3a4f7ee0f4355ad0a1ad9e7 + +reduce wakeups from smart scheduler + +The smart scheduler itimer currently always fires after each request +(which in turn causes the CPU to wake out of idle, burning precious +power). Rather than doing this, just stop the timer before going into +the select() portion of the WaitFor loop. It's a cheap system call, and +it will only get called if there's no more commands batched up from the +active fd. + +This change also allows some of the functions to be simplified; +setitimer() will only fail if it's passed invalid data, and we don't do +that... so make it void and remove all the conditional code that deals +with failure. + +The change also allows us to remove a few variables that were used for +housekeeping between the signal handler and the main loop. + +Signed-off-by: Keith Packard <[EMAIL PROTECTED]> +--- + +--- a/include/dixstruct.h b/include/dixstruct.h +@@ -150,11 +150,9 @@ extern long SmartScheduleTime; + extern long SmartScheduleInterval; + extern long SmartScheduleSlice; + extern long SmartScheduleMaxSlice; +-exte
Re: architecture: all but ... (please add armel to architecture list)
Thansk all for the comments. Since this is good info, I made a wiki page http://wiki.debian.org/PackageArchitectureAlmostAny based on the discussion here. On Sat, Jan 19, 2008 at 05:35:10PM +0100, Luk Claes wrote: > > > 4) wanna-build state dep-wait > > > > One option would be to put gsynaptics to dep-wait on > > xfree86-driver-synaptics. Thus buildd would not try to build > > it unless xfree86-driver-synaptics becomes some day available > > on s390. While X on s390 might seem unlikely, stranger things > > have happened. > > Perfectly reasonable IMHO. Is this what the conclusion is? > > 5) packages-arch-specific [2] > > > > p-a-s makes package never appear in wanna-build. It will > > never by tried to be built on architectures defined there. > > It' maintained by three people who manually update it. > > Any technical advantage this approarch has over n-f-u > > is completly negated by the fact the people who are supposed > > to update it ignore my requests to update it... > > It is also not being built on other suites then the one were it > sometimes is meant not to build anymore... > > Some updates go quickly, others take time, I guess that's because there > are only a few persons who can update it... > > > 6) type-handling > > > > This is a kludge that has been written to workaround problems > > in rest of the architecture selection system. In practice it > > seems to work very well. > > > > Osamu, for short term, I suggest using type-handling to generate > > architecture strings. > > I guess one can see this as a dynamic case of 1) and 2)? Is this alternative generic solution? I am a bit confused. If people finalize this on wiki page, I will appreciate. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461580: xserver-xorg-video-ati: Recent upgrade causes machine crash
Brian DeRocher wrote: > Package: xserver-xorg-video-ati > Version: 1:6.7.197-1 > Severity: important > > This bug report is similar to my previous one (#457563). After upgrading kdm > starts and freezes the system. After removing kdm from /etc/rc2.d, i tried > to > start it up manually. This also fails. I tried startx and that fails too. > > I can ping this machine, but i can't ssh to it. I can't switch to a virtual > console. > > I did not test the resolution in #457563. At that time i downgraded to a > previous > version. Today is the first time i upgraded again. > Well, #457563 is not fixed in 6.7.197 but in a more recent snapshot from experimental. So you might just be reporting the same bug again. Please try xserver-xorg-video-ati from experimental. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461580: xserver-xorg-video-ati: Recent upgrade causes machine crash
Package: xserver-xorg-video-ati Version: 1:6.7.197-1 Severity: important This bug report is similar to my previous one (#457563). After upgrading kdm starts and freezes the system. After removing kdm from /etc/rc2.d, i tried to start it up manually. This also fails. I tried startx and that fails too. I can ping this machine, but i can't ssh to it. I can't switch to a virtual console. I did not test the resolution in #457563. At that time i downgraded to a previous version. Today is the first time i upgraded again. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2007-08-04 17:16 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1969272 2008-01-18 20:00 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :f0:10.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1968 2007-08-27 16:31 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "ATI Technologies Inc RV350 AP [Radeon 9600]" Driver "ati" BusID "PCI:240:16:0" Option "UseFBDev" "true" EndSection Section "Monitor" Identifier "ViewSonic PS" Option "DPMS" HorizSync 30-97 VertRefresh 50-180 EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc RV350 AP [Radeon 9600]" Monitor "ViewSonic PS" DefaultDepth24 SubSection "Display" # Modes "1920x1440" "1920x1200" "1856x1392" "1792x1344" "1680x1050" "1600x1200" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" Modes "1400x1050" "1280x1024" "1280x960" "1280x854" "1280x800" "1280x768" "1200x800" "1152x864" "1152x768" "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 2191 2007-12-23 08:08 /var/log/Xorg.1.log -rw-r--r-- 1 root root 31192 2008-01-19 11:49 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080118-1) Current Operating System: Linux three 2.6.22-2-powerpc64 #1 SMP Thu Aug 30 21:51:55 CEST 2007 ppc64 Build Date: 18 January 2008 11:59:02PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xo
xorg-server: Changes to 'refs/tags/xorg-server-2_1.3.0.0.dfsg-12lenny2'
Tag 'xorg-server-2_1.3.0.0.dfsg-12lenny2' created by Julien Cristau <[EMAIL PROTECTED]> at 2008-01-19 01:53 + Tagging upload of xorg-server 2:1.3.0.0.dfsg-12lenny2 to testing-security. Changes since xorg-server-2_1.3.0.0.dfsg-12lenny1: Julien Cristau (4): Security update, fixes multiple vulnerabilities Prepare changelog for upload. Fix wrong bug number.. Update patch for CVE-2007-6429 to fixed version. --- debian/changelog | 13 + debian/patches/52_CVE-2007-5760.diff | 15 + debian/patches/53_CVE-2007-5958.diff | 22 ++ debian/patches/54_CVE-2008-0006.diff | 18 + debian/patches/55_CVE-2007-6429_EVI.diff | 96 ++ debian/patches/56_CVE-2007-6429_MIT-SHM.diff | 106 +++ debian/patches/57_CVE-2007-6427.diff | 244 +++ debian/patches/58_CVE-2007-6428.diff | 14 + debian/patches/series|7 9 files changed, 535 insertions(+) --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: architecture: all but ... (please add armel to architecture list)
> Now we have several overlapping mechanisms to avoid building packages > on selected architectures. Worse, we don't have any proper instructions > explaining which mechaism to use. > > 1) Architecture: list in package source > > This is what gsynaptics does now. wanna-build will still offer > the package to build (why?), but sbuild will fail it immeadetly. > Annoyingly maintainers can't define negations (!s390). It's still offered for building as it might only be temporary relevant and buildd maintainers and/or porters might want to look into it. sbuild will fail as that's what one expects it to do without changing the Arch-field. > 2) Architecture: list on binary section > > This is used on packages that build some binary on all archs and > some on only selected ones. This is very usefull unless misused. And probably should be used more often for particular kind of packages... > 3) Wanna-build state not-for-us. > > buildd maintainer sets this. From wanna-build docs[1]: > > there's need for a way to list packages for which even an attempt to > build isn't required. The first solution to this problem was > not-for-us; however, as that is difficult to maintain, not-for-us is > deprecated nowadays; autobuilder maintainers should use > packages-arch-specific instead. > > From my armel short buildd maintainance experience, I can't see why > n-f-u is more difficult to maintain. neither n-f-u or p-a-s have > any connection to what package maintainer defines in Architecture: > strings. You can't document why it's in n-f-u AFAICS and one can't easily have a listing of packages per issue probably. > 4) wanna-build state dep-wait > > One option would be to put gsynaptics to dep-wait on > xfree86-driver-synaptics. Thus buildd would not try to build > it unless xfree86-driver-synaptics becomes some day available > on s390. While X on s390 might seem unlikely, stranger things > have happened. Perfectly reasonable IMHO. > 5) packages-arch-specific [2] > > p-a-s makes package never appear in wanna-build. It will > never by tried to be built on architectures defined there. > It' maintained by three people who manually update it. > Any technical advantage this approarch has over n-f-u > is completly negated by the fact the people who are supposed > to update it ignore my requests to update it... It is also not being built on other suites then the one were it sometimes is meant not to build anymore... Some updates go quickly, others take time, I guess that's because there are only a few persons who can update it... > 6) type-handling > > This is a kludge that has been written to workaround problems > in rest of the architecture selection system. In practice it > seems to work very well. > > Osamu, for short term, I suggest using type-handling to generate > architecture strings. I guess one can see this as a dynamic case of 1) and 2)? Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: architecture: all but ... (please add armel to architecture list)
Osamu Aoki wrote: > Hi Luk, > > I wish things were such simple. Here is the root cause etc. > > On Fri, Jan 18, 2008 at 06:58:40PM +0100, Luk Claes wrote: >> Osamu Aoki wrote: >>> Hi, >>> >>> Dear porter, please enlighten me. >>> >>> On Wed, Jan 16, 2008 at 02:26:20PM +, Martin Guy wrote: Package: gsynaptics Version: 0.9.7-3 Severity: wishlist User: [EMAIL PROTECTED] Usertags: eabi Please add "armel" to the architecture list in debian/control (or make it "any") (A new ARM port should be going into lenny to replace the old one in lenny+1; see wiki.debian.org/ArmEabiPort) >>> Since S360 build failure caused me to chose explicit arch list, I >>> think I have to add eabi to fix this bug. I wish if we can do >> s/s360/s390/ > > Yes. > >> What build failure do you mean? 0.9.7-1+b1 as well as 0.9.7-1+b2 built >> fine and 0.9.7-2 didn't have s390 listed anymore as a supported >> architecture... > > That is intentional because of Bug #397917. http://bugs.debian.org/397917 > > What I meant by "build failure" was that an uninstallable package was > created, I think. Ok, though it was still you that chose to go for option 3 which means you have to change the Arch-line every time a new supported arch is known... Changing the synaptics related packages is not going to happen as s390 has no support for it... So you can either still go for option 3 or change to option 4 now by changing it to Arch:any. As the binaries are already removed and it won't be built on s390 anymore anyway, this might be the best thing to do... Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: architecture: all but ... (please add armel to architecture list)
block 461088 by 461551 thanks On Sat, Jan 19, 2008 at 09:58:08PM +0900, Osamu Aoki wrote: > > gsynaptics lists s390 as supported (Architecture: any) but > > xserver-xorg-input-synaptics is not available. This leads to > > uninstallable binary packages. > > Bastian > With serious tag and him being s390 buildd maintainer, I took situation > as that the s390 buildd maintainer (Bastian Blank) will not build > xserver-xorg-input-synaptics with some good reason thus the only way for > me is not to build gsynaptics. For me, it looked like that gsynaptic > being so much special as an input device aimed for consumer oriented > system hardware, s390 system being data server oriented may have some > hardware issues to support such thing. (You know that under the normal > situation, people access s390 system running X-client program from > external X-server. Not the other way.) Yes, it is clearly reasonable to avoid building gsynaptics on s390. However, it should not come with the expense of getting it not built on architectures where it could potentially be usefull. > The xserver-xorg-input-synaptics comes from source package > xfree86-driver-synaptics which has Architecture: alpha amd64 arm hppa > i386 ia64 m68k mips mipsel powerpc sparc > (See > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xfree86-driver-synaptics) > I do not see armel here either. So fixing my package only will cause the same > issue and response from the s390 buildd maintainer. I filed a bug against this, and made it blocker of this bug. I really don't like packages setting hardcoded lists of architectures. Now we have several overlapping mechanisms to avoid building packages on selected architectures. Worse, we don't have any proper instructions explaining which mechaism to use. 1) Architecture: list in package source This is what gsynaptics does now. wanna-build will still offer the package to build (why?), but sbuild will fail it immeadetly. Annoyingly maintainers can't define negations (!s390). 2) Architecture: list on binary section This is used on packages that build some binary on all archs and some on only selected ones. This is very usefull unless misused. 3) Wanna-build state not-for-us. buildd maintainer sets this. From wanna-build docs[1]: there's need for a way to list packages for which even an attempt to build isn't required. The first solution to this problem was not-for-us; however, as that is difficult to maintain, not-for-us is deprecated nowadays; autobuilder maintainers should use packages-arch-specific instead. From my armel short buildd maintainance experience, I can't see why n-f-u is more difficult to maintain. neither n-f-u or p-a-s have any connection to what package maintainer defines in Architecture: strings. 4) wanna-build state dep-wait One option would be to put gsynaptics to dep-wait on xfree86-driver-synaptics. Thus buildd would not try to build it unless xfree86-driver-synaptics becomes some day available on s390. While X on s390 might seem unlikely, stranger things have happened. 5) packages-arch-specific [2] p-a-s makes package never appear in wanna-build. It will never by tried to be built on architectures defined there. It' maintained by three people who manually update it. Any technical advantage this approarch has over n-f-u is completly negated by the fact the people who are supposed to update it ignore my requests to update it... Since it's manually updated, it has gathered a lot of cruft. %xfree86-driver-synaptics: !s390 # Needs %xserver-xfree86 For some unknown reason, this was not a acceptable solution for gsynaptics/ksynaptics, but was for xfree86-driver-synaptics. 6) type-handling This is a kludge that has been written to workaround problems in rest of the architecture selection system. In practice it seems to work very well. Osamu, for short term, I suggest using type-handling to generate architecture strings. [1] http://www.debian.org/devel/buildd/wanna-build-states [1] http://cvs.debian.org/srcdep/Packages-arch-specific?rev=1.731&root=dak&view=markup -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461551: please add armeb and armel to architecture list
Package: xserver-xorg-input-synaptics Version: 0.14.7~git20070706-2 Severity: wishlist User: [EMAIL PROTECTED] Usertags: eabi Hi, please add armeb and armel to the architecture list. -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: architecture: all but ... (please add armel to architecture list)
Hi Luk, I wish things were such simple. Here is the root cause etc. On Fri, Jan 18, 2008 at 06:58:40PM +0100, Luk Claes wrote: > Osamu Aoki wrote: > > Hi, > > > > Dear porter, please enlighten me. > > > > On Wed, Jan 16, 2008 at 02:26:20PM +, Martin Guy wrote: > >> Package: gsynaptics > >> Version: 0.9.7-3 > >> Severity: wishlist > >> User: [EMAIL PROTECTED] > >> Usertags: eabi > >> > >> Please add "armel" to the architecture list in debian/control (or make it > >> "any") > >> > >> (A new ARM port should be going into lenny to replace the old one in > >> lenny+1; > >> see wiki.debian.org/ArmEabiPort) > > > > Since S360 build failure caused me to chose explicit arch list, I > > think I have to add eabi to fix this bug. I wish if we can do > > s/s360/s390/ Yes. > What build failure do you mean? 0.9.7-1+b1 as well as 0.9.7-1+b2 built > fine and 0.9.7-2 didn't have s390 listed anymore as a supported > architecture... That is intentional because of Bug #397917. http://bugs.debian.org/397917 What I meant by "build failure" was that an uninstallable package was created, I think. > Why would you remove the support for an architecture when it doesn't > build anymore, shouldn't you rather fix it to build on that architecture > again in that case? From looking at the binNMU version numbers, the > build failure was only temporary anyway... I hoped if it were so. > The best thing you can do is mark it Arch: any again and inform the s390 > buildd maintainer (Bastian Blank) about that unless you have a valid > reason not to build it on s390 anymore? Well, he is the one who told me as follows in the bug report for Bug #397917: > Package: gsynaptics > Version: 0.9.7-1 > Severity: serious > > gsynaptics lists s390 as supported (Architecture: any) but > xserver-xorg-input-synaptics is not available. This leads to > uninstallable binary packages. > > Bastian With serious tag and him being s390 buildd maintainer, I took situation as that the s390 buildd maintainer (Bastian Blank) will not build xserver-xorg-input-synaptics with some good reason thus the only way for me is not to build gsynaptics. For me, it looked like that gsynaptic being so much special as an input device aimed for consumer oriented system hardware, s390 system being data server oriented may have some hardware issues to support such thing. (You know that under the normal situation, people access s390 system running X-client program from external X-server. Not the other way.) The xserver-xorg-input-synaptics comes from source package xfree86-driver-synaptics which has Architecture: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc sparc (See http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xfree86-driver-synaptics) So the root cause of trouble is the missing xserver-xorg-input-synapticis for s390 because the xfree86-driver-synaptics maintainer chose to use an explicit architecture list without s390 for some good reason. I do not see armel here either. So fixing my package only will cause the same issue and response from the s390 buildd maintainer. OK, let me dig more to get wider issue. I know it is funny but I have no such issue for tpconfig (3.1.3-9) although I never know if it works for s390. As I see qsynaptics and ksynaptics suffer the same problem due to missing xserver-xorg-input-synaptics. Another interesting hint was: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=xfree86-driver-synaptics They do not even support powerpc per bug #334733 due to the kernel issue. (Strange to see it is build for that atchitecture, though.) I do not know the issue is s390 kernel code or not, but before asking gsynaptics, qsynaptics and ksynaptics, you should convince xfree86-driver-synaptics package maintainer first. Maybe before that, you may need to fix kernel issues. Osamu PS: CCing people involved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461410: New packages for etch?
Sven Pilz wrote: > Hi, > > will there be new packages for etch? > Sure, xorg-server_1.1.1-21etch3 is being processed right now. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of xorg-server_1.1.1-21etch3_i386.changes
xorg-server_1.1.1-21etch3_i386.changes uploaded successfully to localhost along with the files: xorg-server_1.1.1-21etch3.dsc xorg-server_1.1.1-21etch3.diff.gz xserver-xorg-core_1.1.1-21etch3_i386.deb xserver-xorg-dev_1.1.1-21etch3_i386.deb xdmx_1.1.1-21etch3_i386.deb xdmx-tools_1.1.1-21etch3_i386.deb xnest_1.1.1-21etch3_i386.deb xvfb_1.1.1-21etch3_i386.deb xserver-xephyr_1.1.1-21etch3_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461410: New packages for etch?
Hi, will there be new packages for etch? Thanks Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461541: xterm-231-1 mouse pointer partial pixel issue
Package: xterm Version: 231-1 After a dist-upgrade this morning (using Debian-testing/Lenny) I noticed the semantics of how the cursor is displayed has changed for the worse. Before: When I was _began_ typing in an xterm, the mouse cursor would disappear and stay that way until I moved the mouse again. Now: For instance when I am typing this e-mail I see the cursor or pieces of it show up and then disappear (while) I am typing, so I see 20% or 30% of it show up and go away, show up and go away, it is quite irritating! I'd prefer the old behavior if possible but for now it looks like I will just have to set it to be on permanently until we figure out what happened. I also tried the -ah and +ah switches but they did not help. Any ideas/what patch munged the cursor/what is causing this? Thanks, Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Secure-testing-team] xorg-server update for lenny
Hi Julien, * Julien Cristau <[EMAIL PROTECTED]> [2008-01-19 13:07]: > as xorg-server 1.4 isn't ready to migrate, and won't be for some more > time, I prepared an updated package for testing-security. Oh thanks, that's really nice. > It fixes CVE-2007-5760, CVE-2007-5958, CVE-2007-6427, CVE-2007-6428, > CVE-2007-6429 and CVE-2008-0006, and will be on its way to klecker in a > few minutes. > I'm travelling right now, so in case something comes up please contact > [EMAIL PROTECTED] Thank you! I am going to check & release this as soon as all buildds pushed their packages to klecker. Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpzPajhHmH8L.pgp Description: PGP signature
Processed: reassign 461489 to xkb-data, found 461489 in 0.9-4
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.13 > reassign 461489 xkb-data Bug#461489: sense of laptop 'fn' key reversed on gateway MX6453 Bug reassigned from package `xorg' to `xkb-data'. > found 461489 0.9-4 Bug#461489: sense of laptop 'fn' key reversed on gateway MX6453 Bug marked as found in version 0.9-4. > 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#461489: sense of laptop 'fn' key reversed on gateway MX6453
Package: xkbd-data Version: 0.9-4 I have a Gateway MX6453 laptop, and I'm having a problem with the keyboard. I believe that this is an xkbd-data 0.9-4 bug. I am using debian 'etch' or stable, and my system is 'up to date' according to the update tool. There's a 'fn' key in the lower left corner which is supposed to turn on special meanings for some of the keys: 7,8,9,U,I,O,J,K,L,M, in particular, map to digits 7,8,9,4,5,6,1,2,3,0 in an effort to mimic a numeric keypad. There are several other keys that should acquire special meanings when 'fn' is depressed, mostly having to do with brightness, loudness, screen contrast, multimedia settings, and internet shortcuts. My problem is that the keyboard behaves like the 'fn' key is pressed, _all_the_time_, unless it is actually pressed. For example, I have to push and hold the 'fn' key and then press 'l' in order to get a lower-case 'l' instead of a '3'. Mysterious extra information: On a reboot, it doesn't seem to affect the initial login and password (this is with X running, but before any user has logged in). Once a user session has started, however, the keyboard bug pops up immediately and doesn't go away even if that user logs out. (subsequent logins are affected). Right now I have two workarounds: if I plug in a standard keyboard with the USB interface, it is not affected by this craziness. (Note the Gateway MX6453 has no PS/2 connections). Second, it doesn't happen unless I start X, so I can still work (to some extent, most of my regular applications don't run without X) in runlevel 3. If I can be of any help in extracting further information from my system, please let me know how. If anyone knows what file to twiddle and how, I'll have a go at seeing if the solution works. Ray Dillinger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#461489: sense of laptop 'fn' key reversed on gateway MX6453
Processing commands for [EMAIL PROTECTED]: > reassign 461489 xorg Bug#461489: sense of laptop 'fn' key reversed on gateway MX6453 Warning: Unknown package 'xkbd-data' Bug reassigned from package `xkbd-data' to `xorg'. > -- 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]
xorg-server update for lenny
Hi, as xorg-server 1.4 isn't ready to migrate, and won't be for some more time, I prepared an updated package for testing-security. It fixes CVE-2007-5760, CVE-2007-5958, CVE-2007-6427, CVE-2007-6428, CVE-2007-6429 and CVE-2008-0006, and will be on its way to klecker in a few minutes. I'm travelling right now, so in case something comes up please contact [EMAIL PROTECTED] Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461501: closed by Brice Goglin <[EMAIL PROTECTED]> (Re: Bug#461501: xserver-xorg-core: dpi set to 96 inspite of DisplaySize option)
On Sat, Jan 19, 2008 at 08:09:07AM +, Debian Bug Tracking System wrote: > Change "Generic Monitor" into "LVDS", it should work. For more detail, > see http://wiki.debian.org/XStrikeForce/HowToRandR12 sections III.1 and > III.3 Yes it does work, I should have RTFWiki ;) , now I get 85x86. Sorry for the noise and many thankd for the quick reply. Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Bug#461521: xkb-data: olpc variants break af group
Package: xkb-data Version: 1.1~cvs.20080104.1-1 Severity: normal setxkbmap chokes on the olpc-enhanced Afghanistan map. Apparently they are using unrecognized symbols. I first noticed this starting up gnome-settings-daemon. On the console, it complained about the "tilde" symbol on line 220. I changed it to asciitilde. Then it complained about the next line. Picking up on a pattern, I didn't bother to investigate further and just deleted all the olpc sections from the file, with success. Suffice it to say they are broken, and it appears that the addition of broken variants (even if they're not used) causes the entire map to be broken. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: bug 451893 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=12865
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.13 > forwarded 451893 https://bugs.freedesktop.org/show_bug.cgi?id=12865 Bug#451893: xserver-xorg-video-intel: shows no fonts Bug#451791: xserver-xorg-video-intel: Fonts and many other items fail to render legibly Bug#452268: all fonts are unreadable Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=12865. > 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#233569: marked as done (xfree86: kick MAXCLIENTS up to 512 in Xserver, xfs, lbxproxy)
Your message dated Sat, 19 Jan 2008 09:35:40 +0100 with message-id <[EMAIL PROTECTED]> and subject line #256129: xfree86: xlibs reports "Maximum number of clients reached" has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xlibs Version: 4.2.1-11 Severity: minor according to http://marc.theaimsgroup.com/?l=xfree-xpert&m=98630396127386&w=4 the limit could be raised to 512... i'm currently using tons of xterms in many many virtual desktops. is there any simple way to raise this limit ? thanks -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux natch 2.4.22.natch #1 Wed Nov 5 16:28:44 EST 2003 i686 Locale: LANG=C, LC_CTYPE=en_US Versions of packages xlibs depends on: ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an ii libfreetype62.1.5-2 FreeType 2 font engine, shared lib ii xfree86-common 4.2.1-11 X Window System (XFree86) infrastr -- no debconf information --- End Message --- --- Begin Message --- Closing this very old wontfix to cleanup the BTS, the problem was probably actually related to resource leak anyway. Brice --- End Message ---
Bug#461503: upgrading xserver-xorg-core in etch causes corrupted display of icons in window manager
Lawrence Curington wrote: > Package: xserver-xorg-core > Version: 2:1.1.1-21etch2 > > If you upgrade to this version of xserver-xorg-core in > Debian Etch, it causes some icons in icewm window > manager to display in a corrupted manner. The actual > pixmaps themselves are not corrupted. They're just > rendered in a manner that is. Other WMs and DEs may > possibly also be affected. > > Downgrading back to version 2:1.1.1-21etch1 fixes the > rendering problem. So it definitely is an issue with > version 2:1.1.1-21etch2 > A new 2:1.1.1-21etch3 has already been prepared to fix a major regression in etch2. Could you test it and let me know if it helps for your problem? thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387444: marked as done (libx11: Should compile for /usr/lib64 as per FHS)
Your message dated Sat, 19 Jan 2008 09:35:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line closing very old wontfix has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: libx11 Severity: important Tags: patch Hi, the FHS specifies that on amd64 64bit libraries must be placed in (/usr)/lib64 and I believe the same rationale applies to the locale plugins in libx11. The libx11-6 library on Debian expects to find its locales in /usr/lib/X11/locale/common while other distributions have them (correctly as per FHS) in /usr/lib64/X11/locale/common. The attached patch compiled libx11-6 to use (/usr)/lib64 as libdir but renames that to (/usr)/lib before building debs as Debian wants it. That way compatibility with other distributions is preserved and the FHS is followed. This also allows automatic conversion to multiarch for the package alowing both 64 and 32bit packages to be installed at the same time without having to recompile the source on every update. MfG Goswin -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-frosties-2 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) diff -u libx11-1.0.0/debian/patches/series libx11-1.0.0/debian/patches/series --- libx11-1.0.0/debian/patches/series +++ libx11-1.0.0/debian/patches/series @@ -14,0 +15 @@ +015_makekeys.diff only in patch2: unchanged: --- libx11-1.0.0.orig/debian/patches/015_makekeys.diff +++ libx11-1.0.0/debian/patches/015_makekeys.diff @@ -0,0 +1,20 @@ +Index: libx11/src/util/makekeys.c +=== +--- libx11-1.0.0/src/util/makekeys.c 2006-01-25 01:40:34.0 + libx11-1.0.3/src/util/makekeys.c 2006-06-22 21:25:32.0 + +@@ -1,5 +1,5 @@ + /* $Xorg: makekeys.c,v 1.5 2001/02/09 02:03:40 $ */ +-/* $XdotOrg: xc/lib/X11/util/makekeys.c,v 1.4 2004/09/26 20:46:17 kuhn Exp $ */ ++/* $XdotOrg: lib/X11/src/util/makekeys.c,v 1.5 2005-07-03 07:00:56 daniels Exp $ */ + /* + + Copyright 1990, 1998 The Open Group +@@ -49,7 +49,7 @@ + KeySym val; + } info[KTNUM]; + +-#define MIN_REHASH 10 ++#define MIN_REHASH 15 + #define MATCHES 10 + + char tab[KTNUM]; diff -u libx11-1.0.0/debian/changelog libx11-1.0.0/debian/changelog --- libx11-1.0.0/debian/changelog +++ libx11-1.0.0/debian/changelog @@ -1,3 +1,11 @@ +libx11 (2:1.0.0-8a0.mrvn.0.1) unstable; urgency=low + + * Add makekeys patch from upstreams 1.0.3 version + * Set libdir to /usr/lib64 on amd64 + * Move debian/tmp/usr/lib64 to lib on amd64 + + -- Goswin von Brederlow <[EMAIL PROTECTED]> Tue, 12 Sep 2006 12:19:17 + + libx11 (2:1.0.0-8) unstable; urgency=low [ Denis Barbier ] diff -u libx11-1.0.0/debian/rules libx11-1.0.0/debian/rules --- libx11-1.0.0/debian/rules +++ libx11-1.0.0/debian/rules @@ -44,6 +44,10 @@ confflags += --enable-man-pages=3 --enable-loadable-i18n +ifeq ($(DEB_HOST_ARCH), amd64) +confflags += --libdir=/usr/lib64 +endif + # so very wrong CFLAGS += -DLIBXCURSOR=\\\"libXcursor.so.1\\\" @@ -80,6 +84,11 @@ dh_installdirs cd obj-$(DEB_BUILD_GNU_TYPE) && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install +ifeq ($(DEB_HOST_ARCH), amd64) + mkdir -p debian/tmp/usr/lib + mv debian/tmp/usr/lib64/* debian/tmp/usr/lib + rmdir debian/tmp/usr/lib64 +endif # Build architecture-dependent files here. binary-arch: build install --- End Message --- --- Begin Message --- I am closing these very old wontfix bugs to cleanup the BTS a bit. Brice --- End Message ---
Bug#85613: marked as done (xfree86: want case-sensitive XLFD font names)
Your message dated Sat, 19 Jan 2008 09:35:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line closing very old wontfix has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xfree86 Version: 4.0.2-1 Severity: wishlist This may be a stupid bug, but I must complain. It seems the X server lowercases all font-names. I.e. "Times New Roman" becomes "times new roman" (-monotype-times new roman-medium-r-normal-*-*-90-*-*-p-*-iso8859-15). This happens even if the font names in the fonts.dir file are correct (-monotype-Times New Roman-medium-r-normal--0-0-0-0-p-0-iso8859-15) I don't know if this is because the protocol/API forces it to be lowercase, but it is still annoying... Oskar Liljeblad ([EMAIL PROTECTED]) -- System Information Debian Release: testing/unstable Kernel Version: Linux oskar 2.2.18 #1 SMP Sat Jan 13 00:22:29 CET 2001 i686 unknown Versions of the packages xserver-xfree86 depends on: ii debconf0.3.73 Debian configuration management system ii libc6 2.2.1-1GNU C Library: Shared libraries and Timezone ii xserver-common 4.0.2-1files and utilities common to all X servers ii zlib1g 1.1.3-12 compression library - runtime --- End Message --- --- Begin Message --- I am closing these very old wontfix bugs to cleanup the BTS a bit. Brice --- End Message ---
Bug#225359: marked as done (xbase-clients: etc/X11/xinit/xinitrc should have mode 755)
Your message dated Sat, 19 Jan 2008 09:35:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line closing very old wontfix has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xbase-clients Version: 4.2.1-14 Severity: minor Tags: patch the xinitrc is a shell script, so I think it should be executable. I noticed this when using the Knoppix script to start the X client/server on boot, it tries to execute this script. Attached is a patch. Cheers, Bastian -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux treasure 2.6.0-treasure1 #1 Fri Dec 19 00:42:40 CET 2003 i686 Locale: LANG=C, [EMAIL PROTECTED] Versions of packages xbase-clients depends on: ii cpp-3.2 1:3.2.3-9 The GNU C preprocessor hi libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an hi libdps1 4.2.1-14 Display PostScript (DPS) client li hi libfreetype6 2.1.7-1FreeType 2 font engine, shared lib hi libncurses5 5.3.20030719-4 Shared libraries for terminal hand hi libxaw7 4.2.1-14 X Athena widget set library hi xlibmesa3-gl [libgl1] 4.2.1-14 Mesa 3D graphics library [XFree86] hi xlibmesa3-glu [libglu1] 4.2.1-14 Mesa OpenGL utility library [XFree hi xlibs 4.2.1-14 X Window System client libraries -- debconf information: * xbase-clients/default_100dpi: * xbase-clients/default_nolisten_tcp: --- debian/rules.basti 2003-12-28 21:45:54.0 +0100 +++ debian/rules2003-12-28 21:51:59.0 +0100 @@ -289,6 +289,7 @@ install -m 644 debian/local/xfs.options.5 $(DEBTREEDIR)/usr/share/man/man5 install -m 755 debian/local/xvfb-run $(DEBTREEDIR)/usr/bin install -m 644 debian/local/xvfb-run.1 $(DEBTREEDIR)/usr/share/man/man1 + chmod 0755 $(DEBTREEDIR)/etc/X11/xinit/xinitrc # compare manifests (cd debian/tmp && find -type f | LC_ALL=C sort | cut -c3-) > debian/MANIFEST.$(ARCH).new # confirm that the installed file list has not changed --- End Message --- --- Begin Message --- I am closing these very old wontfix bugs to cleanup the BTS a bit. Brice --- End Message ---
Bug#207481: marked as done (xserver-xfree86: [debconf] proposed overhaul)
Your message dated Sat, 19 Jan 2008 09:35:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line closing very old wontfix
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: xserver-xfree86
Severity: wishlist
Okay, here is what I would change in xserver-xfree86.config.
- xserver-xfree86/config/device/use_fbdev:
check for existance of /proc/fb before asking the question about
framebuffer support.
- If it does not exist, do not ask the question and set use_fbdev to
false.
- If it does exist, read it, and if
- the contents matches "nvidia", do
not ask the question and set use_fbdev to false.
- otherwise set default to false but ask the question
- To the video card section: I suggest setting SWCursor option
by-default, since some drivers show broken mouse pointer on certain
video cards.
- on every arch except of sun and sgi set the default of
xserver-xfree86/config/inputdevice/keyboard/rules to xfree86. This is
just guessing but should be okay for the majority of the users.
- get the first part /(\w\w)_../ of LC_CTYPE or LANG and set the
default for xserver-xfree86/config/inputdevice/keyboard/layout
- based on this setting, guess the layout most typical for the target
country and set as it as default, then ask the question
- based on the layout, set a default for
xserver-xfree86/config/inputdevice/keyboard/variant and ask the
question.
I suggest to ask people on debian-i18n to send some data about the
settings that majority of the users in their country uses. For
example, in de it is popular to set the "nodeadkeys" option. Russians
may want to set a second keymap in "layout", to "us,ru" and a
"grp:grp:alt_shift_toggle" (or some other toggle) option to rotate
the keymaps. We should just ask them on -i18n, code this settings
into one mapping table and insert them
- ask a question about advanced keyboard options with defaults from the
typical configuration selection mentioned above
- the mouse config is mostly okay, I just wish to see a final sentence
in every description:
"If unsure, choose to emulate the 3rd mouse button."
"If unsure, enable the Zaxismapping."
- For mouse autodetection: if gpm is running (test -e
/var/run/gpm.pid), then open /etc/gpm.conf and source it,
if $repeat_type exists, set
xserver-xfree86/config/inputdevice/mouse/port to /dev/gpmdata
and xserver-xfree86/config/inputdevice/mouse/protocol to the
$repeat_type value (eg. mapped from the gpm syntax to X syntax).
Now the most interessting part, the monitor settings. Following this
algorithm:
- ask about tft/lcd with the existing debconf question
- ask about the monitor identifier (and preset with "Generic Monitor"
or the name provided by parse-edid)
Throw away the current question about simple/medium/advanced setup and
proceed so:
- ask:
Template: xserver-xfree86/config/monitor/screen-size
Type: select
_Choices: Up to 14 inches (355 mm), 15 inches (380 mm), 17 inches (430 mm), 18
inches (480 mm), 19 inches (480 mm), 20 inches (510 mm), 21 inches (530 mm)
Default: 17 inches (430 mm)
_Description: Please choose your approximate monitor size.
Your answer should be as precise as possible. If you monitor has better
or lower quality than the average monitors in its class, you can
refine its settings later.
Template: xserver-xfree86/config/monitor/resolution-class
Type: select
_Choices: VGA (640x480), SVGA (800x600), XGA (1024x768), XGA+ (1152x864), SXGA
(1280x1024), SXGA+ (1400x1050), UXGA (1600x1200), W-UXGA (1920x1200)
Default: XGA (1024x768)
_Description: Please choose your resolution class
The resolution class of you monitor is normaly described in the manual
of the display.
If your display does not fit in any of this categories, choose just anything
and you can refine the settings later.
- If the monitor type is LCD, we can calculate all we need.
However, user may need to tune some things, eg. on non-4:3
displays. Later.
Now, we need a data table to choose the frequency values for an average
monitor of the given type and insert this settings in the following
template:
Template: xserver-xfree86/config/monitor/general-info
Type: boolean
Default: true
_Description: Is the choosed data correct?
Setup has now choosed following settings that should work for an
average monitor of the type you have choosen:
Brand name: ${identifier}
Type: {tft_or_lcd}
Screen ratio: 4:3
General Scr
Bug#297002: marked as done (startx: honour failsafe and default modes)
Your message dated Sat, 19 Jan 2008 09:35:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line closing very old wontfix has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xfree86 Version: 4.3.0.dfsg.1-12.0.1 Severity: wishlist Tags: patch Even though Debian's startx invokes Xsession, the default and failsafe arguments are not honoured. The attached patch adds that functionality. Please consider it for the next release. -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.10-9-amd64-k8 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! --- startx.orig 2005-02-26 12:45:58.0 +0100 +++ startx 2005-02-26 12:53:10.0 +0100 @@ -64,6 +64,10 @@ fi fi ;; +failsafe|default) + # let /etc/X11/Xsession handle failsafe and default mode + xsession_mode=$1 + ;; --) whoseargs="server" ;; @@ -89,6 +93,9 @@ # if no client arguments either, use rc file instead if [ x"$clientargs" = x ]; then client="$defaultclientargs" + if [ -n "$xsession_mode" ]; then + clientargs="$xsession_mode $clientargs" + fi else client=$defaultclient fi signature.asc Description: Digital signature --- End Message --- --- Begin Message --- I am closing these very old wontfix bugs to cleanup the BTS a bit. Brice --- End Message ---
Processed: forcibly merging 363965 220469
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.13 > forcemerge 363965 220469 Bug#363965: xserver-xorg: Can't force update of /etc/X11/xorg.conf Bug#220469: xserver-xfree86: [debconf] should re-create config files if they don't exist Bug#362078: xserver-xorg: dpkg-reconfigure doesn't work if the xorg.conf has been customized Bug#374583: xserver-xorg: Rethink xorg.conf configuration Bug#377294: new concept of upgrading configuration fails on versions management Forcibly Merged 220469 362078 363965 374583 377294. > 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#257703: marked as done (xfree86: consider separate targets for xc and xc-xserver-xfree86-dbg builds)
Your message dated Sat, 19 Jan 2008 09:24:50 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#257703: xfree86: consider separate targets for xc and xc-xserver-xfree86-dbg builds has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xfree86 Severity: wishlist If the xc-xserver-xfree86/ build failes (e.g. because of lack of diskspace) and one runs debian/rules build again, it seems large parts (all of?) xc/ get rebuilt as well. It would be nice if this could be prevented by two new debian/rules targets (like build-xserver and build-xserver-dbg) with accompayning stamps in stampdir. If you think this is a reasonable wishlist, I could try to cook up a patch. cheers, Michael --- End Message --- --- Begin Message --- This doesn't matter anymore today, closing. Brice --- End Message ---
Bug#258130: marked as done (xfree86: make all X clients depend on x-window-system-core)
Your message dated Sat, 19 Jan 2008 09:26:45 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#258130: xfree86: make all X clients depend on x-window-system-core has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xfree86 Version: all Severity: wishlist Error description: I am using Debian GNU/Linux since 1999 (SLINK 2.1r2) and I have gotten in all releases the same bugs. I can install X programs which depends on xlibs but it does not install a working X-Window-System. So what I like to see is to make all X programs which require a working X-Window-System Depends: x-window-system-core Suggest: window-manager -- System Information Debian Release: 3.0 Kernel Version: Linux michelle1 2.4.26-1-686 #1 Sun May 2 18:33:36 CEST 2004 i686 unknown signature.pgp Description: Digital signature --- End Message --- --- Begin Message --- Closing this very old wontfix bug since the installer probably helps newbies to install a pretty minimal system with X. Brice --- End Message ---
Bug#461501: marked as done (xserver-xorg-core: dpi set to 96 inspite of DisplaySize option)
Your message dated Sat, 19 Jan 2008 09:08:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#461501: xserver-xorg-core: dpi set to 96 inspite of DisplaySize option has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg-core Version: 2:1.4.1~git20080105-2 Severity: normal As you can see below, I have set a DisplaySize in xorg.conf which should get me a dpi of 85: $ grep DPI /var/log/Xorg.0.log (**) intel(0): DPI set to (85, 114) but instead I get the (new) default 96 (according to xdpyinfo). I can change it with xrandr, but according to the NEWS for xinit it should work like this. Regards, Andrei -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2006-12-27 01:36 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1673852 2008-01-17 16:26 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1996 2008-01-19 03:21 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "ro,us,ro,de" Option "XkbVariant""comma,,academic" Option "XkbOptions""grp:alts_toggle" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" EndSection Section "Device" Identifier "Generic Video Card" Driver "intel" Option "XAANoOffscreenPixmaps" "true" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" DisplaySize 305 228 EndSection Section "Screen" Identifier "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth16 SubSection "Display" Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection Section "Extensions" Option "Composite" "enable" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 42834 2007-12-19 19:10 /var/log/Xorg.1.log -rw-r--r-- 1 root root 34914 2008-01-19 03:49 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation gi
