Bug#1032517: nginx settings deleted on upgrade

Package: nginx Version: 1.22.1-7 Severity: grave Justification: causes non-serious data loss Dear Maintainer, last weekend I did an "apt upgrade" of my system as usual, asking apt to prune configuration files for packages that are being uninstalled. Now I realize that my nginx stopped working,

Bug#986662: ossp-padsp not working with recent Pulseaudio

Hi all, Meanwhile, the version of osspd that I had uploaded a while ago finally got accepted to unstable. :) When we prepared the fix, we were not aware that this would become an RC bug, so we didn't strive for a minimal fix. Okay. Then I'll open a bugreport with release.debian.org and ask

Bug#986662: ossp-padsp not working with recent Pulseaudio

Hi Sergei, When we prepared the fix, we were not aware that this would become an RC bug, so we didn't strive for a minimal fix. Okay. Then I'll open a bugreport with release.debian.org and ask if this not so minimal update can propagate to testing. If yes, I'll reupload it. That sounds

Bug#986662: ossp-padsp not working with recent Pulseaudio

Hi Sergei, Our current problem is that we cannot even upload the package to unstable since my key in the debian keyring expired (and the updated key missed the April keyring update), and Sebastien is not yet allowed to upload osspd. I've done the upload before figuring this out, so now

Bug#947076: xchat.desktop file has invalid Exec line (at least for KDE)

Package: xchat Version: 2.8.8-18 Severity: grave Justification: renders package unusable Dear Maintainer, since the most recent update, trying to start xchat via the KDE launcher just shows an error: Error processeing Exec field in /usr/share/applications/xchat.desktop And indeed that

Bug#930232: vlc: No video output in any video

Package: vlc Version: 3.0.7-1 Severity: grave Justification: renders package unusable Dear Maintainer, No matter which video file I try to open with VLC, VLC fails to display any image. All I get is a flickering VLC icon. I will attach a "-vv" log for one of the many files that I tried. The

Bug#930213: bzr: "bzr branch" fails: NameError: global name 'self' is not defined

