Bug#1005936: Problem entering unicode characters
Package: mate-terminal Version: 1.26.0 When I try to enter unicode characters via the documented way( hold , enter 'u', enter hex offset, eg 2103 for degrees Celsius, then release ), this is working perfectly in mate-terminal. Except when the unicode hex offset contains hex character 'f' (e.g. U+1F660 (or most other smil, because that triggers the 'Find' tool in mate-terminal. I suggest to change the trigger key for 'Find' from f to something else, make it configurable, or make it possible to switch that off.
Bug#967896: Failed to load firmware chunk for iwlwifi Intel(R) Dual Band Wireless AC 9560 on debian-installer
On Sun, 16 Jan 2022 15:46:47 +0100 Holger Wansing wrote: > Hi, > > Pier Paolo Franco wrote (Sun, 16 Jan 2022 14:48:02 +0100): > > Dear all, > > shortly after this bug commit, I successfully managed to install Debian SID > > on this machine with netinst image. IWLWIFI currently working and happily > > upgraded to Linux sid 5.15.0-2-amd64 #1 SMP Debian 5.15.5-2 (2021-12-18) > > x86_64 GNU/Linux with bookworm/sid without any tweaks in grub/modprobe > > Ok, great. > This is conform with the fact, that the detection of needed firmware and > the installation of it has been massively improved for Bullseye. > > I'm closing this bugreport then. > > Thanks for reporting back > > Holger > > > > -- > Holger Wansing > PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 > > Hi, I am not that skilled in troubleshooting Linux/debian, but auto detection of AC9560 is still not working(correctly). I tried, sid, testing, bullseye and buster DVD installation iso's containing non-free firmware and they will all ask for iwlwifi-9000-pu-jf-b0-30, 31, 32, 33, 34, 35, 36, 37, 38 According to the Intel website "34" should be the correct firmware for AC9560 and should be supported from kernel 4,4 and up.
Bug#976530: dolphin-emu: FTBFS: tests failed
Hi, The reason why one of the unit tests failed is because this unit test was triggering undefined behavior when generating its test values. In other words, there was no bug in the actual program, just in the unit test. This bug was fixed upstream in https://github.com/dolphin-emu/dolphin/commit/8d21fa56a1133529273d57df06888e42bb63fde7 (though do note that this commit depends on an earlier commit from the same pull request). For what it's worth, in upstream we've only encountered this issue on arm64, not amd64. But since it is undefined behavior, I'm not too surprised that this issue doesn't act the same way in your build environment as in ours. I'm not sure how you want to proceed, but I hope this information was useful. JosJuice, dolphin-emu upstream maintainer
Bug#977608: mpd hangs when curl dies
Package: mpd
Version: 0.21.5-3
Severity: important
Dear Maintainer,
mpd plays internet streams via curl. If curl quits unexpectedly, this can hang
mpd. This issue has been resolved in the bugfix release v0.21.23.
-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename: buster
Architecture: armv7l
Kernel: Linux 5.4.79-v7+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mpd depends on:
ii adduser 3.118
ii init-system-helpers 1.56+nmu1
ii libadplug-2.2.1-0v5 2.2.1+dfsg3-1
ii libao41.2.2+20180113-1
ii libasound21.1.8-1+rpt1
ii libaudiofile1 0.3.6-5
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libavcodec58 7:4.1.6-1~deb10u1+rpt1
ii libavformat58 7:4.1.6-1~deb10u1+rpt1
ii libavutil56 7:4.1.6-1~deb10u1+rpt1
ii libbz2-1.01.0.6-9.2~deb10u1
ii libc6 2.28-10+rpi1
ii libcdio-cdda2 10.2+0.94+2-4
ii libcdio-paranoia2 10.2+0.94+2-4
ii libcdio18 2.0.0-2
ii libcurl3-gnutls 7.64.0-4+deb10u1
ii libdbus-1-3 1.12.20-0+deb10u1
ii libexpat1 2.2.6-2+deb10u1
ii libfaad2 2.8.8-3
ii libflac8 1.3.2-3
ii libfluidsynth11.1.11-1
ii libgcc1 1:8.3.0-6+rpi1
ii libgcrypt20 1.8.4-5
ii libgme0 0.6.2-1
ii libicu63 63.1-6+deb10u1
ii libid3tag00.15.1b-14
ii libiso9660-11 2.0.0-2
ii libixml10 1:1.8.4-2
ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2
ii libjs-sphinxdoc 1.8.4-1
ii libmad0 0.15.1b-10
ii libmikmod33.3.11.1-4
ii libmms0 0.6.4-3
ii libmodplug1 1:0.8.9.0-2
ii libmp3lame0 3.100-2+b1
ii libmpcdec62:0.1~r495-1+b1
ii libmpdclient2 2.16-1
ii libmpg123-0 1.25.10-2
ii libnfs12 3.0.0-2
ii libogg0 1.3.2-1+b2
ii libopenal11:1.19.1-1
ii libopus0 1.3-1
ii libpcre3 2:8.39-12
ii libpulse0 12.2-4+deb10u1+rpi2
ii libsamplerate00.1.9-2
ii libshout3 2.4.1-2
ii libsidplayfp4 1.8.8-1
ii libsmbclient 2:4.9.5+dfsg-5+deb10u1+rpi1
ii libsndfile1 1.0.28-6
ii libsoxr0 0.1.2-3
ii libsqlite3-0 3.27.2-3+deb10u1
ii libstdc++68.3.0-6+rpi1
ii libsystemd0 241-7~deb10u5+rpi1
ii libupnp13 1:1.8.4-2
ii libvorbis0a 1.3.6-2
ii libvorbisenc2 1.3.6-2
ii libwavpack1 5.1.0-6
ii libwildmidi2 0.4.3-1
ii libyajl2 2.1.0-3
ii libzzip-0-13 0.13.62-3.2
ii lsb-base 10.2019051400+rpi1
ii zlib1g1:1.2.11.dfsg-1
mpd recommends no packages.
Versions of packages mpd suggests:
ii avahi-daemon 0.7-4+b1
pn icecast2
ii mpc [mpd-client] 0.31-1
pn pulseaudio
-- Configuration Files:
/etc/mpd.conf changed:
music_directory "/var/lib/mpd/music"
playlist_directory "/var/lib/mpd/playlists"
db_file "/var/lib/mpd/tag_cache"
log_file"/var/log/mpd/mpd.log"
pid_file"/run/mpd/pid"
state_file "/var/lib/mpd/state"
sticker_file "/var/lib/mpd/sticker.sql"
user"mpd"
bind_to_address "0.0.0.0"
input {
plugin "curl"
}
input {
enabled"no"
plugin "qobuz"
}
input {
enabled "no"
plugin "tidal"
}
decoder {
plugin "hybrid_dsd"
enabled "no"
}
audio_output {
type"alsa"
name"JustBoom"
device "hw:0,0"# optional
mixer_type "software" # optional
mixer_device"digital" # optional
}
filesystem_charset
Bug#966336: libjpeg-turbo8-dev has no installation candidate
Package: libjpeg-turbo8-dev Severity: normal Tags: newcomer Dear Maintainer, Attempting to install libjpeg-turbo8-dev gives an error about having no installation candidate. Installing libjpeg62-turbo-dev is a viable workaround -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic'), (100, 'bionic-backports') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-18362-Microsoft Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages libjpeg-turbo8-dev depends on: ii libc6-dev [libc-dev] 2.27-3ubuntu1 pn libjpeg-turbo8 libjpeg-turbo8-dev recommends no packages. libjpeg-turbo8-dev suggests no packages.
Bug#958419: swi-prolog 8.1.29 in Debian
Hi Lev, Yes indeed, eye is using a saved state to have it started 10 times faster than normal: $ time swipl -x /opt/eye/lib/eye.pvm -- --version eye --version EYE v20.0423.1748 josd SWI-Prolog version 8.1.29 starting 31 [msec cputime] 37 [msec walltime] real 0m0.041s user 0m0.037s sys 0m0.004s $ time swipl -f /opt/eye/src/eye.pl -g main -- --version eye --version EYE v20.0423.1748 josd SWI-Prolog version 8.1.29 starting 344 [msec cputime] 393 [msec walltime] real 0m0.401s user 0m0.343s sys 0m0.015s and this is quite crucial as eye is typically used as a short running process which is getting data/rules/query from the web, returning answers/proofs for the query and then closing the process as the internal state (e.g. the deductive closure of the forward reasoning run) is of no use to the next run. Kind regards, Jos -- https://josd.github.io/ <http://josd.github.io/> On Tue, Apr 28, 2020 at 1:30 PM Lev Lamberov wrote: > Вт 28 апр 2020 @ 13:11 Jan Wielemaker : > > > Hi Lev, > > > > I most wanted to get Jos in the loop as the developer of eye. Packagers > > working together with developers/maintainers saves a lot of work :) > > Awww... so, CCing Jos De Roo. > > Jos, could you be so kind to take a look at the #958561 Debian bug > report concerning swi-prolog and eye. You can find it there: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958561 > > > On 4/28/20 12:49 PM, Lev Lamberov wrote: > >> Hi Jan, > >> > >> Вт 28 апр 2020 @ 11:22 Jan Wielemaker : > >> > >>> Hi Lev, Jos, > >>> > >>> For Jos, the problem is that eye installs as a SWI-Prolog saved state, > >>> which is highly version dependent and this is difficult to deal with > >>> given the Debian dependency and upgrade policy (Lev, hope this is the > >>> right summary, please correct if not). > >>> > >>> I has a little look at eye and I wonder why we need the state. eye.pl > >>> isn't that big and loads in about 0.12 sec on my machine. Without a > >>> state, eye seems to run easily using the simple script > >>> > >>> swipl -g main /path/to/eye.pl "$@" > >>> > >>> Or by installing eye.pl as the actual executable and start is using > >>> > >>> #!/bin/env swipl > >>> > >>> and use somewhere in the file > >>> > >>> :- initialization(main,main). > >>> > >>> Would it make sense to go this route? If not, why not? Is the > >>> somewhat longer startup time an issue? > >>> > >>> Thanks --- Jan > >> > >> I'm sending your message to the bug report and to Jonas Smedegaard. > >> Please, send your further replies to 958...@bugs.debian.org > >> > >> Cheers! > >> Lev >
Bug#953420: libstdc++-arm-none-eabi-newlib does not work with gcc-arm-none-eabi 15:8-2019-q3-1 in testing and unstable
Package: libstdc++-arm-none-eabi-newlib Version: 15:7-2018-q2-5+12 The upgrade of gcc-arm-none-eabi to 15:8-2019-q3-1 in testing and unstable breaks C++ builds with libstdc++-arm-none-eabi-newlib, as it is still based on GCC 7. For example, after installing libstdc++-arm-none-eabi-newlib: $ arm-none-eabi-g++ -x c++ -E -Wp,-v - << EOF $ #include $ EOF ignoring nonexistent directory "/usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/include/c++/8.3.1" ignoring nonexistent directory "/usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/include/c++/8.3.1/arm-none-eabi" ignoring nonexistent directory "/usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/include/c++/8.3.1/backward" ignoring nonexistent directory "/usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/sys-include" #include "..." search starts here: #include <...> search starts here: /usr/lib/gcc/arm-none-eabi/8.3.1/include /usr/lib/gcc/arm-none-eabi/8.3.1/include-fixed /usr/lib/gcc/arm-none-eabi/8.3.1/../../../arm-none-eabi/include End of search list. # 1 "" # 1 "" # 1 "" # 1 "" :1:10: fatal error: limits: No such file or directory compilation terminated. GCC expects the /usr/lib/arm-none-eabi/include/c++/8.3.1 directory to exist, but it doesn't. Instead, only /usr/lib/arm-none-eabi/include/c++/7.3.1 is available. Best regards, Jos
Bug#949444: depmod ERROR
Package: kmod Version: 27-1 Severity: important reproduced using kmod/27-1: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.5.0-7.slh.1-aptosid-amd64/modules.builtin.bin'
Bug#876759: daisy-player: Broken autopkgtest
Yes, sorry. In version 11.6.1.1. On Thu, Sep 06, 2018 at 07:27:07PM +0200, Samuel Thibault wrote: > Jos Lemmens, le jeu. 06 sept. 2018 19:22:59 +0200, a ecrit: > > No more timeouts in > > > > bash -ec 'LC_ALL=C daisy-player -h' > >(tee -a /tmp/command1-stdout) > > Do you mean: in the latest version 11.6.1.1? > > Samuel -- Sent from Debian GNU/Linux 9 --- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl
Bug#876759: daisy-player: Broken autopkgtest
Hello,
No more timeouts in
bash -ec 'LC_ALL=C daisy-player -h' > >(tee -a /tmp/command1-stdout)
Regards,
Jos.
On Sun, Sep 02, 2018 at 09:14:37PM +0200, Samuel Thibault wrote:
> Hello,
>
> Jos Lemmens, le dim. 02 sept. 2018 21:07:58 +0200, a ecrit:
> > I can't find the reason why it times out after so long.
>
> Did you try
>
> bash -ec 'LC_ALL=C daisy-player -h' > >(tee -a /tmp/command1-stdout)
>
> as I mentioned?
>
> Samuel
--
Sent from Debian GNU/Linux 9
---
Jos Lemmens
The Netherlands
E-mail: j...@jlemmens.nl
Homepage: www.jlemmens.nl
Bug#876759: daisy-player: Broken autopkgtest
Hello, This bug has something to do with fork(), sigaction() and SIGCHLD. After quiting daisy-player now, the terminal hangs. But I can't find the solution yet, sorry. Regards, Jos. On Sun, Sep 02, 2018 at 09:14:37PM +0200, Samuel Thibault wrote: > Hello, > > Jos Lemmens, le dim. 02 sept. 2018 21:07:58 +0200, a ecrit: > > I can't find the reason why it times out after so long. > > Did you try > > bash -ec 'LC_ALL=C daisy-player -h' > >(tee -a /tmp/command1-stdout) > > as I mentioned? > > Samuel -- Sent from Debian GNU/Linux 9 --- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl
Bug#876759: daisy-player: Broken autopkgtest
Hello, I can't find the reason why it times out after so long. What does the latest daisy-player 11.6.1? Regards, Jos. On Mon, Sep 25, 2017 at 11:32:04AM -0400, Jeremy Bicha wrote: > Source: daisy-player > Version: 10.6.4.2-1 > > daisy-player's autopkgtest does not work: > > https://ci.debian.net/packages/d/daisy-player/unstable/amd64/ > http://autopkgtest.ubuntu.com/packages/d/daisy-player/artful/amd64 > > It times out after over 2 hours so it's a bit of a drain on the > autopkgtest infrastructure. > > Thanks, > Jeremy Bicha -- Sent from Debian GNU/Linux 9 --- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl
Bug#876759: daisy-player: Broken autopkgtest
Hello Jeremy, I do know nothing about autopkgtest. It is completely new to me. I will read the manual. Can you give me a hint? Regards, Jos. On Mon, Sep 25, 2017 at 11:32:04AM -0400, Jeremy Bicha wrote: > Source: daisy-player > Version: 10.6.4.2-1 > > daisy-player's autopkgtest does not work: > > https://ci.debian.net/packages/d/daisy-player/unstable/amd64/ > http://autopkgtest.ubuntu.com/packages/d/daisy-player/artful/amd64 > > It times out after over 2 hours so it's a bit of a drain on the > autopkgtest infrastructure. > > Thanks, > Jeremy Bicha -- Sent from Debian GNU/Linux 9 --- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl
Bug#882247:
Package: firefox Version: 58.0~b4-1 Severity: grave After upgrading firefox to version 58.0~b4-1 I get the same issue.
Bug#861228: initramfs will attempt to resume from /dev/zram1
Package: initramfs-tools Version: 0.130 Severity: normal Dear Maintainer, My dual core system uses two zram devices /dev/zram0 and /dev/zram1. Although my swap partitions are ephemeral zram devices I get update-initramfs: Generating /boot/initrd.img-4.11.0-rc8-siduction-amd64 I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=51ef98ff-6b41-479d-a4bb-ae4639681c0e) I: Set the RESUME variable to override this. IMHO initramfs should not attempt to resume from any zram device. -- System Information: Debian Release: 9.0 (Sid) Architecture: amd64 (x86_64), dual core.
Bug#860543: initramfs-tools: boot delayed by 30sec waiting for suspend/resume device
Package: initramfs-tools Version: 0.128 Severity: normal Dear Maintainer, After upgrading initramfs-tools from version 0.127 to 0.128 the boot process is delayed by about 30sec followed by the mention 'Gave up waiting for suspend/resume device'. There was no such delay when using version 0.127. -- System Information: Debian Release: 9.0 (Sid) Architecture: amd64 (x86_64) Init: systemd
Bug#844232: daisy-player: man page title is wrong if build directory isn't named ${package}-${version}
Is changed in the next release of daisy-player.
Thanks.
On Sun, Nov 13, 2016 at 04:22:29PM +, Daniel Shahaf wrote:
> Source: daisy-player
> Version: 10.3-2
> Severity: minor
> Tags: upstream patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: buildpath
>
> Dear Maintainer,
>
> Whilst working on the Reproducible Builds effort [0], we noticed
> that daisy-player could not be built reproducibly, due to `txt2man -p`
> parsing the last component of the build directory.
>
> Patch attached.
>
> [0] https://reproducible-builds.org/
>
> Cheers,
>
> Daniel
>
> P.S. The patch as written is upstreamable. For Debian it might make
> sense to use «$$(cd .. && dpkg-parsechangelog -SVersion)» so as to have
> a more detailed version number.
>
> [[[
> diff --git a/debian/patches/build-path-agnostic.diff
> b/debian/patches/build-path-agnostic.diff
> new file mode 100644
> index 000..94c89c2
> --- /dev/null
> +++ b/debian/patches/build-path-agnostic.diff
> @@ -0,0 +1,16 @@
> +Description: Make the build reproducible
> + Avoid 'txt2man -p' because it parses the build path.
> +Bug-Debian: https://bugs.debian.org/-1
> +Last-Update: 2016-11-13
> +
> +--- daisy-player-10.3.orig/man/Makefile.am
> daisy-player-10.3/man/Makefile.am
> +@@ -3,7 +3,7 @@ man_MANS = daisy-player.1
> + all: daisy-player
> +
> + daisy-player:
> +-@which txt2man > /dev/null && txt2man -p ${srcdir}/../doc/$@.txt >
> ${srcdir}/$@.1
> ++@which txt2man > /dev/null && txt2man -t $@ -s 1 -v "Linux Reference
> Manual" -r $(VERSION) ${srcdir}/../doc/$@.txt > ${srcdir}/$@.1
> + @file ${srcdir}/$@.1 && \
> +man2html ${srcdir}/$@.1 | tail -n +3 > ${srcdir}/../doc/$@.html
> +
> diff --git a/debian/patches/series b/debian/patches/series
> new file mode 100644
> index 000..222072b
> --- /dev/null
> +++ b/debian/patches/series
> @@ -0,0 +1 @@
> +build-path-agnostic.diff
> ]]]
--
Sent from Ubuntu 16.10
---
Jos Lemmens
Insulindesingel 37/A
3131 LM Vlaardingen
The Netherlands
Tel.: + 31-(0)10-248 0 266
E-mail: j...@jlemmens.nl
Homepage: www.jlemmens.nl
Bug#844228: ebook-speaker: man page title is wrong if build directory isn't named ${package}-${version}
Is changed in the next release of eBook-speaker.
Thanks.
On Sun, Nov 13, 2016 at 04:14:13PM +, Daniel Shahaf wrote:
> Source: ebook-speaker
> Version: 4.1.0-1
> Severity: minor
> Tags: patch upstream
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: buildpath
>
> Dear Maintainer,
>
> Whilst working on the Reproducible Builds effort [0], we noticed
> that ebook-speaker could not be built reproducibly, due to `txt2man -p`
> parsing the last component of the build directory.
>
> Patch attached.
>
> [0] https://reproducible-builds.org/
>
> Cheers,
>
> Daniel
>
> P.S. The patch as written is upstreamable. For Debian it might make
> sense to use «$$(cd .. && dpkg-parsechangelog -SVersion)» so as to have
> a more detailed version number.
>
>
> [[[
> diff --git a/debian/patches/build-path-agnostic.diff
> b/debian/patches/build-path-agnostic.diff
> new file mode 100644
> index 000..5d547f3
> --- /dev/null
> +++ b/debian/patches/build-path-agnostic.diff
> @@ -0,0 +1,19 @@
> +Description: Make the build reproducible
> + Avoid 'txt2man -p' because it parses the build path.
> +Bug-Debian: https://bugs.debian.org/-1
> +Last-Update: 2016-11-13
> +
> +--- a/man/Makefile.am
> b/man/Makefile.am
> +@@ -3,7 +3,10 @@
> + all: eBook-speaker
> +
> + eBook-speaker:
> +-@which txt2man > /dev/null && txt2man -p ${srcdir}/../doc/$@.txt > \
> ++@which txt2man > /dev/null && txt2man \
> ++-t 'eBook-speaker' -s 1 -v "Linux Reference Manual" \
> ++-r "ebook-speaker-$(VERSION)" \
> ++${srcdir}/../doc/$@.txt > \
> +${srcdir}/$@.1
> + @file ${srcdir}/$@.1 && \
> + man2html ${srcdir}/$@.1 | tail -n +3 > ${srcdir}/../doc/$@.html
> diff --git a/debian/patches/series b/debian/patches/series
> new file mode 100644
> index 000..222072b
> --- /dev/null
> +++ b/debian/patches/series
> @@ -0,0 +1 @@
> +build-path-agnostic.diff
> ]]]
--
Sent from Ubuntu 16.10
---
Jos Lemmens
The Netherlands
E-mail: j...@jlemmens.nl
Homepage: www.jlemmens.nl
Bug#841714: ebook-speaker: when I run ebook-speaker something.html I get prompt to isntall package xml2
Hello Yukasz, > Off-topic: I mistakenly thought that this version of ebook-speaker > reads mathml. Do you know if the version in testing read mathml, and > if yes, do you perhaps know if it would be any good on something like > http://www.lancaster.ac.uk/staff/grabows1/accessible/math111/doth4.S3.html > ? > > Thanks, > Yukasz eBook-speaker cannot handle mathml at this time. Can you send me such a file? Then I can try to update eBook-speaker. Regards, Jos. -- Sent from Ubuntu 16.10 ------- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl
Bug#841714: ebook-speaker: when I run ebook-speaker something.html I get prompt to isntall package xml2
Hello, On Sat, Oct 22, 2016 at 03:56:16PM +0100, Łukasz Grabowski wrote: > Package: ebook-speaker > Version: 2.8.1-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > running ebook-speaker something.html >* What exactly did you do (or not do) that was effective (or > ineffective)? Version 2.8 used the application html2text for conversion from HTML to TXT and then the app pandoc for conversion to EPUB. Later versions of eBook-speaker use pandoc to convert HTML into EPUB directly. Regards, Jos. >* What was the outcome of this action? > prompt to install package xml2 although it is alaready installed >* What outcome did you expect instead? > reading the file something.html > > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: 8.6 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages ebook-speaker depends on: > ii espeak1.48.04+dfsg-1 > ii libc6 2.19-18+deb8u6 > ii libmagic1 1:5.22+15-2+deb8u2 > ii libncursesw5 5.9+20140913-1+b1 > ii libsox2 14.4.1-5 > ii libtinfo5 5.9+20140913-1+b1 > ii libxml2 2.9.1+dfsg1-5+deb8u3 > ii unar 1.8.1-3+b1 > > ebook-speaker recommends no packages. > > Versions of packages ebook-speaker suggests: > pn calibre > ii ghostscript 9.06~dfsg-2+deb8u3 > ii libreoffice-writer 1:5.2.2~rc2-2~bpo8+1 > ii man2html-base 1.6g-7 > ii pandoc 1.12.4.2~dfsg-1+b13 > ii poppler-utils 0.26.5-2+deb8u1 > ii sane-utils 1.0.24-8+deb8u1 > ii tesseract-ocr 3.03.03-1 > ii xml20.4-3.1 > > -- no debconf information -- Sent from Ubuntu 16.10 --- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl
Bug#829557: lightdm 1.18.2-1 breaks D-BUS
I am using Debian/Sid and encountered the same issue. upgrading to lightdm_1.19.2-0ubuntu1_amd64.deb fixed all issues.
Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Bug#816376: Unfit upstream
On dinsdag 8 maart 2016 08:37:35 CET David Prévot wrote: > Hi, > > Le 08/03/2016 03:03, Jos Poortvliet a écrit : > > The situation is rather sad and frustrating > > OK. > > > as users who decided to trust the Debian developers and took their > > packages over ownCloud's provided packages are now stuck on a version > > which can't trivially be upgraded to either our upstream version or > > anything else. > The thing is, we were working on a proper upgrade path, but upstream > decided without even looking at it that it was “bad” (to put it mildly). > Because of upstream reaction, we have removed our work in progress, and > > now the PR crap (as in words not backed by anything) follows: > > We would love to find a solution for them I know that that is how you choose to look at it - and I feel there is no value to discuss that. > Regards > > David -- Disclaimer: Everything I do and say is based on my view of the world today. I am not responsible for changes in the world, nor my view on it. Everything I say is meant in a positive and friendly way, unless explicitly stated otherwise. find me on blog.jospoortvliet.com
Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Unfit upstream
On Monday, March 7, 2016 5:43:20 PM AMT Sébastien Villemot wrote: > Dear David, > > First, let me thank you for the work that you put into packaging > owncloud for Debian, it is really appreciated. > > On Tue, 1 Mar 2016 07:07:10 -0400 David =?iso-8859-1?Q?Pr=E9vot?= > <taf...@debian.org> wrote: > > > Upstream doesn’t wish to see their software in Debian anymore. Unless > > the situation changes in the next few months, owncloud will not be part > > of Stretch. > > Given that owncloud is such a useful and important package, and that > there is currently no credible alternative, this is really sad news, and > I am wondering whether this outcome could be avoided. > > If I understand correctly, your decision is essentially based on social > issues (upstream hostile to Debian packaging), coupled to some technical > aspects (complex upgrade paths). See my last email here - we'd love to have ownCloud included in Debian but obviously only if it provides a good experience to users. Right now, it seems that that is hard to do within the framework Debian provides. http://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/2016-March/002899.html The situation is rather sad and frustrating as users who decided to trust the Debian developers and took their packages over ownCloud's provided packages are now stuck on a version which can't trivially be upgraded to either our upstream version or anything else. We would love to find a solution for them - as I've said many times, our main concern is the end users, rather than politics, rules or anything else. Thanks for caring about this, Jos > At first glance, this does not seem to prevent the package from staying > in Debian. Maybe this just means that the package needs a new > maintainer, who is willing to handle the tough interaction with upstream > and dealing with the technical issues (note that I am not applying for > the job). > > You are certainly in a better position than me to ascertain whether the > package can stay in Debian or not, but I think that it would be useful > if you could give a little more background on the issues that you > encountered. And, if you think it makes sense to orphan the package, > that would help prospective new maintainers in making the decision to > adopt the package or not. > > Cheers, > > signature.asc Description: This is a digitally signed message part.
Bug#802432: fixed, can be closed.
Dear Maintainer, Issue fixed in version linux-image-4.3.0-trunk-amd64 (4.3-1~exp1). Bug #802432 can be closed. -- System Information: Debian Release: sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-4.3.0-trunk-amd64 Systemd: 227-2 Kind regards, Jos v.Wolput
Bug#802866: fcitx-frontend-qt5
Package: fcitx-frontend-qt5 Version: 1.0.4-1 Bug #802866 can be closed, the issue has been fixed by the release of version 1.0.4-1 in Sid. Thanks! Jos van Wolput
Bug#802866: fcitx-frontend-qt5 version 1.0.0-1 can't be installed
Package: fcitx-frontend-qt5 Version: 1.0.0-1 Severity: normal Dear Maintainer, Package fcitx-frontend-qt5 version 1.0.0-1 (experimental) can't be installed because of qtbase-abi not being available. Could this package be compiled for use with qt5 (5.5.1) which is already available in Sid? -- System Information: Debian Release: sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-4.3.0-rc5-amd64 Systemd: 227-2 Kind regards, Jos v.Wolput
Bug#802432: linux-image-4.3.0-rc5-amd64 fails to attach usb storage device
Package: linux-image-4.3.0-rc5-amd64 Version: 4.3~rc5-1~exp1 Severity: important Dear Maintainer, After upgrading linux-image-4.2.0-1-amd64 (4.2.3-2) from unstable to linux-image-4.3.0-rc5-amd64 from experimental my Verbatim usb flash drive is detected but fails to attach. Using kernel 4.2.3-2 this device is properly detected and attached. Please see the attached kernel.log -- System Information: Debian Release: sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-4.3.0-rc5-amd64 Systemd: 227-2 Kind regards, Jos v.Wolput Oct 20 11:34:21 debian kernel: [ 101.305777] usb-storage 2-2:1.0: USB Mass Storage device detected Oct 20 11:34:21 debian kernel: [ 101.306000] scsi host6: usb-storage 2-2:1.0 Oct 20 11:34:21 debian kernel: [ 101.306240] usbcore: registered new interface driver usb-storage Oct 20 11:34:21 debian kernel: [ 101.335548] usbcore: registered new interface driver uas Oct 20 11:34:22 debian kernel: [ 102.838335] scsi 6:0:0:0: Direct-Access Verbatim PQ: 0 ANSI: 4 Oct 20 11:34:22 debian kernel: [ 102.838737] [ cut here ] Oct 20 11:34:22 debian kernel: [ 102.838755] WARNING: CPU: 0 PID: 100 at /build/linux-HFgDpK/linux-4.3~rc5/kernel/kmod.c:140 __request_module+0x1e9/0x290() Oct 20 11:34:22 debian kernel: [ 102.838759] Modules linked in: uas usb_storage xt_recent nf_log_ipv4 nf_log_common snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device xt_tcpudp ip6table_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_TCPMSS xt_LOG ipt_REJECT nf_reject_ipv4 iptable_mangle xt_multiport xt_state xt_limit xt_conntrack nf_conntrack_ftp nf_conntrack ip6table_filter ip6_tables iptable_filter ip_tables x_tables binfmt_misc zram zsmalloc hid_generic usbhid hid arc4 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media rt2800pci rt2800mmio rt2800lib rt2x00pci rt2x00mmio joydev rt2x00lib eeprom_93cx6 mac80211 tg3 snd_hda_codec_realtek pcmcia kvm_amd cfg80211 snd_hda_codec_generic snd_hda_codec_hdmi ptp pps_core libphy kvm psmouse crc_ccitt snd_hda_intel rfkill pcspkr snd_hda_codec yenta_socket evdev snd_hda_core serio_raw pcmcia_rsrc snd_hwdep pcmcia_core snd_pcm_oss snd_mixer_oss k10temp snd_pcm ohci_pci sp5100_tco i2c_piix4 sr_mod ohci_hcd snd_timer ehci_pci cdrom snd ehci_hcd soundcore sg usbcore usb_common shpchp battery ene_ir rc_core wmi ac video button acpi_cpufreq processor loop parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 sd_mod ahci libahci radeon libata i2c_algo_bit drm_kms_helper scsi_mod ttm drm thermal lz4 lz4_compress Oct 20 11:34:22 debian kernel: [ 102.838926] CPU: 0 PID: 100 Comm: kworker/u4:4 Not tainted 4.3.0-rc5-amd64 #1 Debian 4.3~rc5-1~exp1 Oct 20 11:34:22 debian kernel: [ 102.838930] Hardware name: Acer TravelMate 4530 /Elgon , BIOS V1.11 08/06/2008 Oct 20 11:34:22 debian kernel: [ 102.838938] Workqueue: events_unbound async_run_entry_fn Oct 20 11:34:22 debian kernel: [ 102.838943] 817f5230 812c0349 8106ee11 Oct 20 11:34:22 debian kernel: [ 102.838949] a00de839 8800b8287d70 0001 88009cefa168 Oct 20 11:34:22 debian kernel: [ 102.838954] 81081e99 88012d4c85c0 88012548bba0 Oct 20 11:34:22 debian kernel: [ 102.838960] Call Trace: Oct 20 11:34:22 debian kernel: [ 102.838974] [] ? dump_stack+0x40/0x57 Oct 20 11:34:22 debian kernel: [ 102.838980] [] ? warn_slowpath_common+0x81/0xb0 Oct 20 11:34:22 debian kernel: [ 102.838989] [] ? __request_module+0x1e9/0x290 Oct 20 11:34:22 debian kernel: [ 102.838995] [] ? mutex_lock+0xe/0x30 Oct 20 11:34:22 debian kernel: [ 102.839004] [] ? kernfs_activate+0x65/0xe0 Oct 20 11:34:22 debian kernel: [ 102.839010] [] ? kernfs_add_one+0x100/0x160 Oct 20 11:34:22 debian kernel: [ 102.839048] [] ? scsi_dh_lookup+0x29/0x40 [scsi_mod] Oct 20 11:34:22 debian kernel: [ 102.839067] [] ? scsi_dh_add_device+0xca/0xf0 [scsi_mod] Oct 20 11:34:22 debian kernel: [ 102.839085] [] ? scsi_sysfs_add_sdev+0xb8/0x280 [scsi_mod] Oct 20 11:34:22 debian kernel: [ 102.839101] [] ? do_scan_async+0x116/0x160 [scsi_mod] Oct 20 11:34:22 debian kernel: [ 102.839107] [] ? async_run_entry_fn+0x45/0x140 Oct 20 11:34:22 debian kernel: [ 102.839113] [] ? process_one_work+0x14a/0x3b0 Oct 20 11:34:22 debian kernel: [ 102.839118] [] ? worker_thread+0x4d/0x450 Oct 20 11:34:22 debian kernel: [ 102.839124] [] ? rescuer_thread+0x2e0/0x2e0 Oct 20 11:34:22 debian kernel: [ 102.839130] [] ? kthread+0xbd/0xe0 Oct 20 11:34:22 debian kernel: [ 102.839136] [] ? kthread_park+0x50/0x50 Oct 20 11:34:22 debian kernel: [ 102.839143] [] ? ret_from_fork+0x3f/0x70 Oct 20 11:34:22 debian kernel: [ 102.839149] [] ? kthread_park+0x50/0x50 Oct 20 11:34:22 debian kernel: [ 102.839153] ---[ end trace f351e1b4e96fc210 ]--- Oct 20 11:34:22 debian kernel: [ 102.841533] sd 6:0:0:0: [sdb
Bug#797763: shutdown h:m in systemd 225 shuts down the system immediately
Package: systemd Version: 225-1 Severity: normal Dear Maintainer, After upgrading systemd from v.224-2 to 225-1 shutdown at a scheduled time (shutdown h:m) shuts down the system immediately, not at the scheduled time. Using systemd v.224-2 it works correctly, shutting down at the scheduled time according to /var/run/systemd/shutdown/scheduled. -- System Information: Debian Release: sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-4.2.0-trunk-amd64 Systemd: 225-1 Kind regards, Jos v.Wolput
Bug#783544: daisy-player: cdio_set_speed() function lets daisy-player crash
Hallo Paul, In Ubuntu 14.10 zit daisy-player 8.7.0-1. daar geeft de C functie cdio_set_speed() geen problemen. Ik heb ubuntu-bug nog eens geprobeerd, maar krijg steeds dezelfde fout-melding. toen keek ik in de source en zag: script type=text/javascript document.documentElement.className += ' js'; /script Javascript werkt bij mij niet. Ik zal Martin Pitt een mailtje sturen. Groet, Jos. On Tue, Apr 28, 2015 at 08:14:56PM +0200, Paul Gevers wrote: Control: owner -1 ! Just so nobody understands this wrongly, Jos is upstream of daisy-player, and he is using Ubuntu 15.04 and sees his own program crash. I asked him to report in Ubuntu, but that failed, that is why he ended up reporting here. Paul -- --- Jos Lemmens Insulindesingel 37/A 3131 LM Vlaardingen The Netherlands Tel.: + 31-(0)10-248 0 266 E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783544: daisy-player: cdio_set_speed() function lets daisy-player crash
Package: daisy-player Version: 9.0.0-1 Severity: normal Dear Maintainer, daisy-player crashes while mounting a DAISY-CD. - apt-get source daisyplayer - removed the cdio_set_speed() function call from audiocd.c - ./configure make Now runs fine -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-15-generic (SMP w/4 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to nl_NL.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages daisy-player depends on: ii libc6 2.21-0ubuntu4 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libmagic1 1:5.20-1ubuntu2 ii libncursesw5 5.9+20140712-2ubuntu2 ii libsox214.4.1-5 ii libtinfo5 5.9+20140712-2ubuntu2 ii libxml22.9.2+dfsg1-3 ii madplay0.15.2b-8 ii udisks22.1.5-1 ii unar 1.8.1-3 Versions of packages daisy-player recommends: ii libcddb-get-perl 2.28-1 daisy-player 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#759654: bug#759654 fixed, can be closed.
I checked my system and discovered files from a previous local build from three years ago in /usr/bin. After removing all this old systemd files and reinstallingsystemd this issue is fixed. This bug can be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: fixed, can be closed.
This issue is fixed by installing adjtimex and acpi_pm as clocksource, the interval now increases exponentially. The bug can be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773269: fixed, can be closed.
I checked my system and discovered files from a previous local build from three years ago in /usr/bin. After removing all this old systemd files and reinstallingsystemd this issue is fixed. This bug can be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776350: systemd 218-6 libsystemd-* libraries dependencies
On 01/27/2015 03:23 PM, Martin Pitt wrote: Can you please verify that you actually have the current versions installed and not a local build somewhere else? journalctl and systemctl as in the package don't depend on libsystemd* at all. I checked 'whereis systemctl' and discovered files from a previous local build from three years ago in /usr/bin. After removing all this old systemd files and reinstalling version 218-6 this issue is fixed. Thanks for the tip! This bug can be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776350: systemd 218-6 libsystemd-* libraries dependencies
Package: systemd Version: 218-6 Severity: normal Dear Maintainer, After upgrading systemd from 218-5 to 218-6 and removing the obsolete libsystemd-daemon0, libsystemd-id128-0 and libsystemd-journal0 which have been dropped in version 218-6, systemctl and journalctl complain about missing libsystemd-daemon.so.0, libsystemd-journal.so.0 and libsystemd-id128.so.0 although there should not be dependencies left. Reinstalling libsystemd-* from version 218-5 fixes this issue. -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Systemd: 218-6 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: systemd-timesyncd syncs time about once per minute
This issue is fixed by enabling hpet in grub, setting GRUB_CMDLINE_LINUX=upgrade-from-grub-legacy vga=769 hpet=enable. Using htep as clocksource instead of acpi_pm the interval now increases exponentially: Dec 21 14:27:26 debian systemd-timesyncd[2663]: Using NTP server 202.112.29.82:123 (0.cn.pool.ntp.org). Dec 21 14:27:26 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 32s/-0.083s/0.045s/0.000s/-411ppm Dec 21 14:27:58 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 64s/+0.014s/0.044s/0.005s/-299ppm Dec 21 14:29:02 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 128s/+0.020s/0.046s/0.013s/-222ppm Dec 21 14:31:43 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 256s/+0.042s/0.048s/0.016s/-140ppm Dec 21 14:35:59 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 512s/+0.041s/0.049s/0.018s/-100ppm Dec 21 14:45:03 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 512s/+0.066s/0.049s/0.026s/-35ppm Dec 21 14:54:08 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 1024s/+0.025s/0.044s/0.023s/-23ppm Dec 21 15:11:44 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 2048s/+0.038s/0.046s/0.021s/-14ppm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: systemd-timesyncd syncs time about once per minute
This issue is fixed by enabling hpet in GRUB_CMDLINE_LINUX=upgrade-from-grub-legacy vga=769 hpet=enable. By default hpet is disabled. Using hpet instead of acpi_pm as clocksource the interval now increases exponentially: Dec 21 14:27:26 debian systemd-timesyncd[2663]: Using NTP server 202.112.29.82:123 (0.cn.pool.ntp.org). Dec 21 14:27:26 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 32s/-0.083s/0.045s/0.000s/-411ppm Dec 21 14:27:58 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 64s/+0.014s/0.044s/0.005s/-299ppm Dec 21 14:29:02 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 128s/+0.020s/0.046s/0.013s/-222ppm Dec 21 14:31:43 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 256s/+0.042s/0.048s/0.016s/-140ppm Dec 21 14:35:59 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 512s/+0.041s/0.049s/0.018s/-100ppm Dec 21 14:45:03 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 512s/+0.066s/0.049s/0.026s/-35ppm Dec 21 14:54:08 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 1024s/+0.025s/0.044s/0.023s/-23ppm Dec 21 15:11:44 debian systemd-timesyncd[2663]: interval/delta/delay/jitter/drift 2048s/+0.038s/0.046s/0.021s/-14ppm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773269: Computer crash when installing cups-daemon
On 12/19/2014 09:55 PM, Michael Biebl wrote: It would also help, if you can test with systemd from testing/unstable and the Debian kernel from testing/unstable. Previously I was using kernel 3.18.0 but now 3.18.1 and can't reproduce this issue. As it is not clear in which circumstances this issue occurs and I have installed many packages from experimental, I would suggest not spending more time on this issue and close 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#773252: systemd-timesyncd syncs time about once per minute
On 12/16/2014 09:31 PM, Michael Biebl wrote: roughly 30s - 1m, 1m - 2m, 2m - 4m, 4m - 8m ... This looks like a sensible approach to me. As the interval of systemd-timesyncd on my system never increases I have disabled systemd-timesyncd and instead inabled ntp service (/etc/init.d/ntp). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773269: Computer crash when installing cups-daemon 1.7.5-10
On 12/17/2014 11:47 PM, Didier 'OdyX' Raboud wrote: Control: tags -1 +experimental +moreinfo Could you be more precise in what you mean by computer crash? Can you still SSH to the machine for example? Can you switch to the first tty (Ctrl-Alt-F1)? Are there kernel or systemd logs displayed there? All keys are dead, the mouse is no longer working, the screen is frozen and it is no longer possible to switch to another tty but the disk is still working, after a hard reboot the cups packages were installed. I'm sorry I don't have system logs because they are set tmpfs. I tried to reproduce this issue but it occurs only very occasionally. Today I had a similar issue installing sane-utils which too has to stop a systemd service. Cheers, Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773269: Computer crash when installing cups-daemon 1.7.5-10
Package: cups-daemon Version: 1.7.5-10 Severity: important Dear Maintainer, Installing the newest cups* (version 1.7.5-10) packages from Sid I get a computer crash (needing hard reboot) when apt-get install cups-daemon has been stopping the cups service using systemctl. Systemctl stop cups.service itself doesn't produce a crash. The bug is reproducible, even when the cups service is disabled and not running. -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: Linux debian 3.18-0 amd6 Systemd: 218-1 Kind regards, Jos van Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: systemd-timesyncd syncs time about once per minute
On 12/16/2014 09:07 PM, Michael Biebl wrote: What makes you think systemd-timesync syncs the clock once every 60 seconds? Even every 32 seconds! The systemd journal and the output of systemctl status systemd-timesyncd.service: systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled) Active: active (running) since Tue, 16 Dec 2014 21:21:56 +0800; 8min ago Docs: man:systemd-timesyncd.service(8) Main PID: 24099 (systemd-timesyn) Status: Using Time Server 202.112.10.36:123 (0.debian.pool.ntp.org). Dec 16 21:24:42 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 64s/+0.030s/0.192s/0.043s/+500ppm Dec 16 21:25:47 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.194s/0.095s/0.154s/+500ppm Dec 16 21:26:19 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.084s/0.111s/0.142s/+500ppm Dec 16 21:26:51 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.060s/0.098s/0.132s/+500ppm Dec 16 21:27:23 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.066s/0.101s/0.134s/+500ppm Dec 16 21:27:56 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.063s/0.095s/0.133s/+500ppm Dec 16 21:28:28 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.058s/0.081s/0.053s/+500ppm Dec 16 21:29:00 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.075s/0.100s/0.054s/+500ppm Dec 16 21:29:32 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.087s/0.133s/0.054s/+500ppm Dec 16 21:30:05 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.126s/0.088s/0.030s/+500ppm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: systemd-timesyncd syncs time about once per minute
On 12/16/2014 09:31 PM, Michael Biebl wrote: Am 16.12.2014 um 14:07 schrieb Michael Biebl: Am 16.12.2014 um 04:45 schrieb Jos van Wolput: Package: systemd Version: 215-8 and 218-1 Severity: normal Dear Maintainer, Systemd-timesyncd syncs time about once per 60 seconds. What makes you think systemd-timesync syncs the clock once every 60 seconds? I just studied the code and timesyncd starts with a minimal 32 second interval (NTP_POLL_INTERVAL_MIN_SEC) which is increased until it reaches the maximum 2048 second polling interval (NTP_POLL_INTERVAL_MAX_SEC). It seems to use an exponential like back-off algorithm as shown by the journal Dez 16 14:07:41 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 32s/+0.253s/0.028s/0.000s/+500ppm Dez 16 14:08:13 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 64s/-0.005s/0.025s/0.002s/+460ppm Dez 16 14:09:17 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 128s/-0.022s/0.040s/0.008s/+373ppm Dez 16 14:11:25 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 128s/-0.053s/0.024s/0.050s/+165ppm Dez 16 14:13:33 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 256s/+0.030s/0.124s/0.055s/+165ppm (ignored) Dez 16 14:17:50 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 256s/-0.056s/0.026s/0.052s/+55ppm Dez 16 14:22:06 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 512s/-0.012s/0.025s/0.050s/+43ppm Dez 16 14:30:38 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 1024s/+0.046s/0.149s/0.059s/+43ppm (ignored) roughly 30s - 1m, 1m - 2m, 2m - 4m, 4m - 8m ... This looks like a sensible approach to me. After half an hour I stll get an interval of 32. it doesn't increase exponentialy: Dec 16 21:24:42 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 64s/+0.030s/0.192s/0.043s/+500ppm Dec 16 21:25:47 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.194s/0.095s/0.154s/+500ppm Dec 16 21:26:19 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.084s/0.111s/0.142s/+500ppm . Dec 16 22:01:01 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.065s/0.116s/0.018s/+500ppm Dec 16 22:01:33 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.065s/0.110s/0.017s/+500ppm Dec 16 22:02:05 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.062s/0.104s/0.015s/+500ppm Dec 16 22:02:38 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.062s/0.097s/0.005s/+500ppm Dec 16 22:03:10 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.110s/0.097s/0.019s/+500ppm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: systemd-timesyncd syncs time about once per minute
Package: systemd Version: 215-8 and 218-1 Severity: normal Dear Maintainer, Systemd-timesyncd syncs time about once per 60 seconds. I don't know if this very short interval is a bug or really intented. Should it not be once in 60 minutes? If this short interval is indeed intended, how could it be set to a longer value ? -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: Linux debian 3.18-0 amd6 Systemd: 218-1 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773015: desktop-base (8.0.1) missing Lines login-background.svg
Package: desktop-base Version: 8.0.1 Severity: important Dear Maintainer, After ubgrading desktop-base 8.0.0 to 8.0.1 lightdm does no longer show the Lines login-background.svg because it missing in the package. No such issue using version 8.0.0. -- System Information: Debian Release: Sid Architecture: amd64 (x86_64) Regards, Jos van Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768522: libcurl3 (version 7.38.0-3) relocation error
On 11/08/2014 06:24 PM, Adam D. Barratt wrote: Given: -- System Information: Debian Release: jessie/sid + experimental which version of libssl1.0.0 do you have installed? If it's 1.0.2 from experimental, does downgrading to unstable's version help? I did have installed libssl1.0.0 version 1.0.2~beta3-1 from experimental, downgrading to 1.0.1j-1 (unstable) and installing libcurl3 (version 7.38.0-3) fixes this issue. Thanks! Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768522: libcurl3 (version 7.38.0-3) relocation error
Package: libcurl3 Version: version 7.38.0-3 in unstable Severity: important Dear Maintainer, After upgrading libcurl3 from version 7.38.0-2 to 7.38.0-3 boinc-client (dep: libcurl3) is no longer running because of the following error in libcurl3: --- relocation error: /usr/lib/x86_64-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference --- Reverting libcurl3 to version 7.38.0-2 (testing) fixes this issue. -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: Linux debian 3.17-2 amd6 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757993: bootflag on bootable /dev/sdb2
I tested version 0.14.10 with python-parted installed: fdisk -l Device Boot Start End Sectors Size Id Type /dev/sdb12048 482347007 482344960 230G c W95 FAT32 (LBA) /dev/sdb2 *482347008 48159 2097152 1G c W95 FAT32 (LBA) /dev/sdb3 48160 976773166 492329007 234.8G 83 Linux --- grml2usb --grub --grub-mbr /home/jos/backup/grml64-full_2014.03.iso /dev/sdb2 Executing grml2usb version 0.14.10 Warning: the specified device /dev/sdb2 does not look like a removable usb device. Do you really want to continue? y/N y Using ISO /home/jos/backup/grml64-full_2014.03.iso Identified grml flavour grml64-full. Copying files. This might take a while Installing default MBR Installing grub as bootloader /usr/sbin/grub-install: error: More than one install device?. Installing for i386-pc platform. Installation finished. No error reported. Note: grml flavour grml64-full was installed as the default booting system. Note: you can boot flavour grml64-full using 'grml64-full' on the commandline. Finished execution of grml2usb (0.14.10). Have fun with your Grml system. grml2usb --grub --grub-mbr /home/jos/backup/grml64-full_2014.03.iso /dev/sdb2 8.97s user 6.44s system 17% cpu 1:28.75 total --- Apart from a warning and an error it installs and works properly. About the warning: my /dev/sdb2 is a removable usb hard disk. What about error: More than one install device? Thanks, Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757993: grml2usb (0.14.7) regression, fatal error: grml2usb doesn't see the bootflag on bootable /dev/sdb2
I downloaded and compiled grml2usb-360632e096cbcd38d025d610cd64ce3fbb45c131.zip but it doesn't solve this issue. root@debian:/home/jos/src/grml2usb-360632e096cbcd38d025d610cd64ce3fbb45c131# ./grml2usb --grub --grub-mbr /home/jos/backup/grml64-full_2014.03.iso /dev/sdb2 Executing grml2usb version ***UNRELEASED*** Warning: the specified device /dev/sdb2 does not look like a removable usb device. Do you really want to continue? y/N y Using ISO /home/jos/backup/grml64-full_2014.03.iso Fatal: Device /dev/sdb2 does not have the bootflag set. Please enable it to be able to boot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759654: systemctl: Failed to issue method call: Did not receive a reply.
Package: systemd Version: 214-1 (experimental) Severity: normal Dear Maintainer, After upgrading systemd v.208-8 to v.214-1 systemctl status/start/stop some service.service (in a root terminal) quite often shows the following error: --- Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. --- To get systemctl working I have to repeat it a few times until I get the result. The same error also occurs with apt-get install some package. My network connection is always working! -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: Linux debian 3.16-1.dmz.1-liquorix-amd64 Systemd, udev: 214-1 dbus: 1.8.6-2 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759662: Enabling UAS makes Seagate Expansion Desk unavailable (with workaround)
Package: linux-image-3.16-trunk-amd64 Version: 3.16-1~exp1 (experimental) Severity: normal Dear Maintainer, After upgrading my linux kernel to 3.16 I have problems with my Seagate expansion hard drive. While mounting it or writing to it, my whole system sometimes freezes and needs a hard reset. It seems to be a known UAS (USB Attached SCSI) issue and there is a workaround, see https://bugzilla.kernel.org/show_bug.cgi?id=79511 and https://bbs.archlinux.org/viewtopic.php?id=183190 The workaround fixes the issue by telling the USB-UAS module to ignore the device. -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: Linux debian 3.16-1 amd6 Systemd, udev: 214-1 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757993: grml2usb (0.14.7) regression, fatal error: grml2usb doesn't see the bootflag on bootable /dev/sdb2
Package: grml2usb Version: 0.14.7 Severity: important Dear Maintainer, Using grml2usb (0.14.7) to install grml on my external usb hard disk, grml2usb doesn't see the bootflag on bootable /dev/sdb2: The partition of my usb hd: fdisk -l Device Boot Start End Sectors Size Id Type /dev/sdb12048 482347007 482344960 230G c W95 FAT32 (LBA) /dev/sdb2 *482347008 48159 2097152 1G c W95 FAT32 (LBA) /dev/sdb3 48160 976773166 492329007 234.8G 83 Linux grml2usb --grub --grub-mbr grml64-full_2014.03.iso /dev/sdb2 Executing grml2usb version 0.14.7 Warning: the specified device /dev/sdb2 does not look like a removable usb device. Do you really want to continue? y/N y Using ISO grml64-full_2014.03.iso Fatal: Device /dev/sdb does not have the bootflag set. Please enable it to be able to boot. No such issue when using version 0.12.2 from wheezy, it installs a working grml on bootable /dev/sdb2. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: 3.16-0.slh.2-aptosid-amd64 Systemd, udev: 208-3 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756177: util-linux (2.25-3) fdisk :cannot open /dev/sr0: No medium found
Package: util-linux Version: 2.25-3 Severity: important Dear Maintainer, After upgrading util-linux 2.20.1-5.8 (sid) to version 2.25-3 (experimental) fdisk -l ends with the following error: cannot open /dev/sr0: No medium found --- fdisk -l Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0009db4b Device Boot Start End Sectors Size Id Type /dev/sda1 * 63 39070079 39070017 18.6G 83 Linux /dev/sda239070080 488392064 449321985 214.3G 5 Extended /dev/sda539070206 478720934 439650729 209.7G 83 Linux /dev/sda6 478722983 488392064 9669082 4.6G 83 Linux fdisk: cannot open /dev/sr0: No medium found --- and the other devices /dev/sdb* are not shown. Indeed I don't use the cdrom (sr0) but using fdisk -l from util-linux 2.20.1-5.8 (sid) there is no such issue, all disks are shown: --- fdisk -l Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0009db4b Device Boot Start End Blocks Id System /dev/sda1 * 633907007919535008+ 83 Linux /dev/sda239070080 488392064 224660992+ 5 Extended /dev/sda539070206 478720934 219825364+ 83 Linux /dev/sda6 478722983 488392064 4834541 83 Linux Disk /dev/sdb: 500.1 GB, 500107861504 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773167 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xe5267306 Device Boot Start End Blocks Id System /dev/sdb12048 482347007 241172480c W95 FAT32 (LBA) /dev/sdb2 * 482347008 48159 1048576c W95 FAT32 (LBA) /dev/sdb3 48160 976773166 246164503+ 83 Linux --- -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-3.16-rc6-amd64 Systemd, udev: 208-3 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755995: External USB HD problem in linux kernel 3.16 with usb-uas module
Package: linux-image-3.16-rc6-amd64 Version: 3.16~rc6-1~exp1 Severity: important Dear Maintainer, After upgrading linux to 3.16-rc6 I have problems with my Seagate expansion hard drive. While mounting it or writing to it, my whole system quite often freezes and needs a hard reset. It seems to be a known UAS (USB Attached SCSI) issue and there is a workaround, see https://bbs.archlinux.org/viewtopic.php?id=183190 The mentioned workaround fixes the issue by telling the USB-UAS module to ignore the device. To avoid this issue the UAS module should be patched to handle the hard disk correctly. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: linux-image-3.16-rc6-amd64 Systemd, udev: 208-3 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755768: grml2usb (0.14.6)
Bug #755952 (grml2usb --grub stops with 'NoneType' object has no attribute 'rfind') and #755768 (grml2usb (0.14.6) :fatal error) are the same and can be merged. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755768: grml2usb (0.14.6) :fatal error
Package: grml2usb Version: 0.14.6 Severity: important Dear Maintainer, Using grml2usb (0.14.6) to install grml on my external usb harddisk I get the following fatal error: --- Executing grml2usb version 0.14.6 Warning: the specified device /dev/sdb1 does not look like a removable usb device. Do you really want to continue? y/N y Using ISO grml64-full_2014.03.iso Identified grml flavour grml64-full. Copying files. This might take a while Installing default MBR Installing grub as bootloader Fatal: 'NoneType' object has no attribute 'rfind' --- No such issue when using version 0.12.2 from wheezy, it installs a working grml. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: 3.15-6.dmz.2-liquorix-amd64 Systemd, udev: 208-3 Kind regards, Jos v.Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752739: plymouth (0.9.0): VT1 login issue
This issue was caused by an error in /etc/systemd/system, not a bug. Bug 752739 can be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752739: plymouth (0.9.0-3): VT1 login incorrect, VT7 issue
Package: plymouth Version: 0.9.0-3 Severity: important Dear Maintainer, Since upgrade from 0.8.8-17 to 0.9.0-3 login as root or as user to vt1 (tty1) is no longer possible. After typing the (correct) password and pressing enter the login screen shows 'Login incorrect'. After stopping lightdm it's also not possible to login to vt7, 'Debian login:' is not shown. Login to other vertual terminals (vt2 - vt6) works. No such login issues using plymouth 0.8.8-17. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: 3.14-8.dmz.1-liquorix-amd64 Systemd, udev: 208-3 Kind regards, Jos v. Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750866: inux-image-3.15-rc8-amd64: Freezes by writing to disk, needs hard reboot.
Package: linux-image-3.15-rc8-amd64 Version: 3.15~rc8-1~exp1 I get a similar issue when writing to my external usb hard disk: the system freezes completely and needs a hard reboot. No such issue using linux image 3.14. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734244: closed by Roland Stigge sti...@antcom.de (Bug#734244: fixed in testdisk 6.14-3)
Please reopen bug #734244, testdisk_6.14-3_amd64 can't be installed because of the same dependency problem: - dpkg -i testdisk_6.14-3_amd64.deb (Reading database ... 191748 files and directories currently installed.) Preparing to unpack testdisk_6.14-3_amd64.deb ... Unpacking testdisk (6.14-3) over (6.14-2) ... dpkg: dependency problems prevent configuration of testdisk: testdisk depends on libntfs-3g844; however: Package libntfs-3g844 is not installed. dpkg: error processing package testdisk (--install): dependency problems - leaving unconfigured Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: testdisk - On 04/13/2014 07:09 PM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the testdisk package: #734244: testdisk (6.14-2) has unmet dependencies It has been closed by Roland Stigge sti...@antcom.de. 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 Roland Stigge sti...@antcom.de by replying to this email. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741008: xfce4-panel (4.11): applications menu doesn't show debian-, kde- and gnome-menus applications.
Package: xfce4-panel Version: 4.11.0-1 (experimental) Severity: normal Dear Maintainer, When choosing the custom menu 'debian-menu.menu' from /var/lib/menu-xdg/menus/, the xfce4-panel menu doesn't show debian-menu applications. Only Help, Office and System Tools are shown together with a mention 'No applications found'. Same issue when choosing kde4-applications.menu or gnome-applications.menu. Not all applications are shown and a mention 'No applications found' is displayed. I have also reported to Xfce Bugzilla – Bug 10532 No such issue with version 4.10.1, all apps are displayed. --- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-3.13-5-amd64 Desktop: xfce4 4.11 (experimental) Jos van Wolput http://homepages.onsneteindhoven.nl/~wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741008: xfce4-panel (4.11): applications menu doesn't show debian-, kde- and gnome-menus applications.
On 03/07/2014 03:10 PM, Yves-Alexis Perez wrote: Thanks for the report, but I'm unlikely to spent any time fixing the debian menu. If upstream fixes it, then fine, but I won't look at it. I fixed this issue for my own use by patching the xfce4-panel-4.11 source, replacing ~/xfce4-panel-4.11.0/plugins/applicationsmenu by the ~/applicationsmenu of xfce4-panel-4.10.1 source. No compilation errors. All apps from the debian menu are shown. Regards, Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733480: bash 4.3-rc2 gcc-4.9 compiler very slow
Dear Maintainer, This issue is fixed after installing bash 4.3-1 (Sid), compiling with gcc-4.9 is no longer slow. This bug can be closed. Jos van Wolput http://homepages.onsneteindhoven.nl/~wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733480: bash 4.3~rc2 gcc-4.9 compiler very slow
On 26.02.2014 22:21, Matthias Klose wrote: apt-get remove bash-completion Removing bash-completion doesn't fix this issue: after purging bash-completion (and rebooting) gcc-4.9 compiler is still very slow. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734428: xserver-xorg-core (1.15.0-1) can not be installed because of unmet dependencies
Package: xserver-xorg-core Version: 2:1.15.0-1 (experimental) Severity: important xserver-xorg-core (1.15.0-1) can't be installed because of unmet dependencies: apt-get install xserver-xorg-core/experimental xserver-xorg-input-evdev xserver-xorg-video-radeon Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-input-evdev is already the newest version. xserver-xorg-video-radeon is already the newest version. Selected version '2:1.15.0-1' (Debian:experimental [amd64]) for 'xserver-xorg-core' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-input-evdev : Depends: xorg-input-abi-19 xserver-xorg-video-radeon : Depends: xorg-video-abi-14 E: Unable to correct problems, you have held broken packages. --- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-3.13-rc6-amd64 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734244: testdisk (6.14-2) has unmet dependencies
Package: testdisk Version: 6.14-2 Severity: important When ntfs-3g version 1:2013.1.13AR.3-4 (experimental) is installed, testdisk (6.14-2) can't be installed because of unmet dependencies: apt-get install testdisk ntfs-3g Reading package lists... Done Building dependency tree Reading state information... Done ntfs-3g is already the newest version. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: testdisk : Depends: libntfs-3g841 E: Unable to correct problems, you have held broken packages. Installing ntfs-3g 1:2013.1.13AR.1-2 (unstable) fixes this issue. --- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: linux-image-3.12-6-amd64 ntfs-3g: 1:2013.1.13AR.3-4 (experimental) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733480: bash 4.3~rc1-1 gcc-4.8 compiler very slow
Package:bash Version: 4.3~rc1-1 (experimental) Severity: important After upgrading bash 4.2+dfsg-1 (unstable) to version 4.3~rc1-1 (experimental) compiling with gcc-4.8 (4.8.2-10) has become very slow. For example: using bash/4.2, make xf86-input-evdev takes 5 seconds, using bash/4.3~rc1 the same compilation takes about 60 seconds! Both compilations started after make distclear and autogen in konsole (4:4.11.3-1). Reverting to bash version 4.2 fixes this issue. --- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: linux-image-3.12-6-amd64 Libc6: 2.18-0 experimental -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732256: Busybox 1.21.0-5exp kernel boot panic
Package: busybox Version: 1.21.0-5exp Severity: important After upgrading busybox 1.21.0-1 (sid) to 1.21.0-5exp (experimental) all newly installed kernels panic in the boot process: --- Begin: Running /scripts/local-bottom ...done Begin: Running /scripts/init-bottom ...done /init: exec: line 331: switch_root: not found kernel panic - not syncing: attempted to kill init! exit code: 0x0200 CPU:0 PID:1 Comm : init Not tainted 3.12-trunk-amd64 Hardware name: Acer Travelmate 4530 --- Reverting to busybox 1.21.0-1 and reintalling the new kernel fixes this issue. --- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: linux-image-3.12-trunk-amd64 (3.12.3-1~exp1) Systemd v.204-2 initramfs-tools 0.115 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731820: translation for daisy-player and/or eBook-speaker
Hello Jarek, In Debian, Ubuntu, Knoppix and alike resides my daisy-player and eBook-speaker. daisy-player A full featured DAISY cd player for Linux. eBook-speaker read aloud eBooks, text documents or scanned documents using a software speech-synthesizer like espeak. May I ask you if you will be so kind to translate these applications into Polish. You can do this on my website: http://www.jlemmens.nl Many thanks in advance. Best regards, Jos. -- --- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: lightdm, xfce4: No working restart/shutdown buttons
Hi, On my system, Debian/Sid using systemd and xfce4, I have solved the issue of no working lightdm and xfce4 buttons. As I already mentioned in Message #203, the xfce4 issue is fixed by upgrading policykit-1 to version 0.112-2 (experimental). The issue of the disappeared lightdm buttons is fixed by installing some rules in /etc/polkit-1/rules.d, enabling shutdown/restart/suspend/hibernate, see the attached file. Regards, Jos v.W. 99-lightdm-powerbuttons.rules Description: Binary data
Bug#728361: shutdown/restart/suspend/hibernate buttons
Upgrading policykit-1 to version 0.112-2 solves the problem (at least on my xfce4 system)! After upgrading policykit-1/0.105-4 (sid) to 0.112-2 (experimental) the xfce4 logout shutdown/restart/suspend/hibernate buttons are no longer greyed out, the lightdm/1.8.5-1 shutdown/restart/suspend/hibernate buttons are showed again. The only remaining issue is that after a second login the lightdm restart and hibernate buttons have disappeared, shutdown and suspend are still there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: lightdm and pam-auth-update --force
In message #163 Louis Delmas advises pam-auth-update --force then selecting only Unix Authentication. I tried selecting only Register user sessions in the systemd control group hierarchy and got a weird issue: lightdm allowed logging in without password. Immediately after typing a user name, no password is asked, and logging in is started, as user and as root. This could be a security issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: xfce4: No working restart/shutdown buttons
On 07/11/13 05:35, Yves-Alexis Perez wrote: Can you check if libpam-ck-connector is installed? libpam-ck-connector was not installed. After installing still no shutdown... buttons in lightdm and xfce4 log out. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: xfce4: No working restart/shutdown buttons
After upgrading policykit-1/0.105-4 (sid) to policykit-1/0.112-2 (experimental) lightdm 1.6.3-1 shows the same issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: xfce4: No working restart/shutdown buttons
On 11/01/2013 06:41 PM, Yves-Alexis Perez wrote: Ok so it's not just GNOME related. Can you provide your .xsession-errors.log (beware of anything private there) and the result of: dpkg -l |egrep 'consolekit|policykit|systemd' # dpkg -l |egrep 'consolekit|policykit|systemd' ii consolekit0.4.6-3+b1 amd64framework for defining and tracking users, sessions and seats ii libpam-systemd:amd64 204-5 amd64system and service manager - PAM module ii libsystemd-daemon-dev 204-5 amd64systemd utility library - development files ii libsystemd-daemon0:amd64 204-5 amd64systemd utility library ii libsystemd-id128-0:amd64 204-5 amd64systemd 128 bit ID utility library ii libsystemd-journal0:amd64 204-5 amd64systemd journal utility library ii libsystemd-login-dev 204-5 amd64systemd login utility library - development files ii libsystemd-login0:amd64 204-5 amd64systemd login utility library ii libsystemd-login0:i386204-5 i386 systemd login utility library ii policykit-1 0.112-1 amd64framework for managing administrative policies and privileges ri policykit-1-gnome 0.105-2 amd64GNOME authentication agent for PolicyKit-1 ii python-systemd204-5 amd64python bindings for systemd ii systemd 204-5 amd64system and service manager ii systemd-sysv 204-5 amd64system and service manager - SysV links ii systemd-ui2-2 amd64graphical fronted for systemd # xsession-errors Description: Binary data
Bug#728361: xfce4: No working restart/shutdown buttons
On 11/01/2013 09:48 PM, Yves-Alexis Perez wrote: Can you try to reinstall policykit-1-gnome and see what happens? I tried purging and reinstalling policykit-1-gnome, in both cases nothing happens! Still not working restart/shutdown buttons and very slow login. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728361: xfce4: No working restart/shutdown buttons
Package: lightdm Version: 1.8.3-1 Followup-For: bug #728361 --- System Information: Debian Release: jessie/sid Kernel: Linux 3.12-rc7-amd64 I am using xfce4 (version 4.10.1) and get the same issue, after upgrading lightdm/1.6.3-1 to version 1.8.2-1 and 1.8.3-1 the restart/shutdown buttons no longer work. Downgrading to 1.6.3-1 fixes this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717213: Module::Load::Conditional and taint mode
adding to the bug tracker.
On 9 Sep 2013, at 23:26, Daniel Kahn Gillmor wrote:
It looks like some change introduced between 0.44 and 0.50 cause
Module::Load::Conditional::can_load to choke under taint mode.
I note that both http://bugs.debian.org/722210 and
http://bugs.debian.org/717213 are related to Module::Load::Conditional
failures under taint mode. I suspect they're the same bug.
The versions of Module::Load::Conditional associated here are:
wheezy perl-modules 0.44
wheezy libmodule-load-conditional-perl0.50
sidperl-modules 0.54
sidlibmodule-load-conditional-perl0.52
upstream 0.58
here's a carp trace on a system with 0.58 installed:
0 dkg@alice:/tmp/cdtemp.YOjk3A$ perl -MCarp::Always
-wTMModule::Load::Conditional -e 'Module::Load::Conditional::can_load(modules
= { 'Test' = undef });'
Insecure dependency in eval while running with -T switch at
/usr/share/perl/5.18/Module/Metadata.pm line 631, GEN0 line 23.
Module::Metadata::_evaluate_version_line('Module::Metadata=HASH(0x1063878)',
'$', 'VERSION', '$VERSION = \'1.26\';') called at
/usr/share/perl/5.18/Module/Metadata.pm line 580
Module::Metadata::_parse_fh('Module::Metadata=HASH(0x1063878)',
'FileHandle=GLOB(0x10d3568)') called at
/usr/share/perl/5.18/Module/Metadata.pm line 358
Module::Metadata::_init('Module::Metadata', undef,
'/usr/share/perl/5.18/Test.pm', 'handle', 'FileHandle=GLOB(0x10d3568)')
called at /usr/share/perl/5.18/Module/Metadata.pm line 79
Module::Metadata::new_from_handle('Module::Metadata',
'FileHandle=GLOB(0x10d3568)', '/usr/share/perl/5.18/Test.pm') called at
/usr/share/perl5/Module/Load/Conditional.pm line 259
Module::Load::Conditional::check_install('module', 'Test', 'version',
undef) called at /usr/share/perl5/Module/Load/Conditional.pm line 417
Module::Load::Conditional::can_load('modules', 'HASH(0xd22cb8)') called
at -e line 1
25 dkg@alice:/tmp/cdtemp.YOjk3A$
I note that the upstream changelog only mentions taint mode once, from
years ago:
Changes for 0.24Wed Jan 2 16:53:19 CET 2008
=
* Readdress #29348 to make sure version comparisons
handle alpha versions (XX_YY type) gracefully.
* Address #31680 to make sure $FIND_VERSION works
nicely with taint mode enabled.
Jos, do you have any idea what is going on here, or if it's possible to
run Module::Load::Conditional while under taint mode?
Regards,
--dkg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718843: console-kit-daemon : GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Package: consolekit Version: 0.4.6-2 Severity: normal In rsyslog I get quite a lot of similar errors: console-kit-daemon[2133]: (process:3240): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed. Not only for process 3240 but for many others too. The console-kit-daemon is called by systemd console-kit-daemon.service. - -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Systemd v.204-2 Consolekit Status: install ok installed Depends: libacl1 (= 2.2.51-8), libc6 (= 2.4), libck-connector0 (= 0.4.6-2), libdbus-1-3 (= 1.0.2), libdbus-glib-1-2 (= 0.88), libglib2.0-0 (= 2.31.8), libpolkit-gobject-1-0 (= 0.94), libudev0 (= 154), libx11-6, zlib1g (= 1:1.1.4), dbus (= 1.1.2) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717892: systemd 204: Boot rescue (single) mode hangs
Issue fixed by reinstalling all systemd and udev packages in new /lib/sysemd and /lib/udev directories. The previous upgrade had been done on the existing 44 version. This bug can be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717892: systemd 204: Boot rescue (single) mode hangs
Package: systemd Version: 204-2 Severity: normal After upgrading systemd from v.44 to v.204, attempting to boot systemd in rescue (single) mode results in boot hanging at systemd-fsck:/dev/sda5: clean, 143925/13746176 files,8735537/54956341. System blocks with no further output or disk activity.The system still appears to be running and ctrl-alt-delete triggers a clean reboot. /dev/sda5 and sda6 seem to block booting in rescue mode only, not in multi-user mode. My fstab file: --- /dev/sda1 / ext4errors=remount-ro 0 1 /dev/sda5 /home ext4defaults 0 1 /dev/sda6 swap swapdefaults 0 0 tmpfs /var/log tmpfs defaults,noexec,noatime,mode=0755 0 0 --- I found a work around to make systemd booting in rescue mode by adding 'defaults,comment=systemd.automount' to /dev/sda5 and removing the swap disk from fstab. To get the swap disk working I added /sbin/swapon /dev/sda6 to rc.local. There was no such issue with version 44! -- System Information: Debian Release: Jessie/Sid Architecture: amd64 (x86_64) Kernel: Linux debian 3.10-1-amd64 #1 SMP Debian 3.10.1-1 (2013-07-16) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717892: systemd 204: Boot rescue (single) mode hangs
Could you post the complete kernel command line you used? GRUB_CMDLINE_LINUX_DEFAULT=nothreadirqs quiet logo.nologo splash rootfstype=ext4 transparent_hugepage=always init=/sbin/init /sbin/init points to /lib/systemd/systemd Can you run with debugging enabled [1] and get a full debug log? I'm sorry, I don't know how to enable debugging systemd. Adding 'debug' to the command line, removing 'quiet' and update-grub did not show more info. You should typically use none and sw here. Debian wiki (http://wiki.debian.org/fstab) says /dev/sda5swap swap defaults 0 0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717892: systemd 204: Boot rescue (single) mode hangs
don't see you enabling single mode here? I'm sorry I erroneously showed you the muli-user kernel command, the single mode command is: linux /boot/vmlinuz-3.10-1-amd64 root=UUID=6358264e-67bc-4443-a14d-eb08d628aaae ro single upgrade-from-grub-legacy vga=769 (where root=/dev/sda1). Are you using plymouth or any other type of splash manager? I'm using plymouth with Theme=text but it is not used in single mode. About swap: In fstab I modified the swap entry into /dev/sda6 none swapsw0 0 but it is still blokking single mode. Boot without quiet and withsystemd.log_level=debug systemd.log_target=console I now boot single mode with command linux /boot/vmlinuz-3.10-1-amd64 root=UUID=6358264e-67bc-4443-a14d-eb08d628aaae ro single upgrade-from-grub-legacy vga=769 systemd.log_level=debug systemd.log_target=console This produces a lot of text but I don't find a clue to this issue. Take a screenshot if you can't capture the output otherwise. I can't take a screenshot and don't know how to capure otherwise while the screen is blokked. I tried to get the text into a file by changing the kernel command systemd.log_target=/debug.txt but the file was empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692024: zram module is missing
Package: linux-image-3.6-trunk-amd64 Version: 3.6.4-1~experimental.1 Severity: important zram module is missing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689191: python-libxml2 (v. 2.9.0) undefined symbol
Is this helpful? http://stackoverflow.com/questions/11643666/python-importerror-undefined-symbol- for-custom-c-module Your reference talks about compiling a python module using g++. What I'm doing is building mesa, using 'make'. Compiling mesa with libxml2 v.2.9.0 (exp) and libxml2mod.so v.2.8.0 (sid) in /usr/lib/python2.7/dist-packages/ imports the module and builds without error. This seems to point to an error in libxml2mod.so v.2.9.0 (exp). Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689191: python-libxml2 (v. 2.9.0) undefined symbol
Package: python-libxml2 Version: 2.9.0+dfsg1-2 (experimental) Severity: normal After upgrading python-libxml2 from v.2.8.0+dfsg1-5 (unstable) to v.2.9.0+dfsg1-2 (experimental) building mesa (freedesktop.org git repository) which uses python-libxml2, shows the following error: --- File /usr/lib/python2.7/dist-packages/libxml2.py, line 1, in module import libxml2mod ImportError: /usr/lib/python2.7/dist-packages/libxml2mod.so: undefined symbol: xmlParserError --- System Information: Debian Release: sid Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-4.dmz.1-liquorix-amd64 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688011: fcitx-m17n : no pinyin preedit
I have read your comment about the preedit concept but it doesn't seem to work, at least on my system using xfce4. Choosing input method zh-pinyin (m17n) and for example typing ai1, no underlined text appears. I tried zh-pinyin input in mousepad, gedit and kate editors, no preedit is shown and ctrl+alt+p doesn't open an input window. Trying input in xterm too doesn't open an input window. These are the packages I have installed: fcitx v.4.2.5 from Debian/experimental: fcitx-libs, fcitx-bin, fcitx-data, fcitx-config-common, fcitx-config-gtk, fcitx-frontend-gtk2, fcitx-frontend-gtk3, fcitx-modules (core modules), fcitx-module-dbus,fcitx-module-lua, fcitx-module-x11, fcitx-table, fcitx-tools, fcitx-ui-classic, fcitx-pinyin, fcitx-sunpinyin, fcitx-googlepinyin, fcitx-m17n. Could some package be missing? Using fcitx-pinyin, fcitx-sunpinyin or fcitx-googlepinyin woks, opening an input window but ctrl+alt+p doesn't show preedited text. fcitx-config Description: Binary data
Bug#688011:
The last remark in my previous message was wrong, sorry! Using fcitx-pinyin, fcitx-sunpinyin or fcitx-googlepinyin woks, opening an input window but ctrl+alt+p doesn't show preedited text. should be: Using fcitx-pinyin, fcitx-sunpinyin or fcitx-googlepinyin woks, opening an input window and ctrl+alt+p showing preedited text. Regards, Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688011: fcitx-m17n : no pinyin input window
can it work with fcitx 4.2.4.1? No, same issue, no input window. This issue only occurs with fcitx-m17n, not when using fcitx-pinyin or sunpinyin. I also tried ibus-m17n, here zh-pinyin opens an input window! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688011: fcitx-m17n : no pinyin input window
which ui are you using? KDE, ui-classic, gnome-shell or ui-light? I am using ui-classic with xfce4 (4.10) window manager and panel. Same issue with zh-bopomofo. Fcitx does't work at all with ui-light. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688011: fcitx-m17n : no pinyin input window
Package: fcitx-m17n Version: 0.1.2-1 Severity: normal System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-4.dmz.3-liquorix-amd64 Input method: fcitx version 4.2.5 In package fcitx-m17n the pinyin input methods zh-pinyin, zh-py, zh-tonepy, zh-quick can't be used, they don't show any input window. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687388: libsoup2.4-1: Experimental version breaks midori
Package: libsoup2.4-1 Version: 2.39.90-1 (experimental) System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-3.dmz.3-liquorix-amd64 Midori 0.4.3-1 shows a similar bug: /usr/bin/midori: symbol lookup error: /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1: undefined symbol Also xfce4 screenshot panel plugin no longer attaches to the panel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675816: ledgersmb: Unable to upgrade from 1.2 db to 1.3 db
I am the user who originally reported the failure in the ledger-smb-users mailing list. No, I haven't resolved this issue yet, and I haven't been able to upgrade my databases either. In fact, I upgraded this system to Ubuntu 12.04 and re-installed LedgerSMB from the .deb-files, and I get the same error (apart from the line eval 102 now reading eval 92). After that, all tables have zero rows (and the customer table is missing altogether. Is this normal, btw?) I am using Postgres 9.1 on this system. For the contrib dir, which the page Database Management Console asks for, I enter /usr/share/postgresql/9.1/extension/. I have entered the same path in /etc/ledgersmb/ledgersmb.conf, but when I used the old default, I got the same error. So I'm still stuck. Jos. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572305: linux-image-2.6.33-2-amd64 wlan is not working
Hi Jonathan, Current kernels don't reproduce this problem. The bug can be closed since 2.6.33 is no longer used. Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669949: sysvinit breaks X11: no more mouse and keyboard
Package: sysvinit Version: 2.88dsf-23 I too can confirm this bug. -- System Information: Debian Release: wheezy/sid + experimental Architecture: amd64 Kernel~3.3.0-2.dmz.1-liquorix-amd64 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665459: boinc-client v.7.0.15 Einstein@home S6LV1 tasks all end with computation errors
Package: boinc-client Version: 7.0.15+dfsg-1 Severity: important All Einstein@home S6LV1 tasks end with the same computation error Stderr output: - core_client_version7.0.15/core_client_version ![CDATA[ message process exited with code 2 (0x2, -254) /message stderr_txt sched_setscheduler: Operation not permitted execv: No such file or directory /stderr_txt ]] - According to E@H Message boards : Problems and Bug Reports : S6LV1 tasks all with computation errors: 'This is a Client Problem. The application binary is not made executable after download. This is fixed in 7.0.23. As a workaround you may manually set the execute permission of the einstein* files in the project directory.' http://einstein.phys.uwm.edu/forum_thread.php?id=9355 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665459: boinc-client v.7.0.15 Einstein@home S6LV1 tasks all end with computation errors
Hello, According to Bernd Machenschalk, E@H developer, this is a client problem which is fixed in 7.0.23. Please upgrade the Debian package to the newest version (7.0.15 is pretty old ;-). Cheers, Jos v.W. On 03/24/2012 03:47 PM, Steffen Möller wrote: Hello, I can help. The problem is not with BOINC but with the Einstein folks who apparently have forgotten to set the executable flag for their executables. Or some newer version of BOINC ruins that? No idea. The developers know about it, at least. Please sudo chmod +x /var/lib/boinc-client/projects/einstein*/einstein*S6* This also affects the one or other Mac-running contributor to E@H. Surprisinglyl, all other projects and Win* platforms seem fine. But the latter execute everything ending with .exe, right? Cheers, Steffen On 03/24/2012 01:47 PM, Jos van Wolput wrote: Package: boinc-client Version: 7.0.15+dfsg-1 Severity: important All Einstein@home S6LV1 tasks end with the same computation error Stderr output: - core_client_version7.0.15/core_client_version ![CDATA[ message process exited with code 2 (0x2, -254) /message stderr_txt sched_setscheduler: Operation not permitted execv: No such file or directory /stderr_txt ]] - According to E@H Message boards : Problems and Bug Reports : S6LV1 tasks all with computation errors: 'This is a Client Problem. The application binary is not made executable after download. This is fixed in 7.0.23. As a workaround you may manually set the execute permission of the einstein* files in the project directory.' http://einstein.phys.uwm.edu/forum_thread.php?id=9355 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659838: kmod: v5 acts like a fork bomb
Package: kmod Version: 5-1 System: amd64, kernel 3.2, Debian/Sid + experimental I tried playing midi using kmod 5-1 with all install commented out in /etc/modprobe.d/alsa-base.conf, Timidity worked but pmidi didn't, could not find sequencer, ending with system crash. Jos.v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638165: Gecko-mediaplayer fails to embed in Iceweasel
Hi Sebastian, After some research I have found that this issue is caused by the MediaWrap (v.0.1.7.3) extention. When MediaWrap is disabled Gecko-mediaplayer works correctly. Kind regards, Jos v.W. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658564: daisy-player: Hangs while loading, both from disc and directory.
Hello Erik, I know this bug. I have experienced it myself. I'm busy replacing my own buggy xml-parser by the Mini-XML parser http://www.minixml.org/. I cannot tell when the new version will be available. Regards, Jos. On Sat, Feb 04, 2012 at 06:00:57AM +0100, Erik Sundin wrote: Package: daisy-player Version: 7.0.4.1-1 Severity: important Dear Maintainer, The program hangs with the message Reading ??... displaying in the top left corner directly after startup. Nothing seems to happen after that... This occurs both when running it whitout any arguments (presumably it then attempts to play from /dev/cdrom, though this is not mentioned anywhere (as far as I can tell)) and when a directory is given on the commandline. Unfortunately I only have one book to try it with, but the disk in question works as it should in a physical player which seems to indicate software trouble. I very much hope this can be fixed (since there aren't that many choices for playing daisy books on linux) and will gladly provide any information you may have use of. //Erik Sundin -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages daisy-player depends on: ii libc6 2.13-24 ii libidn11 1.23-2 ii libncursesw5 5.9-4 ii libsox1b 14.3.2-3 ii madplay 0.15.2b-7 ii udisks1.0.4-3 daisy-player recommends no packages. daisy-player suggests no packages. -- no debconf information -- --- Jos Lemmens The Netherlands E-mail: j...@jlemmens.nl Homepage: www.jlemmens.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
