[Touch-packages] [Bug 1933244] [NEW] Pulseaudio does not remember default input/output device
Public bug reported: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: - On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. - I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again choose my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. - I found a solution, which solves this problem.Deleting of patch 0030-load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio to remember default device. + On my ubuntu 18.04 and 20.04 pulseaudio does not remember default + device. + + I have headset and webcam. When I choose my headset as default + input/output device and it works.But when I logout or reboot/power off + my PC, it again chooses my webcam as default device. It`s so annoying, + after each logout or power off to select defaut device. + + I found a solution, which solves this problem.Deleting of patch 0030 + -load-module-switch-on-connect.patch fixes my problem.So, unloading + module module-switch-on-connect, makes pulseaudio remember default + device. + + I`ve created the issue + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1170 + already, but have not received any feedback. ** Description changed: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. - - I`ve created the issue - https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1170 - already, but have not received any feedback. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1933244 Title: Pulseaudio does not remember default input/output device Status in pulseaudio package in Ubuntu: Confirmed Bug description: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1933244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1973608] [NEW] udev TAG-="uaccess" does not work on ubuntu 22.04
Public bug reported:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
-m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
Udev info:
udevadm info -q all -n /dev/bus/usb/001/007
P: /devices/pci:00/:00:14.0/usb1/1-1
N: bus/usb/001/007
L: 0
E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
E: DEVNAME=/dev/bus/usb/001/007
E: DEVTYPE=usb_device
E: DRIVER=apple-mfi-fastcharge
E: PRODUCT=5ac/12a8/1302
E: TYPE=0/0/0
E: BUSNUM=001
E: DEVNUM=007
E: MAJOR=189
E: MINOR=6
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=2331114479
E: USBMUX_SUPPORTED=1
E: SYSTEMD_WANTS=usbmuxd.service
E: ID_VENDOR=Apple_Inc.
E: ID_VENDOR_ENC=Apple\x20Inc.
E: ID_VENDOR_ID=05ac
E: ID_MODEL=iPhone
E: ID_MODEL_ENC=iPhone
E: ID_MODEL_ID=12a8
E: ID_REVISION=1302
E: ID_SERIAL=Apple_Inc._iPhone_8101000A2DD826B8001E
E: ID_SERIAL_SHORT=8101000A2DD826B8001E
E: ID_BUS=usb
E: ID_USB_INTERFACES=:060101:010100:010200:03:fffe02:fffd01:
E: ID_VENDOR_FROM_DATABASE=Apple, Inc.
E: GPHOTO2_DRIVER=PTP
E: ID_GPHOTO2=1
E: ID_MODEL_FROM_DATABASE=iPhone 5/5C/5S/6/SE
E: ID_PATH=pci-:00:14.0-usb-0:1
E: ID_PATH_TAG=pci-_00_14_0-usb-0_1
E: ID_FOR_SEAT=usb-pci-_00_14_0-usb-0_1
E: COLORD_DEVICE=1
E: COLORD_KIND=camera
E: TAGS=:uaccess:seat:systemd:
E: CURRENT_TAGS=:seat:systemd:
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Confirmed
** Description changed:
+ Ubuntu 22.04.
+ Udev version 249.11-0ubuntu3.1.
+
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
- -m g:sudo:rw -m g:plugdev:rw -m g:2046:rw -m g:2027:rw $env{DEVNAME}"
+ -m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
** Description changed:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
-m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
+
+ Udev info:
+ udevadm info -q all -n /dev/bus/usb/001/007
+ P: /devices/pci:00/:00:14.0/usb1/1-1
+ N: bus/usb/001/007
+ L: 0
+ E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
+ E: DEVNAME=/dev/bus/usb/001/007
+ E: DEVTYPE=usb_device
+ E: DRIVER=apple-mfi-fastcharge
[Touch-packages] [Bug 1794516] Re: systemd-logind does not track all user processes
The problem still exists. ** Tags added: focal ** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1794516 Title: systemd-logind does not track all user processes Status in systemd package in Ubuntu: Confirmed Bug description: In Ubuntu 16.04(xenial) release all user processes are in session scope for example: └─user.slice └─user-200463.slice ├─user@200463.service │ └─init.scope │ ├─5886 /lib/systemd/systemd --user │ └─5888 (sd-pam) └─session-c2.scope ├─ 419 bash ├─ 471 mc ├─ 473 bash -rcfile .bashrc ├─ 1432 bash ├─ 1455 mc ├─ 1457 bash -rcfile .bashrc ├─ 1915 /usr/sbin/sssd -D -f In Ubuntu 18.04 (bionic) some processes are in session scope and other are in user service for example: ├─user.slice │ ├─user-200463.slice │ │ ├─session-84.scope │ │ │ ├─14992 gdm-session-worker [pam/gdm-password] │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3 │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15317 /usr/bin/gnome-shell │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog │ │ │ ├─15345 ibus-daemon --xim --panel disable │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys │ │ │ ├─15510 diodon │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify │ │ │ ├─15516 /usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service │ │ │ ├─15519 /usr/lib/i386-linux-gnu/indicator-application/indicator-application-service │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer │ │ │ ├─15531 nautilus-desktop │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple │ │ │ ├─15711 update-notifier │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor │ │ └─user@200463.service │ │ ├─zeitgeist.service │ │ │ └─15551 /usr/bin/zeitgeist-daemon │ │ ├─gnome-terminal-server.service │ │ │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server │ │ │ ├─15671 bash │ │ │ ├─15682 systemd-cgls │ │ │ └─15683 pager │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor │ │ ├─zeitgeist-fts.service │ │ │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts │ │ ├─at-spi-dbus-bus.service │ │ │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher │ │ │ ├─15277 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 │ │ │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session │ │ ├─dbus.service │ │ │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only │ │ │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets │ │ │ ├─15357 /usr/lib/ibus/ibus-portal │ │ │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server │ │ │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon │ │ │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service │ │ │ └─15602 /usr/lib/dconf/dconf-service │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor │ │ ├─evolution-calendar-factory.service │ │ │ ├─15567 /usr/lib/evolution/evolution-calendar-factory │ │ │ └─15603 /usr/lib/evolution/evolution-calendar
[Touch-packages] [Bug 1794517] Re: Empty Display property in org.freedesktop.login1.session
Problem still exists. ** Tags added: focal ** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1794517 Title: Empty Display property in org.freedesktop.login1.session Status in systemd package in Ubuntu: Confirmed Bug description: In Ubuntu 18.04 when get property of Display variable using DBus org.freedesktop.login1.session get empty value. In Ubuntu 16.04 release these values isn`t empty and get for example Display = :0. I use: Description: Ubuntu 18.04.1 LTS Release: 18.04 Package info: Package: systemd Version: 237-3ubuntu10.3 Priority: important Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian systemd Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 12,9 MB Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), libselinux1 (>= 2.1.9) Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps Recommends: libpam-systemd, dbus, networkd-dispatcher Suggests: systemd-container, policykit-1 Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 1.68~), systemd-shim (<< 10-3~), udev (<< 228-5) Replaces: udev (<< 228-5) Homepage: https://www.freedesktop.org/wiki/Software/systemd Task: minimal, ubuntu-core Supported: 5y Download-Size: 2 947 kB APT-Manual-Installed: yes APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages Description: system and service manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1794517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820854] [NEW] Don't hide GdkWindow on grab failure
Public bug reported: I have problem when always-on-top window appears on screen or after it closing for example terminal menu panel does not react to keyboard button pressing and mouse pointer events. To recreate this problem: 1.Login into ubuntu session; 2.Open terminal; 3.Run for exmaple 'ssh-askpass' (which creates always-on-top-window); 4.Try to press terminal menu buttons (they will not respond); 5.Close 'ssh-askpass' and try again to press terminal toolbar menu buttons (they will not respond); But I found a sollution which helps application panel to react for events while showing or after closing always-on-top window here https://gitlab.gnome.org/GNOME/gtk/commit/2c8b95a518bea2192145efe11219f2e36091b37a This sollution is added to upstream in gtk3.0 for Ubuntu 18.10. I use gtk+3.0_3.22.30-1ubuntu2 version. My OS is - Ubuntu 18.04.2 LTS Release: 18.04. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820854 Title: Don't hide GdkWindow on grab failure Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I have problem when always-on-top window appears on screen or after it closing for example terminal menu panel does not react to keyboard button pressing and mouse pointer events. To recreate this problem: 1.Login into ubuntu session; 2.Open terminal; 3.Run for exmaple 'ssh-askpass' (which creates always-on-top-window); 4.Try to press terminal menu buttons (they will not respond); 5.Close 'ssh-askpass' and try again to press terminal toolbar menu buttons (they will not respond); But I found a sollution which helps application panel to react for events while showing or after closing always-on-top window here https://gitlab.gnome.org/GNOME/gtk/commit/2c8b95a518bea2192145efe11219f2e36091b37a This sollution is added to upstream in gtk3.0 for Ubuntu 18.10. I use gtk+3.0_3.22.30-1ubuntu2 version. My OS is - Ubuntu 18.04.2 LTS Release: 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794516] [NEW] systemd-logind does not track all user processes
Public bug reported: In Ubuntu 16.04(xenial) release all user processes are in session scope for example: └─user.slice └─user-200463.slice ├─user@200463.service │ └─init.scope │ ├─5886 /lib/systemd/systemd --user │ └─5888 (sd-pam) └─session-c2.scope ├─ 419 bash ├─ 471 mc ├─ 473 bash -rcfile .bashrc ├─ 1432 bash ├─ 1455 mc ├─ 1457 bash -rcfile .bashrc ├─ 1915 /usr/sbin/sssd -D -f In Ubuntu 18.04 (bionic) some processes are in session scope and other are in user service for example: ├─user.slice │ ├─user-200463.slice │ │ ├─session-84.scope │ │ │ ├─14992 gdm-session-worker [pam/gdm-password] │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3 │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15317 /usr/bin/gnome-shell │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog │ │ │ ├─15345 ibus-daemon --xim --panel disable │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys │ │ │ ├─15510 diodon │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify │ │ │ ├─15516 /usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service │ │ │ ├─15519 /usr/lib/i386-linux-gnu/indicator-application/indicator-application-service │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer │ │ │ ├─15531 nautilus-desktop │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple │ │ │ ├─15711 update-notifier │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor │ │ └─user@200463.service │ │ ├─zeitgeist.service │ │ │ └─15551 /usr/bin/zeitgeist-daemon │ │ ├─gnome-terminal-server.service │ │ │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server │ │ │ ├─15671 bash │ │ │ ├─15682 systemd-cgls │ │ │ └─15683 pager │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor │ │ ├─zeitgeist-fts.service │ │ │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts │ │ ├─at-spi-dbus-bus.service │ │ │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher │ │ │ ├─15277 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 │ │ │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session │ │ ├─dbus.service │ │ │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only │ │ │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets │ │ │ ├─15357 /usr/lib/ibus/ibus-portal │ │ │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server │ │ │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon │ │ │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service │ │ │ └─15602 /usr/lib/dconf/dconf-service │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor │ │ ├─evolution-calendar-factory.service │ │ │ ├─15567 /usr/lib/evolution/evolution-calendar-factory │ │ │ └─15603 /usr/lib/evolution/evolution-calendar-factory-subprocess --factory all --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx15567x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Cal │ │ ├─evolution-source-registry.service │ │ │ └─15368 /usr/lib/evolution/evolution-source-registry │ │ ├─gvfs-metadata.service │ │ │ └─15643 /usr/lib/gvfs/gvfsd-metadata │ │ ├─gvfs-mtp-volume-monitor.service │ │ │ └─15404 /usr/lib/gvfs/gvfs-mtp-volume-monitor │ │ ├─gvfs-goa-volume-monitor.service │ │ │ └─15413 /usr/lib/gvfs/gvfs-goa-volume-monitor │ │ ├─gvfs-afc-vol
[Touch-packages] [Bug 1794517] [NEW] Empty Display property in org.freedesktop.login1.session
Public bug reported: In Ubuntu 18.04 when get property of Display variable using DBus org.freedesktop.login1.session get empty value. In Ubuntu 16.04 release these values isn`t empty and get for example Display = :0. I use: Description:Ubuntu 18.04.1 LTS Release:18.04 Package info: Package: systemd Version: 237-3ubuntu10.3 Priority: important Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian systemd Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 12,9 MB Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), libselinux1 (>= 2.1.9) Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps Recommends: libpam-systemd, dbus, networkd-dispatcher Suggests: systemd-container, policykit-1 Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 1.68~), systemd-shim (<< 10-3~), udev (<< 228-5) Replaces: udev (<< 228-5) Homepage: https://www.freedesktop.org/wiki/Software/systemd Task: minimal, ubuntu-core Supported: 5y Download-Size: 2 947 kB APT-Manual-Installed: yes APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages Description: system and service manager ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: In Ubuntu 18.04 when get property of Display variable using DBus org.freedesktop.login1.session get empty value. In Ubuntu 16.04 release these values isn`t empty and get for example Display = :0. I use: Description: Ubuntu 18.04.1 LTS Release: 18.04 Package info: Package: systemd Version: 237-3ubuntu10.3 Priority: important Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian systemd Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 12,9 MB Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), libselinux1 (>= 2.1.9) Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps Recommends: libpam-systemd, dbus, networkd-dispatcher Suggests: systemd-container, policykit-1 Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 1.68~), systemd-shim (<< 10-3~), udev (<< 228-5) Replaces: udev (<< 228-5) Homepage: https://www.freedesktop.org/wiki/Software/systemd Task: minimal, ubuntu-core Supported: 5y Download-Size: 2 947 kB APT-Manual-Installed: yes - APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current bionic-updates/main i386 Packages + APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages Description: system and service manager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1794517 Title: Empty Display property in org.freedesktop.login1.session Status in systemd package in Ubuntu: New Bug description: In Ubuntu 18.04 when get property of Display variable using DBus org.freedesktop.login1.session get empty value. In Ubuntu 16.04 release these values isn`t empty and get for example Display = :0. I use: Description: Ubuntu 18.04.1 LTS Release: 18.04 Package info: Package: systemd Version: 237-3ubuntu10.3 Priority: important Section: admin Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian systemd Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 12,9 MB Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), libselinux1 (>= 2.1.9) Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), util-linux (>= 2.27.1), mount (>= 2.26
[Touch-packages] [Bug 1794516] Re: systemd-logind does not track all user processes
** Description changed: In Ubuntu 16.04(xenial) release all user processes are in session scope for example: └─user.slice - └─user-200463.slice - ├─user@200463.service - │ └─init.scope - │ ├─5886 /lib/systemd/systemd --user - │ └─5888 (sd-pam) - └─session-c2.scope - ├─ 419 bash - ├─ 471 mc - ├─ 473 bash -rcfile .bashrc - ├─ 1432 bash - ├─ 1455 mc - ├─ 1457 bash -rcfile .bashrc - ├─ 1915 /usr/sbin/sssd -D -f + └─user-200463.slice + ├─user@200463.service + │ └─init.scope + │ ├─5886 /lib/systemd/systemd --user + │ └─5888 (sd-pam) + └─session-c2.scope + ├─ 419 bash + ├─ 471 mc + ├─ 473 bash -rcfile .bashrc + ├─ 1432 bash + ├─ 1455 mc + ├─ 1457 bash -rcfile .bashrc + ├─ 1915 /usr/sbin/sssd -D -f In Ubuntu 18.04 (bionic) some processes are in session scope and other are in user service for example: ├─user.slice │ ├─user-200463.slice │ │ ├─session-84.scope │ │ │ ├─14992 gdm-session-worker [pam/gdm-password] │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3 │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu │ │ │ ├─15317 /usr/bin/gnome-shell │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog │ │ │ ├─15345 ibus-daemon --xim --panel disable │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys │ │ │ ├─15510 diodon │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify │ │ │ ├─15516 /usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service │ │ │ ├─15519 /usr/lib/i386-linux-gnu/indicator-application/indicator-application-service │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer │ │ │ ├─15531 nautilus-desktop │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple │ │ │ ├─15711 update-notifier │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor │ │ └─user@200463.service │ │ ├─zeitgeist.service │ │ │ └─15551 /usr/bin/zeitgeist-daemon │ │ ├─gnome-terminal-server.service │ │ │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server │ │ │ ├─15671 bash │ │ │ ├─15682 systemd-cgls │ │ │ └─15683 pager │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor │ │ ├─zeitgeist-fts.service │ │ │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts │ │ ├─at-spi-dbus-bus.service │ │ │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher │ │ │ ├─15277 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 │ │ │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session │ │ ├─dbus.service │ │ │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only │ │ │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets │ │ │ ├─15357 /usr/lib/ibus/ibus-portal │ │ │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server │ │ │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon │ │ │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service │ │ │ └─15602 /usr/lib/dconf/dconf-service │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor │ │ ├─evolution-calendar-factory.service │ │ │ ├─15567 /usr/lib/evolution/evolution-calendar-factory │ │ │ └─15603 /usr/lib/evolution/evolution-calendar-factory-subprocess --f
[Touch-packages] [Bug 1799663] [NEW] Headerbars big size in Ambiance and Radiance theme
Public bug reported:
In Ubuntu 18.04 (bionic) in Gnome Flashback(Metacity) session headerbars
have too big size in Ambiance and Radiance theme.
I have resolved this problem by setting in gtk-widgets.ccs file`s
section - .titlebar button .titlebutton - padding: 0;
.titlebar button.titlebutton {
background-clip: padding-box;
color: #3d3c37;
-gtk-icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
box-shadow: none;
border: none;
padding-left: 0;
padding-right: 0;
margin: 0;
padding: 0px; <---here
min-width: 20px;
min-height: 20px;
background-size: 20px 20px;
background-image: -gtk-scaled(url("assets/windowbutton.png"),
url("assets/windowbut...@2.png"),
url("assets/windowbut...@3.png"),
url("assets/windowbut...@4.png"));
background-repeat: no-repeat;
background-position: center;
}
As I have seen in light-themes(14.04+16.04.20180326-0ubuntu1) padding:
0; - exists in Ambiance and Radiance theme.
.titlebar.header-bar .button.titlebutton {
background-clip: padding-box;
border: 1px solid #383734;
color: #3d3c37;
icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
border-radius: 9px;
padding: 0; <--here
box-shadow: none;
background-image: linear-gradient(to top, #5a5955, #75746d 50%, #8e8d88);
}
My OS is:
Description:Ubuntu 18.04.1 LTS
Release:18.04
Package: light-themes
Version: 16.10+18.04.20180421.1-0ubuntu1
Priority: optional
Section: gnome
Source: ubuntu-themes
Origin: Ubuntu
Maintainer: Ubuntu Artwork Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 17,7 MB
Depends: gtk2-engines-murrine (>= 0.90.3+git20100810), humanity-icon-theme,
ubuntu-mono
Homepage: https://launchpad.net/ubuntu-themes
Task: ubuntu-desktop, ubuntukylin-desktop
Supported: 5y
Download-Size: 458 kB
APT-Manual-Installed: no
Description: Light Themes (Ambiance and Radiance)
** Affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic
** Description changed:
In Ubuntu 18.04 (bionic) in Gnome Flashback(Metacity) session headerbars
have too big size in Ambiance and Radiance theme.
I have resolved this problem by setting in gtk-widgets.ccs file`s
section - .titlebar button .titlebutton - padding: 0;
.titlebar button.titlebutton {
- background-clip: padding-box;
- color: #3d3c37;
- -gtk-icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
- box-shadow: none;
- border: none;
- padding-left: 0;
- padding-right: 0;
- margin: 0;
+ background-clip: padding-box;
+ color: #3d3c37;
+ -gtk-icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
+ box-shadow: none;
+ border: none;
+ padding-left: 0;
+ padding-right: 0;
+ margin: 0;
- padding: 0px; <---here
- min-width: 20px;
- min-height: 20px;
- background-size: 20px 20px;
- background-image: -gtk-scaled(url("assets/windowbutton.png"),
- url("assets/windowbut...@2.png"),
- url("assets/windowbut...@3.png"),
- url("assets/windowbut...@4.png"));
- background-repeat: no-repeat;
- background-position: center;
+ padding: 0px; <---here
+ min-width: 20px;
+ min-height: 20px;
+ background-size: 20px 20px;
+ background-image: -gtk-scaled(url("assets/windowbutton.png"),
+ url("assets/windowbut...@2.png"),
+ url("assets/windowbut...@3.png"),
+ url("assets/windowbut...@4.png"));
+ background-repeat: no-repeat;
+ background-position: center;
}
As I have seen in light-themes(14.04+16.04.20180326-0ubuntu1) padding:
0; - exists in Ambiance and Radiance theme.
.titlebar.header-bar .button.titlebutton {
- background-clip: padding-box;
- border: 1px solid #383734;
- color: #3d3c37;
- icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
- border-radius: 9px;
- padding: 0; <--here
- box-shadow: none;
- background-image: linear-gradient(to top, #5a5955, #75746d 50%, #8e8d88);
+ background-clip: padding-box;
+ border: 1px solid #383734;
+ color: #3d3c37;
+ icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
+ border-radius: 9px;
+ padding: 0; <--here
+ box-shadow: none;
+ background-image: linear-gradient(to top, #5a5955, #75746d 50%, #8e8d88);
}
My OS is:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Package: light-themes
Version: 16.10+18.04.20180421.1-0ubuntu1
Priority: optional
Section: gnome
Source: ubuntu-themes
Origin: Ubuntu
Maintainer: Ubuntu Artwork Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 17,7 MB
Depends: gtk2-engines-murrine (>= 0.90.3+git20100810), humanity-icon-theme,
ubuntu-mono
Ho
[Touch-packages] [Bug 1799663] Re: Headerbars big size in Ambiance and Radiance theme
Before adding padding: 0;
** Attachment added: "Before adding padding: 0;"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1799663/+attachment/5204850/+files/%D0%97%D0%BD%D1%96%D0%BC%D0%BE%D0%BA%20%D0%B5%D0%BA%D1%80%D0%B0%D0%BD%D1%83%20%D0%B7%202018-10-24%2012-54-59.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1799663
Title:
Headerbars big size in Ambiance and Radiance theme
Status in Ubuntu theme:
Incomplete
Status in ubuntu-themes package in Ubuntu:
Incomplete
Bug description:
In Ubuntu 18.04 (bionic) in Gnome Flashback(Metacity) session
headerbars have too big size in Ambiance and Radiance theme.
I have resolved this problem by setting in gtk-widgets.ccs file`s
section - .titlebar button .titlebutton - padding: 0;
.titlebar button.titlebutton {
background-clip: padding-box;
color: #3d3c37;
-gtk-icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
box-shadow: none;
border: none;
padding-left: 0;
padding-right: 0;
margin: 0;
padding: 0px; <---here
min-width: 20px;
min-height: 20px;
background-size: 20px 20px;
background-image: -gtk-scaled(url("assets/windowbutton.png"),
url("assets/windowbut...@2.png"),
url("assets/windowbut...@3.png"),
url("assets/windowbut...@4.png"));
background-repeat: no-repeat;
background-position: center;
}
As I have seen in light-themes(14.04+16.04.20180326-0ubuntu1) padding:
0; - exists in Ambiance and Radiance theme.
.titlebar.header-bar .button.titlebutton {
background-clip: padding-box;
border: 1px solid #383734;
color: #3d3c37;
icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
border-radius: 9px;
padding: 0; <--here
box-shadow: none;
background-image: linear-gradient(to top, #5a5955, #75746d 50%, #8e8d88);
}
My OS is:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Package: light-themes
Version: 16.10+18.04.20180421.1-0ubuntu1
Priority: optional
Section: gnome
Source: ubuntu-themes
Origin: Ubuntu
Maintainer: Ubuntu Artwork Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 17,7 MB
Depends: gtk2-engines-murrine (>= 0.90.3+git20100810), humanity-icon-theme,
ubuntu-mono
Homepage: https://launchpad.net/ubuntu-themes
Task: ubuntu-desktop, ubuntukylin-desktop
Supported: 5y
Download-Size: 458 kB
APT-Manual-Installed: no
Description: Light Themes (Ambiance and Radiance)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1799663/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799663] Re: Headerbars big size in Ambiance and Radiance theme
After adding padding: 0;
** Attachment added: "After adding padding: 0;"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1799663/+attachment/5204851/+files/%D0%97%D0%BD%D1%96%D0%BC%D0%BE%D0%BA%20%D0%B5%D0%BA%D1%80%D0%B0%D0%BD%D1%83%20%D0%B7%202018-10-24%2012-55-45.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1799663
Title:
Headerbars big size in Ambiance and Radiance theme
Status in Ubuntu theme:
Incomplete
Status in ubuntu-themes package in Ubuntu:
Incomplete
Bug description:
In Ubuntu 18.04 (bionic) in Gnome Flashback(Metacity) session
headerbars have too big size in Ambiance and Radiance theme.
I have resolved this problem by setting in gtk-widgets.ccs file`s
section - .titlebar button .titlebutton - padding: 0;
.titlebar button.titlebutton {
background-clip: padding-box;
color: #3d3c37;
-gtk-icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
box-shadow: none;
border: none;
padding-left: 0;
padding-right: 0;
margin: 0;
padding: 0px; <---here
min-width: 20px;
min-height: 20px;
background-size: 20px 20px;
background-image: -gtk-scaled(url("assets/windowbutton.png"),
url("assets/windowbut...@2.png"),
url("assets/windowbut...@3.png"),
url("assets/windowbut...@4.png"));
background-repeat: no-repeat;
background-position: center;
}
As I have seen in light-themes(14.04+16.04.20180326-0ubuntu1) padding:
0; - exists in Ambiance and Radiance theme.
.titlebar.header-bar .button.titlebutton {
background-clip: padding-box;
border: 1px solid #383734;
color: #3d3c37;
icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
border-radius: 9px;
padding: 0; <--here
box-shadow: none;
background-image: linear-gradient(to top, #5a5955, #75746d 50%, #8e8d88);
}
My OS is:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Package: light-themes
Version: 16.10+18.04.20180421.1-0ubuntu1
Priority: optional
Section: gnome
Source: ubuntu-themes
Origin: Ubuntu
Maintainer: Ubuntu Artwork Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 17,7 MB
Depends: gtk2-engines-murrine (>= 0.90.3+git20100810), humanity-icon-theme,
ubuntu-mono
Homepage: https://launchpad.net/ubuntu-themes
Task: ubuntu-desktop, ubuntukylin-desktop
Supported: 5y
Download-Size: 458 kB
APT-Manual-Installed: no
Description: Light Themes (Ambiance and Radiance)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1799663/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799663] Re: Headerbars big size in Ambiance and Radiance theme
Patch for padding
** Patch added: "Patch for padding"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1799663/+attachment/5204926/+files/padding.patch
** Changed in: ubuntu-themes (Ubuntu)
Status: Incomplete => New
** Changed in: ubuntu-themes
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1799663
Title:
Headerbars big size in Ambiance and Radiance theme
Status in Ubuntu theme:
New
Status in ubuntu-themes package in Ubuntu:
New
Bug description:
In Ubuntu 18.04 (bionic) in Gnome Flashback(Metacity) session
headerbars have too big size in Ambiance and Radiance theme.
I have resolved this problem by setting in gtk-widgets.ccs file`s
section - .titlebar button .titlebutton - padding: 0;
.titlebar button.titlebutton {
background-clip: padding-box;
color: #3d3c37;
-gtk-icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
box-shadow: none;
border: none;
padding-left: 0;
padding-right: 0;
margin: 0;
padding: 0px; <---here
min-width: 20px;
min-height: 20px;
background-size: 20px 20px;
background-image: -gtk-scaled(url("assets/windowbutton.png"),
url("assets/windowbut...@2.png"),
url("assets/windowbut...@3.png"),
url("assets/windowbut...@4.png"));
background-repeat: no-repeat;
background-position: center;
}
As I have seen in light-themes(14.04+16.04.20180326-0ubuntu1) padding:
0; - exists in Ambiance and Radiance theme.
.titlebar.header-bar .button.titlebutton {
background-clip: padding-box;
border: 1px solid #383734;
color: #3d3c37;
icon-shadow: 0 1px rgba(255, 255, 255, 0.1);
border-radius: 9px;
padding: 0; <--here
box-shadow: none;
background-image: linear-gradient(to top, #5a5955, #75746d 50%, #8e8d88);
}
My OS is:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Package: light-themes
Version: 16.10+18.04.20180421.1-0ubuntu1
Priority: optional
Section: gnome
Source: ubuntu-themes
Origin: Ubuntu
Maintainer: Ubuntu Artwork Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 17,7 MB
Depends: gtk2-engines-murrine (>= 0.90.3+git20100810), humanity-icon-theme,
ubuntu-mono
Homepage: https://launchpad.net/ubuntu-themes
Task: ubuntu-desktop, ubuntukylin-desktop
Supported: 5y
Download-Size: 458 kB
APT-Manual-Installed: no
Description: Light Themes (Ambiance and Radiance)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1799663/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2091647] [NEW] gnome-flashback crashes with segfault libgdk-3.so.0.2409.32
Public bug reported: I have ubuntu 24.04 Linux myhost 6.8.0-49-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 4 02:06:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the desktop after a period of idle time. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) Its randomly happens when I try to unlock screen after idle period of time ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: - I have ubuntu 24.04 - gnome flashback - 3.52.1-2ubuntu1 + I have ubuntu 24.04 + gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the desktop after a period of idle time. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) ** Description changed: I have ubuntu 24.04 gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the desktop after a period of idle time. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) + + Its randomly happens when I try t ounlock screen after idle period of + time ** Description changed: I have ubuntu 24.04 gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the desktop after a period of idle time. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) - Its randomly happens when I try t ounlock screen after idle period of + Its randomly happens when I try to unlock screen after idle period of time ** Description changed: - I have ubuntu 24.04 + I have ubuntu 24.04 + Linux myhost 6.8.0-49-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 4 02:06:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux + gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the desktop after a period of idle time. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) Its randomly happens when I try to unlock screen after idle period of time -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2091647 Title: gnome-flashback crashes with segfault libgdk-3.so.0.2409.32 Status in gtk+3.0 package in Ubuntu: New Bug description: I have ubuntu 24.04 Linux myhost 6.8.0-49-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 4 02:06:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the desktop after a period of idle time. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) Its randomly happens when I try to unlock screen after idle period of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2091647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060676] Re: [SRU] login: remove pam_lastlog.so from config
update to login 4.13+dfsg1-4ubuntu3.3 solved problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2060676 Title: [SRU] login: remove pam_lastlog.so from config Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Noble: Fix Committed Status in shadow source package in Oracular: Fix Released Status in shadow package in Debian: Fix Released Bug description: [ Impact ] * The following line has been found in users logs when trying to log in to their systems: login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory This is the only known occurrence of the log. It occurs when users log in to their systems using a tty, or rather referred to as the 'login' method in shadow/pam etc. This log error message is not present when logging in via ssh, gdm, xdm, or other login methods, as they do not depend on the lastlog binary. * The upload fixes the issue by dropping pam_lastlog.so from all config, as well as not installing the lastlog binary. [ Test Plan ] ``` wget https://releases.ubuntu.com/noble/ubuntu-24.04.1-desktop-amd64.iso qemu-system-x86_64 -boot d -cdrom /path/to/ubuntu-24.04.1-desktop-amd64.iso -m 8192M -smp 2 -hda /tmp/yarf-vm.qcow2 -enable-kvm -device qxl # install the system, and reboot # at the login screen post-reboot, press ctrl+alt+f2 # login via tty journalctl -b 0 --no-pager | grep pam_lastlog.so # and you will see the error message sudo sed '/sessionoptional pam_lastlog.so/d' /etc/pam.d/login # logout # log back in via tty journalctl # check the logs since you logged in, you will not see any mention of pam_lastlog.so ``` * In order to test this after the fix lands in noble proposed, do the same as above, except instead of manuall removing the entry from /etc/pam.d/login, install the version of shadow from proposed, and assert that the log messages are no longer present. [ Where problems could occur ] * It seems extremely improbable anyone would configure login.pam to explicitly *require* pam_lastlog.so, I also can't imagine anyone would create any functionality that'd explicitly *depend* on pam_lastlog.so being *required*. [ Other Info ] * the pam_lastlog.so binary was dropped in shadow/1:4.13+dfsg1-5. Included in this change also is dropping pam_lastlog.so from debian/login.pam. * The version of shadow in oracular is 1:4.15.3-3ubuntu2, and thus this error message isn't present in oracular onwards. * We absolutely *cannot* re-introduce pam_lastlog.so as it was dropped as part of the time_t transition, see commit: https://github.com/linux-pam/linux- pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816 * pam_lastlog2 is depended upon in util-linux after version 2.40-7. We can make changes in shadow going forward that depends on pam_lastlog2 rather than pam_lastlog. But that's not really relevant to the SRU I guess. These changes are planned to be implemented upstream https://bugs.debian.org/cgi- bin/bugreport.cgi?att=0;bug=1068229;msg=39, so likely from Ubuntu's side, we can just wait for the changes. * However, upstream, shadow still doesn't have any mention of lastlog2 in debian/login.pam. So we can't SRU a change to depend on this new lastlog binary, as it's not in devel yet. * We could, however, SRU a change wherein we revert the dropping of pam_lastlog.so in shadow, but this is more involved and would likely be a separate SRU, wherein either that SRU or this one lands. [Original description] Imported from Debian bug http://bugs.debian.org/1068229: Package: libpam-modules Version: 1.5.3-6 Severity: normal I noticed the following line in my logs: login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory I looked in the deb files from snapshot.debian.org, and noticed the last version that had it was 1.5.2-9.1 - starting from 1.5.3-1 it disappeared. Maybe it's fallout from the time_t transition and you're already aware of it, in which case feel free to close. Thanks, -- M -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-modules depends on: ii debconf [debconf-2.0] 1.5.86 ii libaudit1 1:3.1.2-2.1 i
[Touch-packages] [Bug 2091647] Re: gnome-flashback crashes with segfault libgdk-3.so.0.2409.32
** Description changed: - I have ubuntu 24.04 + I have ubuntu 24.04 Linux myhost 6.8.0-49-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 4 02:06:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the - desktop after a period of idle time. + desktop after a period of idle time. The problem occurs only when + external monitor is plugged via HDMI to my laptop. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) Its randomly happens when I try to unlock screen after idle period of time -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2091647 Title: gnome-flashback crashes with segfault libgdk-3.so.0.2409.32 Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I have ubuntu 24.04 Linux myhost 6.8.0-49-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 4 02:06:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux gnome-flashback - 3.52.1-2ubuntu1 gtk3 - 3.24.41-4ubuntu1.2 Currently I cannot leave the laptop unattended as it will crash the desktop after a period of idle time. The problem occurs only when external monitor is plugged via HDMI to my laptop. If I check dmesg, I have the following errors ``` kernel: gnome-flashback[242941]: segfault at 62233ef6f200 ip 7d5952ee59c3 sp 7fffcd3694d0 error 4 in libgdk-3.so.0.2409.32[7d5952e66000+84000] likely on CPU 2 (core 4, socket 0) Its randomly happens when I try to unlock screen after idle period of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2091647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2083020] Re: Backport packages for 24.04.2 HWE stack
Updating to mesa after reboot breaks my system, instead of login screen appears white screen with message system breaks, system error ** Tags added: verification-failed-noble ** Tags removed: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/2083020 Title: Backport packages for 24.04.2 HWE stack Status in OEM Priority Project: New Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-19 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in meson-1.5 package in Ubuntu: New Status in spirv-llvm-translator-19 package in Ubuntu: Invalid Status in libdrm source package in Noble: Fix Committed Status in llvm-toolchain-19 source package in Noble: Fix Committed Status in mesa source package in Noble: Fix Committed Status in meson-1.5 source package in Noble: Fix Committed Status in spirv-llvm-translator-19 source package in Noble: In Progress Bug description: [Impact] The graphics HWE stack from oracular needs to be backported for 24.04.2 libdrm - build-dep of mesa spirv-llvm-translator - build-dep of llvm - note that some symbols changed/added/dropped on certain archs due to older gcc/toolchain, so dh_makeshlibs was overridden to not care about those llvm-toolchain-19 - new source in noble - build-dep of mesa - required for new AMD platforms - needs two uploads: * 1st stage bootstrap build * 2nd stage after spirv-llvm-translator has built against 1st stage mesa - new major release, last of the series (24.2.8) so it has accumulated all the fixes upstream considered worthy for it - new HW support, Lunar Lake, Battlemage.. meson-1.5 - needed by mesa - Conflicts/Replaces meson, because otherwise all of the python lib should be renamed, along with the includes etc so it's not a trivial amount of work - tests disabled because four irrelevant ones fail for some reason, doesn't affect the mesa backport [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA driver after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with oracular, we'd already know if there are serious issues. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