Package: bzr Version: 2.7.0+bzr6622-15 Severity: grave Justification: renders package unusable Dear Maintainer, The command `bzr branch lp:mailman/2.1` (which https://code.launchpad.net/~mailman-coders/mailman/2.1 tells me to run to get the mailman source code) fails, with the following error:

Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

Package: libvirt0 Version: 5.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, After a recent upgrade, IPv6 communication between a virtual router and another virtual client over an isolated network stopped working. I am seeing the rotuer advertisments sent by the

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

Oh, I should probably also mention that these machines all run an extra kernel module compiled via dkms: batman-adv 2019.0 from . The same kernel module also runs on a fourth machine with the same setup, but which hasn't gotten the kernel update yet, and that machine

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

Package: linux-image-4.9.0-8-amd64 Version: 4.9.144-3 Severity: critical Justification: breaks the whole system Dear Maintainer, after installing the kernel updates that got released to Debian stable earlier today or yesterday, we saw all the three updated systems fail in the same way: after

Bug#917217: npm breaks other packages' bash-completion

Hi, > I don't see such a line here. > https://salsa.debian.org/js-team/npm/blob/master/lib/utils/completion.sh > > May be that came from an older version? Can you purge npm, reinstall and > confirm > if you still see it? I just extracted the package and to my surprise found the file somewhere

Bug#916231: Including sys/ioctl.h helps

Hi Sergei, thanks a lot! At least it still builds here, so I just made an upload with this fix. Kind regards, Ralf On 25.12.18 12:34, Sergei Golovan wrote: > Hey Ralf, > > Including sys/ioctl.h into ossp.h doesn't help as it is included into > osspd.c too late (sys/socket.h already did harm

Bug#917217: npm breaks other packages' bash-completion

Package: npm Version: 5.8.0+ds6-2 Severity: critical Justification: breaks unrelated software Dear Maintainer, installing npm breaks bash-completion for other packages, for example dd. You can reproduce this by typing "dd if=", typing the beginning of a filename and then hitting "Tab". Now the

Bug#891434: grub-efi: System fails to boot after "No space left on device" on EFI variable storage

Hi, > Fixing this does seem like it would be a good idea for general > robustness against dodgy firmware (this is not the first iteration of > problems along these lines). It would take some development work, but > hopefully not too much. > > Things that GRUB can't do, as far as I can tell: >

Bug#916231: osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared

Hi again, > I found https://patchwork.ozlabs.org/patch/740563/ via some googling. It > mentions MIPS, so it might be related? As a random guess, could you try adding #include at the top of "ossp.h" and see if that makes a difference? It seems that this now somehow triggers the logic in

Bug#916231: osspd FTBFS on mips: osspd.c:769:15: error: 'IOC_IN' undeclared

Hi, > While trying to cross build osspd for mips, I ran into a failure that I > could reproduce natively on minkus.d.o, but not on amd64. I suspect this > is related to glibc/2.28. A build ends with: > > | gcc -Wall -pthread -g -O2 -fdebug-prefix-map=/home/helmutg/osspd-1.3.2=. >

Bug#891434: grub-efi: System fails to boot after "No space left on device" on EFI variable storage

Just had this again, this time even after I repaired Debian, Windows disappeared completely from the start menu. I do not yet know how to get it back. What does it take to get attention t a bug that completely breaks the system? Kind regards, Ralf

Bug#898767: linux-image-4.16.0-1-amd64: (temporary, unreliable) hang on boot since upgrade to 4.16

Package: src:linux Version: 4.16.5-1 Severity: grave Justification: renders package unusable Dear Maintainer, since the upgrade to kerkenl 4.16, the system does not boot reliably any more. Instead, most of the time, it hangs showing the following messages: [2.639465] nouveau :01:00.0:

Bug#891434: grub-efi: System fails to boot after "No space left on device" on EFI variable storage

Package: grub-efi Version: 2.02+dfsg1-1 Severity: critical Justification: breaks the whole system Dear Maintainer, earlier today I did a system update, which completed successfully (as in, dpkg didn't stop due to an error). I then rebooted my machine. This left Linux unable to boot; only the

Bug#875030: libkdewebkit5/libplasma3 removal from buster

Hi, I filed a removal request for lightdm-kde at . ; Ralf

Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

Hi Dmitry, > Emilio has scheduled a lxqt-plugin rebuild now, so I am closing this bug. > > I still hope to be able to refactor the Qt side of this so that platform > plugins do not need to link against the private static library, but this > is not a trivial issue. > > See discussions at [1]

Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

Hi again, I managed to fix the crashes by re-building lxqt-qtplugin against current unstable. The bug this clearly is in lxqt-plugin, reported as #843512. Still, Qt 5.7 should probably not transition to testing without a new version of lxqt-plugin. Kind regards, Ralf

Bug#843512: lxqt-qtplugin: Needs dependency on qtbase-abi, needs rebuild for Qt 5.7

Package: lxqt-qtplugin Version: 0.11.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, the package lacks a dependency on qtbase-abi-5-X-Y. As a consequence, after upgrading to Qt 5.7 (currently in unstabled), many Qt applications crash on startup. For some

Bug#843511: libqt5widgets5: Some Qt applications segfault on startup

Package: libqt5widgets5 Version: 5.7.1~20161021+dfsg-5 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading to Qt 5.7, some applications fail to launch an segfault instead. For example, here's lxqt-powermanagement: #0 0x in ?? () #1

Bug#800586: camorama cannot take pictures

severity 800586 important thanks Hi, > package: camorama > version: 0.19-3 > severity: grave > reason: fails its primary functionality > > It fails with an error message "Cannot create directory ~/Webcam_Picture > s" > > Same message after manually creating the directory. Taking pictures is

Bug#798865: Re: Re: hugin: Stitching fails when project folder path contains umlaut ("ö")

Hi, sorry I didn't see this mail; it was sent to the bug, but not to me. > Is this a new installation or did you upgrade from a prior version of > hugin? If so, did you reset the preferences for the control points > detectors (File -> Preferences -> Control Points Editor, press "Load >

Bug#725284: proper resume hooks

And in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780956 the dev showed that udev already has proper hooks for resume events. So these may be proper mechanisms for packages to ship with a resume hook. And the last one is already tried and proven by laptop-mode-tools. Looking

Bug#725284: proper resume hooks

Hi, In the face of the race condition with systemd unit files, reported by Michael Biebl, there seem to exist different alternatives. Lennart Poettering: https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=nobug=744753#40 a service which needs to be restarted on cases like this

Bug#782456: [Pkg-xfce-devel] Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

Hi, it doesn't look related to lightdm. At least other daemons seems to fail to start as well. From the initial report, virtualbox and postfix have issues as well. I don't think these errors come from postfix or VirtualBox. I rather think that immediately after printing Apr 12 13:48:56

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

Hi, This doesn't guarantee that the service is run on resume. Those targets are activated on suspend/hibernate, so there is a race and you might actually run /usr/lib/pm-utils/power.d/95hdparm-apm *before* the system is suspended. You'd have to order this service after the *service* which

Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

Hi all, I finally had the time to experiment a bit more. Here are my latest findings: I removed all non-Debian kernels, just to be sure. Immediately after enabling splash in grub again, the behavior of lightdm always fails to start reappeared. Then I changed plymouth to text mode, re-generated

Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

Package: plymouth Version: 0.9.0-9 Severity: critical Justification: breaks unrelated software Dear Maintainer, since I installed plymouth, starting the DM (lightdm) on boot sometimes fails. In about 10% (rather more than less) of the cases, the screen only flickers shortly when lightdm should

Bug#782456: With plymouth installed, starting the DM now always fails

Hi again, I have to revise my in 10% of the cases from above: I now have this problem pretty for on every boot (~10 times in a row). I do not know why this starts happening now. I recently installed plymouth-x11, but I removed that again, which did not help. I also recently compiled lots of

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

Hi, The specific one you posted above could probably use oneshot: [Service] Type=oneshot Thanks! I'm not sure if I want anything to wait for hdparm being done with this (which seems to be the only consequence), but in any case it sounds more appropriate to what that unit is doing. Kind

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

Hi again, I did some quick debugging, and it seems like the script /lib/udev/hdparm is never even run on suspend-resume. I'm not really familiar with udev, so I don't know whether udev just doesn't trigger after a resume, or whether there's some other problem here. The second mail in this bug

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

Hi again, sorry for the noise. This is just to confirm that there simply is no event for the disks on resume: $ sudo udevadm monitor -uk monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[49453.633973]

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

Hi, I just uploaded 9.43-2 with the patch mentioned in this bug report. However, I lack the hardware to test hdparm. So please test it before I file an unblock request. This doesn't seem to work: After suspend-resume, my disk behaves as if hdparm was not run at all. I did not yet investigate

Bug#744753: Fix for anacron (running on resume under systemd)

Hi, It *also* has After=sleep.target. That means, depending on the timing, anacron-resume.service might be triggered just before suspend not on resume, and it's not guaranteed that anacron has finished before systemd-sleep is called. I don't think the patch was intended this way? I was

Bug#771719: closed by Laszlo Boszormenyi (GCS) g...@debian.org (Bug#771719: fixed in tcplay 1.1-2)

Hi, #771719: tcplay: does not support discs with 4k sectors It has been closed by Laszlo Boszormenyi (GCS) g...@debian.org. Please report back if it really fixes your issue or not. I can confirm that my issue is fixed: I successfully mounted the partition, wrote some stuff to it, booted

Bug#771719: tcplay: does not support discs with 4k sectors

Hi László, Yes, it seems it was fixed in 2.0, but it has a somewhat unclear license. Ouch. Do you have a pointer to the issue? I've backported the fix for 1.1. But don't have any 4k discs nearby, can you test it for me? You should build it for yourself[1] and only in the last chance use

Bug#771719: tcplay: does not support discs with 4k sectors

Package: tcplay Version: 1.1-1+b1 Severity: critical Tags: upstream Justification: causes serious data loss Dear Maintainer, tcplay does not properly support discs with 4k sectors: They are opened, but reading from the disc produces wrong results, and writing to the discs results in data the

Bug#771515: monodevelop-nunit: Plugin is not installed properly and does not work

Package: monodevelop-nunit Version: 4.0.12+dfsg-5 Severity: grave Justification: renders package unusable Dear Maintainer, the monodevelop-nunit package as it is in Jessie currently is not usable: After installing it, the plugin does not apepar in monodevelop. Manually runnng mdtool shows: $

Bug#761245: Debian icedove: TLS

Hi, propably you are right. I haven't yet any problems depending on this bug report. But I'm also no professional for anything related to mail server and there configuration. Unfortunately the exim maintainers haven't say something about this topic, so yes, maybe the conclusion in the NEWS

Bug#761245: Debian icedove: TLS

Dear Carsten, in the NEWS file of the latest Icedove package in Debian, you are writing: This means every connection from Thunderbird/Icedove to a mail server will using TLS 1.2 with no fall back if you have configured TLS/SSL or STARTTLS for your connections. Some users reported

Bug#765540: grub2: symbol 'grub_term_highlight_color' not found

Hi, Actually, I still have no idea how to do the latter. I assume the dpkg-reconfigure you mentioned will do that, but I currently don't feel like breaking my boot again ;-) Indeed running dpkg-reconfigure grub-pc and telling it to install grub on both /dev/sda and /dev/sdb fixed the problem.

Bug#765540: grub2: symbol 'grub_term_highlight_color' not found

Package: grub2 Version: 2.02~beta2-14 Followup-For: Bug #765540 Dear Maintainer, my system became unbootable after upgraind from grub 2.00-22 to 2.02~beta2-14 with the error message symbol 'grub_term_highlight_color' not found I had to boot a rescue system and downgrade grub again to fix

Bug#765540: grub2: symbol 'grub_term_highlight_color' not found

Hi again, Regarding my setup, I have two disks in my laptop. /dev/sda in the HDD that was shipped with the machine, which I originally installed Debian on. Later, I added an SSD /dev/sdb and moved Debian to it. However, as far as I remember, the machine is still booting from the HDD

Bug#751049: proofgeneral: FTBFS - pdfetex (file cm-super-t1.enc): cannot open encoding file for reading

Hi, As he said, it can be built fine now. (Probably changes in TeX caused this build failure but now it was gone...) So, tagged as unreproducible. Is this still RC? Currently, this bug will prevent proofgeneral from becoming part of Jessie, which would be a pity. Kind regards Ralf --

Bug#763971: mysql-workbench: Conncting through an SSH tunnel does not work

Package: mysql-workbench Version: 6.1.7+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, MySQL Workbench fails to connect to my MySQL installations through an SSH tunnel. Instead, I get the following error: Your connection attempt failed for user 'root' from your

Bug#743128: [Pkg-utopia-maintainers] Bug#743128: network-manager: NM does not work (without systemd)

Hi, In any case, as NM just Recommends: systemd, it should still be functional without using systemd. You are right. I will switch that to Depends: systemd-sysv. I can by now confirm that my issues are systemd-related: When booting my machine with systemd, everything behaves as expected.

Bug#743128: [Pkg-utopia-maintainers] Bug#743128: network-manager: NM does not work (without systemd)

Hi, We do have some patches which make systemd-logind work standalone, i.e. withouth PID 1 = systemd. systemd-logind is a replacement for ConsoleKit and used for session and user tracking. However, with systemd 208 and later those patches no longer work. So you'll need systemd to be PID 1.

Bug#743128: network-manager: NM does not work (without systemd)

Package: network-manager Version: 0.9.8.8-4 Severity: grave Justification: renders package unusable Dear Maintainer, the current unstable version of NM does not work: The NM frontend does not show any connections (even though NM prints to syslog that they were loaded from /etc/NetworkManager).

Bug#739297: python-glpk: import glpk does not work: shared library cannot be found

Package: python-glpk Version: 0.4.52-1.1 Severity: grave Justification: renders package unusable Dear Maintainer, the glpk module does not work. If I run import glpk, I get $ python Python 2.7.6 (default, Jan 11 2014, 14:34:26) [GCC 4.8.2] on linux2 Type help, copyright, credits or license for

Bug#730930: [Pkg-kde-extras] Bug#730930: lightdm-kde: FTBFS: configure errors

tags -1 - jessie thanks -- checking for module 'liblightdm-qt-2=1.4.0' -- package 'liblightdm-qt-2=1.4.0' not found It looks like lightdm-1.8 bumped the soversion of liblightdm-qt, so now reverse dependencies fail to build. However, jessie is not (yet) affected as the package did not (yet)

Bug#727555: Re: python-qt4: Crashes plasma-desktop on startup

Hi, Try these packages http://mb1.pl/~qba/python/ compiled against new python-sip libs. I do not want to partially upgrade my production system to KDE 4.11, so I cannot test these packages. Instead I tried to re-build python-kde4 in testing, but that did not work. It failed to build: In file

Bug#727555: python-qt4: Crashes plasma-desktop on startup

Package: python-qt4 Version: 4.10.3-2 Severity: critical Justification: breaks unrelated software Dear Maintainer, upgrading python-qt4 to 4.10.3-2 and python-sip to 4.15.2-2 makes plasma-desktop crash on startup. I downgraded both back to their previous versions, now it's working again.

Bug#727555: python-qt4: Crashes plasma-desktop on startup

Hi again, some more information: * Just upgrading python-sip (and leaving python-qt4 at the old version) also triggers the crash. * Uninstalling veromix fixes the crash. * I attached the backtrace. Kind regards Ralf Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation

Bug#725087: ntfsclone: Fails to restore image

Package: ntfs-3g Version: 1:2013.1.13AR.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, ntfsclone fails to restore images created with the recommended special image format. To reproduce, simply create an image of a partition (like the small 100MiB Windows boot

Bug#725087: ntfsclone: Fails to restore image

Package: ntfs-3g Version: 1:2013.1.13AR.2-3 Followup-For: Bug #725087 I just verified that the bug is also present in the package from experimental. Kind regards Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#722481: python-git: Fails to work with git RC versions

Package: python-git Version: 0.3.2~RC1-2 Severity: grave Justification: renders package unusable Dear Maintainer, python-git does not work at all anymore since I upgraded git to 1.8.4.rc3. The backtrace says File /usr/lib/python2.7/dist-packages/git/remote.py, line 79, in add_progress v

Bug#711623: ssh-agent: Removes LD_LIBRARY_PATH from environment

Package: openssh-client Version: 1:6.2p2-3 Severity: critical Justification: breaks unrelated software Dear Maintainer, ssh-agent removes the $LD_LIBRARY_PATH from the environment it was started in. This is fatal, for example when starting a session with a desktop installed to a different

Bug#704521: marked as done (virtuoso-opensource-6.1: Virtuoso server stop script fails to stop server cleanly, potentially causing database corruption)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks a lot for the upload and the fast unblock :) Kind regards, Ralf -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

Bug#704521: virtuoso-opensource-6.1: use start-stop-daemon flags instead

We have a patch waiting for pre-approval at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704833 Kind regards, Ralf On 15/04/13 21:47, Tomas Pospisek wrote: Frode Severin Hatlevik writes: When calling '/etc/init.d/virtuoso-opensource-6.1 stop', virtuoso may still be running after the

Bug#694253: kde-workspace-bin fails to configure: Can not copy kcmclockrc

Package: kde-workspace-bin Version: 4:4.8.4-4 Severity: serious Justification: Policy 3.9 Dear Maintainer, kde-workspace-bn fails to install on my system. I get the following error message: Setting up kde-workspace-bin (4:4.8.4-4) ... mv: cannot move ‘/usr/share/kde4/config/kcmclockrc’ to

Bug#686033: libgl1-nvidia-glx:i386 is now co-installable with :amd64 (in sid and experimental)

Hi, I can confirm that your hacked package installed correctly here on my 64-bit sid system, with no destruction to the nvidia driver: Indeed, I was able to unisntall my custom libxvmc packages. A simple aptitude install does not immediately work as aptitude wants to pull the recommends in, but

Bug#686033: libgl1-nvidia-glx: 304.37-1 libgl1-nvidia-glx:i386, removes libgl1-nvidia-glx (amd64) and Nvidia driver

Hi, I can confirm that the patch by you, Andreas, is working fine. The problems with the conffile are caused by a bug in dpkg [1] and there are other packages triggering it, like libpam-modules. Which dpkg versions are affected? Current unstable and sid. Guillem is aware of the issue (as

Bug#684776: Re: Bug#684776: dpkg incorrectly complains about conffile contents being different for MA packages

Hi again, (sorry if you got this mail twice, my email program is acting strange) Yeah, reproduced here, and looking into it right now. I have a hunch I've already fixed this in my 1.17.x branch, though. Ok, I fixed this locally and been running some tests, will do some more tests and

Bug#686033: libgl1-nvidia-glx: 304.37-1 libgl1-nvidia-glx:i386, removes libgl1-nvidia-glx (amd64) and Nvidia driver

Hi, Current unstable and sid. probably wheezy and sid which both have dpkg 1.16.8 Uhm, sorry, you are right of course. To avoid this bug, there is still a possibility to split out a -common package. The bug is only triggered by calling dpkg with both architectures of the package at once,

Bug#686033: libgl1-nvidia-glx: 304.37-1 libgl1-nvidia-glx:i386, removes libgl1-nvidia-glx (amd64) and Nvidia driver

Hi, with the 304 drivers in current unstable, this bug even means that 32bit apps get no acceleration at all since the ia32 packages have already been removed. I can confirm that the patch by you, Andreas, is working fine. The problems with the conffile are caused by a bug in dpkg [1] and there

Bug#684776: dpkg incorrectly complains about conffile contents being different for MA packages

Hi, Yeah, reproduced here, and looking into it right now. I have a hunch I've already fixed this in my 1.17.x branch, though. Ok, I fixed this locally and been running some tests, will do some more tests and ponder a bit about the implications of the fix before pushing to master. Thanks

Bug#679687: plymouth: initramfs hook fails to find renderers with multi-arch

Hi, I am also hit by this bug, it seems: During the upgrade I just ran on my Debian unstable machine, I got this error: update-initramfs: Generating /boot/initrd.img-3.2.0-3-amd64 E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for

Bug#676686: [xml/sgml-pkgs] Bug#676686: libxslt1.1: libxslt1.1 binNMU broke multi-arch installability

Hi, True, but seems to be a problem for other paties involved to M-A, for example the buildd binNMU and dpkg handling. I'll clone this bug for them. Yeah, binNMU and MA don't seem to combine well so far. For libxslt, I'll make an upload soon when I come back - roughly after 12th, to try to

Bug#671320: [Pkg-fglrx-devel] Bug#671320: fglrx-driver: due to dependencies, uninstallable with current xorg in sid

Hi, fglrx 12-5 will work with the new XOrg, but Support for your card is also dropped with 12-5, to be exactly with 12-5 fglrx will not work with R6xx and R7xx ASICs anymore, so you might switch to the radeon driver, now. where did you get this from? I read somewhere that AMD plans to

Bug#671882: virtuoso-opensource: vanished in testing, please bring it back

.) Yes, it does (the package is kde-runtime, not libnepomuk4 as I originally thought, which just has a suggests). Kind regards, Ralf Jung -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable

Package: libnepomuk4 Version: 4:4.7.4-4 Severity: grave Justification: renders package unusable Virtuoso is missing from testing, and without it, Nepomuk does not work (also see [1]). As I had to find out the hard way [2], reporting this against Virtuoso is wrong (sorry for the multiple bug

Bug#671882: virtuoso-opensource: vanished in testing, please bring it back

Source: virtuoso-opensource Version: 6.1.3+dfsg1-2.1 Severity: serious Dear Maintainer, virtuoso-opensource recently vanished from testing [1]. This is especially problematic since the KDE service Nepomuk (required for all the semantic desktop features) does not work without virtuoso [2].

Bug#656688: Thanks

I can confirm that usb-modeswitch 1.2.3+repack0-1 works great here. Thanks a lot! Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#656854: Bug#656248: Rise severity of usb-modeswitch 1.2.2 bugs

Hi, Ralf: note that #656248 _is_ closed but that you are now affected by #656854 which is a different beast, sorry. That's okay, I just wanted to make sure this is tracked somewhere, so it does not hit testing. I am using the package you created for the other bug to have a working printer

Bug#639875: Fixed

Thanks a lot, just installed the new fglrx and the Xorg update and it's all working! Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#639875: fglrx removed

Hi, is it because of this that fglrx just got removed from testing, thereby removing support for 3d acceleration on a whole lot of systems? Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#635968: installation-reports: Initial boot after installation failed

Hi, Can you verify this by clearing the boot flag you now have and seeing if your system will boot after that? Yes, I tried that: The system showed exactly the same error about not being able to find a bootable device if the boot flag is unset, and after setting it again, things now work like

Bug#635968: installation-reports: Initial boot after installation failed

Package: installation-reports Severity: grave Tags: d-i Justification: renders package unusable Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch- latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: July 27th, 2011 Machine: HP Compaq 615 Processor: