Bug#789599: gnome-settings-daemon: fn+fx buttons does not work after update
Package: gnome-settings-daemon
Version: 3.16.2-3
Severity: important
Dear Maintainer,
After update of gnome-settings-daemon(actually a lot of gnome packages, but
I
guess problem is in gnome-settings-daemon, correct me if I wrong) fn+fx
buttons
stopped working for me(Laptop lenovo u330p).
When I try to use any of these hotkeys(e.g. volume up) following message
appears in syslog:
Jun 22 15:19:37 u330p gnome-session[3159]: (gnome-settings-daemon:3221):
GLib-
GIO-WARNING **: Dropping signal AcceleratorActivated of type (uuu) since the
type from the expected interface is (ua{sv})
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages gnome-settings-daemon depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2
ii gsettings-desktop-schemas3.16.1-1
ii libc62.19-18
ii libcairo21.14.2-2
ii libcanberra-gtk3-0 0.30-2.1
ii libcanberra0 0.30-2.1
ii libcolord2 1.2.1-1+b2
ii libcups2 1.7.5-12
ii libfontconfig1 2.11.0-6.3
ii libgdk-pixbuf2.0-0 2.31.4-2
ii libgeocode-glib0 3.16.2-1
ii libglib2.0-0 2.44.1-1
ii libgnome-desktop-3-103.16.2-2
ii libgtk-3-0 3.16.4-2
ii libgudev-1.0-0 230-1
ii libgweather-3-6 3.16.1-1
ii liblcms2-2 2.6-3+b3
ii libnm-glib4 1.0.2-2
ii libnm-util2 1.0.2-2
ii libnotify4 0.7.6-2
ii libnspr4 2:4.10.8-2
ii libnss3 2:3.19.1-2
ii libpackagekit-glib2-18 1.0.6-1
ii libpam-systemd 215-18
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libpolkit-gobject-1-00.105-8
ii libpulse-mainloop-glib0 6.0-2
ii libpulse06.0-2
ii librsvg2-2 2.40.9-2
ii libupower-glib3 0.99.3-1+b1
ii libwacom20.8-1
ii libwayland-client0 1.8.1-1
ii libx11-6 2:1.6.3-1
ii libxext6 2:1.3.3-1
ii libxi6 2:1.7.4-1+b2
ii libxtst6 2:1.2.2-1+b1
ii nautilus-data3.14.2-1
Versions of packages gnome-settings-daemon recommends:
ii pulseaudio 6.0-2
Versions of packages gnome-settings-daemon suggests:
ii gnome-screensaver3.6.1-4
ii metacity [x-window-manager] 1:3.14.3-1
ii mutter [x-window-manager]3.14.4-2+b1
ii openbox [x-window-manager] 3.5.2-8
ii x11-xserver-utils7.7+4
-- no debconf information
Bug#789599:
win+L(lock screen hotkey) Does not work too, with same log message
Bug#789599:
Thanks for the hint, that fixed the problem
Bug#766420:
Hi, complete removal(with aptitude remove) and then installing chromium again solved this issue for me. I guess dpkg cannot handle situation when there is directory with same name as file that should be installed.
Bug#767697: chromium: icons' location does not conform to freedesktop.org standard
Package: chromium Version: 38.0.2125.101-3.1 Severity: minor Dear Maintainer, package installs icons to /usr/share/icons/hicolor//, but they should be in /usr/share/icons/hicolor//apps/. This issue in conjunctions with bug #766420 causes that gnome could not find icon for chromium at all. Attached patch fixes the problem. I'm not sure that I did patch right, never did them before. Sorry in that case. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii libasound2 1.0.28-1 ii libc62.19-12 ii libcairo21.12.16-5 ii libcap2 1:2.24-6 ii libcups2 1.7.5-5 ii libdbus-1-3 1.8.8-2 ii libexpat12.1.0-6 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgnome-keyring03.12.0-1+b1 ii libgtk2.0-0 2.24.25-1 ii libharfbuzz0b0.9.35-1 ii libjpeg62-turbo 1:1.3.1-8 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpci3 1:3.2.1-3 ii libspeechd2 0.8-6 ii libspeex11.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1.1 ii libstdc++6 4.9.1-16 ii libudev1 215-5+b1 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1 ii libxdamage1 1:1.1.4-2 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2 ii libxi6 2:1.7.4-1 ii libxml2 2.9.1+dfsg1-4 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxslt1.1 1.1.28-2+b1 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1 ii xdg-utils1.1.0~rc1+git20111210-7.1 chromium recommends no packages. Versions of packages chromium suggests: ii chromium-inspector 38.0.2125.101-3 pn chromium-l10n -- no debconf information diff --git a/debian/chromium.links b/debian/chromium.links index fe0fba3..4b06380 100644 --- a/debian/chromium.links +++ b/debian/chromium.links @@ -1,2 +1,2 @@ -usr/share/icons/hicolor/32x32/chromium.xpm usr/share/pixmaps/chromium.xpm -usr/share/icons/hicolor/48x48/chromium.png usr/share/pixmaps/chromium.png +usr/share/icons/hicolor/32x32/apps/chromium.xpm usr/share/pixmaps/chromium.xpm +usr/share/icons/hicolor/48x48/apps/chromium.png usr/share/pixmaps/chromium.png diff --git a/debian/rules b/debian/rules index f22616a..9ac2488 100755 --- a/debian/rules +++ b/debian/rules @@ -124,7 +124,7 @@ override_dh_auto_install: for file in $(shell find chrome/app/theme/chromium -name product_logo_[0-9]* -a ! -name *mono*); do \ ext=$$(echo $$file | cut -d\. -f2); \ siz=$$(echo $$file | cut -d_ -f3 | sed s/\.$$ext//); \ - dst=debian/chromium/usr/share/icons/hicolor/$$siz\x$$siz; \ + dst=debian/chromium/usr/share/icons/hicolor/$$siz\x$$siz/apps; \ mkdir -p $$dst; \ cp $$file $$dst/chromium.$$ext; \ done
Bug#767735: gnucash: Does not display any graphs using any stylesheet
Hi all, I have same problem in reports. Grid is drawn but no charts are displayed. This happens only with stacked bars, if I uncheck "Use stacked Bars" in Edit report options, graphs appear again. But non stacked bar charts are mostly useless.
Bug#832622: clang-3.9: Uninstallable in unstable
I have encountered this bug too. I found following workaround so far: First removing llvm-3.9-dev package: apt remove llvm-3.9-dev Then installing them together: apt install llvm-3.9-dev clang-3.9
