Bug#708812: [Aptitude-devel] Bug#708812: [aptitude] aptitude segfaults upon being called.
On Tue, Jun 18, 2013 at 5:22 PM, Axel Beckert a...@debian.org wrote: ... Was that today's upgrade on Wheezy or on Sid? (Or asked the other way round: Does this bug affect Stable or Unstable?) On unstable (sid). -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708812: [Aptitude-devel] Bug#708812: [aptitude] aptitude segfaults upon being called.
On Tue, Jun 18, 2013 at 5:14 PM, Axel Beckert a...@debian.org wrote: ... Any chance to figure out which dependencies of aptitude were upgraded during that run? The backtrace wasn't as helpful as expected. (Yeah, I know it's late for that question, but maybe either aptitude's, apt's or dpkg's logs are still there and can answer that question.) I'm afraid not, sorry... There was one other person reporting the same issue, perhaps he might be able to provide logs on that particular run. -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614252: qemu -enable-kvm freezes
On Sun, Feb 20, 2011 at 12:39 PM, Vagrant Cascadian vagr...@freegeek.org wrote: On Sun, Feb 20, 2011 at 11:24:16AM -0600, Javier Vasquez wrote: ... i know you've tried a variety of commandline options, but what about just using the defaults with -enable-kvm? If I don't specify cpu it doesn't work, the only NIC that works is rtl8139, and with the virtio drivers then the virtio NIC as well. At the beginning I didn't require to use virtio scsi storage for disks, but now it's a must, otherwise, as I indicated before, the guest just freezes with high cpu utilization. In other words, little room I see to make more variations on the parameters to the qemu command line, and for sure defaults don't work for this XP image, which is a HP-COE one. BTW. ... do you have other hardware you can test with? -enable-kvm seems to work for me on i386, at least. Unfortunately not, :-( are you able to boot a different OS? i've only tested with Debian/GNU Linux or Debian/GNU kFreeBSD. You mean guest OS? Nope I haven't tried other guests, and can't run on different host either any ways, :-) live well, vagrant Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614252: qemu -enable-kvm freezes
On Mon, Feb 21, 2011 at 11:29 AM, Javier Vasquez j.e.vasque...@gmail.com wrote: On Sun, Feb 20, 2011 at 12:39 PM, Vagrant Cascadian vagr...@freegeek.org wrote: On Sun, Feb 20, 2011 at 11:24:16AM -0600, Javier Vasquez wrote: ... i know you've tried a variety of commandline options, but what about just using the defaults with -enable-kvm? In other words, little room I see to make more variations on the parameters to the qemu command line, and for sure defaults don't work ... Hmm, found the issue, :-) If I do not specify VGA driver at all, meaning I do not use vga=std or vga=vmware, things work as expected needing no change in any other parameter. So, it really was the VGA driver the one making qemu -enable-kvm not to work. As it was mentioned it was not the issue, I got insisting on other things like the virtio drivers, cpu, driver, sound driver, etc... But the suggestion of using defaults helped, since it entitled me to challenge the VGA driver... Any ways, the cyrrus driver used by default is really bad. It provides just too few configurations, an the max resolution I can get is 1280x1024 @ 16 bits color depth. Not only that is bad, but also I can't use a resolution at least proportional to the one in the host (1920x1200) so that I can expand it proportionally to the available space... So now, at least I can work with qemu-kvm again, but with very poor VGA driver. BTW, I'm wondering why there's no such a driver that auto configures resolution keeping high color depth, like virtualbox' one... So one just resizes the guest screen, and the resolution gets automatically adjusted as with NX as well, the the font can get adjusted for the common size, :-) Any ways, I still see a bug in here, by not supporting -vga std, neither -vga vmware, but I'd say the bug is no longer that severe, and it can be renamed (no idea how to do any of those things), :-)... Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614252: qemu -enable-kvm freezes
Subject: qemu -enable-kvm freezes Package: qemu Version: 0.14.0+dfsg-2 Justification: renders package unusable Severity: grave *** Please type your report below this line *** On an amd64 laptop (debian unstable) I've been using qemu with the following arguments (with windows XP guest): ARGS_GEN=-enable-kvm -drive file=$1,if=virtio -boot order=c -m 512 -rtc base=localtime ARGS_NET=-net nic -net tap,ifname=tap0,script=no,downscript=no ARGS_BIOS0=-smbios file=/home/vasqueja/.qemu_kvm/bios_bin/smbios_type_0.bin ARGS_BIOS1=-smbios file=/home/vasqueja/.qemu_kvm/bios_bin/smbios_type_1.bin ARGS_VGA=-vga std ARGS_AUDIO=-soundhw ac97 ARGS_USB=-usb -usbdevice tablet ARGS_CPU=-cpu athlon ARGS_NIC=-net nic,model=virtio qemu $ARGS_GEN $ARGS_NET $ARGS_BIOS0 $ARGS_BIOS1 $ARGS_VGA $ARGS_AUDIO $ARGS_USB $ARGS_CPU $ARGS_NIC Where $1 is provided as the qcow2 windows XP image. And it just with no action at all. As I was getting the following verbose print outs: qemu: pci_add_option_rom: failed to find romfile vgabios-stdvga.bin qemu: virtio_ioport_write: unexpected address 0x13 value 0x1 Initially I thought it was because I was using virtio driver for IO storage and NIC, then I changed that to use just plane -hda $1 and NIC model rtl8139 which work, but are necessary, since without the virtio NIC the guest will eventually freeze will the CPU consuming 100%... However by not using virtio drivers, the phenomena still shows up. Then I tried just removing the STD vga driver, and instead using the vmware (already installed in the guest) driver, and combinations of virtio drivers and vga ones, and nothing seems to work. I'm filing this against qemu package then, since not sure about the origin, but it seems not possible to load the guest client... The laptop is HP compaq 8510w... Notice as I'm using nouveau xorg driver version 1:0.0.16+git20101210+8bb8231-2, I can only use linux-image 2.6.37-1 (unstable default) and can't try the 2.6.32, so I can't test the kvm modules on older kernel... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-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/dash Versions of packages qemu depends on: ii qemu-system0.14.0+dfsg-2 QEMU full system emulation binarie ii qemu-user 0.14.0+dfsg-2 QEMU user mode emulation binaries ii qemu-utils 0.14.0+dfsg-2 QEMU utilities qemu recommends no packages. Versions of packages qemu suggests: pn qemu-user-static none (no description available) -- no debconf information % uname -a Linux jvasquez14 2.6.37-1-amd64 #1 SMP Tue Feb 15 17:43:38 UTC 2011 x86_64 GNU/Linux Thanks -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590817: evolution-mapi: Package is uninstallable, please update to 0.30.x
Hi, I think the latest evolution-mapi is 0.30.3, at least according to: http://ftp.acc.umu.se/pub/GNOME/sources/evolution-mapi/0.30 Under AUR for archLinux, I can see it depends upon openchange 0.9: http://aur.archlinux.org/packages/evolution-mapi/evolution-mapi/PKGBUILD And I see that openchange 0.9 is already the latest version upstream: http://www.openchange.org/index.php?option=com_phocadownloadview=categoryid=1:releases And it's already used in archLinux AUR as upstream version: http://aur.archlinux.org/packages/openchange/openchange/PKGBUILD So if there was a need for openchange 0.9 to be released, it already have. If there was a need for a different openchange version, I think that's not necessary with openchange 0.9... So perhaps now it can be uipgraded to 0.30.3, :-) -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
Answering to myself, :-) The keys file generated automatically, when starting fluxbox with no ~/.fluxbox directory present seems to work OK, as it was suggested previously. I just couldn't use the old ~/.fluxbox/keys since it got it overrided witht the /etc/X11/fluxbox/keys... Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
OK to me. Thanks... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
One more thing missing (didn't notice before). I can't resize any window application at all from the left/right bottom corners with left mouse. Is there any particular configuration for that? Attaching keys configuration file copied from /etc/X11/fluxbox, andmodified so that alt-left alt-right is all nedded to move to prev/next work spaces (desktops)... keys Description: Binary data
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
Package: fluxbox Version: 1.1.1+git20100807.0cc08f9-1 Severity: serious The recent upgraded fluxbox on unstable does not allow moving window applications inside a window desktop through pressing left mouse button and moving the window around. It's still possible to use the middle button, which is not present on every mouse, but the behaviour is different than the left button, since the application window is hidden, leaving just the application bar, and the movement is more limited than with left button. % uname -a Linux jvasquez14 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592904: Latest fluxbox package on debian gnu/linux unstable breaks moving objects around the window with left bottom.
Reporting back that: OnTitlebar Mouse1 :StartMoving Actually fixed the issue. So it was a matter of changing the configuration file as mentioned. Perhaps this can be closed then as a user configuration issue. As mentioned fixing /etc/X11/fluxbox/keys doesn't fix ~/.fluxbox/keys, but a key learning for users might be to always compare configuration files against global ones when upgrades happen. Thanks for quick response... Javier. On 8/13/10, Paul Tagliamonte paul...@ubuntu.com wrote: retitle: Fluxbox's upstrem changes break old configuration files thanks Just going to reset the title to something more descriptive of what the issue is Thanks, Paul On Fri, Aug 13, 2010 at 4:21 PM, Paul Tagliamonte paul...@ubuntu.com wrote: Confirmed This happens because in 1.1.1 release, this was default behavior. Upstream decided to change this for the next release. To keep behavior standard, I patched the default config file to enable left click dragging. This does not carry over into the ~/.fluxbox/keys file, even though this option is in /etc/X11/fluxbox. One fix is to remove the .fluxbox directory and restart fluxbox. This is not acceptable for people who have very complex setups, but then again, if they have complex setups, they should be able to set this manually. -Paul On Fri, Aug 13, 2010 at 4:09 PM, Paul Tagliamonte paul...@ubuntu.com wrote: severity: important justification: alt + move should still work, and middle click ( emulated by left + right ) thanks The more I think about this, the more I think this is a migration issue for old packages. Retagging to important. -Paul On Fri, Aug 13, 2010 at 4:00 PM, Paul Tagliamonte paul...@ubuntu.com wrote: Hey Javier, Were you running fluxbox before? This could be due to a small issue with the git tree. This should not affect anyone just installing. Try adding this to your keys file OnTitlebar Mouse1 :StartMoving Please do follow up with this -Paul On Fri, Aug 13, 2010 at 3:38 PM, Javier Vasquez j.e.vasque...@gmail.com wrote: Package: fluxbox Version: 1.1.1+git20100807.0cc08f9-1 Severity: serious The recent upgraded fluxbox on unstable does not allow moving window applications inside a window desktop through pressing left mouse button and moving the window around. It's still possible to use the middle button, which is not present on every mouse, but the behaviour is different than the left button, since the application window is hidden, leaving just the application bar, and the movement is more limited than with left button. % uname -a Linux jvasquez14 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux -- #define sizeof(x) rand() :wq -- #define sizeof(x) rand() :wq -- #define sizeof(x) rand() :wq -- #define sizeof(x) rand() :wq -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
