Bug#719796: Why is cups not a depends
Hi, I've run into the same situation (wanting to connect to cups on my (local) server), so I installed print-manager '--without-recommends'. It looks like cups is a requirement, so I don't get why cups is a recommends. So what's the reason cups is a recommends only? -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#733150: Confirmation of this bug
I can confirm this bug, downgrading to the version in testing (2.0.9-1) fixed it. Since apt-listbug uses this package, aptitude/apt-get got unusable after upgrading to 2.1.0-1 Cheers, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#738326: live-build installs extra packages (suggests or based on source package instead of binary)
On Thursday 20 February 2014 20:23:17 Daniel Dickinson wrote: > I still suspect a bug because NONE of the Recommends on or Depends packages > for gnuplot are shown as being installed Maybe I'm overlooking something, but have you started/booted your image and then did an "aptitude why gnuplot" ? It should tell you why gnuplot is/was installed. -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#740016: nvidia-driver: OpenGL image painted over other windows
On Tuesday 25 February 2014 18:35:19 Gleb Golubitsky wrote: > Suggestion: maybe this bug should be moved to xserver-xorg-core package? First try if you can reproduce it with a free driver (f.e. nouveau) -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#735424: nvidia-driver: needed option x for additional information
On Monday 20 January 2014 10:39:11 Karsten Malcher wrote:
> > Please try the new driver releases 319.82 in unstable and 331.38 in
> > experimental.
>
> How can i install this driver in jessie?
Add the following line to your /etc/apt/sources.list:
deb http://ftp.debian.org/debian/ unstable main contrib non-free
You probably also want to create /etc/apt/apt.conf.d/50-default-release with
the following contents:
Apt {
Default-Release "testing";
};
If your /etc/apt/sources.list has "jessie" lines instead of testing, use
jessie instead.
This will make sure you install packages from testing/jessie by default and
only install packages from other archives (unstable) when you explicitly say
so.
To install the nvidia package from unstable, do the following:
aptitude install nvidia-driver -t unstable
This should pull in that package from unstable including it's dependencies.
If it reports dependency issues, let aptitude offer you other suggestions until
the issues are resolved.
Another useful parameter for aptitude is "-s" which stands for simulate, so
you can experiment as much as you want (also as normal user) without actually
committing the changes.
To install the driver from experimental, add another line to your sources, but
use experimental instead of unstable and to install use '-t experimental'
instead of '-t unstable'.
> > And try a minimal config file as decribed in
> > /usr/share/doc/nvidia-driver/README.Debian.gz
>
> I tried to use nvidia-xconfig with the same result of this black blank
> screen. The xorg.conf is attached.
That's not a minimal config file ;-)
This is:
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
So remove all the other lines, so your xorg.conf only contains the part above.
HTH,
Diederik
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
Bug#735424: nvidia-driver: New vesa test
On Thursday 23 January 2014 12:37:29 Karsten Malcher wrote: > 2. Boot jessie, deinstall all Debian NVidia packages Instead of just deinstalling, I'd suggest purging the package(s), which also removes configuration files. Optionally you can also do the following to make sure all config files are indeed removed: - check /etc/X11/xorg.conf.d/ to see if there are any config files there (which could interfere) - run 'updatedb.mlocate' (as root) - run 'find -name *nvidia* -type f' (as root) to see whether there are still nvidia files on your system you'd like to get rid of Then reboot and install the nvidia driver HTH, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#735424: nvidia-driver: New vesa test
On Friday 24 January 2014 10:41:37 Karsten Malcher wrote: > I have purged all the packages. > But installation of the NVidia driver fails, because compilation does not > work. I atteched the logs. > > The directory /usr/src/linux-headers-3.12-1-amd64 exists! > But only with 1,9 MB content? Can you post the output of: aptitude search '?narrow(~i,(dkms|linux-headers|linux-image|build|nvidia))' -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#735424: nvidia-driver: New vesa test
On Monday 27 January 2014 20:49:51 Karsten Malcher wrote: > > the NVIDIA driver does not work under RT kernels, so get rid of the > > linux-headers-3.12-1-rt-amd64 linux-headers-3.12-1-common-rt packages > > i can't remember to have this packages installed. > They are not installed under wheezy! They were installed as dependency of linux-headers-3.12-1-all-amd64, so get rid of that package (and leave linux-headers-amd64 installed; that's the one you want). -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#735424: nvidia-driver: New vesa test
On Wednesday 29 January 2014 10:25:21 Karsten Malcher wrote: > ii linux-headers-3.12-1-amd64 > 3.12.6-2 amd64Header files for Linux > 3.12-1-amd64 ii linux-headers-3.12-1-common > 3.12.6-2 amd64Common header files for Linux > 3.12-1 Reinstall the linux-headers-amd64 package. > echo >&2 " ERROR: Kernel configuration is invalid."; \ > echo >&2 " include/generated/autoconf.h or > include/config/auto.conf are missing.";\ echo >&2 " Run 'make > oldconfig && make prepare' on kernel src to fix it.";\ > > That's not normal! I have that error in my make.log as well (as well as a bunch of warnings). Can you run the following command and attach the resulting file (bug735424- packages.txt) to your reply? aptitude versions '?narrow(~i,(dkms|linux-headers|linux-image|build|gcc| nvidia))' > bug735424-packages.txt -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#735424: nvidia-driver: New vesa test
Hi Karsten, On Wednesday 29 January 2014 11:29:51 Karsten Malcher wrote: > >> ii linux-headers-3.12-1-amd64 > >> 3.12.6-2 amd64Header files for Linux > >> 3.12-1-amd64 ii linux-headers-3.12-1-common > >> 3.12.6-2 amd64Common header files for Linux > >> 3.12-1 > > > > Reinstall the linux-headers-amd64 package. > > As i have written i purged all header packages and reinstalled this package. You've installed 'linux-headers-3.12-1-amd64' package, not 'linux-headers- amd64'. This won't solve your current issue, but it will make sure that when a new kernel lands in testing (which will happen), the appropriate linux-headers package will also be installed. > > Can you run the following command and attach the resulting file > > (bug735424-packages.txt) to your reply? > > I rebooted and you will find the file attached. I'm missing a whole bunch of nvidia packages ... Locating the problem becomes much harder if you keep using NVidia's .run file, so please stop doing that. Post the output of 'ls -l /usr/bin/gcc' And run the following command: 'aptitude install nvidia-driver' When that has finished, attach the file '/var/lib/dkms/nvidia- current/319.76/3.12-1-amd64/x86_64/log/make.log' to your reply. -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#735424: nvidia-driver: New vesa test
On Wednesday 29 January 2014 12:25:49 Karsten Malcher wrote: > > You've installed 'linux-headers-3.12-1-amd64' package, not 'linux-headers- > > amd64'. > > This won't solve your current issue, but it will make sure that when a new > > kernel lands in testing (which will happen), the appropriate linux-headers > > package will also be installed. > > O.K. - but what is the difference? > > As "user" i expect to get the correct headers for the kernel > linux-image-3.12-1-amd64 when i install 'linux-headers-3.12-1-amd64' That is correct. But you have the package 'linux-image-amd64' installed (and that's a good thing), so when a new kernel enters testing, it will be installed on your system and then you won't have the corresponding headers package on your system. Having both 'linux-image-amd64' and 'linux-headers-amd64' will make sure that when you get a new linux-image package, the corresponding linux-headers package will also be installed. > > I'm missing a whole bunch of nvidia packages ... > > Locating the problem becomes much harder if you keep using NVidia's .run > > file, so please stop doing that. > > Yes - i only tested the original nvidia installer as comparison to the > environment with the self compiled kernel. > > Post the output of 'ls -l /usr/bin/gcc' > > > > And run the following command: > > 'aptitude install nvidia-driver' > > First i have to install the original nvidia driver now. If you mean the 'nvidia-driver' package from Debian, then yes, do that. And report back with the requested information. > Do you think it is a good idea to start with a clean new copy of wheezy now > and upgrade it to jessie? I think everything is really mixed up now. Not now. Let's try to find (and fix) your issue now, otherwise you may end up in the same situation again. But it wouldn't hurt to start *preparing* for a complete new install and migrating your users files/settings/etc. -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#737217: nvidia-detect: incorrect detection for 304xx and current nvidia devices when using wheezy-backports nvidia-detect
On Friday 31 January 2014 22:46:47 Andreas Beckmann wrote: > > What brought this up is I've created a script to install the nvidia > > driver, and it uses nvidia-detect to select the correct nvidia driver > > package. > > Glad to see someone is using nvidia-detect for some autodetection work, > maybe you can share your scripts for others to benefit from. Debian Live also does some detection, albeit not just for nvidia. Would be great if we all could share/integrate things so we'd all benefit and avoid duplication of work. http://live.debian.net/gitweb/?p=live-config.git;a=blob;f=components/1140-xserver-xorg Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#731964: [Pkg-owncloud-maintainers] Bug#731964: owncloud: please depend on mediawiki-classes instead of mediawiki
On Wednesday 11 December 2013 18:12:10 Simon McVittie wrote: > mediawiki 1:1.19.8+dfsg-2.1, with the split mediawiki-classes package, > has reached testing. Please switch owncloud's dependency to > mediawiki-classes (>= VERSION) | mediawiki (>= VERSION), or just > mediawiki-classes, or something. This change would also prevent installing (another) database server if you're using owncloud with sqlite, since mediawiki recommends mysql-server | postgresql-contrib -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#731964: Apply fix to 5.0.13 too?
Oeps, already done. But could you add the fix/change to the 5.0.13 too? TIA, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#731964: [Pkg-owncloud-maintainers] Bug#731964: Apply fix to 5.0.13 too?
"David Prévot" wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA256 > >Le 12/12/2013 02:57, Diederik de Haas a écrit : >> Oeps, already done. >> But could you add the fix/change to the 5.0.13 too? > >Can’t this wait for the upcoming 5.0.14 (expected in a few days)? That >shall be the last 5.0 update in Sid (php-dompdf is the last bit missing >for a proper 6.0 upload to Sid). > >https://ftp-master.debian.org/new/php-dompdf_0.6.0~beta3+dfsg0-1.html >http://people.debian.org/~taffit/owncloud/php-dompdf_0.6.0~beta3+dfsg-1_all.deb > >Regards > >David Excellent. I ment the 5.x series, so yes it can wait till the next release. Thanks for your great work :-) Regards, Diederik -- GPG: 0x138E41915C7EFED6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732596: deluged: debian-deluged can't write to it's home directory (/var/lib/deluged)
Package: deluged Version: 1.3.6-1 Severity: important When installing deluged the user 'debian-deluged' is created with /var/lib/deluged as it's home directory. The owner of that directory however is root and (therefor) only root is allowed to write to it. The directory /var/lib/deluged/config is properly chown-ed to debian-deluged, but so should /var/lib/deluged be. Severity set to important since deluge(d) defaults to downloading to it's home directory and therefor fails. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-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 deluged depends on: ii adduser3.113+nmu3 ii deluge-common 1.3.6-1 ii lsb-base 4.1+Debian12 ii python 2.7.5-5 ii python-libtorrent 0.16.11-2 deluged recommends no packages. deluged suggests no packages. -- Configuration Files: /etc/default/deluged changed: ENABLE_DELUGED=1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732596: deluged: debian-deluged can't write to it's home directory (/var/lib/deluged)
tags 732596 + patch thanks Find below the patch which should fix this bug. diff --git a/debian/deluged.postinst b/debian/deluged.postinst index f8e6f90..8d4a061 100644 --- a/debian/deluged.postinst +++ b/debian/deluged.postinst @@ -17,7 +17,7 @@ case "$1" in fi add_override debian-deluged adm 2750 /var/log/deluged -add_override debian-deluged debian-deluged 0750 /var/lib/deluged/config +add_override debian-deluged debian-deluged 0750 /var/lib/deluged ;; esac Cheers, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#732605: quassel: Please provide Vcs control fields
Package: quassel Severity: wishlist I was looking for a git repo (or sth like that), but couldn't find one. Providing the Vcs control fields allows ppl to browse all the sources for this package and possibly provide patches ;-) Cheers, Diederik -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (151, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735424: Different drivers for different graphic cards?
On Wednesday 15 January 2014 11:17:25 Karsten Malcher wrote: > In Debian there is only one driver package. > How it is able to suffer all the different graphic cards? aptitude show nvidia-driver output: Description: NVIDIA metapackage This version only supports GeForce 8xxx and higher of the Geforce GPUs plus corresponding Quadros and nforce. Look at the legacy packages for older cards. -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#711234: Version 1.1.1 is now available
According to http://sourceforge.net/projects/minidlna/files/minidlna/1.1.1/ version 1.1.1 was released on 2013-11-01. So if you're going to update the package, might as well do it to the very latest version. TIA -- GPG: 0x138E41915C7EFED6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693399: Alpha 4 or git snapshot in experimental?
Hi! Alpha 4 is released and it would be great if it was packaged and put in experimental. What would even more cool is if a git snapshot could be uploaded to experimental. Code now seems to be at https://github.com/keepassx/keepassx Cheers, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#730734: [Pkg-owncloud-maintainers] Bug#730734: owncloud: 6.0 not installable
On Thursday 28 November 2013 21:48:27 Shawn Landden wrote: > Package: owncloud > Severity: important > > owncloud : Depends: php-doctrine-common but it is not installable > Depends: php-dompdf but it is not installable That is correct and is a known issue, see http://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/Week-of-Mon-20131125/001042.html Regards, Diederik -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#731115: libqtwebkit4: Optionally depend on libgstreamer 1.0 libraries
Package: libqtwebkit4 Version: 2.2.1-7 Severity: wishlist Is it possible that this package libgstreamer dependencies are updated to the 1.0 versions of those libraries? If it would be an 'or' dependency, that would be fine too. Cheers, Diederik -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (151, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/4 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 libqtwebkit4 depends on: ii libc62.17-97 ii libgcc1 1:4.8.2-7 ii libglib2.0-0 2.36.4-1 ii libgstreamer-plugins-base0.10-0 0.10.36-1.1 ii libgstreamer0.10-0 0.10.36-1.2 ii libqt4-network 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtcore4 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtgui44:4.8.5+git121-g2a9ea11+dfsg1-2 ii libsqlite3-0 3.8.1-1 ii libstdc++6 4.8.2-7 ii libx11-6 2:1.6.2-1 ii libxrender1 1:0.9.8-1 ii multiarch-support2.17-97 libqtwebkit4 recommends no packages. libqtwebkit4 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731115: libqtwebkit4: Optionally depend on libgstreamer 1.0 libraries
On Monday 02 December 2013 22:06:59 you wrote: > Hi! I would like to know first why you want this lib compiled against > libgstreamer 1.0. Because it represents the 1.0 release and is 'officially' released. And afaik libqtwebkit4 is the only one still depended on the 0.1 version. > libgstreamer is a build-time dependency, so no, it can't be an optional one. With an 'or' dependency I meant "libgstreamer0.10-0 | libgstreamer1.0-0", not remove it completely. > Now let's suppose you have a very good reason to have it compiled against > libgstreamer 1.0. Do you know if it will compile if I change the build > dependencies? I have no idea whether it will compile against gstreamer 1.0 libraries and I also don't have a good reason to have it changed/adjusted, just a wish (hence the severity). -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#698343: owncloud: sends wrong content-type
On Thursday 17 January 2013 11:09:35 Michael Tsang wrote: > I have just installed owncloud on this server. However, when I try to > access it from a web browser, it shows the html code as text. That means > the php script fails to set the content-type. What's the output of "aptitude search ~iphp" ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692761: nvidia: gnome shell hangs randomly, errors in Xorg.0.log
On Thursday 08 November 2012 17:29:54 Andev wrote:
> How do I enable unstable repository?
Add the following line to your /etc/apt/sources.list:
deb http://ftp.debian.org/debian/ unstable main contrib non-free
You probably also want to create or add to /etc/apt/apt.conf the following:
Apt {
Default-Release "testing";
};
If your /etc/apt/sources.list has "wheezy" lines instead of testing, use wheezy
instead.
This will make sure you install packages from testing/wheezy by default and
only
install packages from other archives (unstable) when you explicitly say so.
To install the nvidia package from unstable, do the following:
aptitude install xserver-xorg-video-nvidia -t unstable
This should pull in that package from unstable including it's dependencies.
If it reports dependency issues, let aptitude offer you other suggestions until
the issues are resolved.
Another useful parameter for aptitude is "-s" which stands for simulate, so you
can experiment as much as you want (also as normal user) without actually
committing the changes.
> And I don't want to use an unsupported release other than for testing
> purposes. So, is it possible to downgrade to testing later on?
instead of "-t unstable", do "-t testing" (or wheezy).
If that doesn't work, add "/testing" to the package you want to downgrade, like
xserver-xorg-video-nvidia/testing. You may have to supply all the package names
you wish to downgrade (not sure why that is).
HTH,
Diederik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692761: nvidia: gnome shell hangs randomly, errors in Xorg.0.log
On Thursday 08 November 2012 18:31:05 Andreas Beckmann wrote: > > To install the nvidia package from unstable, do the following: > > aptitude install xserver-xorg-video-nvidia -t unstable > > It's probably easier to do this on the nvidia-glx package Agreed. Since the bug was reported against xserver-xorg-video-nvidia, I used that in my example. Diederik PS: I used nvidia-kernel-dkms myself, but will change that to nvidia-glx now. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691649: deluged: Move umask setting to /etc/default/deluged
Package: deluged
Version: 1.3.5-1
Severity: normal
Dear Maintainer,
If I want to change permissions on the downloaded files, I now have to modify
the init script (MASK setting). This is unfortunate since (afaik) this will
prevent you (the maintainer) from providing a new one.
To me, moving that setting to /etc/default/deluged (for example) seems more
logical and allows you to provide a new init script.
The same logic could be applied to the USER setting btw.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-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 deluged depends on:
ii adduser3.113+nmu3
ii deluge-common 1.3.5-1
ii lsb-base 4.1+Debian7
ii python 2.7.3~rc2-1
ii python-libtorrent 0.15.10-1+b1
deluged recommends no packages.
deluged suggests no packages.
-- Configuration Files:
/etc/default/deluged changed:
ENABLE_DELUGED=1
/etc/init.d/deluged changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="Deluge BitTorrent Daemon"
NAME="deluged"
DAEMON=/usr/bin/$NAME
DAEMON_ARGS="-d -c /var/lib/deluged/config -l /var/log/deluged/daemon.log -L
info"
USER=debian-deluged
MASK=0007
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
[ -x "$DAEMON" ] || exit 0
ENABLE_DELUGED=1
[ -r /etc/default/$NAME ] && . /etc/default/$NAME
[ -f /etc/default/rcS ] && . /etc/default/rcS
. /lib/lsb/init-functions
do_start()
{
if [ $ENABLE_DELUGED != 1 ]; then
log_progress_msg "Not starting ${DESC} ${NAME}, disabled in
/etc/default/${NAME}"
else
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
start-stop-daemon --start --background --quiet --pidfile $PIDFILE --exec
$DAEMON \
--chuid $USER --umask $MASK --test > /dev/null \
|| return 1
start-stop-daemon --start --background --quiet --pidfile $PIDFILE --make-
pidfile --exec $DAEMON \
--chuid $USER --umask $MASK -- $DAEMON_ARGS \
|| return 2
fi
}
do_stop()
{
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE
RETVAL="$?"
[ "$RETVAL" = "2" ] && return 2
rm -f $PIDFILE
return "$RETVAL"
}
case "$1" in
start)
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
stop)
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
;;
restart|force-reload)
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
0|1)
do_start
case "$?" in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to stop
log_end_msg 1
;;
esac
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac
:
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691652: deluged: Allow configuration of user/group deluged is run under
Package: deluged
Version: 1.3.5-1
Severity: wishlist
Dear Maintainer,
With the default setup all downloaded files are owned by
debian-deluged:debian-deluged and others have no access to the files.
There are a number of ways in which you can 'solve' this.
1. Become root and "chown (-R) user:group ", but you have to do
this for every downloaded file.
2. Change the init script to modify USER to debian-deluged:downloaders
(downloaders is a group I created myself)
3. Add your own user(s) to the debian-deluged group
4. Change the default group of debian-deluged to your preferred group (in
which you/your users are placed)
5. Change MASK setting to allow the world to read(/write) the files.
Option 2-4 can optionally be combined with changing MASK setting.
See also bug #691649.
The solution I'm using now is the following:
- Created (non-system) group downloaders and added myself and debian-deluged
to it
- Changed default group of debian-deluged to downloaders
- Changed MASK setting to give downloaders group full permissions
It would be great if this or a scenario like this, can be configured through
debconf or sth like that.
Cheers,
Diederik
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-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 deluged depends on:
ii adduser3.113+nmu3
ii deluge-common 1.3.5-1
ii lsb-base 4.1+Debian7
ii python 2.7.3~rc2-1
ii python-libtorrent 0.15.10-1+b1
deluged recommends no packages.
deluged suggests no packages.
-- Configuration Files:
/etc/default/deluged changed:
ENABLE_DELUGED=1
/etc/init.d/deluged changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="Deluge BitTorrent Daemon"
NAME="deluged"
DAEMON=/usr/bin/$NAME
DAEMON_ARGS="-d -c /var/lib/deluged/config -l /var/log/deluged/daemon.log -L
info"
USER=debian-deluged
MASK=0007
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
[ -x "$DAEMON" ] || exit 0
ENABLE_DELUGED=1
[ -r /etc/default/$NAME ] && . /etc/default/$NAME
[ -f /etc/default/rcS ] && . /etc/default/rcS
.. /lib/lsb/init-functions
do_start()
{
if [ $ENABLE_DELUGED != 1 ]; then
log_progress_msg "Not starting ${DESC} ${NAME}, disabled in
/etc/default/${NAME}"
else
# Return
# 0 if daemon has been started
# 1 if daemon was already running
# 2 if daemon could not be started
start-stop-daemon --start --background --quiet --pidfile $PIDFILE --exec
$DAEMON \
--chuid $USER --umask $MASK --test > /dev/null \
|| return 1
start-stop-daemon --start --background --quiet --pidfile $PIDFILE
--make-pidfile --exec $DAEMON \
--chuid $USER --umask $MASK -- $DAEMON_ARGS \
|| return 2
fi
}
do_stop()
{
# Return
# 0 if daemon has been stopped
# 1 if daemon was already stopped
# 2 if daemon could not be stopped
# other if a failure occurred
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE
RETVAL="$?"
[ "$RETVAL" = "2" ] && return 2
rm -f $PIDFILE
return "$RETVAL"
}
case "$1" in
start)
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
stop)
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
;;
restart|force-reload)
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
0|1)
do_start
case "$?" in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to stop
log_end_msg 1
;;
esac
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac
:
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691854: exim4-doc-html: incorrect paths in html files
Package: exim4-doc-html Version: 4.80-2 Severity: minor Dear Maintainer, All the html pages contain links to pictures/script which are not valid for this package (they are valid for the online version). Some examples: location for the google+ picture is "../../../../i/gplus-32.png" location for expand picture is "../../../../doc/plus-12x12.png" (index.html) location for contents picture is "../../../../doc/contents.png" location for script is "../../../../doc/index.js" This causes the following lines in apache's error.log with each page request: [Tue Oct 30 13:08:10 2012] [error] [client client-ip] File does not exist: /var/www/doc, referer: http://server/exim-docs/ch01.html [Tue Oct 30 13:08:10 2012] [error] [client client-ip] File does not exist: /var/www/i, referer: http://server/exim-docs/ch01.html [Tue Oct 30 13:08:10 2012] [error] [client client-ip] File does not exist: /var/www/doc, referer: http://server/exim-docs/ch01.html [Tue Oct 30 13:08:10 2012] [error] [client client-ip] File does not exist: /var/www/doc, referer: http://server/exim-docs/ch01.html [Tue Oct 30 13:08:10 2012] [error] [client client-ip] File does not exist: /var/www/i, referer: http://server/exim-docs/ch01.html [Tue Oct 30 13:08:10 2012] [error] [client client-ip] File does not exist: /var/www/doc, referer: http://server/exim-docs/ch01.html Cheers, Diederik -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688394: [Pkg-owncloud-maintainers] Bug#688394: owncloud: can't add new users
notfound 688394 4.0.7debian-1 found 688394 4.0.4debian2-2 tags 688394 = moreinfo unreproducible thanks On Saturday 22 September 2012 13:53:40 Oz N wrote: > Package: owncloud > Version: 4.0.7debian-1 > Severity: normal > Tags: patch > > Hi, > after the default install in debian I can't add new users ... > applying the patch: > > # diff /usr/share/owncloud/settings/js/users.js > # /usr/share/owncloud/settings/js/users.js.ORG > 216c216 > < //location.reload(); > --- > > > location.reload(); > > seems to solve the problem Hi, Can you (re-) run reportbug against the owncloud package, so we also get information about the dependencies + versions installed on the affected system? Furthermore the patch you provided does fix the issue with version 4.0.4debian2-2, but that function call isn't present in version 4.0.7debian-1. At least not on a clean debian system, hence the request for more information. Cheers, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688394: [Pkg-owncloud-maintainers] Bug#688394: owncloud: can't add new users
tags 688394 - moreinfo unreproducible thanks On Saturday 22 September 2012 16:41:40 Oz Nahum Tiram wrote: > Well, I also installed the version 4.0.7debian-1, it seemed to solve > the problem. > Do you still need the bug report re-run ? No, that's not needed. For next time it would be preferable to have the full output from reportbug though. > If not you can close the bug, the package from sid solves it. The issue was present in the current version in testing, so thanks for reporting it. The bug will be closed with the next upload to testing-proposed-updates which is due shortly. Thanks, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687324: owncloud: Install wizard doesn't run
On Sunday 23 September 2012 01:27:18 Karl Sackett wrote: > > Can you try 4.0.4debian-2 which is available in testing-proposed-updates? > > I just installed 4.0.4debian-2 on a clean debian system, but could not > > reproduce your issue. > > The command I used was "aptitude install owncloud-sqlite owncloud" and > > accepted aptitude's first proposal. > > Both owncloud and owncloud-sqlite are at 4.0.4debian2-2. > I'm still having this problem. > > All of the php files in /usr/share/owncloud behave this way. > The file contents is dumped to the browser window without > being processed Please keep the bug CC-ed so everyone can follow along. I'm pretty sure this is not an owncloud bug, but most likely a error in your apache installation/configuration. Do other php files work or are only owncloud's php files not working? To test that, create /var/www/test.php and put in the following contents: PHP Test page PHP Info When you then request http:///test.php and you only see a heading with "PHP Info" then that means the appropriate php module isn't installed or loaded. "aptitude search ~ilibapache" should at least return "libapache2-mod-php5" and "ls -l /etc/apache2/mods-enabled/ | grep php" should return "../mods- available/php5.conf" and "../mods-available/php5.load". If that's not the case, then it surely is an apache/php install/config problem. HTH, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687324: [Pkg-owncloud-maintainers] Bug#687324: owncloud: Install wizard doesn't run
On Sunday 23 September 2012 04:09:32 Karl Sackett wrote: > On Sat, Sep 22, 2012 at 7:10 PM, Diederik de Haas wrote: > > When you then request http:///test.php and you only see a heading > > with "PHP Info" then that means the appropriate php module isn't > > installed or loaded. "aptitude search ~ilibapache" should at least > > return "libapache2-mod-php5" and "ls -l /etc/apache2/mods-enabled/ | > > grep php" should return "../mods- available/php5.conf" and > > "../mods-available/php5.load". > > I found the problem: the owncloud package doesn't depend on > libapache2-mod-php5, so it wasn't automatically installed when I > installed owncloud itself. After I manually installed libapache2-mod-php5 > everything started working. So adding that dependency to the owncloud > package should fix the bug, I think. The owncloud package depends on php5, which depends on libapache2-mod-php5 (or libapache2-mod-php5filter or php5-cgi or php5-fpm), so it should've worked. Below you'll find the list of php/apache packages installed on my freshly installed testing system and comparing it to your output might reveal why libapache2-mod-php5 wasn't automatically installed. $ aptitude -F "%c%M %p %v" search '~i(php|apache)' iA apache2 2.2.22-11 iA apache2-mpm-prefork2.2.22-11 iA apache2-utils2.2.22-11 iA apache2.2-bin 2.2.22-11 iA apache2.2-common 2.2.22-11 iA libapache2-mod-php5 5.4.4-7 iA libphp-phpmailer5.1-1 iA php-crypt-blowfish 1.1.0~RC2-1 iA php-getid3 1.9.3-1 iA php-mdb2 2.5.0b3-2 iA php-mdb2-schema 0.8.5-1 iA php-pear5.4.4-7 iA php-sabredav 1.6.2-3 iA php-xml-dtd0.5.2+dfsg1-1 iA php-xml-parser 1.3.4-6 iA php-xml-serializer0.20.2-2 iA php5 5.4.4-7 iA php5-cli 5.4.4-7 iA php5-common 5.4.4-7 iA php5-curl5.4.4-7 iA php5-gd 5.4.4-7 iA php5-sqlite 5.4.4-7 > Thanks for your help. You're welcome. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687324: [Pkg-owncloud-maintainers] Bug#687324: owncloud: Install wizard doesn't run
On Sunday 23 September 2012 21:03:10 Karl Sackett wrote: > i php5-cgi 5.4.4-7 On Sunday 23 September 2012 13:10:22 Diederik de Haas wrote: > The owncloud package depends on php5, which depends on libapache2-mod-php5 > (or libapache2-mod-php5filter or php5-cgi or php5-fpm), so it should've > worked. You've manually installed php5-cgi which satisfies (one of) the dependency of the php5 package, therefor libapache2-mod-php5 wasn't installed. So if you had correctly configured php5-cgi you could've made it work as well (I think; I have no experience with php5-cgi package). The description of php5-cgi contains "Note that MOST Apache users probably want the libapache2-mod-php5 package". So it's (likely) possible to configure php handling with cgi, but it's easier with libapache2-mod-php5 ;-) With 'aptitude why/why-not ' you can probably figure out why a certain package is installed (why) or why you don't want to remove it (why-not). Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678694: preseed_fetch fails with relative url
Package: preseed
Severity: normal
Tags: d-i
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Trying to install Debian Wheezy in a VirtualBox image using preseeding and
trying to use the following line:
d-i preseed/late_command string preseed_fetch \
/scripts/late_command.sh /root/late_command.sh
* What exactly did you do (or not do) that was effective (or
ineffective)?
- Create a VirtualBox (VB) image
- Assign debian-wheezy-DI-a1-amd64-businesscard.iso to the CDROM
drive
- Start the VB image and when presented with d-i start screen,
press TAB to add "auto=true url=my.server.com DEBCONF_DEBUG=5" so it
uses my
preseed file from http://my.server.com/d-i/wheezy/./preseed.cfg
I only added DEBCONF_DEBUG=5 when deciding to report a bug,
without it, it also failed.
- At the very end (after GRUB install) I get an error msg saying
'Execution of preseeded command "preseed_fetch
/scripts/late_command.sh /root/late_command.sh" failed with exit
code 2.'
Going to Ctl+Alt+F4, I see the error "can't open
'/usr/lib/fetch-url//./scrips/late_command.sh'"
* What was the outcome of this action?
The requested file was not downloaded to the requested location.
Relevant section of /var/log/installer/syslog:
Jun 23 17:21:03 debconf: --> GET preseed/late_command
Jun 23 17:21:03 debconf: <-- 0 preseed_fetch /scripts/late_command.sh
/root/late_command.sh
Jun 23 17:21:04 preseed: running preseed command
preseed/late_command: preseed_fetch /scripts/late_command.sh
/root/late_command.sh
Jun 23 17:21:04 log-output: /bin/fetch-url:
Jun 23 17:21:04 log-output: .:
Jun 23 17:21:04 log-output: line 33:
Jun 23 17:21:04 log-output: can't open
'/usr/lib/fetch-url//./scripts/late_command.sh'
Jun 23 17:21:04 log-output:
Jun 23 17:21:04 debconf: --> SUBST preseed/command_failed COMMAND
preseed_fetch /scripts/late_command.sh /root/late_command.sh
Jun 23 17:21:04 debconf: Adding [COMMAND] -> [preseed_fetch
/scripts/late_command.sh /root/late_command.sh]
Jun 23 17:21:04 debconf: <-- 0
Jun 23 17:21:04 debconf: --> SUBST preseed/command_failed CODE 2
Jun 23 17:21:04 debconf: Adding [CODE] -> [2]
Jun 23 17:21:04 debconf: <-- 0
Jun 23 17:21:04 debconf: --> INPUT critical preseed/command_failed
Jun 23 17:21:04 debconf: <-- 0 question will be asked
* What outcome did you expect instead?
That the file was downloaded to the specified location (and the next
step would be to execute it).
This bug may have similarities with bug #573138, but when trying to
use preseed/include it failed to retrieve that file with the
following error:
"The file needed for preconfiguration could not be retrieved from
http://my.server.com/d-i/wheezy/./core-pkgs.cfg. The installation
will proceed in non-automated mode."
Ctl+Alt+F4 showed the following line (ie no error msg):
"preseed: successfully loaded preseed file from
http://my.server.com/d-i/wheezy/./preseed.cfg";
When loading the various urls in my browser, they all loaded fine.
I haven't tried with absolute urls, since that would 'destroy' the
portability of my preseed file(s).
My preseed.cfg file:
=
Contents of the preconfiguration file (for wheezy)
### Localization
# Preseeding only locale sets language, country and locale.
#d-i debian-installer/locale string en_US
# The values can also be preseeded individually for greater
# flexibility.
d-i debian-installer/language string en
d-i debian-installer/country string NL
d-i debian-installer/locale string en_US.UTF-8
d-i console-keymaps-at/keymap select us
d-i keyboard-configuration/xkb-keymap select us
# Optionally specify additional locales to be generated.
#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8
d-i mirror/country string nl
d-i mirror/http/hostname string ftp.debian.org
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string http://192.168.1.5:3142
#d-i mirror/http/proxy seen false
#Additional repositories
d-i apt-setup/local0/repository string http://ftp.debian.org/debian
sid main
d-i apt-setup/local0/comment string Unstable repository
d-i apt-setup/local0/source boolean false
d-i passwd/root-password password root
d-i passwd/root-password-again password root
d-i passwd/user-fullname string Debian User
d-i passwd/username string debian
d-i passwd/user-password password debian
d-i passwd/user-password-again password debian
d-i partman-auto/disk string /dev/sda
d-i partman-auto/method string regular
d-i partman-auto/expert_recipe string \
boot-root :: \
8000 8000 8000 ext4 \
$primary{ } $bootable{ } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext4 } \
Bug#678694: Also reported on Launchpad
See https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/909139 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655125: closed by Alessio Treglia (Bug#655125: fixed in smplayer 0.7.0-1)
On Thursday 16 February 2012 12:36:29 Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the smplayer package: > > #655125: smplayer: new upstream release (0.6.10) > > It has been closed by Alessio Treglia . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Alessio Treglia > by replying to this email. Awesome, thank you very much :-D Just one question: Shouldn't the Depends field be "mplayer | mplayer2" so that mplayer won't be installed if mplayer2 is already installed? (Optionally mention in the Description that it's also a front-end for MPlayer2) Regards, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655125: Another new version (0.7.0)
There's yet another new release, now it's version number is 0.7.0, see http://smplayer.sourceforge.net/forum/viewtopic.php?f=3&t=5255 Most important changes since 0.6.10: - New favorite menu, where you can add your favorite videos, music, streams, youtube videos... It's also possible to add submenus. - Support for youtube. Now you can open urls like http://www.youtube.com/watch?v=. using the Open -> URL dialog or dragging a link from a browser to the smplayer window. - Support for mplayer2 (http://www.mplayer2.org). It's a fork of mplayer with interesting features like precise seeking, ordered chapters in mkv videos and better pause handling (e.g. seek works while the video is paused). - New translation: croatian. Regards, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681138: owncloud: setup sets wrong db entrys which prevent using cal/carddav
On Tuesday 10 July 2012 22:36:38 o0u wrote: > Tags: upstream Seems to be bug oc-1199 http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-1199 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681636: apt: It looks like Default-Release is not respected anymore
Package: apt Version: 0.9.7.1 Severity: normal Dear Maintainer, * What led up to the situation? Doing aptitude update and then aptitude safe-upgrade on my server which has Default-Release set to "testing". * What was the outcome of this action? All packages were taken from sid instead of pulling them in when they hit the testing release. * What outcome did you expect instead? That the packages would only be upgraded when they had transitioned to testing (obvious exception would be packages explicitly pulled from sid, but that was not the case). Default-Release set to "testing" stopped working not too long ago (don't know for sure when, but a month ago it did work properly). Before that it always upgraded packages when they transitioned to testing. Cheers, Diederik -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "i386"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "0"; APT::Install-Suggests "0"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image.*"; APT::NeverAutoRemove:: "^kfreebsd-image.*"; APT::NeverAutoRemove:: "^linux-restricted-modules.*"; APT::NeverAutoRemove:: "^linux-ubuntu-modules-.*"; APT::NeverAutoRemove:: "^gnumach$"; APT::NeverAutoRemove:: "^gnumach-image.*"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Never-MarkAuto-Sections:: "oldlibs"; APT::Never-MarkAuto-Sections:: "restricted/oldlibs"; APT::Never-MarkAuto-Sections:: "universe/oldlibs"; APT::Never-MarkAuto-Sections:: "multiverse/oldlibs"; APT::Default-Release "testing"; APT::Architectures ""; APT::Architectures:: "i386"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "1"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "2"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-9n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "3"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-9"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "4"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "5"; APT::Compressor::lzma::CompressArg ""; APT::Compressor::lzma::CompressArg:: "--format=lzma"; APT::Compressor::lzma::CompressArg:: "-9"; APT::Compressor::lzma::UncompressArg ""; APT::Compressor::lzma::UncompressArg:: "--format=lzma"; APT::Compressor::lzma::UncompressArg:: "-d"; APT::CompressorName ""; APT::CompressorExtension "."; APT::CompressorBinary ""; APT::CompressorCost "100"; APT::CompressorCompressArg ""; APT::CompressorCompressArg:: "-9"; APT::CompressorUncompressArg ""; APT::CompressorUncompressArg:: "-d"; Dir "/"; Dir::State "var/lib/apt/"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::mirrors "mirrors/"; Dir::State::extended_states "extended_states"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt/"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt/"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::sourceparts "sources.list.d"; Dir::Etc::vendorlist "vendors.list"; Dir::Etc::vendorparts "vendors.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::netrc "auth.conf"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Etc::preferencesparts "preferences.d"; Dir::Etc::trusted "trusted.gpg"; Dir::Etc::trustedparts "trusted.gpg.d"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::solvers ""; Dir::Bin::solvers:: "/usr/lib/apt/solvers"; Dir::Bin::dpkg "/usr/bin/dpkg"; Dir::Bin::bzip2 "/bin/bzip2"; Dir::Bin::xz "/usr/bin/xz"; Dir::Media ""; Dir::Media::MountPath "/media/apt"; Dir::Log "var/log/apt"; Dir::Log::Termina
Bug#681636: Additional information
When thinking some more about when it change in behaviour happened, I realised
that the freeze started about 2 weeks ago, so it could very well be related to
that.
It looks like the "apt-config dump" interpreted /etc/apt/apt.conf correctly,
but
in case the format of that file is relevant, here's the content of that file:
Apt {
Default-Release "testing";
Install-Recommends "0";
};
Aptitude {
Autoclean-After-Update "true";
};
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681636: Looks like this bug is invalid
Hi, I just got an updated pkg (binutils, version 2.22-7.1) on my sid box, but it didn't show up on my server, which has Default-Release "testing". The only way to get that version installed on my server was by "apt-get/aptitude install binutils -t sid". Don't know why "apt-get dist-upgrade" or "aptitude full-upgrade" didn't upgrade the package though. So it looks like this bug report is invalid. If I can't reproduce this bug in the coming week, I'll close it myself. If someone else (f.e. maintainers) already know it is invalid they can close this bug too of course ;-) Cheers, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681169: Increasing severity
severity 681169 important thanks Increasing severity since it's rather important to be able to create users besides the admin user. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681138: Specifying upstream bug
forwarded 681138 http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-1199 thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687324: owncloud: Install wizard doesn't run
On Tuesday 11 September 2012 20:22:46 Karl Sackett wrote: > Package: owncloud > Version: 4.0.4debian-1 > Severity: important Can you try 4.0.4debian-2 which is available in testing-proposed-updates? I just installed 4.0.4debian-2 on a clean debian system, but could not reproduce your issue. The command I used was "aptitude install owncloud-sqlite owncloud" and accepted aptitude's first proposal. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681169: Bug is also fixed in current testing
fixed 681169 4.0.4debian2-3 Verified it works with the version currently in testing by upgrading my existing vms and also 2 vms created from scratch. It works in all of them, so marking bug report accordingly. Cheers, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703313: nvidia-kernel-dkms: Confirmation of this bug
Package: nvidia-kernel-dkms Version: 304.84-1 Followup-For: Bug #703313 I don't know if it didn't happen with 304.64-4, but I have just tested whether switching to VT[1-6] works, and indeed the display is turned off and when switching to VT7, ie X session, the display is turned on again. Ran 'whole' reportbug instead of a simple msg in case my details may help. Feel free to ask for more info and/or testing. -- Package-specific info: uname -a: Linux bagend 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux /proc/version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.84 Wed Feb 27 04:58:49 PST 2013 GCC version: gcc version 4.6.3 (Debian 4.6.3-15) lspci 'VGA compatible controller [0300]': 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2304] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.00] Console: colour VGA+ 80x25 [0.633587] vgaarb: device added: PCI::05:00.0,decodes=io+mem,owns=io+mem,locks=none [0.633587] vgaarb: loaded [0.633587] vgaarb: bridge control possible :05:00.0 [1.892466] PCI-DMA: Disabling AGP. [1.892565] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture [2.112289] Linux agpgart interface v0.103 [6.041673] nvidia: module license 'NVIDIA' taints kernel. [6.142593] nvidia :05:00.0: setting latency timer to 64 [6.142607] vgaarb: device changed decodes: PCI::05:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [6.142961] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.84 Wed Feb 27 04:58:49 PST 2013 [7.492324] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:05:00.1/sound/card1/input6 [7.492599] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:05:00.1/sound/card1/input7 [7.492811] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:05:00.1/sound/card1/input8 [7.493024] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:05:00.1/sound/card1/input9 OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jan 25 00:34 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 43 Jan 25 00:34 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jan 25 00:34 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Jan 25 00:34 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 59 Jan 25 00:34 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 51 Jan 25 00:34 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Jan 25 00:34 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 36 Jan 25 00:34 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Jan 25 00:34 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 23 Jan 25 00:34 /etc/alternatives/nvidia -> /usr/lib/nvidia/current lrwxrwxrwx 1 root root 51 Jan 25 00:34 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 51 Jan 25 00:34 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 59 Jan 25 00:34 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 67 Jan 25 00:34 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 33 Jan 25 00:34 /etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/current/libglx.so lrwxrwxrwx 1 root root 59 Jan 25 00:34 /etc/alternatives/nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 44 Jan 25 00:34 /etc/alternatives/nvidia--nvidia-bug-report.sh ->
Bug#703313: nvidia-kernel-dkms: Confirmation of this bug
On Friday 29 March 2013 14:39:39 Diederik de Haas wrote: > Package: nvidia-kernel-dkms > Version: 304.84-1 > Followup-For: Bug #703313 Just did an "aptitude install nvidia-glx -t experimental" and rebooted my machine and now VT[1-6] do work. So it looks like version 313.26-1 fixes this bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637808: installation-report: Graphical Installer doesn't work properly
> If someone has a virtual machine system handy, trying to locate when the > problem appeared would be nice, e.g. using the dailies. Images downloaded through http://cdimage.debian.org/cdimage/daily-builds/daily/ Tested with VirtualBox 4.1 on a Debian sid install on amd64. I've used the testing businesscard image from the respective dates, amd64 flavour. Error msg (from /var/log/syslog, through Ctl+Alt+F2): debconf: cdebconf_gtk (process:
Bug#640019: [nvidia-kernel-source] No longer works
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. --- > 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 idea where to apply it. > > I removed the packages and attempted a reinstall > Both dkms and m-a builds fail to install the module (even though there is > no dkms notification of such). > > nvidia-glx is not (re-)installable at present > Hi David, See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639737 Below you'll find my /etc/X11/xorg.conf.d/20-nvidia.conf: #This section is a workaround for the ABI mismatch between 280.13-2 and Xorg #This workaround was mentioned in bug 639737 Section "ServerFlags" Option "IgnoreABI" "true" EndSection Section "Device" Identifier "Configured Video Device" Driver "nvidia" EndSection As far as I know there are a couple of workarounds: 1. Downgrade X to version 1.10 (as described by Andreas in the aforementioned bug) 2. Downgrade nvidia drivers to the testing versions 3. Upgrade to the (beta) version in experimental (285.03) and add the IgnoreABI flag. HTH, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639737: xserver-xorg-video-nvidia: Please update ABI compatibility and add abi 11 for video
On Tuesday 30 August 2011 15:54:41 Eric Valette wrote:
> On 08/30/2011 03:45 PM, Julien Cristau wrote:
> > On Mon, Aug 29, 2011 at 21:35:46 +0200, Eric Valette wrote:
> >> Package: xserver-xorg-video-nvidia
> >> Version: 285.03-1
> >> Severity: normal
> >>
> >> The new .11 xorg driver ABI has been updated to 11. As the nvidia driver
> >> supports it at least enough to be useable via kde4, please add the
> >> xorg-video-abi- compatibility.
> >
> > There's a known issue with nvidia's libglx with that version, so I'm not
> > sure it's a good idea quite yet.
> > http://lists.x.org/pipermail/xorg-devel/2011-August/024752.html
>
> I broke my X system with a bogus dist-upgrade and was forced to
> reinstall libglx and nvidei xorg driver :-(
Hi,
I did a safe-upgrade, which upgraded nvidia-graphics-drivers to 280.13-2, and
after reboot, X didn't
start (properly).
In /var/log/Xorg.0.log I found a/the message about mismatching ABI version.
Since I'm subscribed to this list, I was aware of a potential problem (hence
the reboot) and
therefor was able to quickly find the relevant bug report (639737).
That bug report describes how to fix/workaround it ('therefore the "IgnoreABI"
option needs to be
enabled, see xorg.conf(5)'). (Haven't tried if it worked yet)
I do have apt-listbugs installed, but since this bug was/is severity normal
(and marked as done)
I didn't get a warning or sth like that.
I got X working again by downgrading (and holding) to the testing versions of
nvidia-kernel-dkms and
xserver-xorg-video-nvidia which caused those and related packages to be
downgraded:
partly snippet from /var/log/aptitude:
=
[DOWNGRADE] libgl1-nvidia-glx 280.13-2 -> 280.13-1
[DOWNGRADE] nvidia-alternative 280.13-2 -> 280.13-1
[DOWNGRADE] nvidia-glx 280.13-2 -> 280.13-1
[DOWNGRADE] nvidia-vdpau-driver 280.13-2 -> 280.13-1
[DOWNGRADE] xserver-xorg-core 2:1.11.0-1 -> 2:1.10.4-1
[DOWNGRADE] xserver-xorg-input-evdev 1:2.6.0-2+b2 -> 1:2.6.0-2+b1
[DOWNGRADE] xserver-xorg-video-nvidia 280.13-2 -> 280.13-1
[DOWNGRADE] xserver-xorg-video-vesa 1:2.3.0-7+b1 -> 1:2.3.0-7
[HOLD] nvidia-kernel-dkms
=
But if I wasn't subscribed to this list, I probably wouldn't have found this
bug report and therefor
wouldn't have found the workaround.
And since this bug is closed and doesn't (didn't) have a high enough severity,
apt-listbug didn't
issue a warning that the upgrade would make X stop working and/or alerted me to
the bug report
describing the workaround.
Shouldn't there be a warning or sth like that mentioning the workaround when
upgrading to 280.13-2?
And/or shouldn't this bug be reopened (or sth like that) with a higher
severity, so ppl with apt-
listbug will get notified and prevents the current version from entering
testing?
Regards,
Diederik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643783: kmymoney: KMM 4.6 is released
Package: kmymoney Version: 4.5.3-2 Severity: wishlist Dear Maintainer, KMyMoney version 4.6 is released, see http://mail.kde.org/pipermail/kmymoney/2011-August/000420.html Please consider packaging this new version. Thanks in advance, Diederik -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/3 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 kmymoney depends on: ii kdebase-runtime 4:4.6.5-1+b1 ii kdepim-runtime4:4.4.11.1-2 ii kmymoney-common 4.5.3-2 ii libaqbanking335.0.16-1 ii libc6 2.13-21 ii libgcc1 1:4.6.1-13 ii libgpgme++2 4:4.6.5-1 ii libgwengui-qt4-0 4.3.0-1 ii libgwenhywfar60 4.3.0-1 ii libical0 0.44-3 ii libkabc4 4:4.6.5-1 ii libkdecore5 4:4.6.5-2 ii libkdeui5 4:4.6.5-2 ii libkfile4 4:4.6.5-2 ii libkholidays4 4:4.6.5-1 ii libkhtml5 4:4.6.5-2 ii libkio5 4:4.6.5-2 ii libkutils44:4.6.5-2 ii libofx4 1:0.9.4-2 ii libqt4-dbus 4:4.7.3-8 ii libqt4-network4:4.7.3-8 ii libqt4-sql4:4.7.3-8 ii libqt4-svg4:4.7.3-8 ii libqt4-xml4:4.7.3-8 ii libqtcore44:4.7.3-8 ii libqtgui4 4:4.7.3-8 ii libstdc++64.6.1-13 kmymoney recommends no packages. kmymoney suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711745: [Pkg-owncloud-maintainers] Bug#711745: owncloud: New upstream version 5.0 available
On Sunday 09 June 2013 11:07:23 Tobias Frost wrote: > Package: owncloud > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Add experimental to your sources.list and you should be good to go ;-) http://packages.debian.org/experimental/owncloud -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722213: [Pkg-owncloud-maintainers] Bug#722213: owncloud: contains unregistered embedded copy of php-patchwork-utf8
On Monday 09 September 2013 08:17:53 Helmut Grohne wrote: > It has come to my attention that owncloud fully embeds[1] the > php-patchwork-utf8 package. This practise is discouraged by the Debian > policy, but not prohibited. Please investigate whether you can use the > php-patchwork-utf8 package instead of embedding it. See bug #721889 -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#724651: Nvidia driver and X Segmentation fault - Fatal server
On Thursday 26 September 2013 11:04:44 Luigi Cirillo wrote: > << /etc/X11/xorg.conf >> > # nvidia-xconfig: X configuration file generated by nvidia-xconfig > # nvidia-xconfig: version 304.48 (pbuilder@cake) Wed Sep 12 10:54:51 UTC > 2012 > > > > Section "Device" > Identifier "Device0" > Driver "nvidia" > VendorName "NVIDIA Corporation" > EndSection > > ^^ /etc/X11/xorg.conf ^^ What happens if you clear/remove your /etc/X11/xorg.conf and place the above section in /etc/X11/xorg.conf.d/20-nvidia.conf as described in [1] and reboot? There were a number of warnings related to your xorg.conf settings. HTH [1] https://wiki.debian.org/NvidiaGraphicsDrivers#configure -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#724666: Lowering severity
severity 724666 normal thanks Lowering the severity since it doesn't make live-config unusable. It does make kwallet unusable (which caused me to choose grave) and thereby a major effect on the usability of the resulting KDE image(s). -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#714328: postgresql-9.3: Postinstall script fails
Package: postgresql-9.3 Version: 9.3~beta2-1 Severity: important Dear Maintainer, While running aptitude safe-upgrade, the post-install scripts fails: The following partially installed packages will be configured: postgresql-9.3 No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Setting up postgresql-9.3 (9.3~beta2-1) ... [] Starting PostgreSQL 9.3 database server: main[] The PostgreSQL server failed to start. Please check the log output: 2013-06-28 01:43:16 CEST FATAL: database files are incompatible with server 2013-06-28 01:43:16 CEST DETAIL: The database cluster was initialized with CATALOG_VERSION_NO 201305061, but [FAILerver was compiled with CATALOG_VERSION_NO 201306121. 2013-06-28 01:43:16 CEST HINT: It looks like you need to initdb. ... failed! failed! invoke-rc.d: initscript postgresql, action "start" failed. dpkg: error processing postgresql-9.3 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: postgresql-9.3 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up postgresql-9.3 (9.3~beta2-1) ... [] Starting PostgreSQL 9.3 database server: main[] The PostgreSQL server failed to start. Please check the log output: 2013-06-28 01:43:18 CEST FATAL: database files are incompatible with server 2013-06-28 01:43:18 CEST DETAIL: The database cluster was initialized with CATALOG_VERSION_NO 201305061, but [FAILerver was compiled with CATALOG_VERSION_NO 201306121. 2013-06-28 01:43:18 CEST HINT: It looks like you need to initdb. ... failed! failed! invoke-rc.d: initscript postgresql, action "start" failed. dpkg: error processing postgresql-9.3 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: postgresql-9.3 Note that I've recently install postgresql for the first time and I've only created 1 db to 'play'. If I need to do 'things' with postgresql to provide additional information, you'll likely have to tell me how to do it. I am familiar with (adminstrating) Debian though. Cheers, Diederik -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 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 postgresql-9.3 depends on: ii libc6 2.17-5 ii libcomerr2 1.42.8-1 ii libgssapi-krb5-2 1.10.1+dfsg-6 ii libkrb5-3 1.10.1+dfsg-6 ii libldap-2.4-2 2.4.31-1+nmu2 ii libpam0g 1.1.3-9 ii libpq5 9.3~beta2-1 ii libssl1.0.01.0.1e-3 ii libxml22.9.1+dfsg1-2 ii locales2.17-5 ii postgresql-client-9.3 9.3~beta2-1 ii postgresql-common 145 ii ssl-cert 1.0.32 ii tzdata 2013c-2 postgresql-9.3 recommends no packages. Versions of packages postgresql-9.3 suggests: pn locales-all pn oidentd | ident-server -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714328: [Pkg-postgresql-public] Bug#714328: postgresql-9.3: Postinstall script fails
Martin Pitt wrote: >Hello Diederik, Hi Martin, >Ah, sorry about that. The DB format changed between beta1 and beta2, >so this upgrade doesn't work with existing clusters. I'll add some >preinst magic to guard against that. No problem and excellent. >In the meantime, if you don't need the DB any more, please run > > # pg_dropcluster 9.3 main Did that, upgraded, ran '#pg_createcluster 9.3 main' and '#/etc/init.d/postgresql start' (it didn't start after the upgrade, normal?) and I was up and running again :-) Cheers! Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655125: smplayer: new upstream release (0.6.10)
Package: smplayer Version: 0.6.9-4 Severity: wishlist Dear Maintainer, The developer of SMPlayer resumed development again and made a new version available, namely 0.6.10. See http://smplayer.sourceforge.net/forum/viewtopic.php?f=3&t=5209 and http://smplayer.sourceforge.net/downloads.php for the updated sources. Please consider upgrading. Regards, Diederik -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 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 smplayer depends on: ii libc6 2.13-24 ii libgcc1 1:4.6.2-11 ii libqt4-network 4:4.7.4-2 ii libqt4-xml 4:4.7.4-2 ii libqtcore4 4:4.7.4-2 ii libqtgui4 4:4.7.4-2 ii libstdc++6 4.6.2-11 ii mplayer 3:1.0~rc4+svn20120108-0.0 ii zlib1g 1:1.2.3.4.dfsg-3 Versions of packages smplayer recommends: ii smplayer-themes0.1.20+dfsg-1 ii smplayer-translations 0.6.9-4 smplayer suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655125: Should also fix bug #610204
According to 0.6.10's changelog (http://smplayer.sourceforge.net/forum/viewtopic.php?f=3&t=199) there's now a configuration dialog which allows the user to select which vdpau codec to use. See also http://smplayer.sourceforge.net/forum/viewtopic.php?f=3&t=4403 It looks like it will also fix bug #610204 Regards, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637798: deluge: sudden crash: 'X window system error'
Package: deluge
Version: 1.3.3-2
Followup-For: Bug #637798
Dear Maintainer,
* What led up to the situation?
Trying to start deluge(-gtk) on my PC, connecting to deluged running
on server.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Typed 'deluge' in KRunner (Alt+F2 on KDE 4.7.4), selected the deluged
daemon from my server and click on the Connect button.
* What was the outcome of this action?
Deluge crashed with an 'X window system error'.
I found that out by starting deluge from the commandline with
'deluge -L debug'. Full output:
[INFO] 09:24:01 main:119 Deluge ui 1.3.3
[DEBUG ] 09:24:01 main:120 options: {'loglevel': 'debug',
'default_ui': None, 'args': None, 'quiet': False, 'ui': None,
'logfile': None, 'config': None}
[DEBUG ] 09:24:01 main:121 args: []
[DEBUG ] 09:24:01 main:122 ui_args: []
[INFO] 09:24:01 main:125 Starting ui..
[DEBUG ] 09:24:01 ui:115 UI init..
[DEBUG ] 09:24:01 configmanager:111 Getting config 'ui.conf'
[DEBUG ] 09:24:01 config:197 Setting 'default_ui' to gtk of
[WARNING ] 09:24:01 config:361 Unable to open config file
/home/diederik/.config/deluge/ui.conf: [Errno 2] No such file or
directory: '/home/diederik/.config/deluge/ui.conf'
[WARNING ] 09:24:01 config:419 Unable to open config file:
/home/diederik/.config/deluge/ui.conf because: [Errno 2] No such file
or directory: '/home/diederik/.config/deluge/ui.conf'
[DEBUG ] 09:24:01 config:423 Saving new config file
/home/diederik/.config/deluge/ui.conf.new
[DEBUG ] 09:24:01 config:436 Backing up old config file to
/home/diederik/.config/deluge/ui.conf~
[ERROR ] 09:24:01 config:439 Error backing up old config..
[DEBUG ] 09:24:01 config:444 Moving new config file
/home/diederik/.config/deluge/ui.conf.new to
/home/diederik/.config/deluge/ui.conf..
[INFO] 09:24:01 ui:132 Starting GtkUI..
** (deluge:19599): WARNING **: Trying to register gtype
'GMountMountFlags' as flags when in fact it is of type 'GEnum'
** (deluge:19599): WARNING **: Trying to register gtype
'GDriveStartFlags' as flags when in fact it is of type 'GEnum'
** (deluge:19599): WARNING **: Trying to register gtype
'GSocketMsgFlags' as flags when in fact it is of type 'GEnum'
[WARNING ] 09:24:01 gtkui:180 Unable to register a 'die' handler with
the GNOME session manager: No module named gnome.ui
[DEBUG ] 09:24:01 common:247 gconf not available, so will not
attempt to register magnet uri handler
[DEBUG ] 09:24:01 configmanager:111 Getting config 'gtkui.conf'
[DEBUG ] 09:24:01 config:197 Setting 'close_to_tray' to False of
[DEBUG ] 09:24:01 config:197 Setting 'ntf_sound_path' to
/home/diederik of
[DEBUG ] 09:24:01 config:197 Setting 'window_width' to 640 of
[DEBUG ] 09:24:01 config:197 Setting 'default_load_path' to None of
[DEBUG ] 09:24:01 config:197 Setting 'window_y_pos' to 0 of
[DEBUG ] 09:24:01 config:197 Setting 'ntf_email' to False of
[DEBUG ] 09:24:01 config:197 Setting 'tray_upload_speed_list' to
[5.0, 10.0, 30.0, 80.0, 300.0] of
[DEBUG ] 09:24:01 config:197 Setting 'show_statusbar' to True of
[DEBUG ] 09:24:01 config:197 Setting 'ntf_popup' to False of
[DEBUG ] 09:24:01 config:197 Setting 'ntf_pass' to of
[DEBUG ] 09:24:01 config:197 Setting 'tray_download_speed_list' to
[5.0, 10.0, 30.0, 80.0, 300.0] of
[DEBUG ] 09:24:01 config:197 Setting 'window_maximized' to False of
[DEBUG ] 09:24:01 config:197 Setting 'enable_system_tray' to True
of
[DEBUG ] 09:24:01 config:197 Setting 'show_sidebar' to True of
[DEBUG ] 09:24:01 config:197 Setting
'show_connection_manager_on_start' to True of
[DEBUG ] 09:24:01 config:197 Setting 'lock_tray' to False of
[DEBUG ] 09:24:01 config:197 Setting 'createtorrent.trackers' to []
of
[DEBUG ] 09:24:01 config:197 Setting 'ntf_sound' to False of
[DEBUG ] 09:24:01 config:197 Setting 'tray_password' to of
[DEBUG ] 09:24:01 config:197 Setting 'focus_add_dialog' to True of
[DEBUG ] 09:24:01 config:197 Setting 'ntf_server' to of
[DEBUG ] 09:24:01 config:197 Setting 'start_in_tray' to False of
[DEBUG ] 09:24:01 config:197 Setting 'ntf_tray_blink' to True of
[DEBUG ] 09:24:01 config:197 Setting 'check_new_releases' to False
of
[DEBUG ] 09:24:01 config:197 Setting 'autoadd_queued' to False of
[DEBUG ] 09:24:01 config:197 Setting 'pref_dialog_width' to None of
[DEBUG ] 09:24:01 config:197 Setting 'autoadd_enable' to False of
[DEBUG ] 09:24:01 config:197 Setting 'autoconnect_host_id' to None
of
[DEBUG ] 09:24:01 config:197 Setting 'classic_mode'
Bug#675498: akregator: akrekator crashes on quit
Wolfgang Walter wrote: > Would be very glad if this makes it as soon as possible into sid as akregator > is rather unusable now: +1 Apparently Akregator only marks feeds read (on disk) when closing Akregator (properly), which 'never' happens since I got bitten by this bug. Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676844: deluge-console: BadLoginError: Username does not exist
Package: deluge-console
Version: 1.3.5-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Installed deluged and then deluge-console on my headless server so I
could reconfigure deluged to allow remote connections. Then I started
deluge-console to do just that.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Start deluge-console
* What was the outcome of this action?
[ERROR ] 23:25:05 client:395 RPCError Message Received!
RPCRequest: daemon.login(, )
File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 259, in
dispatch
ret = component.get("AuthManager").authorize(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 87, in
authorize
raise BadLoginError("Username does not exist")
BadLoginError: Username does not exist
(various whitespace and other non-functional characters removed)
* What outcome did you expect instead?
A normally started deluge-console
Note that if you type help (for example) the normal deluge-console window is
shown and you can use the program, but that's not exactly obvious. I stumbled
upon it
by accident. Before that, I thought the program was unusable.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (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/bash
Versions of packages deluge-console depends on:
ii deluge-common 1.3.5-1
ii python 2.7.2-10
ii python2.6 2.6.7-4
ii python2.7 2.7.3~rc2-2.1
deluge-console recommends no packages.
deluge-console suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#798849: konsole: setting size in profile does not work any more
On Sunday 13 September 2015 16:45:54 M G Berberich wrote: > setting the default size in the profile settings no longer > works. konsole always starts with 80×31. This looks like a duplicate of 794055. Can you confirm or deny that? signature.asc Description: This is a digitally signed message part.
Bug#794055: Affects yakuake
affects 794055 yakuake thanks I believe this bug is also the reason that yakuake doesn't retain it's width setting. With me it always reverts back to 80% signature.asc Description: This is a digitally signed message part.
Bug#794055: Affects yakuake
affects 794055 - yakuake thanks On Monday 14 September 2015 12:41:58 Scott Kitterman wrote: > > I believe this bug is also the reason that yakuake doesn't retain it's > > width setting. With me it always reverts back to 80% > > I think this is unlikely since yakuake is KDE 4 and konsole is Kf5. Ok. Reverting the affects then. Will file separate issue on yakuake then. signature.asc Description: This is a digitally signed message part.
Bug#798982: yakuake: Doesn't retain changes in width/height between sessions
Package: yakuake Version: 2.9.9-1 Severity: normal When you change the width, height or both settings of the yakuake window and then log out and back in again, the width and height setting are back to the defaults (80% width, 50% height). I don't know whether there is a relationship between this bug and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794055 but I'm mentioning it just in case. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yakuake depends on: ii kde-runtime4:15.08.0-2 ii konsole4:15.08.0-1 ii libc6 2.19-20 ii libgcc11:5.2.1-17 ii libkdecore54:4.14.10-3 ii libkdeui5 4:4.14.10-3 ii libkio54:4.14.10-3 ii libknewstuff3-44:4.14.10-3 ii libknotifyconfig4 4:4.14.10-3 ii libkparts4 4:4.14.10-3 ii libnepomuk44:4.14.10-3 ii libnepomukutils4 4:4.14.10-3 ii libqt4-dbus4:4.8.7+dfsg-3 ii libqt4-network 4:4.8.7+dfsg-3 ii libqt4-svg 4:4.8.7+dfsg-3 ii libqt4-xml 4:4.8.7+dfsg-3 ii libqtcore4 4:4.8.7+dfsg-3 ii libqtgui4 4:4.8.7+dfsg-3 ii libsoprano42.9.4+dfsg-3+b1 ii libstdc++6 5.2.1-17 ii libx11-6 2:1.6.3-1 yakuake recommends no packages. yakuake suggests no packages. -- no debconf information
Bug#798986: yakuake: Should depend on konsole4-kpart instead of konsole
Package: yakuake Version: 2.9.9-1 Severity: minor This package depends on konsole while it actually should depend on konsole4-kpart. Since konsole depends on konsole4-kpart (now) on my architecture it is not a problem, but it would be more correct to depend on konsole4-kpart. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages yakuake depends on: ii kde-runtime4:15.08.0-2 ii konsole4:15.08.0-1 ii libc6 2.19-20 ii libgcc11:5.2.1-17 ii libkdecore54:4.14.10-3 ii libkdeui5 4:4.14.10-3 ii libkio54:4.14.10-3 ii libknewstuff3-44:4.14.10-3 ii libknotifyconfig4 4:4.14.10-3 ii libkparts4 4:4.14.10-3 ii libnepomuk44:4.14.10-3 ii libnepomukutils4 4:4.14.10-3 ii libqt4-dbus4:4.8.7+dfsg-3 ii libqt4-network 4:4.8.7+dfsg-3 ii libqt4-svg 4:4.8.7+dfsg-3 ii libqt4-xml 4:4.8.7+dfsg-3 ii libqtcore4 4:4.8.7+dfsg-3 ii libqtgui4 4:4.8.7+dfsg-3 ii libsoprano42.9.4+dfsg-3+b1 ii libstdc++6 5.2.1-17 ii libx11-6 2:1.6.3-1 yakuake recommends no packages. yakuake suggests no packages. -- no debconf information
Bug#796956: Note that this is a docked laptop using external monitor
On Wednesday 16 September 2015 12:44:02 Lisandro Damián Nicanor Pérez Meyer wrote: > > qt5.5 has an abi blocker for things that link against its private symbols, > > so Konsole outputthings that depend on qtbase-abi-5-4-2 will need to be > > recompiled against the new qt version. > > > > frameworkintegration is the one the I see that directly depends on that. > > In other words: you need to either recompile the necessary stuff yourself > or wait until Qt 5.5 arrives to unstable. Is it a possibility to get those packages compiled against Qt 5.5 in experimental? signature.asc Description: This is a digitally signed message part.
Bug#781219: Version 4.7.x is released
Now that 4.7.0 and even 4.7.1 are released, it looks to me that this bug can be closed. signature.asc Description: This is a digitally signed message part.
Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
Package: glx-diversions Version: 0.5.1 Severity: normal Earlier today I upgraded to version 0.6.0 of glx-diversions and glx-alternative-mesa and glx-alternative-nvidia and after a reboot the sddm-greeter crashed which made it impossible to start my KDE Plasma 5 desktop. After downgrading to version 0.5.1 of those packages the sddm-greeter did start and I'm now writing this bug report from Plasma 5. I have 2 crash report from sddm-greeter and will attach to this bug report later. If you need more info and/or want me to do tests, let me know. Regards, Diederik -- Package-specific info: Diversions: diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by glx-diversions diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1 by glx-diversions di
Bug#799948: Further bug updates
severity 799948 grave thanks I specified severity grave in reportbug, but apparently this wasn't retained, thus raising it back to grave. signature.asc Description: This is a digitally signed message part.
Bug#797979: Again
What does 'aptitude search ~ikwin' return? signature.asc Description: This is a digitally signed message part.
Bug#797979: Again
On Thursday 24 September 2015 23:35:50 Hynek Vychodil wrote: > $ aptitude search ~ikwin > i A kwin-common > i A kwin-data > i A kwin-style-breeze > i A kwin-wayland > i A kwin-x11 > i A libkwin4-effect-builtins1 > i A libkwineffects6 > i A libkwinglutils6 > i A libkwinxrenderutils6 > i A qml-module-org-kde-kwindowsystem I have that same list, with 1 addition: kwin-wayland-backend-x11 (I have kwin-wayland and kwin-x11 manually installed though) signature.asc Description: This is a digitally signed message part.
Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
On Friday 25 September 2015 01:12:58 Diederik de Haas wrote:
> It wasn't a problem to log into a console with Ctl+Alt+F1 and is how I
> collected various info from the boot process, see attachments.
> The last line from kern.log seems particular relevant.
My guess was correct.
With the crash ('grep sddm-greeter /var/log/syslog'):
Sep 25 00:11:42 bagend sddm-greeter[1213]: Reading from
"/usr/share/xsessions/plasma.desktop"
Sep 25 00:11:42 bagend sddm-greeter[1213]: Reading from
"/usr/share/xsessions/failsafe.desktop"
Sep 25 00:11:42 bagend sddm-greeter[1213]: Connected to the daemon.
Sep 25 00:11:44 bagend sddm-greeter[1213]: QObject::installEventFilter():
Cannot filter events for objects in a different thread.
Sep 25 00:11:46 bagend sddm-greeter[1213]: QObject::installEventFilter():
Cannot filter events for objects in a different thread.
Sep 25 00:11:48 bagend sddm-greeter[1213]:
file:///usr/share/sddm/themes/breeze/components/InfoPane.qml:52:22: Unable to
assign [undefined] to int
Sep 25 00:11:48 bagend sddm-greeter[1213]: QDBusConnection: name
'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.8'
Sep 25 00:11:48 bagend sddm-greeter[1213]: Message received from daemon:
Capabilities
Sep 25 00:11:48 bagend sddm-greeter[1213]: Message received from daemon:
HostName
Sep 25 00:11:48 bagend sddm-greeter[1213]: Failed to create OpenGL context for
format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile 0)
Normal boot (after downgrading glx-diversions):
Sep 25 00:46:43 bagend sddm-greeter[1282]: Reading from
"/usr/share/xsessions/plasma.desktop"
Sep 25 00:46:43 bagend sddm-greeter[1282]: Reading from
"/usr/share/xsessions/failsafe.desktop"
Sep 25 00:46:44 bagend sddm-greeter[1282]: Connected to the daemon.
Sep 25 00:46:45 bagend sddm-greeter[1282]: QObject::installEventFilter():
Cannot filter events for objects in a different thread.
Sep 25 00:46:47 bagend sddm-greeter[1282]: QObject::installEventFilter():
Cannot filter events for objects in a different thread.
Sep 25 00:46:49 bagend sddm-greeter[1282]:
file:///usr/share/sddm/themes/breeze/components/InfoPane.qml:52:22: Unable to
assign [undefined] to int
Sep 25 00:46:49 bagend sddm-greeter[1282]: QDBusConnection: name
'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.8'
Sep 25 00:46:49 bagend sddm-greeter[1282]: Message received from daemon:
Capabilities
Sep 25 00:46:49 bagend sddm-greeter[1282]: Message received from daemon:
HostName
Sep 25 00:46:52 bagend sddm-greeter[1282]: Reading from
"/usr/share/xsessions/plasma.desktop"
Sep 25 00:46:53 bagend sddm-greeter[1282]: Message received from daemon:
LoginSucceeded
HTH
signature.asc
Description: This is a digitally signed message part.
Bug#799948: glx-diversions: gdm also crashes
On Friday 25 September 2015 12:05:04 you wrote: > nvidia-* update from 340.93-1 to 340.93-2 occured at the same time on my > machine, but reverting back to 340.93-1 did not solve de problem. To solve the problem I had to revert back to glx-diversions 0.5.1. But in order to do so, it _seemed_ that I also had to downgrade the nvidia- driver package(s). I may have been wrong about that because I was working in a (to me) limited console, whereas I normally do it in Konsole where I can see much more and can (easily) scroll back to see all the output. signature.asc Description: This is a digitally signed message part.
Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
On Friday 25 September 2015 01:12:58 Diederik de Haas wrote: > > Does any other display manager work with 0.6.0? (kdm seems to work for > > me with the changes from 0.6.0). > > I'll now (also) install kdm I installed kdm and selected that as the default ... and it didn't crash! What was funny though is that after the kdm login screen and providing my credentials, it seemed to switch over to sddm. I'll now purge sddm and see what happens ... signature.asc Description: This is a digitally signed message part.
Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
On Friday 25 September 2015 12:44:17 Diederik de Haas wrote: > What was funny though is that after the kdm login screen and providing my > credentials, it seemed to switch over to sddm. Apparently not sddm, as that was now purged, but likely something from breeze. > I'll now purge sddm and see what happens ... That worked too. So it works with kdm, but not with sddm. And judging by the reports from Ara and Luca it also doesn't work with gdm. Could it be that sddm and gdm use/invoke new(er) technologies that break things? As I said earlier kdm is dead upstream, so it's codebase may be old. signature.asc Description: This is a digitally signed message part.
Bug#800051: sddm: Starting with sddm as dm ended in a black screen
On Saturday 26 September 2015 03:16:08 Alf Gaida wrote: > Sep 26 02:57:44 razorbox sddm-greeter[2582]: Failed to create OpenGL context > for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize > 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, > alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, > swapInterval 1, profile 0) Sep 26 02:57:44 razorbox sddm-helper[2574]: > [PAM] Ended. Do you have glx-diversions version 0.6.0 installed? If so look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948 signature.asc Description: This is a digitally signed message part.
Bug#795471: kdegames: no possibility to launch kdegames
On Friday 14 August 2015 12:27:37 Pascal Raton wrote: > *** Reporter, please consider answering these questions, where appropriate > *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** Well, that was an informative bug report... It's likely caused by bug #794419 and adding '/usr/games/' back onto your $PATH will probably fix it. signature.asc Description: This is a digitally signed message part.
Bug#794087: More info on this bug
reassign 794087 src:qtbase-opensource-src thanks First of all, I can confirm this bug. The odd thing is though that it does work in (for example) kate and vim in konsole, but not in kcalc. When searching the web for this issue I found various, but conflicting, information. I'll describe them all, so that someone who can figure out what it is exactly has all the information at his/her disposal. This bug is also reported on the KDE bugtracker: https://bugs.kde.org/show_bug.cgi?id=344638 where it is marked as 'RESOLVED UPSTREAM'. On comment 8 of that bug it is marked as a regression in Qt5 with the following link: https://codereview.qt-project.org/#/c/95219/ But on that Code Review has the status 'Review in Progress'. It also references 2 Qt bugs: http://bugreports.qt.io/browse/QTBUG-33093 and http://bugreports.qt.io/browse/QTBUG-44577 The latter bug looks the most applicable, but it was closed due to inactivity and it seems to (also) talk about text widget, where I'm not seeing the issue. If anyone needs more info, let me know. signature.asc Description: This is a digitally signed message part.
Bug#795471: Fwd: Re: Bug#795471: kdegames: no possibility to launch kdegames
Forwarding it to the bug report so others can see/use the info as well. -- Forwarded Message -- Subject: Fwd: Re: Bug#795471: kdegames: no possibility to launch kdegames Date: Friday 14 August 2015, 19:47:41 From: pc To: didi.deb...@cknow.org >> Diederik de Haas But with "export PATH=$PATH:/usr/games" in the bash file "/~/.config/plasma-workspace/env//path.sh", it's ok... Thanks for your help Message transféré Sujet : Re: Bug#795471: kdegames: no possibility to launch kdegames Date : Fri, 14 Aug 2015 19:41:24 +0200 De : pc Pour : Diederik de Haas Thanks for your help. In the file "/etc/profile", there is : Konsole output /# /etc/profile: system-wide .profile file for the Bourne shell (sh(1)) // //# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...). // //if [ "`id -u`" -eq 0 ]; then // // PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" // //else // // PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games" // //fi // //export PATH /Normaly path should be ok for normal user, but command "echo $PATH" is "/bin:/usr/bin:/usr/local/bin" If I do command "export PATH=$PATH:/usr/games", it's ok in the console, but not with kde5 menu... Like this link : https://en.opensuse.org/SDB:KDE_Plasma_5#System_tray_icons_for_applications_such_as_Skype_no_longer_show I write a bash script with "export PATH=usr/games:$PATH" inside but always same problem. I'msorrybutIdon'tknowwhatto do... Pascal Raton signature.asc Description: This is a digitally signed message part.
Bug#795471: Fwd: Re: Bug#795471: kdegames: no possibility to launch kdegames
Please reply to the bug report and not me personally. On Saturday 15 August 2015 11:01:32 pc wrote: > I'm very disapointed but with "export PATH=$PATH:/usr/games" in the bash > file "/~/.config/plasma-workspace/env/path.sh, this bashloopcontinuously > with one processor core used to 100%. signature.asc Description: This is a digitally signed message part.
Bug#795608: krdc: Package uninstallable?
On Saturday 15 August 2015 20:03:35 Christian Perrier wrote: > (reporting as "important" because I'm unsure about the ongoing > transition to Plasma 5) That is likely the cause. I wouldn't be surprised if it would work if you also had the testing repos in your /etc/apt/sources.list signature.asc Description: This is a digitally signed message part.
Bug#795471: Right to choose
On Saturday 15 August 2015 19:35:59 pr1vacy.matt...@cryptolab.net wrote: > I understand SDDM is 'the future' to some people(mostly the systemd > fanbois) but since when do we not have the right to choose our dm? No one has denied you that choice. All that was said is that it is not a proper solution to the reported problem. Given that testing is meant as preparation or test-bed for the next stable release, there's enough time to find a proper solution. I have no idea what your systemd rant has anything to do with this bug though. And no, I don't want you to explain. I don't care. But most of all, this bug report is _not_ the right place for a systemd discussion. signature.asc Description: This is a digitally signed message part.
Bug#795608: krdc: Package uninstallable?
On Sunday 16 August 2015 09:16:54 Christian PERRIER wrote: > > That is likely the cause. I wouldn't be surprised if it would work if you > > also had the testing repos in your /etc/apt/sources.list > > Sadly, no. It may still be possible, but then you would probably have to downgrade a whole bunch of packages to their testing versions, including libstdc++6 which will bring lots of packages to their pre-gcc-5-transition versions. I've guided some ppl to do just that, but it was a lengthy (>1 hour) exercise with direct communication on IRC (#debian-kde). Not sure it would be doable or the appropriate place on a bug report. And you may not want to do that for a single package. signature.asc Description: This is a digitally signed message part.
Bug#796098: libkf5guiaddons5: KDE is stuck in login splash screen
On Wednesday 19 August 2015 15:05:12 Peter Marschall wrote: > Downgrading those packages to stable is not possible, asd these packages > were introduced after the last release only. You could downgrade those packages to a previous version by using snapshot.debian.org signature.asc Description: This is a digitally signed message part.
Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue
On maandag 14 november 2016 15:12:14 CET Vincent Lefevre wrote: > aptitude often ignores Recommends. So, you should not rely on it. That's an incorrect statement. Aptitude, and I think apt too, doesn't automatically install _new_ recommended packages for an already installed package. It does report "The following recommended packages will not be installed" (or sth along those lines). But that's far from ignoring it. signature.asc Description: This is a digitally signed message part.
Bug#840844: improving the UX with the default KDE installation
Hi Maxy! On vrijdag 31 maart 2017 18:45:36 CEST Maximiliano Curia wrote: > > ping https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840844 ? > > (it's about adding kdeconnect to kde-standard) > > I thought I had replied to that/this request. I also use kdeconnect, but > it's only useful if the user has smartphone running Android, that it's > also running kdeconnect. So, we might add a Suggests, but not a dependency. My main goal for that bug was discoverability of kdeconnect and a Suggest would accomplish that. I use it all the time and for *me* it's the main gem in the KDE suit, so I wouldn't mind a Recommends either ;-P signature.asc Description: This is a digitally signed message part.
Bug#822755: Upstream known and fixed bug with qt 5.6
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=360105 Control: tags -1 upstream fixed-upstream signature.asc Description: This is a digitally signed message part.
Bug#824695: phonon4qt5-backend-vlc: List of mime types do not match the ones in the vlc desktop file
On Wednesday 18 May 2016 21:28:51 Petter Reinholdtsen wrote: > Package: phonon4qt5-backend-vlc > Version: 0.8.2-1 > > When comparing the list of MIME types in > phonon-backend-vlc-0.8.2/MimeTypes.cmake with the file > share/vlc.desktop.mimetypes in the vlc upstream git, the list of MIME > types do mot match each other. phonon-backend-vlc 0.9.0-1 just got accepted to unstable and the git repo has the latest sources which is probably more useful to check (again). https://anonscm.debian.org/cgit/pkg-kde/kde-std/phonon-backend-vlc.git/ signature.asc Description: This is a digitally signed message part.
Bug#824766: armory: New home for armory and new upstream release
Package: armory Version: 0.92.3-1+b2 Severity: normal As can be read in the links from this issue https://github.com/etotheipi/BitcoinArmory/issues/325 Armory Technologies has stopped working on armory, at least for the time being. As can be read in the linked threads, there is now a fork which seemed to be (somewhat) official, namely https://github.com/goatpig/BitcoinArmory and there have been several releases there, the latest being 0.94.1. Maybe it's a good idea to switch the Debian package to the fork? Cheers, Diederik -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages armory depends on: ii bittornado 0.3.18-10.2 ii libc6 2.22-9 ii libcrypto++6 5.6.3-6 ii libgcc11:6.1.1-3 ii libleveldb1v5 1.18-5 ii libstdc++6 6.1.1-3 ii python-psutil 4.1.0-1 ii python-qt4 4.11.4+dfsg-1+b3 ii python-qt4reactor 1.0-1 ii python-twisted 16.1.1-1 ii python2.7 2.7.11-9 pn python:any ii xdg-utils 1.1.1-1 Versions of packages armory recommends: ii bitcoind 0.11.2-1 armory suggests no packages. -- no debconf information
Bug#825243: qtchooser tries to overwrite /usr/share/qtchooser/qt5-x86_64-linux-gnu.conf also in libqt5core5a
Control: -1 severity serious Control: -1 merge 825111 On Wednesday 25 May 2016 02:31:38 Vincent Lefevre wrote: > trying to overwrite '/usr/share/qtchooser/qt5-x86_64-linux-gnu.conf', which > is also in package libqt5core5a:amd64 5.6.0+dfsg-2+b1 Sounds like the same bug as #825111 signature.asc Description: This is a digitally signed message part.
Bug#825243: qtchooser tries to overwrite /usr/share/qtchooser/qt5-x86_64-linux-gnu.conf also in libqt5core5a
Control: severity -1 serious Control: merge -1 825111 signature.asc Description: This is a digitally signed message part.
Bug#825243: qtchooser tries to overwrite /usr/share/qtchooser/qt5-x86_64-linux-gnu.conf also in libqt5core5a
Control: reassign -1 src:qtbase-opensource-src 5.6.0-1 Control: forcemerge -1 825111 Control: affects -1 qtchooser On Wednesday 25 May 2016 09:47:55 Vincent Lefevre wrote: > On 2016-05-25 03:46:39 +0200, Diederik de Haas wrote: > > On Wednesday 25 May 2016 02:31:38 Vincent Lefevre wrote: > > > trying to overwrite '/usr/share/qtchooser/qt5-x86_64-linux-gnu.conf', > > > which > > > is also in package libqt5core5a:amd64 5.6.0+dfsg-2+b1 > > > > Sounds like the same bug as #825111 > > Yes. It was not signaled by apt-listbugs because #825111 is assigned > to src:qtbase-opensource-src instead of the binary package qtchooser. > IMHO, for this reason, it should be reassigned to qtchooser, which > is the package affected by the bug. qtchooser is affected by this bug, but libqt5core5a/src:qtbase-opensource-src is doing the wrong thing, therefor the bug is in src:qtbase-opensource-src See https://www.debian.org/Bugs/server-control#affects for details. signature.asc Description: This is a digitally signed message part.
Bug#807902: konsole: segfault on exit
On Monday 14 December 2015 11:51:01 Dominik George wrote: > Package: konsole > Version: 4:15.08.3-1 > Severity: normal > > Recently, Konsole started crashing when closing the last tab and exiting: With me it's not recently but has been happening for a while already. Here's a stacktrace I just got with a Konsole crash: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f8ddf029657 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7f8ddf02aa2a in __GI_abort () at abort.c:89 #8 0x7f8ddf067bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f8ddf1605f8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f8ddf06d00e in malloc_printerr (action=1, str=0x7f8ddf1606c0 "double free or corruption (out)", ptr=) at malloc.c:4965 #10 0x7f8ddf06d7eb in _int_free (av=, p=, have_lock=0) at malloc.c:3834 #11 0x7f8ddbc80aec in QMetaCallEvent::~QMetaCallEvent() (this=0x7f8dc4005780, __in_chrg=) at kernel/qobject.cpp:468 #12 0x7f8ddbc80b39 in QMetaCallEvent::~QMetaCallEvent() (this=0x7f8dc4005780, __in_chrg=) at kernel/qobject.cpp:476 #13 0x7f8ddbc57727 in QCoreApplication::removePostedEvents(QObject*, int) (receiver=0x1b9ed10, eventType=eventType@entry=0) at kernel/qcoreapplication.cpp:1670 #14 0x7f8ddbc82e42 in QObjectPrivate::~QObjectPrivate() (this=0x1b9f070, __in_chrg=) at kernel/qobject.cpp:235 #15 0x7f8ddbc82f69 in QObjectPrivate::~QObjectPrivate() (this=0x1b9f070, __in_chrg=) at kernel/qobject.cpp:246 #16 0x7f8ddbc8b558 in QObject::~QObject() (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:54 #17 0x7f8ddbc8b558 in QObject::~QObject() (this=0x1b9ed18, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:101 #18 0x7f8ddbc8b558 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:883 #19 0x7f8dcb556619 in QXcbConnection::~QXcbConnection() (this=0x1b9ed10, __in_chrg=) at qxcbconnection.cpp:635 #20 0x7f8dcb5580b6 in QXcbIntegration::~QXcbIntegration() (end=..., begin=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:317 #21 0x7f8dcb5580b6 in QXcbIntegration::~QXcbIntegration() (c=...) at ../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:325 #22 0x7f8dcb5580b6 in QXcbIntegration::~QXcbIntegration() (this=0x1bb8d30, __in_chrg=) at qxcbintegration.cpp:190 #23 0x7f8dcb5581c9 in QXcbIntegration::~QXcbIntegration() (this=0x1bb8d30, __in_chrg=) at qxcbintegration.cpp:192 #24 0x7f8ddbf8d9a3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() (this=0x1bb9be0, __in_chrg=) at kernel/qguiapplication.cpp:1390 #25 0x7f8ddc544029 in QApplicationPrivate::~QApplicationPrivate() (this=0x1bb9be0, __in_chrg=) at kernel/qapplication.cpp:192 #26 0x7f8ddbc8b558 in QObject::~QObject() (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:54 #27 0x7f8ddbc8b558 in QObject::~QObject() (this=0x7ffe9f3752a8, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:101 #28 0x7f8ddbc8b558 in QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:883 #29 0x7f8ddc545e19 in QApplication::~QApplication() (this=0x7ffe9f3752a0, __in_chrg=) at kernel/qapplication.cpp:816 #30 0x7f8ddf3bb375 in kdemain(int, char**) (argc=1, argv=0x7ffe9f3753e8) at ../../src/main.cpp:110 #31 0x7f8ddf016870 in __libc_start_main (main=0x400710 , argc=1, argv=0x7ffe9f3753e8, init=, fini=, rtld_fini=, stack_end=0x7ffe9f3753d8) at libc-start.c:291 #32 0x00400749 in _start () at ../sysdeps/x86_64/start.S:118 signature.asc Description: This is a digitally signed message part.
Bug#808001: cantor: add support for julia (julialang.org
forwarded 808001 https://bugs.kde.org/show_bug.cgi?id=356759 thanks On Tuesday 15 December 2015 18:21:07 Hörmetjan Yiltiz wrote: > forwarded 808001 https://bugs.kde.org/show_bug.cgi?id=356759 You forgot to sent it to 'cont...@bugs.debian.org' and you need to close the commands with 'thanks' (there are also others). signature.asc Description: This is a digitally signed message part.
Bug#808094: Konsole segmentation fault after closing it
Looks like a duplicate of #807902 signature.asc Description: This is a digitally signed message part.
Bug#807902: konsole: segfault on exit
Got another stacktrace: Application: konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f8f6a6a11b3 in QString::~QString() (_q_value=@0x7f8f56584560: ) at ../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:90 #7 0x7f8f6a6a11b3 in QString::~QString() (this=0x7f8f56584560) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:116 #8 0x7f8f6a6a11b3 in QString::~QString() (this=0x7f8f56584560) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:60 #9 0x7f8f6a6a11b3 in QString::~QString() (this=0xf4aa08, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qstring.h:1053 #10 0x7f8f6a6975dd in QDBusConnectionPrivate::~QDBusConnectionPrivate() (this=0xf4a9f0, __in_chrg=) at qdbusintegrator.cpp:1034 #11 0x7f8f6a697c79 in QDBusConnectionPrivate::~QDBusConnectionPrivate() (this=0xf4a9f0, __in_chrg=) at qdbusintegrator.cpp:1061 #12 0x7f8f6a68c2ed in QDBusConnectionManager::~QDBusConnectionManager() (this=0x7f8f6a6f4d00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>, __in_chrg=) at qdbusconnection.cpp:86 #13 0x7f8f6a68c399 in (anonymous namespace)::Q_QGS__q_manager::Holder::~Holder() (this=, __in_chrg=) at qdbusconnection.cpp:59 #14 0x7f8f69fd7f52 in __run_exit_handlers (status=0, listp=0x7f8f6a340698 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #15 0x7f8f69fd7fa5 in __GI_exit (status=) at exit.c:104 #16 0x7f8f69fc2877 in __libc_start_main (main=0x400710 , argc=1, argv=0x7ffd4c1a0aa8, init=, fini=, rtld_fini=, stack_end=0x7ffd4c1a0a98) at libc-start.c:325 #17 0x00400749 in _start () at ../sysdeps/x86_64/start.S:118 HTH signature.asc Description: This is a digitally signed message part.
