[Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config
This is fixed now right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1991592 Title: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config Status in openssh package in Ubuntu: Triaged Bug description: A criticism of the existing sshd socket activation implementation is that Port/ListenAddress options are migrated on a one-time basis at package upgrade time, and afterwards users get the surprising behavior that Port/ListenAddress settings added to sshd_config are ignored. A systemd generator could be used to change the ssh socket unit configuration on boot, and on each change of /etc/ssh/sshd_config. Sample implementation from Dimitri: ssh.socket: [Unit] Wants=sshd-config.path # # Note the below defaults are cleared and overriden by #/lib/systemd/system-generators/sshd-generator # based on the sshd config from the sshd -T output # ListenStream=[::]:22 ListenStream=0.0.0.0:22 diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path new file mode 100644 index 0..cfa9674a3 --- /dev/null +++ b/systemd/sshd-config.path @@ -0,0 +1,4 @@ +[Unit] +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run +[Path] +PathChanged=/etc/ssh/sshd_config diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service new file mode 100644 index 0..b009ea52c --- /dev/null +++ b/systemd/sshd-config.service @@ -0,0 +1,5 @@ +[Unit] +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in + +[Service] +ExecStart=/bin/systemctl daemon-reload diff --git a/systemd/sshd-generator b/systemd/sshd-generator new file mode 100755 index 0..72c6aac04 --- /dev/null +++ b/systemd/sshd-generator @@ -0,0 +1,10 @@ +#!/bin/sh +set -eu +mkdir -p /run/sshd +sshd -t +mkdir -p $1/ssh.socket.d +target="$1/ssh.socket.d/ssh-listen.conf" +echo '[Socket]' > $target +echo 'ListenStream=' >> $target +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target +rmdir --ignore-fail-on-non-empty /run/sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Yeah... A missing fixup on a cherry-pick... Maybe we should re-upload this? Would that be accepted? I guess should be changed to 1.18.04.1 or what? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Bionic: In Progress Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
** Description changed: + [ Impact ] + In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. + + [ Test case ] + + Note: this only tests the appindicator-side that may have lead to + "activating" the application, it's not something that will fix the + applications issues that is a QT bug. + + 1. Start a QT application with indicator +(after gnome-shell has started; e.g. clementine, barrier...) + 2. The applindicator menu with shell theme should appear + 3. No activation happens on the application (e.g. the window is not opened) + + [ Regression potential ] + + Mouse events aren't properly exposed to the indicators ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Fix Committed ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: qtbase-opensource-src (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-appindicator (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen Status in Ubuntu AppIndicators: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Committed Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in gnome-shell source package in Noble: New Status in gnome-shell-extension-appindicator source package in Noble: New Status in qtbase-opensource-src source package in Noble: New Bug description: [ Impact ] In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. [ Test case ] Note: this only tests the appindicator-side that may have lead to "activating" the application, it's not something that will fix the applications issues that is a QT bug. 1. Start a QT application with indicator (after gnome-shell has started; e.g. clementine, barrier...) 2. The applindicator menu with shell theme should appear 3. No activation happens on the application (e.g. the window is not opened) [ Regression potential ] Mouse events aren't properly exposed to the indicators To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2075549] [NEW] Running gtk applications in compositor supporting only shared memory buffers does not work with zink
Public bug reported: [ Impact ] An application is not draw if using GL and running in a wayland compositor that doesn't support dmabuf (e.g. just shared memory). This is happening with amd graphics, but I've read of reports with intel. See: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11613 Fixed by: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30479 [ Test case ] 1. Install weston compositor 2. Install mesa-utils and gtk-4-examples 3. In a terminal run: weston --renderer=pixman 4. In the weston terminal run: gtk4-demo 4a. The application should start and show 5. In the weston terminal run: eglgears_wayland 5a. The application should start and the gears spinning [ Regression potential ] swrast driver is used to render when proper hardware acceleration can be used instead. ** Affects: mesa (Ubuntu) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2075549 Title: Running gtk applications in compositor supporting only shared memory buffers does not work with zink Status in mesa package in Ubuntu: Triaged Bug description: [ Impact ] An application is not draw if using GL and running in a wayland compositor that doesn't support dmabuf (e.g. just shared memory). This is happening with amd graphics, but I've read of reports with intel. See: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11613 Fixed by: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30479 [ Test case ] 1. Install weston compositor 2. Install mesa-utils and gtk-4-examples 3. In a terminal run: weston --renderer=pixman 4. In the weston terminal run: gtk4-demo 4a. The application should start and show 5. In the weston terminal run: eglgears_wayland 5a. The application should start and the gears spinning [ Regression potential ] swrast driver is used to render when proper hardware acceleration can be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2075549/+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 2073356] Re: Choose password for new keyring the first time chromium-browser is started on each session
** Changed in: chromium-browser (Ubuntu) Status: Invalid => Won't Fix -- 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/2073356 Title: Choose password for new keyring the first time chromium-browser is started on each session Status in chromium-browser package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Bug description: I get this popup the first time I start chromium-browser: https://askubuntu.com/questions/1446379/why-am-i-always-asked-to- create-a-new-keyring either manually or via a startup script. Closing and restarting does not create the popup until I reboot. After the reboot, the password prompt is back again. What I do is just enter enter enter with empty password and life moves on. Under "Passwords and Keys" in settings, I just get a new "Default keyring" every time this happens. My disk is encrypted, I don't have a password to login, and I don't want to type any passwords after unlocking my disk during boot. Ubuntu 24.04, snap chromium version 126.0.6478.126. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2073356/+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 2075549] Re: Running gtk applications in compositor supporting only shared memory buffers does not work with zink
** Also affects: mesa (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2075549 Title: Running gtk applications in compositor supporting only shared memory buffers does not work with zink Status in mesa package in Ubuntu: Triaged Status in mesa source package in Noble: Triaged Bug description: [ Impact ] An application is not draw if using GL and running in a wayland compositor that doesn't support dmabuf (e.g. just shared memory). This is happening with amd graphics, but I've read of reports with intel. See: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11613 Fixed by: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30479 [ Test case ] 1. Install weston compositor 2. Install mesa-utils and gtk-4-examples 3. In a terminal run: weston --renderer=pixman 4. In the weston terminal run: gtk4-demo 4a. The application should start and show 5. In the weston terminal run: eglgears_wayland 5a. The application should start and the gears spinning [ Regression potential ] swrast driver is used to render when proper hardware acceleration can be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2075549/+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 2066353] Re: MESA: error: ZINK: failed to choose pdev
Can you check if this is a duplicate of https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2066353 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2066353 Title: MESA: error: ZINK: failed to choose pdev Status in mesa package in Ubuntu: Confirmed Bug description: MESA: error: ZINK: failed to choose pdev OS: Ubuntu 24.04 Noble Numbat LTS Kernel: 6.8 Canonical Kernel Session: SSH with X11 Forwarding - Client: MobaXterm ROS2 Robotics SDK Rolling Distro installed completely. # ros2 run turtlesim turtlesim_node [INFO] [1716371954.877337053] [turtlesim]: Starting turtlesim with node name /turtlesim [INFO] [1716371954.881675854] [turtlesim]: Spawning turtle [turtle1] at x=[5.55], y=[5.55], theta=[0.00] MESA: error: ZINK: failed to choose pdev glx: failed to create drisw screen [INFO] [1716371959.794685632] [rclcpp]: signal_handler(signum=2) i view this messages: MESA: error: ZINK: failed to choose pdev and glx: failed to create drisw screen Is a issue with MESA and Wayland over SSH X11 connection? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2066353/+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 2077576] [NEW] SSH client doesn't handle properly non-ASCII chars
Public bug reported:
[ Impact ]
Non-ascii visible chars are not properly rendered by clients, showing
their octal visualization.
Such as:
Hello SSHD! We love \360\237\215\225!
[ Test case ]
## Server preparation
Enable PAM and keyboard interactive authentication in a ssh server:
Add a configuration file such as:
/etc/ssh/sshd_config.d/test-ssh-pam.conf
Containing:
UsePAM yes
KbdInteractiveAuthentication yes
Restart the server:
sudo systemctl restart ssh.service
Edit the sshd PAM configuration file, adding as first line:
authrequisite pam_echo.so Hello SSHD! We love 🍕!
Can be done with the command:
sudo sed '1 i\authrequisite pam_echo.so Hello SSHD! We love 🍕!' -i
/etc/pam.d/sshd
## Client test
In the same host:
ssh -o PubkeyAuthentication=no \
-o PasswordAuthentication=no \
-o PreferredAuthentications=keyboard-interactive \
$USER@localhost
The client should show:
Hello SSHD-dev in devel schroot! Want some 🍕?
($USER@localhost) Password:
## Cleanup
Revert the changes done in the cleanup phase, after test is done
sudo sed '/pam_echo\.so/d' -i /etc/pam.d/sshd
sudo rm /etc/ssh/sshd_config.d/test-ssh-pam.conf
[ Regression potential ]
SSH info messages are not shown by the client
** Affects: openssh (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Released
** Affects: openssh (Ubuntu Focal)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Affects: openssh (Ubuntu Jammy)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Affects: openssh (Ubuntu Noble)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Released
** Also affects: openssh (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: openssh (Ubuntu Jammy)
Status: New => In Progress
** Changed in: openssh (Ubuntu Jammy)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Also affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: openssh (Ubuntu Focal)
Status: New => In Progress
** Changed in: openssh (Ubuntu Focal)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Also affects: openssh (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: openssh (Ubuntu Noble)
Status: New => In Progress
** Changed in: openssh (Ubuntu Noble)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: openssh (Ubuntu Noble)
Status: In Progress => Fix Released
** Changed in: openssh (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2077576
Title:
SSH client doesn't handle properly non-ASCII chars
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Focal:
In Progress
Status in openssh source package in Jammy:
In Progress
Status in openssh source package in Noble:
Fix Released
Bug description:
[ Impact ]
Non-ascii visible chars are not properly rendered by clients, showing
their octal visualization.
Such as:
Hello SSHD! We love \360\237\215\225!
[ Test case ]
## Server preparation
Enable PAM and keyboard interactive authentication in a ssh server:
Add a configuration file such as:
/etc/ssh/sshd_config.d/test-ssh-pam.conf
Containing:
UsePAM yes
KbdInteractiveAuthentication yes
Restart the server:
sudo systemctl restart ssh.service
Edit the sshd PAM configuration file, adding as first line:
authrequisite pam_echo.so Hello SSHD! We love 🍕!
Can be done with the command:
sudo sed '1 i\authrequisite pam_echo.so Hello SSHD! We love 🍕!' -i
/etc/pam.d/sshd
## Client test
In the same host:
ssh -o PubkeyAuthentication=no \
-o PasswordAuthentication=no \
-o PreferredAuthentications=keyboard-interactive \
$USER@localhost
The client should show:
Hello SSHD-dev in devel schroot! Want some 🍕?
($USER@localhost) Password:
## Cleanup
Revert the changes done in the cleanup phase, after test is done
sudo sed '/pam_echo\.so/d' -i /etc/pam.d/sshd
sudo rm /etc/ssh/sshd_config.d/test-ssh-pam.conf
[ Regression potential ]
SSH info messages are not shown by the client
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2077576/+subscriptions
--
Mailing list: https://launchpad.ne
[Touch-packages] [Bug 2077576] Re: SSH client doesn't handle properly non-ASCII chars
** Description changed: [ Impact ] Non-ascii visible chars are not properly rendered by clients, showing their octal visualization. Such as: Hello SSHD! We love \360\237\215\225! [ Test case ] ## Server preparation Enable PAM and keyboard interactive authentication in a ssh server: Add a configuration file such as: - /etc/ssh/sshd_config.d/test-ssh-pam.conf + /etc/ssh/sshd_config.d/test-ssh-pam.conf Containing: UsePAM yes KbdInteractiveAuthentication yes - Restart the server: - sudo systemctl restart ssh.service + sudo systemctl restart ssh.service Edit the sshd PAM configuration file, adding as first line: - authrequisite pam_echo.so Hello SSHD! We love 🍕! + authrequisite pam_echo.so Hello SSHD! We love 🍕! Can be done with the command: - sudo sed '1 i\authrequisite pam_echo.so Hello SSHD! We love 🍕!' -i /etc/pam.d/sshd - + sudo sed '1 i\authrequisite pam_echo.so Hello SSHD! We love 🍕!' -i /etc/pam.d/sshd ## Client test In the same host: - ssh -o PubkeyAuthentication=no \ - -o PasswordAuthentication=no \ - -o PreferredAuthentications=keyboard-interactive \ - $USER@localhost + ssh -o PubkeyAuthentication=no \ + -o PasswordAuthentication=no \ + -o PreferredAuthentications=keyboard-interactive \ + $USER@localhost The client should show: Hello SSHD-dev in devel schroot! Want some 🍕? ($USER@localhost) Password: + Retry the same with another host and without keyboard authentication + enabled in the server side. ## Cleanup Revert the changes done in the cleanup phase, after test is done sudo sed '/pam_echo\.so/d' -i /etc/pam.d/sshd sudo rm /etc/ssh/sshd_config.d/test-ssh-pam.conf [ Regression potential ] - SSH info messages are not shown by the client + SSH info messages are not shown by the client. + + These kind of messages are normally shown only when PAM is enabled in + the server side, so it should not affect the normal behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2077576 Title: SSH client doesn't handle properly non-ASCII chars Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: In Progress Status in openssh source package in Jammy: In Progress Status in openssh source package in Noble: Fix Released Bug description: [ Impact ] Non-ascii visible chars are not properly rendered by clients, showing their octal visualization. Such as: Hello SSHD! We love \360\237\215\225! [ Test case ] ## Server preparation Enable PAM and keyboard interactive authentication in a ssh server: Add a configuration file such as: /etc/ssh/sshd_config.d/test-ssh-pam.conf Containing: UsePAM yes KbdInteractiveAuthentication yes Restart the server: sudo systemctl restart ssh.service Edit the sshd PAM configuration file, adding as first line: authrequisite pam_echo.so Hello SSHD! We love 🍕! Can be done with the command: sudo sed '1 i\authrequisite pam_echo.so Hello SSHD! We love 🍕!' -i /etc/pam.d/sshd ## Client test In the same host: ssh -o PubkeyAuthentication=no \ -o PasswordAuthentication=no \ -o PreferredAuthentications=keyboard-interactive \ $USER@localhost The client should show: Hello SSHD-dev in devel schroot! Want some 🍕? ($USER@localhost) Password: Retry the same with another host and without keyboard authentication enabled in the server side. ## Cleanup Revert the changes done in the cleanup phase, after test is done sudo sed '/pam_echo\.so/d' -i /etc/pam.d/sshd sudo rm /etc/ssh/sshd_config.d/test-ssh-pam.conf [ Regression potential ] SSH info messages are not shown by the client. These kind of messages are normally shown only when PAM is enabled in the server side, so it should not affect the normal behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2077576/+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 2077741] Re: No default background set for GNOME-Greeter
** Changed in: ubuntu-settings (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: ubuntu-settings (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: ubuntu-settings (Ubuntu Noble) Status: New => In Progress ** Changed in: ubuntu-settings (Ubuntu Noble) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2077741 Title: No default background set for GNOME-Greeter Status in ubuntu-settings package in Ubuntu: In Progress Status in ubuntu-settings source package in Noble: In Progress Bug description: While using Gnome-Initial-Setup launched from GDM (when no user > 1000 is present on the machine), no background is set on GNOME-Greeter, leading to a solid blue background wallpaper. Could we set the background here to the Ubuntu default? By updating /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override with: ``` # for GDM/DM # FIXME: move to :Ubuntu-Greeter once upstream supports this, see LP: #1788 [org.gnome.desktop.interface:GNOME-Greeter] gtk-theme = 'Yaru' icon-theme = 'Yaru' cursor-theme = 'Yaru' font-name = 'Ubuntu 11' monospace-font-name = 'Ubuntu Mono 13' font-antialiasing = 'rgba' [org.gnome.login-screen] logo='/usr/share/plymouth/ubuntu-logo.png' + [org.gnome.desktop.background:GNOME-Greeter] + picture-uri = 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + picture-uri-dark = 'file:///usr/share/backgrounds/ubuntu-wallpaper-d.png' + show-desktop-icons = false ``` I was able to add in one. This will help improve the GIS installer flow for Raspberry Pi we plan to support in 24.10 ubuntu-settings: Installed: 24.04.3 Ubuntu version: 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077741/+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 2077741] Re: No default background set for GNOME-Greeter
** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-settings (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: ubuntu-settings (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2077741 Title: No default background set for GNOME-Greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Committed Bug description: While using Gnome-Initial-Setup launched from GDM (when no user > 1000 is present on the machine), no background is set on GNOME-Greeter, leading to a solid blue background wallpaper. Could we set the background here to the Ubuntu default? By updating /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override with: ``` # for GDM/DM # FIXME: move to :Ubuntu-Greeter once upstream supports this, see LP: #1788 [org.gnome.desktop.interface:GNOME-Greeter] gtk-theme = 'Yaru' icon-theme = 'Yaru' cursor-theme = 'Yaru' font-name = 'Ubuntu 11' monospace-font-name = 'Ubuntu Mono 13' font-antialiasing = 'rgba' [org.gnome.login-screen] logo='/usr/share/plymouth/ubuntu-logo.png' + [org.gnome.desktop.background:GNOME-Greeter] + picture-uri = 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + picture-uri-dark = 'file:///usr/share/backgrounds/ubuntu-wallpaper-d.png' + show-desktop-icons = false ``` I was able to add in one. This will help improve the GIS installer flow for Raspberry Pi we plan to support in 24.10 ubuntu-settings: Installed: 24.04.3 Ubuntu version: 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077741/+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 2077576] Re: SSH client doesn't handle properly non-ASCII chars
> This seems like quite an invasive change. It has not yet been accepted upstream. Nope, but reviewed and approved by at least one upstream developer both upstream and downstream (Tobias), while we're using it in noble for few months already with no issue reported so far. > It touches PAM, and it looks to me like it might affect behaviour before authentication is complete. It affects escaping. Injection of malicious data into a stream to be parsed by the terminal has security implications. There is no security analysis or opinion of the security team presented. It doesn't touch PAM authentication by default, it's triggered by (some) PAM authentications. However, we can definitely get the security team in the loop here. > What are we looking at here? Just the ability to include emoji in messages that, according to the SRU documentation provided, won't even be seen by the user? I can clarify this in the description, but showing emoji that's clearly not the root cause, it's just the simplest and easier reproducer for this issue. Indeed, the reason for this is that in authd we are presenting a qrcode to perform weblogin and that doesn't work. We are basically affected by the same issue of https://github.com/ubuntu/authd/issues/497 The test case for it, in a such complex setup isn't as easy to test as the minimal reproducer that it's enough to cover the fix and to ensure there are no regressions in the normal behavior. We're going to handle that in the openssh server too (starting from noble), but still we should be able to support this capability in the right way in ubuntu. > That sounds like a feature to me, and therefore doesn't seem appropriate to > change a stable release for given that no justification has been provided. Well, all the bug fixes can be features, if you are strict enough. But this is not the case IMHO, the client is clearly broken at handling some particular text, we're fixing it. There are no changes in behavior, and other major SSH clients (putty) handle this case already as the proposed change does for years. >> > SSH info messages are not shown by the client. > This seems to be contradicted by the provided Test Plan, which runs the > client and checks for the message. Please explain. PAM info messsages are exposed as generic SSH messages, they're the only ones of this kind AFAIK, but I wanted to be generic enough so that normal ssh usage should be checked too. >> These kind of messages are normally shown only when PAM is enabled in the >> server side, so it should not affect the normal behavior. > PAM is enabled by default on openssh on Ubuntu, no? PAM it is, but keyboard interactive authentication (which is the only case that triggers these messages) is not, so the change doesn't affect PAM behavior of ssh per se, only if the server has enabled keyboard interactive authentication, which PAM modules can trigger. But again, this is not default. ** Bug watch added: github.com/ubuntu/authd/issues #497 https://github.com/ubuntu/authd/issues/497 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2077576 Title: SSH client doesn't handle properly non-ASCII chars Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Incomplete Status in openssh source package in Jammy: Incomplete Status in openssh source package in Noble: Fix Released Bug description: [ Impact ] Non-ascii visible chars are not properly rendered by clients, showing their octal visualization. Such as: Hello SSHD! We love \360\237\215\225! [ Test case ] ## Server preparation Enable PAM and keyboard interactive authentication in a ssh server: Add a configuration file such as: /etc/ssh/sshd_config.d/test-ssh-pam.conf Containing: UsePAM yes KbdInteractiveAuthentication yes Restart the server: sudo systemctl restart ssh.service Edit the sshd PAM configuration file, adding as first line: authrequisite pam_echo.so Hello SSHD! We love 🍕! Can be done with the command: sudo sed '1 i\authrequisite pam_echo.so Hello SSHD! We love 🍕!' -i /etc/pam.d/sshd ## Client test In the same host: ssh -o PubkeyAuthentication=no \ -o PasswordAuthentication=no \ -o PreferredAuthentications=keyboard-interactive \ $USER@localhost The client should show: Hello SSHD-dev in devel schroot! Want some 🍕? ($USER@localhost) Password: Retry the same with another host and without keyboard authentication enabled in the server side. ## Cleanup Revert the changes done in the cleanup phase, after test is done sudo sed '/pam_echo\.so/d' -i /etc/pam.d/sshd sudo rm /etc/ssh/sshd_config.d/test-ssh-pam.conf [ Regression potential ] SSH info messages are not shown by the client. These kind of messages are normally shown only when PAM is enabled in th
[Touch-packages] [Bug 2077576] Re: SSH client doesn't handle properly non-ASCII chars
** Description changed: [ Impact ] - Non-ascii visible chars are not properly rendered by clients, showing - their octal visualization. + Non-ascii visible chars (including back-slashes, new lines and so) are + not properly rendered by clients, showing their octal visualization. Such as: - Hello SSHD! We love \360\237\215\225! + Hello SSHD \\ We love \360\237\215\225! + + Instead of: + + Hello SSHD \ We love 🍕! + + This is particularly an issue when a server has configured keyboard + interactive authentication and a PAM module wants to show non-ASCII + characters such as a QR code for web authentication: + + When using an ubuntu server running authd for web authentication we may + end up having the login qrcode rendered such as + + \210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210 + https://ubuntu.com +1337 + + Which is clearly unreadable. [ Test case ] ## Server preparation Enable PAM and keyboard interactive authentication in a ssh server: Add a configuration file such as: /etc/ssh/sshd_config.d/test-ssh-pam.conf Containing: UsePAM yes KbdInteractiveAuthentication yes + # This was working already; here to check potential regressions + ForceCommand bash -c "echo Hello from SSHD \ We also love 🍕!; $SHELL" + + It's also suggested to check for regressions using a `Banner` option in + sshd, pointing to a file with utf-8 contents. Restart the server: sudo systemctl restart ssh.service Edit the sshd PAM configuration file, adding as first line: - authrequisite pam_echo.so Hello SSHD! We love 🍕! + authrequisite pam_echo.so Hello SSHD \ We love 🍕! Can be done with the command: - sudo sed '1 i\authrequisite pam_echo.so Hello SSHD! We love 🍕!' -i /etc/pam.d/sshd + sudo sed '1 iauthrequisite pam_echo.so Hello SSHD! \\ We love 🍕!' \ +-i /etc/pam.d/sshd ## Client test In the same host: ssh -o PubkeyAuthentication=no \ -o PasswordAuthentication=no \ -o PreferredAuthentications=keyboard-interactive \ $USER@localhost The client should show: - Hello SSHD-dev in devel schroot! Want some 🍕? + Hello SSHD \ We love 🍕! ($USER@localhost) Password: + ... + Hello from SSHD \ We also love 🍕! Retry the same with another host and without keyboard authentication enabled in the server side. ## Cleanup Revert the changes done in the cleanup phase, after test is done sudo sed '/pam_echo\.so/d' -i /etc/pam.d/sshd sudo rm /etc/ssh/sshd_config.d/test-ssh-pam.conf [ Regression potential ] - SSH info messages are not shown by the client. + SSH info messages are not shown by the client. Even though those aren't + covered by this change, it's important to check for regressions in any + output that SSH exposes to the user. So banners and other messages + should be checked for regressions. - These kind of messages are normally shown only when PAM is enabled in - the server side, so it should not affect the normal behavior. + These kind of messages are normally shown only when PAM *and* keyboard + interaction are enabled in the server side, so it should not affect the + default ubuntu servers behavior. ** Description changed: [ Impact ] Non-ascii visible chars (including back-slashes, new lines and so) are not properly rendered by clients, showing their octal visualization. Such as: - Hello SSHD \\ We love \360\237\215\225! + Hello SSHD \\ We love \360\237\215\225! Instead of: - Hello SSHD \ We love 🍕! + Hello SSHD \ We love 🍕! This is particularly an issue when a server has configured keyboard interactive authentication and a PAM module wants to show non-ASCII characters such as a QR code for web authentication: When using an ubuntu server running authd for web authentication we may end up having the login qrcode rendered such as \210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210 - https://ubuntu.com -1337 + https://ubuntu.com + 1337 Which is clearly unreadable. [ Test case ] ## Server preparation Enable PAM and keyboard interactive authentication in a ssh server: Add
[Touch-packages] [Bug 2077576] Re: SSH client doesn't handle properly non-ASCII chars
Mh, yeah looks like the terminal filtering is something we should do in openssh anyways, at various levels though. Fact is that if a server is malicious, nothing prevents to do the same through a simpler sshd banner or command, that is still able to act on remote terminal. It's true that PAM modules are sneakier than that, as they may be checked less than the pure openssh server configuration, but still it's all server duty, and if compromised (intentionally or not), it can be still a driver for such issues in the current state. ASCII based solutions for qr code are acceptable, they can just quite big though. Being a problem if you use them from a tty. However that's another possibility we were considering already. Regarding upstream diversion, I totally agree (and I would have loved to avoid it)... Ideally we had a plan, and the fix was proposed way earlier upstream than downstream. So we were just waiting... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2077576 Title: SSH client doesn't handle properly non-ASCII chars Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Incomplete Status in openssh source package in Jammy: Incomplete Status in openssh source package in Noble: Fix Released Bug description: [ Impact ] Non-ascii visible chars (including back-slashes, new lines and so) are not properly rendered by clients, showing their octal visualization. Such as: Hello SSHD \\ We love \360\237\215\225! Instead of: Hello SSHD \ We love 🍕! This is particularly an issue when a server has configured keyboard interactive authentication and a PAM module wants to show non-ASCII characters such as a QR code for web authentication: When using an ubuntu server running authd for web authentication we may end up having the login qrcode rendered such as \210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210\342\226\210 https://ubuntu.com 1337 Which is clearly unreadable. [ Test case ] ## Server preparation Enable PAM and keyboard interactive authentication in a ssh server: Add a configuration file such as: /etc/ssh/sshd_config.d/test-ssh-pam.conf Containing: UsePAM yes KbdInteractiveAuthentication yes # This was working already; here to check potential regressions ForceCommand bash -c "echo Hello from SSHD \ We also love 🍕!; $SHELL" It's also suggested to check for regressions using a `Banner` option in sshd, pointing to a file with utf-8 contents. Restart the server: sudo systemctl restart ssh.service Edit the sshd PAM configuration file, adding as first line: authrequisite pam_echo.so Hello SSHD \ We love 🍕! Can be done with the command: sudo sed '1 iauthrequisite pam_echo.so Hello SSHD! \\ We love 🍕!' \ -i /etc/pam.d/sshd ## Client test In the same host: ssh -o PubkeyAuthentication=no \ -o PasswordAuthentication=no \ -o PreferredAuthentications=keyboard-interactive \ $USER@localhost The client should show: Hello SSHD \ We love 🍕! ($USER@localhost) Password: ... Hello from SSHD \ We also love 🍕! Retry the same with another host and without keyboard authentication enabled in the server side. To verify the fix in more complex scenario it's possible to follow the instructions of configuring authd: - https://github.com/ubuntu/authd/wiki/05--How%E2%80%90to-log-in-over-SSH Once authd is configured, the user should be able to scan a QrCode from a ssh session. ## Cleanup Revert the changes done in the cleanup phase, after test is done sudo sed '/pam_echo\.so/d' -i /etc/pam.d/sshd sudo rm /etc/ssh/sshd_config.d/test-ssh-pam.conf [ Regression potential ] SSH info messages are not shown by the client. Even though those aren't covered by this change, it's important to check for regressions in any output that SSH exposes to the user. So banners and other messages should be checked for regressions. These kind of messages are normally shown only when PAM *and* keyboard interaction are enabled in the server side, so it should not affect the default ubuntu servers behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2077576/+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/Li
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
** Also affects: evolution (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: libcanberra (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: evolution (Ubuntu Jammy)
** Changed in: libcanberra (Ubuntu)
Status: Triaged => In Progress
** Changed in: libcanberra (Ubuntu Jammy)
Status: New => Triaged
** Changed in: libcanberra (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: libcanberra (Ubuntu Jammy)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
In Progress
Status in libcanberra source package in Jammy:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
> Why are you setting d->object to NULL in on_object_disposed? By doing that you are introducing memory leak, no? Well the point was that I didn't want this to happen when last reference was removed, but this can't really happen in a sane setup unless something played some dirty game with the object. So that's fine, I've handled it as part of fix for #1983794 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Won't Fix Status in libcanberra package in Ubuntu: Fix Released Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1983794] Re: Evolution not deleting autosave files
** Also affects: evolution (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: libcanberra (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: libcanberra (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: libcanberra (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: libcanberra (Ubuntu Kinetic)
Importance: Undecided => Low
** Changed in: libcanberra (Ubuntu Kinetic)
Importance: Low => Medium
** Changed in: evolution (Ubuntu)
Importance: Medium => Low
** Changed in: libcanberra (Ubuntu Kinetic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
In Progress
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1983794] Re: Evolution not deleting autosave files
** Description changed:
+ [ Impact ]
+
+ Autosave files are not removed from evolution local state directories
+ (and windows leaked)
+
+
+ [ Test case ]
+
+ 1. Open evolution, and start to compose a new email
+ 2. Write enough text and wait few minutes so that this command returns a file
+ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
+ 3. Close the email composer window, hitting "Do not save"
+ 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
+ 5. Opening and closing again evolution should not ask to restore the previous
email
+
+
+ [ Regression potential ]
+
+ No sounds could be performed during some UI actions
+
+ ---
+
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was
installed with the distribution on a new system and received settings
imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string). When
the email is successfully sent, the autosave file SHOULD be deleted.
It's not. When evolution is shut down and restarted I'm asked if I want
to recover an unfinished email. Answering No to this will delete the
autosave file, but otherwise it persists and the recovery query recurs
the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people
aren't dealing with it, perhaps considering it a distro-specific bug.
On a system used by many people this is a potential security issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
In Progress
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1983794] Re: Evolution not deleting autosave files
miguelquiros, can we mark this as verified?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1983794] Re: Evolution not deleting autosave files
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2004241] Re: Update to glib >= 2.75.1
Snapd just migrated, we can remove the block. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 Status in glib2.0 package in Ubuntu: Fix Committed Bug description: Update to glib >= 2.75.1 because that's what mutter 44 now requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
Chris, please try to use the upstream version of this extension from https://github.com/ubuntu/gnome-shell-extension-appindicator/ It changes the way we handle indicator-multiload in a way that should improve performance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 1987560] Re: don't switch Ubuntu libtimezonemap to libsoup3
We've an ubuntu package now, so it won't be auto-synced ** Changed in: libtimezonemap (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/1987560 Title: don't switch Ubuntu libtimezonemap to libsoup3 Status in libtimezonemap package in Ubuntu: Fix Released Bug description: libtimezonemap is used by ubiquity and ubiquity still uses libsoup2. See https://launchpad.net/bugs/1987454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtimezonemap/+bug/1987560/+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 2012116] Re: Installer crashes after clicking on a time zone
** Changed in: libtimezonemap (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/2012116 Title: Installer crashes after clicking on a time zone Status in libtimezonemap package in Ubuntu: Fix Released Status in libtimezonemap source package in Lunar: Fix Released Bug description: When I reach the "Where are you?" screen, my time zone is not correctly selected. Clicking the map to select my time zone causes the installer to crash without an error message or the option to report an issue. Relaunching the installer from the desktop will fail at the same point, but this time, I get the error message, "ubi-partman failed with exit code 10." If I go through the installer and DO NOT change the time zone, the installation completes successfully. I am performing this install with two different Virtual Machine platforms: Virtual Box and Gnome Boxes. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity 23.04.4 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: XFCE Date: Sat Mar 18 03:36:03 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtimezonemap/+bug/2012116/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
I can test this too if needed, I've a AMD® Ryzen 7 pro 7840u with radeon 780m graphics (phoenix). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [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 blob 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/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 mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
Hi, Related to the desktop team specific needs, I wanted to mention that at the current state we don't expect to need or support pam-pkcs11 given that we want to rely only on pam-sss (that should be at this time more than enough for any need), other than being already in main. So, while in debian [1] (and ubuntu) I've added both profiles for pam- sss and pam-pkcs11 the latter is mainly untested and not default (can be seleceted with update-alternatives in case). Said this, if there are not other requirements for it, I'd consider it safe to be dropped from the MIR list from our POV. Regarding pcscd, however... I think we need it. I've done my testing with limited hardware here (mostly my national healthcare card) but that's only supported by opensc-pkcs11 IF pcscd is installed. So I've the feeling we can't downgrade pcscd to a simple suggestion in most of the cases. [1] https://salsa.debian.org/gnome-team/gdm/-/tree/debian/master/debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be use
[Touch-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1931582] [NEW] Add LOGO to /etc/os-release
Public bug reported: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg ** Affects: base-files (Ubuntu) Importance: Medium Status: Triaged ** Affects: base-files (Debian) Importance: Unknown Status: Unknown ** Description changed: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg - - This issue should be probably be opened in debian too ** Bug watch added: Debian Bug tracker #989690 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989690 ** Also affects: base-files (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989690 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1931582 Title: Add LOGO to /etc/os-release Status in base-files package in Ubuntu: Triaged Status in base-files package in Debian: Unknown Bug description: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1931582/+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 1931901] Re: Revert background key patch removal breaks dependent packages
So the function isn't really used anywhere we care about, so I think we can just drop it https://paste.ubuntu.com/p/tyN5Vp99Fj/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1931901 Title: Revert background key patch removal breaks dependent packages Status in gnome-desktop3 package in Ubuntu: New Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: in the package gnome-desktop3 there is a custom ubuntu patch that tries to write to the draw-background key that has now been removed in gsettings-desktop-schemas 40.0-1ubuntu1 All packages that depend on the gnome-desktop3 library now crash such as budgie-desktop Suggestion - either re-add the patch again ... or revert the gnome- desktop3 custom patch. The latter option changes the symbols so probably I'm guessing a so- name version bump is needed and any dependent packages need a rebuild? I'll try to locally rebuild gnome-desktop3 without the custom ubuntu patch to see what happens with budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jun 14 20:52:16 2021 InstallationDate: Installed on 2021-06-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+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 1964274] Re: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool
I guess mutter side can be closed, since we've already beta in archive. ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1964274 Title: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Released Status in wayland package in Ubuntu: In Progress Status in xwayland package in Ubuntu: Fix Released Bug description: System : Ubuntu 21.10 Kernel 5.13.0-35 Session : Wayland Each time I try to rip a CD with "abcde" gnome-shell crashes What I understand from the logs : Before the CD is ripped, abcde downloads a picture (from internet) as a cover of the CD. When tracker-extract discovers this picture something bad happens. Then gnome-shell crashes. After the crash (and re-login into Ubuntu) I can resume the ripping process as the picture has been cached by abcde, and tracker-extract does not interact again with it. Obviously the problem is back for each new CD. The problem appeared quite recently, probably less than 1 month ago. Logs : 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 comm="/usr/libexec/tracker-mi> 00:13:06 host systemd[3523]: Starting Tracker metadata extractor... 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' 00:13:06 host systemd[3523]: Started Tracker metadata extractor. 00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 0x50 00:13:14 host tracker-extract[11545]: Task for 'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: Could not get any metadata for uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg' 00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), message create_pool(nhi) 00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640) 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[4456]: Fatal server error: 00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[3640]: Connection to xwayland lost To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1964274/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
This is the root issue: https://gitlab.gnome.org/GNOME/glib/-/issues/389 ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #389 https://gitlab.gnome.org/GNOME/glib/-/issues/389 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Triaged Status in libcanberra package in Ubuntu: Triaged Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Won't Fix ** Changed in: libcanberra (Ubuntu) Status: Triaged => Fix Committed ** Changed in: libcanberra (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Won't Fix Status in libcanberra package in Ubuntu: Fix Committed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice
I think this is triggered by valgrind because it leads to slowdowns, but the bug is indeed there. We can handle it in a later upload I think, but due to gslice and the randomness of these memory errors, I wouldn't be shocked if this is actually presenting right now in the wild with a different stack trace. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Valgrind memory errors in gnome-shell 42 from accountsservice Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free
[Touch-packages] [Bug 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Snap version built via snapcraft at https://github.com/3v1n0/notify- send-test-snap/commits/46b035b ** Description changed: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. - [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] - Build the test snap: - git clone https://github.com/3v1n0/notify-send-test-snap - snapcraft prime - snap try prime + Build the test snap (or install it from the attached files to this bug): + git clone https://github.com/3v1n0/notify-send-test-snap + snapcraft prime + snap try prime Check that icons are shown when launching: - notify-send-test-snap - notify-send-test-snap.image-path + notify-send-test-snap + notify-send-test-snap.image-path - Running them with G_MESSAGES_DEBUG=all should provide translation - logging + Ensure that desktop entry is correctly sent, monitoring the dbus + session: + + In a terminal: +dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" + + In the other: +notify-send-test-snap.desktop-entry +notify-send-test-snap.desktop-entry-explicit-id +notify-send-test-snap.desktop-entry-explicit-file-name +notify-send-test-snap.desktop-entry-explicit-path +notify-send-test-snap.desktop-entry-explicit-uri +notify-send-test-snap.desktop-entry-explicit-snapped-uri + + The + `desktop-entry` value sent to dbus should be either: +- A `notify-send-test-snap_`-prefixed desktop ID +- A .desktop file path (readable from both inside and outside the snap) +- A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file ** Also affects: libnotify (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: libnotify (Ubuntu Focal) Importance: Undecided Status: New ** Attachment added: "notify-send-test-snap_0+git.46b035b_amd64.snap" https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5582259/+files/notify-send-test-snap_0+git.46b035b_amd64.snap ** Description changed: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime + To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) + snap install --dangerous notify-send-test-snap_*.snap + Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path Ensure that desktop entry is correctly sent, monitoring the dbus session: - In a terminal: -dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" + In a terminal: + dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" - In the other: -notify-send-test-snap.desktop-entry -notify-send-test-snap.desktop-entry-explicit-id -notify-send-test-snap.desktop-entry-explicit-file-name -notify-send-test-snap.desktop-entry-explicit-path -notify-send-test-snap.desktop-entry-explicit-uri -notify-send-test-snap.desktop-entry-explicit-snapped-uri + In the other: + notify-send-test-snap.desktop-entry + notify-send-test-snap.desktop-entry-explicit-id + notify-send-test-snap.desktop-entry-explicit-file-name + notify-send-test-snap.desktop-entry-explicit-path + notify-send-test-snap.desktop-entry-explicit-uri + notify-send-test-snap.desktop-entry-explicit-snapped-uri - The - `desktop-entry` value sent to dbus should be either: -- A `notify-send-test-snap_`-prefixed desktop ID -- A .desktop file path (readable from both inside and outside the snap) -- A .desktop file uri (readable from both inside and outside the snap) + The + `desktop-entry` value sent to dbus should be either: + - A `notify-send-test-snap_`-prefixed desktop ID + - A .desktop f
[Touch-packages] [Bug 1255591] Re: [Feature request] notify-send option to change the "notify-send" app name that appears in all my notifications.
This was fixed in
https://gitlab.gnome.org/GNOME/libnotify/commit/b873c61ecc85c1a87c9471046f3d25ecd2446959
included in old revisions
** Changed in: libnotify (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1255591
Title:
[Feature request] notify-send option to change the "notify-send" app
name that appears in all my notifications.
Status in libnotify package in Ubuntu:
Fix Released
Bug description:
(I wasn't sure if feature requests counted as bug reports or
questions. My apologies if I guessed wrong. I also apologize if this
is the wrong place for a patch, but I couldn't find a repo to fork.)
I use notify-send in a number of shell scripts. I would like it to be
able to accurately report which script is sending the notification.
Instead I'm stuck with "notify-send" as the application responsible
for creating all the notifications.
I saw that the string "notify-send" appears exactly once in notify-
send.c. So I added a cli option, -l/--app-label, to change it.
Here's the patch:
```
128a129
> static char*app_label = NULL;
151a153,154
> {"app-label", 'l', 0, G_OPTION_ARG_STRING, &app_label,
> N_("Specifies the label shown in the notification
(default: notify-send)"), N_("APP_LABEL")},
223c226
< if (!notify_init ("notify-send"))
---
> if (!notify_init (app_label != NULL ? app_label : "notify-send"))
```
This is for libnotify-0.7.6 downloaded with apt-get source libnotify.
I figure the patch is trivial enough that the version probably doesn't
matter too much. I'd appreciate it if this functionality could make
it into libnotify, but I don't care if it's implemented with my patch
or some other method.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1255591/+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 537208] Re: pidgin crashed with SIGSEGV in notify_get_server_caps()
** Changed in: libnotify (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/537208 Title: pidgin crashed with SIGSEGV in notify_get_server_caps() Status in libnotify package in Ubuntu: Invalid Status in libnotify source package in Lucid: Won't Fix Bug description: Binary package hint: pidgin bug occurs after enable/disable notify applet ProblemType: Crash Architecture: i386 Date: Thu Mar 11 11:12:51 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/pidgin InstallationMedia: Error: [Errno 13] Отказано в доступе: '/var/log/installer/media-info' Package: pidgin 1:2.6.6-1ubuntu4 ProcCmdline: pidgin ProcEnviron: SHELL=/bin/bash LANG=ru_UA.utf8 ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SegvAnalysis: Segfault happened at: 0x16441cb :mov 0x8(%eax),%eax PC (0x016441cb) ok source "0x8(%eax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: notify_get_server_caps () from /usr/lib/libnotify.so.1 ?? () from /usr/lib/purple-2/pidgin-libnotify.so purple_plugin_load () from /usr/lib/libpurple.so.0 ?? () g_cclosure_marshal_VOID__STRING () Title: pidgin crashed with SIGSEGV in notify_get_server_caps() Uname: Linux 2.6.32-16-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:8260): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (bluetooth-applet:8262): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed (gnome-terminal:8443): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/537208/+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 1970647] [NEW] notify-send exit code doesn't match result
Public bug reported: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. ** Affects: libnotify (Ubuntu) Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: In Progress Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 725435] Re: notify-osd a memory hog (memory leak?)
** Changed in: libnotify (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/725435 Title: notify-osd a memory hog (memory leak?) Status in libnotify package in Ubuntu: Invalid Status in notify-osd package in Ubuntu: Triaged Bug description: Binary package hint: notify-osd Noticed this today on my lucid box in top: 2647 myaccount 20 0 1196m 595m 3528 S0 29.7 1:09.68 notify-osd I don't think a simple notifcation daemon should suck up more than a Gig of memory of which half is real memory. It's the first time I noticed this. I don't have too much information at this point. $ dpkg -l notify-osd* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii notify-osd0.9.29-0ubuntu2 daemon that displays passive pop-up notifications ii notify-osd-icons 0.6 Notify-OSD icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/725435/+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 383875] Re: add convenience function "notify_has_server_cap" to notify.h
** Changed in: libnotify (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/383875 Title: add convenience function "notify_has_server_cap" to notify.h Status in galago-daemon: New Status in libnotify package in Ubuntu: Fix Released Bug description: Inspired by http://bugzilla.gnome.org/show_bug.cgi?id=584857#c2 I added a convenience function to libnotify that allows easy testing for certain capabilities: gboolean notify_has_server_cap(const char* capability) Attaching patch. To manage notifications about this bug go to: https://bugs.launchpad.net/galago-daemon/+bug/383875/+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 257135] Re: notify-send(1) can't replace an existing notification
** Changed in: libnotify (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/257135 Title: notify-send(1) can't replace an existing notification Status in libnotify package in Ubuntu: In Progress Status in libnotify package in Debian: Fix Released Bug description: Binary package hint: libnotify-bin Ubuntu 8.04, libnotify-bin 0.4.4-3build1. notify-send(1) is very useful but it doesn't tell me the notification ID that's been created, nor does it let me specify that to replace an earlier notification. See http://www.galago- project.org/specs/notification/0.9/x408.html#command-notify, in particular the replaces_id parameter and the return value. I'd like to be able to use it something like id=$(notify-send --show-id foo) sleep 60 notify-send --replace $id bar This would be great for long-running shell scripts that are monitoring something. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+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 1970647] Re: notify-send exit code doesn't match result
On focal: ❯ apt-cache policy libnotify-bin libnotify-bin: Installato: 0.7.9-1ubuntu3.20.04.2 Candidato: 0.7.9-1ubuntu3.20.04.2 Tabella versione: *** 0.7.9-1ubuntu3.20.04.2 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.7.9-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ❯ env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo exit-error L'indirizzo fornito è vuoto exit-error ** Description changed: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: -jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error + env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1970647] Re: notify-send exit code doesn't match result
On Jammy: ❯ apt-cache policy libnotify4 libnotify4: Installato: 0.7.9-3ubuntu5.22.04.1 Candidato: 0.7.9-3ubuntu5.22.04.1 Tabella versione: *** 0.7.9-3ubuntu5.22.04.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.7.9-3ubuntu5 400 400 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ❯ env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo exit-error The given address is empty exit-error ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: Fix Committed Status in libnotify source package in Jammy: Fix Committed Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1960768] Re: fwupd crash on stop
** Changed in: libgusb (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()
** Bug watch added: github.com/libusb/libusb/issues #1079 https://github.com/libusb/libusb/issues/1079 ** Also affects: libfprint via https://github.com/libusb/libusb/issues/1079 Importance: Unknown Status: Unknown ** Project changed: libfprint => libusb ** Changed in: fprintd (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: libusb (Ubuntu) Importance: Undecided Status: New ** Changed in: libusb (Ubuntu) Importance: Undecided => High ** Changed in: libusb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960387 Title: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device() Status in libusb: Unknown Status in fprintd package in Ubuntu: Won't Fix Status in libusb package in Ubuntu: Confirmed Bug description: + ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.1-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 7 21:58:32 2022 ExecutablePath: /usr/libexec/fprintd InstallationDate: Installed on 2021-12-21 (50 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/libexec/fprintd ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fd8a7a3855f:call *%rax PC (0x7fd8a7a3855f) ok source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region (needed readable region)! destination "(%rsp)" (0x7ffdceacc590) ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: fprintd StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgusb.so.2 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: fprintd crashed with SIGSEGV in libusb_unref_device() UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/libusb/+bug/1960387/+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 1892559] Re: [MIR] ccid opensc pcsc-lite
The plan seems quite solid, and I do agree that having some more testing would be nice (also using libsofthsm2 can help here I think). I'm not sure if all this can be achieved by the next LTS though, which I think we're targetting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, ho
[Touch-packages] [Bug 2016312] Re: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_sig
*** This bug is a duplicate of bug 2015962 *** https://bugs.launchpad.net/bugs/2015962 ** Package changed: indicator-messages (Ubuntu) => accountsservice (Ubuntu) ** Changed in: accountsservice (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 2015962 indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2016312 Title: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages- service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit Status in accountsservice package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/0e715044718e39117f0d6382a7dc032e629ee88e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2016312/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
** Changed in: accountsservice (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 1983794] Re: Evolution not deleting autosave files
Yeah, thanks I was aware of this and it was indeed my starting point.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
Ok I was quite sure that CERT_LIST_HEAD was already guarding us from NULL pointers (as in many NSS places i didn't see the check) but it's not the case [1], so thanks! [1] https://searchfox.org/mozilla- central/source/security/nss/lib/certdb/certt.h#361 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend The option 3) has been finally choosen, but we also require migration scripts on upgrade. [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then: 1) If you previously configured SSSD match rules and/or CA certificates: - You should still get your certificate public key printed as output - Configured login with smartcard should continue working 2) If SSSD was not configured to do smartcard authentication: - p11_child may fail if the card certificate was not previously added to the trusted DB, but this is outside of this test case.
[Touch-packages] [Bug 1916956] Re: xvfb fails when building mutter in hirsute-proposed
** Changed in: xorg-server (Ubuntu) Status: New => Invalid ** Summary changed: - xvfb fails when building mutter in hirsute-proposed + mutter fails to run using wayland with glib2.0 2.67.4-1 ** Description changed: When hirsute-proposed is enabled (works fine in hirsute), mutter fails building as per xvfb not able to run: XIO: fatal IO error 88 (Socket operation on non-socket) on X server ":99" - after 209 requests (209 known processed) with 2 events remaining. + after 209 requests (209 known processed) with 2 events remaining. (EE) could not connect to wayland server Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu- hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz + + See more at https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1 + + This just happens by running in a session: + mutter --wayland --nested + + That fails instead of opening a nested compositor ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916956 Title: mutter fails to run using wayland with glib2.0 2.67.4-1 Status in glib2.0 package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: When hirsute-proposed is enabled (works fine in hirsute), mutter fails building as per xvfb not able to run: XIO: fatal IO error 88 (Socket operation on non-socket) on X server ":99" after 209 requests (209 known processed) with 2 events remaining. (EE) could not connect to wayland server Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu- hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz See more at https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1 This just happens by running in a session: mutter --wayland --nested That fails instead of opening a nested compositor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916956/+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 1916956] Re: mutter fails to run using wayland with glib2.0 2.67.4-1
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2332 https://gitlab.gnome.org/GNOME/glib/-/issues/2332 ** Also affects: xorg-server via https://gitlab.gnome.org/GNOME/glib/-/issues/2332 Importance: Unknown Status: Unknown ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Critical ** Project changed: xorg-server => glib -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916956 Title: mutter fails to run using wayland with glib2.0 2.67.4-1 Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Invalid Bug description: When hirsute-proposed is enabled (works fine in hirsute), mutter fails building as per xvfb not able to run: XIO: fatal IO error 88 (Socket operation on non-socket) on X server ":99" after 209 requests (209 known processed) with 2 events remaining. (EE) could not connect to wayland server Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu- hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz See more at https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1 This just happens by running in a session: mutter --wayland --nested That fails instead of opening a nested compositor To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916956/+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 1916956] Re: mutter fails to run using wayland with glib2.0 2.67.4-1
*** This bug is a duplicate of bug 1916701 *** https://bugs.launchpad.net/bugs/1916701 ** This bug has been marked a duplicate of bug 1916701 [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916956 Title: mutter fails to run using wayland with glib2.0 2.67.4-1 Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Invalid Bug description: When hirsute-proposed is enabled (works fine in hirsute), mutter fails building as per xvfb not able to run: XIO: fatal IO error 88 (Socket operation on non-socket) on X server ":99" after 209 requests (209 known processed) with 2 events remaining. (EE) could not connect to wayland server Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu- hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz See more at https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1 This just happens by running in a session: mutter --wayland --nested That fails instead of opening a nested compositor To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916956/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Committed ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Committed Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916701/+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 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
Thanks Valters for your verification! It's always better when someone that didn't commit the fix can help with it. I've also done further verification to ensure that the migration happens as expected, so my sssd.conf was: [sssd] enable_files_domain = True services = pam certificate_verification = no_ocsp [certmap/implicit_files/marco] matchrule = .*TRVMRC[A-Z0-9]+/6090010669298009\.YOrY0zOk5CdMby2Z2O/HnVRA8Ao.* [pam] pam_cert_auth = True pam_verbosity = 10 debug_level = 10 #pam_cert_db_path = /etc/ssl/certs/ca-certificates.crt # pam_cert_db_path = /etc/pki/nssdb pam_cert_db_path = /etc/pki/nssdb2 ca_db = /etc/pki/nssdb2 #ca_db = /etc/pki/nssdb With /etc/pki/nssdb2 configured so that it was able to read my reader and containing the relative CA certificate: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 --nssdb=/etc/pki/nssdb2 (Mon Mar 1 15:16:29:470908 2021) [[sssd[p11_child[70818 [main] (0x0400): p11_child started. (Mon Mar 1 15:16:29:470980 2021) [[sssd[p11_child[70818 [main] (0x2000): Running in [pre-auth] mode. (Mon Mar 1 15:16:29:470991 2021) [[sssd[p11_child[70818 [main] (0x2000): Running with effective IDs: [0][0]. (Mon Mar 1 15:16:29:470998 2021) [[sssd[p11_child[70818 [main] (0x2000): Running with real IDs [0][0]. (Mon Mar 1 15:16:31:152580 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Default Module List: (Mon Mar 1 15:16:31:152668 2021) [[sssd[p11_child[70818 [do_card] (0x4000): common name: [NSS Internal PKCS #11 Module]. (Mon Mar 1 15:16:31:152697 2021) [[sssd[p11_child[70818 [do_card] (0x4000): dll name: [(null)]. (Mon Mar 1 15:16:31:152706 2021) [[sssd[p11_child[70818 [do_card] (0x4000): common name: [PKCS#11 Kit modules proxy]. (Mon Mar 1 15:16:31:152715 2021) [[sssd[p11_child[70818 [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/p11-kit-proxy.so]. (Mon Mar 1 15:16:31:152724 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Dead Module List: (Mon Mar 1 15:16:31:152732 2021) [[sssd[p11_child[70818 [do_card] (0x4000): DB Module List: (Mon Mar 1 15:16:31:152750 2021) [[sssd[p11_child[70818 [do_card] (0x4000): common name: [NSS Internal Module]. (Mon Mar 1 15:16:31:152759 2021) [[sssd[p11_child[70818 [do_card] (0x4000): dll name: [(null)]. (Mon Mar 1 15:16:31:152769 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Description [NSS Internal Cryptographic Services Mozilla Foundation] Manufacturer [Mozilla Foundation ] flags [9] removable [false] token present [true]. (Mon Mar 1 15:16:31:152818 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Description [NSS User Private Key and Certificate Services Mozilla Foundation ] Manufacturer [Mozilla Foundation ] flags [1] removable [false] token present [true]. (Mon Mar 1 15:16:31:153898 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (Mon Mar 1 15:16:31:153949 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][16] of module [2][/usr/lib/x86_64-linux-gnu/p11-kit-proxy.so]. (Mon Mar 1 15:16:31:153976 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Token is NOT friendly. (Mon Mar 1 15:16:31:153995 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Trying to switch to friendly to read certificate. (Mon Mar 1 15:16:31:154029 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Login required. (Mon Mar 1 15:16:31:154041 2021) [[sssd[p11_child[70818 [do_card] (0x0020): Login required but no PIN available, continue. (Mon Mar 1 15:16:31:170652 2021) [[sssd[p11_child[70818 [do_card] (0x4000): found cert[MARCO TREVISAN (PIN CNS0):CNS0][SN=TREVISAN,givenName=MARCO,CN="TRVMRC85T31A851Y/6090010669298009.YOrY0zOk5CdMby2Z2O/HnVRA8Ao=",OU=REGIONE TOSCANA,O=Actalis S.p.A.,C=IT] (Mon Mar 1 15:16:31:170710 2021) [[sssd[p11_child[70818 [do_card] (0x4000): Filtered certificates: (Mon Mar 1 15:16:31:170725 2021) [[sssd[p11_child[70818 [do_card] (0x4000): found cert[MARCO TREVISAN (PIN CNS0):CNS0][SN=TREVISAN,givenName=MARCO,CN="TRVMRC85T31A851Y/6090010669298009.YOrY0zOk5CdMby2Z2O/HnVRA8Ao=",OU=REGIONE TOSCANA,O=Actalis S.p.A.,C=IT] (Mon Mar 1 15:16:31:170776 2021) [[sssd[p11_child[70818 [do_card] (0x4000): module uri: pkcs11:library-manufacturer=PKCS%2311%20Kit;library-description=PKCS%2311%20Kit%20Proxy%20Module;library-version=1.1. (Mon Mar 1 15:16:31:170847 2021) [[sssd[p11_child[70818 [do_card] (0x4000): token uri: pkcs11:token=MARCO%20TREVISAN%20(PIN%20CNS0);manufacturer=IC:%20STMicroelectronics%3B%20mask:...;serial=6090010669298009;model=PKCS%2315%20emulated. (Mon Mar 1 15:16:31:287477 2021) [[
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
Ah, and of course the SSSD pem file is properly populated: $ sudo openssl crl2pkcs7 -nocrl -certfile /etc/sssd/pki/sssd_auth_ca_db.pem | openssl pkcs7 -print_certs -noout | grep subject | wc -l 421 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: Fix Released Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend The option 3) has been finally choosen, but we also require migration scripts on upgrade. [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then: 1) If you previously configured SSSD match rules and/or CA certificates: - You should still get your certificate public key printed as output - Configured login with smartcard should continue working 2) If SSSD was not configured to do smartcard authentication: - p11_child may fail if the card certificate was not previously added to the trusted DB, but this is outside of this test case. - What it matters is that the card is found.
[Touch-packages] [Bug 1916827] Re: Update libgweather to v40
Not sure, but do we need a FF for this? Is it retro-compatible, I guess, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1916827 Title: Update libgweather to v40 Status in libgweather package in Ubuntu: New Bug description: Without the latest gweather v40, gnome-shell 40 fails to start: (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No property application_id on GWeatherInfo WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29 _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31 _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25 _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34 _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14 _init@resource:///org/gnome/shell/ui/panel.js:778:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13 start@resource:///org/gnome/shell/ui/main.js:169:5 @:1:47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1916827/+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 1916827] Re: Update libgweather to v40
FFe I meant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1916827 Title: Update libgweather to v40 Status in libgweather package in Ubuntu: New Bug description: Without the latest gweather v40, gnome-shell 40 fails to start: (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No property application_id on GWeatherInfo WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29 _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31 _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25 _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34 _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14 _init@resource:///org/gnome/shell/ui/panel.js:778:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13 start@resource:///org/gnome/shell/ui/main.js:169:5 @:1:47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1916827/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
Should be fixed by
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Changed in: mutter (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in gnome-shell package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Triaged
Status in network-manager package in Ubuntu:
Invalid
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-3ubuntu1
Candidate: 3.38.3-3ubuntu1
Version table:
*** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg-query -W|grep mutter
gir1.2-mutter-7:amd64 3.38.3-3ubuntu1
libmutter-7-0:amd64 3.38.3-3ubuntu1
mutter3.38.3-3ubuntu1
mutter-common 3.38.3-3ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.30.0 connected started full enabled enabled
disabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+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 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1896171 Title: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in Mutter: Unknown Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+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
Re: [Touch-packages] [Bug 1905790] Re: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support for p11_child
>> Soo... Given we prefer to stay conservative and not change SSSD crypto > > I didn't say that! I know, I'm not saying that you took a decision on that but I was speaking in plural form as I recognize what you say in the sense that indeed there may be cases which we don't think of that we could break. >> backend fully (to be clear, I would have preferred it to follow >> upstream, not to provide a solution that will change in next LTS no >> matter what, and avoid having "frankensteins", but wasn't a strong >> requirement for me) I've been exploring ways to get only the component >> we care (p11_child) to use p11-kit and openssl. > > This is certainly a valuable angle to look at - thanks! > >> Robie, this would be better SRU approach? > > I think you misunderstand me. I'm not saying that your upload *has* to > be narrow. I've not formed an opinion that yet. What I'm saying is that > whatever size of scope you choose, there must be a regression analysis > that covers that scope. I understood this, reason why I thought that, given we have the chance to make it a narrower scope, then I tried to get that done. > But the analysis is still necessary and must not be skipped. Sure, not trying to do that, I'm just saying that I can't over all the cases myself. > I appreciate that sometimes it's harder or riskier to narrow the scope, > so I'm still open to widening the scope - *if* there is an appropriate > justification *and* full regression analysis of that wider scope > provided. Problem is that I'm quite sure we can't cover all the cases in a such complicated piece of software that may be configured in so many ways. Thus the reason I thought narrowing the scope was a better idea. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit
Re: [Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
> This does raise a question as to why we don't provide a system nssdb. I > think we should. I wonder if libnss or libnss3-tools could ship ca- > certificates hook to provide a system nssdb certificate store. I don't think it makes much sense at this point as most of the tools that were depending on NSS are leaving it anyways (curl, sssd...) and even Fedora is trying to get rid the usage of libnss completely and only support one crypto backend. So, I was thinking of doing that and it could be a possibility, but wouldn't still be a futurable solution as we'd regress in next LTS, and so we'd end up providing a solution for this LTS (for something that we didn't support so far) that is going to be broken in the next version. And I don't think it's a professional thing to ask our users to setup something and reconfigure it at next mayor update when we can start with the right foot now. > If we are changing backends, and certs were provided for the nss > backend, imho we should automatically convert them and keep them active > for the openssl backend. However unlikely it is that somebody made nss- > based p11_child work. Yeah, as I said isn't hard to do... The only problem I see is that the postinst script for NSS should depend on libnss3-tools (if we don't write us something in C that is shipped with SSSD) in order to read the certs and export them to the OpenSSL chain. As you said, it's quite unlikely, but could happen. > Actually, I don't see sssd at all using TLS connections, does it? It > seems that to perform ldaps connections, it uses libldap from openldap > which in turn uses GnuTLS. And any and all TLS LDAPS options are simply > passed through to the libldap. I had this feeling too, both looking at the code and at the various logs I found around, where I noticed that connection was handled differently, but not being the maximum expert here, I preferred not to talk. So happy you say so. > Inspecting all sssd binary packages I can see that only p11_child is the > only one using libssl and that does not do TLS. Yeah, exactly... It does only certs management basically. > Thus changing nss => openssl backend should be immaterial to what sssd > uses from them. Ok, good to hear. > I don't know how to configure p11_child but I do have > smartcard reader and multiple smartcards so happy to test things =) I wrote a bit of hints in this document, should help: https://hackmd.io/@3v1n0/ubuntu-smartcard-login -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a smar
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
** Description changed: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 + 3) Recompile SSSD completely to use libcrypto as backend + [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: - $ p11-kit list-modules + $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca- certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable - crypto backend for PKCS#11 operations. And behavior should not change - (if not improved), also assuming that upstream dropped NSS support - completely in latest release, keeping the same functionalities. + crypto backend for PKCS#11 operations. Behavior should not change, also + assuming that upstream dropped NSS support completely in latest release + [3], keeping the same functionalities. - The only binary that is really affected in its behavior is p11_child. + As per a further review of this by xnox [4], we can safely assume that + SSSD does not use libcrypto for operations where its behavior should + differ from NSS. As it's needed only for certificates handling. - And I'm confident this will break only those setup (if there are any, - given that smartcard access is currently not supported by ubuntu) that - ha
[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide
Also adding SSSD here, would be easy enough to make its default PAM CA ring to point to /etc/ssl/certs/ca-certificates.crt by default (and change-able in settings) but not sure if we want to go this route as it may make SSSD documentation confusing (as it everywhere mentions /etc/sssd/pki/sssd_auth_ca_db.pem or /etc/sssd/pki/sssd_auth_ca_db.pem). Maybe a nice way would be to provide a default sssd.conf file that explicitly set that instead of hard-coding it, so we won't break current installations. ** Also affects: sssd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in sssd package in Ubuntu: New Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
** Description changed: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. - Then the tool might fail if the card certificate is not added to the ca- - certificates.crt, but this is outside the scope of the test case. + Then: + 1) If you previously configured SSSD match rules and/or CA certificates: + - You should still get your certificate public key printed as output + - Configured login with smartcard should continue working - What it matters is that the card is found. + 2) If SSSD was not configured to do smartcard authentication: + - p11_child may fail if the card certificate was not previously added to + the trusted DB, but this is outside of this test case. + - What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. Behavior should not change, also assuming that upstream dropped NSS support completely in latest release [3], keeping the same functionalities. As per a further review of this by xnox [4], we can safely assume that SSSD does not use libcrypto for operations where its behavior should differ from NSS. As it's needed only for
[Touch-packages] [Bug 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Daniel, do you think there would be any problem in overriding the default configuration we ship to have auto_switch=2 set by default? -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1913756] [NEW] alure is loading the wrong libfluidsynth version in focal
Public bug reported: Error loading libfluidsynth.so.1: libfluidsynth.so.1: cannot open shared object file: No such file or directory It's due to the lib to be d'loaded and soname changed. ** Affects: fluidsynth (Ubuntu) Importance: High Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1913756 Title: alure is loading the wrong libfluidsynth version in focal Status in fluidsynth package in Ubuntu: Triaged Bug description: Error loading libfluidsynth.so.1: libfluidsynth.so.1: cannot open shared object file: No such file or directory It's due to the lib to be d'loaded and soname changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1913756/+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 1913756] Re: alure is loading the wrong libfluidsynth version in focal
** Patch added: "alure-fixed-dload.debdiff" https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1913756/+attachment/5458080/+files/alure-fixed-dload.debdiff ** Tags added: needs-design -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1913756 Title: alure is loading the wrong libfluidsynth version in focal Status in fluidsynth package in Ubuntu: Triaged Bug description: Error loading libfluidsynth.so.1: libfluidsynth.so.1: cannot open shared object file: No such file or directory It's due to the lib to be d'loaded and soname changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1913756/+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 1931901] Re: Revert background key patch removal breaks dependent packages
Yeah, wasn't using the libgnome-desktop3 API though, so we should just drop it from unity-settings-daemon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1931901 Title: Revert background key patch removal breaks dependent packages Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: in the package gnome-desktop3 there is a custom ubuntu patch that tries to write to the draw-background key that has now been removed in gsettings-desktop-schemas 40.0-1ubuntu1 All packages that depend on the gnome-desktop3 library now crash such as budgie-desktop Suggestion - either re-add the patch again ... or revert the gnome- desktop3 custom patch. The latter option changes the symbols so probably I'm guessing a so- name version bump is needed and any dependent packages need a rebuild? I'll try to locally rebuild gnome-desktop3 without the custom ubuntu patch to see what happens with budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jun 14 20:52:16 2021 InstallationDate: Installed on 2021-06-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+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 1937922] Re: gtk4 not built for i386
I think wasn't built as per missing pango build on i386, that's now fixed so shoudl just trigger a rebuild of gtk4 itself. Probably though an upload though. ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1937922 Title: gtk4 not built for i386 Status in ibus package in Ubuntu: New Bug description: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Kay-Heng, what's the status of the linux image landing on bionic? Can you help in verify this once we've all there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Since no regression shell-side has been reported so far and verification has beend done with a matching kernel, I think we can safely verify this SRU (also coming as part of GNOME upstream changes) unblocking it from the queue. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved
Run test for test_move_item inside glib 2.56.4-0ubuntu0.18.04.2 and it works as expected. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1760569 Title: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved Status in glib2.0 package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Status in nautilus source package in Bionic: Invalid Bug description: [ Description ] A crasher when using nautilus. No clear reproducer. [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Make sure nautilus works, and that the error tracker buckets listed below at least don't increase more rapidly (but hopefully tail off with the new version) [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. [ Original description ] Happens when there's a "rename" to a file to its same value, no known reproducer though. Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1816547] Re: SRU 2.56.4 to bionic
As per GNOME MRE, package hit properly proposed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816547 Title: SRU 2.56.4 to bionic Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] New upstream bug fix microrelease * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582) * Bug fixes: #1588 Moving a bookmark item to the same URI causes a crash #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56 Plus fix for LP: #1760569 [ QA ] Under the GNOME MRE, believe all bugs that upstream says are fixed are really fixed without explicitly verifying them. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Test various parts of the desktop. - Logging in - Shutting down - Starting a variety of apps and checking that they work + rhythmbox (play a song using gstreamer) + cheese (look at yourself with your webcam using gstreamer) + network-manager + epiphany (web stuff works) Monitor the error tracker for any increases. [ Regression potential ] It's GLib. A regression could break the whole desktop, or any part of it... Our QA should help us have confidence that the update is at least not that bad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1755232] Re: Xorg crashes when tapping Unity system tray icons
This is fixed in https://gitlab.freedesktop.org/xorg/xserver/commit/35e5a76cc1d02801fadd49d12e60664b02e4bebc Will be in next xorg revision (if not cherry-picked earlier) ** Changed in: xorg (Ubuntu) Status: New => In Progress ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1755232 Title: Xorg crashes when tapping Unity system tray icons Status in xorg package in Ubuntu: In Progress Bug description: This bug requires some prerequisites to reproduce: 0. Make sure you've got multitouch-enable display 1. Start Unity+xorg session 2. Verify that four-finger tap gesture works (shows unity app search tool) 3. Wait some time for this gesture to stop working - this is another bug, not necessarily xorg one, already known and thought to be connected with Google Chrome running. 4. Once it stops working, quickly tap all icons in the Unity system tray like you would be pretending to play a piano (tapping them individually or slowly does not cause any problems). 5. Xorg crashes immediately. This scenario is 100% reproducible on my setup. I recompiled xorg with debug info enabled and got this nice trace: [ 22705.385] (EE) [ 22705.385] (EE) Backtrace: [ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f] [ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) [0x7f382f64414f] [ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f382f2880bb] [ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) [0x7f382f289f5d] [ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) [0x7f382f2d22bd] [ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) [0x7f382f2d9f7a] [ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) [0x7f382f2de0fe] [ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) [0x7f382f2e044e] [ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32] [ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) [0x562a3698428f] [ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) [0x562a3698ea8b] [ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) [0x562a369bc371] [ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689] [ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) [0x562a3696e488] [ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9] [ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3] [ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22] [ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f382f2721c1] [ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a] [ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] Looks like FreeGrab tries to free pGrab for the second time (some multithreading issue?) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Mar 12 17:03:34 2018 DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2017-09-01 (192 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HES2130Q ProcEnviron: LANGUAGE=pl_PL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 i915.enable_guc_submissi
[Touch-packages] [Bug 1803487] Re: gnome-shell crashes in libgweather gweather_location_common_deserialize
** Summary changed: - /usr/bin/gnome-shell:11:gweather_location_common_deserialize:gweather_location_format_two_deserialize:gweather_location_deserialize:ffi_call_unix64:ffi_call + gnome-shell crashes in libgweather gweather_location_common_deserialize ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released ** Also affects: libgweather (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1803487 Title: gnome-shell crashes in libgweather gweather_location_common_deserialize Status in gnome-shell package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+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 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libgweather (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libgweather (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Description changed: + [ Description ] + + The second stable release in the 3.28 series. + + [ QA ] + + Run Ubuntu session, expect the shell to show weather information and not + to crash on timezone changes + + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + [ Regresison potential ] + + Weather location might be leaked. However this is very safe as upstream + fix comes with proper testing. + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1803487 Title: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64 → ffi_call Status in gnome-shell package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: New Bug description: [ Description ] The second stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to show weather information and not to crash on timezone changes https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Weather location might be leaked. However this is very safe as upstream fix comes with proper testing. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+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 1805200] [NEW] Xorg crashes when it tries to resume a scale transformation after that Screen has been closed
Public bug reported: Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous versions Very easy to reproduce: Start a simple (empty) X server instance (say Xorg :2 vt8) Set a scale transformation xrandr -d :2 --output eDP-1 --scale 2x2 Call xrandr again so that the server tries to resume the previous transformation xrandr -d :2 I've addressed the issue at https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed various fixes for that, but so far no feedback. Marking it as incoming rls bug as this needs to be addressed as per supporting xrandr scaling support in desktop. ** Affects: xorg (Ubuntu) Importance: High Assignee: Timo Aaltonen (tjaalton) Status: Triaged ** Tags: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1805200 Title: Xorg crashes when it tries to resume a scale transformation after that Screen has been closed Status in xorg package in Ubuntu: Triaged Bug description: Happens in X.Org X Server 2:1.20.3-1ubuntu1, but also previous versions Very easy to reproduce: Start a simple (empty) X server instance (say Xorg :2 vt8) Set a scale transformation xrandr -d :2 --output eDP-1 --scale 2x2 Call xrandr again so that the server tries to resume the previous transformation xrandr -d :2 I've addressed the issue at https://gitlab.freedesktop.org/xorg/xserver/issues/14 and proposed various fixes for that, but so far no feedback. Marking it as incoming rls bug as this needs to be addressed as per supporting xrandr scaling support in desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1805200/+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 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64
No crash has been seen here using libgweather 3.28.2-1~ubuntu18.04.1 for some weeks now, so we can safely mark as verified. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1803487 Title: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64 → ffi_call Status in gnome-shell package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in libgweather source package in Bionic: Fix Committed Bug description: [ Description ] The second stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to show weather information and not to crash on timezone changes https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Weather location might be leaked. However this is very safe as upstream fix comes with proper testing. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+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 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user
Not a gnome-shell issue, but an accountsservice one. ** Summary changed: - /usr/bin/gnome-shell:11:g_str_hash:g_hash_table_hash_to_index:g_hash_table_lookup_node:g_hash_table_lookup:update_user + gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu) Status: New => In Progress ** Changed in: accountsservice (Ubuntu) Status: In Progress => Triaged ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/issues #55 https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/55 ** Also affects: accountsservice via https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/55 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1832865 Title: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1832865/+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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Importance: Medium => Unknown ** Changed in: mesa Remote watch: freedesktop.org Bugzilla #64202 => gitlab.freedesktop.org/mesa/mesa/issues #727 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Unknown Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+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 1842118] [NEW] [FFe] Update tracker(-miners) to 2.3.0
Public bug reported:
Ubuntu is stuck with tracker 2.1.8 and tracker miners 2.1.6, while GNOME
3.34 will ship versions 2.3.0 of both.
Main changes since archive version, in tracker:
- Support for storing Musicbrainz metadata in the multimedia ontology.
- Fix detection of files that need writeback
- Fix crashes and invalid memory writes
- Fixed initialization of virtual tables
- Fixed segmentation fault in libtracker-miner
- Don't try to create JSON-LD nodes with unsigned integers
- Handle correctly backreferences in TrackerResource tree
- Fixed handling doubles with exponents in SPARQL
- Don't limit to specific desktop environments
- Fix unichar unescaping
- Correctly Handle BIND in first place of a triples block
- Fix possible deadlock on WAL checkpoint
- Fix some double values not being deleted
- Fixed CHANGES_DONE_HINT handling in TrackerMonitor
- Ported data generator utilities to python3
- Ported functional tests to python3, reformatted to PEP-8
- Correctly apply ignored-directories-with-content filter on monitor updates
- Multiple memory leak and memory corruption fixes
- New SPARQL parser, able to generate SQL that is generally more readable
and at places performs better. Multiple buglets fixed in the process
- Much improved support of SPARQL1.1 features and syntax that was missing:
* Property paths: Allowing to match connectivity between two resources
by an arbitrary length path. There is a number of supported operators
(alternative, sequence, oneOrMany, ...) that can be combined, e.g:
SELECT ?s ?p { ?s ^(nfo:belongsToContainer*)/(nie:url|nie:title)
?p }
Only the negated path operator (!) is not supported at the moment.
* Support for fully unrestricted queries, eg:
SELECT ?s ?p ?o { ?s ?p ?o } ORDER BY ?o ?p ?s
Queries with unrestricted predicate (?p in the example above) were
just supported in a very restricted set of situations. All those
limitations are gone.
* MINUS allows subtracting the solutions that match the given triples
template, eg:
SELECT ?s { ?s a nfo:Media } MINUS { ?s a nfo:MusicPiece }
- Support for prepared statements. TrackerSparqlStatement can be built
with SELECT queries containing (custom) ~var syntax, and updating
their values before obtaining a cursor.
- tracker-store now automatically shuts down on inactivity.
- More property paths supported, new operators supported are -, +, ? and |,
only the ! operator is not supported yet.
- Improve error handling in DBus backend
- New SPARQL parser, able to support more 1.1 features and generating
friendlier SQL at places. There is initial support for property
paths (/ and ^), and other missing 1.1 syntax (MINUS, SHA384, ...).
More improvements are expected to happen in the future thanks to this.
- Support for prepared statements. TrackerSparqlStatement can be built
with SELECT queries containing (custom) ~var syntax, and updating
their values before obtaining a cursor.
NEWS upstream file changes:
https://gitlab.gnome.org/GNOME/tracker/compare/2.1.8...2.2.99.0#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
While in tracker-miners:
- Support for reading Musicbrainz metadata from audio files.
- Tracker Writeback now uses GStreamer to write metadata to audio files,
instead of depending on taglib directly.
- Directories will now be ignored if they contain a file named `.nomedia`.
A file named `.trackerignore` has the same effect, but the `.nomedia` file
brings us in line with Android.
- Removed obsolete 'max-media-art-width' setting.
- Functional tests now use python3
- Fix text extractor handling of non-existent files
- Fix indexing of tracks in FLAC files
- Whitelist syscall fadvise64_64
- Fix failed functional tests being reported as successful
- Fixes to desktop file indexing
- The functionality of tracker-miner-apps has been adopted by
tracker-miner-fs/tracker-extract.
- Updated tracker-miner-fs and tracker-miner-rss to use TrackerResource
NEWS upstream file changes:
https://gitlab.gnome.org/GNOME/tracker-miners/compare/2.1.6...2.2.99.0#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8
So changes are quite a lot and with lots of improvements, that it's
quite important to test a bit more before next LTS, so having in 19.10
would be smart.
** Affects: tracker (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: New
** Affects: tracker-miners (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: New
** Changed in: tracker (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Also affects: tracker-miners (Ubuntu)
Importance: Undecided
Status: New
** Changed in: tracker-miners (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: tracker-miners (U
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Kai-Heng Feng, What's the status of the kernel fix in bionic? As to verify UI fixes we should get everything in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => In Progress ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: upower (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: upower (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: linux (Ubuntu Bionic) Assignee: Marco Trevisan (Treviño) (3v1n0) => Kai-Heng Feng (kaihengfeng) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: upower (Ubuntu) Importance: Undecided => Medium ** Changed in: upower (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: upower (Ubuntu) Status: Confirmed => In Progress ** Changed in: upower (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:r
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Augustin, What version of ubuntu have you tested? Can you please paste here the output of the command apt-cache policy linux-image-generic upower gnome-control-center gnome-shell Are you also using a fixed kernel? ** Changed in: upower (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: gnome-control-center (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-control-center (Ubuntu Bionic) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved
** Changed in: glib2.0 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1760569 Title: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved Status in glib2.0 package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: Happens when there's a "rename" to a file to its same value, no known reproducer though. Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1816547] [NEW] SRU 2.56.4 to bionic
Public bug reported: * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582) * Bug fixes: #1588 Moving a bookmark item to the same URI causes a crash #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56 Plus fix for LP: #1760569 ** Affects: glib2.0 (Ubuntu) Importance: Medium Assignee: Iain Lane (laney) Status: Triaged ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816547 Title: SRU 2.56.4 to bionic Status in glib2.0 package in Ubuntu: Triaged Bug description: * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582) * Bug fixes: #1588 Moving a bookmark item to the same URI causes a crash #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56 Plus fix for LP: #1760569 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1726322] Re: Suggested and Destructive action buttons in headerbar have wrong gradients in maximized windows
** Changed in: ubuntu-themes Status: In Progress => Fix Released -- 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/1726322 Title: Suggested and Destructive action buttons in headerbar have wrong gradients in maximized windows Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Artful: Fix Released Bug description: [Impact] Suggested and Desctructive action (simple-scan is an example for both) buttons still have the "normal" gradient when the window is maximized, while this should be inverted. See https://usercontent.irccloud-cdn.com/file/hm2uCy3D/image.png (shown both for reference) [Test case] 1. Run simple scan 2. Maximize the window 3. The gradient should have consistent direction with other buttons around [Regression potential] Background gradients for windows with such buttons might be wrong in normal windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1726322/+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 1762465] Re: Nautilus sidebar theming is confusing
** Changed in: ubuntu-themes Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1762465 Title: Nautilus sidebar theming is confusing Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The new theming of the Nautilus sidebar is confusing to users. The icons and the icon labels have a different background colour, and when a specific location is selected the background colour of the selected icon changes to be the same as the background colour of the labels, while the other icons have a darker background colour. This is giving the impression that the text labels are a hierarchy of the icon, rather than simply being labels associated with each icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1762465/+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 1726318] Re: Destructive actions on headerbar aren't properly themed
** Changed in: ubuntu-themes Status: In Progress => Fix Released -- 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/1726318 Title: Destructive actions on headerbar aren't properly themed Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Artful: Fix Released Bug description: [ Impact ] On simple scan (for example) there's a .destructive-action button in the headerbar and it's not drawn as red unless the button is hovered, clicked or unfocused. It also uses inconsistent gradients [ Test case ] 1. Run gnome-scan 2. Start a scan session (or use the inspector to set the "Stop" button as visible) 3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered) [ Regression Potential] Destructive buttons in headerbar could be broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1726318/+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 1568273] Re: Visual issues with linked buttons
** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Fix Released -- 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/1568273 Title: Visual issues with linked buttons Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: GTK buttons have many visual glitches. It looks like all default themes (Radiance, Ambiance and High Contrast) aren't compatible with GTK 3.18 - Open Nautilus, on the left tool bar click on "Documents", then click on "Home". After that the "Home" button on the top bar will look all rounded, where it shouldn't be in the side next to the adjacent button: https://launchpadlibrarian.net/253125292/1-bad.png - On the top bar, point the mouse over the "Home" button. After that the "Home" button looks OK: https://launchpadlibrarian.net/253125315/2-ok.png - Keep Nautilus open and don't touch it. Open System Settings and go back to Nautilus. After that on the top bar the "Home" button suddenly looks OK: https://launchpadlibrarian.net/253125315/2-ok.png - On the left tool bar, click on "Recent". After that the right side of the "Recent" button doesn't have all its corners rounded: https://launchpadlibrarian.net/253125350/3-bad.png - On the top bar, point the mouse over the "Recent" button. Then the button will look fine until you move the mouse pointer away. This is just example, but there are many more visual issues. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: light-themes 14.04+16.04.20160324.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 9 13:23:43 2016 InstallationDate: Installed on 2016-04-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160407) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1568273/+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 1765561] [NEW] Nautilus path bar buttons are inconsistent
Public bug reported: As per: https://github.com/CanonicalLtd/desktop-design/issues/28 There are a lot of different greys in the breadcrumbs at the top of the Nautilus window which need some rationalisation. Also it's very hard to discern what is selected. ** Affects: ubuntu-themes (Ubuntu) Importance: High Assignee: Carlo Lobrano (c-lobrano) Status: In Progress ** Branch linked: lp:~c-lobrano/ubuntu-themes/pathbar-review -- 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/1765561 Title: Nautilus path bar buttons are inconsistent Status in ubuntu-themes package in Ubuntu: In Progress Bug description: As per: https://github.com/CanonicalLtd/desktop-design/issues/28 There are a lot of different greys in the breadcrumbs at the top of the Nautilus window which need some rationalisation. Also it's very hard to discern what is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765561/+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 1759754] Re: Ambiance titlebar gradient doesn't match the Terminal menubar colour
** No longer affects: gnome-terminal (Ubuntu) ** Changed in: ubuntu-themes (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Summary changed: - Ambiance titlebar gradient doesn't match the Terminal menubar colour + Ambiance titlebar gradient doesn't match the menubar colour -- 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/1759754 Title: Ambiance titlebar gradient doesn't match the menubar colour Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Ambiance titlebar gradient doesn't match the Terminal menubar colour. There's a hard line visible between a terminal's titlebar and menu bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1759754/+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 1762465] Re: Nautilus sidebar theming is confusing
Not sure how this can be solved... Something like https://i.imgur.com/ZVXQ1ku.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/1762465 Title: Nautilus sidebar theming is confusing Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The new theming of the Nautilus sidebar is confusing to users. The icons and the icon labels have a different background colour, and when a specific location is selected the background colour of the selected icon changes to be the same as the background colour of the labels, while the other icons have a darker background colour. This is giving the impression that the text labels are a hierarchy of the icon, rather than simply being labels associated with each icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1762465/+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 1762465] Re: Nautilus sidebar theming is confusing
Not sure how this can be solved... Something like https://i.imgur.com/RA9esFK.png would be better? -- 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/1762465 Title: Nautilus sidebar theming is confusing Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The new theming of the Nautilus sidebar is confusing to users. The icons and the icon labels have a different background colour, and when a specific location is selected the background colour of the selected icon changes to be the same as the background colour of the labels, while the other icons have a darker background colour. This is giving the impression that the text labels are a hierarchy of the icon, rather than simply being labels associated with each icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1762465/+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
