Bug#487195: pending
tags 487195 +pending thanks This will be fixed in 5:2 upload. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486713: gcj-doc: tries to overwrite file owned by gcj
reassign 486713 gcj thanks Unpacking gcj-doc (from .../gcj-doc_5%3a1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/gcj-doc_5%3a1_amd64.deb (--unpack): trying to overwrite `/usr/share/man/man1/grmic.1.gz', which is also in package gcj This looks like bug in gcj package. Packages gcj-4.3 does not provide grmic.4.3.1.gz, so gcj should not link on it. I will upload gcc-doc-defaults with gcj-doc Replaces: gcj (= VER) as soon as fixed gcj will be uploaded. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486693: libetpan: minor 32/64 bits problem break some parse functions
The fix is a one-line change, and is already in libetpan CVS: http://libetpan.cvs.sourceforge.net/libetpan/libetpan/src/low-level/imf/mai limf.h?view=diffr1=1.27r2=1.28 Please consider applying it. Actually the above URL is only part of the fix, previous commit is relevant as well. But that's trivial. More interesting issue is - this fix will change a macro in public header. So any external code using this macro will have to be recompile. I'm unsure how to handle this in packaging. Will ask on debian-devel. Nikita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#573362: file: wrong report on UBI images
tags 573362 confirmed moreinfo thanks Nikita V. Youshchenko wrote... (...) ...# ubinize -o ubi.img -m 2048 -p 64KiB -s 512 ubinize.cfg ...# file ubi.img ubi.img: HIT archive data Could reproduce that, thanks. Problem is, HIT archive data has a really weak magic. The only sound solution was to provide strong magic for ubi.img. I didn't find proper documentation, so please help. Same applies for ubifs.img which deserves a better recognition than data. Hi. Well this is a bit not my topic but still, in kernel source in drivers/mtd/ubi/ubi-media.h we have /* Erase counter header magic number (ASCII UBI#) */ #define UBI_EC_HDR_MAGIC 0x55424923 /* Volume identifier header magic number (ASCII UBI!) */ #define UBI_VID_HDR_MAGIC 0x55424921 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573362: file: wrong report on UBI images
tags 573362 confirmed moreinfo thanks Nikita V. Youshchenko wrote... (...) ...# ubinize -o ubi.img -m 2048 -p 64KiB -s 512 ubinize.cfg ...# file ubi.img ubi.img: HIT archive data Could reproduce that, thanks. Problem is, HIT archive data has a really weak magic. The only sound solution was to provide strong magic for ubi.img. I didn't find proper documentation, so please help. Same applies for ubifs.img which deserves a better recognition than data. Hi. Well this is a bit not my topic but still, in kernel source in drivers/mtd/ubi/ubi-media.h we have /* Erase counter header magic number (ASCII UBI#) */ #define UBI_EC_HDR_MAGIC 0x55424923 /* Volume identifier header magic number (ASCII UBI!) */ #define UBI_VID_HDR_MAGIC 0x55424921 Same file contains definition of struct ubi_ec_hdr that is located in ubi image at beginning of each physical erase block, including offset 0. It contains some comments on what data is where. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#805821: systemd does not see existing dmraid volumes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > Could you send us a "udevadm info" dump for those devices. root@nyws:~# udevadm info /dev/mapper/jmicron_Main P: /devices/virtual/block/dm-0 N: dm-0 S: disk/by-id/dm-name-jmicron_Main S: disk/by-id/dm-uuid-DMRAID-jmicron_Main E: DEVLINKS=/dev/disk/by-id/dm-name-jmicron_Main /dev/disk/by-id/dm-uuid-DMRAID-jmicron_Main E: DEVNAME=/dev/dm-0 E: DEVPATH=/devices/virtual/block/dm-0 E: DEVTYPE=disk E: DM_ACTIVATION=1 E: DM_NAME=jmicron_Main E: DM_SUSPENDED=0 E: DM_UDEV_DISABLE_DM_RULES_FLAG=1 E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1 E: DM_UDEV_PRIMARY_SOURCE_FLAG=1 E: DM_UDEV_RULES=1 E: DM_UUID=DMRAID-jmicron_Main E: ID_PART_TABLE_TYPE=dos E: ID_PART_TABLE_UUID=93f56e8a E: MAJOR=254 E: MINOR=0 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=90779 root@nyws:~# udevadm info /dev/mapper/jmicron_Main1 P: /devices/virtual/block/dm-1 N: dm-1 S: disk/by-id/dm-name-jmicron_Main1 S: disk/by-id/dm-uuid-DMRAID-jmicron_Main1 S: disk/by-label/SYSTEM S: disk/by-uuid/544872EF4872CF6C E: DEVLINKS=/dev/disk/by-id/dm-name-jmicron_Main1 /dev/disk/by-id/dm-uuid-DMRAID-jmicron_Main1 /dev/disk/by-label/SYSTEM /dev/disk/by-uuid/544872EF4872CF6C E: DEVNAME=/dev/dm-1 E: DEVPATH=/devices/virtual/block/dm-1 E: DEVTYPE=disk E: DM_ACTIVATION=1 E: DM_NAME=jmicron_Main1 E: DM_SUSPENDED=0 E: DM_UDEV_DISABLE_DM_RULES_FLAG=1 E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1 E: DM_UDEV_PRIMARY_SOURCE_FLAG=1 E: DM_UDEV_RULES=1 E: DM_UUID=DMRAID-jmicron_Main1 E: ID_FS_LABEL=SYSTEM E: ID_FS_LABEL_ENC=SYSTEM E: ID_FS_TYPE=ntfs E: ID_FS_USAGE=filesystem E: ID_FS_UUID=544872EF4872CF6C E: ID_FS_UUID_ENC=544872EF4872CF6C E: MAJOR=254 E: MINOR=1 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=99808 root@nyws:~# udevadm info /dev/mapper/jmicron_Main2 P: /devices/virtual/block/dm-2 N: dm-2 S: disk/by-id/dm-name-jmicron_Main2 S: disk/by-id/dm-uuid-DMRAID-jmicron_Main2 S: disk/by-uuid/8ec92c5a-06f7-4d94-8c44-a99125f0b5a3 E: DEVLINKS=/dev/disk/by-id/dm-name-jmicron_Main2 /dev/disk/by-id/dm-uuid-DMRAID-jmicron_Main2 /dev/disk/by-uuid/8ec92c5a-06f7-4d94-8c44-a99125f0b5a3 E: DEVNAME=/dev/dm-2 E: DEVPATH=/devices/virtual/block/dm-2 E: DEVTYPE=disk E: DM_ACTIVATION=1 E: DM_NAME=jmicron_Main2 E: DM_SUSPENDED=0 E: DM_UDEV_DISABLE_DM_RULES_FLAG=1 E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1 E: DM_UDEV_PRIMARY_SOURCE_FLAG=1 E: DM_UDEV_RULES=1 E: DM_UUID=DMRAID-jmicron_Main2 E: ID_FS_TYPE=swap E: ID_FS_USAGE=other E: ID_FS_UUID=8ec92c5a-06f7-4d94-8c44-a99125f0b5a3 E: ID_FS_UUID_ENC=8ec92c5a-06f7-4d94-8c44-a99125f0b5a3 E: ID_FS_VERSION=1 E: MAJOR=254 E: MINOR=2 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=2256 root@nyws:~# udevadm info /dev/mapper/jmicron_Main3 P: /devices/virtual/block/dm-3 N: dm-3 S: disk/by-id/dm-name-jmicron_Main3 S: disk/by-id/dm-uuid-DMRAID-jmicron_Main3 S: disk/by-uuid/6c5d2303-22eb-47cb-90ec-2e12daf612a1 E: DEVLINKS=/dev/disk/by-id/dm-name-jmicron_Main3 /dev/disk/by-id/dm-uuid-DMRAID-jmicron_Main3 /dev/disk/by-uuid/6c5d2303-22eb-47cb-90ec-2e12daf612a1 E: DEVNAME=/dev/dm-3 E: DEVPATH=/devices/virtual/block/dm-3 E: DEVTYPE=disk E: DM_ACTIVATION=1 E: DM_NAME=jmicron_Main3 E: DM_SUSPENDED=0 E: DM_UDEV_DISABLE_DM_RULES_FLAG=1 E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1 E: DM_UDEV_PRIMARY_SOURCE_FLAG=1 E: DM_UDEV_RULES=1 E: DM_UUID=DMRAID-jmicron_Main3 E: ID_FS_TYPE=ext4 E: ID_FS_USAGE=filesystem E: ID_FS_UUID=6c5d2303-22eb-47cb-90ec-2e12daf612a1 E: ID_FS_UUID_ENC=6c5d2303-22eb-47cb-90ec-2e12daf612a1 E: ID_FS_VERSION=1.0 E: MAJOR=254 E: MINOR=3 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=5775 root@nyws:~# udevadm info /dev/mapper/jmicron_Main4 P: /devices/virtual/block/dm-4 N: dm-4 S: disk/by-id/dm-name-jmicron_Main4 S: disk/by-id/dm-uuid-DMRAID-jmicron_Main4 S: disk/by-label/Data S: disk/by-uuid/008008E58008E2D0 E: DEVLINKS=/dev/disk/by-id/dm-name-jmicron_Main4 /dev/disk/by-id/dm-uuid-DMRAID-jmicron_Main4 /dev/disk/by-label/Data /dev/disk/by-uuid/008008E58008E2D0 E: DEVNAME=/dev/dm-4 E: DEVPATH=/devices/virtual/block/dm-4 E: DEVTYPE=disk E: DM_ACTIVATION=1 E: DM_NAME=jmicron_Main4 E: DM_SUSPENDED=0 E: DM_UDEV_DISABLE_DM_RULES_FLAG=1 E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1 E: DM_UDEV_PRIMARY_SOURCE_FLAG=1 E: DM_UDEV_RULES=1 E: DM_UUID=DMRAID-jmicron_Main4 E: ID_FS_LABEL=Data E: ID_FS_LABEL_ENC=Data E: ID_FS_TYPE=ntfs E: ID_FS_USAGE=filesystem E: ID_FS_UUID=008008E58008E2D0 E: ID_FS_UUID_ENC=008008E58008E2D0 E: MAJOR=254 E: MINOR=4 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=8190 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWU3QzAAoJEMXQWOS9aK7bucQP/jD/M0a/wcQE5e/x2uX4Sod+ ++ipcH2/qB3Fe4W/67lGXlFLiEuGW6m72ZXwVisky58Zg3wuG6xXdj+2Cu/j48FX JaGr+BIXu20tUQx910EbqZFyz3rkdKxsaU+sNlBnNhVCfJzNXBDJhQu+0iqX5+w+ FNbopu6p7Gh7ULwrO3y+CjUjpkRmdtWKMld5oTJO/oy39yHTnEzv+VCBfpXhYB3A LkVdxhU+FyUkTyazcqTaEBi57Zyn914ecIR5qE1P/+6iK5byX2vDPZjuc+tFF8aM RfBXyoEuVStcuCqReYLuUoQZxNIgOIYr2yM4aFexc3gFbCbjxzTc/nmme9qv+geP
Bug#876907: same here ...
found 876907 4:5.8.6-2.1 thanks Same happens on stretch. And is quite annoying ... Looks like changing virtual desktop is not the only way to reproduce it. It happens on some other window manager (new windows appear, etc) related events as well.
Bug#876907: (no subject)
forwarded 876907 https://bugs.kde.org/show_bug.cgi?id=377956 thanks Same issue is mentioned in KDE bug tracker at https://bugs.kde.org/show_bug.cgi?id=377956
Bug#859213: marked as done (x11vnc: stack smashing detected: x11vnc terminated)
01.06.2018 01:52, Mark wrote: > On Wed, 9 May 2018 00:54:58 +0200 Bernhard Ehlers wrote: Just build > x11vnc/0.9.13-6 in Stretch and it indeed solves the issue. Good job Nikita. > As my private build is obsolete now, I will delete them from my server. Best > regards Bernhard > > In the Stretch repository, I am still seeing the 0.9.13-2. -6 is in Testing. > Can someone advise how to request this fix be pushed into Stable (or > Backports)? Last time I mixed stuff from testing, I got thoroughly told off > ;-) Hi. Debian stable repositories are not normally updated with bugfixes unless it is security hole or otherwise grave problem. For backports, manual upload is possible. However, for x11vnc this currently does not worth - you can just use deb files from testing on stretch. It shall install and work without issues. Nikita signature.asc Description: OpenPGP digital signature
Bug#902893: x11vnc: Error in `x11vnc': corrupted size vs. prev_size: 0x000055f181552530
Hello Mortiz.
Please check latest package version from sid/testing.
(it should not have any dependences not available in stretch)
I believe issue with memory corruption is resolved there.
I can't comment on input issue yet, did not face it.
Nikita
> Package: x11vnc
> Version: 0.9.13-2
> Severity: important
>
> Dear Maintainer,
>
> for me x11vnc does not accept any input although I can see the
> remove screen. I use tightvnc viewer 2.6 on windows 7 as the client.
>
> Also, x11vnc shows a memory corruption issue. Output of the session follows.
>
> ###
> #@#
> #@ @#
> #@ ** WARNING ** WARNING ** WARNING ** WARNING ** @#
> #@ @#
> #@YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!!@#
> #@ @#
> #@ This means anyone with network access to this computer @#
> #@ may be able to view and control your desktop.@#
> #@ @#
> #@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
> #@ @#
> #@#
> #@ @#
> #@ You can create an x11vnc password file by running: @#
> #@ @#
> #@ x11vnc -storepasswd password /path/to/passfile @#
> #@ or x11vnc -storepasswd /path/to/passfile @#
> #@ or x11vnc -storepasswd @#
> #@ @#
> #@ (the last one will use ~/.vnc/passwd)@#
> #@ @#
> #@ and then starting x11vnc via:@#
> #@ @#
> #@ x11vnc -rfbauth /path/to/passfile@#
> #@ @#
> #@ an existing ~/.vnc/passwd file from another VNC @#
> #@ application will work fine too. @#
> #@ @#
> #@ You can also use the -passwdfile or -passwd options. @#
> #@ (note -passwd is unsafe if local users are not trusted) @#
> #@ @#
> #@ Make sure any -rfbauth and -passwdfile password files@#
> #@ cannot be read by untrusted users. @#
> #@ @#
> #@ Use x11vnc -usepw to automatically use your @#
> #@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @#
> #@ (and prompt you to create ~/.vnc/passwd if neither @#
> #@ file exists.) Under -usepw, x11vnc will exit if it @#
> #@ cannot find a password to use. @#
> #@ @#
> #@ @#
> #@ Even with a password, the subsequent VNC traffic is @#
> #@ sent in the clear. Consider tunnelling via ssh(1): @#
> #@ @#
> #@http://www.karlrunge.com/x11vnc/#tunnelling@#
> #@ @#
> #@ Or using the x11vnc SSL options: -ssl and -stunnel @#
> #@ @#
> #@ Please Read the documention for more info about @#
> #@ passwords, security, and encryption. @#
> #@ @#
> #@http://www.karlrunge.com/x11vnc/faq.html#faq-passwd@#
> #@ @#
> #@ To disable this warning use the -nopw option, or put @#
> #@ 'nopw' on a line in your ~/.x11vncrc file. @#
> #@ @#
> #@#
> ###
> 03/07/2018 04:58:08 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 26307
> 03/07/2018 04:58:08 XOpenDisplay("") failed.
> 03/07/2018 04:58:08 Trying again with XAUTHLOCALHOSTNAME=localhost ...
> 03/07/2018 04:58:08
> 03/07/2018 04:58:08 *** XOpenDisplay failed. No -display or DISPLAY.
> 03/07/2018 04:58:08 *** Trying ":0" in 4 seconds. Press Ctrl-C to abort.
> 03/07/2018 04:58:08 *** 1 2 3 4
> 03/07/2018 04:58:12 *** XOpenDisplay of ":0" successful.
> 03/07/2018 04:58:12
> 03/07/2018 04:58:12 Using X display :0
> 03/07/2018 04:58:12
Bug#905480: typo: piv4 -> ipv4
> Dear Maintainer, > I found typo in man page and some files. > > $ grep -r piv4 . > ./README: all usage modes no IPv4 support is required. > See -nopiv4 > ./.pc/0002-Support-openssl-1.1.0.patch/README: all > usage modes no IPv4 support is required. See -nopiv4 > ./x11vnc/help.c:" all usage modes no IPv4 support is > required. See -nopiv4.\n" > ./x11vnc/README: all usage modes no IPv4 support is > required. See -nopiv4 > ./x11vnc/x11vnc.1:all usage modes no IPv4 support is required. See > \fB-nopiv4.\fR > > I think there should be ipv4. Thank you for reporting that. x11vnc 0.9.13 is obsolete anyway, no more uploads of that codebase are planned. Will switch to versions from http://libvnc.github.io/ I don't know if they still contain these typos. Feel free to check and report upstream if they are still there. Nikita signature.asc Description: OpenPGP digital signature
Bug#879439: want to adopt x11vnc
Hello Andrian. I'm considering adoption of x11vnc debian package which is currently orphaned [1]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879439 You have recently uploaded a version of that package, on behalf of debian-qa [2]. Thus, before retitling bug 879439 to ITA, I'm asking if you are ok with that. [2] https://tracker.debian.org/news/944321/accepted-x11vnc-0913-3-source-into-unstable/ WBR, Nikita Yushchenko signature.asc Description: OpenPGP digital signature
Bug#859213: x11vnc: stack smashing detected: x11vnc terminated
Hi. Thank you for the reminder. As far as I understand, this issue is patched in ubuntu (https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1686084). Did you try their patch? Does it fix the issue for you? I've adopted x11vnc package recently and I will try to go through list of open issues soon. Nikita > This problem is still present in version: x11vnc 0.9.13-5 (sid) > > > > Note: Lots of errors in debian are already fixed in patch in a lots of > bugs! But, lots of package are "orphan"... and you can't upload a simple > patch without going through a traumatizing "adoption". > > > > PS: Sory my bad ingles. :-P > > > > Guillermo Reisch > > UInf - FENF - UdelaR > > > signature.asc Description: OpenPGP digital signature
Bug#805821: systemd does not see existing dmraid volumes
>>> Could you send us a "udevadm info" dump for those devices. >> >> root@nyws:~# udevadm info /dev/mapper/jmicron_Main > > [snip] > > Those udevadm info dumps look ok to me. I don't see anything that would > obviously be wrong. > > Can you still reproduce the issue? > Would be great if you can check again on a buster system. Unfortunately that system block no longer exists. signature.asc Description: OpenPGP digital signature
