Bug#736811: linux-image-3.12-1-amd64: Booting in VMware Fusion VM fails with module vmwgfx loaded
Package: src:linux Version: 3.12.6-2 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, Installed from debian-testing-amd64-netinst.iso dated 26 January 2014 in new VMware Fusion VM, which went well. Upon first reboot, the boot process stopped right away with an error message related to the i2c_piix4 module, which was expected as SMBus is not enabled in VMware Fusion. I started the iso in rescue mode, blacklisted this module, updated initramfs and booted again. From this point on the boot process stopped usually at Waiting for /dev to be fully populated... and sometimes even at Synthesizing the initial hotplug events... and never got any further, no matter how long I waited. I tried booting in single user mode, and it appeared that various messages related to vmware modules, like vmw_vmci and vmwgfx. I recognized these names because in my Wheezy installation and older these modules had to be compiled separately from various openvm packages, if the user needed them (only vmw_balloon or memctl was actually needed and already included in the modules for kernel 3.2.0 in Wheezy). I then tried blacklisting these modules (in rescue mode) one by one (followed by updating initramfs). I got lucky with the vmwgfx module (located in kernel/drivers/gpu/drm/...). Blacklisting it (in addition to i2c_piix4, see above) made the boot process continue OK. So it would seem that the vmwgfx module is the culprit. This, and other vmware-related modules are now packaged with the kernel -- perhaps they should be separated again as they were in the various openvm packages in Wheezy. Personally, I've not actually ever needed these modules (except vmw_balloon or memctl), so could do without them. Just my 2 cents, naturally... Henk Koster -- Package-specific info: ** Version: Linux version 3.12-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-10) ) #1 SMP Debian 3.12.6-2 (2013-12-29) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.12-1-amd64 root=UUID=04a9cfcc-dc04-4b5a-a89c-bc6db38d9079 ro quiet ** Not tainted ** Kernel log: [2.069645] hub 2-0:1.0: 2 ports detected [2.220217] ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 0001, max UDMA/33 [2.235700] ata2.00: configured for UDMA/33 [2.236015] scsi 2:0:0:0: CD-ROMNECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5 [2.240750] sr0: scsi3-mmc drive: 1x/1x writer dvd-ram cd/rw xa/form2 cdda tray [2.240753] cdrom: Uniform CD-ROM driver Revision: 3.20 [2.241016] sr 2:0:0:0: Attached scsi CD-ROM sr0 [2.244220] sd 0:0:0:0: [sda] 62914560 512-byte logical blocks: (32.2 GB/30.0 GiB) [2.244277] sd 0:0:0:0: [sda] Write Protect is off [2.244279] sd 0:0:0:0: [sda] Mode Sense: 61 00 00 00 [2.244342] sd 0:0:0:0: [sda] Cache data unavailable [2.244344] sd 0:0:0:0: [sda] Assuming drive cache: write through [2.244680] sd 0:0:0:0: [sda] Cache data unavailable [2.244682] sd 0:0:0:0: [sda] Assuming drive cache: write through [2.246205] sda: sda1 sda2 sda3 [2.246575] sd 0:0:0:0: [sda] Cache data unavailable [2.246577] sd 0:0:0:0: [sda] Assuming drive cache: write through [2.246673] sd 0:0:0:0: [sda] Attached SCSI disk [2.246915] sd 0:0:0:0: Attached scsi generic sg0 type 0 [2.246936] sr 2:0:0:0: Attached scsi generic sg1 type 5 [2.292834] PM: Starting manual resume from disk [2.292837] PM: Hibernation image partition 8:3 present [2.292837] PM: Looking for hibernation image. [2.293029] PM: Image not found (code -22) [2.293030] PM: Hibernation image not present or could not be loaded. [2.304685] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [2.379514] usb 2-1: new full-speed USB device number 2 using uhci_hcd [2.499834] systemd-udevd[310]: starting version 204 [2.557411] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [2.557416] ACPI: Power Button [PWRF] [2.559097] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [2.564719] vmw_vmci :00:07.7: enabling device ( - 0003) [2.565235] vmw_vmci :00:07.7: Found VMCI PCI device at 0x12100, irq 16 [2.565275] vmw_vmci :00:07.7: setting latency timer to 64 [2.565305] vmw_vmci :00:07.7: Using capabilities 0xc [2.565484] vmw_vmci :00:07.7: irq 72 for MSI/MSI-X [2.565533] vmw_vmci :00:07.7: irq 73 for MSI/MSI-X [2.565850] Guest personality initialized and is active [2.565894] VMCI host device registered (name=vmci, major=10, minor=59) [2.565896] Initialized host personality [2.566261] ACPI: AC Adapter [ACAD] (on-line) [2.595815] snd_ens1371 :02:02.0: enabling device ( - 0001) [2.596517] snd_ens1371 :02:02.0: setting latency timer to 64 [2.605536] parport_pc 00:08: [io 0x0378-0x037b] [2.606013] parport_pc 00:08: [irq 5] [2.606636] parport_pc 00:08: activated [2.606639] parport_pc 00
Bug#682787: open-vm-tools: Faulty screen resolution on 15-inch MacBook Pro Retina
Package: open-vm-tools
Version: 2:8.8.0+2012.05.21-724730-3
Severity: normal
Tags: upstream
Dear Maintainer,
The new MacBook Pro Retina sports a true 2880x1800 resolution screen, but
not even Apple are using that true resolution. Instead, they offer a choice
of scaled resolutions, with the equivalent of 1440x900 being recommended.
Other useful choices are 1650x1080 and 1920x1200.
I find that the best virtual screen resolution in a VMware Fusion VM should
match the equivalent value in OS X, any other choice (whether scaled in Gnome3
or not) leads to fuzzy letters. The above resolutions are available in Systems
Settings/Displays or with xrandr, and can be applied without any problem.
The problem of this bug is that this resolution choice (Keep this
configuration) does not survive relogging in or rebooting. While the gdm3
login screen shows my preferred 1440x900, Gnome3 reverts to the real 2880x1800
resolution each and every time with the open-vm-{tools,dkms,toolbox} packages
and related kernel modules installed. My eyes are just not good enough to
handle the extremely small text under 2880x1800.
I've tried setting the 1440x900 mode in xorg.conf, but this doesn't have any
effect. Removing the open-vm-... packages solves the problem, though; then
the preferred resolution survives rebooting.
I've also tried the official VMware Tools, but here the same problem exists.
This leads me to think that it is an upstream issue: the VM should consider
as native screen resolution the choice of scaled resolution used in OS X.
Regards,
Henk Koster
*** End of the template - remove these lines ***
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-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
Versions of packages open-vm-tools depends on:
ii libc6 2.13-35
ii libdumbnet1 1.12-3.1
ii libfuse2 2.9.0-5
ii libgcc1 1:4.7.1-5
ii libglib2.0-0 2.32.3-1
ii libicu48 4.8.1.1-8
ii libprocps01:3.3.3-2
ii libstdc++64.7.1-5
Versions of packages open-vm-tools recommends:
ii ethtool 1:3.4.2-1
ii open-vm-dkms 2:8.8.0+2012.05.21-724730-3
ii zerofree 1.0.2-1
Versions of packages open-vm-tools suggests:
ii open-vm-toolbox 2:8.8.0+2012.05.21-724730-3
-- Configuration Files:
/etc/pam.d/vmtoolsd [Errno 2] No such file or directory: u'/etc/pam.d/vmtoolsd'
/etc/vmware-tools/poweroff-vm-default [Errno 2] No such file or directory:
u'/etc/vmware-tools/poweroff-vm-default'
/etc/vmware-tools/poweron-vm-default [Errno 2] No such file or directory:
u'/etc/vmware-tools/poweron-vm-default'
/etc/vmware-tools/resume-vm-default [Errno 2] No such file or directory:
u'/etc/vmware-tools/resume-vm-default'
/etc/vmware-tools/scripts/vmware/network [Errno 2] No such file or directory:
u'/etc/vmware-tools/scripts/vmware/network'
/etc/vmware-tools/statechange.subr [Errno 2] No such file or directory:
u'/etc/vmware-tools/statechange.subr'
/etc/vmware-tools/suspend-vm-default [Errno 2] No such file or directory:
u'/etc/vmware-tools/suspend-vm-default'
/etc/vmware-tools/tools.conf changed:
/etc/xdg/autostart/vmware-user.desktop [Errno 2] No such file or directory:
u'/etc/xdg/autostart/vmware-user.desktop'
-- 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#532293: Clarification...
There have been several updates of the open-vm-source package in Sid since this bug was filed, as well as a new kernel 2.6.30 and a new source package at SourceForge. I just want to confirm that the current open-vm-source package in Sid (2009-06-18) still does not build with m-a, and that the work-around posted above does also apply to all these updates. To clarify for those unfamiliar with the syntax of makefiles: 1. Run m-a a-i h...@debianvm:~$ lsmod |grep vm vmsync 4704 0 vmmemctl8824 0 vmhgfs 50408 0 vmci 30016 0 hpen-vm (as root) -- this still fails, but leaves an unpacked source in the /usr/src/modules/open-vm/ directory. 2. Download the latest stable tar-ball open-vm-tools-2009.06.18-172495.tar.gz from http://sourceforge.net/projects/open-vm-tools/files/ and unpack it, e.g. in /home/user/Downloads. 3. As root, edit /usr/src/modules/open-vm/Makefile and add at the beginning of each of the lines under 'build' OVT_SOURCE_DIR=/home/user/Download/open-vm-tools-2009.06.18-172495 (let the remainder of the line wrap around). 4. Now rerun the m-a command, except that the source must not be unpacked again (that would override the changes just made), so use the command (as root) m-a -O a-i open-vm (that's a capital letter O), and now the compilation and the subsequent Debian packaging and installation of the modules succeeds (it did for my 2.6.30-1-amd64 kernel in a mixed testing/Sid system) -- open-vm-modules-2.6.30-1-amd64 package listed in Aptitude under Obsolete and Locally created packages. The modules load properly: $ lsmod |grep vm vmsync 4704 0 vmmemctl8824 0 vmhgfs 50408 0 vmci 30016 0 Cheers! -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532293: Clarification...
Sorry about the typo (there's no way that I know of to edit my message)... Henk Koster wrote: There have been several updates of the open-vm-source package in Sid since this bug was filed, as well as a new kernel 2.6.30 and a new source package at SourceForge. I just want to confirm that the current open-vm-source package in Sid (2009-06-18) still does not build with m-a, and that the work-around posted above does also apply to all these updates. To clarify for those unfamiliar with the syntax of makefiles: 1. Run m-a a-i open-vm (as root) -- this still fails, but leaves an unpacked source in the /usr/src/modules/open-vm/ directory. 2. Download the latest stable tar-ball open-vm-tools-2009.06.18-172495.tar.gz from http://sourceforge.net/projects/open-vm-tools/files/ and unpack it, e.g. in /home/user/Downloads. 3. As root, edit /usr/src/modules/open-vm/Makefile and add at the beginning of each of the lines under 'build' OVT_SOURCE_DIR=/home/user/Download/open-vm-tools-2009.06.18-172495 (let the remainder of the line wrap around). 4. Now rerun the m-a command, except that the source must not be unpacked again (that would override the changes just made), so use the command (as root) m-a -O a-i open-vm (that's a capital letter O), and now the compilation and the subsequent Debian packaging and installation of the modules succeeds (it did for my 2.6.30-1-amd64 kernel in a mixed testing/Sid system) -- open-vm-modules-2.6.30-1-amd64 package listed in Aptitude under Obsolete and Locally created packages. The modules load properly: $ lsmod |grep vm vmsync 4704 0 vmmemctl8824 0 vmhgfs 50408 0 vmci 30016 0 Cheers! -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#494293: Reinstalling...
OK, I reinstalled from the daily debian-testing-amd64-netinst.iso dated 13 December 2008 on my MacBook Pro 4,1 (Penryn), dual-booting with Mac OS X Leopard, using partitions /dev/sda3 and /dev/sda4 for root and swap, respectively. As before, installation went without any problem, with again the installer correctly detecting EFI/GPT and automatically installing Grub-2 (grub-pc): I opted for installing it to the MBR. Upon reboot, the rEFIt boot manager showed both Mac OS X and GNU/Linux icons, but selecting the latter gave a boot media not found message --- a known problem, since the MBR partition table must first be synchronized with GPT. On my wish-list is to have the installer do this (e.g. with the gptsync utility). In the event, I rebooted and used the Partition tool in the rEFIt menu, then rebooted once more, chose the GNU/Linux icon and lo! the Grub menu appeared and few seconds later the familiar Debian login screen. So, it appears that my earlier Grub problem has been solved, for which I thank the developers. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#470400: This bug has bitten me...
This bug has recently bitten me in an unexpected manner! I had just done a new installation of Debian testing on my MacBook Pro with GUID partition table (GPT), using the 6 August 2008 testing-amd64-netinst.iso. Towards the end of the installation, the installer automatically installed new Grub (grub-pc) to the MBR of the internal HD, but (after resynching GPT and the MBR partition table) then it produced the error message error: not a regular file Entering rescue mode... I knew that old Grub would work, so I set up a chroot, purged the grub-pc package, installed the older grub package, used update-grub and grub-install and rebooted (again after synching the partition tables). What? The same error... It wasn't until after I just emptied the /boot/grub directory and reinstalled grub, etc, that all was well and my new Debian could be booted. Several hours later, I might add... Mind you, the Debian installer should have asked me whether I wanted to have grub-pc installed, I filed bug #494293 on that. The earlier response to the current bug underlines the importance of my bug. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494293: A bit more info...
I used the very same amd64-netinst.iso dated 6 August 2008 to install on a newly built desktop computer, just a straight-forward install with Desktop and Standard tasks. Towards the end the installer installed grub... the old Grub (as I could verify after the successful reboot). Emboldened by this result, I popped the install CD back into the MacBook Pro and proceeded to do a similar installation, using root/swap partitions from a previous installation of Ubuntu 8.04 Hardy (uses the old Grub). I even left off the Laptop task, but again towards the end the installer installed grub2(the dummy package) and grub-pc... the new Grub. Apparently, the Debian Installer picks up on the fact that this is a dual-boot installation next to Mac OS X, so there is a GUID partition table. The installer is (apparently) configured to install the new Grub in that case, since it can deal with GPT (from the description in Aptitude). Unfortunately, this does not work: without resynching the GPT and the MBR partition table there is no bootable device, and with resynching (I'm using the Partition tool in the rEFIt boot manager) it gives the error reported earlier. I believe this bug would solved by the Debian Installer giving a choice between installing old or new Grub. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494293: ...and finally.
I've started the install-CD in rescue mode, opened a shell in a chroot, and did an apt-get purge to get rid of grub-pc in preparation of replacing it with the old grub package. Bit then, unlike the previous time, I checked and saw that /boot/grub was still full of files left there, including grub.cfg. So, I deleted the whole lot, before doing apt-get install grub, /usr/sbin/update-grub and /usr/sbin/grub-install. Now the reboot brought up the newly-installed Debian testing. Some final thoughts: 1. The apt-get purge grub-pc command should not leave a whole directory full of config files that are subsequently used by grub-install. 2. Perhaps old and new grub should not share the same grub-install. 3. The Debian Installer should give users a choice when it wants to install a piece of crucial software that is still considered by many to be in beta (in this case new Grub vs. old Grub). Thank you for your consideration. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491896: Future of OO2C Debian package
OK, OK, enough already... I apologize for my intemperate language earlier in this thread. Several others have also mentioned the possibility to propose user packages via sponsoring, or via debian-unofficial. I intend to look further into this, as I feel that Wirth's elegant Oberon-2 language and its OO2C implementation deserve a package accessible to Debianites. In the meantime, compiling the latest stable source (downloaded from the OOC pages at SourceForge) is an easy substitute. Peace! -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491896: Terminating OO2C
Just like that, eh? Some guy proposes to chuck oo2c (and liboo2c-dev and liboo2c3), and next you know it it's gone. I'm sure that someone here will reply that it's policy and that I should have protested earlier. Well, fuck policy if that means leaving ordinary users (like myself) in trouble. I would certainly have protested if I'd known that this was coming, but I don't normally troll these messages. Now, with Lenny frozen, I presume there's no way to rectify this. Oh, just for the record: I've thought about adopting this package, but cannot even come close to the requirements of the exalted priesthood of Debian maintainers. Thanks for nothing. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483604: oo2c: Dependencies need fixing
Package: oo2c Version: 2.1.11-3 Severity: important The oo2c package, as installed with dependencies, is not sufficient to compile Oberon2 programmes. Various other packages are required for this, including (but perhaps not limited to): liboo2c-dev, libg2c0-dev and libtool (as of 29 May 2008). There may be others, since I already had module-assistant installed and done an m-a prepare command. These dependencies should be fixed before Lenny goes final. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages oo2c depends on: ii gcc 4:4.2.3-10 The GNU C compiler ii libc6 2.7-10 GNU C Library: Shared libraries ii libc6-dev 2.7-10 GNU C Library: Development Librari ii libgc-dev 1:6.8-1.1 conservative garbage collector for ii liboo2c3 2.1.11-3 Optimizing Oberon-2 to ANSI-C Comp oo2c recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483615: Config file /etc/oo2c/oo2crc.xml does not work
Package: oo2c Version: 2.1.11-3 Severity: important Tried do add another repository to /etc/oo2c/oo2crc.xml, but the change was not picked up when running the programme. Making the identical change to /usr/lib/oo2c/oo2crc.xml was properly noticed by the programme. Is this not counter to Debian policy? Of course, the added repository can also be specified in the environmental variable OOC_REPS, but I believe the config file in /etc should work if one is provided. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages oo2c depends on: ii gcc 4:4.2.3-10 The GNU C compiler ii libc6 2.7-10 GNU C Library: Shared libraries ii libc6-dev 2.7-10 GNU C Library: Development Librari ii libgc-dev 1:6.8-1.1 conservative garbage collector for ii liboo2c3 2.1.11-3 Optimizing Oberon-2 to ANSI-C Comp oo2c recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471147: sbcl: SBCL does not install cleanly,
Package: sbcl Version: 1:1.0.15.0-1 Severity: normal Installation of SBCL invoked the debugger; this can be reproduced with: [EMAIL PROTECTED]:~# dpkg-reconfigure sbcl /usr/lib/common-lisp/bin/sbcl.sh loading and dumping clc. fatal error encountered in SBCL pid 15136(tid 47683278071520): GC invariant lost, file gencgc.c, line 834 Welcome to LDB, a low-level debugger for the Lisp runtime environment. ldb quit Really quit? [y] mv: cannot stat `sbcl-new.core': No such file or directory FAILED To be sure, SBCL can be started but I don't trust it as long as installation invkes the debugger... -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sbcl depends on: ii common-lisp-controller6.14 Common Lisp source and compiler ma ii libc6 2.7-9 GNU C Library: Shared libraries Versions of packages sbcl recommends: ii binfmt-support1.2.10 Support for extra binary formats -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453296: MacBook: cannot assign right mouse click to lower Enter key
Package: xserver-xorg Version: 1:7.3+7 Severity: normal The CD MacBook keyboard only has a single (left) mouse button below the touchpad, so I like to assign the right mouse click function to the lower Enter key (KP_Enter) with the commands xmodmap -e keycode 108 = Pointer_Button3 xkbset m These commands have been put in a script in .kde/Autostart. This setup has worked fine until a recent upgrade of X, now there is no response from hitting the lower Enter key. I have included the output from hitting the left mouse button (which works) and the right mouse button (which doesn't). It appears that there is a spurious extra pair of ButtonPress/Release events in the latter case... I have always specified the keyboard as pc104; changing this to pc105, macbook78 or macbook79 makes no difference. The Mouse Navigation with numpad feature has not been enabled in KDE Settings/ Peripherals/Mouse. Enabling it (and commenting the above xkbset command) makes no difference either. There is no keypad entry in the /etc/X11 subtree; copying it from /usr/share/X11/xkb/symbols to /etc/X11/xkb/synbols and changing all occurrences of KP_Enter to Pointer_Button3 makes no difference either. -- 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-03-17 15:29 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1672732 2007-11-20 03:03 /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 Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) /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 1914 2007-11-27 18:27 /etc/X11/xorg.conf Contents of /etc/X11/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 manual page. # (Type man at the shell prompt.) # # This file is automatically updated on package upgrades *only* # if it has not been modified since the last upgrade of the # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh 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 EndSection Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option MaxTapTime 0 Option VertScrollDelta 20 Option VertTwoFingerScroll 1 Option MinSpeed .70 Option MaxSpeed .70 Option AccelFactor 0.06 EndSection Section Device Identifier Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller Driver intel BusID PCI:0:2:0 Option UseFBDev true EndSection Section Monitor Identifier Configured Monitor Option DPMS HorizSync 28-33 VertRefresh 43-72 EndSection Section Screen Identifier Default Screen MonitorConfigured Monitor DefaultDepth24 SubSection Display Modes 1280x800 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse InputDevice Synaptics Touchpad EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 34314 2007-11-28 13:09 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20071119-1) Current Operating System: Linux sid32 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 Build Date: 20 November 2007 01:48:55AM 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/Xorg.0.log, Time: Wed Nov 28 13:09:44 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default
Bug#448863: Workaround...
But the workaround for this bug was already mentioned on 3 November in Dwayne Litzenberger's response (see above) to this bug... It can attest that it works, so no need to be without Sid for over a week while waiting for the upgrade to wend its way through uploads. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437360: /usr/bin/setkeycodes.... which package?
My earlier reply to your request got eaten by the system, so here again: /usr/bin/setkeycodes is in the console-tools-1:0.2.3dbs-65 package (current in Sid). Henk Koster -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#437360: ...and won't be removed either!
This bug appears while apt-get (dist-)upgrading Sid on both an AMD64 and a 686 system. Interestingly, it also shows when trying to apt-get remove the package: Removing hotkey-setup ... KDSETKEYCODE: Invalid argument failed to set scancode 1 to keycode 256 invoke-rc.d: initscript hotkey-setup, action stop failed. dpkg: error processing hotkey-setup (--remove): subprocess pre-removal script returned error exit status 1 Errors were encountered while processing: hotkey-setup E: Sub-process /usr/bin/dpkg returned an error code (1) And, finally, the following two lines have appeared for weeks now in the messages that flash by when shutting the computer down: KDSETKEYCODE: Invalid argument failed to set scancode 1 to keycode 256 Can't install, can't upgrade, can't remove and can't stop the messages... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430497: Shutdown (8) possibly to be updated...
It appears from the referenced linux-ata.org site that the problem *may* affect Debian's shutdown utility if it has been modified from the upstream version. Not doing anything in that case may have negative effect on the lifetime of the disk! In my case that would be an expensive laptop HD. It seems to me that this bug needs to be handled with greater urgency -- 30 days have already gone by since it was first reported. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387851: still a problem July 2007
As the OP seems to have lost interest, let me report that the problem still persists on my system (with an Atheros AR5424 chip) running up-to-date Sid with madwifi-source package 1:0.9.3-3 compiled for the 2.6.21-2-686 kernel. The problem does not only exist with my Linksys WAG200G AP at home, but also with various HotSpots on the road. I have now given up on network-manager (removed it) and am using wpa_supplicant in roaming mode, which connects flawlessly and automatically to my WPA-PSK secured LAN at home, a WEP-protected LAN at a friend's house, or any unsecured HotSpot network on the road, whichever available. Remarkably, roaming mode of wpa_supplicant seems to be a well-kept secret, as it is never mentioned in any of the Debian (or Debian-related) forums... -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425364: There is no resource available!
Package: korganizer Version: 4:3.5.6.dfsg.1-2 Severity: important Existing appointments (to dos, alarms) do not show when opening KOrganizer, and new appointments cannot be entered because There is no resource available!. Existing appointments are still present in .kde/share/apps/korganizer/std.ics, dated a few days ago (16 May 2007), predating the latest upgrade of the korganizer package. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425364: Dependency information
korganizer package version 4:3.5.6.dfsg.1-2 depends on: kdelibs4c2a (= 4:3.5.6-1), libart-2.0-2 (= 2.3.18), libaudio2, libc6 (= 2.5), libfontconfig1 (= 2.4.0), libfreetype6 (= 2.2), libgcc1 (= 1:4.1.1-12), libice6 (= 1:1.0.0), libidn11 (= 0.5.18), libjpeg62, libkcal2b (= 4:3.5.6), libkdepim1a (= 4:3.5.6), libkpimexchange1 (= 4:3.5.6), libkpimidentities1 (= 4:3.5.6), libpng12-0 (= 1.2.13-4), libqt3-mt (= 3:3.3.7), libsm6, libstdc++6 (= 4.1.1-12), libx11-6, libxcursor1 ( 1.1.2), libxext6, libxft2 ( 2.1.1), libxi6, libxinerama1, libxrandr2 (= 2:1.2.0), libxrender1, libxt6, zlib1g (= 1:1.2.1), perl Is this what you want/need? -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425364: korganizer: dependencies
Package: korganizer Version: 4:3.5.6.dfsg.1-2 Followup-For: Bug #425364 Is this what you want/need? I'm still learning... -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-k7 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages korganizer depends on: ii kdelibs4c2a 4:3.5.7.dfsg.1-1 core libraries and binaries for al ii libart-2.0-22.3.19-3 Library of functions for 2D graphi ii libaudio2 1.9-2The Network Audio System (NAS). (s ii libc6 2.5-7GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1.2generic font configuration library ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libgcc1 1:4.2-20070516-1 GCC support library ii libice6 1:1.0.3-2X11 Inter-Client Exchange library ii libidn110.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.6.dfsg.1-2 KDE calendaring library ii libkdepim1a 4:3.5.6.dfsg.1-2 KDE PIM library ii libkpimexchange14:3.5.6.dfsg.1-2 KDE PIM Exchange library ii libkpimidentities1 4:3.5.6.dfsg.1-2 KDE PIM user identity information ii libpng12-0 1.2.15~beta5-2 PNG library - runtime ii libqt3-mt 3:3.3.7-4+b1 Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-1X11 Session Management library ii libstdc++6 4.2-20070516-1 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxcursor1 1:1.1.8-2X cursor management library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxi6 1:1.0.1-4X11 Input extension library ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxrandr2 2:1.2.1-1X11 RandR extension library ii libxrender1 1:0.9.2-1X Rendering Extension client libra ii libxt6 1:1.0.5-3X11 toolkit intrinsics library ii perl5.8.8-7 Larry Wall's Practical Extraction ii zlib1g 1:1.2.3-15 compression library - runtime Versions of packages korganizer recommends: ii kghostview4:3.5.6-2 PostScript viewer for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425364: Restarting KDE solved it -- still a bug!
Had the same problem on my laptop, but there it disappeared after a reboot. I then also restarted KDE on my always on desktop computer, and now the problem disappeared as well. Apparently, a recent upgrade in one or more of the KDE packages requires a restart of KDE, but none was indicated -- still a bug, in my opinion. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398351: qemu -- release mouse/keyboard with Ctl-Alt
This is likely not a bug, but may be due to the OP reassigning the Ctl or the Alt key in Keyboard Layout. For example, changing the left Alt key to produce ISO_Level3_Shift is one of the choices with which to produce a EuroSign on a standard US English keyboard. The Ctl-Left Alt key combination then fails to release the Qemu mouse/keyboard grab -- and so it should. All of this can easily be checked with xev. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419627: But how about context?
The texlive-context package depends on -pdfetex and is also not installable; will it be dropped from the Debianized packages for TeXLive2007 as well? -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407574: kdvi should *recommend* texlive-fonts-recommended, not *depend* on it!
In the old version 4:3.5.5-3 kdvi recommended the now obsolete tetex-bin. The new version 4:3.5.6-2 depends on texlive -fonts-recommended, which also pulls in texlive-common, -base, and -base-bin. These dependencies may not be wanted, as in my own case where I have already installed TeXLive2007 directly from the TUG distro in my /usr/local/texlive/2007 tree. I can live with kdvi *recommending* texlive package(s), but not with *depending* on them. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407574: Texlive dependencies
Making a bunch of texlive packages dependencies of kdvi only makes sense if kdvi is an optional package in KDE. But, as things stand now, kdvi cannot be removed without removing all of kde... So much for choice, huh? -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420297: kdegraphics should no longer depend on kdvi
Package: kdegraphics Version:4:3.5.6-2 The kdegraphics package depends on kdvi. The kdvi package 4:3.5.6-2 recommended the now obsolete tetex-bin package. Version 4:3.5.6-2 has replaced this with texlive-fonts-recommended and made this a dependency as well, which in turn pulls in a TeX system: texlive-common, -base, -base-bin and -doc-base (and may be more), together a download of more than 100MB. This seems a bit much for KDE users who don't use TeX, and leads to a sizable duplication for those (like myself) who elect to install TeXLive straight from the TUG distro (if only to avoid lengthy upgrades with multiple runnings of mktexlsr, updmap-sys and format generation). The kdvi maintainer considers *not* having the above texlive dependencies a bug (see message under bug 407574 dated 21 April 2007), but this clearly only affects users of kdvi and the texlive packages. It seems reasonable, in view of the above, that kdvi be removed as a dependency of kdegraphics. Habitual users of kdvi should have no trouble installing this package on their own. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418687: Pommed: undefined symbol in libsmbios
Package: pommed Version: 1.2~dfsg-1 Dependency: libsmbios1 Version:0.13.4-1 Pommed fails to start (with sudo /etc/init.d/pommed start) on my MacBook (CD, 1.83GHz) with the error message: Starting pommed: /usr/sbin/pommed: Symbol lookup error: /usr/lib/libsmbios.so.1: undefined symbol: __cxa_pure_virtual Restarting with sudo /etc/init.d/pommed/restart gives no error message, but the special keys don't work in that case. When reinstalling 'pommed', the same error message appears, followed by invoke-rc.d: initscript pommed, action start failed. I'm running a current Debian unstable (Sid) with 2.6.18-4-686 kernel (version 2.6.18.dfsg.1-12). I upgraded to Sid from Etch just recently (2 April 2007), running the same kernel, where I had installed the above 'pommed' and 'libsmbios1' (as well as the 'libconfuse0' dependency) manually, since these are not available in Etch. Pommed then ran fine, with all the F1--F5 and Eject keys working. Even some months before that I had the 'mbpeventd' package similarly working fine. Julien Blache says in answer to some other bug that kernel 2.6.19 is required for 'pommed' to run, but that has not been my experience on the original MacBook CoreDuo. The above problem seems related to the dependency package 'libsmbios1'. -- Henk Koster Behavioral axioms are right, but agents make mistakes. Attributed to L.J. Savage -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
