[Touch-packages] [Bug 1098876] Re: ddclient do not ask for all necessary informations on initial configuration
Closing stale bug report as invalid. ddclient 3.9.1-7 (not yet released) will have many debconf improvements. Please wait for that version to be released. If the debconf questions in that version are still insufficient, please reopen. ** Changed in: debconf (Ubuntu) Status: New => Invalid ** Changed in: ddclient (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1098876 Title: ddclient do not ask for all necessary informations on initial configuration Status in ddclient package in Ubuntu: Invalid Status in debconf package in Ubuntu: Invalid Bug description: ddclient is after installing asking the user for some infromations about the dyndns service. After giving asnwers to all this questions the ddclient configuration file is in this state: " # Configuration file for ddclient generated by debconf # # /etc/ddclient.conf protocol=dyndns2 use=if, if=wlan0 server=www.dnsdynamic.org login=melchiaros password='' virtual-tutorial.dnsdynamic.com " Following http://www.dnsdynamic.org/api.php it there should be some more information asked for good user feeling. Please see this as wish. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ddclient 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Sat Jan 12 14:33:01 2013 InstallationDate: Installed on 2013-01-01 (10 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130101) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ddclient UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.8-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-01-01 (10 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130101) MarkForUpload: True Package: debconf PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Tags: raring running-unity Uname: Linux 3.8.0-0-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddclient/+bug/1098876/+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 1371250] Re: LightDM fails to switch to greeter on logout if allow-user-switching=false
** Tags added: multiseat -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1371250 Title: LightDM fails to switch to greeter on logout if allow-user- switching=false Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in Light Display Manager 1.12 series: Won't Fix Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Won't Fix Bug description: In my multiseat system, if I logout on a non-seat0 seat (which has allow-user-switching=false by default), lightdm fails to start a greeter on that seat: DEBUG: Seat: Display server stopped DEBUG: Seat: Active display server stopped, starting greeter DEBUG: Seat: Stopping; failed to start a greeter DEBUG: Seat: Stopping DEBUG: Seat: Stopped I guess the problem is related to seat_switch_to_greeter() calls in session_stopped or display_server_stopped callbacks in seat.c. Switch to greeter should be always allowed on logout. NOTE: This was observed in LightDM 1.10.2 on Ubuntu 14.04, but I guess it also happens on trunk series. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371250/+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 1685754] Re: gnome-terminal unduly forces umask=0022
** Tags removed: focal
** Summary changed:
- gnome-terminal unduly forces umask=0022
+ 'systemd --user' unduly forces umask=0022
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed => Invalid
** Changed in: dbus (Ubuntu)
Status: Confirmed => Invalid
** Changed in: gnome-session
Status: New => Invalid
** Changed in: nautilus
Status: Confirmed => Invalid
--
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/1685754
Title:
'systemd --user' unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
Invalid
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Invalid
Status in dbus package in Ubuntu:
Invalid
Status in gnome-terminal package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1685754] Re: 'systemd --user' unduly forces umask=0022
** Also affects: systemd via
https://github.com/systemd/systemd/issues/6077
Importance: Unknown
Status: Unknown
--
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/1685754
Title:
'systemd --user' unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
Invalid
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Invalid
Status in systemd:
Unknown
Status in dbus package in Ubuntu:
Invalid
Status in gnome-terminal package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1521043] [NEW] less 458 crashes if search regex has many groups
Public bug reported:
less 458 crashes if there are enough capture groups in the regular
expression used for search:
newline=$(printf \\nx); newline=${newline%x}
echo x | LESS="+g/(x)${newline}" less
On amd64, the above produces a segfault:
Segmentation fault (core dumped)
On i386, the above triggers an assert:
*** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
Aborted
** Affects: less (Ubuntu)
Importance: Undecided
Status: New
** Affects: less (Debian)
Importance: Unknown
Status: Unknown
** Tags: trusty wily
** Bug watch added: Debian Bug tracker #707824
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707824
** Also affects: less (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707824
Importance: Unknown
Status: Unknown
** Summary changed:
- less crashes if regex has many groups
+ less crashes if search regex has many groups
** Description changed:
- less crashes if there are enough capture groups in the regular
+ less 458 crashes if there are enough capture groups in the regular
expression used for search:
- newline=$(printf \\nx)
- newline=${newline%x}
- echo x | LESS="+g/(x)${newline}" less
+ newline=$(printf \\nx)
+ newline=${newline%x}
+ echo x | LESS="+g/(x)${newline}" less
On amd64, the above produces a segfault:
- Segmentation fault (core dumped)
+ Segmentation fault (core dumped)
On i386, the above triggers an assert:
- *** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
- Aborted
+ *** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
+ Aborted
** Summary changed:
- less crashes if search regex has many groups
+ less 458 crashes if search regex has many groups
** Tags added: trusty wily
** Description changed:
less 458 crashes if there are enough capture groups in the regular
expression used for search:
- newline=$(printf \\nx)
- newline=${newline%x}
+ newline=$(printf \\nx); newline=${newline%x}
echo x | LESS="+g/(x)${newline}" less
On amd64, the above produces a segfault:
Segmentation fault (core dumped)
On i386, the above triggers an assert:
*** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
Aborted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to less in Ubuntu.
https://bugs.launchpad.net/bugs/1521043
Title:
less 458 crashes if search regex has many groups
Status in less package in Ubuntu:
New
Status in less package in Debian:
Unknown
Bug description:
less 458 crashes if there are enough capture groups in the regular
expression used for search:
newline=$(printf \\nx); newline=${newline%x}
echo x | LESS="+g/(x)${newline}" less
On amd64, the above produces a segfault:
Segmentation fault (core dumped)
On i386, the above triggers an assert:
*** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
Aborted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1521043/+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 1521043] Re: less 458 crashes if search regex has many groups
This is an upstream less bug that was fixed in version 481. Attached is
a debdiff that cherry-picks the fix for this bug.
I have uploaded a fixed version of less to my PPA (for trusty (14.04) and wily
(15.10)). See:
https://launchpad.net/~a7x/+archive/ubuntu/bug1521043
** Patch added: "debdiff"
https://bugs.launchpad.net/debian/+source/less/+bug/1521043/+attachment/4527386/+files/debdiff.patch
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to less in Ubuntu.
https://bugs.launchpad.net/bugs/1521043
Title:
less 458 crashes if search regex has many groups
Status in less package in Ubuntu:
New
Status in less package in Debian:
Incomplete
Bug description:
less 458 crashes if there are enough capture groups in the regular
expression used for search:
newline=$(printf \\nx); newline=${newline%x}
echo x | LESS="+g/(x)${newline}" less
On amd64, the above produces a segfault:
Segmentation fault (core dumped)
On i386, the above triggers an assert:
*** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
Aborted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1521043/+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 1521043] Re: less 458 crashes if search regex has many groups
I renamed my account, so the PPA with the fixed version is now at:
https://launchpad.net/~rhansen/+archive/ubuntu/bug1521043
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to less in Ubuntu.
https://bugs.launchpad.net/bugs/1521043
Title:
less 458 crashes if search regex has many groups
Status in less package in Ubuntu:
Triaged
Status in less package in Debian:
Incomplete
Bug description:
less 458 crashes if there are enough capture groups in the regular
expression used for search:
newline=$(printf \\nx); newline=${newline%x}
echo x | LESS="+g/(x)${newline}" less
On amd64, the above produces a segfault:
Segmentation fault (core dumped)
On i386, the above triggers an assert:
*** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
Aborted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1521043/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools Assignee: Joe (jrhodgeneo74) => (unassigned) ** No longer affects: initramfs-tools ** Also affects: initramfs-tools Importance: Undecided Status: New ** Changed in: initramfs-tools Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
undo recent bug vandalism ** Package changed: ubuntu => initramfs-tools ** Project changed: initramfs-tools => null-and-void ** Also affects: initramfs-tools Importance: Undecided Status: New ** Changed in: initramfs-tools Status: New => Confirmed ** Changed in: initramfs-tools (Ubuntu) Assignee: Javier Arias (jareche1) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: Confirmed Status in NULL Project: Fix Released Status in initramfs-tools package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: Confirmed Status in NULL Project: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 507728] Re: man page missing for slapo-nssov
Still a problem in trusty. ** Tags removed: patch ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/507728 Title: man page missing for slapo-nssov Status in openldap package in Ubuntu: Confirmed Bug description: source package: openldap (2.4.18-0ubuntu1) >lsb_release -rd Description: Ubuntu 9.10 Release: 9.10 >apt-cache policy slapd slapd: Installed: 2.4.18-0ubuntu1 Candidate: 2.4.18-0ubuntu1 Version table: *** 2.4.18-0ubuntu1 0 500 http://us.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status the man page for the nss overlay (e.g. slapo-nssov) is not present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/507728/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools (Ubuntu) Assignee: Kishor Kansara (kansarakishor) => (unassigned) ** Changed in: initramfs-tools Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1167281] Re: "stdin: is not a tty" due to "mesg n" instead of "tty -s && mesg n" in .profile
** Also affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags added: xenial -- 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/1167281 Title: "stdin: is not a tty" due to "mesg n" instead of "tty -s && mesg n" in .profile Status in base-files package in Ubuntu: New Status in xen-3.1 package in Ubuntu: Invalid Bug description: Upstreaming from https://bugzilla.wikimedia.org/show_bug.cgi?id=46913 : This used to happen at the start of every Puppet run, because of the line "mesg n" in /root/.profile. The shell provisioner is actually invoked to fix the problem by changing it to "tty -s && mesg n". This fixes the problem for every subsequent run. Still, I'd like to prevent it from appearing even once. Ubuntu could fix this by adding a check to .profile. Also see https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/201884 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1167281/+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 1522675] Re: /root/.synaptic/ not created
** Bug watch added: Debian Bug tracker #808802 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808802 ** Also affects: synaptic (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808802 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: /root/.synaptic/ not created Status in apt package in Ubuntu: Invalid Status in synaptic package in Ubuntu: Triaged Status in synaptic package in Debian: Unknown Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools Assignee: vanvan (bartel-vanessa) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: Fix Released Status in initramfs-tools package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 405116] Re: "hpcups" driver of HPLIP has broken margins
> Can someone please reopen this bug! If you are still experiencing a problem similar to the one described in this bug report, please file a new bug report with complete details. It is believed that this bug is fixed, so this particular bug will not be revisited again. If you are experiencing a problem with similar symptoms then it's likely the underlying cause to your problem is different from the underlying cause identified in this bug report, or there has been a regression. Either way, a new bug report is required before Ubuntu developers will take a look. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/405116 Title: "hpcups" driver of HPLIP has broken margins Status in HP Linux Imaging and Printing: Fix Released Status in cups package in Ubuntu: Fix Released Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip Hi. I have an HP DeskJet D2600 connected via USB. When I turned the printer on, a default configuration named Deskjet-D2600-series (using the "HP Deskjet d2600 Series [en]" driver) was generated that I can see in the gnome printer configuration window. When I print a test page the contents has a big margin at the top and the bottom is cut off. In the printer configuration if I change the driver to "HP Deksjet d2600 Series hpijs [en]" or "HP Deksjet d2600 Series hpijs 3.9.6b.4 [en]" the margin problem is corrected, but now black contents is printed in what looks like a combination of colors that appears black but looks more like dark brown. What I'm hoping for is that the margins for the default driver are corrected. I can provide any information that might be needed. Thanks. ProblemType: Bug Architecture: amd64 Date: Sun Jul 26 23:03:14 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Deskjet-D2600-series: hp:/usb/Deskjet_D2600_series?serial=TH94M140BG05C9 Package: hpijs-ppds 3.9.6b-1ubuntu4 PackageArchitecture: all Papersize: letter PpdFiles: Deskjet-D2600-series: HP Deskjet d2600 Series, hpcups 3.9.6b ProcCmdLine: root=UUID=06e1c48d-56bd-443b-8324-1975f908d414 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-4.22-generic SourcePackage: hplip Uname: Linux 2.6.31-4-generic x86_64 dmi.bios.date: 05/17/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AV8 (VIA K8T800P-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/17/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAV8(VIAK8T800P-8237):rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/405116/+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 1190581] Re: Support logind's automatic multiseat feature
The trusty-proposed package works for me; no observed regressions. ** Tags removed: verification-needed ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1190581 Title: Support logind's automatic multiseat feature Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Utopic: Fix Released Status in lightdm package in Fedora: Unknown Bug description: [Impact] LightDM does not use the information provided by logind to support automatic multi-seat setups. We have backported this support from LightDM 1.12 so this functionality can be used in 14.04 LTS. It is disabled by default. [Test Case] 1. Enable multiseat in the LightDM configuration: [LightDM] logind-load-seats=true 2. Start LightDM Expected result: The greeter is shown on both monitors and two sessions can be logged in. Observed result: Currently only one monitor / seat works. [Regression Potential] There is some risk of unrelated code being changed. This has been reduced by the use of regression tests, manual testing and providing this in the Ubuntu Desktop PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190581/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
User kamalwanas recently vandalized this bug by changing the status from confirmed to fix released, but I can't seem to change it back. I was able to revert the vandalism by abnercontreras11 (change the package back to initramfs-tools). ** Package changed: cloud-initramfs-tools (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools Assignee: Kamal Wanas (kamalwanas) => (unassigned) ** Changed in: initramfs-tools Status: Fix Committed => Confirmed ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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
