I agree. At least an ETA would be nice instead of vague "releases are
coming" for such a critical bug.
It has been long two working days waiting for a fix and still no idea
when to expect it to be working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
a later time...
Janne Snabb
sn...@epipe.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768230
Title:
Long time booting : Failed to connect to lvmetad. Falling back to
device scanning.
To manage n
I agree. It appears that version 0.130ubuntu3.3 is broken again.
When looking at the changelog here:
http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs-tools
/initramfs-tools_0.130ubuntu3.3/changelog
...and comparing it to the changelog at:
$ apt-file search kbd_mode
kbd: /bin/kbd_mode
kbd: /usr/share/man/man1/kbd_mode.1.gz
[..]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508146
Title:
Alt+left/right arrows switch between tty
After disappearing for a while, the problem re-appeared.
Luckily the bug is now fixed in Debian. The fix will eventually land in
a future Ubuntu version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have this issue at every boot in my Ubuntu Virtualbox VM. It started
happening after updating it from Ubuntu 17.10 to Ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768230
Title:
It appears that the crash does not happen any more even though the
wvdial package version remains the same as before. Possibly some
condition has changed, not sure what (library versions is one
possibility).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I may have experienced this issue also on bionic (18.04) with the
current kernel version as of today (4.15.0-13.14).
I upgraded one affected system with "do-release-upgrade -d". After
completing the upgrade and rebooting, the system froze the same way as
with the affected 17.10 kernel and
I tested the new kernel in artful-proposed on a system which failed with
the newest kernel + intel-microcode in normal artful repository.
Thus I confirm that the kernel in artful-proposed fixes this issue for
me.
$ apt policy linux-image-4.13.0-39-generic
linux-image-4.13.0-39-generic:
Public bug reported:
Since upgrading Ubuntu from 17.10 to 18.04 wvdial is crashing with the
following error message when connection is established:
# wvdial 3gconnect
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0
Also affects Ubuntu 18.04 bionic (beta2 right now).
$ apt policy gnome-settings-daemon
gnome-settings-daemon:
Installed: 3.28.0-0ubuntu2
Candidate: 3.28.0-0ubuntu2
Version table:
*** 3.28.0-0ubuntu2 500
500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100
Temporary workaround:
1) sudo mv /usr/lib/gnome-settings-daemon/gsd-housekeeping
/usr/lib/gnome-settings-daemon/gsd-housekeeping.off
2) logout and login
This needs to be redone when "gnome-settings-daemon" package is updated.
I do not know if it is doing something useful for some people.
The same hardware and same default choices results with successfull
installation (using grub-install /dev/sda) when using ubuntu-
gnome-16.04.3-desktop-amd64.iso. So the bug has appeared after that
version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This happened with ubuntu-gnome-16.04.3-desktop-amd64.iso when trying to
install on a system which had a pre-existing Ubuntu installation on hard
disk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Another report of the same bug:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1708880
(That one is also incorrectly marked Invalid.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I encountered this issue also. I downloaded ubuntu-17.10.1-desktop-
amd64.iso and created USB disk and tried to install Ubuntu using it. I
did not specify anything, just pressing and selecting whatever
is offered by default. It should not end like this.
** Changed in: ubiquity (Ubuntu)
Public bug reported:
Apparently a process called gsd-housekeeping is periodically invoked on
my Ubuntu 17.10 system. It traverses my /var/tmp for some reason. Looks
like it is leaking file descriptors while doing so.
My syslogs are full of error messages like the following:
Jan 26 20:21:42
In my case I was able to workaround this issue by changing the lock
shortcut from super-L to ctrl-alt-L. All shortcuts using super are
broken. My "window action key" in gnome-tweaks is "super". So it appears
that it is impossible to use the window action key for shortcuts any
more after some very
I am using gdm3 (AFAIK) and super-L also stopped working just now when I
did "apt dist-upgrade". So in my case it does not seem to depend on
lightdm vs gdm3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Forgot to include affected gnome-shell-extensions package version:
$ apt policy gnome-shell-extensions
gnome-shell-extensions:
Installed: 3.26.0-1
Candidate: 3.26.0-1
Version table:
*** 3.26.0-1 500
500 http://se.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
500
This bug appears only with "GNOME Classic" session.
How to repeat:
1. Install Ubuntu 17.10
2. apt install gnome-shell-extensions
3. reboot
4. login choosing "GNOME Classic" session
5. open terminal
6. do "notify-send foobar"
7. unreadable notification box appears
Thus, I was able to get rid of
Public bug reported:
After upgrading my Ubuntu GNOME 17.04 system to Ubuntu 17.10 the
notification message window colour is unreadable.
It is black text on very dark grey background. See attached screenshot.
To make sure that it does not come from my settings, I created a new
user account with
I have this problem on Ubuntu Gnome 17.04 running in virtualbox. I
believe it is not using Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and
Happens every time after login on fresh install of Ubuntu GNOME 17.04.
Happened also with few previous releases of Ubuntu.
Reproducible: always on every Ubuntu installation
Not dependent on hardware as it happens on virtual box VMs as well as on
physical machines.
This gives a very bad
Thanks!
I verified that the bug is fixed in these versions:
ii percona-xtrabackup 2.3.7-0ubuntu0.16.10.2 amd64Open source backup
tool for InnoDB and XtraDB
ii percona-xtrabackup 2.3.7-0ubuntu0.16.04.2 amd64Open source backup
tool for InnoDB and XtraDB
** Tags removed:
Public bug reported:
percona-xtrabackup was upgraded from 2.2.3-2.1build1.1 to
2.3.7-0ubuntu0.16.04.1.
It appears that MySQL default socket file path has changed in the new
version.
After the update my backups started failing with the following:
170402 06:30:04 Connecting to MySQL server host:
I have found several other mentions of this issue:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1612882
https://irclogs.ubuntu.com/2016/04/26/%23snappy.html
https://irclogs.ubuntu.com/2016/08/30/%23snappy.html
Clearly some other people are affected too, not just the two of us. :)
In
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617765
Title:
Connections reset when downloading snaps from CDN
To manage
Before applying this patch, please note that it has a regression in
ProxyPass connectiontimeout parameter handling, see
https://bugzilla.redhat.com/show_bug.cgi?id=1242416
** Bug watch added: Red Hat Bugzilla #1242416
https://bugzilla.redhat.com/show_bug.cgi?id=1242416
--
You received this
Before applying this patch, please note that it has a regression in
ProxyPass connectiontimeout parameter handling, see
https://bugzilla.redhat.com/show_bug.cgi?id=1242416
** Bug watch added: Red Hat Bugzilla #1242416
https://bugzilla.redhat.com/show_bug.cgi?id=1242416
--
You received this
I am affected by this issue on Ubuntu 15.04 x86_64. I have AMI
BIOS/UEFI. Ctrl-X does not work (but F10 works). In my case 'x' is
inserted as if I did not press Ctrl key.
I found a discussion and a potential patch at:
https://lists.gnu.org/archive/html/grub-devel/2013-08/msg3.html
Possibly
I encountered this issue on a Hetzner VPS. It is a KVM based virtual
server, not VMware. After rebooting I was unable to login through ssh.
Accessing the system from console was possible thugh running many
commands resulted in Killed. The kernel stack trace was the same as in
the original bug
Same issue herre on Xubuntu 14.04.1 x86_64.
I have 103 instances of the process. The processes are owned by
lightdm user except for one which is owned by my userid snabb (see
the process list at the end).
There are also 103 instances of process init --user --startup-event
One more thing:
I was able to get rid of the processes by executing the following
command:
$ sudo kill `ps axuwww | fgrep indicator-services-start | awk '{ print
$2 }'`
However, as a result I lost the sound control thingy from the panel. I
should have probably excluded the indicator process
On 2013-01-08 23:21, Hadrien Titeux wrote:
Apparently this problem only appears after an upgrade.It seems I never
got this kind of problem with fresh installs, and people here appear to
be in the same situation...
I have a fresh install of Ubuntu 12.10 and I have this problem.
--
You
Please increase the importance of this bug!
It is really embarrassing to go to a customer meeting, open my laptop
and notice that I can not connect to a network because network-manager
does not respond. I have to start by apologizing that I need to reboot
my computer. It is a major PITA.
While I
This bug appears to be a possible duplicate of bug #930563 which is
certainly not fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933791
Title:
Stops responding to mouse clicks and won't open
This appears to be duplicate of bug #930563 (or vice versa?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/845660
Title:
Network manager not responding to button presses
To manage notifications
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085812
Title:
modem-manager crashed with SIGSEGV in get_cind_signal_done()
To manage notifications
Here is a syslog snippet from the time when the crash happened.
Looks like the crash is triggered when the connection is terminated for
some reason:
Dec 3 06:31:15 foil pppd[19273]: LCP terminated by peer
Dec 3 06:31:15 foil pppd[19273]: Connect time 444.3 minutes.
Dec 3 06:31:15 foil
Some additional details:
- This bug is triggered only if num-threads setting in unbound.conf is
higher than 1. Therefore a simple workaround is to reduce the amount of
threads to 1 (which is the default).
- A description of the problem and a patch is available at
** Bug watch added: Debian Bug tracker #691528
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691528
** Also affects: unbound (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691528
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
$ gdb /usr/sbin/unbound core.28338
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and
Public bug reported:
ntpd crashes with SIGSEGV when (teredo IPv6) interface goes down after
unplugging a network cable:
Oct 22 03:17:03 oil ntpdate[5896]: adjust time server 118.143.17.82 offset
0.005534 sec
Oct 22 03:17:03 oil ntpd[5951]: ntpd 4.2.6p3@1.2290-o Mon Aug 20 15:15:21 UTC
2012 (1)
Public bug reported:
ntpd crashes with SIGSEGV when (teredo IPv6) interface goes down after
unplugging a network cable:
Oct 22 03:17:03 oil ntpdate[5896]: adjust time server 118.143.17.82 offset
0.005534 sec
Oct 22 03:17:03 oil ntpd[5951]: ntpd 4.2.6p3@1.2290-o Mon Aug 20 15:15:21 UTC
2012 (1)
I encountered this error also when trying to update Xubuntu 12.04 to
12.10 with do-release-upgrade.
I got the following output:
Preparing to replace php5-suhosin 0.9.33-1 (using
.../php5-suhosin_0.9.33-3build1_amd64.deb) ...
mv: cannot move `/etc/php5/conf.d/suhosin.ini' to
Additionally I have the following messages in /var/log/dist-
upgrade/main.log:
2012-10-19 18:07:56,014 ERROR got an error from dpkg for pkg:
'/var/cache/apt/archives/php5-suhosin_0.9.33-3build1_amd64.deb': 'subprocess
new pre-installation script returned error exit status 1'
2012-10-19
** Changed in: apparmor (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage
** Changed in: apparmor (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about
There is an easy workaround. I am adding it here for the benefit of
others who are bothered by this:
# dpkg-reconfigure popularity-contest
And select No.
(There is no point in submitting this data when nobody bothered to
update this package for precise. Feels like nobody appreciates users
I encountered this issue today the first time when adding a torrent to
transmission's download queue. According to apport it is the same bug.
I have the following libc6 package version, my system is fully up to
date:
2.15-0ubuntu10
--
You received this bug notification because you are a member
Hi,
I installed 1.0.3+dfsg-1ubuntu0.1 from precise-proposed and looks like
it is working fine.
My PSGI app was loaded successfully:
Tue Jul 17 08:12:13 2012 - PSGI app 0 (/www/test/TestApp/bin/app.pl)
loaded at 0x176d038
And nginx can successfully request a page from it:
[pid: 28119|app:
I forgot to add a successfull test case result which matches the
original simple test case.
The test case in the bug description can be now verified by observing
the following in /var/log/uwsgi/app/test.log:
Tue Jul 17 22:06:05 2012 - PSGI app 0 (/dev/null) loaded at 0x105ed18
Tue Jul 17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024528
Title:
psgi_plugin.so: undefined symbol: boot_DynaLoader
To manage notifications about this bug go to:
Public bug reported:
It appears that uwsgi-plugin-psgi does not load libperl.so and therefore
the package is unusable.
How to test:
1. # apt-get install uwsgi uwsgi-plugin-psgi
2. # vi /etc/uwsgi/apps-available/test.yaml
Put the following contents there:
---cut-here---
uwsgi:
plugins: psgi
apport information
** Tags added: apport-collected
** Description changed:
Syslog output:
Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking
failed for file /home/foobar/Maildir/dovecot.index.log: No such file or
directory
Apr 29 10:59:06 host12 dovecot:
apport information
** Attachment added: ApparmorStatusOutput.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216656/+files/ApparmorStatusOutput.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216657/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216658/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
apport information
** Attachment added: PstreeP.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216659/+files/PstreeP.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
I am able to reproduce this on a fresh install some times but not
reliably. It would be great if someone who has some apparmor experience
could have a look at this.
Steps to re-produce:
1. Install Ubuntu 12.04 Server from amd64 ISO in a virtual machine and make
sure it is up to date:
# apt-get
On 07/08/2012 09:02 PM, Jamie Strandboge wrote:
Thanks for the extra information. Can you also attach the output of:
$ sudo aa-status
This is already there, in the attachment ApparmorStatusOutput.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
apport information
** Tags added: apport-collected
** Description changed:
Syslog output:
Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking
failed for file /home/foobar/Maildir/dovecot.index.log: No such file or
directory
Apr 29 10:59:06 host12 dovecot:
apport information
** Attachment added: ApparmorStatusOutput.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216656/+files/ApparmorStatusOutput.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216657/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216658/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
apport information
** Attachment added: PstreeP.txt
https://bugs.launchpad.net/bugs/997269/+attachment/3216659/+files/PstreeP.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
I am able to reproduce this on a fresh install some times but not
reliably. It would be great if someone who has some apparmor experience
could have a look at this.
Steps to re-produce:
1. Install Ubuntu 12.04 Server from amd64 ISO in a virtual machine and make
sure it is up to date:
# apt-get
On 07/08/2012 09:02 PM, Jamie Strandboge wrote:
Thanks for the extra information. Can you also attach the output of:
$ sudo aa-status
This is already there, in the attachment ApparmorStatusOutput.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As a workaround I run haveged in some of my virtual machines. It
hopefully seeds /dev/random with something truly random.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/865499
Title:
Please include
It appears that the limit has been already increased to 3072 bits in the
newest NSS release 3.13.4, see diff at:
How to test:
certtool --generate-privkey --outfile key.pem
certtool --generate-self-signed --load-privkey key.pem --outfile cert.pem
certtool --generate-dh-params --bits 2237 --outfile dh2237.pem
certtool --generate-dh-params --bits 2236 --outfile dh2236.pem
gnutls-serv --http --x509keyfile
Public bug reported:
NSS (Netscape Security Services) module provides encryption services to
many applications, such as Thunderbird, Firefox and Chromium. NSS has a
hard coded maximum limit of 2236 bits for ephemeral Diffie-Hellman (DHE)
keys. If the TLS server (such as a web server, SMTP server,
** Patch added: nss-dh-max-p-bits.patch
https://bugs.launchpad.net/bugs/1002434/+attachment/3156350/+files/nss-dh-max-p-bits.patch
** Bug watch added: Mozilla Bugzilla #636802
https://bugzilla.mozilla.org/show_bug.cgi?id=636802
** Also affects: thunderbird via
Here are the relevant error messages from different NSS consumers.
Thunderbird:
Sending of message failed.
The message could not be sent using SMTP server localhost for an unknown
reason. Please verify that your SMTP server settings are correct and try
again, or contact your network
How to test:
certtool --generate-privkey --outfile key.pem
certtool --generate-self-signed --load-privkey key.pem --outfile cert.pem
certtool --generate-dh-params --bits 2237 --outfile dh2237.pem
certtool --generate-dh-params --bits 2236 --outfile dh2236.pem
gnutls-serv --http --x509keyfile
Public bug reported:
Syslog output:
Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking
failed for file /home/foobar/Maildir/dovecot.index.log: No such file or
directory
Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about this bug go to:
This looks like it could be an apparmor bug instead of dovecot bug, it
just happens to manifest itself with dovecot. Adding apparmor in
affects.
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
Syslog output:
Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking
failed for file /home/foobar/Maildir/dovecot.index.log: No such file or
directory
Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about this bug go to:
This looks like it could be an apparmor bug instead of dovecot bug, it
just happens to manifest itself with dovecot. Adding apparmor in
affects.
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This bug still exists on Xubuntu 12.04 precise as released, version
information below:
$ apt-cache policy libvte9
libvte9:
Installed: 1:0.28.2-3ubuntu2
Candidate: 1:0.28.2-3ubuntu2
Version table:
*** 1:0.28.2-3ubuntu2 0
500 http://kh.archive.ubuntu.com/ubuntu/ precise/main amd64
How about updating libvte (1:0.28.2-4) now from Debian when there is
still time remaining before the various freezes start in release
schedule?
It would be nice to have a working terminal application in the next
Xubuntu release.
The debian maintainer fixed the broken packaging already more than
I got hit by this on natty. There seems to be a corresponding Red Hat
bug at: https://bugzilla.redhat.com/show_bug.cgi?id=676205
** Bug watch added: Red Hat Bugzilla #676205
https://bugzilla.redhat.com/show_bug.cgi?id=676205
** Also affects: libvirt via
I noticed that it also brought in Gnome libraries on Xubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/842478
Title:
virt-manager depends on gnome libraries
To manage notifications about this
I got hit by this on natty. There seems to be a corresponding Red Hat
bug at: https://bugzilla.redhat.com/show_bug.cgi?id=676205
** Bug watch added: Red Hat Bugzilla #676205
https://bugzilla.redhat.com/show_bug.cgi?id=676205
** Also affects: libvirt via
*** This bug is a duplicate of bug 834725 ***
https://bugs.launchpad.net/bugs/834725
** This bug has been marked a duplicate of bug 834725
Powertop fails to report number of wakeups/events
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 834725 ***
https://bugs.launchpad.net/bugs/834725
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873360
Title:
powertop statistics display zero
To manage
*** This bug is a duplicate of bug 834725 ***
https://bugs.launchpad.net/bugs/834725
Public bug reported:
I installed powertop to find out information about my laptop's power
consumption.
Unfortunately it does not display some of the essential statistics, they
remain at zero. For example
Some additional details about this bug:
I run strace -o trace.out -f xfce4-terminal and found the following:
6828 execve(/usr/lib/vte/gnome-pty-helper, [gnome-pty-helper], [/*
54 vars */]) = -1 ENOENT (No such file or directory)
On my system locate gnome-pty-helper tells me the following:
Looks like libvte9 package is internally using an incorrect path for
gnome-pty-helper. libvte-2.90-9 package of the same library is using the
correct path. gnome-terminal updates utmp successfully because it is
using the latter library.
libvte9 tries to run /usr/lib/vte/gnome-pty-helper but
** Bug watch added: Debian Bug tracker #645104
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645104
** Also affects: vte (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645104
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
See attached patch.
Description:
Move the gnome-pty-helper into the -common package and install
only a single copy of this set-gid binary in /usr/lib/libvte.
The downside of this approach is that the -common package becomes
architecture specific.
--
You received this bug notification because
Oops, wrong bug. Sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838820
Title:
the proxy authentication option is not easy to use
To manage notifications about this bug go to:
See attached patch.
Move the gnome-pty-helper into the -common package and install
only a single copy of this set-gid binary in /usr/lib/libvte.
The downside of this approach is that the -common package becomes
architecture specific.
I submitted this to the Debian bug also.
** Patch added:
Public bug reported:
This is more of a feature request than a bug.
Please include the virtio-rng hw_random module in the -virtual kernel
package along with the other virtio drivers.
Virtual machines often do not have much of hardware randomness
available. This can negatively affect performance
apport logs are not useful because this is a feature request. Changing
status.
** Changed in: linux (Ubuntu)
Status: Incomplete = Opinion
** Changed in: linux (Ubuntu)
Status: Opinion = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
When using xfce4-terminal (0.4.8-1) on freshly installed Xubuntu 11.10
beta2 x86_64 no utmp entries are being recorded.
On the same machine login, sshd, screen, xterm and gnome-terminal all
record utmp entries successfully.
This is an example output of w and who run on a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864609
Title:
xfce4-terminal fails to record utmp/login entries
To manage notifications about this bug go to:
1 - 100 of 113 matches
Mail list logo
