Bug#1051056: transmission-daemon: memory leaks lead to eventual memory exhaustion

2023-09-04 Thread Fufu Fang
This issue has been reported in Github. I think recent versions of
Transmission all have memory leak. 

For version 3.0, I think the first mention is here:
https://github.com/transmission/transmission/issues/3077

The latest bug fix in 4.0.0 branch is here: 
https://github.com/transmission/transmission/pull/5748



Bug#992918: re: gwenview: fails to save jpg/jpeg image

2023-08-27 Thread Fufu Fang
I got home, and followed Ian's suggestion, and removed "*.jfif" from
the top of the list. The problem is now resolved. 



Bug#1031744: httpdirfs: usage of ubsan might introduce vulnerabilities

2023-02-22 Thread Fufu Fang
Hi Adrian,
I have pushed a commit to Github which removes the usage of UBSAN. I am
happy to go with this method. 

Do let me know if you prefer ASAN to be added alongside UBSAN, rather
than simply removing UBSAN.
Best wishes,
Fufu



Bug#1031744: httpdirfs: usage of ubsan might introduce vulnerabilities

2023-02-22 Thread Fufu Fang
Hi Adrian,
I am the author of httpdirfs. Do you reckon I should just remove ubsan,
or should I add asan into the Makefile? I reckon I should just remove
ubsan.
Best wishes,
Fufu
 
On Tue, 2023-02-21 at 21:41 +0200, Adrian Bunk wrote:
> Package: httpdirfs
> Version: 1.2.4-1
> Severity: serious
> Tags: security
> X-Debbugs-Cc: Debian Security Team 
> 
> Package: httpdirfs
> Version: 1.2.4-2
> Depends: ..., libubsan1 (>= 8), ...
> 
> 
> This is a bad idea not only due to slower execution,
> but might even introduce vulnerabilities:
> https://www.openwall.com/lists/oss-security/2016/02/17/9
> 
> While there are safe usages of ubsan, httpdirfs being the
> only package in the archive that uses ubsan but not asan
> is something that sounds wrong and underreviewed.
> 



Bug#992918: gwenview: fails to save jpg/jpeg image

2021-08-29 Thread Fufu Fang
If I installed the libjpeg62-turbo from Debian Buster, the
"automatically select filename
extension (.jfif)" would change into "automatically select filename
(.jpeg)". 

I suspect it is the problem with libjpeg62-turbo.


On Sun, 2021-08-29 at 13:17 +0100, Ian Goddard wrote:
> On Sun, 29 Aug 2021 10:27:30 +0200 Francesco 
> wrote:
> > Package: gwenview
> > Version: 4:21.08.0-1
> > Followup-For: Bug #992918
> > 
> > Dear Maintainer,
> > 
> > *** Reporter, please consider answering these questions, where
> > appropriate ***
> > 
> >    * What led up to the situation?
> >    Maybe a shared QT library bug, not only gwenview is affected
> 
> Kolourpaint is also affected.
> 
> I noticed that for both Gwenview & Kolourpaint when the format JPEG
> is 
> selected on the save menu the file extension is set to .jpe rather
> than 
> .jpeg or .jpg.   Correcting the extension doesn't resolve the problem
> but maybe this is a quirk of the same library.
> 
> Krita is not affected.
> 



Bug#992918: gwenview: fails to save jpg/jpeg image

2021-08-24 Thread Fufu Fang
Package: gwenview
Version: 4:20.12.3-2
Severity: normal

Dear Maintainer,
I opened an image in Gwenview (it can be any format), then I go to the "File"
menu, and click on the "Save As..." menu option. If I select "JPEG image" as
the file type, then press the "Save" button, two modal dialogs pop up.

One dialog has the title "Error -- Gwenview", with the text "Unsupported image
format".

The other dialog has the title "Warning -- Gwenview", with the text "Saving
'x.jpg' failed: Unspported image format". I am offered to save it as
another format.


-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC,
TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gwenview depends on:
ii  kinit  5.78.0-2
ii  kio5.78.0-5
ii  libc6  2.31-13
ii  libcfitsio93.490-3
ii  libexiv2-270.27.3-3+deb11u1
ii  libgcc-s1  10.2.1-6
ii  libjpeg62-turbo1:2.0.6-4
ii  libkf5activities5  5.78.0-2
ii  libkf5baloo5   5.78.0-3
ii  libkf5completion5  5.78.0-3
ii  libkf5configcore5  5.78.0-4
ii  libkf5configgui5   5.78.0-4
ii  libkf5configwidgets5   5.78.0-2
ii  libkf5coreaddons5  5.78.0-4
ii  libkf5filemetadata35.78.0-2
ii  libkf5i18n55.78.0-2
ii  libkf5iconthemes5  5.78.0-2
ii  libkf5itemmodels5  5.78.0-2
ii  libkf5itemviews5   5.78.0-2
ii  libkf5jobwidgets5  5.78.0-2
ii  libkf5kdcraw5  20.12.0-1
ii  libkf5kiocore5 5.78.0-5
ii  libkf5kiofilewidgets5  5.78.0-5
ii  libkf5kiowidgets5  5.78.0-5
ii  libkf5kipi32.0.0   4:20.12.1-1
ii  libkf5notifications5   5.78.0-2
ii  libkf5parts5   5.78.0-3
ii  libkf5purpose-bin  5.78.0-2
ii  libkf5purpose5 5.78.0-2
ii  libkf5service-bin  5.78.0-2
ii  libkf5service5 5.78.0-2
ii  libkf5solid5   5.78.0-2
ii  libkf5widgetsaddons5   5.78.0-2
ii  libkf5xmlgui5  5.78.0-2
ii  liblcms2-2 2.12~rc1-2
ii  libphonon4qt5-44:4.11.1-4
ii  libpng16-161.6.37-3
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5dbus55.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5printsupport55.15.2+dfsg-9
ii  libqt5svg5 5.15.2-3
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libqt5x11extras5   5.15.2-2
ii  libstdc++6 10.2.1-6
ii  libtiff5   4.2.0-1
ii  libx11-6   2:1.7.2-1
ii  perl   5.32.1-4+deb11u1
ii  phonon4qt5 4:4.11.1-4

