Bug#754165: libqt5webkit5: with qt5 from the debian testing repository, qupzilla devel crashes on several websites
Package: libqt5webkit5 Version: 5.3.1+dfsg-2 Severity: important With qt5 from the debian testing repository, qupzilla devel crashes on several websites. The qupzilla maintainer says it is a webkit bug. After downloading qt5 from the qtproject site (qt-opensource- linux-x64-5.3.1.run), and copying three files to /usr/lib/x86_64-linux-gnu, the crashes were gone! The three files i copied are libQt5WebKitWidgets.so.5.3.1, libQt5WebKit.so.5.3.1 and libQt5Widgets.so.5.3.1. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15.3-roje (SMP w/2 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 libqt5webkit5 depends on: ii dpkg 1.17.10 ii libc6 2.19-4 ii libgl1-mesa-glx [libgl1] 10.2.1-2 ii libglib2.0-0 2.40.0-3 ii libgstreamer-plugins-base0.10-0 0.10.36-1.1 ii libgstreamer0.10-00.10.36-1.2 ii libicu52 52.1-4 ii libjpeg8 8d-2 ii libpng12-01.2.50-1 ii libqt5core5a [qtbase-abi-5-3-1] 5.3.1+dfsg-3 ii libqt5gui55.3.1+dfsg-3 ii libqt5network55.3.1+dfsg-3 ii libqt5opengl5 5.3.1+dfsg-3 ii libqt5printsupport5 5.3.1+dfsg-3 ii libqt5qml5 [qtdeclarative-abi-5-3-0] 5.3.1-3 ii libqt5quick5 5.3.1-3 ii libqt5sql55.3.1+dfsg-3 ii libqt5widgets55.3.1+dfsg-3 ii libsqlite3-0 3.8.5-2 ii libstdc++64.9.0-7 ii libwebp5 0.4.0-4.1 ii libx11-6 2:1.6.2-2 ii libxcomposite11:0.4.4-1 ii libxml2 2.9.1+dfsg1-3 ii libxrender1 1:0.9.8-1 ii libxslt1.11.1.28-2 ii multiarch-support 2.19-4 ii zlib1g1:1.2.8.dfsg-1 libqt5webkit5 recommends no packages. libqt5webkit5 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140708101455.6110.69745.reportbug@dll
Bug#746589: [kdm] Time to Get on With This!
This is apparently no widely reported--otherwise the hue-and-cry across Debian-KDE-land would be deafening :-) What do I and the original reporter have in common? We both started out with a relatively recent Debian installer, he 7.4, I 7.5. And then, we both wanted to upgrade it. Bingo. I do not know how he set his up but I used a multi-partition install and not wanting one-big-physical-partition, did not use LVM (probably an error!). Unfortunately, the Debian installer does not let me set this up the way I would want to do so. Throws 90% of the space to home and gives small partitions for everything else. So ... /usr has little room for expansion. May rbind or symlink /usr/local off on that oversized /home or another platter. I remember doing all kinds of tricks like this when I had all of Debian on an 8gig partition. With one terra, I though all this stuff was behind me! /opt -- no room for this at all. So ... same trick. These have little to do with KDE, however. What about /var? This partition begins to fill up, with emails, with logs, etc., until it is pretty darned full. I have had the email system grind to a halt because humongous logs filling the /var partition. KDE still functioned, however. That was KDE3. So, did the original reporter have separate partitions by the installer? How long before the issue started showing up? How much free space (if there be any minimum) does KDE require to log in and start the session? Problem is the /var has loads of smaller stuff. My one choice would be to symlink or rbind /var/mail (presently 40meg, too big, this may be in error due to kmail as well). Cheap enough to try but would like some input here before.
Bug#754200: kde-baseapps-bin: KDE fails to recognize keyboard backlight capabilities on fresh boot
Package: kde-baseapps-bin
Version: 4:4.12.4-1
Severity: normal
Dear Maintainer,
I'm not sure if this is right package to post the bug to. I had a hard
time figuring out which KDE package contains all the power management
stuff.
When I boot my laptop, an Asus G55VW, I notice my Fn+F3/F4 shortcut keys
are useless within KDE, even though 'xev' correctly identifies the keys:
KeyRelease event, serial 46, synthetic NO, window 0x781,
root 0x289, subw 0x0, time 3638383, (105,55), root:(105,78),
state 0x0, keycode 238 (keysym 0x1008ff05, XF86KbdBrightnessUp),
same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 46, synthetic NO, window 0x781,
root 0x289, subw 0x0, time 3639413, (105,55), root:(105,78),
state 0x0, keycode 237 (keysym 0x1008ff06, XF86KbdBrightnessDown),
same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
However, I've noticed that if I log out and log back in, KDE's power
manager is suddenly aware that the keyboard backlight can be changed and
everything works as expected.
It looks like during the booting process KDE starts sooner than upower
or something like that, but I find that strange because screen
brightness keys work all the time.
Furthermore after booting the first time (KDE unaware of keyboard
brightness) I can change the brightness manual through the command like
either by invoking this command:
dbus-send --type=method_call --print-reply=literal --system \
--dest='org.freedesktop.UPower' \
'/org/freedesktop/UPower/KbdBacklight'\
'org.freedesktop.UPower.KbdBacklight.SetBrightness' \
int32:${value}}
(with ${value}} equal to 0,1,2 or 3)
or as superuser:
echo 1 /sys/class/leds/asus::kbd_backlight/brightness
So the hardware works as expected and the kernel seems to be doing what
is supposed to be doing but KDE's power manager seems unable to register
this during the initial boot sequence.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (200, 'unstable'), (175, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13.11.4-desktop.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
Versions of packages kde-baseapps-bin depends on:
ii kde-baseapps-data 4:4.12.4-1
ii kde-runtime4:4.13.1-1
ii libc6 2.19-4
ii libkdecore54:4.13.1-1
ii libkdeui5 4:4.13.1-1
ii libkfile4 4:4.13.1-1
ii libkio54:4.13.1-1
ii libkparts4 4:4.13.1-1
ii libqt4-dbus4:4.8.6+dfsg-2
ii libqt4-xml 4:4.8.6+dfsg-2
ii libqtcore4 4:4.8.6+dfsg-2
ii libqtgui4 4:4.8.6+dfsg-2
ii libstdc++6 4.9.0-7
ii libx11-6 2:1.6.2-2
kde-baseapps-bin recommends no packages.
kde-baseapps-bin suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20140708162743.25076.41770.reportbug@asus-g55vw
Processed: Re: Bug#753835: Sparc too
Processing commands for cont...@bugs.debian.org: tag 753835 pending Bug #753835 [qtmultimedia5-dev] qtmultimedia5-dev: Not installable on hurd due to depends on libqgsttools-p1 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 753835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.140484395131707.transcr...@bugs.debian.org
Processed: tagging 749916
Processing commands for cont...@bugs.debian.org: tags 749916 + pending Bug #749916 [ark] ark: Having upgraded to version 4.13.1, the bug is not resolved. Ark still fails to produce a valid zip archive. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 749916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.140484639115776.transcr...@bugs.debian.org
Bug#753835: Sparc too
On 2014-07-06 17:50, Scott Kitterman wrote: This bug also seems to make qtmultimedia5-dev uninstallable on sparc, which, through a long series of interactions makes korundum unbuildable on sparc which means libokularcore3 can't be decrufted on sparc. No, sparc is affected by the fact that ruby2.1, which is the default ruby, does not build and it has never built on that arch. This causes qtwebkit-opensource-src to be out-of-date, thus still depending on an old qtbase-abi. -- Pino Toscano -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/7ff5c3c64279a58a909d2f3a5f62d...@pino.toscano.name
Bug#752209: About calligra icc profiles packaging.
Hi: Thanks for the report. I've checked the fogra27l.icm file details. It indeed matches the one provided by the (nonfree) icc-profiles. Anyway, according to iccdump: iccdump plugins/colorengines/lcms2/colorprofiles/data/fogra27l.icm [...] tag 1: sig 'cprt' type 'text' offset 396 size 22 Text: No. chars = 14 0x: Public Domain [...] So I think we can consider this file as Public Domain. As you say, it is not licensed under the same terms as the rest of the package but I don't think this make the whole package fails to comply with the Debian policy. Anyway, copyright file may be adjusted and maybe we should add and support dependency on icc-profiles* packages. As an extra, I'm adding some information iccdump provided and which we should verify with upstream: krita/data/profiles/WideGamut.icm (No copyright) krita/data/profiles/sRGB.icm (No copyright) krita/data/profiles/scRGB.icm (© Cyrille Berger) krita25_lcms-builtin-sRGB_g100-truegamma.icc (v4 not supported by iccdump) plugins/colorengines/lcms2/colorprofiles/data/fogra27l.icm (public domain) plugins/colorengines/lcms2/colorprofiles/data/CMY.icm (copyright Sun Microsystems, 1996) Regards, -- Raúl Sánchez Siles -Proud Debian user- Linux registered user #416098 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4428568.k9POQG9YLe@portaka
Bug#746589: marked as done (kdm: DBUS connection error after apt-get dist-upgrade (from deb.7.4))
Your message dated Wed, 9 Jul 2014 00:25:06 +0200 with message-id 20140708222506.gb4...@gnuservers.com.ar and subject line Re: Bug#746589: [kdm] Not enough information to work on this bug has caused the Debian Bug report #746589, regarding kdm: DBUS connection error after apt-get dist-upgrade (from deb.7.4) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 746589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kdm Version: 4:4.8.4-6 Severity: grave Justification: renders package unusable Dear Maintainer, on the clean install (debian 7.4.*): gnome and other utils/pkgs worked best. At some time i'm installed asterisk, that asks me distrib, that i hav'nt any more, and i was been need update system by apt-get dist-upgrade After rebooting, gnome was stopped interract with mouse/keyboard (but utils interract at some case). then i'm triyng apt-get install kde kde installed, but starting X with kde gives same result. in /var/log/kdm.log i'm seen the next: launcher(6235) kdemain: No DBUS session-bus found. Check if you... deinit4: Communication error... -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdm depends on: ii adduser 3.113+nmu3 ii consolekit0.4.5-3.1 ii debconf [debconf-2.0] 1.5.49 ii kde-runtime 4:4.8.4-2 ii kde-wallpapers-default4:4.8.4-1 ii kde-workspace-kgreet-plugins 4:4.8.4-6 ii libc6 2.13-38+deb7u1 ii libck-connector0 0.4.5-3.1 ii libdbus-1-3 1.6.8-1+deb7u1 ii libkdecore5 4:4.8.4-4 ii libkdeui5 4:4.8.4-4 ii libkio5 4:4.8.4-4 ii libknewstuff3-4 4:4.8.4-4 ii libkworkspace4abi14:4.8.4-6 ii libpam0g 1.1.3-7.1 ii libqimageblitz4 1:0.0.6-4 ii libqt4-svg4:4.8.2+dfsg-11 ii libqt4-xml4:4.8.2+dfsg-11 ii libqtcore44:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libstdc++64.7.2-5 ii libx11-6 2:1.5.0-1+deb7u1 ii libxau6 1:1.0.7-1 ii libxdmcp6 1:1.1.1-1 ii libxtst6 2:1.2.1-1+deb7u1 ii lsb-base 4.1+Debian8+deb7u1 Versions of packages kdm recommends: ii gnome-session [x-session-manager] 3.4.2.1-4 ii gnome-session-fallback [x-session-manager] 3.4.2.1-4 ii gnome-terminal [x-terminal-emulator]3.4.1.1-2 ii kde-window-manager [x-window-manager] 4:4.8.4-6 ii kde-workspace 4:4.8.4-6 ii konsole [x-terminal-emulator] 4:4.8.4-2 ii logrotate 3.8.1-4 ii metacity [x-window-manager] 1:2.34.3-4 ii xserver-xephyr [xserver]2:1.12.4-6+deb7u2 ii xserver-xorg [xserver] 1:7.7+3~deb7u1 ii xterm [x-terminal-emulator] 278-4 Versions of packages kdm suggests: ii kde-wallpapers 4:4.8.4-1 ii kdepasswd 4:4.8.4-2 -- debconf information: kdm/stop_running_server_with_children: false * shared/default-x-display-manager: kdm kdm/daemon_name: /usr/bin/kdm ---End Message--- ---BeginMessage--- Control: severity -1 normal Hello, Unfortunately, we are not in a position to help with many unrelated issues as are reported in this bug. The original reporter had issues with their input (mouse and keyboard) before installing KDE, and after that reported that KDE had the same issues. This could be caused by any number of reasons, most likely hardware related. It's impossible for us to do anything about it, since we can't reproduce this. The second report seems to be quite a different problem. It's not clear at all what the specific symptoms of this problem are. The fact that the partitions were not allocated as desired is completely unrelated to KDE, kdm, X, etc. If you have specific issues with a specific package, please open a new bug describing a way to reproduce the problem (and please open one bug per issue). Thanks. -- Inside every large problem is a small problem struggling to get out. -- Hoare's Law of Large Problems
