Bug#993227: gramps: Error installing the PostgreSQL addon into Gramps
Package: gramps Version: 5.1.3-1 Severity: minor X-Debbugs-Cc: jsmith+debb...@alum.mit.edu Dear Maintainer, * What led up to the situation? Trying to install the PostgreSQL addon for Gramps * What exactly did you do (or not do) that was effective (or ineffective)? Ran the Gramps Plugin manager, chose install for postgreSQL * What was the outcome of this action? "The following addon had errors: PostGreSQL" * What outcome did you expect instead? Installation of the addon -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gramps depends on: ii gir1.2-gtk-3.03.24.30-2 ii librsvg2-22.50.3+dfsg-1 ii python3 3.9.2-3 ii python3-bsddb36.2.9-1 ii python3-gi3.40.1-2 ii python3-gi-cairo 3.40.1-2 ii xdg-utils 1.1.3-4.1 Versions of packages gramps recommends: ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-gexiv2-0.10 0.12.1-1 ii gir1.2-osmgpsmap-1.01.2.0-1 ii graphviz2.42.2-5 ii python3-icu 2.5-1+b2 Versions of packages gramps suggests: ii fonts-freefont-ttf20120503-10 ii gir1.2-goocanvas-2.0 2.0.4-1+b1 ii gir1.2-gtkspell3-3.0 3.0.10-1 ii python3-numpy 1:1.19.5-1 ii python3-pil 8.1.2+dfsg-0.3 ii rcs 5.10.0-1 PostgreSQL installed: ii postgresql13+225 all ii postgresql-13 13.4-2 amd64 ii postgresql-client 13+225 all ii postgresql-client-13 13.4-2 amd64 ii postgresql-client-common 225 all ii postgresql-common 225 all ii postgresql-contrib13+225 all ii postgresql-doc13+225 all ii postgresql-doc-13 13.4-2 all ii postgresql-filedump 13.1-1 amd64 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gramps depends on: ii gir1.2-gtk-3.03.24.30-2 ii librsvg2-22.50.3+dfsg-1 ii python3 3.9.2-3 ii python3-bsddb36.2.9-1 ii python3-gi3.40.1-2 ii python3-gi-cairo 3.40.1-2 ii xdg-utils 1.1.3-4.1 Versions of packages gramps recommends: ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-gexiv2-0.10 0.12.1-1 ii gir1.2-osmgpsmap-1.01.2.0-1 ii graphviz2.42.2-5 ii python3-icu 2.5-1+b2 Versions of packages gramps suggests: ii fonts-freefont-ttf20120503-10 ii gir1.2-goocanvas-2.0 2.0.4-1+b1 ii gir1.2-gtkspell3-3.0 3.0.10-1 ii python3-numpy 1:1.19.5-1 ii python3-pil 8.1.2+dfsg-0.3 ii rcs 5.10.0-1 PostgreSQL installed: -- no debconf information -- no debconf information
Bug#932403: Bug932403
I can't reproduce this. I'd guess it is a font-related crash like https://debbugs.gnu.org/30045 If it still happens to you with Emacs 27.1, I suggest you report it upstream with M-x report-emacs-bug.
Bug#484468:
13 years on, if you are still interested in this feature, I suggest you ask for it on the cc-mode mailing list: https://sourceforge.net/p/cc-mode/mailman/cc-mode-help/ where the cc-mode maintainer can hopefully give a definitive answer. No development of cc-mode happens on Debian.
Bug#700808:
This was 8 years and 4 Emacs major releases ago. If this is still an issue with Emacs 27.1, I suggest opening a new report with upstream directly.
Bug#624210:
I can't reproduce this. This report is 10 years old, refers to an Emacs 4 major versions ago, and has seen no comments. I suggest closing it, and opening a new report with upstream Emacs if this is still an issue.
Bug#971444:
Using the recipe from the OP, it works fine for me in Emacs 27.1.
Bug#829321:
I was unable to reproduce this. If it still happens with Emacs 27.1, I encourage you to send a complete, minimal example to the Emacs developers using M-x report-emacs-bug.
Bug#972885:
Gnus no longer exists outside of Emacs. I suggest you report this with M-x report-emacs-bug. I note that `article' is not documented as one of the variables one can use in `gnus-summary-highlight'.
Bug#956443:
I can reproduce this with current Emacs master. I encourage you to report this to the Emacs developers using M-x report-emacs-bug.
Bug#926025:
"X protocol error: BadLength (poly request too large or internal Xlib length error) on protocol request 139" is https://debbugs.gnu.org/37895 (amongst others) This is marked as fixed in Emacs 27.1. If the issue still occurs for you with Emacs 27.1, I suggest reporting it using M-x report-emacs-bug. Reporting Emacs bugs that aren't specific to Debian (eg packaging) as Debian bugs tends not to lead anywhere.
Bug#965291:
I was unable to reproduce this. If it still happens with Emacs 27.1, I encourage you to report it to the Emacs developers with M-x report-emacs-bug. They will need: 1) A complete, minimal example that shows the problem (eg lists exactly which version of helm and its dependencies you installed). 2) The output of addr2line, as per https://www.gnu.org/software/emacs/manual/html_node/emacs/Crashing.html
Bug#904333: Bug904333
I was unable to reproduce this. If it still happens with Emacs 27.1, I encourage you to report it to the Emacs developers with M-x report-emacs-bug.
Bug#794920:
This report was forwarded to https://sourceforge.net/p/docutils/bugs/283/, where it received the comment: "Indeed this feature isn't implemented yet and probably won't be anytime soon." Is there any value in keeping the Debian bug report open, or can it be closed?
Bug#982755:
The emacs-bin-common package does recommend mailutils. That seems an appropriate level of dependency, given that many won't use Emacs for mail at all.
Bug#982756:
Presumably this is https://bugs.debian.org/968955 , an issue in dictionaries-common that was fixed last August.
Bug#944616:
It's disappointing to see Emacs 26.3 fail to propagate to Debian testing for the best part of six months due to this issue. This "FTBS" is a single test failure on mips, in test set-process-filter-t. This test is not present prior to Emacs 26.3. It was added for https://debbugs.gnu.org/36591 , so if anyone is using Debian Emacs on mips, they could try investigating the test failure using the information in that report. Otherwise, skipping the test on mips would allow people on other platforms to get an updated Emacs.
Bug#947801: linux-image-5.3.0-3-amd64: b44 module unable to dma to address
Package: src:linux Version: 5.3.15-1 Severity: normal Dear Maintainer, * What led up to the situation? Had been having lockup with swiotlb getting overloaded, added iommu=force, intel_iommu=on, swiotlb=noforce to fix. Have reduced the swiotlb lockup, but now get a freeze on system with the b44 DMA below * What exactly did you do (or not do) that was effective (or ineffective)? Attempting to figure out b44 parametrs to get DMA to work, searched with google on how to overcome DMA issues * What was the outcome of this action? no luck * What outcome did you expect instead? Reduce DMA issues, stop freezes of system -- Package-specific info: ** Version: Linux version 5.3.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.15-1 (2019-12-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-3-amd64 root=UUID=f0a976b0-b2fa-418b-bdf5-d1666e3c05fb ro iommu=force intel_iommu=on swiotlb=noforce quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 321.030640] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 325.970842] swiotlb_map: 681 callbacks suppressed [ 325.970851] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 325.978046] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 325.985252] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 325.992504] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 325.999757] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 326.007003] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 326.014247] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 326.021437] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 326.028655] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 326.035878] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 330.976083] swiotlb_map: 681 callbacks suppressed [ 330.976092] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 330.983295] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 330.990535] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 330.997751] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 331.005015] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 331.012209] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 331.019415] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 331.026683] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 331.033945] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 331.041102] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 335.981437] swiotlb_map: 681 callbacks suppressed [ 335.981446] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 335.988568] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 335.995770] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 336.010229] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 336.017460] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 336.024678] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 336.031882] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 336.039114] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 336.046375] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 336.053610] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 340.986518] swiotlb_map: 680 callbacks suppressed [ 340.986527] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 340.993788] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 341.000963] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 341.008251] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 341.015466] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 341.022652] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 341.029887] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 341.037124] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 341.044388] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 341.051624] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 345.991870] swiotlb_map: 681 callbacks suppressed [ 345.991880] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 345.999000] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 346.006239] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 346.013465] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 346.020694] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 346.027896] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 346.035155] b44 :03:00.0: Cannot do
Bug#931497:
Not reproducible. (Obviously Debian isn't going to choose to disable font-lock by default in Emacs.)
Bug#935754:
You've misundertood the points being made both in Emacs bug 37156 and Debian bug 916227. LANG=zh_TW aspell -c README Error: No word lists can be found for the language "zh_TW" This is nothing to do with Emacs.
Bug#929567:
See https://debbugs.gnu.org/30045 (fixed in Emacs 26.2).
Bug#918646:
Maybe this helps? http://lists.gnu.org/r/emacs-diffs/2018-12/msg00377.html
Bug#127267:
I wonder if this report is no longer relevant and could be closed? There is no standalone Gnus package any more, and no versioned emacs21 etc packages, so the comments from message#27 no longer seem relevant.
Bug#898550:
reassign 898550 dictionaries-common stop Your backtrace indicates that the error comes from debian-ispell-preprocess-dicts-alist, which is provided by debian-ispell.el from the dictionaries-common package. This is corroborated by the fact that the error disappears with -Q, which prevents loading of such site-lisp files. Perhaps the basic problem is using 'UTF-8 where 'utf-8 is needed.
Bug#883683:
tags 883683 moreinfo unreproducible stop /usr/bin/emacs --xrm 'Emacs.verticalScrollBars:off' seems to work fine for me with GTK Emacs 26.
Bug#910231:
tags 910231 moreinfo unreproducible stop I can't reproduce this. Does it happen with emacs -Q?
Bug#907482:
The filenotify tests are flaky, and often seem to fail for non-Emacs reasons. I suggest you mark that one as unstable if it causes you problems.
Bug#916012:
forwarded 916012 https://debbugs.gnu.org/30045 stop Please note that the upstream report #30045 I referenced is only marked as fixed in Emacs 26.2, not 26.1.
Bug#916012:
See https://debbugs.gnu.org/30045 and similar.
Bug#902025: Any news on the emacs 26 front ?
On Wednesday, 5 December 2018, 09:31:09 GMT-8, Rob Browning wrote: > I believe I did, but additional files have been added to Emacs 26 Please could you list all the files that concern you?
Bug#902025: Any news on the emacs 26 front ?
> It's a question about the Unicode data file license. I've contacted > unicode.org, and finally referred it to the ftp-masters. We'll see what > they determine. > I noticed it while looking at the changes in Emacs 26. For example > IVD_Sequences.txt But this same issue about IVD_Sequences was present in Emacs 24: https://lists.gnu.org/archive/html/emacs-devel/2014-10/msg00742.html Unicode.org did not bother to reply then either. This file still seems to only be relevant to Emacs on OS X, so can't you still just remove it?
Bug#890299:
The crash is (probably) a libotf bug, see https://debbugs.gnu.org/30193, and debian bug#909699.
Bug#909699:
This is a libotf bug. See https://debbugs.gnu.org/30193 According to ldd, gedit does not use libotf.
Bug#883434:
By experiment, this issue is present since Emacs 23.1. Perhaps it therefore does not have to hold up the testing migration of Emacs 25.
Bug#905767:
Just ignore this test. See https://bugs.debian.org/879020 .
Bug#903436:
reassign 903436 wnpp stop It's bad practice to bundle add-ons into the actual Emacs package, so this is better interpreted as a request for a new standalone tramp package. Personally I think this is extremely low priority, since the Tramp maintainer very actively syncs the latest Tramp release into upstream Emacs.
Bug#891063:
This is not an Emacs bug (or a bug at all) IMO. See eg bug#766464 and its many duplicates, or the summary from bug#827639: The problem is that you are using su to start a X/GNOME application as root. su does not clear the environment, so XDG_RUNTIME_DIR points to your users path, and the application running with root privileges changes the permissions. Please stop using su (without -l) or running X apps as root.
Bug#883689:
I think your expectation is incorrect, and that you should add the -c argument to get a new frame.
Bug#883683:
I'd guess that in a GTK Emacs, the GTK scrollbar ignores X resources. Try emacs25-lucid?
Bug#879020:
It's a bad test, please don't waste your time trying to debug it. It fails randomly on other platforms too, and upstream don't know why; ref https://debbugs.gnu.org/24503 You should probably just ignore/disable it.
Bug#875678:
Maybe you have psgml installed? Ref: https://debbugs.gnu.org/24538#19
Bug#871706: sudo apt-get install usrmerge problems with libpam_misc
For libpng12, you previously reported https://bugs.debian.org/766809 . I think I had 1.2.54-4 installed, but maybe the spurious /usr/lib link was still present.
Bug#871706: sudo apt-get install usrmerge problems with libpam_misc
Thanks for the quick response. >> FATAL ERROR:>> Both /lib/x86_64-linux-gnu/libpng12.so.0 and >> /usr/lib/x86_64-linux-gnu/libpng12.so.0 exist. > This is weird, because I see nothing in the package which would create > this link. I don't think that was due to usrmerge, I think it was related to me having both libpng12-0 and libpng16-16 installed (?). usrmerge only gets the blame for everything that happened afterwards. :) > You can boot from a live CD and chroot or add init=/bin/bash to the > kernel > command line. Then fix the libpng thing and keep running usrmerge > until it complets. Thanks for the hint. Adding init=/bin/bash (and changing a ro to rw) worked. I still had some problems to resolve after that: 1. I could not trivially run convert-usrmerge again. It failed because perl could not find libcrypt.so.1. LD_LIBRARY_PATH worked for that. The script completed, but reported a number of broken links. 2. On reboot, /sbin/init failed and the system panicked. ldd /usr/sbin/init revealed a number of missing libraries, eg librt.so.1. The issue was the same in every case. In /usr/lib/x86_64-linux-gnu, librt.so.1 was a circular symlink pointing to /usr/lib/x86_64-linux-gnu/librt.so.1. There was a librt.so.1.usrmerge-broken link pointing to librt-2.24.so, which was correct. So basically I had to rename all the *usrmerge-broken links. The full list of affected items was: libauparse.so.0.usrmerge-broken libnss_nis.so.2.usrmerge-broken libcap.so.2.usrmerge-broken libpam_misc.so.0.usrmerge-broken libext2fs.so.2.usrmerge-broken libply-splash-core.so.4.usrmerge-broken libgcrypt.so.20.usrmerge-broken libresolv.so.2.usrmerge-broken libhistory.so.5.usrmerge-broken librt.so.1.usrmerge-broken libnfsidmap.so.0.usrmerge-brokenlibsmartcols.so.1.usrmerge-broken libnss_compat.so.2.usrmerge-broken libudev.so.1.usrmerge-broken libnss_files.so.2.usrmerge-broken After fixing all these, the system seems ok again.
Bug#871706: Acknowledgement (sudo apt-get install usrmerge problems with libpam_misc)
PS It's surprising that this tool does not default to a dry-run mode of operation, or at least check that there are no name clashes before it starts moving things.
Bug#871706: sudo apt-get install usrmerge problems with libpam_misc
Package: usrmerge Version: 16 Severity: important On testing, I ran: sudo apt-get install usrmerge In hindsight, this was a mistake... It aborted partway through with: FATAL ERROR: Both /lib/x86_64-linux-gnu/libpng12.so.0 and /usr/lib/x86_64-linux-gnu/libpng12.so.0 exist. Now my system is very unwell... su does not work: su: error while loading shared libraries: libpam_misc.so.0: cannot open shared object file: No such file or directory It looks like libpam_misc.so has been partly moved: /lib/x86_64-linux-gnu/libpam_misc.so.0.82.0 exists /lib/x86_64-linux-gnu/libpam_misc.so.0 is a broken link pointing to /usr/lib/x86_64-linux-gnu/libpam_misc.so.0 Since su is setuid, I cannot fix this with eg LD_LIBRARY_PATH. sudo does not work: sudo: unknown uid 1000: who are you? At the moment, I don't know how to fix this. I have no root sessions open on the machine, so I cannot eg simply move libpam_misc.so. :(
Bug#862050:
Emacs 25.2 was uploaded some time ago. This report should be closed.
Bug#868856:
This bug is blocking the migration of the Emacs 25 package. It was apparently fixed in https://packages.qa.debian.org/e/emacs25/news/20170729T201922Z.html but the wrong bug number was cited in the upload message.
Bug#792746: linux: Upgrading to thinkpad T440s laptop to 4.0.8-1 kernel causes external monitors to stop working, with fifo underrun error
Source: linux Version: 4.0.8-1 Severity: important On my thinkpad T440s (Intel graphics), I often use an external (HDMI) monitor via a docking station. With the 3.16.7-ckt11 version of the kernel, this works great. With 4.0.8-1 (current in testing), it doesn't work at all -- it detects that the monitor is there, Xorg.0.log says: [ 103.360] (II) intel(0): switch to mode 3440x1440@60.0 on DP2-1 using pipe 1, position (1920, 0), rotation normal, reflection none [ 104.092] (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none but then the kernel log says: Jul 17 17:10:21 branna kernel: [ 13.488687] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A Jul 17 17:10:21 branna kernel: [ 13.488707] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun and the external monitor stays resolutely blank. The gnome display settings tool thinks that it's active, and that it can be configured; each time I try reconfiguring it I get the fifo underrun error again. But at no point does the external monitor leave power-saving mode. Curiously, if I switch to a text console (ctrl-alt-f1), then the text console *does* appear on both the built-in and external displays. The cause is definitely the kernel, because if I reboot and select the older kernel from the grub menu, while keeping everything else the same, then it works perfectly again. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774742: linux: Screen intermittently goes black while dmesg fills with WARNINGs from intel DRM driver
Source: linux Version: 3.16.0-4-amd64 Severity: important After running a dist-upgrade yesterday (for the first time in a few weeks), the intel graphics driver on my laptop (Thinkpad T440s) has started spewing tons of WARNINGs into my kernel logs, e.g. at suspend/resume (but also other times). And worse, the screen is randomly and intermittently turning itself off altogether for a few seconds, and then turning on again. (This may be triggered by some sort of automatic power savings thing that GNOME is doing, but I can't connect it with anything obvious -- e.g. it might happen 2 seconds after I have been typing, so it doesn't seem to be the dim-after-10-minutes-idle timer going off or anything like that.) Each of these events also causes a similar WARNING spew in the kernel logs. These intermittent blank screens seem to come and go: maybe half the time everything is fine, and then the other half of the time my screen is blinking on and off multiple times per minute and the computer is extremely frustrating to use. uname -a: Linux branna 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux Logs for an interrmittent screen blank: Jan 06 19:54:53 branna kernel: [ cut here ] Jan 06 19:54:53 branna kernel: WARNING: CPU: 3 PID: 9732 at /build/linux- CMiYW9/linux-3.16.7-ckt2/drivers/gpu/drm/i915/intel_display.c:7256 hsw_enable_pc8+0x463/0x5e0 [i915]() Jan 06 19:54:53 branna kernel: CRTC for pipe A enabled Jan 06 19:54:53 branna kernel: Modules linked in: usb_storage ctr ccm pci_stub binfmt_misc vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) bnep nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc nls_utf8 nls_cp437 vfat fat snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic iTCO_wdt iTCO_vendor_support joydev arc4 uvcvideo ecb videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media btusb bluetooth 6lowpan_iphc x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm_intel kvm crc32_pclmul ghash_clmulni_intel iwlmvm aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper mac80211 cryptd efi_pstore evdev psmouse serio_raw pcspkr efivars iwlwifi i2c_i801 rtsx_pci_ms memstick cfg80211 lpc_ich wmi i915 snd_hda_intel snd_hda_controller thinkpad_acpi snd_hda_codec snd_hwdep Jan 06 19:54:53 branna kernel: ac nvram snd_pcm tpm_tis rfkill battery tpm snd_timer drm_kms_helper snd intel_smartconnect soundcore drm video mei_me mei i2c_algo_bit button i2c_core shpchp processor fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 md_mod sg sd_mod crc_t10dif crct10dif_generic rtsx_pci_sdmmc mmc_core crct10dif_pclmul crct10dif_common crc32c_intel ehci_pci xhci_hcd ehci_hcd ahci libahci libata e1000e ptp pps_core scsi_mod rtsx_pci mfd_core usbcore thermal usb_common thermal_sys Jan 06 19:54:53 branna kernel: CPU: 3 PID: 9732 Comm: kworker/3:2 Tainted: G W O 3.16.0-4-amd64 #1 Debian 3.16.7-ckt2-1 Jan 06 19:54:53 branna kernel: Hardware name: LENOVO 20ARA0H300/20ARA0H300, BIOS GJET67WW (2.17 ) 12/10/2013 Jan 06 19:54:53 branna kernel: Workqueue: pm pm_runtime_work Jan 06 19:54:53 branna kernel: 0009 81507263 8801490e3ca8 81065847 Jan 06 19:54:53 branna kernel: 8803100a 8801490e3cf8 8803103ba370 8803108e9098 Jan 06 19:54:53 branna kernel: 810658ac a04e8940 88030020 Jan 06 19:54:53 branna kernel: Call Trace: Jan 06 19:54:53 branna kernel: [81507263] ? dump_stack+0x41/0x51 Jan 06 19:54:53 branna kernel: [81065847] ? warn_slowpath_common+0x77/0x90 Jan 06 19:54:53 branna kernel: [810658ac] ? warn_slowpath_fmt+0x4c/0x50 Jan 06 19:54:53 branna kernel: [a0480f52] ? lpt_disable_clkout_dp+0x62/0xc0 [i915] Jan 06 19:54:53 branna kernel: [a0491893] ? hsw_enable_pc8+0x463/0x5e0 [i915] Jan 06 19:54:53 branna kernel: [a043d895] ? intel_runtime_suspend+0x185/0x860 [i915] Jan 06 19:54:53 branna kernel: [812e0169] ? pci_pm_runtime_suspend+0x59/0x120 Jan 06 19:54:53 branna kernel: [813a74dc] ? __rpm_callback+0x2c/0x80 Jan 06 19:54:53 branna kernel: [813a754f] ? rpm_callback+0x1f/0x80 Jan 06 19:54:53 branna kernel: [813a76b7] ? rpm_suspend+0x107/0x5f0 Jan 06 19:54:53 branna kernel: [813a8b52] ? pm_runtime_work+0x72/0xa0 Jan 06 19:54:53 branna kernel: [8107f5e2] ? process_one_work+0x172/0x420 Jan 06 19:54:53 branna kernel: [8107fc75] ? worker_thread+0x115/0x520 Jan 06 19:54:53 branna kernel: [81509681] ? __schedule+0x2b1/0x710 Jan 06 19:54:53 branna kernel: [8107fb60] ? rescuer_thread+0x2d0/0x2d0 Jan 06 19:54:53 branna kernel: [81085f1d] ? kthread+0xbd/0xe0 Jan 06 19:54:53 branna kernel: [81085e60] ? kthread_create_on_node+0x180/0x180 Jan 06 19:54:53 branna kernel: [8150d27c] ? ret_from_fork+0x7c/0xb0 Jan 06 19:54:53 branna kernel: [81085e60] ?
Bug#751264: awscli: Unconditionally crashes at startup
Package: awscli Version: 1.2.9-2 Severity: grave Justification: renders package unusable Any attempt to run 'aws' crashes with the following traceback: ~$ aws --version Traceback (most recent call last): File /usr/bin/aws, line 23, in module sys.exit(main()) File /usr/bin/aws, line 19, in main return awscli.clidriver.main() File /usr/share/awscli/awscli/clidriver.py, line 44, in main driver = create_clidriver() File /usr/share/awscli/awscli/clidriver.py, line 53, in create_clidriver event_hooks=emitter) File /usr/share/awscli/awscli/plugin.py, line 49, in load_plugins plugin.awscli_initialize(event_hooks) File /usr/share/awscli/awscli/handlers.py, line 73, in awscli_initialize register_removals(event_handlers) File /usr/share/awscli/awscli/customizations/removals.py, line 32, in register_removals 'verify-email-address']) File /usr/share/awscli/awscli/customizations/removals.py, line 45, in remove self._create_remover(remove_commands)) File /usr/lib/python3/dist-packages/botocore/hooks.py, line 64, in register self._verify_accept_kwargs(handler) File /usr/lib/python3/dist-packages/botocore/hooks.py, line 84, in _verify_accept_kwargs argspec = inspect.getargspec(func) File /usr/lib/python3.4/inspect.py, line 930, in getargspec raise ValueError(Function has keyword-only arguments or annotations ValueError: Function has keyword-only arguments or annotations, use getfullargspec() API which can support them -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awscli depends on: ii python3 3.4.1~rc1-1 ii python3-bcdoc 0.12.0-2 ii python3-botocore 0.29.0+repack-2 ii python3-colorama 0.2.5-0.2 ii python3-docutils 0.11-3 ii python3-rsa 3.1.2-1 ii python3-six 1.6.1-2 pn python3:any none awscli recommends no packages. awscli suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#114849:
Note that the default value of mail-interactive changed from nil to t in Emacs 23.1. If you still feel there is something more that needs to be done, I'd suggest reporting it directly to bug-gnu-em...@gnu.org (and closing this Debian report). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745984: linux: CrashPlan (proprietary backup software) malfunctions when uname -r does not contain a 3-part version number
Source: linux
Severity: normal
CrashPlan is a backup product:
http://crashplan.com
They're unusual in this space in that their cloud backup hosting service is a
bazillion times cheaper than everyone else's, and they have full Linux support.
The downside is that you have to use their proprietary backup software (though,
to be fair, it is substantially more featureful than any FOSS equivalent).
However, it apparently also contains a truly terrible bit of code which
attempts to figure out whether the kernel supports inotify by looking at the
kernel version number, and if the kernel version number does not contain 2
dots, then it assumes inotify is *not* available, and disables live filesystem
watching. The effect in practice is that backups are pretty much silently
disabled, so it's seriously dire. And unfortunately, on Debian:
~$ uname -r
3.13-1-amd64
Quoting a response from their customer support:
-
Thank you for contacting Code42 support. Yes, this is a known issue, usually
affecting pre-release Debian users. Here is the notes from Engineering on the
issue:
Our validation of the kernel version is looking for two separating periods and
the realtime file watcher fails to run if this is not found:
From InotifyManager.java, lines 164-170:
/* Kernel versions always have three distinct digits */
String[] versions = m.group(1).split(\.);
if (versions.length 3) {
log.info(Inadequate kernel version information: + m.group());
return false;
}
We don't have a fix/patch yet, but it looks like it is in the queue to be
looked at, and hopefully a resolution will be pushed out soon. Let me know if I
can answer anything else. Thanks!
--
I'm not sure if Debian should do anything about this, given that it's clearly a
bug in a piece of proprietary software, not in Debian itself. But it is the
case that Debian's handling of the Linux release field is causing real-world
interoperability problems with software that works on (AFAIK) all non-Debian
Linux systems. And if nothing else it's probably helpful for this information
to be recorded somewhere public.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592802: (no subject)
tags 592802 wontfix close 592802 stop That's just how Emacs works. Adding a directory to the load-path does not cause everything in there to be loaded. You have to load (or require) the relevant library as a separate step. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690317:
tags 690317 moreinfo stop PGG is obsolete since Emacs 24.1, replaced by EasyPG. In any case, without a recipe to reproduce this state, nothing can be done. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681392:
severity 681392 wishlist stop The files in /etc/emacs/site-start.d/ are tiny files that mainly just (auto)load other files. Compiling them would bring no visible benefit, and introduce extra complication. Since Debian compiles separate elc files for each Emacs version, you would need to add Emacs-version-specific site-start.d directories for this to work. Do you have any measurable data that shows why it's desirable to compile these files? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679753:
This is fixed upstream. See http://lists.gnu.org/archive/html/emacs-diffs/2013-10/msg00204.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726251:
This is a feature. The idea is that you start the commit log with header lines (eg Author: whoever), then have a blank line, then have the commit message. The blank line is font-locked as a thin bar to indicate it separates the header from the body. http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14382 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691345:
IIUC, this should be fixed in Emacs 24.3. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720775: emacs24-common: sh-learn-buffer-indent fails
This was fixed upstream. (To contact Emacs upstream, always mail bug-gnu-emacs@gnu rather than the original file author, who in many cases is no longer the maintainer.) Ref: http://lists.gnu.org/archive/html/emacs-diffs/2013-10/msg00165.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#476946: also affects phpbb
This bug also affects phpbb, which uses dbconfig-common. Thanks, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#418832: Build fails in Qt 4.2.1 due to known bug
Package: libqt4-core Version: 4.2.1-2+b1 My application fails to build when the QT_NO_DEBUG_OUTPUT define is made. This was a known bug in Qt 4.2 which was fixed in v4.2.2; see this Trolltech tracker issue: http://www.trolltech.com/developer/task-tracker/index_html?method=entryid=133796 Build fails with errors like these (I use CMake for configure, hence the output style): [ 54%] Building CXX object CMakeFiles/qtm.dir/catkin.o /usr/include/qt4/QtCore/qglobal.h:1250: error: expected unqualified-id before ‘if’ /usr/include/qt4/QtCore/qglobal.h:1250: error: expected unqualified-id before ‘else’ make[2]: *** [CMakeFiles/qtm.dir/catkin.o] Error 1 make[1]: *** [CMakeFiles/qtm.dir/all] Error 2 make: *** [all] Error 2 I use this macro to control my own debug output, not just to suppress Qt's own. I would add that the latest patch release (4.2.3) fixes a bug which causes the scroll bar to fail to appear in QTextEdit widgets when text starts to go beyond the widget's size. This is important to me as my application uses that class heavily. I suggest that Qt 4 be updated at least to version 4.2.2. I am using Debian Etch, kernel 2.6.18-4-686, libc6 v2.3.6.ds1-13. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
