Bug#805389: signon-ui: runaway dbus-daemon during build
On Thu, 7 Apr 2016, Diane Trout wrote: > I wasn't able to replicate this issue with an amd64-unstable sbuild chroot on > my system. I ran it in several times in case it was a intermittent failure. > > for a in $(seq 10) ; do sbuild -c unstable-amd64-sbuild signon- > ui_0.17+15.10.20150810-2.dsc ; done > > Do you have any thoughts what might be different about our build environments? I can reproduce it every time. My system is a QEMU/KVM virtual machine with 4GB RAM + 4GB swap running jessie. I'm using sbuild 0.68.0-1~bpo8+1 from jessie-backports. I call sbuild this way: sbuild -A -d stretch signon-ui_0.17+15.10.20150810-2 The build happens normally but only until this point: [...] dpkg-genchanges: warning: package signon-ui-x11-dbgsym listed in files list but not in control info dpkg-genchanges: binary-only upload (no source code included) dpkg-source --after-build signon-ui-0.17+15.10.20150810 dpkg-buildpackage: binary-only upload (no source included) --- At this point, it hangs and does nothing else. When you finally kill the dbus-daemon process by hand, the remaining build log appears: --- Build finished at 20160408-0111 Finished [...] --- Hope this helps. Thanks.
Processed: libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together
Processing control commands: > found -1 4:15.12.1-1 Bug #820447 [libkf5libkdepim5,oxygen5-icon-theme] libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together There is no source info for the package 'oxygen5-icon-theme' at version '4:15.12.1-1' with architecture '' Marked as found in versions kdepim/4:15.12.1-1. > found -1 5.19.0-1 Bug #820447 [libkf5libkdepim5,oxygen5-icon-theme] libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together There is no source info for the package 'libkf5libkdepim5' at version '5.19.0-1' with architecture '' Marked as found in versions oxygen-icons5/5.19.0-1. -- 820447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#820447: libkf5libkdepim5,oxygen5-icon-theme: error when trying to install together
Package: libkf5libkdepim5,oxygen5-icon-theme Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 4:15.12.1-1 Control: found -1 5.19.0-1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libkf5libkdepim5. Preparing to unpack .../libkf5libkdepim5_4%3a15.12.1-1_amd64.deb ... Unpacking libkf5libkdepim5 (4:15.12.1-1) ... dpkg: error processing archive /var/cache/apt/archives/libkf5libkdepim5_4%3a15.12.1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/icons/oxygen/128x128/mimetypes/x-mail-distribution-list.png', which is also in package oxygen5-icon-theme 5.19.0-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for experimental/amd64, which may be slightly out of sync): usr/share/icons/oxygen/128x128/mimetypes/x-mail-distribution-list.png usr/share/icons/oxygen/16x16/mimetypes/x-mail-distribution-list.png usr/share/icons/oxygen/22x22/mimetypes/x-mail-distribution-list.png usr/share/icons/oxygen/256x256/mimetypes/x-mail-distribution-list.png usr/share/icons/oxygen/32x32/mimetypes/x-mail-distribution-list.png usr/share/icons/oxygen/48x48/mimetypes/x-mail-distribution-list.png This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html oxygen5-icon-theme=5.19.0-1_libkf5libkdepim5=4%15.12.1-1.log.gz Description: application/gzip
Bug#820478: okular-extra-backends: cannot open epub even with extra-backends package installed
Package: okular-extra-backends Version: 4:15.08.3-1 Severity: normal Hello, I have just installed the okular-extra-backends package and am unable to open .epub files with Okular, which the package description says I should be able to do. When I try to open any ePub document I get a dialog saying: "Could not open /path/to/myfile.epub" (replace with proper path) The main UI window also indicates: "Can not find a plugin which is able to handle the document being passed". Let me know what I can do to help fix and test this. After installing the extra-backends package ePub files have been associated with Okular, which they weren't before so it's further indication that the program should be able to handle them. The files open fine on fbreader. I'd also like to question why isn't the extra-backends package recommended instead of suggested (which would make it install by default on some package managers like aptitude). Especially due to the epub capability I think it should be recommended, as I see many people on the web ask about epub readers for Linux and Okular's premise of being a all-in-one reader makes it perfect as an ebook reader. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/8 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) Versions of packages okular-extra-backends depends on: ii libc6 2.22-5 ii libchm1 2:0.40a-3+b1 ii libdjvulibre21 3.5.27.1-5 ii libepub00.2.2-4+b1 ii libkdecore5 4:4.14.14-1+b1 ii libkdeui5 4:4.14.14-1+b1 ii libkhtml5 4:4.14.14-1+b1 ii libkio5 4:4.14.14-1+b1 ii libokularcore6 4:15.08.3-1 ii libqt4-xml 4:4.8.7+dfsg-6 ii libqtcore4 4:4.8.7+dfsg-6 ii libqtgui4 4:4.8.7+dfsg-6 ii libstdc++6 5.3.1-13 ii libtiff54.0.6-1 Versions of packages okular-extra-backends recommends: ii okular 4:15.08.3-1 okular-extra-backends suggests no packages. -- no debconf information
Bug#794110: More info needed
Le mercredi 16 mars 2016, 10:16:18 Lisandro Damián Nicanor Pérez Meyer a écrit : > tag 794110 moreinfo > thanks > > Hi everyone! With my Qt maintainer hat on, I would like you to give me some > info. > > First: We have only one backtrace coming from the original submitter. Can > the rest of you check if when a crash happens the current thread's (the > crashing one) backtrace says something like: Hi Lisandro, I hope you are doing well. Sorry for the late answer, I was in the middle of a relocation and didn't touch my computer much. I haven't had any crash since I have so the bug seems to be solved on my side. I'll update the bug report if I ever get a new crash in the following (14) days but I don't expect to. Best regards, Thomas signature.asc Description: This is a digitally signed message part.
