-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tuesday 18 May 2021, Debian Bug Tracking System was heard to say:
> This is an automatic notification regarding your Bug report
> which was filed against the wicd package:
>
> #613727: wicd should conflict with network-manager
>
> It has been clos
Dear Debian,
To further troubleshoot, I downloaded and built kernel 3.4.4 generic
from Kernel.org, built the .deb package as per "Building the kernel
the Debian way", and automount works perfectly when running 3.4.4.
I may have forgotten to mention that even CDs fail to mount while
running the De
Package: src
Version: 3.2.21-3
Severity: important
Good morning. I have updated two laptops and a desktop system with the same
result,
plugging in a USB thumb drive fails to automount, and trying to mount the device
gets the error "Permissions problem".
However, one system still has kernel 3.2.
On Wednesday 16 February 2011, David Paleino was heard to say:
> No. They can manage different interfaces :)
Oh. Well, they conflict for me. Just having NetworkManager installed
and trying to use wicd causes the network interfaces to not function
at all. They report "up" but nothing more.
> Ple
Package: wicd
Severity: wishlist
Wicd and NetworkManager conflict when installed at the same time.
The Wicd and NetworkManager programs should not be able to be installed
at the same time, but they can be.
Please add "networkmanager conflicts with wicd" and the reverse into
the Debian packaging
Package: bittornado
Version: 0.3.18-10
Severity: normal
Up to date Sid, just got this same error myself:
$ btlaunchmanycurses --max_download_rate 100 --max_upload_rate 30 --minport
1 --maxport 10020 .
/usr/lib/pymodules/python2.6/BitTornado/__init__.py:8: DeprecationWarning: the
sha module
Package: apt
Version: 0.7.25.3
Severity: wishlist
I have a broadband 'Net connection, and apt could utilize this by pulling
multiple DEB files in parallel when those files are available from multiple
repository mirrors in sources.list.
I looked through the bug reports for apt and saw several ban
Package: xfce4
Version: 4.6.1.3
Severity: important
File: xfce
Tags: squeeze
The xfce menu does not include any entry for the all-inclusive Debian
application menu. This seems new to Squeeze, since Lenny has such an
entry.
This severely impacts the usability of xfce, since there are lots of
appl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 August 2009, Patrick Matthäi was heard to say:
> severity #543529 wishlist
> thanks
Got it, I understand.
> It fails with 2.6.26? I do not think so, sorry, so I am
> downgrading.
No, you're right, I didn't know where to look to find th
First, I'm sorry. It wasn't 2.6.26, it was 2.6.30-686 and
2.6.30-amd64.
I have the two build log files here, which I will attach.
Curt-
--
The Magistrate, enrobed in taxes, condemns the thief in stolen rags.
/usr/bin/make -f debian/rules clean
make[1]: Entering directory `/usr/src/modules/f
Package: fglrx-source
Version: 1:8-12-4
Severity: important
File: fglrx
Justification: fails to build from source
When using module assistant, the fglrx-source package fails to build, with
"conflicting types for irqreturn_t", at least that is what it looks like. I
can't find the m-a log file loc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 23 June 2008, Brice Goglin was heard to say:
> There's already bug #483821 about the nvidia driver having to ship
> a nvidia.ids file so that the server can autoload the driver when
> it sees the nvidia board.
Got it, thanks.
Simply adding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 19 June 2008 it was so written:
> Hi,
>
> Curt Howland wrote:
> > Ok, it worked. However, I got an error when uninstalling, and the
>
> So your OOo works now again and this bug can be closed? :)
Yes, please. I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 18 June 2008 it was so written:
> Exactly that :) (Well, apt-get remove openoffice.org-*, apt-get
> instal openoffice.org openoffice.org-.. , or with --reinstall
> of all OOo packages, but that won't help if files in
> /etc/openoffice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 18 June 2008 it was so written:
> Also it can be that simply (because of fs errors etc) your fs (and
> therefore OOos files) became corrupted...
Ran fsck (thank you, Knoppix) as detailed as I could last night, no
problems. If there is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 18 June 2008 it was so written:
> tag 486913 + moreinfo
> tag 486913 + unreproducible
> thanks
>
> Hi,
Thanks for the questions. The fact that it is happening to no one else
is more than I got asking in Debian-user.
> Works here. The me
Package: openoffice.org-common
Version: 1:2.4.1-3
Severity: important
File: /usr/bin/ooffice
Up to date Sid. Just ran Dselect to make sure there was no further updates
today.
When trying to open any document, spreadsheet or presentation, or start
oowriter,
oocalc, etc, from the command line, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just in case it wasn't obvious, I reverted the xorg.conf to a previous
working version before filing the bug.
Curt-
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://getfiregpg.org
iQEVAwUBSDLWPi9Y35yItIgBAQIKTgf/VVxglH
Package: xserver-xorg
Version: 1:7.3+10
Severity: normal
When I try "dpkg-reconfigure xserver-xorg" the configuration for various
keyboard
options is executed, then the reconfiguration stops. The monitor, mouse and
video
card are never considered, and those areas in the /etc/X11/xorg.conf are l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The file /var/lib/dpkg/info/libqt4-qt3support.list had become
corrupted. Now I know yet another place to look for problems. :^)
I put in a good copy, and everything is working now. Please close the
ticket.
Curt-
- --
Treason! http://blog.mises.
Package: libqt4-qt3support
Version: 4.4.0~rc1-5
Severity: important
Every time I try to do anyting with apt, the following error
occurs:
=
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... dpkg: error processing
/var/cache/apt/archives/libgnutls26_2.
Package: nvidia-kernel-source
Version: 100.14.11-1
Severity: wishlist
The following error message comes up when installing latest nvidia driver
in Sid. I've also seen the same message for some time:
Unpacking nvidia-kernel-2.6.22-2-686 (from
.../nvidia-kernel-2.6.22-2-686_100.14.11-1+2.6.22-4_i
Package: dvgrab
Version: 2.1-2
Severity: important
I'm sorry if this should have been a wishlist bug, I couldn't decide.
As of kernel 2.6.22, according to bug #436267 which I opened on the
kernel, the reason that /dev/raw1394 doesn't exist is because the Debian
kernel folks aren't building the m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 06 August 2007, maximilian attems was heard to say:
> no they are the old firwire stack,
> that has been disabled due to security concern and general
> distrust.
Oh crud. :^(
> what are you missing in the yuyu stack?
At least raw1394, to c
Package: linux-image-2.6.22-1-686
Version: 2.6.22-3
Severity: wishlist
The IEEE1394 kernel drivers that have been built as modiles in prior
kernels have not been built with the kernel in the linux-image-2.6.22-1-686
package. Having these modules available without compiling a custom
kernel has bee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 26 July 2007, Debian Bug Tracking System was heard to say:
> This is an automatic notification regarding your Bug report
> #434412: kino: Broken Dependency: Libquicktime0 conflicts with
> libquicktime1, which was filed against the kino pack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bastian Blank <[EMAIL PROTECTED]> wrote:
>> Justification: breaks the whole system
>No it does not.
Yes, it did. Unbootable is one of the options listed in reportbug
for "breaks the whole system".
>Don't use yaird.
Then why is yaird packaged?
I wa
Package: linux-image-2.6.22-1-686
Version: 2.6.22-2
Severity: critical
Justification: breaks the whole system
When installing linux-image-2.6.22-1-686 (2.6.22-2), the following error
comes up:
--
Setting up linux-image-2.6.22-1-686 (2.6.22-2) ...
Running depmod.
Finding valid ramdisk creat
Package: kino
Version: 0.92-3+b2
Severity: important
Libquicktime1 is overriding libquicktime0, kino depends upon
libquicktime0. Could kino be set to use libquicktime1 please?
Curt-
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architec
Package: dvgrab
Version: 1.8-4
Severity: important
Libquicktime1 is conflicting with libquicktime0, dvgrab depends upon
libquictime0. Can dvgrab be set to use libquicktime1 please?
Curt-
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Arch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm sorry, but now it's working. After half a dozen reboots and
fiddles last night, with continual failure, this morning I forgot to
reboot into 2.6.18 and let 2.6.21 boot. It came up with the Nvidia
driver just fine, no errors.
I hate it when sof
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The problem occurred on 2.6.21, compiled using the kernel package from
Debian source with the only change to the config being
paravirtualization turned off because otherwise the Nvidia kernel
module will not compile. (GPL only violation)
I went ba
Package: nvidia-kernel-source
Version: 100.14.06-1
Severity: grave
Justification: renders package unusable
Just upgraded to Nvidia 100.14.06-1, after building with m-a a-i nvidia-kernel
and
then installing the latest nvidia-glx, the Nvidia spash screen "beta" comes up,
and
the following system c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 22 April 2007, Debian Bug Tracking System was heard to say:
> This is an automatic notification regarding your Bug report
> #420523: xserver-xorg-core: Cannot find installed Nvidia driver,
> which was filed against the xserver-xorg-core packa
Package: xserver-xorg-core
Version: 2:1.3.0.0.dfsg-2
Severity: important
Other people in Debian-user have reported that by downgrading
xserver-xorg-core this problem goes away.
As of the update yesterday morning, every time I startx, the
following error occurs in /var/log/Xorg.0.log
(WW) Warni
Package: nvidia-kernel-source
Version: 1.0.9746-2
Severity: grave
Justification: renders package unusable
The module had previously built just fine under kernel 2.6.18, trying to
compile for 2.6.20-1 and tonight 2.6.20-2.
Tried version presently in unstable first, received the same
error then tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 18 December 2006 19:03, Joey Hess was heard to say:
> Curt Howland wrote:
> > ls: relocation error: /lib/libacl.so.1: symbol getxattr, version
> > ATTR_1.0 not defined in file libattr.so.1 with link tim
Package: libacl.so.1
Severity: important
Hi, Sorry, I don't know which package this library is in. I'm unable to
do much of anything with my system, even ls -al gets the following
error:
$ ls -al
ls: relocation error: /lib/libacl.so.1: symbol getxattr, version
ATTR_1.0 not defined in file lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Good morning.
On Friday 01 December 2006 02:25 it was so written:
> With konq-plugins version 4:3.5.5-1 (KDE 3.5.5), these actions are
> present in the konqueror context menu.
> Could you check this problem is fixed in your side?
Yes, Move To and Cop
Package: console-common
Version: 0.7.64
Followup-For: Bug #392717
The text of the error I received when doing apt-get upgrade
this morning is:
Preparing to replace console-common 0.7.62 (using
.../console-common_0.7.64_all.deb) ...
/var/lib/dpkg/tmp.ci/preinst: line 63: [: -eq: unary operator e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 11 October 2006 13:46, Sjoerd Simons was heard to say:
> > Just installed fresh Unstable last week, hald never ran
> > correctly. The boot messages say "Starting hal daemon...failed".
> > As with the prior ticket, trying to start the daemo
Package: hal
Version: 0.5.8.1-1
Followup-For: Bug #366370
Just installed fresh Unstable last week, hald never ran correctly. The boot
messages say "Starting hal daemon...failed". As with the prior ticket, trying
to start the daemon by hand also fails, even though hal reports that it is
going to r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
BTW, the Alsa boot message is as follows:
- --
Setting up ALSA...done (none loaded).
- --
Alsa doesn't show up in dmesg either.
I also tried "#alsactl store" after alsacfg was successful, to no
effect.
Curt-
- --
September 11th, 2001
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
BTW, during this latest cycle, I tried "touch /etc/modprobe.conf" to
see if that would be updated by alsaconf if the file simply existed.
It was not, and the file does not exist now, but _this_ time the
file /etc/modprobe.d/sound was created with t
Package: alsaconf
Severity: important
Other people are reporting the same problem. Alsaconf does not
save its changes through a reboot. Alsaconf asks if the user
wants to update /etc/modprobe.d/sound and /etc/modprobe.conf,
but neither of these files exists in a recent install of Sid or,
if other
Package: gnupg-agent
Version: 1.9.20-2
Severity: important
Installed Sid on Wednesday, libpth20 installed due to other dependencies.
libpth2 is not available and will not install due to confluct with libpth20,
gnupg-agent will not install without libpth2.
-- System Information:
Debian Release: t
Yes, it is working now.
Thank you very much for all your efforts.
Curt-
On Saturday 26 August 2006 08:02, Bill Allombert was heard to say:
> reassign 383506 apollon
> tags 383506 fixed
> quit
>
> On Thu, Aug 17, 2006 at 01:48:33PM -0400, Curt Howland wrote:
> > As root
Package: update-menus
Severity: important
I noticed that I didn't have "Debian" under the K menu in KDE, so I
poked around and discovered that "update-menus" is not functioning.
As root, I get the following errors. Because of my window width, I'm
not sure the carrat is in the right place:
-
Package: konq-plugins
Version: 4:3.5.2-1
Severity: normal
A couple of days ago I noticed that "move to:" and "copy to:" are missing from
the
right-click-on-a-file context menu in Konqueror. The same action on the desktop
has
the move and copy entries. I looked it up at KDE and it says the plug-
Package: nvidia-kernel-2.6.16-1-686
Version: 1.0.8756+1
Followup-For: Bug #366630
The pre-built nvidia-kernel-2.6.16-1-686 fails, Xlog shows "unable to load",
but if I build it from the nvidia-kernel-source it works just fine.
When I run dselect, it automatically "upgrades" to the prebuilt kerne
This problem was solved with 2.6.15, and continues to work in 2.6.16,
so I figure it's ok to close the bugreport.
Thanks for all the help,
Curt-
--
September 11th, 2001
The proudest day for gun control and central
planning advocates in American history
--
To UNSUBSCRIBE, email to [EMAIL
According to other folks, the modules-assistant compiles madwifi just
fine even with the error message.
Second, with the 1.0.8178-3 version of the nvidia kernel source, it is
no longer looking for the header file that has gone missing from
2.6.16 that was in 2.6.15 and earlier, and so it compil
Package: linux-headers-2.6.16-1-686
Version: 2.6.16-2
Severity: normal
Hi. I have two kernel modules which I build from source, both of which worked
perfectly well with 2.6.15 but both fail when trying to compile for 2.6.16.
When I tried building madwifi, module-assistant reported "unconfigured s
Package: dselect
Version: 1.13.16
Severity: wishlist
Good afternoon. Some time around when Sarge was released, the dselect
"welcome to dselect's main package listing" screen changed behavior.
When I first used it, the required keystroke was the space-bar to go
from that screen to the actual l
Package: defoma
Version: 0.11.8-0.1
Severity: minor
When installing fonts in dselect, I noticed the following error was printed
many times:
Registering /usr/share/fonts/truetype/mikachan/mikachan-PS.ttf..
Use of uninitialized value in print at /var/lib/defoma/scripts/gs.defoma line
108.
The f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Francois, indeed it does seem to be the same error. Sorry I didn't
check the KDE bugtrack this time. :^(
However, I have added a comment to that bug that I did get a
successful verify when burning a CD from .ISO file. I haven't tried a
DVD from .IS
Package: k3b
Version: 0.12.10-2
Severity: normal
When I select "verify", the data DVD writes and ejects, but when I close the
DVD drive and hit OK to continue, K3b reports "cannot read file ..." and lists
the first file on the disk. Obviously, this fails the verify.
I have tried CDs, and verify
Package: kdm
Version: 4:3.5.0-4
Severity: normal
kdm used to list twm, olwm, and other installed window managers a couple
years ago when I first installed kdm, I do not remember which Debian
release it was. I
recently installed Sarge, and updated to Sid. olwm and twm have been
installed the entir
Package: twm
Version: 6.9.0.dfsg.1-3
Severity: wishlist
I had to create a twm.desktop file in /usr/share/xsessions, by copying
the one that kde automatically creates.
When did twm stop creating the file? I noticed that olwm twm and
windowlab all stopped showing up in the display manager list abo
Package: olwm
Version: 3.2p1.4-19.1
Followup-For: Bug #238865
I had to create a olwm.desktop file in /usr/share/xsessions, by copying
the one that kde automatically creates.
When did olwm stop creating the file? I noticed that twm, olwm and
windowlab all stopped showing up in the display manager
Suggest merge with #343042, it seems this is happening to lots of
people.
I attempted the fix mentioned in #343042, adding MODULE ide-generic
and MODULE ide-disk to /etc/haird/Default.cfg, and running yaird -v
-o /boot/initrd.img-2.6.14-2-686 2.6.14-2-686, but the same error
occured. I have no
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Followup-For: Bug #343048
I took a picture of the failure message that was not included in the
message opening this bug report:
Right after mice: and input: messages,
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33 MH
I noticed that this evening there's been an update to 2.6.14-2-686, so
I installed it and tried again. No change, I still receive this
error:
dierdre# uname -a
Linux dierdre 2.6.14-2-686 #1 Mon Nov 14 14:19:05 UTC 2005 i686
GNU/Linux
~
dierdre# hdparm -d 1 /dev/hda
/dev/hda:
setting using_dma
On Monday 14 November 2005 17:03, Jonas Smedegaard was heard to say:
> No need for excuse: this is highly relevant info, as I suspect it
> shows that the recent yaird inclusion of fbcon is what solves this.
>
> Could it be that even if you noticed the new fbcon line in
> Default.cfg, your image is
Just after I filed this wishlist item, I decided to try again. This
time vga=791 works. Surprisingly, the characters are even smaller
than when running 2.6.12. It's better than 80x25, though.
Please excuse the bug report, I guess it's already obsolete.
Curt-
--
September 11th, 2001
The pro
Package: linux-image-2.6.14-1-686
Version: 2.6.14-2
Severity: wishlist
First, thank you for all your astounding work keeping Debian the best
distribution bar none.
Until 2.6.14, I was able to use "vga=791" for framebuffer in lilo.conf,
and found the substantially larger console very useful. "vga
Package: linux-image-2.6.14-1-686
Version: 2.6.14-2
Severity: important
I have 2.6.12 and 2.6.14 (686 P4) installed on this machine. If I boot back into
2.6.12 DMA is on for /dev/hda. It is off in 2.6.14 and will not enable:
# hdparm -d 1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET
Package: kmail
Version: 4:3.4.2-2
Followup-For: Bug #306183
Using Sid, Kmail 1.8.2 InlinePGP selected still gets sent as PGP/MIME.
http://bugs.kde.org/show_bug.cgi?id=99089 has a patch to this bug.
I guess that Debian is just waiting for the change to make its way
downstream.
In the mean time,
I'm very sorry, the problem was a user error.
I had "dragged and dropped" the *directory* VIDEO_TS into the K3b DVD
project "VIDEO_TS" location, when I should have copied the individual
files out of the directory instead.
It is working fine now. I will now go slap myself silly so that I
never
Package: dvd+rw-tools
Version: 5.21.4.10.8-1
Severity: important
File: /usr/bin/growisofs
*** Please type your report below this line ***
I'm running up-to-date Sid.
Writing a data DVD works fine, as do video and regular CDs. The last
time I successfully wrote a video DVD was in January. Howeve
70 matches
Mail list logo