Versions of packages gwenview recommends:
ii  kamera 4:20.12.0-1
pn  kio-extras 
ii  qt5-image-formats-plugins  5.15.2-2

gwenview suggests no packages.



Bug#888647: (no subject)

2018-09-19 Thread Fufu Fang
I am experiencing the same problem as well. I tried installing 
libpam-cfgs from unstable and Ubuntu, none of them solve my problem.


These is my log:

 lxc-start 20180919144245.625 ERROR    lxc_cgfs - 
cgroups/cgfs.c:lxc_cgroupfs_create:1022 - Permission denied - Could not 
create cgroup '/user.slice/user-1000.slice/session-4197.scope/lxc' in 
'/sys/fs/cgroup/systemd'.
  lxc-start 20180919144245.628 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/devices/user.slice
  lxc-start 20180919144245.631 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/memory/user.slice
  lxc-start 20180919144245.632 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete 
/sys/fs/cgroup/pids/user.slice/user-1000.slice/session-4197.scope
  lxc-start 20180919144245.634 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/blkio/user.slice
  lxc-start 20180919144245.634 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/perf_event//docker
  lxc-start 20180919144245.635 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/perf_event//machine
  lxc-start 20180919144245.635 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/perf_event//lxc
  lxc-start 20180919144245.635 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/perf_event/
  lxc-start 20180919144245.636 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/net_cls,net_prio//docker
  lxc-start 20180919144245.636 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/net_cls,net_prio//machine
  lxc-start 20180919144245.636 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/net_cls,net_prio//lxc
  lxc-start 20180919144245.637 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/net_cls,net_prio/
  lxc-start 20180919144245.637 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//docker
  lxc-start 20180919144245.638 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//user/root/0
  lxc-start 20180919144245.638 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//user/root
  lxc-start 20180919144245.639 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//user/fangfufu/0
  lxc-start 20180919144245.639 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//user/fangfufu
  lxc-start 20180919144245.639 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//user
  lxc-start 20180919144245.640 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//machine
  lxc-start 20180919144245.640 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer//lxc
  lxc-start 20180919144245.640 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/freezer/
  lxc-start 20180919144245.641 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/cpu,cpuacct/user.slice
  lxc-start 20180919144245.641 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/cpuset//docker
  lxc-start 20180919144245.642 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/cpuset//machine
  lxc-start 20180919144245.643 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/cpuset//lxc
  lxc-start 20180919144245.643 ERROR    lxc_cgfs - 
cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: 
failed to delete /sys/fs/cgroup/cpuset/
  lxc-start 

Bug#794419: sddm doesn't source /etc/profile and $HOME/.profile

2015-08-04 Thread Fufu Fang
I am experiencing the same problem. Switching to the old kdm does help. 

