Bug#932086: Missing drivers indroduced after Linux 5
A lot of device drivers introduced after Linux 5 is not built in 5.2.9-2, including > # CONFIG_MISC_ALCOR_PCI is not set > # CONFIG_USB_NET_AQC111 is not set I wish much newly introduced drivers could be built along with the new upstream kernel release, or is there any policy preventing these new drivers being enabled?
Bug#922608: Info received (Bug#922608: Acknowledgement (modem-manager-gui aborts to start after modemmanager is upgraded to 1.10.0-1))
This bug has already been reported to upstream via https://linuxonly.ru/forum/modem-manager-gui/57/cannot-load-modem-manager-gui-arch-linux-lts-i3wm/#post-241
Bug#922608: Acknowledgement (modem-manager-gui aborts to start after modemmanager is upgraded to 1.10.0-1)
With further examination, I notice that this bug only occurs when a
modem with 3gpp location capability is installed, and locate the bug at
src/modules/mm07.c (the same bug also exist in mm06.c). If (the context
could be located with the attached patch) the modem has 3gpp location
capability (otherwise, locationstring is NULL and the bug is not
triggered), locationstring will be a g_free()able pointer returned by
g_strdep(), but strsep() modifies its value, effectively making
locationstring never a g_free()able pointer anymore, and g_free()ing it
causes the program aborted.
This bug should be fixed with the attached patch.
diff -Nrup modem-manager-gui-0.0.19.1/src/modules/mm06.c modem-manager-gui-0.0.19.1.fix/src/modules/mm06.c
--- modem-manager-gui-0.0.19.1/src/modules/mm06.c 2018-04-06 22:43:09.0 +0800
+++ modem-manager-gui-0.0.19.1.fix/src/modules/mm06.c 2019-02-19 10:56:32.419076874 +0800
@@ -1581,10 +1581,11 @@ static gboolean mmgui_module_devices_upd
//3GPP location
strlength = 256;
locationstring = g_strdup(g_variant_get_string(locationdata, &strlength));
-device->loc3gppdata[0] = (guint)strtol(strsep(&locationstring, ","), NULL, 10);
-device->loc3gppdata[1] = (guint)strtol(strsep(&locationstring, ","), NULL, 10);
-device->loc3gppdata[2] = (guint)strtol(strsep(&locationstring, ","), NULL, 16);
-device->loc3gppdata[3] = (guint)strtol(strsep(&locationstring, ","), NULL, 16);
+gchar* finger = locationstring;
+device->loc3gppdata[0] = (guint)strtol(strsep(&finger, ","), NULL, 10);
+device->loc3gppdata[1] = (guint)strtol(strsep(&finger, ","), NULL, 10);
+device->loc3gppdata[2] = (guint)strtol(strsep(&finger, ","), NULL, 16);
+device->loc3gppdata[3] = (guint)strtol(strsep(&finger, ","), NULL, 16);
g_free(locationstring);
g_variant_unref(locationdata);
g_debug("3GPP location: %u, %u, %4x, %4x", device->loc3gppdata[0], device->loc3gppdata[1], device->loc3gppdata[2], device->loc3gppdata[3]);
diff -Nrup modem-manager-gui-0.0.19.1/src/modules/mm07.c modem-manager-gui-0.0.19.1.fix/src/modules/mm07.c
--- modem-manager-gui-0.0.19.1/src/modules/mm07.c 2018-04-06 22:43:09.0 +0800
+++ modem-manager-gui-0.0.19.1.fix/src/modules/mm07.c 2019-02-19 10:56:32.419076874 +0800
@@ -1685,10 +1685,11 @@ static gboolean mmgui_module_devices_upd
/*3GPP location*/
strlength = 256;
locationstring = g_strdup(g_variant_get_string(locationdata, &strlength));
-device->loc3gppdata[0] = (guint)strtol(strsep(&locationstring, ","), NULL, 10);
-device->loc3gppdata[1] = (guint)strtol(strsep(&locationstring, ","), NULL, 10);
-device->loc3gppdata[2] = (guint)strtol(strsep(&locationstring, ","), NULL, 16);
-device->loc3gppdata[3] = (guint)strtol(strsep(&locationstring, ","), NULL, 16);
+gchar *finger = locationstring;
+device->loc3gppdata[0] = (guint)strtol(strsep(&finger, ","), NULL, 10);
+device->loc3gppdata[1] = (guint)strtol(strsep(&finger, ","), NULL, 10);
+device->loc3gppdata[2] = (guint)strtol(strsep(&finger, ","), NULL, 16);
+device->loc3gppdata[3] = (guint)strtol(strsep(&finger, ","), NULL, 16);
g_free(locationstring);
g_variant_unref(locationdata);
g_debug("3GPP location: %u, %u, %4x, %4x\n", device->loc3gppdata[0], device->loc3gppdata[1], device->loc3gppdata[2], device->loc3gppdata[3]);
Bug#922608: modem-manager-gui aborts to start after modemmanager is upgraded to 1.10.0-1
Package: modem-manager-gui Version: 0.0.19.1-1+b1 Severity: important Dear Maintainer, modem-manager-gui used to work fine in my box, but after modemmanager is upgraded to 1.10.0-1 today, modem-manager-gui becomes unable to start. If I launch it from command line (with ulimit -c unlimited), it abort()s with the following output: > Connection manager: Network Manager >= 0.9.0 > Modem manager: Modem Manager >= 0.7.0 > free(): invalid pointer > Aborted (core dumped) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages modem-manager-gui depends on: ii libappindicator3-1 0.4.92-7 ii libc6 2.28-6 ii libcairo2 1.16.0-2 ii libgdbm61.18.1-2 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7 ii libglib2.0-02.58.3-1 ii libgtk-3-0 3.24.5-1 ii libgtkspell3-3-03.0.9-3 ii mobile-broadband-provider-info 20170903-1 ii modemmanager1.10.0-1 ii network-manager 1.14.4-4 ii policykit-1 0.105-25 ii ppp 2.4.7-2+4 Versions of packages modem-manager-gui recommends: ii modem-manager-gui-help 0.0.19.1-1 ii yelp3.31.90-1 Versions of packages modem-manager-gui suggests: ii evolution-data-server 3.30.5-1 ii libindicate5 0.6.92-6 ii libnotify4 0.7.7-4 -- no debconf information
Bug#834697: Acknowledgement (modem-manager-gui gets stalled when closing due to connection to akonadi server.)
In order to evade such problem, I removed akonadi-server, which I seldom use, and now modem-manager-gui shuts down properly.
Bug#834697: Acknowledgement (modem-manager-gui gets stalled when closing due to connection to akonadi server.)
In order to evade such problem, I removed akonadi-server, which I seldom use. 在 2016年08月18日 13:39, Debian Bug Tracking System 写道: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Graham Inggs > > If you wish to submit further information on this problem, please > send it to 834...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. >
Bug#817260: Wish: Replace virtualbox's guest BIOS with Coreboot
Hi, Then I may have to choose letting the idea die, for MIT cannot protect our freedom. Anyway, we already have qemu... 在 2016年03月11日 21:40, Gianfranco Costamagna 写道: Hi, I cannot put it under MIT license if I start to work, because Coreboot uses GPL. if you can't comply with Oracle License agreement or MIT [1] [2] I'm not sure it can be released in Debian as-is... cheers, G. [1] https://www.virtualbox.org/wiki/Contributor_information [2] https://www.virtualbox.org/wiki/ICA
Bug#817260: Wish: Replace virtualbox's guest BIOS with Coreboot
Hi, I cannot put it under MIT license if I start to work, because Coreboot uses GPL. persmule 在 2016年03月11日 21:24, Gianfranco Costamagna 写道: Hi, if you can provide one, I'll be happy to forward it upstream. Just a few notes: please put it under MIT license, and please sync with Oracle developers, to know how and if they are interested in it. I would really like to avoid having such an huge difference between Debian and Upstream, such patches are too difficult to debug and maintain downstream. I hope you agree, and if you can upstream a more Open Source friendly BIOS, thumbs up! cheers, G.
Bug#817260: Wish: Replace virtualbox's guest BIOS with Coreboot
Hi, Because the toolchain to build the bios is non-free, which causes the whole virtualbox is unable to put in main repository. So it may be helpful to use a bios implementation which can be build by a free toolchain. persmule 在 2016年03月11日 19:50, Gianfranco Costamagna 写道: Hi, Coreboot is a project to reimplement firmware of computer, it is not a software running atop any operating system. the bios of virtualbox is completely open source, I'm not sure what is your point here :) Coreboot is at https://www.coreboot.org/, which has not been included within debian. this seems to be a blocker then And I have never been working on virtualbox. Now I am only a Coreboot user and potential developer. I just want to point out the possibility about that. ok thanks for that, let me explain what I think about the issue (note: the issue is older than my virtualbox adoption, so I might be wrong). The virtualbox firmware/bios is completely open source, the problem here is that the *compiler* (open watcom) is only "freeware" and not open source, and the open source alternatives are not capable of building it, at least they weren't some months ago, when I tried them. If you have a different opinion, or progresses please let me know, I tried many times to put it back to main, but I couldn't build anything :( cheers, G.
Bug#817260: Wish: Replace virtualbox's guest BIOS with Coreboot
Hi. Coreboot is a project to reimplement firmware of computer, it is not a software running atop any operating system. Coreboot is at https://www.coreboot.org/, which has not been included within debian. And I have never been working on virtualbox. Now I am only a Coreboot user and potential developer. I just want to point out the possibility about that. Thanks. 在 2016年03月11日 18:22, Gianfranco Costamagna 写道: > control: tags -1 moreinfo > > Hi, Tianming, can you please point me to the coreboot package in debian > unstable? > I have difficulties in finding it, and a patch for building it would be > apppreciated. > > cheers, > > G. > > > > > > Il Mercoledì 9 Marzo 2016 15:39, Tianming Xie ha scritto: > Package: virtualbox > Severity: wishlist > > Dear Maintainer, > > As far as I know, the reason why virtualbox is moved to contrib is the > toolchain to build the guest BIOS is non-free. The source code of the BIOS > itself is viewable. So is it possible to reimplement the guest bios atop > Coreboot, which already has a completely free toolchain? > > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (900, 'testing'), (500, 'testing-proposed-updates') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system)
Bug#809710: mpv can never load external subtitle file.
Oh, I noticed some ASS do work with mpv. The ASS unable to play is
attached. It can be played by the last version, as well as other media
players.
在 2016年01月09日 22:14, Alessandro Ghedini 写道:
> On Sun, Jan 03, 2016 at 05:30:58PM +0800, Tianming Xie wrote:
>> Package: mpv
>> Version: 0.14.0-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> After upgraded to the current version, mpv can never load external ASS
>> subtitle
>> file any more, neither a subtitle file located beside the corresponding video
>> file, which may be loaded automatically when opening the video file, nor
>> explicitly assigned targets via --sub-file, with the following error log:
>>
>> [cplayer] Can not open external file
>>
>> The last version does not have this bug.
>>
>> Subtitles embedded as stream within video files seem not affected, but I lack
>> more samples to test, and now I do not have subtitle files in other formats.
> Could you please provide the ASS file that doesn't work, so I can try to
> reproduce this?
>
> Thanks

