Package: systemsettings
Version: 4:5.12.3-1
Severity: grave
--- Please enter the report below this line. ---
Previous version and current version:
Application comes up with black windows. The left pane will show its MouseOver
toolboxes.
--- System information. ---
Architecture:
Kernel: Li
Package: gweled
Version: 0.9.1-4
Severity: grave
--- Please enter the report below this line. ---
Can no longer use the program. Error from CLI:
~$ gweled
*WARNING* **: Locale not supported by C library.
*WARNING* **: GError set over the top of a previous GError or uninitializ
--- System inf
More experiences with this problem:
When I get the error, not possible to log in. Must poweroff using the power
button, hold until stop.
If the CPU is not abnormally hot (usually will not be), then rebooting will
usually proceed normally.
Doing this reboot using a sysvinit bootup shows no rele
Package: systemd
Version: 234-3
Severity: critical
--- Please enter the report below this line. ---
This touches systemd because of concurrent boot threads but actual bug may be
elsewhere!
Sporadically get, instead of the usual bootup and kdm start, a console logon.
It is not possible to log on
Package: python-tk
Version: 2.7.13-1
Severity: critical
--- Please enter the report below this line. ---
Running the game pysolfc, get the following traceback:
~$ pysolfc
Traceback (most recent call last):
File "/usr/games/pysolfc", line 26, in
init()
File "/usr/share/games/pysolfc/pysol
Package: systemd
Version: 233-10
--- Please enter the report below this line. ---
I have not seen this env variable in ages.
Do I need to install something involving the getty systemd service to get it?
Since I have lived without it so far, question is if not using ssh xorg login,
to I indeed ne
I would re-open this!
Why?
Latest upgrades of the 304xx and the 4.9 kernels will work using xrender,
compositor enabled on start. Window decorations will appear, if sometimes
delayed.
Now the ace-of-penguins freecell dies again. Their other card games work fine.
This was the same problem befor
On יום שני, 19 בדצמבר 2016 13:26:04 IST Luca Boccassi wrote:
> On Mon, 19 Dec 2016 14:56:33 +0200 David Baron wrote:
> > On ××× ×©× ×, 19 ××צ××ר 2016 10:44:13 IST Andreas Beckmann
wrote:
> > > Hi David,
> > >
> > > On 2016-12-17 19:39, David B
On יום שבת, 17 בדצמבר 2016 2:03:17 IST Andreas Beckmann wrote:
> Hi,
>
> I just uploaded 304.134 to sid, it should appear on the mirrors later
> today. Please test it to see whether this bug is now fixed.
>
> Thanks
>
>
> Andreas
Program has been running fine. Bug should have been closed befor
Package: gufw
Version: 12.10.0-1
Severity: grave
--- Please enter the report below this line. ---
Note: The ufw CLI application works correctly.
~$ sudo gufw
No protocol specified
Unable to init server: Could not connect: Connection refused
(gufw.py:10441): Gtk-WARNING **: Locale not supported b
Package: src:linux
Version: linux-image-4.3.0-1
Severity: grave
--- Please enter the report below this line. ---
Today's upgrades, nvidia-legacy drivers, dkms, and linux-image, headers
4.3.0-1
On reboot to 4.3.0-1 kernel, get two messages "Local modules fail to load"
Everything else seems to pla
Spontaneously gave it a try today and ... it
booted successfully!
Did have an "invalid mount point" error up
front but does not show on journalctl or
dmesg.
On Thursday 15 October 2015 15:23:28 Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Am 15.10.2015 um 10:23 schrieb David Baron:
> > Package: systemd
> > Version: 226-4
> > Severity: grave
> >
> > --- Please enter the report below this line. ---
&
Package: systemd
Version: 226-4
Severity: grave
--- Please enter the report below this line. ---
Systemd is still 226-4, not upgraded, had been working up until my first boot
morning of 14.10
which booted OK.
Upgraded some KF5 Baloo packages to fix dorked KDE, rebooted, then bingo.
Boot stop
Package: plasma-desktop
Version: 4:5.4.2-1
Severity: grave
--- Please enter the report below this line. ---
Recent upgrade from Sid breaks plasma-desktop. All apps can be run from a
command line (i.e
Yakuake starts and works!) but there is no desktop.
Plasmashell is running using few resources.
Package: einstein
Version: 2.0.dfsg.2-9+b1
--- Please enter the report below this line. ---
Since this was reported in July, upgrades of surrounding packages fixed it,
has been working until now.
Einstein was upgraded to the +b1 version with all the gcc5 business on Sid.
Was working until Septem
Package: einstein
Version: 2.0.dfsg.2-9
Severity: grave
--- Please enter the report below this line. ---
Get the following when run from a terminal:
~$ einstein
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
Aborted
Worked f
On Wednesday 01 April 2015 11:46:38 Dmitry Shachnev wrote:
> Control: tags -1 moreinfo
>
> Hi David,
>
> On Mon, 30 Mar 2015 13:51:51 +0300, David Baron wrote:
> > Attempts to use qmake->qtchooser always yields qt5 libraries. Cannot make
> > anything in qt4 unless
Package: qtchooser
Version: 47-gd2b7997-2
Severity: grave
--- Please enter the report below this line. ---
Might be corollary to #781226
Attempts to use qmake->qtchooser always yields qt5 libraries. Cannot make
anything in qt4 unless manually running qmake-qt4 and ./configure may not set
up com
Package: kdm
Version: 4:4.11.9-1
--- Please enter the report below this line. ---
Yes, empty home directory for user and it logs in. Any data, of course, can be
brought in from the saved copy.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-4-amd64
Debian Release: jess
Package: kdm
Version: 4:4.11.9-1
--- Please enter the report below this line. ---
Yes, my user account is working fine.
Others simply blink and back to login dialog. I do not think that the user's
home .kde is accessed at all. Never gets out of kdm.
All the permissions seem to be OK. Enough spac
Package: kdm
Version: 4:4.11.9-1
--- Please enter the report below this line. ---
I got back on after (most of a) dist-upgrade. This was suggested by a poster
elsewhere.
The dbus error may or may not have been relevant at all. Might have been
generated once and simple viewed again.
KDE came up
Package: spamassassin
Version: 3.4.0-1
Severity: grave
--- Please enter the report below this line. ---
On start:
Starting SpamAssassin Mail Filter Daemon: server socket setup failed, retry 1:
spamd: could not create IO::Socket::INET6 socket on [::1]:783: Cannot assign
requested address
server
Package: apt
Version: 0.9.15.1
Severity: grave
--- Please enter the report below this line. ---
Will remove everything, libc6 and all if I let it.
Following packages are broken:
libc-bin, libc6 libc6-dbg, libc6-i686, libc6:amd64
Apt-get upgrade tried to install experimental versions and experimen
Package: openbsd-inetd
Version: 0.20091229-3
Severity: grave
--- Please enter the report below this line. ---
Installation fails with:
[] Restarting internet superserver: inetd/usr/sbin/inetd:
/lib/libbsd.so.0: version `LIBBSD_0.5' not found (required by /usr/sbin/inetd)
/usr/sbin/inetd: /lib
On Thursday, 21 November, 2013 10:40:36 Andrew Shadura wrote:
> Hello,
>
> On 21 November 2013 10:23, David Baron wrote:
> > Updated now to 0.7.46-1. Anything new. Bug is a month old.
>
> Well, it's not strictly a bug... It's rather incorrect usage. If you
>
Package: ifupdown
Version: 0.7.44
--- Please enter the report below this line. ---
Updated now to 0.7.46-1. Anything new. Bug is a month old.
Related to #723184 posted around same time?
--- System information. ---
Architecture: i386
Kernel: Linux 3.11-2-686-pae
Debian Release: jessie/sid
Package: android-tools-adb
Version: 4.2.2+git20130529-2.1
Severity: grave
--- Please enter the report below this line. ---
After upgrade to current version git20130529-2.1, either does not know it is
indeed running (or maybe it is not though there is a process).
Sample session:
david@dovidhalev
On Thursday 01 November 2012 23:52:01 Craig Small wrote:
> forcemerge 691847 692063
> thankyou
>
> On Thu, Nov 01, 2012 at 08:43:37PM +0200, David Baron wrote:
> >Yesterday (31 October 2012) Sid upgrades. As procps had a critical bug
> >(which may indeed be
Package: procps
Version: 1:3.3.4
Severity: critical
--- Please enter the report below this line. ---
Yesterday (31 October 2012) Sid upgrades. As procps had a critical bug (which
may indeed be related, dup of this one!) against it, I did not upgrade procps
but upgraded everything else.
On reboo
On Monday 11 June 2012 17:57:53 Gordon Haverland wrote:
> On June 11, 2012, Paul Menzel wrote:
> > Am Montag, den 11.06.2012, 16:11 +0300 schrieb Timo Juhani
>
> Lindfors:
> > > after changing
> > >
> > > add_problematic "package $package left obsolete init.d
> > >
> > >script behind"
> > >
> >
> If the reported problem is a local modification, it needs to be fixed
> manually. These are typically due to obsolete conffiles being left after
> a package has been removed, but not purged. It is suggested that these
> are removed by running:
>
> dpkg --purge fuse initscripts initscripts init
I have downloaded sysv-rc to testing so other upgrades can proceed.
The "recommendations." i.e purging initscripts, are impossible due to its
widesperad dependents, and is absurd.
So I can get along with testing until some resolution is possible.
Note that the announcement of no more static ini
On Thursday 07 June 2012 21:07:39 Roger Leigh wrote:
> On Thu, Jun 07, 2012 at 05:34:33PM +0300, David Baron wrote:
> > I have an older init scripted system which will not configure for
> > dep-based boot due to man missing lsb tags and overrides (what can I do
> > abou
Package: sysv-rc
Version: 2.88dsf-26
Severity: grave
--- Please enter the report below this line. ---
I have an older init scripted system which will not configure for dep-based
boot due to man missing lsb tags and overrides (what can I do about this?).
Additonally, as per bug #676463, there are
Package: nut-client
Version: 2.6.3-2
--- Please enter the report below this line. ---
Attached file. Did not keep original to run diff
Lines were 98,105,127, I believe
--- System information. ---
Architecture: i386
Kernel: Linux 3.2.0-2-686-pae
Debian Release: wheezy/sid
500 unstable
On Wednesday 15 February 2012 11:40:02 Michael Prokop wrote:
> * David Baron [Wed Feb 15, 2012 at 10:49:53AM +0200]:
> > --- Please enter the report below this line. ---
> > On attempted upgrade
>
> From which initramfs-tools version are you upgrading?
Previous Sid ve
Package: initramfs-tools
Version: 0.100
Severity: grave
--- Please enter the report below this line. ---
On attempted upgrade
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-1-686-pae
/rootfs: N
On Sunday 25 Tishrey 5772 13:31:44 Bastian Blank wrote:
> On Sun, Oct 23, 2011 at 12:58:23PM +0200, David Baron wrote:
> > After recent upgrade, the linux-3.0-2-pae kernel would not boot. Got
> > placed in an initramfs busybox shell. From there I was able to reboot
> > and
On Sunday 25 Tishrey 5772 13:31:44 Bastian Blank wrote:
> On Sun, Oct 23, 2011 at 12:58:23PM +0200, David Baron wrote:
> > After recent upgrade, the linux-3.0-2-pae kernel would not boot. Got
> > placed in an initramfs busybox shell. From there I was able to reboot
> > and
Package: lvm2
Version: 2.02.88-1
Severity: grave
--- Please enter the report below this line. ---
After recent upgrade, the linux-3.0-2-pae kernel would not boot. Got placed in
an initramfs busybox shell. From there I was able to reboot and un the -1-pae
kernel. Apparently the postintall did not
On Thursday 02 Elul 5771 18:07:55 Diederik de Haas wrote:
> On Thursday 01 September 2011 16:48:08 David Baron wrote:
> > Package: nvidia-kernel-source
> > Version: 280.13-3
> > Severity: grave
> >
> > --- Please enter the report below this line. ---
> >
Package: nvidia-kernel-source
Version: 280.13-3
Severity: grave
--- Please enter the report below this line. ---
Previously installed version (including related software and alternatives
packages) failed on kdm start. Error cited was ABI incompatabiliy. The
suggested option -ignoreABI--I have no
On Tuesday 02 Av 5771 22:11:04 Frank Küster wrote:
> unmerge 636328 636304
> retitle 636328 libpaper script ist non-functional and prints garbage
> thanks
>
> David Baron wrote:
> > Package: texlive-base
> > Version: 2009-12
> > Severity: normal
> >
>
Package: hplip
Version: 3.11.5-2
Severity: grave
--- Please enter the report below this line. ---
Cannot run any of the utilities. Get error message
warning: CUPSEXT could not be loaded. Please check HPLIP installation.
reinstalling does not help
--- System information. ---
Architecture: i386
Ke
On Tuesday 19 Sivan 5771 20:00:29 Aurelien Jarno wrote:
> > Do please check over the pre/post/install scripts involved so this mess
> > does not recur :-)
>
> I don't really know what can be done, the preinst script already abort
> the installation if a non-dpkg owned version of ld.so is found. A
On Tuesday 19 Sivan 5771 18:21:35 Aurelien Jarno wrote:
> Le 21/06/2011 16:59, David Baron a écrit :
> >> > I, of course, did not touch the 2.13 ones. There are actually only a
> >> > few
> >> >
> >> > of them but are locally symlinked. There
> > I, of course, did not touch the 2.13 ones. There are actually only a few
> > of them but are locally symlinked. There would be three version of
> > these, on /lib, lib/i386-gnu... and /lib/i686/cmov. The ones I checked a
> > all different.
> >
> >
> > Should the /lib ones be actually be remov
> * * * * *
> > > > > So to clean up this system, would I:
> > > > > 1. remove ALL 2.11.2 files in /lib (making sure there are no
> > > > > symlinks to them).
> > > > > 2. NOW, re-upgrade to 2.13-7
> > > > >
> > > > > What happened before:
> > > > > 1. I myself placed the 2.11.2 files from the liv
On Tuesday 19 Sivan 5771 01:21:46 Aurelien Jarno wrote:
> On Mon, Jun 20, 2011 at 10:30:45PM +0300, David Baron wrote:
> > On Monday 18 Sivan 5771 21:16:28 David Baron wrote:
> > > On Monday 18 Sivan 5771 20:18:42 David Baron wrote:
> > > > I was looking at the conte
On Monday 18 Sivan 5771 21:16:28 David Baron wrote:
> On Monday 18 Sivan 5771 20:18:42 David Baron wrote:
> > I was looking at the content of my /lib variations. Very interesting.
> >
> > The testing one I am using now las libc.so.6 -> libc-2.13.so dated May
> > 1
On Monday 18 Sivan 5771 20:18:42 David Baron wrote:
> I was looking at the content of my /lib variations. Very interesting.
>
> The testing one I am using now las libc.so.6 -> libc-2.13.so dated May 12.
> The "sid" one I copied from the segfaulting /lib has libc.so.6
I was looking at the content of my /lib variations. Very interesting.
The testing one I am using now las libc.so.6 -> libc-2.13.so dated May 12.
The "sid" one I copied from the segfaulting /lib has libc.so.6 ->
libc-2.11.2.so dated JUNE!
Something is amiss here, huh?
All the 2.13 files, symlinks
A very similar bug reported years back. Culprit was libc6-i686. Bug#586241.
Relevant?
On Sunday 17 Sivan 5771 02:22:46 Jonathan Nieder wrote:
> Hi David,
>
> David Baron wrote:
> (out of order for convenience)
>
> > Note that there is no "root." I have a working /lib with (mostly) testing
> > libc6 et al packages and lib-sid which has the -7
On Thursday 14 Sivan 5771 00:25:42 you wrote:
> reassign 630608 libc6 2.13-7
> quit
>
> Hi David,
>
> David Baron wrote:
> > After upgrading lib6 to current Sid (-7), everything, I mean everything
> > segfaults. System will boot up very normally but as soon a
Package: bash
Version: 4.1-3
Severity: critical
--- Please enter the report below this line. ---
After upgrading lib6 to current Sid (-7), everything, I mean everything
segfaults. System will boot up very normally but as soon as I log in, the fun
begins.
There are numerous error messages from t
Package: kqemu-source
Version: 1.3.0~pre11-8
Severity: grave
Justification: renders package unusable
Compile fails with Unknown field `ioctl` spe in kqemu-linux.c.
Note than when selected in m-a menu, a cdfs is also installed which is not
listed as a dependency of kqemu-source.
-- System I
Package: flightgear
Version: 2.0.0-1
Severity: grave
--- Please enter the report below this line. ---
Attempt to upgrade to this new version will install kernel images for 486,
nvidia modules for it, among other stuff, ignoring existing kernel
architecture and video driver in use. This could be
Package: reportbug-ng
Version: 1.20
Severity: grave
Justification: renders package unusable
Any attempt to query the program receives such as:
Traceback (most recent call last):
File "/usr/share/reportbug-ng/rnggui.py", line 205, in
lineedit_return_pressed
buglist = bts.get_bugs(query)
Package: mysql-server-5.1
Severity: normal
Marcin Trybus said:
> I'd like to confirm that this also happens with a clean install of pure
> squeeze (only iceweasel taken from experimental). I tried both mysql-server
> from squeeze (5.1.37-2) and sid (5.1.39-1).
I installed testing and upgraded to
On Sunday 22 November 2009 17:28:05 Jonathan Niehof wrote:
> (David, I'm cc-ing you on this since you commented on not receiving a
> CC previously...if you want to receive updates on a particular bug,
> directions on subscribing are at
> http://www.debian.org/Bugs/Developer#subscribe )
>
If I sub
Following your instruction, I have (re-)achieved some filtering. So maybe my
configuration got messed over somewhere and I was not paying attention so
proxy 3129 --> dansguardion --> 8080 ---> browser proxy on 8080 seems to be
OK.
So this bug may be closed as my error.
Problem now is bogging do
I have be delaying a bunch of upgrades because of this. Had a system messed by
libc6 before.
Is this bug current?
Only am64?
Is it safe to upgrades these packages?!?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
On Sunday 15 November 2009 17:10:16 David Baron wrote:
> On Sunday 15 November 2009 16:53:31 David Baron wrote:
> > I had always used port 3128 and have tinyproxy set to that.
> > I had always manually set the proxy port to that, 3128.
> > It used to work.
> >
> >
I had always used port 3128 and have tinyproxy set to that.
I had always manually set the proxy port to that, 3128.
It used to work.
In ansgardian.conf
proxport = 3128
/filterport = 8080
oroxyip = 127.0.0.1
The posting implies using 3128 (or ) bypasses the filter.
So I tried setting the p
On Sunday 15 November 2009 16:53:31 David Baron wrote:
> I had always used port 3128 and have tinyproxy set to that.
> I had always manually set the proxy port to that, 3128.
> It used to work.
>
> In ansgardian.conf
> proxport = 3128
>
> /filterport = 8080
>
> o
Package: dansguardian
Version: 2.10.1.1-1
Severity: grave
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
--- Please enter the report below this line. ---
Dansguardian was working with Tinyproxy. This always worked before, easily
tested by entering obvious porn sites.
No
Package: nvidia-glx-legacy-71xx
Severity: grave
Justification: renders package unusable
Installing this baby will happily remove all of xorg.
Hint: Nvidia's version reports:
/usr/lib/xorg/modules/drivers//nvidia_drv.so: undefined symbol:
/ AllocateScreenPrivateIndex
-- System Information:
Debia
On Wednesday 15 July 2009 18:38:54 Timo Sirainen wrote:
> On Jul 15, 2009, at 11:28 AM, David Baron wrote:
> > When starting new version fails, get incorrect variabe sieve in conf
> > file
> > (using my old one). If I delete the two sieve lines, the daemon will
> > star
Package: dovecot-imapd
Version: 1:1.2.1-1
Severity: grave
--- Please enter the report below this line. ---
When starting new version fails, get incorrect variabe sieve in conf file
(using my old one). If I delete the two sieve lines, the daemon will start but
does not function
I downgraded to t
Package: firmware-linux
Version: 0.16
Severity: grave
--- Please enter the report below this line. ---
If firmware-linux is not installed, card "reports" error loading firmware,
then is not DRI enabled but no other problems.
If firmware is installed, firmware is requested and successfully loaded.
Package: reportbug
Version: 4.1
Severity: grave
--- Please enter the report below this line. ---
Versions 4.0, 4.1 will produce a traceback like:
File "/usr/bin/reportbug", line 1831, in
main()
File
Package: firmware-linux
Version: 0.16?
Severity: critical
Justification: breaks the whole system
As of 2.6.29 kernels, this (nonfree?) code is broken out of the kernel's driver
and loaded from this package.
The mga driver for Matrox g200 mila card worked before when this separate
firmware was no
On Friday 23 January 2009 13:21:24 Torsten Marek wrote:
> Am Freitag, den 23.01.2009, 11:19 +0200 schrieb David Baron:
> > Package: python-qt4
> > Version: 4.4.2-4
> > Severity: grave
> > Justification: renders package unusable
> >
> > Because some newer
Package: python-qt4
Version: 4.4.2-4
Severity: grave
Justification: renders package unusable
Because some newer python program required 4.4.3, tried to install this off
experimental. The package will not install, error returned during unpack.
Trying a --force-all install using dpkg showed that th
Links may also be disabled after one is exercised,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sunday 09 November 2008 17:12:48 Christian Perrier wrote:
> Quoting David Baron ([EMAIL PROTECTED]):
> > As I posted, the problem is NOT in the boinc-app-seti package at all.
> >
> > The start-stop-daemon for boinc (boinc-client) was producing a pid file
> > contai
As I posted, the problem is NOT in the boinc-app-seti package at all.
The start-stop-daemon for boinc (boinc-client) was producing a pid file
containing a different pid number than the actual boinc pid! This would cause
the distribution /etc/init.d/boinc_client fails to stop the boinc and this
Actually, start-stop-daemon WILL start boinc just fine. The pid file contains
a different pid than that yielded by pidof boinc. This does not sit well with
the distribution boinc_client init.d script. Workaround: either explicitely
set the pidfile content to pidof boinc or change the isrunning f
Package: boinc-app-seti
Version: 5.13+cvs20060510-4
Severity: grave
Justification: renders package unusable
The configure/post-configure script of the installation fails.
The reason is most probably that /etc/init.d/boinc-client distribution will
not start boinc. The daemon start/stop utility sim
P.S.
Instead of all that stuff about SysV, why not an error message like:
Dansguardian cannot open /tmp/ Check permissions.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tuesday 21 October 2008 22:20:21 Alexander Wirt wrote:
> David Baron schrieb am Tuesday, den 21. October 2008:
> > Package: dansguardian
> > Version: 2.9.9.7-2
> > Severity: grave
> > Justification: renders package unusable
> >
> > After migrating t
Package: dansguardian
Version: 2.9.9.7-2
Severity: grave
Justification: renders package unusable
After migrating to new disk (but there had been a recent upgrade of the
package and I did not notice whether is worked before migrating) I cannot
start Dansguardian.
Get a failure recommenting using s
OK.
This has nothing to do with the sources. It may have something to do with
the kbuild, how it gets its paths!
I have always had funny stuff building nvidia.ko, both with m-a and with
nvidia's .run.
It thinks my 2.6.23 was built with gcc-2. I can only get nvidia to build if
I symlink to that.
This is really strange. I built this for the running 2.6.23 kernel and using
the make variable, for a 2.6.26 kernel.
The the 2.6.23 had this error. I went to edit the 2.6.26 and found it 100%
correct! A look at the sources, an fgrep 96.43 saw all the version string
variables correctly defined
Package: nvidia-kernel-legacy-96xx-source
Version: 96.43.07-1
Severity: critical
File: nvidia-kernel-legacy-96xx
Justification: breaks the whole system
I manually built this from sources, substituting
__COMPAT_SEMAPHORE_INITIALIZE and such for rt patch usage.
I installed Nvidia's libglx.so
On res
Package: libplasma2
Version: 4:4.0.98-1
Severity: serious
File: /usr/bin/plasma
Justification: 4
Drag included file from a kmail email to a desktop icon for a folder (icon
as opposed to a folder-view plasmoid).
Choose copy (probably does not matter).
A zero length file of the target name is create
Your last chance for free credit http://ch2systems.com/default.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
My daughter discovered this by accidentally starting a kde4 session with no a
single crash at all!!
1. Must have a clean .kde4 on start! Even the one that I got by starting using
sudo was not clean enough. Got rid of that. Viole.
2. Kicker and kdesktop will come up anyway, it seems (the old kde
Package: planetpenguin-racer
Version: 0.3.1-11
Severity: grave
File: /usr/games/ppracer
Justification: renders package unusable
Obviously, no keyboard, no game (I have no joystick).
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (650, 'tes
Here is some more, possibly useful information:
Postings on kubuntu's lists complained of problems with dbus without root
permissions. Kubuntu/ubuntu's approach to this is sudo only so becomes more
problematic. On my Debian system:
1. Dbusd IS running, started on init. (Note: There is no udev r
Here is some more, possibly useful information:
Run from a failsafe session in an xterm, "sudo /usr/bin/startkde" will bring
up successfully a KDE4 session, no crashes, everything (currently
implemented) there!
Run without root privileges, I get all the crashes.
Apparently, run from a KDM logo
Package: kde4
Version: 1
Severity: grave
Justification: renders package unusable
Starting kde4, either from its /etc/init.d/kdm or from a failsafe session
running /usr/bin/startkde brings up a blue background then a series of
crashes:
kcminit (from kdm)
krunner (so no desktop)
plasma (so no panels
Package: ardour-i686
Version: 1:2.2-1
Severity: grave
Justification: renders package unusable
/usr/lib/ardour2/ardour-2.2: symbol lookup error:
/usr/lib/libgnomecanvas-2.so.0: undefined symbol: art_alloc
I had this problem when I compiled ardour myself as well. This may be a gtk
problem, has been
Package: flashplugin-nonfree
Version: 9.0.115.0.1
Severity: grave
File: flashplugin
Justification: renders package unusable
Get multiple crashes (KDE) viewing pages in Konqueror.
Here is the backtrace (not very illuminating since this is release):
Using host libthread_db library "/lib/i686/cmov/l
Package: xmms2
Version: 0.2DrJekyll-4
Severity: grave
Justification: renders package unusable
This new version has stopped working (never really used it but ... )
Error message is:
Bad glib version: GLib version too old (micro mismatch)
Xmms2 and glib from Sid.
-- System Information:
Debian Rel
Package: enigma
Version: 1.00-2
Severity: grave
Justification: renders package unusable
After latest Sid upgrades (including libc6), enigma will fail after
completing one board with an undefined libzipios symbol. Leaves screen at
wrong setting if played full screen and mouse is eaten whether full
>>> LD_ASSUME_KERNEL="2.6.1" /lib/ld-2.5.so /lib/libc.so.6
>>I have a LD_ASSUME_KERNEL=2.4.19 in /etc/profile which was put there for
>>jackd. Maybe I should get rid of that! Tried that with the upgrade and
>>actually got into a bash login from the console but kdm would not restart to
>>test it
>> LD_ASSUME_KERNEL="2.6.1" /lib/ld-2.5.so /lib/libc.so.6
>I have a LD_ASSUME_KERNEL=2.4.19 in /etc/profile which was put there for
>jackd. Maybe I should get rid of that! Tried that with the upgrade and
>actually got into a bash login from the console but kdm would not restart to
>test it ther
1 - 100 of 129 matches
Mail list logo