-- System Information: Debian Release:
stretch/sid APT prefers
testing APT policy: (500, 'testing'), (500, 'stable'), (1,
'unstable') Architecture: amd64
(x86_64) Foreign Architectures:
i386 
Kernel: Linux 4.0.0-2-amd64 (SMP w/8 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 sddm depends on:
ii  adduser   3.113+nmu3
ii  debconf [debconf-2.0] 1.5.57
ii  libc6 2.19-19
ii  libgcc1   1:5.1.1-14
ii  libpam0g  1.1.8-3.1
ii  libqt5core5a  5.4.2+dfsg-5
ii  libqt5dbus5   5.4.2+dfsg-5
ii  libqt5gui55.4.2+dfsg-5
ii  libqt5network55.4.2+dfsg-5
ii  libqt5qml55.4.2-4
ii  libqt5quick5  5.4.2-4
ii  libstdc++65.1.1-14
ii  libsystemd0   222-2
ii  libxcb-xkb1   1.10-3+b1
ii  libxcb1   1.10-3+b1
ii  qml-module-qtquick2   5.4.2-4
ii  sddm-theme-breeze [sddm-theme]4:5.3.2-4
ii  sddm-theme-circles [sddm-theme]   0.11.0-3
ii  sddm-theme-elarun [sddm-theme]0.11.0-3
ii  sddm-theme-maldives [sddm-theme]  0.11.0-3
ii  sddm-theme-maui [sddm-theme]  0.11.0-3

sddm recommends no packages.

sddm suggests no packages.

-- debconf information:
* shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#793574: systemsettings lost options, what's there working incorrectly

2015-07-26 Thread Fufu Fang
I had the same problem. I am fairly certain the upgrade to
systemsettings caused it. The problem can be temporarily resolved by
downgrading to systemsettings/stable. I am holding the old version for
now. 


On Sat, 25 Jul 2015 10:12:16 +0100 Tony Green
dddeb...@web-brewer.co.uk wrote:
 Package: systemsettings
 Version: 4:5.3.2-2
 Severity: important
 
 Dear Maintainer,
 
* What led up to the situation?
 Installed systemsettings 4:5.3.2-2 as part of routine installing of
 available updates. It appears that systemsettings for KDE5 has been
 installed in place of the correct version as /usr/bin/systemsettings
 has been replaced by /usr/bin/systemsettings5.
 
* What exactly did you do (or not do) that was effective (or
  ineffective)?
 Launched systemsettings from icon.
 
* What was the outcome of this action?
 Only four options showing on systemsettings - Application Style,
 Applications, Network settings, Display  Monitor.
 In addition, these options open incorrect configuration settings:
 Application style - opens Widget style of GNOME/GTK applications.
 Applications - opens Configure file associations
 Network settings - opens SSL Versions  Certificates
 Display  Monitor - crashes systemsettings. The following error
 messages are generated:
 
 ---
 Couldn't start kded5 from org.kde.kded5.service:
 QDBusError(org.freedesktop.DBus.Error.ServiceUnknown, The name
 org.kde.kded5 was not provided by any .service files) , falling back
 to running kbuildsycoca5
 kf5.kservice.sycoca: Trying to open ksycoca from
 /home/tony/.cache/ksycoca5 LOAD
 kscreen: launcherDataAvailable: org.kde.KScreen.Backend.XRandR
 kscreen: Launcher finished with exit code 1 , status 0
 kscreen: Service for requested backend already running
 file:///usr/share/kcm_kscreen/qml/main.qml:20:1: module
 QtQuick.Controls is not installed
  import QtQuick.Controls 1.1 as Controls
  ^
 file:///usr/share/kcm_kscreen/qml/main.qml:21:1: module
 org.kde.plasma.core is not installed
  import org.kde.plasma.core 2.0 as PlasmaCore
  ^
 file:///usr/share/kcm_kscreen/qml/main.qml:22:1: module
 org.kde.kquickcontrols is not installed
  import org.kde.kquickcontrols 2.0
  ^
 file:///usr/share/kcm_kscreen/qml/main.qml:19:1: module QtQuick is
 not installed
  import QtQuick 2.1
  ^
 file:///usr/share/kcm_kscreen/qml/main.qml:20:1: module
 QtQuick.Controls is not installed
  import QtQuick.Controls 1.1 as Controls
  ^
 file:///usr/share/kcm_kscreen/qml/main.qml:21:1: module
 org.kde.plasma.core is not installed
  import org.kde.plasma.core 2.0 as PlasmaCore
  ^


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#790720: (no subject)

2015-07-24 Thread Fufu Fang
Could everyone check what's in their KDE System Settings please? 

I only have 6 buttons left. Virtually everything had gone missing. I
can't eve set my display's resolution. 

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/8 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 plasma-nm depends on:
ii  libc6   2.19-19
ii  libkf5completion5   5.12.0-1
ii  libkf5configcore5   5.12.0-1
ii  libkf5configwidgets55.12.0-1
ii  libkf5coreaddons5   5.12.0-1
ii  libkf5dbusaddons5   5.12.0-1
ii  libkf5i18n5 5.12.0-1
ii  libkf5iconthemes5   5.12.0-1
ii  libkf5itemviews55.12.0-1
ii  libkf5kdelibs4support5  5.12.0-2
ii  libkf5kiowidgets5   5.12.0-1
ii  libkf5modemmanagerqt6   5.12.0-1
ii  libkf5networkmanagerqt6 5.12.0-1
ii  libkf5notifications55.12.0-1
ii  libkf5service5  5.12.0-1
ii  libkf5solid55.12.0-1
ii  libkf5wallet5   5.12.0-1
ii  libkf5widgetsaddons55.12.0-1
ii  libkf5windowsystem5 5.12.0-1
ii  libkf5xmlgui5   5.12.0-1
ii  libopenconnect5 7.06-2
ii  libqt5core5a5.4.2+dfsg-4
ii  libqt5dbus5 5.4.2+dfsg-4
ii  libqt5gui5  5.4.2+dfsg-4
ii  libqt5network5  5.4.2+dfsg-4
ii  libqt5qml5  5.4.2-3
ii  libqt5widgets5  5.4.2+dfsg-4
ii  libqt5xml5  5.4.2+dfsg-4
ii  libstdc++6  5.1.1-14
ii  mobile-broadband-provider-info  20140317-1
ii  network-manager 1.0.2-2

plasma-nm recommends no packages.

Versions of packages plasma-nm suggests:
pn  network-manager-openconnect  none
ii  network-manager-openvpn  1.0.2-1
ii  network-manager-pptp 1.0.2-1
ii  network-manager-vpnc 1.0.2-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#789867: pidgin: Pidgin crashes upton IRC disconnection

2015-06-26 Thread Fufu Fang
This is what happened when I ran the command:

fangfufu@illustrious:~$ pidgin -d  pidgin.log
Pidgin 2.10.11 has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.

If you can reproduce the crash, please notify the developers
by reporting a bug at:
http://developer.pidgin.im/simpleticket/

Please make sure to specify what you were doing at the time
and post the backtrace from the core file.  If you do not know
how to get the backtrace, please read the instructions at
http://developer.pidgin.im/wiki/GetABacktrace
Aborted


I am have attached pidgin.log as in this email. We can figure something
out together if the attachment doesn't get through. This is the first
time I attempt to put an attachment in a bug report. 

On Fri, 26 Jun 2015 15:09:25 +
Ari Pollak a...@debian.org wrote:

 Thanks. One other thing - would you mind running pidgin -d 
 pidginlog.txt, reproducing the bug, and attaching the log file? You
 might want to look through the file first to see if there's any
 personal information that shouldn't be exposed.

(16:17:06) prefs: Reading /home//.purple/prefs.xml
(16:17:06) prefs: Finished reading /home//.purple/prefs.xml
(16:17:06) prefs: Unable to find rename pref for /core/plugins
(16:17:06) prefs: Renaming /core to /purple
(16:17:06) prefs: removing pref /core/plugins/core-plugin_pack-google/domain
(16:17:06) prefs: removing pref /core/plugins/core-plugin_pack-google
(16:17:06) prefs: removing pref /core/plugins
(16:17:06) prefs: removing pref /core
(16:17:06) prefs: purple_prefs_get_path: Unknown pref /pidgin/browsers/command
(16:17:06) dbus: okkk
(16:17:06) plugins: probing /usr/lib/pidgin/sendbutton.so
(16:17:06) plugins: probing /usr/lib/pidgin/lastseen.so
(16:17:06) plugins: probing /usr/lib/pidgin/album.so
(16:17:06) plugins: probing /usr/lib/pidgin/libextprefs.so
(16:17:06) plugins: probing /usr/lib/pidgin/xmppconsole.so
(16:17:06) plugins: probing /usr/lib/pidgin/listlog.so
(16:17:06) plugins: probing /usr/lib/pidgin/cap.so
(16:17:06) plugins: probing /usr/lib/pidgin/convcolors.so
(16:17:06) plugins: probing /usr/lib/pidgin/history.so
(16:17:06) plugins: probing /usr/lib/pidgin/blistops.so
(16:17:06) plugins: probing /usr/lib/pidgin/gRIM.so
(16:17:06) plugins: probing /usr/lib/pidgin/irssi.so
(16:17:06) plugins: probing /usr/lib/pidgin/plonkers.so
(16:17:06) plugins: probing /usr/lib/pidgin/difftopic.so
(16:17:06) plugins: probing /usr/lib/pidgin/gtkbuddynote.so
(16:17:06) plugins: probing /usr/lib/pidgin/infopane.so
(16:17:06) plugins: probing /usr/lib/pidgin/convbadger.so
(16:17:06) plugins: probing /usr/lib/pidgin/markerline.so
(16:17:06) plugins: probing /usr/lib/pidgin/musicmessaging.so
(16:17:06) plugins: probing /usr/lib/pidgin/notify.so
(16:17:06) plugins: probing /usr/lib/pidgin/switchspell.so
(16:17:06) plugins: probing /usr/lib/pidgin/themeedit.so
(16:17:06) plugins: probing /usr/lib/pidgin/pidginrc.so
(16:17:06) plugins: probing /usr/lib/pidgin/ticker.so
(16:17:06) plugins: probing /usr/lib/pidgin/xchat-chats.so
(16:17:06) plugins: probing /usr/lib/pidgin/timestamp_format.so
(16:17:06) plugins: probing /usr/lib/pidgin/icon_override.so
(16:17:06) plugins: probing /usr/lib/pidgin/timelog.so
(16:17:06) plugins: probing /usr/lib/pidgin/pidgin-schedule.so
(16:17:06) plugins: probing /usr/lib/pidgin/iconaway.so
(16:17:06) plugins: probing /usr/lib/pidgin/mystatusbox.so
(16:17:06) plugins: probing /usr/lib/pidgin/spellchk.so
(16:17:06) plugins: probing /usr/lib/pidgin/gestures.so
(16:17:06) plugins: probing /usr/lib/pidgin/enhancedhist.so
(16:17:06) plugins: probing /usr/lib/pidgin/pidgin-otr.so
(16:17:06) plugins: probing /usr/lib/pidgin/sepandtab.so
(16:17:06) plugins: probing /usr/lib/pidgin/nicksaid.so
(16:17:06) plugins: probing /usr/lib/pidgin/xmppdisco.so
(16:17:06) plugins: probing /usr/lib/pidgin/timestamp.so
(16:17:06) plugins: probing /usr/lib/pidgin/extplacement.so
(16:17:06) plugins: probing /usr/lib/pidgin/vvconfig.so
(16:17:06) plugins: probing /usr/lib/purple-2/joinpart.so
(16:17:06) plugins: probing /usr/lib/purple-2/listhandler.so
(16:17:06) plugins: probing /usr/lib/purple-2/libirc.so
(16:17:06) plugins: probing /usr/lib/purple-2/libicq.so
(16:17:06) plugins: probing /usr/lib/purple-2/autoaccept.so
(16:17:06) plugins: probing /usr/lib/purple-2/splitter.so
(16:17:06) plugins: probing /usr/lib/purple-2/napster.so
(16:17:06) plugins: probing /usr/lib/purple-2/irchelper.so
(16:17:06) plugins: probing /usr/lib/purple-2/dbus-example.so
(16:17:06) plugins: probing /usr/lib/purple-2/ignore.so
(16:17:06) plugins: probing /usr/lib/purple-2/flip.so
(16:17:06) plugins: probing /usr/lib/purple-2/tcl.so
(16:17:06) plugins: probing /usr/lib/purple-2/liboscar.so
(16:17:06) plugins: /usr/lib/purple-2/liboscar.so is not usable because the 'purple_init_plugin' symbol 

Bug#789867: pidgin: Pidgin crashes upton IRC disconnection

2015-06-25 Thread Fufu Fang
There you go, the new backtrace:

Program received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x8006f) at malloc.c:2929
2929malloc.c: No such file or directory.
(gdb) bt
#0  __GI___libc_free (mem=0x8006f) at malloc.c:2929
#1  0x7558c86b in g_string_free ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2  0x7fffe6a4cda9 in
irc_close (gc=0x563d1520)
at /tmp/buildd/pidgin-2.10.11/./libpurple/protocols/irc/irc.c:529 #3
0x75240ec6 in _purple_connection_destroy (gc=0x563d1520)
at /tmp/buildd/pidgin-2.10.11/./libpurple/connection.c:275 #4
0x7522c99b in purple_account_disconnect
(account=0x5595f970)
at /tmp/buildd/pidgin-2.10.11/./libpurple/account.c:1343 #5
0x555ad673 in pidgin_connection_network_disconnected ()
at /tmp/buildd/pidgin-2.10.11/./pidgin/gtkconn.c:200 #6
0x7050670c in ?? ()
from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 #7
0x758412d5 in g_closure_invoke ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8
0x7585303c in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9
0x7585b698 in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10
0x7585b8ff in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11
0x70507052 in ?? ()
from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 #12
0x77ba31d1 in dbus_connection_dispatch ()
from /lib/x86_64-linux-gnu/libdbus-1.so.3 #13 0x70500db5 in ??
() from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 #14
0x7556bc3d in g_main_context_dispatch ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7556bf20
in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16
0x7556c242 in g_main_loop_run ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x768165d7 in
IA__gtk_main () at /tmp/buildd/gtk+2.0-2.24.28/gtk/gtkmain.c:1268 #18
0x5558f557 in main (argc=1, argv=0x7fffdf98)
at /tmp/buildd/pidgin-2.10.11/./pidgin/gtkmain.c:937 (gdb)

