Bug#983605: dicomscope: Files missing from distribution

Package: dicomscope Version: 3.6.0-22 Severity: grave Justification: renders package unusable After attempting to install this package it does not work and various files seem to be missing. At https://packages.debian.org/bullseye/all/dicomscope/filelist I get the message "No such package in this

Bug#972281: linux-source-5.8: Fails to compile with no LKMs if no Module.symvers

Package: linux-source-5.8 Version: 5.8.10-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) When compiling a static kernel (i.e. with no LKMs), which I have done many times before, deb-pkg fails after the compiling has finished unless

Bug#875688: Reports won't run

OK, those file locations were a red herring. I am wondering if the suggestion that new reports can run is misleading. I only seem to have access to "Use wizard to create report ..." which seems to create a different sort of report not using Report Builder. I don't seem to have any facility to

Bug#875688: Existing reports won't run

I notice that reportbuilder.jar and reportbuilderwizard.jar are in /usr/lib/libreoffice/program/classes/ whereas everything else in that folder is symlinks to files in /usr/share/libreoffice/program/classes/

Bug#875688: Existing reports won't run

Same problem here, I think. I open a .odb file. I go to reports and select a report. I right click on it and select "Open" or "Edit". In each case I get the message: The document "*" could not be opened. The report, "*", requires the Oracle Report Builder feature. Further, in More

Bug#833698: Icedove 1:45.2.0-2+b1 (Debian Testing) SegFault

On Tue, 09 Aug 2016 22:48:00 + =?UTF-8?B?VmlrdG9yIErDpGdlcnNrw7xwcGVy?= wrote: Everybody who reads only this bug report, please consider my workaround mentioned in bug 833532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532#50 Thanks Viktor. I

Bug#833698: Version: 1:45.2.0-2+b1 now in testing

Version: 1:45.2.0-2+b1 was uploaded to testing last night although it does not appear in the PTS. It segfaults on start up, would this be due to this bug? John

Bug#644957: libreoffice-base: Base runs extremely slowly

Package: libreoffice-base Version: 1:3.4.3-3 Severity: grave Justification: renders package unusable I have reported this issue against openjdk-6-jre, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641537 . However the problem is even worse in LibreOffice 3.4.3-3 using openjdk-7-jre. It

Bug#644957: libreoffice-base: Base runs extremely slowly

Hi René I marked the bug as grave for LibreOffice-base (not LibreOffice) because base runs so slowly with openjdk-7-jre that it is unusable. It is not a grave bug for openjdk-7-jre because it can be used for other things. The question seems to be, how can this bug be resolved, whichever

Bug#584755: Move and edit comments unavailable

Is this bug connected with the fact that Move and edit Comments are unavailable in my version of gthumb (2.11.3 from squeeze)? John -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#577276: Starting the application.

Ah! It is easy when I know. I presume my difficulty arose from moving Alarm Clock to the notification area and it being started as a normal application. I was expecting it to still to be added to a panel in the same way as other Gnome applets. I am thinking that it would be a good idea for the

Bug#577276: alarm-clock-applet: will not run in the background

Package: alarm-clock-applet Version: 0.3.0-1 Severity: grave Tags: squeeze Justification: renders package unusable After the recent upgrade of the package the applet disappeared. At first I had some of these messages: The panel encountered a problem while loading OAFIID:AlarmClock. Do you want

Bug#577276: Does not start

OK thanks, that helps. At least I have now got the applet running. I have retitled the bug as the only reason I tried to start it from the terminal is that it did not start automatically and I was doing some problem solving. So the issue is that the application stopped automatically running

Bug#568977: Further information

Michael wrote: According to your bug report, the libraries are -2 but network-manager is -3. Please upgrade all available nm packages to -3. Sorry I did not make it clear, I realised that the libraries had not been upgraded when I started assembling the bug report. I upgraded them and

Bug#568977: After NetworkManager is stopped

wind:/home/john# service network-manager stop Stopping network connection manager: NetworkManager. wind:/home/john# nm-tool NetworkManager Tool State: unknown ** (process:3209): WARNING **: error: could not connect to NetworkManager johnwtwind:/home/john# NetworkManager --no-daemon

Bug#568977: network-manager-gnome: Shows No network connection and The network connection has been disconnected

Package: network-manager-gnome Version: 0.7.999-2 Severity: grave Justification: renders package unusable The network manager icon shows No network connection when I point to it and if I right click and disable then re-enable networking I get the disconnected message. This happened after

Bug#539359: Upgrading seems to work

I upgraded gnome-settings-daemon to version 2.26 from unstable (added unstable to sources.list, u in aptitude, + gnome-settings-daemon, it pulled in a few dependencies, particularly x-server drivers, installed, removed unstable from sources.list and u again in aptitude) And the problem seems

Bug#519773: gksu: causes errors

I am finding that I cannot now open a root terminal from gnome, nothing happens after I enter the password or if I have already done so, just nothing happens. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#511657: icedove-beagle: Indexing error, component failure

Package: icedove-beagle Version: 0.3.8-1 Severity: grave Justification: renders package unusable When I start Icedove I get a script processing error. Then Beagle starts generating the following error in Icedove window repeatedly: An error occurred while indexing. Error description :

Bug#505473: crashes when viewing www.eroski.es

Interestin. I just checked this out of curiosity and the site worked fine for me. I am using Testing with a 2.6.26 kernal that I have compiled. John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]