[Script Info]
; Script generated by Danmaku2ASS
; https://github.com/m13253/danmaku2ass
Script Updated By: Danmaku2ASS (https://github.com/m13253/danmaku2ass)
ScriptType: v4.00+
PlayResX: 1280
PlayResY: 720
Aspect Ratio: 1280:720
Collisions: Normal
WrapStyle: 2
ScaledBorderAndShadow: yes
YCbCr Matrix: TV.601
[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Danmaku2ASS_2824, sans-serif, 34, &H33FF, &H33FF, &H3300, &H3300, 0, 0, 0, 0, 100, 100, 0.00, 0.00, 1, 1, 0, 7, 0, 0, 0, 0
[Events]
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: 2,0:00:06.17,0:00:11.17,Danmaku2ASS_2824,,,,,,{\an8\pos(640, 0)\c&H1300D3&}å¼å£è·ª
Dialogue: 2,0:00:06.47,0:00:14.47,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -102, 0)}è¿æ¯å¥
Dialogue: 2,0:00:07.81,0:00:15.81,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -68, 0)}åå
Dialogue: 2,0:00:08.52,0:00:16.52,Danmaku2ASS_2824,,,,,,{\move(1280, 34, -408, 34)}_(ë_ëãâ )_å¼å£è·ª
Dialogue: 2,0:00:09.57,0:00:17.57,Danmaku2ASS_2824,,,,,,{\move(1280, 68, -442, 68)}2
Dialogue: 2,0:00:11.47,0:00:19.47,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -102, 0)}å¼¹å¹å¢
Dialogue: 2,0:00:14.20,0:00:22.20,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -340, 0)}23
Dialogue: 2,0:00:14.99,0:00:22.99,Danmaku2ASS_2824,,,,,,{\move(1280, 34, -136, 34)}çµéææ
Dialogue: 2,0:00:20.51,0:00:28.51,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -68, 0)}第å
Dialogue: 2,0:00:25.32,0:00:33.32,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -544, 0)}2333
Dialogue: 2,0:00:30.53,0:00:38.53,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -238, 0)}46åéç人ç
Dialogue: 2,0:00:33.53,0:00:41.53,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -170, 0)}为ä½ä¸å¨å
Dialogue: 2,0:00:34.07,0:00:42.07,Danmaku2ASS_2824,,,,,,{\move(1280, 34, -136, 34)}ä½ ä»¬äººå¢
Dialogue: 2,0:00:38.01,0:00:46.01,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -102, 0)}å¨è¿é
Dialogue: 2,0:00:41.52,0:00:49.52,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -272, 0)}诹å°çæï¼ï¼ï¼ï¼
Dialogue: 2,0:00:48.02,0:00:56.02,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -170, 0)}å§æ§½è¿åå·®
Dialogue: 2,0:00:51.51,0:00:59.51,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -204, 0)}å§æ§½ãããã
Dialogue: 2,0:00:52.78,0:01:00.78,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -238, 0)}å¾çsaber
Dialogue: 2,0:00:54.67,0:01:02.67,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -102, 0)}WOC
Dialogue: 2,0:00:55.50,0:01:03.50,Danmaku2ASS_2824,,,,,,{\move(1280, 34, -306, 34)}å±
ç¶æ¯èµ°è系路线ä¹
Dialogue: 2,0:00:57.98,0:01:05.98,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -170, 0)}è¿æ¯å¾çï¼
Dialogue: 2,0:00:58.11,0:01:06.11,Danmaku2ASS_2824,,,,,,{\move(1280, 34, -68, 34)\c&HE5AC0E&}å¾ç
Dialogue: 2,0:01:01.42,0:01:09.42,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -374, 0)}âå±
ç¶æ¯åå¿çopâ¦â¦
Dialogue: 2,0:01:02.73,0:01:10.73,Danmaku2ASS_2824,,,,,,{\move(1280, 34, -170, 34)}软软çå¾ç
Dialogue: 2,0:01:03.23,0:01:11.23,Danmaku2ASS_2824,,,,,,{\move(1280, 68, -238, 68)}=. =å·å«æ
Dialogue: 2,0:01:04.19,0:01:12.19,Danmaku2ASS_2824,,,,,,{\move(1280, 0, -272, 0)}æ..å»
Dialogue: 2,0:01:04.21,0:01:12.21,Danmaku2ASS_2824,,,,,,{\move(1280, 102, -340, 102)}å¦å¦å¥½å¯ç±2
Dialogue: 2,0:01:04.36,0:01:12.36,Danmaku2ASS_2824,,,,,,{\move(1280, 34, -136, 34)}浪客åå¿
Dialogue: 2,0:01:04.83,0:01:12.83,Danmaku2ASS_2824,,,,,,{\move(1280, 136, -340, 136)}å¾çç声é³.
Dia
Bug#802118: [pkg-opensc-maint] Bug#802118: libengine-pkcs11-openssl: Functions to set static global data may cause memory leak.
Dear Maintainer, I have filed a patch for set_init_args (thus the bugs related to these four functions are fixed completely) to upstream on github, which has been merged into its master branch 6 hours ago. Please check. On Sun, 18 Oct 2015 17:31:08 -0400 Eric Dorland wrote: > * persmule (persm...@gmail.com) wrote: > > Package: libengine-pkcs11-openssl > > Version: 0.1.8-5 > > Severity: grave > > Tags: security > > Justification: user security hole > > > > Dear Maintainer, > > > > Functions in src/engine_pkcs11.c to set static global data (set_module, > > set_pin, get_pin and set_init_args) do not free memories pointed by the > > corresponding pointers before assigning them to newly allocated > > memories, which > > may cause memory leaks if they are called more than once. > > > > The bugs related to set_module, set_pin and get_pin are fixed on > > upstream, but > > the one of set_init_args is not. > > Agreed that these are valid memory leaks but what's the security > implication? This doesn't seem obviously exploitable. > > -- > Eric Dorland > 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93 signature.asc Description: OpenPGP digital signature
Bug#802429: modem-manager-gui: Program crash for ABI mismatch.
Dear Maintainer, I rechecked the backtrace, and noticed the cause of crash is not an ABI mismatch, but a nonstandard coded opcodestr "00340036003000300031", which is the UTF16BE dump for L"46001", which means mcc = 460 and mnc = 1. The current version of mmgui_module_gsm_operator_code in modules/mm07.c cannot handle its length (and its code), and crashes for buffer overflow. The title of the bug might have to be changed, sorry. On Tue, 20 Oct 2015 09:56:25 +0800 Tianming Xie wrote: > Package: modem-manager-gui > Version: 0.0.18-1 > Severity: normal > > Dear Maintainer, > > Recently, I bought a "Fibocom L810 LTE Module > (http://www.fibocom.com/product/2-1-5-4.html)" modem in the form of a mini > pci-e card, with usb id 1519:0443 and recognized as "Comneon Telit LN930". It > can be powered by the current version of modemmanager with the "Generic" > plugin. > > But modem-manager-gui crashed when using this modem (it works fine with > Huawei's internal modem module and detachable usb modem). I managed to get the > core and dump a backtrace, and noticed that the order of parameters during the > call of memcpy by mmgui_module_gsm_operator_code (between stack layer #5 and > #6) is reversed! > > #5 0x7f846972b17a in memcpy (__len=17, __src=0x7f8464004223, > __dest=0x7ffd28c7ef60) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 > #6 mmgui_module_gsm_operator_code (opcodestr=0x7f8464004220 > "00340036003000300031") at mm07.c:287 > > Finally, it goes to abort the execution. > > I will attached the complete backtrace and info about the modem (generated with > mmcli), may it be useful to you. > > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages modem-manager-gui depends on: > ii libc6 2.19-22 > ii libcairo2 1.14.2-2 > ii libgdbm3 1.8.3-13.1 > ii libgdk-pixbuf2.0-0 2.32.1-1 > ii libglib2.0-0 2.46.0-2 > ii libgtk-3-0 3.18.2-1 > ii libgtkspell3-3-0 3.0.7-2 > ii modemmanager 1.4.12-1 > ii network-manager 1.0.6-1 > ii policykit-1 0.105-12 > ii ppp 2.4.6-3.1 > > Versions of packages modem-manager-gui recommends: > ii mobile-broadband-provider-info 20140317-1 > ii yelp 3.16.1-1 > > Versions of packages modem-manager-gui suggests: > ii evolution-data-server 3.18.0-3
Bug#802118: [pkg-opensc-maint] Bug#802118: libengine-pkcs11-openssl: Functions to set static global data may cause memory leak.
Dear Maintainer,
I don't know whether it is easy to exploit. But I believe every memory
bug related to a security-oriented package is grave.
By the way, I managed creating a patch locally, may it be useful for you.
Persmule
On Sun, 18 Oct 2015 17:31:08 -0400 Eric Dorland wrote:
> * persmule (persm...@gmail.com) wrote:
> > Package: libengine-pkcs11-openssl
> > Version: 0.1.8-5
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> >
> > Dear Maintainer,
> >
> > Functions in src/engine_pkcs11.c to set static global data (set_module,
> > set_pin, get_pin and set_init_args) do not free memories pointed by the
> > corresponding pointers before assigning them to newly allocated
> > memories, which
> > may cause memory leaks if they are called more than once.
> >
> > The bugs related to set_module, set_pin and get_pin are fixed on
> > upstream, but
> > the one of set_init_args is not.
>
> Agreed that these are valid memory leaks but what's the security
> implication? This doesn't seem obviously exploitable.
>
> --
> Eric Dorland
> 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93
Description:
Functions in src/engine_pkcs11.c to set static global data
(set_module, set_pin, get_pin and set_init_args) do not free
memories pointed by the corresponding pointers before assigning
them to newly allocated memories, which may cause memory leaks
if they are called more than once.
.
engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium
.
* src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)
Author: Xie Tianming
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update:
--- engine-pkcs11-0.1.8.orig/src/engine_pkcs11.c
+++ engine-pkcs11-0.1.8/src/engine_pkcs11.c
@@ -62,10 +62,22 @@ static char *init_args = NULL;
int set_module(const char *modulename)
{
+ free(module);
module = modulename ? strdup(modulename) : NULL;
return 1;
}
+/* Free PIN storage in secure way. */
+static void zero_pin(void)
+{
+ if (pin != NULL) {
+ OPENSSL_cleanse(pin, pin_length);
+ free(pin);
+ pin = NULL;
+ pin_length = 0;
+ }
+}
+
/**
* Set the PIN used for login. A copy of the PIN shall be made.
*
@@ -89,6 +101,7 @@ int set_pin(const char *_pin)
/* Copy the PIN. If the string cannot be copied, NULL
shall be returned and errno shall be set. */
+ zero_pin();
pin = strdup(_pin);
if (pin != NULL)
pin_length = strlen(pin);
@@ -115,6 +128,7 @@ static int get_pin(UI_METHOD * ui_method
/* pin in the call back data, copy and use */
if (mycb != NULL && mycb->password) {
+ zero_pin();
pin = (char *)calloc(MAX_PIN_LENGTH, sizeof(char));
if (!pin)
return 0;
@@ -147,6 +161,7 @@ static int get_pin(UI_METHOD * ui_method
int set_init_args(const char *init_args_orig)
{
+ free(init_args);
init_args = init_args_orig ? strdup(init_args_orig) : NULL;
return 1;
}
engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium
* src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)
-- Xie Tianming Mon, 19 Oct 2015 09:19:53 +0800
engine-pkcs11 (0.1.8-5) unstable; urgency=medium
* debian/source/options, debian/source/patch-header: Remove obsolete
source control files.
* debian/watch: Fix URL.
* debian/control: Move maintainer to
pkg-opensc-ma...@lists.alioth.debian.org to and myself to Uploaders.
* debian/copyright: Move to DEP5 copyright file.
* debian/gbp.conf: Use pristine-tar.
* debian/control, debian/rules: Use dh-autoreconf.
-- Eric Dorland Sun, 10 May 2015 15:49:32 -0400
engine-pkcs11 (0.1.8-4) unstable; urgency=medium
* debian/control: Standards-Version to 3.9.6.
* debian/control: Add Vcs-* fields.
* debian/control: Add Homepage field.
* debian/watch: Update with new GitHub location.
* debian/control: Run wrap-and-sort.
-- Eric Dorland Sat, 20 Sep 2014 19:03:02 -0400
engine-pkcs11 (0.1.8-3) unstable; urgency=low
* debian/control, debian/rules: Use autotools-dev.
* debian/compat, debian/control: Use debhelper v9.
* debian/control: Upgrade Standards-Version to 3.9.4.
-- Eric Dorland Wed, 11 Sep 2013 23:52:42 -0400
engine-pkcs11 (0.1.8-2) unstable; urgency=low
* debian/rules: Actually install the engine in the correct
location.(Closes: #566971)
-- Eric Dorland Tue, 09 Feb 2010 02:33:41 -0500
engine-pkcs11 (0.1.8-1) unstable; urgency=low
* New upstream release. (Closes: #564056)
* debian/libengine-pkcs11-openssl.links: Engine is now installed into
the correct location under /usr/lib/ssl/engines, add a symlink to the
old location
Bug#802118: [pkg-opensc-maint] Bug#802118: libengine-pkcs11-openssl: Functions to set static global data may cause memory leak.
Dear Maintainer,
I don't know whether it is easy to exploit. But I believe every
memory bug related to a security-oriented package is grave.
By the way, I managed creating a patch locally, may it be useful for
you.
Persmule
On Sun, 18 Oct 2015 17:31:08 -0400 Eric Dorland
wrote:
> * persmule (persm...@gmail.com) wrote:
> > Package: libengine-pkcs11-openssl
> > Version: 0.1.8-5
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> >
> > Dear Maintainer,
> >
> > Functions in src/engine_pkcs11.c to set static global data
(set_module,
> > set_pin, get_pin and set_init_args) do not free memories
pointed by the
> > corresponding pointers before assigning them to newly
allocated
> > memories, which
> > may cause memory leaks if they are called more than once.
> >
> > The bugs related to set_module, set_pin and get_pin are
fixed on
> > upstream, but
> > the one of set_init_args is not.
>
> Agreed that these are valid memory leaks but what's the
security
> implication? This doesn't seem obviously exploitable.
>
> --
> Eric Dorland
> 43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93
Description:
Functions in src/engine_pkcs11.c to set static global data
(set_module, set_pin, get_pin and set_init_args) do not free
memories pointed by the corresponding pointers before assigning
them to newly allocated memories, which may cause memory leaks
if they are called more than once.
.
engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium
.
* src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)
Author: Xie Tianming
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update:
--- engine-pkcs11-0.1.8.orig/src/engine_pkcs11.c
+++ engine-pkcs11-0.1.8/src/engine_pkcs11.c
@@ -62,10 +62,22 @@ static char *init_args = NULL;
int set_module(const char *modulename)
{
+ free(module);
module = modulename ? strdup(modulename) : NULL;
return 1;
}
+/* Free PIN storage in secure way. */
+static void zero_pin(void)
+{
+ if (pin != NULL) {
+ OPENSSL_cleanse(pin, pin_length);
+ free(pin);
+ pin = NULL;
+ pin_length = 0;
+ }
+}
+
/**
* Set the PIN used for login. A copy of the PIN shall be made.
*
@@ -89,6 +101,7 @@ int set_pin(const char *_pin)
/* Copy the PIN. If the string cannot be copied, NULL
shall be returned and errno shall be set. */
+ zero_pin();
pin = strdup(_pin);
if (pin != NULL)
pin_length = strlen(pin);
@@ -115,6 +128,7 @@ static int get_pin(UI_METHOD * ui_method
/* pin in the call back data, copy and use */
if (mycb != NULL && mycb->password) {
+ zero_pin();
pin = (char *)calloc(MAX_PIN_LENGTH, sizeof(char));
if (!pin)
return 0;
@@ -147,6 +161,7 @@ static int get_pin(UI_METHOD * ui_method
int set_init_args(const char *init_args_orig)
{
+ free(init_args);
init_args = init_args_orig ? strdup(init_args_orig) : NULL;
return 1;
}
engine-pkcs11 (0.1.8-5.1) unstable; urgency=medium
* src/engine_pkcs11.c: Prevent potential memory leak (fix #802118)
-- Xie Tianming Mon, 19 Oct 2015 09:19:53 +0800
engine-pkcs11 (0.1.8-5) unstable; urgency=medium
* debian/source/options, debian/source/patch-header: Remove obsolete
source control files.
* debian/watch: Fix URL.
* debian/control: Move maintainer to
pkg-opensc-ma...@lists.alioth.debian.org to and myself to Uploaders.
* debian/copyright: Move to DEP5 copyright file.
* debian/gbp.conf: Use pristine-tar.
* debian/control, debian/rules: Use dh-autoreconf.
-- Eric Dorland Sun, 10 May 2015 15:49:32 -0400
engine-pkcs11 (0.1.8-4) unstable; urgency=medium
* debian/control: Standards-Version to 3.9.6.
* debian/control: Add Vcs-* fields.
* debian/control: Add Homepage field.
* debian/watch: Update with new GitHub location.
* debian/control: Run wrap-and-sort.
-- Eric Dorland Sat, 20 Sep 2014 19:03:02 -0400
engine-pkcs11 (0.1.8-3) unstable; urgency=low
* debian/control, debian/rules: Use autotools-dev.
* debian/compat, debian/control: Use debhelper v9.
* debian/control: Upgrade Standards-Version to 3.9.4.
-- Eric Dorland Wed, 11 Sep 2013 23:52:42 -0400
engine-pkcs11 (0.1.8-2) unstable; urgency=low
* debian/rules: Actually install the engine in the correct
location.(Closes: #566971)
-- Eric Dorland Tue, 09 Feb 2010 02:33:41 -0500
engine-pkcs11 (0.1.8-1) unstable; urgency=low
* New upstream relea
Bug#802118: libengine-pkcs11-openssl: Functions to set static global data may cause memory leak.
Package: libengine-pkcs11-openssl Version: 0.1.8-5 Severity: grave Tags: security Justification: user security hole Dear Maintainer, Functions in src/engine_pkcs11.c to set static global data (set_module, set_pin, get_pin and set_init_args) do not free memories pointed by the corresponding pointers before assigning them to newly allocated memories, which may cause memory leaks if they are called more than once. The bugs related to set_module, set_pin and get_pin are fixed on upstream, but the one of set_init_args is not. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libengine-pkcs11-openssl depends on: ii libc62.19-22 ii libp11-2 0.2.8-6 ii libssl1.0.0 1.0.2d-1 libengine-pkcs11-openssl recommends no packages. libengine-pkcs11-openssl suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#799935: emacs24: double desktop entry in .desktop file does not work in cinnamon
This problem also appears on my GNOME environment. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages emacs24 depends on: ii emacs24-bin-common 24.5+1-2 ii gconf-service 3.2.6-3 ii libacl12.2.52-2 ii libasound2 1.0.29-1 ii libatk1.0-02.16.0-2 ii libc6 2.19-22 ii libcairo-gobject2 1.14.2-2 ii libcairo2 1.14.2-2 ii libdbus-1-31.10.0-3 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.6-2 ii libgconf-2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.32.0-1 ii libgif44.1.6-11 ii libglib2.0-0 2.44.1-1.1 ii libgnutls-deb0-28 3.3.17-1 ii libgomp1 5.2.1-17 ii libgpm21.20.4-6.1+b2 ii libgtk-3-0 3.16.6-1 ii libice62:1.0.9-1+b1 ii libjpeg62-turbo1:1.4.1-2 ii libm17n-0 1.7.0-1 ii libmagickcore-6.q16-2 8:6.8.9.9-6 ii libmagickwand-6.q16-2 8:6.8.9.9-6 ii libotf00.9.13-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libpng12-0 1.2.50-2+b2 ii librsvg2-2 2.40.10-1 ii libselinux12.3-2+b1 ii libsm6 2:1.2.2-1+b1 ii libtiff5 4.0.5-1 ii libtinfo5 6.0+20150810-1 ii libx11-6 2:1.6.3-1 ii libxft22.3.2-1 ii libxinerama1 2:1.1.3-1+b1 ii libxml22.9.2+zdfsg1-4 ii libxpm41:3.5.11-1+b1 ii libxrandr2 2:1.5.0-1 ii libxrender11:0.9.8-1+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 emacs24 recommends no packages. Versions of packages emacs24 suggests: ii emacs24-common-non-dfsg 24.4+1-2 -- no debconf information On Thu, 24 Sep 2015 22:20:20 +0900 Norbert Preining wrote: > Package: emacs24 > Version: 24.5+1-2 > Severity: normal > > Hi, > > the recent update brought a new emacs24 .desktop file that contains > two desktop entries. But unfortunately this seems to be not > supported by cinnamon, or at least it offers me only the > GNU Emacs 24 (Terminal) > option. > > Could you please ship two different .desktop files if possible? > > Thanks a lot > > Norbert > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable'), (300, 'testing'), (200, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.3.0-rc1 (SMP w/4 CPU cores; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages emacs24 depends on: > ii emacs24-bin-common 24.5+1-2 > ii gconf-service 3.2.6-3 > ii libacl1 2.2.52-2 > ii libasound2 1.0.29-1 > ii libatk1.0-0 2.16.0-2 > ii libc6 2.19-22 > ii libcairo-gobject2 1.14.2-2 > ii libcairo2 1.14.2-2 > ii libdbus-1-3 1.10.0-3 > ii libfontconfig1 2.11.0-6.3 > ii libfreetype6 2.6-2 > ii libgconf-2-4 3.2.6-3 > ii libgdk-pixbuf2.0-0 2.32.0-1 > ii libgif4 4.1.6-11 > ii libglib2.0-0 2.44.1-1.1 > ii libgnutls-deb0-28 3.3.17-1 > ii libgomp1 5.2.1-17 > ii libgpm2 1.20.4-6.1+b2 > ii libgtk-3-0 3.16.6-1 > ii libice6 2:1.0.9-1+b1 > ii libjpeg62-turbo 1:1.4.1-2 > ii libm17n-0 1.7.0-1 > ii libmagickcore-6.q16-2 8:6.8.9.9-6 > ii libmagickwand-6.q16-2 8:6.8.9.9-6 > ii libotf0 0.9.13-2 > ii libpango-1.0-0 1.36.8-3 > ii libpangocairo-1.0-0 1.36.8-3 > ii libpng12-0 1.2.50-2+b2
Bug#799347: [Pkg-amule-devel] Bug#799347: amule: libcrypto++ starts to conflict to the current version of amule.
Sadly the maintainer of wx2.8 refuses to put more effort into it (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799367), which may lead to a removal of amule inside debian. I believe an agreement between you and the the maintainer of wx2.8 is needed to fix the ABI-incompatibility (please forgive my crippled english :-) ). 在 2015年09月18日 18:31, Sandro Tosi 写道: > why do yo ask me? I'm not the WX maintainer, I guess you should ask them. > > On Fri, Sep 18, 2015 at 11:29 AM, persmule wrote: >> Is it possible to rebuild wx2.8 with gcc-5? The main problem is that the ABI >> used by >> >> wx2.8 and libcrypto++9v5 (and the new libcrypto++-dev) is not compatible. >> >> >> 在 2015年09月18日 16:01, Sandro Tosi 写道: >> >> I'm not sure what are you asking us to do, please clarify. Note, amule >> is currently not migratable to WX3.0 >> >> On Fri, Sep 18, 2015 at 8:39 AM, Tianming Xie wrote: >> >> Package: amule >> Version: 2.3.1+git1a369e47-3 >> Severity: important >> >> Dear Maintainer, >> >> libcrypto++-dev 5.6.1-9 has entered testing repository, which causes a >> conflict to the current version of amule. since amule depends on wx2.8, >> which >> is built against the ABI (mainly std::string) of gcc-4, and cannot use >> libcrypto++9v5, on which libcrypto++-dev 5.6.1-9 depends, built against >> gcc-5's >> C++ ABI. So now I have not to upgrade libcrypto++-dev to 5.6.1-9. >> >> libcrypto++9v5 cannot coexist with libcrypto++9, on which the current >> amule >> depends. So if the upgrading of libcrypto++-dev is finally unstoppable, we >> may >> have to rebuild wx2.8 with gcc-5, then rebuild amule, or migrate amule to >> wx3.0v5, which has been built against gcc-5's C++ ABI. >> >> >> >> -- System Information: >> Debian Release: stretch/sid >> APT prefers testing >> APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, >> 'unstable') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) >> Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> Init: systemd (via /run/systemd/system) >> >> Versions of packages amule depends on: >> ii amule-common2.3.1+git1a369e47-3 >> ii libc6 2.19-19 >> ii libcrypto++95.6.1-7 >> ii libgcc1 1:5.2.1-17 >> ii libgeoip1 1.6.6-1+b1 >> ii libstdc++6 5.2.1-17 >> ii libupnp61:1.6.19+git20141001-1 >> ii libwxbase2.8-0 2.8.12.1+dfsg2-2 >> ii libwxgtk2.8-0 2.8.12.1+dfsg2-2 >> ii zlib1g 1:1.2.8.dfsg-2+b1 >> >> Versions of packages amule recommends: >> ii amule-utils 2.3.1+git1a369e47-3 >> ii unzip6.0-18 >> >> Versions of packages amule suggests: >> ii amule-utils-gui 2.3.1+git1a369e47-3 >> >> -- no debconf information >> >> ___ >> Pkg-amule-devel mailing list >> pkg-amule-de...@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-amule-devel >> >> >> > >
Bug#790494: modem-manager-gui: libebook 3.16 API break
Dear Graham,
There already is a patch
http://download.tuxfamily.org/gsf/patch/modem-manager-gui-0.0.17.1-fix-libebook-api-break-v2.patch
linked on
http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.31.0
,
but the bug remains not tracked.
In order to use modem-manager-gui on stretch, I applied this patch locally to
build new .deb packages, and the result works like a charm.
In the process I created a debianized patch file. May it be useful to you and
every stretch users.
Best regards
Persmule
Description: temporarily fix bug #790494
Author: Xie Tianming
Origin: other, http://download.tuxfamily.org/gsf/patch/modem-manager-gui-0.0.17.1-fix-libebook-api-break-v2.patch
Bug: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.31.0
Bug-Debian: https://bugs.debian.org/790494
Forwarded: no
Last-Update: 2015-05-02
--- modem-manager-gui-0.0.17.1.orig/src/addressbooks.c
+++ modem-manager-gui-0.0.17.1/src/addressbooks.c
@@ -36,6 +36,8 @@
#include "vcard.h"
#include "addressbooks.h"
+#define MMGUI_ADDRESSBOOKS_GNOME_CONNECT_TIMEOUT 15
+
#define MMGUI_ADDRESSBOOKS_AKONADI_LINK_PATH "%s/.local/share/akonadi/socket-localhost"
#define MMGUI_ADDRESSBOOKS_AKONADI_SOCKET_PATH "%s/akonadiserver.socket"
#define MMGUI_ADDRESSBOOKS_AKONADI_DBUS_INTERFACE"org.freedesktop.Akonadi.Control"
@@ -78,7 +80,6 @@ struct _mmgui_addressbooks_akonadi_colle
typedef struct _mmgui_addressbooks_akonadi_collection *mmgui_addressbooks_akonadi_collection_t;
-
//KDE (Akonadi)
static gboolean mmgui_addressbooks_session_service_activate(gchar *interface, guint *status);
static gint mmgui_addressbooks_open_kde_socket(void);
@@ -95,7 +96,7 @@ static guint mmgui_addressbooks_akonadi_
static gboolean mmgui_addressbooks_get_kde_contacts(mmgui_addressbooks_t addressbooks);
//GNOME (Evolution data server)
static void mmgui_addressbooks_get_gnome_contacts_foreach(gpointer data, gpointer user_data);
-static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks);
+static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks, mmgui_libpaths_cache_t libcache);
//Other
static void mmgui_addressbooks_free_contacts_list_foreach(gpointer data, gpointer user_data);
@@ -787,7 +788,7 @@ static void mmgui_addressbooks_get_gnome
g_list_free(emails);
}
-static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks)
+static gboolean mmgui_addressbooks_get_gnome_contacts(mmgui_addressbooks_t addressbooks, mmgui_libpaths_cache_t libcache)
{
EBookQuery *queryelements[2];
EBookQuery *query;
@@ -802,12 +803,17 @@ static gboolean mmgui_addressbooks_get_g
EBook *book;
GList *dcontacts;
- if (addressbooks == NULL) return FALSE;
+ if ((addressbooks == NULL) || (libcache == NULL)) return FALSE;
if (!addressbooks->gnomesupported) return FALSE;
if (addressbooks->ebookmodule == NULL) return FALSE;
error = NULL;
+ if (!mmgui_libpaths_cache_check_library_version(libcache, "libebook-1.2", 12, 3, 0)) {
+ g_debug("GNOME contacts API isn't supported\n");
+ return FALSE;
+ }
+
queryelements[0] = (addressbooks->e_book_query_field_exists)(E_CONTACT_PHONE_HOME);
queryelements[1] = (addressbooks->e_book_query_field_exists)(E_CONTACT_PHONE_MOBILE);
@@ -817,39 +823,63 @@ static gboolean mmgui_addressbooks_get_g
return FALSE;
}
- if (addressbooks->e_book_new_system_addressbook != NULL) {
- g_debug("Using old GNOME contacts API\n");
- book = (addressbooks->e_book_new_system_addressbook)(&error);
- if (book == NULL) {
+ if (mmgui_libpaths_cache_check_library_version(libcache, "libebook-1.2", 14, 3, 0)) {
+ g_debug("Using GNOME contacts API version 3.6 ... ?\n");
+ registry = (addressbooks->e_source_registry_new_sync)(NULL, &error);
+ if (registry == NULL) {
(addressbooks->e_book_query_unref)(query);
- g_debug("Failed to load GNOME system addressbook: %s\n", error->message);
+ g_debug("Failed to get ESourceRegistry: %s\n", error->message);
g_error_free(error);
return FALSE;
}
- if (!(addressbooks->e_book_open)(book, TRUE, &error)) {
+ source = (addressbooks->e_source_registry_ref_builtin_address_book)(registry);
+ if (source == NULL) {
(addressbooks->e_book_query_unref)(query);
- g_debug("Failed to load GNOME system addressbook: %s\n", error->message);
- g_error_free(error);
+ g_debug("Failed to get ESource\n");
return FALSE;
}
- source = (addressbooks->e_book_get_source)(book);
+ addressbooks->gnomesourcename = (addressbooks->e_source_get_display_name)(source);
- if (addressbooks->e_source_get_display_name != NULL) {
- addressbooks->gnomesourcename = (addressbooks->e_source_get_di
Bug#790494: Bug#764693: modem-manager-gui: crash on start
Dear Graham, There already is a patch http://download.tuxfamily.org/gsf/patch/modem-manager-gui-0.0.17.1-fix-libebook-api-break-v2.patch linked on http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.31.0, but the bug remains not assigned. Is it possible to apply this patch on debian first, to make the software usable? On Mon, 29 Jun 2015 21:41:41 +0200 Graham Inggs wrote: > Hi persmule > > On 29 June 2015 at 07:19, persmule wrote: > > Package: modem-manager-gui > > Version: 0.0.17.1-2 > > Followup-For: Bug #764693 > > > > Dear Maintainer, > > > > The bug reappears in modem-manager-gui 0.0.17.1-2. > > > > When I invoked modem-manager-gui in a terminal emulator, I got the following > > error log from its stdout, Then the program aborted: > > > >>Connection manager: Network Manager >= 0.9.0 > >>Modem manager: Modem Manager >= 0.7.0 > >>Segmentation fault at address: 0x8 > >>Stack trace: > >>1. modem-manager-gui(mmgui_addressbooks_new+0xeaf) [0x4135df] > >>2. modem-manager-gui(mmgui_addressbooks_new+0xeaf) [0x4135df] > >>3. modem-manager-gui() [0x42ebf3] > >>4. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x145) > > [0x7f05943e42d5] > >>5. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2203c) [0x7f05943f603c] > >>6. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xfd8) > > [0x7f05943fe698] > >>7. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f) > > [0x7f05943fe8ff] > >>8. /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xa93ee) [0x7f05946d03ee] > >>9. /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_application_run+0x172) > > [0x7f05946d05e2] > > > > And I managed to generate a core with gdb (attached, compressed with xz, > > but still large), may it be useful. > > This seems to be a different bug to #764693. > I found a similar bug reported upstream: > http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.31.0 > > I have cloned the bug as #790494, please use this number for follow up. > > Regards > Graham > > signature.asc Description: OpenPGP digital signature
Bug#794243: Acknowledgement (grub-common: Add support for F2FS to grub-probe)
Besides, the current linux kernel can boot with rootfs assigned via UUID with no problem: > [ 0.00] Command line: BOOT_IMAGE=/vmlinuz-4.0.0-2-amd64 root=UUID=bd5dda9c-073c-45ca-b89b-e8c73272254b ro quiet 在 2015年08月01日 00:18, Debian Bug Tracking System 写道: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): GRUB Maintainers If you wish to submit further information on this problem, please send it to 794...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#790869: gnome-shell is trapped with invalid opcode when working with gdm3.
Package: gnome-shell Version: 3.16.2-4 Severity: normal Dear Maintainer, When I log in this machine (with Intel(R) Celeron(R) CPUU3400 @ 1.07GHz) after booting, the normal screen of gnome-shell DE appears, but the whole screen turns black. If I press a key, the lockdown screen appears. When I try to type the password, it enters an endless loop as if the unlock button were clicked repeatedly, as the screen starts blinking, and any input to the password textbox disappears, except that a notice like "authentication failed(In Chinese)" is shown. With the help of my friend, I tried to login from text ttys (1~6), and restart gdm3. But the gnome-shell crashes, with the following lines in the syslog: >Jul 2 19:29:49 toshiba-chenlin kernel: [ 115.119886] traps: gnome- shell[3129] trap invalid opcode ip:7f729104a639 sp:7ffc81171df8 error:0 >Jul 2 19:29:51 toshiba-chenlin dbus[1950]: [system] Activating service name='org.freedesktop.GeoClue2' (using servicehelper) >Jul 2 19:29:51 toshiba-chenlin dbus[1950]: [system] Successfully activated service 'org.freedesktop.GeoClue2' >Jul 2 19:29:51 toshiba-chenlin kernel: [ 117.825838] traps: gnome- shell[3218] trap invalid opcode ip:7f857808d639 sp:7ffef6ea8d78 error:0 >Jul 2 19:29:51 toshiba-chenlin gnome-session[3064]: WARNING: App 'gnome- shell.desktop' respawning too quickly And it seems the above "black screen" phenomenon is also caused by the crash of gnome shell. Now I have to switch to an lxde env I installed earlier for work. This bug nevers appears on any other machines I know, running debian testing and full gnome DE. My friend tried to get cores from any possible crashed program, but could not find any way. If you have and idea about how to get cores for gdm3,please let me know, so I can gather more info for the bug. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii evolution-data-server3.16.3-1+b1 ii gir1.2-accountsservice-1.0 0.6.40-2 ii gir1.2-atspi-2.0 2.16.0-1 ii gir1.2-caribou-1.0 0.4.18.1-1 ii gir1.2-clutter-1.0 1.22.2-3 ii gir1.2-freedesktop 1.44.0-1+b1 ii gir1.2-gcr-3 3.16.0-1 ii gir1.2-gdesktopenums-3.0 3.16.1-1 ii gir1.2-gdm3 3.14.1-8 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.44.0-1+b1 ii gir1.2-gnomebluetooth-1.03.16.1-1 ii gir1.2-gnomedesktop-3.0 3.16.2-2 ii gir1.2-gtk-3.0 3.16.4-2 ii gir1.2-gweather-3.0 3.16.1-1 ii gir1.2-ibus-1.0 1.5.10-1 ii gir1.2-mutter-3.03.16.2-2 ii gir1.2-networkmanager-1.01.0.2-2 ii gir1.2-nmgtk-1.0 1.0.2-1 ii gir1.2-pango-1.0 1.36.8-3 ii gir1.2-polkit-1.00.105-8 ii gir1.2-soup-2.4 2.50.0-2 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.3-1+b1 ii gjs 1.43.3-2 ii gnome-backgrounds3.16.0-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.16.2-3 ii gnome-shell-common 3.16.2-4 ii gnome-themes-standard3.16.2-2 ii gsettings-desktop-schemas3.16.1-1 ii libatk-bridge2.0-0 2.16.0-1 ii libatk1.0-0 2.16.0-2 ii libc62.19-18 ii libcairo21.14.2-2 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.22.2-3 ii libcogl-pango20 1.20.0-2 ii libcogl201.20.0-2 ii libcroco30.6.8-3+b1 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-18 3.16.3-1+b1 ii libedataserver-1.2-203.16.3-1+b1 ii libgcr-base-3-1 3.16.0-1 ii libgdk-pixbuf2.0-0
Bug#772725: network-manager: NetworkManager daemon aborts after removing an interface when Nokia Phonet interfaces are present.
在 2014年12月10日 22:31, Tianming Xie 写道: > Package: network-manager > Version: 0.9.10.0-3 > Severity: important > > Dear Maintainer, > > The NetworkManager daemon aborts after removing any interface (eg. > unplug an iphone, which expose an ipheth interface, or any hot-pluggable NIC > card) on one of my computers (on which I am writing this bug report), which > has > never taken place on my other computers. > > I managed to grab the core file of NetworkManager daemon, which may be > useful. > > Thanks. > > > > -- System Information: > Debian Release: 8.0 > APT prefers testing > APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, > 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages network-manager depends on: > ii adduser3.113+nmu3 > ii dbus 1.8.12-1 > ii init-system-helpers1.22 > ii isc-dhcp-client4.3.1-5 > ii libc6 2.19-13 > ii libdbus-1-31.8.12-1 > ii libdbus-glib-1-2 0.102-1 > ii libgcrypt201.6.2-4+b1 > ii libglib2.0-0 2.42.1-1 > ii libgnutls-deb0-28 3.3.8-5 > ii libgudev-1.0-0 215-7 > ii libmm-glib01.4.0-1 > ii libndp01.4-2 > ii libnewt0.520.52.17-1+b1 > ii libnl-3-2003.2.24-2 > ii libnl-genl-3-200 3.2.24-2 > ii libnl-route-3-200 3.2.24-2 > ii libnm-glib40.9.10.0-3 > ii libnm-util20.9.10.0-3 > ii libpam-systemd 215-7 > ii libpolkit-gobject-1-0 0.105-8 > ii libreadline6 6.3-8+b2 > ii libsoup2.4-1 2.48.0-1 > ii libsystemd0215-7 > ii libteamdctl0 1.12-1 > ii libuuid1 2.25.2-3 > ii lsb-base 4.1+Debian13+nmu1 > ii policykit-10.105-8 > ii udev 215-7 > ii wpasupplicant 2.3-1 > > Versions of packages network-manager recommends: > ii crda 3.13-1 > ii dnsmasq-base 2.72-2 > ii iptables 1.4.21-2+b1 > ii modemmanager 1.4.0-1 > ii ppp 2.4.6-3 > > Versions of packages network-manager suggests: > ii avahi-autoipd 0.6.31-4+b2 > pn libteam-utils > > -- no debconf information Today I went into the core a bit further. When the NM daemon aborts, a Nokia phone providing Phonet interface is connected to the computer. So before the abortion, the value (which you can see via the core) of ((struct rtnl_route*)object)->rt_family (and ((struct rtnl_addr*)object)->a_family, located in the same address of ((struct rtnl_route*)object)->rt_family ) is 35 "AF_PHONET", a value that function object_type_from_nl_object() can not recognize and give a return value OBJECT_TYPE_UNKNOWN, leading to object_has_ifindex() to abort the daemon. signature.asc Description: OpenPGP digital signature
Bug#766010: further infomation
If there is any information I must but not provide, please ask me for them. Thanks. Module Size Used by rfcomm 57927 4 snd_hrtimer12604 1 snd_seq57061 1 snd_seq_device 13132 1 snd_seq bnep 17431 2 binfmt_misc16949 1 nfsd 263053 2 auth_rpcgss51240 1 nfsd oid_registry 12419 1 auth_rpcgss nfs_acl12511 1 nfsd nfs 187961 0 lockd 83417 2 nfs,nfsd fscache45542 1 nfs sunrpc237445 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl ecb12737 1 btusb 29721 0 bluetooth 374429 26 bnep,btusb,rfcomm 6lowpan_iphc 16588 1 bluetooth nls_utf8 12456 1 nls_cp437 16553 1 vfat 17135 1 fat61986 1 vfat snd_hda_codec_realtek63031 1 snd_hda_codec_generic63107 1 snd_hda_codec_realtek hid_generic12393 0 isight_firmware12500 0 efi_pstore 12805 1 arc4 12536 2 joydev 17063 0 ath9k 90244 0 ath9k_common 21746 1 ath9k ath9k_hw 391172 2 ath9k_common,ath9k ath26067 3 ath9k_common,ath9k,ath9k_hw applesmc 18526 0 input_polldev 13118 1 applesmc coretemp 12820 0 mac80211 474202 1 ath9k kvm_intel 139077 0 kvm 388597 1 kvm_intel cfg80211 405538 4 ath,ath9k_common,ath9k,mac80211 pcspkr 12595 0 efivars17257 1 efi_pstore rfkill 18867 5 cfg80211,bluetooth shpchp 31121 0 cdc_ether 12564 0 usbnet 30844 1 cdc_ether cdc_phonet 12793 0 mii12675 1 usbnet cdc_acm26266 4 phonet 27725 1 cdc_phonet evdev 17445 16 snd_hda_intel 26327 4 snd_hda_controller 26727 1 snd_hda_intel snd_hda_codec 104463 4 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller snd_hwdep 13148 1 snd_hda_codec snd_pcm88662 3 snd_hda_codec,snd_hda_intel,snd_hda_controller snd_timer 26614 3 snd_hrtimer,snd_pcm,snd_seq snd65244 18 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device soundcore 13026 2 snd,snd_hda_codec i2c_nforce212591 0 i2c_core 46012 1 i2c_nforce2 hid_apple 12596 0 appletouch 17050 0 battery13356 0 sbs13012 0 sbshc 12842 1 sbs acpi_cpufreq 17218 1 processor 28221 3 acpi_cpufreq ac 12715 0 button 12944 0 thermal_sys27642 1 processor apple_bl 12872 0 fuse 83350 3 parport_pc 26300 0 ppdev 16782 0 lp 17074 0 parport35749 3 lp,ppdev,parport_pc autofs435529 2 hid_appleir12724 0 usbhid 44467 0 hid 102264 4 hid_generic,usbhid,hid_appleir,hid_apple ext4 469572 9 crc16 12343 2 ext4,bluetooth mbcache17171 1 ext4 jbd2 82413 1 ext4 sg 29973 0 sd_mod 44356 13 crc_t10dif 12431 1 sd_mod crct10dif_generic 12581 1 crct10dif_common 12356 2 crct10dif_generic,crc_t10dif ohci_pci 12808 0 firewire_ohci 39523 0 ahci 29195 11 libahci27158 1 ahci firewire_core 56665 1 firewire_ohci crc_itu_t 12347 1 firewire_core libata177457 2 ahci,libahci scsi_mod 191405 3 sg,libata,sd_mod ohci_hcd 42982 1 ohci_pci ehci_pci 12512 0 ehci_hcd 69837 1 ehci_pci forcedeth 64983 0 usbcore 195340 12 btusb,isight_firmware,ohci_hcd,ohci_pci,ehci_hcd,ehci_pci,cdc_phonet,usbhid,usbnet,appletouch,cdc_acm,cdc_ether usb_common 12440 1 usbcore # dmidecode 2.12 # SMBIOS entry point at 0xbfec7000 SMBIOS 2.4 present. 42 structures occupying 2107 bytes. Table at 0xBFEC6000. Handle 0x, DMI type 4, 35 bytes Processor Information Socket Designation: U2E1 Type: Central Processor Family: Other Manufacturer: Intel(R) Corporation ID: 7A 06 01 00 FF FB EB BF Signature: Type 0, Family 6, Model 23, Stepping 10 Flags: FPU (Floating-point unit on-chip)
Bug#754927: transmission-daemon: segfaults with systemd due to erroneous /lib/systemd/system/transmission-daemon.service file
Package: transmission-daemon
Version: 2.82-1.1+b1
Severity: important
Dear Maintainer,
The ExecStart field of transmission-daemon.service file is "/usr/bin
/transmission-daemon -f --log-error", without explicitly definition of the
config directory as the SysV flavour init scripts (such as /etc/default
/transmission-daemon) do, which cause transmission-daemon to segfault when
started via transmission-daemon.service, even prevent the
transmission-daemon
package from being seccessfully configured by dpkg. If I just gzipped
/lib/systemd/system/transmission-daemon.service and let systemd use
those SysV
flaver init scripts, everything works fine.
I believe the way to start the daemon via systemd service file and SysV
flavour init scripts should be kept consistent, or just let systemd use
those
SysV flaver init scripts.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.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.19
ii libc62.19-7
ii libcurl3-gnutls 7.37.0-1+b1
ii libevent-2.0-5 2.0.21-stable-1
ii libnatpmp1 20110808-3
ii libssl1.0.0 1.0.1h-3
ii libsystemd-daemon0 204-14
ii lsb-base 4.1+Debian13
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+b1
transmission-daemon suggests no packages.
-- Configuration Files:
/etc/default/transmission-daemon changed [not included]
/etc/transmission-daemon/settings.json [Errno 13] æéä¸å¤: u'/etc
/transmission-daemon/settings.json'
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target
[Service]
User=debian-transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error
[Install]
WantedBy=multi-user.target
#!/bin/sh -e
### BEGIN INIT INFO
# Provides: transmission-daemon
# Required-Start:$local_fs $remote_fs $network
# Required-Stop: $local_fs $remote_fs $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start or stop the transmission-daemon.
# Description: Enable service provided by transmission-daemon.
### END INIT INFO
NAME=transmission-daemon
DAEMON=/usr/bin/$NAME
USER=debian-transmission
STOP_TIMEOUT=30
export PATH="${PATH:+$PATH:}/sbin"
[ -x $DAEMON ] || exit 0
[ -e /etc/default/$NAME ] && . /etc/default/$NAME
.. /lib/lsb/init-functions
start_daemon () {
if [ $ENABLE_DAEMON != 1 ]; then
log_progress_msg "(disabled)"
log_end_msg 255 || true
else
start-stop-daemon --start \
--chuid $USER \
$START_STOP_OPTIONS \
--exec $DAEMON -- $OPTIONS || log_end_msg $?
log_end_msg 0
fi
}
case "$1" in
start)
log_daemon_msg "Starting bittorrent daemon" "$NAME"
start_daemon
;;
stop)
log_daemon_msg "Stopping bittorrent daemon" "$NAME"
start-stop-daemon --stop --quiet \
--exec $DAEMON --retry $STOP_TIMEOUT \
--oknodo || log_end_msg $?
log_end_msg 0
;;
reload)
log_daemon_msg "Reloading bittorrent daemon" "$NAME"
start-stop-daemon --stop --quiet \
--exec $DAEMON \
--oknodo --signal 1 || log_end_msg $?
log_end_msg 0
;;
restart|force-reload)
log_daemon_msg "Restarting bittorrent daemon" "$NAME"
start-stop-daemon --stop --quiet \
--exec $DAEMON --retry $STOP_TIMEOUT \
--oknodo || log_end_msg $?
start_daemon
;;
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
;;
*)
log_action_msg "Usage: /etc/init.d/$NAME {start|stop|reload|force-reload|restart|status}" || true
exit 2
;;
esac
exit 0
# defaults for transmission-daemon
# sourced by /etc/init.d/transmission-daemon
# Change to 0 to disable daemon
ENABLE_DAEMON=0
# This directory stores some runtime information, like torrent files
# and links to the config file, which itself can be found in
# /etc/transmission-daemon/settings.json
CONFIG_DIR="/var/lib/transmission-daemon/info"
# Default options for daemon, see transmission-daemon(1) for more options
OPTIONS="--config-dir $CONFIG_DIR"
# (optional) extra options to start-stop-daemon
#START_STOP_OPTIONS="--iosched idle --nicelevel 10"