On Fri, 26 Jun 2015 02:03:06 +
Ari Pollak a...@debian.org wrote:

 Would you mind sending a new backtrace after installing the pidgin-dbg
 package?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#789867: pidgin: Pidgin crashes upton IRC disconnection

2015-06-24 Thread Fufu Fang
Package: pidgin
Version: 2.10.11-1
Severity: important

Dear Maintainer,

I use Pidgin's IRC feature. Occasionally when the network disconnects, Pidgin
crashes. This bug can be easily reproduced by running Pidgin, signing in an IRC
account, and send the computer to sleep. Pidgin is guaranteed to crash upon
resuming.

I have produced a backtrace, the problem seems to be related an excess free()
call. Below is the backtrace:

*** Error in `/usr/bin/pidgin': free(): invalid pointer: 0x55a0a0e0 ***

Program received signal SIGABRT, Aborted.
0x74955107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x74955107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x749564e8 in __GI_abort () at abort.c:89
#2  0x74993204 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x74a85fe0 *** Error in `%s': %s: 0x%s ***\n) at
../sysdeps/posix/libc_fatal.c:175
#3  0x749989de in malloc_printerr (action=1, str=0x74a8209e
free(): invalid pointer,
ptr=optimized out) at malloc.c:4996
#4  0x749996e6 in _int_free (av=optimized out, p=optimized out,
have_lock=0) at malloc.c:3840
#5  0x7558c86b in g_string_free () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#6  0x7fffe6a4cda9 in ?? () from /usr/lib/purple-2/libirc.so
#7  0x75240ec6 in _purple_connection_destroy () from
/usr/lib/libpurple.so.0
#8  0x7522c99b in purple_account_disconnect () from
/usr/lib/libpurple.so.0
#9  0x555ad673 in ?? ()
#10 0x7050670c in ?? () from /usr/lib/x86_64-linux-gnu/libdbus-
glib-1.so.2
#11 0x758412d5 in g_closure_invoke () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#12 0x7585303c in ?? () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#13 0x7585b698 in g_signal_emit_valist () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#14 0x7585b8ff in g_signal_emit () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#15 0x70507052 in ?? () from /usr/lib/x86_64-linux-gnu/libdbus-
glib-1.so.2
#16 0x77ba31d1 in dbus_connection_dispatch () from /lib/x86_64-linux-
gnu/libdbus-1.so.3
#17 0x70500db5 in ?? () from /usr/lib/x86_64-linux-gnu/libdbus-
glib-1.so.2
#18 0x7556bc3d in g_main_context_dispatch () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#19 0x7556bf20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7556c242 in g_main_loop_run () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#21 0x768165d7 in IA__gtk_main () at
/tmp/buildd/gtk+2.0-2.24.28/gtk/gtkmain.c:1268
#22 0x5558f557 in main ()
(gdb)

