[Touch-packages] [Bug 1071930] Re: apport-bug options not mentioned in manpage synopsis
The thing is `apport-bug` is just a wrapper script. It doesn't process any of its arguments and just passes over all positional parameters to one of `apport-cli`, `apport-gtk` and `apport-kde`. The reason `apport- bug --help` shows a minimal subset of options is that in this mode only a handful of them are supported, or at least are meaningful. If invoked as `apport-bug`, `apport-cli` by default starts in File bug report mode, so mentioning it is redundant. I think both the man page and the help message are fine as they are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1071930 Title: apport-bug options not mentioned in manpage synopsis Status in Apport: Triaged Status in One Hundred Papercuts: Confirmed Status in apport package in Ubuntu: Triaged Bug description: The man page of apport-bug does not mention in the synopsis that apport-bug takes options. You will not be informed about additional options until you reach the options section. The options section says: "Please see the apport-cli(1) manpage for possible options." Can you add that apport-bug takes the same parameters than apport-cli, they work the same, and the only different is that apport-bug has a GUI and apport-cli is for the command line (if this is correct)? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: apport 2.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Oct 26 23:49:11 2012 InstallationDate: Installed on 2012-04-24 (184 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to quantal on 2012-10-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1071930/+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 1940097] Re: A forgotten "space"
@eshagh, thank you for noticing this typo and reporting a bug.
This patch adds the missing space.
** Changed in: python-apt (Ubuntu)
Assignee: (unassigned) => Akbarkhon Variskhanov (kbar)
** Changed in: python-apt (Ubuntu)
Status: Confirmed => In Progress
** Patch added: "1-2.3.0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1940097/+attachment/5598106/+files/1-2.3.0ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1940097
Title:
A forgotten "space"
Status in python-apt package in Ubuntu:
In Progress
Bug description:
Hi
A "space" character has been forgotten in the "apt/package.py" file and line
"592".
I found this error while translating.
https://translations.launchpad.net/ubuntu/impish/+source/python-apt/+pots/python-apt/fa/36/+translate
if not dsc:
return _("Missing description for '%s'." <===
"Please report.") % (self.package.name)
This line should be like this
if not dsc:
return _("Missing description for '%s'. " <===
"Please report.") % (self.package.name)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1940097/+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 1975735] [NEW] Build with libedit support by default
Public bug reported: The libedit support needs to be enabled by default. Even though dash is the default sh on Ubuntu and is mainly used to run POSIX shell scripts, it's also a good interactive shell for testing scripts and prototype code. Enabling history will make life much easier. Otherwise, the "Command Line Editing" section and the "fc" command should be removed from the man page as it's currently misleading. ** Affects: dash (Ubuntu) Importance: Undecided Status: Opinion ** Changed in: dash (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1975735 Title: Build with libedit support by default Status in dash package in Ubuntu: Opinion Bug description: The libedit support needs to be enabled by default. Even though dash is the default sh on Ubuntu and is mainly used to run POSIX shell scripts, it's also a good interactive shell for testing scripts and prototype code. Enabling history will make life much easier. Otherwise, the "Command Line Editing" section and the "fc" command should be removed from the man page as it's currently misleading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1975735/+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 1969305] Re: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well
It's one of the shell scripts in https://git.launchpad.net/ubuntu/+source/xorg/tree/debian/local/Xsession.d, which is then installed to /etc/X11/Xsession.d The most appropriate would be 60x11-common_xdg_path, where CONFIG and DATA dirs are exported from. I'm on Xubuntu 20.04 but I checked the devel branch. -- 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/1969305 Title: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well Status in xorg package in Ubuntu: Incomplete Bug description: These base directories should also be included to make scripting easier. Their default values should be set as per XDG base-dir spec, i.e.: XDG_CONFIG_HOME="$HOME/.config" XDG_DATA_HOME="$HOME/.local/share" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969305/+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 1969305] [NEW] Export XDG_CONFIG_HOME and XDG_DATA_HOME as well
Public bug reported: These base directories should also be included to make scripting easier. Their default values should be set as per XDG base-dir spec, i.e.: XDG_CONFIG_HOME="$HOME/.config" XDG_DATA_HOME="$HOME/.local/share" ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1969305 Title: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well Status in xorg package in Ubuntu: New Bug description: These base directories should also be included to make scripting easier. Their default values should be set as per XDG base-dir spec, i.e.: XDG_CONFIG_HOME="$HOME/.config" XDG_DATA_HOME="$HOME/.local/share" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969305/+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 1954311] Re: Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action
Replaced -prune with -maxdepth 1 because -delete automatically turns on -depth. Reverted the second command back to its original state as -delete can't delete directories that aren't empty. ** Patch added: "apport.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1954311/+attachment/5554429/+files/apport.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1954311 Title: Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action Status in apport package in Ubuntu: New Bug description: Executing `rm` as a separate process each time for every single file is unnecessary and inefficient. The option '-delete' should be used instead. Patch is included below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1954311/+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 1954311] Re: Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action
Also removed -prune primary as it conflicted with -depth, which is automatically turned on by -delete. ** Patch added: "removed_prune_primary.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1954311/+attachment/5553122/+files/removed_prune_primary.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1954311 Title: Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action Status in apport package in Ubuntu: New Bug description: Executing `rm` as a separate process each time for every single file is unnecessary and inefficient. The option '-delete' should be used instead. Patch is included below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1954311/+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 1955316] Re: Wishlist - Make apport entries copy-able
** Summary changed: - Wishlist - Make apport entires copy-able + Wishlist - Make apport entries copy-able -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1955316 Title: Wishlist - Make apport entries copy-able Status in Apport: New Status in apport package in Ubuntu: New Bug description: Due to previous experiences with other software I'm not comfortable to just send some large unchecked logs. Apparently that might also be an issue with apport, which is why it's disabled by default in Ubuntu- Mater. I'd still like to help with bug-reports by providing the information which I can check easily. Not being able to just copy entries from the gui makes this much more time-consuming then necessary and might result in cases where users provide less information than they would otherwise. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1955316/+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 1952083] Re: Add support for Beige Goby
@tjaalton, I always use the main official server (archive.ubuntu.com). Anyway, there were no errors today and the update went smoothly. -- 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/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+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 1954311] [NEW] Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action
Public bug reported: Executing `rm` as a separate process each time for every single file is unnecessary and inefficient. The option '-delete' should be used instead. Patch is included below. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Patch added: "apport.patch" https://bugs.launchpad.net/bugs/1954311/+attachment/5546501/+files/apport.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1954311 Title: Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action Status in apport package in Ubuntu: New Bug description: Executing `rm` as a separate process each time for every single file is unnecessary and inefficient. The option '-delete' should be used instead. Patch is included below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1954311/+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 1953151] Re: Doubled control operators before `alert` will have their second characted appear in the body of the message
** Description changed: + Patch attached below. + [Description] Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message, for example with: sleep 5s && alert notify-send will display the following message: sleep 5s & which is obviously undesirable and not intended. [Suggested fix] Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1953151 Title: Doubled control operators before `alert` will have their second characted appear in the body of the message Status in bash package in Ubuntu: New Bug description: Patch attached below. [Description] Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message, for example with: sleep 5s && alert notify-send will display the following message: sleep 5s & which is obviously undesirable and not intended. [Suggested fix] Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1953151/+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 1953151] Re: Doubled control operators before `alert` will have their second characted appear in the body of the message
** Description changed: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message, for example: sleep 5s && alert + + will display the following message: + + sleep 5s & Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be - printed in the body of a message, for example: + printed in the body of a message, for example with: sleep 5s && alert - will display the following message: + notify-send will display the following message: sleep 5s & Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: + [Description] + Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message, for example with: sleep 5s && alert notify-send will display the following message: sleep 5s & + + which is obviously not intended and undesirable + + [Suggested fix] Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Description] Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message, for example with: sleep 5s && alert notify-send will display the following message: sleep 5s & - which is obviously not intended and undesirable + which is obviously undesirable and not intended. [Suggested fix] Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu.
[Touch-packages] [Bug 1953151] Re: Doubled control operators before `alert` will have their second characted appear in the body of the message
** Patch added: "skel.bashrc.patch" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1953151/+attachment/5545229/+files/skel.bashrc.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1953151 Title: Doubled control operators before `alert` will have their second characted appear in the body of the message Status in bash package in Ubuntu: New Bug description: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message, for example: sleep 5s && alert Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1953151/+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 1953151] Re: Doubled control operators before `alert` will have their second characted appear in the body of the message
** Description changed: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be - printed in the body of a message. Adding the asterisk after the [;&|] - bracket expression fixes it: + printed in the body of a message, for example: + + sleep 5s && alert + + Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1953151 Title: Doubled control operators before `alert` will have their second characted appear in the body of the message Status in bash package in Ubuntu: New Bug description: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message, for example: sleep 5s && alert Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1953151/+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 616028] Re: add an "alert" alias, which can optionally be added after long running commands
Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of the message. Adding the asterisk after the [;&|] bracket expression fixes it. alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' Bug #1953151 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/616028 Title: add an "alert" alias, which can optionally be added after long running commands Status in bash package in Ubuntu: Fix Released Bug description: Binary package hint: bash This bug is closely related, though slightly different from Bug #315932. I recently posted: http://blog.dustinkirkland.com/2010/07/dear-command-line-please-ping-me-when.html This post received some positive feedback in the comments and in IRC. A number of people have asked for this sort of functionality in the default Ubuntu .bashrc. I think this is a perfectly reasonable request. It doesn't get in the way, as current users must consciously append "; alert" onto their long running commands. We can experiment with this as a proof-of-concept in Maverick, and perhaps look at better ways of doing this automagically by default (again, see the really interesting implementation in Bug #315932). I have tested: a) when libnotify-bin is not installed -- command-not-found prints a useful error message b) when gnome-terminal is not installed -- icons aren't present; notify message pops up without icons; still functional c) over ssh -X -- works fine, assuming the client and host has the necessary packages to do libnotify stuff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/616028/+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 1953151] [NEW] Doubled control operators before `alert` will have their second characted appear in the body of the message
Public bug reported: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message. Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be - printed in the body of the message. Adding the asterisk after the [;&|] - bracket expression fixes it. + printed in the body of a message. Adding the asterisk after the [;&|] + bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1953151 Title: Doubled control operators before `alert` will have their second characted appear in the body of the message Status in bash package in Ubuntu: New Bug description: Separating the first part of a list and the `alert` part with && (or any of the doubled control operators) will result the second character to be printed in the body of a message. Adding the asterisk after the [;&|] bracket expression fixes it: alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]*\s*alert$//'\'')"' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 3 16:56:21 2021 InstallationDate: Installed on 2021-05-17 (200 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1953151/+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 1952083] Re: Add support for Beige Goby
This version wants to break dependencies and introduces a conflict between packages. Xubuntu 20.04.3 LTS ** Attachment added: "Screenshot_2021-12-02_13-21-29.png" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952083/+attachment/5544859/+files/Screenshot_2021-12-02_13-21-29.png -- 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/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+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 1943318] Re: systemd-shutdown[1]: Failed to finalize file systems, ignoring.
** Attachment added: "Reached target Reboot." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943318/+attachment/5524534/+files/Screenshot_2021-09-11_16-02-20.png -- 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/1943318 Title: systemd-shutdown[1]: Failed to finalize file systems, ignoring. Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Impish Indri (development branch) Release: 21.10 Impish Indri 20210911 build, erase disk and install, packages updated after installation Installation failed at step 15: bug #1925314 "no eject media message after install". System restarted successfully. Changed downloading updates to main server and was prompted to update a few packages. After updates finished, pressed "Restart now". This is the result. Updated packages: Start-Date: 2021-09-11 15:56:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.83' Upgrade: libedata-book-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), libebook-1.2-20:amd64 (3.40.2-1build1, 3.40.4-1), libgomp1:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libecal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), libedataserver-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), evolution-data-server:amd64 (3.40.2-1build1, 3.40.4-1), libgcr-base-3-1:amd64 (3.38.1-2, 3.40.0-3), evolution-data-server-common:amd64 (3.40.2-1build1, 3.40.4-1), open-vm-tools-desktop:amd64 (2:11.2.5-2ubuntu1, 2:11.3.0-2), gcr:amd64 (3.38.1-2, 3.40.0-3), libgcr-ui-3-1:amd64 (3.38.1-2, 3.40.0-3), libcamel-1.2-62:amd64 (3.40.2-1build1, 3.40.4-1), libxmlsec1:amd64 (1.2.31-1, 1.2.32-1), libebook-contacts-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), libedataserverui-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), open-vm-tools:amd64 (2:11.2.5-2ubuntu1, 2:11.3.0-2), libgupnp-av-1.0-2:amd64 (0.12.11-2, 0.12.11-3), cpp-11:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), printer-driver-pnm2ppa:amd64 (1.13+nondbs-0ubuntu7, 1.13+nondbs-0ubuntu8), libedata-cal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), gcc-11-base:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), groff-base:amd64 (1.22.4-6, 1.22.4-7), libgck-1-0:amd64 (3.38.1-2, 3.40.0-3), gir1.2-gck-1:amd64 (3.38.1-2, 3.40.0-3), libstdc++6:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libebackend-1.2-10:amd64 (3.40.2-1build1, 3.40.4-1), libxmlsec1-openssl:amd64 (1.2.31-1, 1.2.32-1), gir1.2-gcr-3:amd64 (3.38.1-2, 3.40.0-3), libgcc-s1:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1) End-Date: 2021-09-11 15:57:17 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 11 16:07:46 2021 InstallationDate: Installed on 2021-09-11 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=54dc5a9f-dd8b-435f-a346-0647390276de ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943318/+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 1943318] Re: systemd-shutdown[1]: Failed to finalize file systems, ignoring.
** Attachment added: "systemd-shutdown" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943318/+attachment/5524535/+files/Screenshot_2021-09-11_16-02-38.png -- 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/1943318 Title: systemd-shutdown[1]: Failed to finalize file systems, ignoring. Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Impish Indri (development branch) Release: 21.10 Impish Indri 20210911 build, erase disk and install, packages updated after installation Installation failed at step 15: bug #1925314 "no eject media message after install". System restarted successfully. Changed downloading updates to main server and was prompted to update a few packages. After updates finished, pressed "Restart now". This is the result. Updated packages: Start-Date: 2021-09-11 15:56:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.83' Upgrade: libedata-book-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), libebook-1.2-20:amd64 (3.40.2-1build1, 3.40.4-1), libgomp1:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libecal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), libedataserver-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), evolution-data-server:amd64 (3.40.2-1build1, 3.40.4-1), libgcr-base-3-1:amd64 (3.38.1-2, 3.40.0-3), evolution-data-server-common:amd64 (3.40.2-1build1, 3.40.4-1), open-vm-tools-desktop:amd64 (2:11.2.5-2ubuntu1, 2:11.3.0-2), gcr:amd64 (3.38.1-2, 3.40.0-3), libgcr-ui-3-1:amd64 (3.38.1-2, 3.40.0-3), libcamel-1.2-62:amd64 (3.40.2-1build1, 3.40.4-1), libxmlsec1:amd64 (1.2.31-1, 1.2.32-1), libebook-contacts-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), libedataserverui-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), open-vm-tools:amd64 (2:11.2.5-2ubuntu1, 2:11.3.0-2), libgupnp-av-1.0-2:amd64 (0.12.11-2, 0.12.11-3), cpp-11:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), printer-driver-pnm2ppa:amd64 (1.13+nondbs-0ubuntu7, 1.13+nondbs-0ubuntu8), libedata-cal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), gcc-11-base:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), groff-base:amd64 (1.22.4-6, 1.22.4-7), libgck-1-0:amd64 (3.38.1-2, 3.40.0-3), gir1.2-gck-1:amd64 (3.38.1-2, 3.40.0-3), libstdc++6:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libebackend-1.2-10:amd64 (3.40.2-1build1, 3.40.4-1), libxmlsec1-openssl:amd64 (1.2.31-1, 1.2.32-1), gir1.2-gcr-3:amd64 (3.38.1-2, 3.40.0-3), libgcc-s1:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1) End-Date: 2021-09-11 15:57:17 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 11 16:07:46 2021 InstallationDate: Installed on 2021-09-11 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=54dc5a9f-dd8b-435f-a346-0647390276de ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943318/+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 1943318] [NEW] systemd-shutdown[1]: Failed to finalize file systems, ignoring.
Public bug reported: Description:Ubuntu Impish Indri (development branch) Release:21.10 Impish Indri 20210911 build, erase disk and install, packages updated after installation Installation failed at step 15: bug #1925314 "no eject media message after install". System restarted successfully. Changed downloading updates to main server and was prompted to update a few packages. After updates finished, pressed "Restart now". This is the result. Updated packages: Start-Date: 2021-09-11 15:56:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.83' Upgrade: libedata-book-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), libebook-1.2-20:amd64 (3.40.2-1build1, 3.40.4-1), libgomp1:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libecal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), libedataserver-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), evolution-data-server:amd64 (3.40.2-1build1, 3.40.4-1), libgcr-base-3-1:amd64 (3.38.1-2, 3.40.0-3), evolution-data-server-common:amd64 (3.40.2-1build1, 3.40.4-1), open-vm-tools-desktop:amd64 (2:11.2.5-2ubuntu1, 2:11.3.0-2), gcr:amd64 (3.38.1-2, 3.40.0-3), libgcr-ui-3-1:amd64 (3.38.1-2, 3.40.0-3), libcamel-1.2-62:amd64 (3.40.2-1build1, 3.40.4-1), libxmlsec1:amd64 (1.2.31-1, 1.2.32-1), libebook-contacts-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), libedataserverui-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), open-vm-tools:amd64 (2:11.2.5-2ubuntu1, 2:11.3.0-2), libgupnp-av-1.0-2:amd64 (0.12.11-2, 0.12.11-3), cpp-11:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), printer-driver-pnm2ppa:amd64 (1.13+nondbs-0ubuntu7, 1.13+nondbs-0ubuntu8), libedata-cal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), gcc-11-base:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), groff-base:amd64 (1.22.4-6, 1.22.4-7), libgck-1-0:amd64 (3.38.1-2, 3.40.0-3), gir1.2-gck-1:amd64 (3.38.1-2, 3.40.0-3), libstdc++6:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libebackend-1.2-10:amd64 (3.40.2-1build1, 3.40.4-1), libxmlsec1-openssl:amd64 (1.2.31-1, 1.2.32-1), gir1.2-gcr-3:amd64 (3.38.1-2, 3.40.0-3), libgcc-s1:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1) End-Date: 2021-09-11 15:57:17 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 11 16:07:46 2021 InstallationDate: Installed on 2021-09-11 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=54dc5a9f-dd8b-435f-a346-0647390276de ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1943318 Title: systemd-shutdown[1]: Failed to finalize file systems, ignoring. Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Impish Indri (development branch) Release: 21.10 Impish Indri 20210911 build, erase disk and install, packages updated after installation Installation failed at step 15: bug #1925314 "no eject media message after install". System restarted successfully. Changed downloading updates to main server and was prompted to update a few packages. After updates finished, pressed "Restart now". This is the result. Updated packages: Start-Date: 2021-09-11 15:56:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.83' Upgrade: libedata-book-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), libebook-1.2-20:amd64 (3.40.2-1build1, 3.40.4-1), libgomp1:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libecal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), libedataserver-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), evolution-data-server:amd64 (3.40.2-1build1, 3.40.4-1), libgcr-base-3-1:amd64 (3.38.1-2, 3.40.0-3),
[Touch-packages] [Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()
I believe this bug needs to be mentioned here: https://discourse.ubuntu.com/t/impish-indri-release-notes/21951 in the "Ubuntu Desktop" category. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() Status in gnome-shell package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed 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 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 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/1942031/+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 1890281] [NEW] Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit
Public bug reported: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit by the height of the Top Bar and the desktop background to show up. Controlling the audio volume or screen brightness, or using keyboard shortcuts should not bring up the GNOME desktop and misplace the window in fullscreen games. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 17:33:35 2020 DistUpgraded: 2020-07-24 11:33:50,776 DEBUG running apport_crash() DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:220d] InstallationDate: Installed on 2016-11-03 (1369 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=fff07cd8-771d-418e-a056-c094fe8e3a55 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2020-07-24 (11 days ago) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 24 10:49:18 2020 xserver.configfile: default xserver.errors: Failed to load module "vesa" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 831 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- 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/1890281 Title: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit Status in xorg package in Ubuntu: New Bug description: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit by the height of the Top Bar and the desktop background to show up. Controlling the audio volume or screen brightness, or using keyboard shortcuts should not bring up the GNOME desktop and misplace the window in fullscreen games. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 17:33:35 2020 DistUpgraded: 2020-07-24 11:33:50,776 DEBUG running apport_crash() DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics
