Bug#732134: adding new themes in admin doesn't work
On a fresh new install of wordpress (Installed: 3.6.1+dfsg-1~deb7u4)
on my Debian wheezy machine, I added a new theme that I downloaded
from the interwebs. I unpacked it into /var/lib/wordpress/wp-content/themes
and some example new paths are:
/var/lib/wordpress/wp-content/themes/business-pro/
/var/lib/wordpress/wp-content/themes/business-pro/index.php
However the new theme does not show up in the admin (visiting url:
http://mdowney/wp-admin/themes.php)
I expected to see the new theme there and it is not. There is only the
following two themes:
twentytwelve
twentythirteen
After some fishing around, I concluded that in fact, wordpress admin is
not looking in /var/lib/wordpress/wp-contents for the themes.
Maybe once a theme is installed and some pages use it (I wouldn't know,
I haven't got that far yet), then wordpress uses that path, but the admin
itself does not.
I am doing to try what a person above did, which is to copy the theme into
/usr/share/wordpress/wp-content/themes.
A test I did do was to move /usr/share/wordpress/wp-content/themes to
themes.aside,
(while leaving /var/lib/wordpress/wp-content/themes in place) and indeed, there
is now only one theme twentythirteen and it has nothing to customize (the
customize page has no fields on it, although wp-admin does give you a
page for customizing. I'm guessing that page should have several choices
like background colour, text colour for certain elements, etc).
So I hope this helps to understand this bug.
Aha, indeed, adding a symlink from
/usr/share/wordpress/wp-content/themes/business-pro
- /var/lib/wordpress/wp-content/themes/business-pro results in the theme
showing up
in the admin.
I will be wary of the symlink, hopefully I won't forget that it is iffy if I run
into trouble when not using the admin. Hmm, I wonder if it is the apache
config that makes symlinks troublesome according to some reports ...
That can be fixed in the apache config. Although I suppose it's not terribly
secure, esp. if you allow editing of the themes from the web interface.
--
}{ Centre for Research and Experimental Development in Informatics Libre
Brenda J. Butler
b...@credil.org
+1 613 693 0684 #3202
F3018 - 283 Alexandre Taché
Gatineau (QC) J9A 1L8 CANADA
Sustainable Innovation // Innovation Durable
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718891: freetds package conflicts with kde packages (eg, konsole, okular)
Package: freetds Severity: normal Dear Maintainer, * What led up to the situation? I wanted to install freetds, while using a desktop with many kde packages (for instance konsole and okular). * What exactly did you do (or not do) that was effective (or ineffective)? apt-get install freetds * What was the outcome of this action? apt-get uninstalled a pile of kde packages, including konsole and okular, and installed freetds. I was able to use freetds - it was functional. Thankfully my existing konsole instances did not disappear when konsole was removed from the system. * What outcome did you expect instead? I expected freetds to be installed without uninstalling a bunch of completely unrelated packages. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657677: tex-common: missing files in /usr/share/doc/tex-common
On Tue, Feb 07, 2012 at 12:08:55PM +0100, Frank K?ster wrote: Brenda J. Butler b...@sourcerer.ca wrote: Package: tex-common Version: 2.08.1 Severity: minor I went to look at http://localhost/doc/tex-common/README.Debian.html, which exists, but every link from that page is broken. And the page consists mostly of links. Those links point to things like: localhost/doc/tex-common/ch1.html localhost/doc/tex-common/ch2.html#s-sec-texmf-trees localhost/doc/tex-common/ch5.html And those documents do not exist in my filesystem. That is a problem how symlinks are treated by the browser. README.Debian.html is a symlink to TeX-on-Debian.html/index.html. If you open the latter file, the http links work, but since they are relative links, they don't work from README.Debian.html one directory level higher. Does anybody have a clue how to fix this? Suggestion 1: Take away the symbolic link and make people go to the subdirectory to see the top-level file. Suggestion 2: Or, make a lot of symbolic links. Suggestion 3: Or, make a subdirectory for the extra links, and make a link to the subdirectory from the top. Illustrating the last suggestion: As it is now: (going from memory) .../doc/tex-common/README.Debian.html - html/README.Debian.html .../doc/tex-common/html/README.Debian.html .../doc/tex-common/html/ch1.html .../doc/tex-common/html/ch2.html README.Debian.html contains links like: ch1.html Suggested arrangement: .../doc/tex-common/README.Debian.html - html/README.Debian.html .../doc/tex-common/more - html/more .../doc/tex-common/html/README.Debian.html .../doc/tex-common/html/more/ch1.html .../doc/tex-common/html/more/ch2.html README.Debian.html contains links like: more/ch1.html HTH bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657677: tex-common: missing files in /usr/share/doc/tex-common
Package: tex-common Version: 2.08.1 Severity: minor I went to look at http://localhost/doc/tex-common/README.Debian.html, which exists, but every link from that page is broken. And the page consists mostly of links. Those links point to things like: localhost/doc/tex-common/ch1.html localhost/doc/tex-common/ch2.html#s-sec-texmf-trees localhost/doc/tex-common/ch5.html And those documents do not exist in my filesystem. apt-search file does not find a(nother) package in which those files belong. -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages tex-common depends on: ii debconf [debconf-2.0]1.5.36.1Debian configuration management sy ii dpkg 1.15.8.11 Debian package management system ii ucf 3.0025+nmu1 Update Configuration File: preserv tex-common recommends no packages. Versions of packages tex-common suggests: ii debhelper 8.0.0 helper programs for debian/rules Versions of packages texlive-base depends on: ii dpkg 1.15.8.11 Debian package management system ii install-info 4.13a.dfsg.1-6 Manage installed documentation in ii luatex0.60.2-1 next generation TeX engine ii mime-support 3.48-1 MIME files 'mime.types' 'mailcap ii texlive-binaries 2009-8 Binaries for TeX Live ii texlive-common2009-11TeX Live: Base component ii texlive-doc-base 2009-2 TeX Live: TeX Live documentation -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650082: CREDIL is interested to join this list
My organization is interested in joining this list and participating.
bjb
--
}{ Centre for Research and Experimental Development in Informatics Libre
Brenda J. Butler
b...@credil.org
+1 613 693 0684 #3202
F3018 - 283 Alexandre Taché
Gatineau (QC) J9A 1L8 CANADA
Sustainable Innovation // Innovation Durable
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: [Pkg-xen-devel] Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
YES!!! Thank you! (from my graphical desktop on my dom0). Let me know if there are any other things you'd like me to try. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
The function that returns ENOMEM is actually copy_mm. It returns ENOMEM when dup_mm returns 0. copy_mm receives clone_flags and task_struct * tsk. I think tsk is pointing to the new task (the process being forked). copy_mm assigns some values into *tsk, then: tsk-mm = NULL; tsk-active_mm = NULL; then we check if current process has -mm; if not, return 0 (effectively copying the no mm status into the new task_struct, is this true?). Presumably 0 return is success, because failure returns are things like -ENOMEM. If we haven't returned, then we check if clone_flags includes CLONE_VM; if so, we set our mm = the current process' -mm, set some elements in -mm and -tsk and return. If clone_flags does not include CLONE_VM, we try to set mm = dup_mm(tsk) which presumably means we are trying to duplicate the -mm of the task being created?!? and if that fails (0 return) then we return with -ENOMEM. So presumably the X server is trying to fork xkbcomp and is coming to this bit of code - current-mm is not 0, but clone_flags CLONE_VM is false. And I imagine that tsk-mm is still 0 (as we are trying to create it in copy_mm, is that true?) so copy_mm fails. I need to know more about clone_flags and who sets it. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On Fri, Nov 25, 2011 at 09:03:03PM -0500, Brenda J. Butler wrote: If clone_flags does not include CLONE_VM, we try to set mm = dup_mm(tsk) which presumably means we are trying to duplicate the -mm of the task being created?!? and if that fails (0 return) then we return with -ENOMEM. No, dup_mm tries to copy memory of the current task into the new task. But we see this message in kern.log: Xorg:2967 map pfn expected mapping type write-back for d000-e000, got write-combining This comes from reserve_pfn_range in arch/x86/mm/pat.c. In another note: I was able to do a kernel compilation with the kernel under xen that couldn't run the X server due to this forking problem. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
The thing that returns ENOMEM in fork.c when this failure occurs is: dup_mm I still have to see why. To try distinguishing between the ENOMEM returns, I tried adding a flag to the return value (eg: retval = -(ENOMEM | 0x8000) retval = -(ENOMEM | 0x4000) retval = -(ENOMEM | 0x2000) etc but that just caused the X server to disappear. At least it was a way to distinguish whether that return was being used, and I used that to tell which return ENOMEM was the problem, but a better method would be handy (without filling the logs too much reporting on every process rather than just the Xorg process). Anyway, I will look further at this to see why it's failing - suggestions on directions to try and methods to use are welcome. Also, I noticed during the several reboots for these experiments that when /etc/init.d/xend runs (under xen hypervisor), a bunch of errors show up on the console - and that's probably when this shows up in kern.log: Nov 24 08:52:08 blueeyes kernel: [ 30.913604] XENBUS: Unable to read cpu state Nov 24 08:52:08 blueeyes kernel: [ 30.913774] XENBUS: Unable to read cpu state Nov 24 08:52:08 blueeyes kernel: [ 30.913904] XENBUS: Unable to read cpu state Nov 24 08:52:08 blueeyes kernel: [ 30.914017] XENBUS: Unable to read cpu state Nov 24 08:52:08 blueeyes kernel: [ 30.914129] XENBUS: Unable to read cpu state Nov 24 08:52:08 blueeyes kernel: [ 30.914409] XENBUS: Unable to read cpu state Nov 24 08:52:08 blueeyes kernel: [ 30.914521] XENBUS: Unable to read cpu state Nov 24 08:52:08 blueeyes kernel: [ 30.914631] XENBUS: Unable to read cpu state This is before the system tries to run Xorg, as far as I can tell, because the console is still visible and spewing bootup text. Then later in kern.log, this appears (when booting under xen, not without xen): Nov 24 08:52:21 blueeyes kernel: [ 43.881792] Xorg:2940 map pfn expected mapping type write-back for d000-e000, got write-combining Nov 24 08:52:21 blueeyes kernel: [ 43.889937] BUG: unable to handle kernel paging request at f254 I am attaching a full kern.log for two boots. The first one is under xen, the second is not under xen. Same kernel and Xorg binaries. Maybe I will attach that in a second email. It's kind of big and might not get through. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
One more clue: in kern.log, when xserver is running under hypervisor, this appears: Nov 21 22:05:13 blueeyes kernel: [ 45.899070] Xorg:2949 map pfn expected mapping type writ e-back for d000-e000, got write-combining Nov 21 22:05:13 blueeyes kernel: [ 46.067758] Xorg:2949 freeing invalid memtype d000-e 000 And when the same binary xserver is running under the same linux kernel but not under hypervisor, it does not appear. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649394: linux-source-2.6.32: can't build 2.6.32-5 using 2.6_2.6.32-34squeeze1
Package: linux-source-2.6.32 Version: 2.6.32-38 Severity: normal I'm running 2.6.32-5-xen-amd64 and I'd like to compile a new vmlinuz with enhanced errno reporting (distinguish between ENOMEM returns in fork.c). When I try to build 2.6.32-5, it applies all the patches through 34squeeze1 (and actually fails to do that as one of the later patches conflicts with my change). What I did: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc /usr/src/kernel-patches/all/2.6.32/apply/debian 5 cd linux-2.6-2.6.32 vi kernel/fork.c fakeroot make -f debian/rules.gen binary-arch_amd64_xen What happened: (all the rest of the patches started to apply, and failed at version 14 where there was another edit to fork.c, so the build failed) What I expected: A build without all the rest of the patches being applied. Variant: in What I did, I tried this also, and all the patches still got applied: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc /usr/src/kernel-patches/all/2.6.32/apply/debian 5 cd linux-2.6-2.6.32 vi kernel/fork.c fakeroot make -f debian/rules.gen build_amd64_xen_amd64_real I looked in the makefiles, and noted that in debian/rules.real, the apply-patch command definition has no way to specify the patch-level: define patch_cmd cd '$(DIR)'; python '$(CURDIR)/debian/bin/patch.apply' --overwrite-home='$(CURDIR)/debian/patches' endef Maybe the $(ABINAME) could be used to produce a patch-level for this command? I'm not all that familiar with building Debian kernels from source, I'd be happy to learn the right way if I was doing it wrong. I was following instructions from http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage and supplemented it by reading the makefiles. bjb -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages linux-source-2.6.32 depends on: ii binutils 2.20.1-16 The GNU assembler, linker and bina ii bzip2 1.0.5-6high-quality block-sorting file co Versions of packages linux-source-2.6.32 recommends: ii gcc 4:4.4.5-1 The GNU C compiler ii libc6-dev [libc-dev] 2.11.2-10 Embedded GNU C Library: Developmen ii make 3.81-8 An utility for Directing compilati Versions of packages linux-source-2.6.32 suggests: ii kernel-package12.036+nmu1A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20100313-5 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649394: linux-source-2.6.32: can't build 2.6.32-5 using 2.6_2.6.32-34squeeze1
I see with further experimentation that the ABINAME being 5 and the patch-release that I want being 5 is probably just a coincidence. I added 5 (literal) as an argument to patch_command and it seems to be building without the extra patches. I haven't tried putting in my change yet ... will report on whether that succeeds later. bjb On Sun, Nov 20, 2011 at 11:28:45AM -0500, Brenda J. Butler wrote: Package: linux-source-2.6.32 Version: 2.6.32-38 Severity: normal I'm running 2.6.32-5-xen-amd64 and I'd like to compile a new vmlinuz with enhanced errno reporting (distinguish between ENOMEM returns in fork.c). When I try to build 2.6.32-5, it applies all the patches through 34squeeze1 (and actually fails to do that as one of the later patches conflicts with my change). What I did: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc /usr/src/kernel-patches/all/2.6.32/apply/debian 5 cd linux-2.6-2.6.32 vi kernel/fork.c fakeroot make -f debian/rules.gen binary-arch_amd64_xen What happened: (all the rest of the patches started to apply, and failed at version 14 where there was another edit to fork.c, so the build failed) What I expected: A build without all the rest of the patches being applied. Variant: in What I did, I tried this also, and all the patches still got applied: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc /usr/src/kernel-patches/all/2.6.32/apply/debian 5 cd linux-2.6-2.6.32 vi kernel/fork.c fakeroot make -f debian/rules.gen build_amd64_xen_amd64_real I looked in the makefiles, and noted that in debian/rules.real, the apply-patch command definition has no way to specify the patch-level: define patch_cmd cd '$(DIR)'; python '$(CURDIR)/debian/bin/patch.apply' --overwrite-home='$(CURDIR)/debian/patches' endef Maybe the $(ABINAME) could be used to produce a patch-level for this command? I'm not all that familiar with building Debian kernels from source, I'd be happy to learn the right way if I was doing it wrong. I was following instructions from http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage and supplemented it by reading the makefiles. bjb -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages linux-source-2.6.32 depends on: ii binutils 2.20.1-16 The GNU assembler, linker and bina ii bzip2 1.0.5-6high-quality block-sorting file co Versions of packages linux-source-2.6.32 recommends: ii gcc 4:4.4.5-1 The GNU C compiler ii libc6-dev [libc-dev] 2.11.2-10 Embedded GNU C Library: Developmen ii make 3.81-8 An utility for Directing compilati Versions of packages linux-source-2.6.32 suggests: ii kernel-package12.036+nmu1A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20100313-5 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- no debconf information ---end quoted text--- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On Thu, Nov 10, 2011 at 09:30:58AM -0500, Brenda J. Butler wrote: Please let me know if there is any other info you need. I'm not sure what to do next. I've gotten the source for the kernel I'm using, and put a bunch of debug statements in the kernel/fork.c:do_fork routine (to distinguish between all the ENOMEM returns) - but I'm not sure how to compile it the Debian way. I'm following instructions from http://kernel-handbook.alioth.debian.org/ch-common-tasks.html: To prepare, I make a fresh new directory: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc Apply patches: /src/kernel-patches/all/2.6.32/apply/debian 5 Make my changes: cd linux-2.6-2.6.32 vi kernel/fork.c Then when I try to compile: fakeroot make -f debian/rules.gen binary-arch_amd64_xen the build system applies the patches from -6 onward (which is bad, I don't want this, but willing to see if the patches will be unapplied in a later step), and failing and halting when it gets to a patch that wants to edit fork.c. I've tried removing the patches involved with -6 forward, but I must have done it badly because now the patches from the beginning through -5 don't apply cleanly. So, I'm trying to figure this out ... any help would be appreciated to get me moving forward more quickly. I'd really like to build a kernel that matches all my modules so I only have to replace the vmlinuz file for this test. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647961: xorg-server: --enable-debug exposes compile error
Package: xorg-server Version: 1.7.7 Severity: minor What I did: apt-get source xorg-server=1.7.7 cd xorg-server-1.7.7 fakeroot debian/rules patch sed -i 's/--disable-debug/--enable-debug/' debian/rules fakeroot debian/rules build Results: ... CCxf86Config.o ../../../../hw/xfree86/common/xf86Config.c: In function 'configInputDevices': ../../../../hw/xfree86/common/xf86Config.c:1501: error: request for member 'lay_identifier' in something not a structure or union make[6]: *** [xf86Config.lo] Error 1 ... What I expected: A completed build. Note: build without the change from sed succeeds. -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On Sat, Nov 05, 2011 at 12:35:32PM +0100, Julien Cristau wrote: apt is being stupid and trying to satisfy build-deps for the backports xorg-server. Try apt-get build-dep xorg-server=2:1.7.7-13. Thank you! I also had to apt-get source xorg-server=2:1.7.7-13, as I had gotten the source package for the squeeze-backports X server (no wonder it wanted all the newer libs, etc ...) It's compiling now. I'll try out the unchanged server to see that it works as well as the old one, then try making changes. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
Coming back to this - I see that the command line will be printed out if a debug flag is set - how do I set it? in ddxList.c on lines 206-207: if (xkbDebugFlags) DebugF([xkb] xkbList executes: %s\n,buf); How can I set xbkDebugFlags? I'd like to try the exact invocation at the command line to see what happens. bjb On Sat, Oct 29, 2011 at 06:25:46PM +0200, Julien Cristau wrote: On Sat, Oct 29, 2011 at 09:57:23 -0400, Brenda J. Butler wrote: I don't have any .xkb or .xkm files on my system (the xkbcomp man page says it uses and produces files of those names) although I do have a directory /usr/share/X11/xkb. The .xkm files are created by xkbcomp in /tmp or /var/lib/xkb, read by the server, and then immediately deleted, so you're not supposed to have those around. Cheers, Julien ---end quoted text--- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On Fri, Nov 04, 2011 at 10:00:33PM +0100, Julien Cristau wrote:
On Fri, Nov 4, 2011 at 13:41:02 -0400, Brenda J. Butler wrote:
Coming back to this - I see that the command line will be printed out
if a debug flag is set - how do I set it?
in ddxList.c on lines 206-207:
if (xkbDebugFlags)
DebugF([xkb] xkbList executes: %s\n,buf);
How can I set xbkDebugFlags? I'd like to try the exact invocation
at the command line to see what happens.
#include X11/Xlib.h
#include X11/XKBlib.h
int main() {
Display *dpy = XOpenDisplay(NULL);
if (!dpy)
return 1;
return XkbSetDebuggingFlags(dpy, 1, 1, NULL, 0, 0, NULL, NULL) !=
True;
}
(link with -lX11)
Did I mention XKB was made of crazy?
Unfortunately, the X server doesn't run long enough to run a client
under it ... I wanted to set the flag from the X server command line.
Well, option 2 is to recompile it with some changes. Wish me luck.
First I'm looking at the source code to see the chain of events that
leads to the problem. I guess the X server main routine is in dix/main.c,
it looks like this:
while (1)
...
InitExtensions (argc, argv);
...
InitCoreDevices ()
InitInput (agrc, argv)
InitAndStartDevices ()
...
Dispatch ();
...
}
InitExtensions calls XkbExtensionInit ()
XkbExtensionInit calls AddExtension (-, -, -, ProcXkbDispatch, ...)
AddExtension puts ProxXkbDispatch into the ProcVector table.
ProcVector routines are called from dix/dispatch.c,
--- still a big fog ---
XkbListComponents called from ProcXkbDispatch
XkbListComponent called from XkbListComponents
XkbDDXListComponent outputs: 'Could not invoke keymap compiler' after
a call to System with the xkbcomp command line returns less than 0.
So it might be that the X server initializes, gets as far as Dispatch,
and sends itself an event to do with the keybord but fails to run xkbcomp.
Or it might be that the problem occurs in initialization (seems more likely
but I don't see the call chain ... yet).
Thanks for your help!
I can only work on this on Fridays/weekends and unfortunately I don't have a
lot of time for it.
bjb
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
Cannot build: I probably did something wrong, but what? did apt-get build-dep xserver-xorg then tried fakeroot debian/rules binary and had to install quilt and xutils-dev separately because they didn't get installed with build-dep, then this: bjb@blueeyes:~/projects/xserver-xorg/xorg-server-1.10.4$ fakeroot debian/rules binary dh_testdir autoreconf -vfi autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 configure.ac:29: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg autoreconf: configure.ac: tracing configure.ac:29: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force configure.ac:29: warning: AC_INIT: not a literal: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg configure.ac:69: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:70: error: possibly undefined macro: AC_DISABLE_STATIC configure.ac:71: error: possibly undefined macro: AC_PROG_LIBTOOL autoreconf: /usr/bin/autoconf failed with exit status: 1 make: *** [stampdir/autoreconf] Error 1 bjb@blueeyes:~/projects/xserver-xorg/xorg-server-1.10.4$ apt-cache policy xserver-xorg xserver-xorg: Installed: 1:7.5+8 Candidate: 1:7.5+8 Version table: 1:7.6+8~bpo60+1 0 100 http://debian.mirror.iweb.ca/debian-backports/ squeeze-backports/main amd64 Packages *** 1:7.5+8 0 500 http://debian.mirror.iweb.ca/debian/ squeeze/main amd64 Packages 100 /var/lib/dpkg/status I see that 1:7.5+8 is the latest for squeeze. help? bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On Fri, Nov 04, 2011 at 06:19:53PM -0400, Brenda J. Butler wrote: Cannot build: I probably did something wrong, but what? I had to install libtool: sudo apt-get install libtool libtool-doc Found the solution in ubuntu forums, now it's in debian bug tracker too : - ) On to the next hurdle: installing libudev-dev, because it didn't get installed with build-dep either. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On to the next hurdle: installing libudev-dev, because it didn't get installed with build-dep either. Installing libudev-dev, as well as x11proto-gl-dev was no problem. Then it wanted me to install x11proto-xf86dri-dev, which I did, but the subsequent build attempt gave this error: configure: error: Package requirements (glproto = 1.4.10 dri = 7.8.0) were not met: Requested 'dri = 7.8.0' but version of dri is 7.7.1 I have to leave it here for today. Any advice would be appreciated for the next time I pick it up. I can't help thinking I started out wrong, to be having all these problems building a stock debian package on a debian stable system. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On Sat, Nov 05, 2011 at 01:11:36AM +0100, Julien Cristau wrote:
On Fri, Nov 4, 2011 at 19:39:32 -0400, Brenda J. Butler wrote:
I can't help thinking I started out wrong, to be having all these problems
building a stock debian package on a debian stable system.
It doesn't sound like you've actually run apt-get build-dep xorg-server.
Installing libgl1-mesa-dev should get you over this one failure though.
Yes, you are right: today I ran apt-get build-dep ... must have been some other
name, but I thought it was the right one and it installed some stuff so
I thought that step was done.
When I run it with the right package name, it says:
bjb@blueeyes:~/projects/xserver-xorg/xorg-server-1.10.4$ sudo apt-get build-dep
xorg-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Build-Depends dependency for xorg-server cannot be satisfied because no
available versions of package x11proto-core-dev can satisfy version requirements
and
bjb@blueeyes:~/projects/xserver-xorg/xorg-server-1.10.4$ apt-cache policy
x11proto-core-dev
x11proto-core-dev:
Installed: 7.0.16-1
Candidate: 7.0.16-1
Version table:
7.0.22-1~bpo60+1 0
100 http://debian.mirror.iweb.ca/debian-backports/
squeeze-backports/main amd64 Packages
*** 7.0.16-1 0
500 http://debian.mirror.iweb.ca/debian/ squeeze/main amd64 Packages
100 /var/lib/dpkg/status
Hmm, I have 7.0.16-1, and that is the squeeze version ...
Re the other package libgl1-mesa-dev:
bjb@blueeyes:~/projects/xserver-xorg/xorg-server-1.10.4$ apt-cache policy
libgl1-mesa-dev
libgl1-mesa-dev:
Installed: 7.7.1-5
Candidate: 7.7.1-5
Version table:
7.10.3-4~bpo60+1 0
100 http://debian.mirror.iweb.ca/debian-backports/
squeeze-backports/main amd64 Packages
*** 7.7.1-5 0
500 http://debian.mirror.iweb.ca/debian/ squeeze/main amd64 Packages
100 /var/lib/dpkg/status
Trying to find dependency problems from another angle, which packages do I
have installed that come from backports:
bjb@blueeyes:~$ dpkg --get-selections | cut -f 1 | while read PKG; do echo -n
$PKG; dpkg-query -W -f '${Version}\n' $PKG ; done | egrep '.*bpo'
mupdf0.8.15-1~bpo60+1
mupdf-tools0.8.15-1~bpo60+1
Doesn't look like something that would interfere with an xorg-xserver build.
bjb
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646987: /usr/bin/xinit: xinit fails with xkbcomp could not be invoked
On Sat, Oct 29, 2011 at 12:02:43PM +0200, Julien Cristau wrote: On Fri, Oct 28, 2011 at 22:35:20 -0400, Brenda J. Butler wrote: Package: xinit Version: 1.2.0-2 Severity: important File: /usr/bin/xinit using 2.6.32-5-xen-amd64 I can run an X server, but using 2.6.32-5-xen-amd64 (the same) under the Xen 4.0 hypervisor, I cannot. The Xorg.log file from running under hypervisor is included below, it has the following in it: (EE) XKB: Could not invoke xkbcomp and then a couple of lines later: Fatal server error: Failed to activate core devices. This log file is after I switched to just VESA (not radeon) X driver after seeing some advice to someone to try removing all xserver-xorg-video-* packages except vesa and fbdev. With the radeon driver, I get the same result (xorg works with kernel, not with hypervisor + kernel). I do have a /usr/bin/xkbcomp file, and I can run it from the command line. I cannot find where xkbcomp is invoked in the x init scripts, so I'm stuck trying to debug this. I'm also unfamiliar with xkbcomp generally (what are the inputs and outputs, where do they exist on disk, etc.) so although I could invoke it at the command line, I didn't know what args to try to pass it. Or how to do that step manually so xinit does not have to. However, it seems xinit cannot even invoke it, if the log message was literal. xkbcomp is invoked by the X server directly. It uses the files in /usr/share/X11/xkb/ to build a keymap. Ok, so this bug is not for xinit - I will try to move it over to the X server package. I don't have any .xkb or .xkm files on my system (the xkbcomp man page says it uses and produces files of those names) although I do have a directory /usr/share/X11/xkb. I see the X Server gives this message Could not invoke keymap compiler from xkb/ddxList.c, it would be nice if it could report the error status in the log message. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611407: xen-tools: --ip=auto option always fails; 'auto' doesn't match IPaddr regex
Package: xen-tools Version: 4.2-1 Severity: normal Tags: upstream xen-create-image --ip=auto --otheroptions always fails as the regex checks are done before the special-case processing of --ip=auto, and 'auto' doesn't match the IPv4 address regex. -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages xen-tools depends on: ii debootstrap 1.0.23 Bootstrap a basic Debian system ii libconfig-inifiles-perl 2.52-1 Read .ini-style configuration file ii libfile-slurp-perl.13-1 single call read write file rout ii libtext-template-perl 1.45-1 Text::Template perl module ii perl-modules 5.10.1-14 Core Perl modules Versions of packages xen-tools recommends: ii libexpect-perl1.21-1 Expect.pm - Perl Expect interface ii rinse 1.7-1 RPM installation environment ii xen-hypervisor-3.2-1-i386 [xe 3.2.1-2The Xen Hypervisor on i386 ii xen-shell 1.8-3 Console based Xen administration u Versions of packages xen-tools suggests: pn btrfs-toolsnone(no description available) pn cfengine2 none(no description available) pn evms-cli none(no description available) ii reiserfsprogs 1:3.6.19-6User-level tools for ReiserFS file ii xen-utils-4.0 [xen-utils] 4.0.1~rc6-1 XEN administrative tools ii xfsprogs 2.9.8-1lenny1 Utilities for managing the XFS fil -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596196: problem went away
After today's upgrade and a reboot, kdm starts properly now. Here are the versions of these packages as they stand on my machine today - 2010-09-17 (added next to package name): No changes made to graphics config. bjb consolekit0.4.1-4 debconf 1.5.35 2010-08-06 12:47:32 status installed debconf 1.5.33 2010-08-09 22:11:10 status installed debconf 1.5.35 kdebase-runtime 4:4.4.5-1 2010-08-10 19:12:27 status installed kdebase-runtime 4:4.4.5-1 kdebase-workspace-kgreet-plugins 4:4.4.5-3 libc62.11.2-6 2010-08-06 11:45:25 status installed libc6 2.11.2-2 2010-09-04 10:23:49 status installed libc6 2.11.2-4 2010-09-07 09:10:26 status installed libc6 2.11.2-5 libck-connector0 0.4.1-4 libdbus-1-3 1.2.24-3 2010-08-09 20:46:06 status installed libdbus-1-3 1.2.24-3 libkdecore5 4:4.4.5-1 2010-08-09 20:47:06 status installed libkdecore5 4:4.4.5-1 libkdeui5 4:4.4.5-1 2010-08-09 20:47:07 status installed libkdeui5 4:4.4.5-1 libkio5 4:4.4.4-5 2010-08-09 20:47:07 status installed libkio5 4:4.4.5-1 libknewstuff2-4 4:4.4.5-1 2010-08-09 20:47:10 status installed libknewstuff2-4 4:4.4.5-1 libkworkspace44:4.4.5-3 2010-08-09 20:55:43 status installed libkworkspace4 4:4.4.5-1 2010-08-10 19:13:05 status installed libkworkspace4 4:4.4.5-2 2010-08-12 15:23:12 status installed libkworkspace4 4:4.4.5-3 libpam0g1.1.1-6 2010-08-16 18:49:18 status installed libpam0g 1.1.1-4 2010-09-07 09:19:38 status installed libpam0g 1.1.1-6 libqimageblitz4 1:0.0.4-4 libqt4-svg 4:4.6.3-2 2010-09-07 09:25:26 status installed libqt4-svg 4:4.6.3-2 libqt4-xml 4:4.6.3-2 2010-09-07 09:25:24 status installed libqt4-xml 4:4.6.3-2 libqtcore4 4:4.6.3-2 2010-09-07 09:25:24 status installed libqtcore4 4:4.6.3-2 libqtgui4 4:4.6.3-2 2010-09-07 09:25:25 status installed libqtgui4 4:4.6.3-2 libstdc++6 4.4.4-14 libx11-6 2:1.3.3-3 libxau6 1:1.0.6-1 2010-08-09 20:50:17 status installed libxau6 1:1.0.6-1 libxdmcp6 1:1.0.3-2 libxtst6 2:1.1.0-3 2010-08-09 20:47:06 status installed libxtst6 2:1.1.0-3 lsb-base 3.2-23.1 fluxbox 1.1.1+git20100908.df2f51b-2 2010-08-09 21:00:43 status installed fluxbox 1.1.1+dfsg2-1 2010-08-13 16:32:09 status installed fluxbox 1.1.1+git20100807.0cc08f9-1 kde-window-manager4:4.4.5-3 2010-08-09 20:55:48 status installed kde-window-manager 4:4.4.5-1 2010-08-10 19:13:05 status installed kde-window-manager 4:4.4.5-2 2010-08-12 15:23:15 status installed kde-window-manager 4:4.4.5-3 kdebase 5:64 2010-08-09 20:55:53 status installed kdebase 5:64 konsole 4:4.4.5-1 2010-08-09 20:55:34 status installed konsole 4:4.4.5-1 logrotate3.7.8-6 metacity1:2.30.1-2 2010-08-09 20:56:53 status installed metacity 1:2.30.1-2 twm 1:1.0.4-2 xserver-xorg1:7.5+7 2010-09-07 09:26:04 status installed xserver-xorg 1:7.5+7 xterm 261-1 2010-08-09 20:55:34 status installed xterm 261-1 kdepasswd 4:4.4.5-1 2010-08-09 20:55:48 status installed kdepasswd 4:4.4.5-1 linux-image none (!) 2010-08-09 20:48:04 status installed linux-image-2.6.32-5-686 2.6.32-18 2010-08-09 20:56:46 status installed linux-image-2.6-686 2.6.32+28 2010-08-09 20:56:46 status installed linux-image-686 2.6.32+28 2010-08-09 22:27:23 status installed linux-image-2.6.32-5-686 2.6.32-19 2010-08-13 16:32:07 status installed linux-image-2.6.32-5-686 2.6.32-20 2010-08-28 15:03:13 status installed linux-image-2.6.32-5-xen-686 2.6.32-21 2010-08-28 15:03:16 status installed linux-image-2.6-xen-686 2.6.32+28 2010-08-28 15:24:28 status installed linux-image-2.6.26-2-xen-686 2.6.26-24lenny1 2010-09-04 10:34:46 status installed linux-image-2.6.32-5-686 2.6.32-21 2010-09-07 09:25:43 status installed linux-image-2.6.26-2-xen-686 2.6.26-25 linux-image-2.6.32-5-6862.6.32-22 linux-image-2.6-686 2.6.32+28 linux-image-686 2.6.32+28 linux-image-2.6.32-5-xen-6862.6.32-22 linux-image-2.6.26-2-xen-6862.6.26-25lenny1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596196: kdm shows black screen instead of login
Subject: kdm shows black screen instead of login Package: kdm Version: 4:4.4.5-3 Severity: important *** Please type your report below this line *** Problem: kdm shows a black screen When it happens: When kdm is started, I see a black screen (every time) What I expected: Some login input fields user and password More info: - It used to work with an earlier version of stuff - I have been upgrading often in the last couple of weeks This happened earlier this week (ie, in the last 7 days). I'm not sure if kdm was upgraded recently. ... hmm, nope. It was upgraded to the current version Aug 12. - When I boot the machine, it does a normal boot of the kernel and init scripts, then goes into graphical mode and shows a black backlit screen with no mouse cursor. - kdm is running. - I can use the init scripts to kill off kdm and restart it. invoke-rc.d kdm stop; invoke-rc.d kdm start kdm stops and restarts as requested. - after I stop kdm, I can run xinit or startx and I can see some graphics. - problem occurs with reported kernel and with linux-image-2.6.32-5-xen-686 - hardware is laptop, ThinkPad T43, type 1872WTE. output from lspci: 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11) 04:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller 04:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05) extracts from Xorg.0.log: (egrep '(EE|WW)' /var/log/Xorg.0.log) (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. (II) Loading extension MIT-SCREEN-SAVER (WW) Falling back to old probe method for vesa (WW) Falling back to old probe method for fbdev (EE) GLX error: Can not get required symbols. (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device SynPS/2 Synaptics TouchPad (EE) GLX error: Can not get required symbols. (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device SynPS/2 Synaptics TouchPad last section from /var/log/kdm.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 i686 Debian Current Operating System: Linux spidy 2.6.32-5-686 #1 SMP Wed Aug 25 14:28:12 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=UUID=15c49a99-7c9a-49b6-b7d2-92eee917c9b9 ro acpi_sleep=s3_bios Build Date: 04 September 2010 10:33:09PM xorg-server 2:1.7.7-5 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. 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/Xorg.0.log, Time: Wed Sep 8 19:08:42 2010 (==) Using system config directory /usr/share/X11/xorg.conf.d WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/bluez, it will be ignored in a future release. WARNING: All config files need .conf:
Bug#586143: Same problem
Yes, this file /boot/grub/stage2 exists on my system. Thanks for your work on grub. bjb On Fri, Jun 18, 2010 at 01:10:42PM +0100, Colin Watson wrote: On Fri, Jun 18, 2010 at 01:59:15PM +0200, Salvatore Bonaccorso wrote: I'm not the original reporter but experience the similar problem, getting 'unaligned pointer 0x4c1b0297'. I tried to collect the information you requested for that: Thanks. This is the most interesting part: Generating core.img Saving menu.lst backup in /boot/grub/menu.lst_backup_by_grub2_postinst Running update-grub Legacy to hook our core.img in it [...] I've just gone through an extensive debugging session with an affected user on IRC who had the same symptom (thanks, dileX), and I believe I understand the problem now. I would like to confirm one fact with the people who have contributed to this bug report so far, namely: Does the file /boot/grub/stage2 exist on your system? I strongly suspect at this point that that will be the case for all of you, and if that's the case then I know what to do. Thanks, -- Colin Watson [cjwat...@debian.org] ---end quoted text--- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586143: doesn't load grub: unaligned pointer 0x4c19a146
With grub-pc 1.98+20100614-2, I had the same failure, with unaligned pointer 0x4c19a146. This occurred before any other output to the screen by grub. No menu, no shell, nothing. downgraded to grub-pc 1.98+20100602-2 (and grub-common 1.98+20100602-2) and the problem went away. The problem occurred after an upgrade from grub-pc (and grub-common) 1.98+20100602-2 to 1.98+20100614-2. This was on a Thinkpad T43. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#459524: rules for palm in udev.rules and z60_libpisock9.rules: why?
I'm probably wrong about the pilot udev rule - see this link for how it is explained to me. Something about using libusb vs using the kernel visor module. I was probably confusing the two methods and trying to do some of each. http://lists.pilot-link.org/pipermail/pilot-link-devel/2008-January/001671.html I will send the udevinfo -a when I get home again, and try out some stuff as well. bjb On Mon, Jan 07, 2008 at 01:18:57AM -0500, Brenda J. Butler wrote: There are two places where rules related to palm's exist: - udev.rules, where the symlink is created - z60_libpisock9.rules, where permissions and ownership is decided for the actual device nodes. udev.rulesis owned by package udev. z60_libpisock9.rules is owned by package pilot-link. Maybe that rule about pilots in udev.rules should be moved to z60_libpisock9.rules? Just a thought ... bjb ---end quoted text--- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459524: udevinfo output
Hopefully I got the right invocation ... Chose this name because
that's what /dev/pilot was pointing to, and the last two numbers
matched up with the dmesg output.
[EMAIL PROTECTED] $ udevinfo -a --name /dev/bus/usb/004/032
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/usb_device/usbdev4.32':
KERNEL==usbdev4.32
SUBSYSTEM==usb_device
DRIVER==
ATTR{dev}==189:415
looking at parent device '/devices/pci:00/:00:1d.3/usb4/4-1':
KERNELS==4-1
SUBSYSTEMS==usb
DRIVERS==usb
ATTRS{product}==Palm Handheld
ATTRS{manufacturer}==Palm, Inc.
ATTRS{quirks}==0x0
ATTRS{maxchild}==0
ATTRS{version}== 1.10
ATTRS{devnum}==32
ATTRS{busnum}==4
ATTRS{speed}==12
ATTRS{bMaxPacketSize0}==8
ATTRS{bNumConfigurations}==1
ATTRS{bDeviceProtocol}==00
ATTRS{bDeviceSubClass}==00
ATTRS{bDeviceClass}==ff
ATTRS{bcdDevice}==0100
ATTRS{idProduct}==0061
ATTRS{idVendor}==0830
ATTRS{bMaxPower}==500mA
ATTRS{bmAttributes}==c0
ATTRS{bConfigurationValue}==1
ATTRS{bNumInterfaces}== 1
ATTRS{configuration}==
ATTRS{dev}==189:415
looking at parent device '/devices/pci:00/:00:1d.3/usb4':
KERNELS==usb4
SUBSYSTEMS==usb
DRIVERS==usb
ATTRS{serial}==:00:1d.3
ATTRS{product}==UHCI Host Controller
ATTRS{manufacturer}==Linux 2.6.22-2-686 uhci_hcd
ATTRS{quirks}==0x0
ATTRS{maxchild}==2
ATTRS{version}== 1.10
ATTRS{devnum}==1
ATTRS{busnum}==4
ATTRS{speed}==12
ATTRS{bMaxPacketSize0}==64
ATTRS{bNumConfigurations}==1
ATTRS{bDeviceProtocol}==00
ATTRS{bDeviceSubClass}==00
ATTRS{bDeviceClass}==09
ATTRS{bcdDevice}==0206
ATTRS{idProduct}==
ATTRS{idVendor}==
ATTRS{bMaxPower}== 0mA
ATTRS{bmAttributes}==e0
ATTRS{bConfigurationValue}==1
ATTRS{bNumInterfaces}== 1
ATTRS{configuration}==
ATTRS{dev}==189:384
looking at parent device '/devices/pci:00/:00:1d.3':
KERNELS==:00:1d.3
SUBSYSTEMS==pci
DRIVERS==uhci_hcd
ATTRS{msi_bus}==
ATTRS{broken_parity_status}==0
ATTRS{modalias}==pci:v8086d24DEsv1014sd0287bc0Csc03i00
ATTRS{local_cpus}==ff
ATTRS{irq}==16
ATTRS{class}==0x0c0300
ATTRS{subsystem_device}==0x0287
ATTRS{subsystem_vendor}==0x1014
ATTRS{device}==0x24de
ATTRS{vendor}==0x8086
looking at parent device '/devices/pci:00':
KERNELS==pci:00
SUBSYSTEMS==
DRIVERS==
ATTRS{uevent}==
[EMAIL PROTECTED] $
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459524: udev.rules: remove KERNEL==ttyUSB* condition from pilot symlink
Package: udev
Version: 0.114-2
Severity: normal
The pilot-link package doesn't work for me because /dev/pilot isn't
getting created - and I think that's because in this rule of udev.rules:
SUBSYSTEMS==usb, KERNEL==ttyUSB*, \
ATTRS{product}==Palm Handheld*|Handspring Visor|palmOne Handheld, \
SYMLINK+=pilot
the KERNEL==ttyUSB* condition is no longer being met.
When I remove that condition, the /dev/pilot symlink gets created
and the pilot-link package can talk to the Palm again.
(bjb.rules below contains stuff about some hard disks - nothing in there about
pilots. In fact, here's the contents of bjb.rules in case you need to see it)
##
# Explore
##
ACTION==add ENV{BJB_VAR}=add
ACTION==remove ENV{BJB_VAR}=remove
ACTION==change ENV{BJB_VAR}=change
PROGRAM=/usr/bin/logger -p info -i 'udev unconditional start $env{BJB_VAR}'
##
# Kingston Datatraveller memory stick
##
#KERNEL==1-5
#SUBSYSTEM==usb
#SYSFS{configuration}==
#SYSFS{serial}==09907451019018DB
#SYSFS{product}==DataTraveler 2.0
#SYSFS{manufacturer}==Kingston
#SYSFS{maxchild}==0
#SYSFS{version}== 2.00
#SYSFS{devnum}==8
#SYSFS{speed}==480
#SYSFS{bMaxPacketSize0}==64
#SYSFS{bNumConfigurations}==1
#SYSFS{bDeviceProtocol}==00
#SYSFS{bDeviceSubClass}==00
#SYSFS{bDeviceClass}==00
#SYSFS{bcdDevice}==0100
#SYSFS{idProduct}==0008
#SYSFS{idVendor}==08ec
#SYSFS{bMaxPower}==200mA
#SYSFS{bmAttributes}==80
#SYSFS{bConfigurationValue}==1
#SYSFS{bNumInterfaces}== 1
SYSFS{serial}==09907451019018DB, SYSFS{product}==DataTraveler 2.0, \
SYSFS{manufacturer}==Kingston, \
NAME=%k, SYMLINK=usbdisk
##
# John Nash's backup disk
##
# find /sys -name dev
# udevinfo -a -p /sys/block/sdb/sdb1
# looking at parent device '/devices/pci:00/:00:1d.7/usb5/5-6':
#KERNELS==5-6
#SUBSYSTEMS==usb
#DRIVERS==usb
#ATTRS{configuration}==
#ATTRS{serial}==10038694
#ATTRS{product}==USB2.0 Storage Device
#ATTRS{manufacturer}==Cypress Semiconductor
#ATTRS{maxchild}==0
#ATTRS{version}== 2.00
#ATTRS{devnum}==8
#ATTRS{speed}==480
#ATTRS{bMaxPacketSize0}==64
#ATTRS{bNumConfigurations}==1
#ATTRS{bDeviceProtocol}==00
#ATTRS{bDeviceSubClass}==00
#ATTRS{bDeviceClass}==00
#ATTRS{bcdDevice}==0001
#ATTRS{idProduct}==6830
#ATTRS{idVendor}==04b4
#ATTRS{bMaxPower}== 0mA
#ATTRS{bmAttributes}==c0
#ATTRS{bConfigurationValue}==1
#ATTRS{bNumInterfaces}== 1
SYSFS{serial}==10038694, SYSFS{product}==USB2.0 Storage Device, \
SYSFS{manufacturer}==Cypress Semiconductor, \
NAME=%k, SYMLINK+=nash
# try to use a new variable in an action in the same rule
SYSFS{serial}==10038694, SYSFS{product}==USB2.0 Storage Device, \
SYSFS{manufacturer}==Cypress Semiconductor, \
ENV{BJB_ACTION}=ACTION, \
RUN+=logger -p info -i 'udev: nash event $env{BJB_ACTION}'
##
# my backup disk partitions
##
# find /sys -name dev
# udevinfo -a -p /sys/block/sdc/sdc12
# looking at parent device '/devices/pci:00/:00:1d.7/usb5/5-4':
#KERNELS==5-4
#SUBSYSTEMS==usb
#DRIVERS==usb
#ATTRS{configuration}==Config0
#ATTRS{serial}==6QG04957
#ATTRS{product}==FreeAgentDesktop
#ATTRS{manufacturer}==Seagate
#ATTRS{maxchild}==0
#ATTRS{version}== 2.00
#ATTRS{devnum}==12
#ATTRS{speed}==480
#ATTRS{bMaxPacketSize0}==64
#ATTRS{bNumConfigurations}==1
#ATTRS{bDeviceProtocol}==00
#ATTRS{bDeviceSubClass}==00
#ATTRS{bDeviceClass}==00
#ATTRS{bcdDevice}==
#ATTRS{idProduct}==3000
#ATTRS{idVendor}==0bc2
#ATTRS{bMaxPower}== 0mA
#ATTRS{bmAttributes}==c0
#ATTRS{bConfigurationValue}==1
#ATTRS{bNumInterfaces}== 1
KERNEL==sd*[0-9]*, SYSFS{serial}==6QG04957, \
SYSFS{manufacturer}==Seagate, SYSFS{idProduct}==3000, \
SYSFS{idVendor}==0bc2, \
SYMLINK+=backup-%n
# try to use a new variable in an action in the same rule
KERNEL==sd*[0-9]*, SYSFS{serial}==6QG04957, \
SYSFS{manufacturer}==Seagate, SYSFS{idProduct}==3000, \
SYSFS{idVendor}==0bc2, \
ENV{BJB_ACTION}=ACTION, \
RUN+=logger -p info -i 'udev: backup event [%n] $env{BJB_ACTION}'
#KERNEL==sd*[0-9]*, SYSFS{serial}==6QG04957, \
# SYSFS{manufacturer}==Seagate, SYSFS{idProduct}==3000, \
# SYSFS{idVendor}==0bc2, \
# SYMLINK+=backup-%n RUN=mount /dev/backup-%n
-- Package-specific info:
-- /etc/udev/rules.d/:
Bug#459524: rules for palm in udev.rules and z60_libpisock9.rules: why?
There are two places where rules related to palm's exist: - udev.rules, where the symlink is created - z60_libpisock9.rules, where permissions and ownership is decided for the actual device nodes. udev.rules is owned by package udev. z60_libpisock9.rulesis owned by package pilot-link. Maybe that rule about pilots in udev.rules should be moved to z60_libpisock9.rules? Just a thought ... bjb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457996: Acknowledgement (xserver-xorg-video-intel: fonts and icons illegible; console fonts missing)
A bit more info: the problem occured with both stock kernels: 2.6.22-2-686 2.6.18-4-686 Tried dpkg-reconfiguring the following, with no effect: xserver-xorg xfonts-base defoma Tried modprobe the following, with no effect; fbcon console Tried dpkg-reconfiguring the following: fontconfig Interestingly, the first boot after fontconfig was reconfigured (to 2.6.22-2-686) had a clear font. But, I needed to to try an unrelated USB thing (for pilot-xfer) so rebooted to 2.6.18-4-686 immediately and the problem re-appeared. Then tried rebooting to 2.6.22-2-686 to see if the fonts were still legible, and they weren't. bjb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457996: xserver-xorg-video-intel: fonts and icons illegible; console fonts missing
On Thu, Dec 27, 2007 at 10:38:57PM +0100, Brice Goglin wrote: This is probably similar to bug #439210. I am merging these bugs. You should first try adding Option AccelMethod XAA to the Device section of your xorg.conf. I tried this and it didn't help - no effect. There's also a patch in https://bugs.freedesktop.org/attachment.cgi?id=12993 which should solve the problem even without the above config line. It would be nice to test it since I don't remember anybody else having this problem on an i865 board. If you need help to rebuild the driver with this patch, see http://bgoglin.livejournal.com/10936.html and feel free to ask. (xf86-video-intel commit 96246c27cb836bae8ee02c46c68a1f2102efd14b) This worked great! The kdm full-page graphic (root window) looks fine, the text is legible. After logging in, all the text in the KDE desktop (menus, panel, in konsole, window title, everywhere) looks great, all the icons are crisp and clear. Alt-F1 brings me a console that I can log in on and the monitor does not immediately go to power-save mode. Thank you to Brice for his quick response to my bug and for his excellent instructions for trying the patch. And thanks to sooperkul on irc.oftc.net #debian for identifying the right place for me to put the bug for a speedy resolution. bjb not so scared of X problems any more -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424938: vrms: total num of pkgs missing on clean system
Package: vrms Version: 1.12-0.1 Severity: wishlist *** Please type your report below this line *** vrms output for non-clean system ends with a summary line like: 3 non-free packages, 0.2% of 1363 installed packages. but vrms output for a clean system ends with: No non-free packages installed on gw.stuffed.animals! rms would be proud. If I want to compare my systems, it would be nice to have a total number of installed packages on the clean output. Thanks! -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages vrms depends on: ii perl-modules 5.8.8-7Core Perl modules vrms recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292806: some debugging
It seems the problem (for a fresh install) is that the call to parse_cpu_data fails because the file /usr/local/share/pmk/pmkcpu.dat does not exist on a fresh install. (Why is the error message that says the file does not exist commented out?) I don't know how you want to fix this (create the file? proceed with the value from uname?) so I haven't attached a patch, but hopefully I've saved you some time. See: pmksetup.c, function get_cpu_data detect_cpu.c, function parse_cpu_data parse_cpu_data returns a pointer to the parsed data from the file, or NULL on a variety of failures, so ignoring the one case where the file didn't exist would be hard for me to implement (as someone who doesn't know the ins and outs of the program). But if you have a suggestion on how to proceed, fire it my way and I'll give it a shot. cheerio, bjb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292806: still bug in 0.9.2
Ok, so I saw the new email to this bug and downloaded the upstream 0.9.2 version and tried that. It still fails in cpu detection, this time the error message _is_ printed and it says: Error : cannot open '/home/bjb/.pmk/pmkcpu.dat' : No such file or directory. Error : failure in cpu detection. Error : child failed (status 256) cheerio, bjb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