Thanks,
Fufu



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (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 pidgin depends on:
ii  gconf2  3.2.6-3
ii  libatk1.0-0 2.16.0-2
ii  libc6   2.19-18
ii  libcairo2   1.14.2-2
ii  libdbus-1-3 1.8.18-1
ii  libdbus-glib-1-20.102-1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-4
ii  libgadu31:1.12.0-5
ii  libgdk-pixbuf2.0-0  2.31.4-2
ii  libglib2.0-02.44.1-1
ii  libgstreamer0.10-0  0.10.36-1.5
ii  libgtk2.0-0 2.24.28-1
ii  libgtkspell02.0.16-1.1
ii  libice6 2:1.0.9-1+b1
ii  libpango-1.0-0  1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libpangoft2-1.0-0   1.36.8-3
ii  libpurple0  2.10.11-1
ii  libsm6  2:1.2.2-1+b1
ii  libx11-62:1.6.3-1
ii  libxml2 2.9.1+dfsg1-5
ii  libxss1 1:1.2.2-1
ii  perl-base [perlapi-5.20.1]  5.20.2-6
ii  pidgin-data 2.10.11-1

Versions of packages pidgin recommends:
ii  gstreamer0.10-alsa  0.10.36-2
ii  gstreamer0.10-ffmpeg1:0.10.13-dmo2
ii  gstreamer0.10-plugins-base  0.10.36-2
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4+b1

Versions of packages pidgin suggests:
ii  libsqlite3-0  3.8.10.2-1


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#770982: libwebcam0-dev: dynctrl-logitech.h is missing in libwebcam0-dev

2014-11-25 Thread Fufu Fang
Package: libwebcam0-dev
Version: 0.2.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
I needed to include webcam.h, however during the compilation, the following
error occured:
---
/usr/include/webcam.h:32:30: fatal error: dynctrl-logitech.h: No such file or
directory
 #include dynctrl-logitech.h
  ^
compilation terminated.
---

A quick search using apt-file shows that no debian package contains that
particular header file. This bug is quite bad, as anything that include
webcam.h cannot be compiled.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (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

Versions of packages libwebcam0-dev depends on:
ii  libwebcam0  0.2.4-1

libwebcam0-dev recommends no packages.

libwebcam0-dev suggests no packages.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#770982: libwebcam0-dev: dynctrl-logitech.h is missing in libwebcam0-dev

2014-11-25 Thread Fufu Fang
Hi,
A temporary fix is indeed copying the header file from the source to
/usr/local/include.

However I haven't got much clue on Debian's package process. Are there
any pointers to help me get started? I suppose I can submit a patch or
something.

Best wishes,
Fufu

On 25/11/14 20:19, Juhani Numminen wrote:
 Hi,

 http://sources.debian.net/src/libwebcam/0.2.4-1/common/include/
 Folder: include
   .. (parent)
   dynctrl-logitech.h
   webcam.h
 Quickly checking using sources.debian.net shows that the file
 dynctrl-logitech.h is included in the source package. I think this bug
 might be easily fixable just by modifying debian/libwebcam0-dev.install.

 Cheers,
 Juhani

 PS. Sorry for not actually fixing an RC bug, but maybe providing
 additional info will speed up someone else’s job.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#754450: acpi-support: laptop backlight is not dimmed when unplugging power

2014-10-04 Thread Fufu Fang
Hi,
I experienced the same issue. I temporarily fixed it by replacing
/etc/acpi/power.sh with the following content:
#!/bin/sh

test -f /usr/share/acpi-support/key-constants || exit 0

. /usr/share/acpi-support/power-funcs
. /usr/share/acpi-support/policy-funcs

#if [ -z $* ]  { CheckPolicy || CheckUPowerPolicy; }; then
#exit;
#fi

pm-powersave $(on_ac_power)
Cheers,
Fufu

On Fri, 11 Jul 2014 10:27:27 +0200 Nicolas =?utf-8?Q?=C3=89vrard?=
ni...@no-log.org wrote:
 Package: acpi-support
 Version: 0.142-1
 Severity: normal

 Dear Maintainer,

 I notice that since I switched to systemd my laptop do not dim the
 backlight when unplugging the power cord.

 According to me this is due to two things:

 - acpid wrongly calls power.sh without argument (I had to install
 consolekit for power.sh to be called because it uses
 ck-list-sessions, that's maybe another bug).

 - the test CheckPolicy checks for HasLogindAndSystemd1Manager but
 if I am not mistaken systemd does not handle battery events.

 Thus power.sh exits and pm-powersave is never called.

 Thank you for your time!


 -- System Information:
 Debian Release: jessie/sid
 APT prefers unstable
 APT policy: (500, 'unstable'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386

 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

 Versions of packages acpi-support depends on:
 ii acpi-support-base 0.142-1
 ii acpid 1:2.0.22-2
 ii lsb-base 4.1+Debian13
 ii pm-utils 1.4.1-15
 ii x11-xserver-utils 7.7+2

 Versions of packages acpi-support recommends:
 ii acpi-fakekey 0.142-1
 pn rfkill none

 Versions of packages acpi-support suggests:
 pn radeontool none
 ii vbetool 1.1-3
 ii xautolock 1:2.2-4
 pn xinput none
 ii xtrlock 2.6

 -- Configuration Files:
 /etc/default/acpi-support changed:
 ACPI_SLEEP=true
 ACPI_HIBERNATE=true
 LOCK_SCREEN=true
 LID_SLEEP=true
 DISPLAY_DPMS=xset
 XRANDR_OUTPUT=LVDS


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#757733: 答复: Bug#757733: RTS2557 SD card reader does not work

2014-09-21 Thread Fufu Fang
Hi Wei,
I am affected by this bug too.

I patched the kernel source, recompiled the modules in drivers/mfd, and
it gives the following message when I run dmesg:

[ 3940.436153] rtsx_pci :03:00.0: irq 50 for MSI/MSI-X
[ 3940.436185] rtsx_pci :03:00.0: rtsx_pci_acquire_irq: pcr-msi_en
= 1, pci-irq = 50
[ 3940.535119] rtsx_pci :03:00.0: rtsx_pci_init_hw error: optimize phy
[ 3940.535264] rtsx_pci: probe of :03:00.0 failed with error -110

Cheers,
Fufu

On Mon, 11 Aug 2014 06:45:24 + =?utf-8?B?546L54Kc?=
wei_w...@realsil.com.cn wrote:

  -邮件原件-
  发件人: Philipp Hagemeister [mailto:phi...@phihag.de]
  发送时间: 2014年8月11日 9:10
  收件人: Ben Hutchings; 王炜
  抄送: 757...@bugs.debian.org; LKML
  主题: Re: Bug#757733: RTS2557 SD card reader does not work
 
   A web search shows some similar reports (e.g.
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329566,
  
  http://askubuntu.com/questions/473848/ubuntu-14-04-realtek-semiconducto
  r-co-ltd-rts5227-pci-express-card-reader-isn).
   But in that last one, it turns out that the out-of-tree driver does
   work.
 
  Indeed, that is a workaround - download from
  http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PNid=
  15PFid=25Level=4Conn=3DownTypeID=3GetDown=false
  , apply the attached patch, remove all rtsx_* modules, and insert
the new
  rts2557 module into the kernel.


 Hi Philipp  Ben:

 Would you please try this patch. If it does work, we will submit it to
upstream kernel.

 BR,
 Wei


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#758543: fixed in libdvdnav 5.0.1-1

2014-08-31 Thread Fufu Fang
Dear Maintainer,
The problem is still there. I have upgraded to 5.0.1-1, I still can't
run mplayer. The error message is still the same. I checked the file
list (https://packages.debian.org/sid/amd64/libdvdnav4/filelist),
libdvdnavmini.so.4 is not in the file list.
Cheers,
Fufu

On Sat, 30 Aug 2014 21:06:10 + Benjamin Drung bdr...@debian.org wrote:
 Source: libdvdnav
 Source-Version: 5.0.1-1

 We believe that the bug you reported is fixed in the latest version of
 libdvdnav, which is due to be installed in the Debian FTP archive.

 A summary of the changes between this version and the previous one is
 attached.

 Thank you for reporting the bug, which will now be closed. If you
 have further comments please address them to 758...@bugs.debian.org,
 and the maintainer will reopen the bug report if appropriate.

 Debian distribution maintenance software
 pp.
 Benjamin Drung bdr...@debian.org (supplier of updated libdvdnav package)

 (This message was generated automatically at their request; if you
 believe that there is a problem with it please contact the archive
 administrators by mailing ftpmas...@ftp-master.debian.org)


 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 Format: 1.8
 Date: Sat, 30 Aug 2014 22:38:37 +0200
 Source: libdvdnav
 Binary: libdvdnav4 libdvdnav-dbg libdvdnav-dev libdvdnav-doc
 Architecture: source amd64 all
 Version: 5.0.1-1
 Distribution: unstable
 Urgency: medium
 Maintainer: Debian Multimedia Maintainers
pkg-multimedia-maintain...@lists.alioth.debian.org
 Changed-By: Benjamin Drung bdr...@debian.org
 Description:
 libdvdnav-dbg - DVD navigation library (debug)
 libdvdnav-dev - DVD navigation library (development)
 libdvdnav-doc - DVD navigation library (documentation)
 libdvdnav4 - DVD navigation library
 Closes: 758543 759866
 Changes:
 libdvdnav (5.0.1-1) unstable; urgency=medium
 .
 [ Benjamin Drung ]
 * New upstream release (Closes: #759866)
 * Update debian/watch to point to VideoLAN (and check signature)
 * Update lintian override
 * Put documentation into /usr/share/doc/libdvdnav-doc
 * Disable silent rules (to get verbose build output)
 * Do not ship the upstream COPYING file
 .
 [ Stuart Prescott ]
 * Break old mplayer mencoder packages. (Closes: #758543)
 Checksums-Sha1:
 dfa3865a55013f9d4e75bd1ee76b21c514013898 2272 libdvdnav_5.0.1-1.dsc
 9c234fc1a11f760c90cc278b702b1e41fc418b7e 354568
libdvdnav_5.0.1.orig.tar.bz2
 6086216ab2dcff131e18c9d97ae966e97a37e5d4 7892
libdvdnav_5.0.1-1.debian.tar.xz
 24e81a35079089d85a0534d4d318a0ae797dacaa 43450
libdvdnav4_5.0.1-1_amd64.deb
 c00f82348159e473217c5aa1278502ccad7b8492 123046
libdvdnav-dbg_5.0.1-1_amd64.deb



Bug#758543: fixed in libdvdnav 5.0.1-1

2014-08-31 Thread Fufu Fang
I installed the unstable version of mplayer, now the problem has 
resolved. It was my bad. Sorry.
Fufu

On Sun 31 Aug 2014 14:40:09 BST, Reinhard Tartler wrote:
 On Sun, Aug 31, 2014 at 6:38 AM, Fufu Fang fangfufu2...@gmail.com wrote:
 Dear Maintainer,
 The problem is still there. I have upgraded to 5.0.1-1, I still can't run
 mplayer. The error message is still the same. I checked the file list
 (https://packages.debian.org/sid/amd64/libdvdnav4/filelist),
 libdvdnavmini.so.4 is not in the file list.

 What exact version of the mplayer package do you have installed?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742239: Transmission-daemon segfault due to libgnutls.so

2014-04-03 Thread Fufu Fang
Hi,
I purged my transmission-daemon, re-installed it, reverted the 
configuration file back to the one I used before purging. It magically 
worked. The daemon no longer segfaults. I am not entirely sure why...

I suppose you could close this bug? I don't think my experience could 
benefit anyone else. I am totally clueless why the daemon works with 
the same settings after purging and re-installing.

P.S. I am not sure who I should CC this email to. So I am just CC-ing 
it to the address you CC-ed to.
Regards,
Fufu


On Thu 03 Apr 2014 21:29:22 BST, Markus Koschany wrote:
 Hi,

 (please keep the bug report CC'ed so that others get a chance to help too)

 On 03.04.2014 16:15, Fufu Fang wrote:
 Hi,
 It appears that I don't have systemd installed. That particular machine
 is also on Debian testing. Somehow systemd wasn't installed along side
 the updates.

 # systemctl status transmission-daemon.service
 The program 'systemctl' is currently not installed.  You can install it
 by typing:
 apt-get install systemd
 systemctl: command not found

 Thanks. That means this bug is distinct from the other release critical RC 
 bug.

 https://bugs.debian.org/718624

 I tried giving debian-transmission a home folder by doing this:
 usermod -d /var/lib/transmission-daemon/downloads/ debian-transmission

 It still crashes.

 Alright. That's indeed a little bit odd. Your backtrace indicated that there 
 might
 be something wrong with reading the contents of a directory or file 
 permissions.
 It did not show any sign that the segfault is related to libgnutls.so.

 However there are other bug reports that mention segfaults due to 
 libgnutls.so.

 https://bugs.debian.org/734211

 or another similar bug report

 https://bugs.debian.org/740949

 They all claim that setting

 speed-limit-down-enabled: true

 in the configuration file would cause the segmentation faults but not if set 
 to
 false.

 Your case seems to be different because you had set the value to false 
 according to your
 initial report.

 Now you could still try to purge transmission-daemon and all other 
 transmission packages from your
 system and also clean all configuration files. Then reinstall the packages 
 again and try to
 reproduce the crash but this time try to get a backtrace with bt full. 
 Perhaps this helps to find
 an answer.


 Regards,

 Markus







-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742239: Transmission-daemon segfault due to libgnutls.so

2014-03-20 Thread Fufu Fang
Package: transmission-daemon
Version: 2.82-1.1
Severity: grave

Dear Maintainer,

My transmission-daemon keeps crashing after recent system upgrade. It
started crashing since a couple days ago. I suspect it is related to the
recent GnuTLS update.

Here is the procedure that result in the crash:

$ sudo /etc/init.d/transmission-daemon start
[ ok ] Starting bittorrent daemon: transmission-daemon.

After about 1 second, transmission-daemon crashes, producing the
following message in the kernel log.

$ dmesg | tail -1
[47974.672753] transmission-da[31521]: segfault at 0 ip 7f4468a12689
sp 7f4465942970 error 4 in libgnutls.so.26.22.6[7f446899b000+b9000]

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13-1-amd64 (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

Versions of packages transmission-daemon depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.18
ii  libc62.18-4
ii  libcurl3-gnutls  7.35.0-1
ii  libevent-2.0-5   2.0.21-stable-1
ii  libminiupnpc81.6-3
ii  libnatpmp1   20110808-3
ii  libssl1.0.0  1.0.1f-1
ii  libsystemd-daemon0   204-7
ii  lsb-base 4.1+Debian12
ii  transmission-common  2.82-1.1
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages transmission-daemon recommends:
ii  transmission-cli  2.82-1.1

transmission-daemon suggests no packages.

-- Configuration Files:
/etc/transmission-daemon/settings.json changed:
{
alt-speed-down: 50,
alt-speed-enabled: false,
alt-speed-time-begin: 540,
alt-speed-time-day: 127,
alt-speed-time-enabled: false,
alt-speed-time-end: 1020,
alt-speed-up: 50,
bind-address-ipv4: 0.0.0.0,
bind-address-ipv6: ::,
blocklist-enabled: true,
blocklist-url: ,
cache-size-mb: 256,
dht-enabled: true,
download-dir: /var/lib/transmission-daemon/downloads,
download-limit: 100,
download-limit-enabled: 0,
download-queue-enabled: true,
download-queue-size: 5,
encryption: 2,
idle-seeding-limit: 1440,
idle-seeding-limit-enabled: true,
incomplete-dir: /root/Downloads,
incomplete-dir-enabled: false,
lpd-enabled: true,
max-peers-global: 200,
message-level: 2,
peer-congestion-algorithm: ,
peer-id-ttl-hours: 6,
peer-limit-global: 300,
peer-limit-per-torrent: 50,
peer-port: 60248,
peer-port-random-high: 65535,
peer-port-random-low: 49152,
peer-port-random-on-start: true,
peer-socket-tos: default,
pex-enabled: true,
port-forwarding-enabled: false,
preallocation: 1,
prefetch-enabled: 1,
queue-stalled-enabled: true,
queue-stalled-minutes: 10,
ratio-limit: 3,
ratio-limit-enabled: true,
rename-partial-files: true,
rpc-authentication-required: false,
rpc-bind-address: 0.0.0.0,
rpc-enabled: true,
rpc-password: ,
rpc-port: 9091,
rpc-url: /transmission/,
rpc-username: transmission,
rpc-whitelist: ,
rpc-whitelist-enabled: true,
scrape-paused-torrents-enabled: true,
script-torrent-done-enabled: false,
script-torrent-done-filename: ,
seed-queue-enabled: true,
seed-queue-size: 5,
speed-limit-down: 100,
speed-limit-down-enabled: false,
speed-limit-up: 100,
speed-limit-up-enabled: false,
start-added-torrents: true,
trash-original-torrent-files: false,
umask: 18,
upload-limit: 100,
upload-limit-enabled: 0,
upload-slots-per-torrent: 14,
utp-enabled: true
}


-- no debconf information