date:20171027

** Changed in: mutter
   Status: Unknown => Confirmed

** Changed in: mutter
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-10-27 Thread Adam Conrad

Hello PeterPall, or anyone else affected,

Accepted sane-backends into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/sane-
backends/1.0.27-1~experimental2ubuntu2.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed verification-failed-artful
** Tags added: verification-needed-artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707352

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724738] Re: gnome-control-center crashed with SIGSEGV

2017-10-27 Thread Muhammad Darwish

*** This bug is a duplicate of bug 1720400 ***
https://bugs.launchpad.net/bugs/1720400

Happened right after logging in to a google account

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724738

Title:
  gnome-control-center crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724738/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727666] Re: package pki-base 10.3.5+12-4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1, the wifi is not working, the mouse is not w

2017-10-27 Thread Timo Aaltonen

*** This bug is a duplicate of bug 1691655 ***
https://bugs.launchpad.net/bugs/1691655

** This bug has been marked a duplicate of bug 1691655
   pki-base postinst creates corrupt /etc/pki/pki.version

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727666

Title:
  package pki-base 10.3.5+12-4ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1, the wifi is not working, the mouse is not working properly
  and the computers is slower then before

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1727666/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727943] Re: package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2017-10-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727943

Title:
  package keyboard-configuration 1.108ubuntu15.3 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1727943/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716842] Re: dogtag-pki needs porting work for tomcat 8.5

2017-10-27 Thread Timo Aaltonen

** Summary changed:

- dogtag-pki needs porting work for tomcat8
+ dogtag-pki needs porting work for tomcat 8.5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716842

Title:
  dogtag-pki needs porting work for tomcat 8.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1716842/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1640001] Re: package libpam-modules 1.1.8-1ubuntu2.2 failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied

Thank you for reporting this issue and helping to improve Ubuntu.

  unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new':
Permission denied

This is not a bug in the Ubuntu PAM package, but instead points to
corruption on your filesystem or a problem with your hardware (since
dpkg runs as root and should never have permission denied when unpacking
packages).  Closing as invalid.

** Changed in: pam (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640001

Title:
  package libpam-modules 1.1.8-1ubuntu2.2 failed to install/upgrade:
  unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new':
  Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1640001/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1442859] Re: package libpam-systemd:amd64 219-7ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

*** This bug is a duplicate of bug 1607929 ***
https://bugs.launchpad.net/bugs/1607929

** This bug is no longer a duplicate of bug 1372193
   package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128 in 
pam-auth-update
** This bug has been marked a duplicate of bug 1607929
   update-manager: missing dependency on libgtk2-perl for debconf frontend

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442859

Title:
  package libpam-systemd:amd64 219-7ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1442859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1420547] Re: wrong contents for libpam0g-dbgsym:i386 in trusty

this is resolved (as well as it's going to) by the publication of the
1.1.8-1ubuntu2.2 security update to trusty-security.

** Changed in: pam (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420547

Title:
  wrong contents for libpam0g-dbgsym:i386 in trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1420547/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1406724] Re: package libpam-systemd:amd64 204-5ubuntu20.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

*** This bug is a duplicate of bug 1607929 ***
https://bugs.launchpad.net/bugs/1607929

** This bug is no longer a duplicate of bug 1372193
   package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128 in 
pam-auth-update
** This bug has been marked a duplicate of bug 1607929
   update-manager: missing dependency on libgtk2-perl for debconf frontend

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406724

Title:
  package libpam-systemd:amd64 204-5ubuntu20.9 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1406724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1372193] Re: package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 in pam-auth-update

*** This bug is a duplicate of bug 1607929 ***
https://bugs.launchpad.net/bugs/1607929

** This bug has been marked a duplicate of bug 1607929
   update-manager: missing dependency on libgtk2-perl for debconf frontend

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372193

Title:
  package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128 in pam-auth-update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1372193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1497625] Re: /etc/security/namespace.init always fails with default /bin/sh

*** This bug is a duplicate of bug 1081323 ***
https://bugs.launchpad.net/bugs/1081323

** This bug has been marked a duplicate of bug 1081323
   /bin/sh illegal option -p when using pam_namespace.so

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497625

Title:
  /etc/security/namespace.init always fails with default /bin/sh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1497625/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

2017-10-27 Thread Markus Schade

The ppa package works for my use case. Maybe add this test-case to QA.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727301

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1402283.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-12-07T07:42:06+00:00 mvetter wrote:

Created attachment 1228916
failed_wayland_gnome_shell_log.txt (journalctl)

Description of problem:

On a system with two graphics cards (Intel integrated graphics
controller and an AMD discrete card), gnome-shell crashes in wayland
mode (returns to the gdm login screen).

The machine is using the Intel integrated graphics for video output.
The AMD card has no monitors attached to it. It's only used for GPGPU computing 
via OpenCL.

When the AMD card is removed, gnome-shell works correctly in wayland
mode.


Version-Release number of selected component (if applicable):
3.22.2-2.fc25

How reproducible:
Always.

Steps to Reproduce:
1. install second graphics card
2. boot machine
3. gnome-shell fails in Wayland mode

Actual results:
gnome-shell does not work in Wayland mode when two graphics cards are present.

Expected results:
gnome-shell should work in Wayland mode, no matter how many video cards the 
system has.


Additional info:

kernel 4.8.11-300

extract from lspci:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland
GL [FirePro W2100]

journalctl log has:
Dec 07 16:32:49 localhost.localdomain gnome-shell[]: Can't initialize KMS 
backend: could not find drm kms device
Dec 07 16:32:49 localhost.localdomain gnome-session[2189]: 
gnome-session-binary[2189]: WARNING: App 'org.gnome.Shell.desktop' exited with 
code 1
Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
Dec 07 16:32:49 localhost.localdomain gdm-password][2164]: 
pam_unix(gdm-password:session): session closed for user tmp

I've attached two logs: one for booting into gdm, and one for attempting
to log in using gnome-shell.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/0


On 2016-12-07T07:43:50+00:00 mvetter wrote:

Created attachment 1228917
failed_gdm_log.txt (journalctl)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/1


On 2016-12-07T08:41:54+00:00 mvetter wrote:

Same problem happens when the AMD card is swapped out for an Nvidia
card.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/2


On 2016-12-12T17:34:01+00:00 sebby2k wrote:

I can confirm this also happens on my system.

Logging into Fedora 25 Gnome wayland session fails on Dell laptop with
Intel Haswell CPU and discrete Radeon HD 8790M graphics.

This used to work fine on F24 w/ 4.7.x kernel.

Hardware name: Dell Inc. Latitude E6540/0725FP

Version-Release number of selected component (if applicable):

Name: kernel-core
Arch: x86_64
Epoch   : 0
Version : 4.8.11
Release : 300.fc25

Name: gnome-shell
Arch: x86_64
Epoch   : 0
Version : 3.22.2
Release : 2.fc25

Name: mutter
Arch: i686
Epoch   : 0
Version : 3.22.2
Release : 3.fc25

I ended up disabling radeon kms mode setting by adding radeon.modeset=0
to grub. With this kernel configuration, I can now start Gnome Wayland
session successfully

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/3


On 2017-01-02T19:34:17+00:00 Carwyn wrote:

Same with these two cards on F25:

0:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 
Ti] (rev a2)

nouveau is the primary with the i915 unused.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/4


On 2017-01-02T22:12:21+00:00 Carwyn wrote:

Seems to be a similar problem to bug #1403512

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/comments/5


On 2017-05-04T08:09:10+00:00 Pavel wrote:

Same here, workaround with radeon.modeset=0 helped with the pro

[Bug 1722600] Re: virtual machines can't be renamed

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1500906.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-10-11T17:24:19+00:00 Volker wrote:

Description of problem:
In the virt-manager GUI, virtual machines can't be renamed, once they are 
created. There is no menu item for doing so. 

Version-Release number of selected component (if applicable):
1.3.2

How reproducible:
look through all the menus

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/1722600/comments/5


On 2017-10-18T14:44:08+00:00 Cole wrote:

Sorry this was confusing, but there is an option to rename. Shut off the
VM. Go to the VM Details window, Overview->Name, edit it, click apply

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/1722600/comments/7


** Changed in: virt-manager
   Status: Unknown => Invalid

** Changed in: virt-manager
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722600

Title:
  virtual machines can't be renamed

To manage notifications about this bug go to:
https://bugs.launchpad.net/virt-manager/+bug/1722600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727581] Re: Segmentation fault on map loading (17.10)

2017-10-27 Thread Dima

redeclipse-stable-x86_64.AppImage works fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727581

Title:
  Segmentation fault on map loading (17.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redeclipse/+bug/1727581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725836] Re: No more than 2 displays work simultaneously

2017-10-27 Thread Daniel van Vugt

This could be related to OpenGL texture sizes or something similar.
Unity7 (Compiz) has workarounds to avoid that limitation. And Xfce
avoids it by not using hardware accelerated compositing at all (last I
checked). It's not surprising if only Gnome Shell hits a problem like
this...

Do you get the same bug logging in to "Ubuntu" vs "Ubuntu on Xorg"?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726017] Re: dnsmasq prematurely returns REFUSED, breaking resolver

Thanks for the Check Martin.

I pushed merge proposals with my change so that one can double check for 
issues/mistakes.
Once they get approved this will enter the SRU [1] process.

If you could add an SRU Template [2] (to the head of the bug
description) in the time my MPs are in review that would be a great help
for me ( I can add regression risk if you are unsure, but especially
"how to reproduce" is often best by the reporter).

[1]: https://wiki.ubuntu.com/StableReleaseUpdates
[2]: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

** Changed in: dnsmasq (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: dnsmasq (Ubuntu Zesty)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726017

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1726017/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726017] Re: dnsmasq prematurely returns REFUSED, breaking resolver

2017-10-27 Thread Launchpad Bug Tracker

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/332888

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/332889

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726017

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1726017/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673649] Re: Xorg crashed with SIGABRT in OsAbort()

2017-10-27 Thread Alex Lohr

This usually happens for me when I login and the X session is started,
which sends me back to the login. I have made the observation that this
doesn't happen if a stable network connection is already present.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673649

Title:
  Xorg crashed with SIGABRT in OsAbort()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1673649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1281074] Re: updatedb.conf: CephFS should be included in PRUNEFS

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1223582.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-05-20T23:06:46+00:00 Ken wrote:

Description of problem:
Ceph is a software-defined storage project, and it stores its data in 
/var/lib/ceph as a big set of files. The problem is that updatedb indexes 
/var/lib/ceph along with everything else on the system. This /var/lib/ceph 
location is typically *very* large, and Ceph users are not supposed to go 
poking around at the files in there.

Version-Release number of selected component (if applicable):
mlocate-0.26-9.fc22

How reproducible:
always

Steps to Reproduce:
1. mount some large OSD disks under /var/lib/ceph
2. updatedb runs and indexes all of the OSDs' files

Actual results:
IO slows to a crawl

Expected results:
updatedb excludes Ceph data (add /var/lib/ceph to PRUNEPATHS)

Additional info:
Ceph also has a filesystem, so it would be nice to exclude the "ceph" and 
"fuse.ceph" filesystem types as well (via PRUNEFS).

For more background information, see a thread on the ceph-users mailing
list: http://lists.ceph.com/pipermail/ceph-users-
ceph.com/2014-February/037446.html

More discussion on ceph-devel: http://www.spinics.net/lists/ceph-
devel/msg18098.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/comments/4


On 2015-05-27T11:15:43+00:00 Fedora wrote:

mlocate-0.26-8.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/mlocate-0.26-8.fc21

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/comments/7


On 2015-05-28T11:58:04+00:00 Fedora wrote:

Package mlocate-0.26-8.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mlocate-0.26-8.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-8989/mlocate-0.26-8.fc21
then log in and leave karma (feedback).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/comments/8


On 2015-05-28T12:49:37+00:00 Fedora wrote:

mlocate-0.26-10.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/mlocate-0.26-10.fc22

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/comments/9


On 2015-05-28T14:39:03+00:00 Ken wrote:

Thanks for shipping this change!

Would you mind excluding the "ceph" and "fuse.ceph" filesystem types as
well, adding them to PRUNEFS?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/comments/10


On 2015-06-07T16:03:57+00:00 Fedora wrote:

mlocate-0.26-10.fc22 has been pushed to the Fedora 22 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/comments/11


On 2015-06-21T00:19:38+00:00 Fedora wrote:

mlocate-0.26-8.fc21 has been pushed to the Fedora 21 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/comments/12


** Changed in: mlocate (Fedora)
   Status: Unknown => Fix Released

** Changed in: mlocate (Fedora)
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281074

Title:
  updatedb.conf: CephFS should be included in PRUNEFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1308674] Re: [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked

Launchpad has imported 24 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1067071.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2014-02-19T15:51:05+00:00 Kamil wrote:

Created attachment 865143
journal snippet

Description of problem:
If this happens:
1. You power on the notebook inside the docking station.
2. You log in.
3. You dock out the notebook.

Then your brightness is set to minimum (the screen is nearly unreadable)
and the brightness control is broken - you can't adjust the brightness.

When you dock the notebook back in, the brightness is restored to the
normal level and you can control it.

If you start your notebook outside of the docking station, this bug is
not experienced at all (even if you dock in and dock out, everything
works).

This is a regression with kernel-3.13.2-200.fc20.x86_64 , if I boot 
kernel-3.12.9-301.fc20.x86_64 then everything works OK.

I have this confirmed on Thinkpad X220:
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

and also on Thinkpad T520. I guess both use Intel HD 3000?

I don't see anything useful in the logs. I attach journal snippet when I
undock the notebook. You can see brightness-related systemd printouts,
that's when I try to change the brightness (or some of that happens
automatically during docking out).

Version-Release number of selected component (if applicable):
kernel-3.13.2-200.fc20.x86_64

How reproducible:
100%

Steps to Reproduce:
1. power on the notebook inside the docking station
2. log in
3. dock out the notebook

Actual results:
your brightness is set to minimum (the screen is nearly unreadable) and the 
brightness control is broken - you can't adjust the brightness

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308674/comments/0

On 2014-02-19T17:24:26+00:00 Josh wrote:

Do you have an external monitor attached to the dock?  If so, how do you
have the screens configured when docked?

Which brightness controls are you using?  The hardware keys or the
software slider?

If you use the hardware keys, does the OSD show any changes after you
undock but those changes are not reflected in actual brightness
adjustment?

If you adjust the brightness in any manner, do the values of
brightness/actual_brightness in /sys/class/backlight/acpi_video0 and/or
/sys/class/backlight/intel_backlight change?  If so, which is changed on
3.12 and which is changed on 3.13?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308674/comments/1

On 2014-02-19T18:52:29+00:00 Josh wrote:

Could you also try the 3.14.0-0.rc3.git0.1.fc21.x86_64 build and see if
that fixes the controls for you?  I have similar hardware and can
recreate your issue, and I think 3.14-rc3 seems to work again but I'd
like you to confirm.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308674/comments/2

On 2014-02-20T08:49:51+00:00 Kamil wrote:

(In reply to Josh Boyer from comment #1)
> Do you have an external monitor attached to the dock?

Yes.

>  If so, how do you
> have the screens configured when docked?

$ xrandr
Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 8192 x 8192
LVDS1 connected 1366x768+0+128 (normal left inverted right x axis y axis) 277mm 
x 156mm
   1366x768   60.1*+
   1024x768   60.0  
   800x60060.3 56.2  
   640x48059.9  
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 connected primary 1920x1080+1366+0 (normal left inverted right x axis y 
axis) 510mm x 290mm
   1920x1080  60.0*+
   1680x1050  59.9  
   1280x1024  60.0  
   1280x960   60.0  
   1152x864   60.0  
   1024x768   60.0  
   800x60060.3  
   640x48060.0  
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)

> 
> Which brightness controls are you using?  The hardware keys or the software
> slider?

Neither of them work.

> 
> If you use the hardware keys, does the OSD show any changes after you undock
> but those changes are not reflected in actual brightness adjustment?

Exactly. OSD indicates changes, but the actual brightness is not
changed.

> 
> If you adjust the brightness in any manner, do the values of
> brightness/ac

[Bug 1424123] Re: Need to update for XFS crc=1 (non-default) on-disk format change

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1001279.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2013-08-26T20:13:26+00:00 Eric wrote:

>From the XFS list:

> Just a heads-up: GRUB currently doesn't work on a CRC enabled
> file-system. It will print the following error message:
> "not a correct XFS inode"

This format is still WIP upstream, but we should probably have the issue
on the RHEL7 radar since we plan to default to XFS even for /boot.

A simple workaround would be to not enable CRCs for the root fs; this
may be done by default in any case.

So this bug may be a WONTFIX or NOTABUG, but I figured we should at
least log the issue.

Thanks,
-Eric

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/0

On 2013-09-05T16:51:02+00:00 Ric wrote:

We probably do want this support in though - I can imagine we might not
always need a broken out /boot?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/1

On 2014-12-15T15:37:15+00:00 Peter wrote:

At the very least can we get a pointer here to some details about the FS
feature?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/2

On 2014-12-15T17:42:24+00:00 Eric wrote:

on-disk format stuff has recently been coalesced into
libxfs/xfs_format.h

http://oss.sgi.com/cgi-
bin/gitweb.cgi?p=xfs/xfs.git;a=blob;f=fs/xfs/libxfs/xfs_format.h

Other than that, we maybe need to do some buddy coding to do this, as I
don't think either grub2 or xfs has great up-to-date documentation...

For starters I assume grub2 could just grok new formats, but skip the
actual CRC verification... things haven't changed *that* much.

-Eric

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/3

On 2014-12-15T18:16:41+00:00 Zach wrote:

https://www.google.com/search?q=add+grub2+support+for+xfs+crc

https://www.mail-archive.com/debian-bugs-
d...@lists.debian.org/msg1288553.html

wget
http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/src/grub2-2.02~beta2-201.4.src.rpm

rpm2cpio grub2-2.02~beta2-201.4.src.rpm  | cpio -id

ls *xfs*

grub2-xfs-Add-helper-for-inode-size.patch
grub2-xfs-Convert-inode-numbers-to-cpu-endianity-immediate.patch
grub2-xfs-Fix-termination-loop-for-directory-iteration.patch
grub2-xfs-V5-filesystem-format-support.patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/4

On 2015-06-09T14:50:36+00:00 Peter wrote:

*** Bug 1220844 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/8

On 2015-09-13T11:27:24+00:00 Winfrid wrote:

I have tested grub2-2.02-0.23.fc23.x86_64 installed on an Fedora 21

I succeeded in booting a CentOS 7 with XFS from the fedora boot menu,
but I still cannot boot a SLED 12 with XFS from the fedora boot menu.

Using my openSUSE 13.2 I can boot CentOS 7 and SLED 12.

If you need more information, please advise me, how to create a log from
grub2.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/9

On 2015-11-19T12:23:23+00:00 errata-xmlrpc wrote:

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2401.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/comments/10

** Changed in: grub2 (Fedora)
   Status: Unknown => Fix Released

** Changed in: grub2 (Fedora)
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424123

Title:
  Need to update for XFS crc=1 (non-default) on-disk format change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1424123/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 704623] Re: Thunderbird renders system unusable / uses 100% CPU while indexing new messages

** Changed in: thunderbird (Fedora)
   Status: Unknown => Fix Released

** Changed in: thunderbird (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704623

Title:
  Thunderbird renders system unusable / uses 100% CPU while indexing new
  messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/704623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails

Launchpad has imported 18 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1201964.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-03-14T03:14:36+00:00 Adam wrote:

Created attachment 1001544
failure log

Since around March 6th, my Fedora 22 desktop system has frequently
failed to boot properly.

Unfortunately the last time I booted the system before that was February
23rd, so there's quite a big list of possible changes in there.

I have tried downgrading from systemd-219-8.fc22 to systemd-219-5.fc22
and from kernel-4.0.0-0.rc3.git1.2 to 3.20.0-0.rc0.git10.1.fc22; neither
seems to change anything, the bug still happens.

When the boot fails, various services don't attempt to start for some
time, and when they try and start, many fail. The system never manages
to start any consoles or gdm.

>From the debug console (tty9), running 'systemctl' appears to do nothing
for a long time, then shows an error like "Failed to register match for
disconnected message".

I will attach logs of both failed and successful boots with
systemd.log_level = debug.

The boot fails on average ~3 in 4 times.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/13


On 2015-03-14T03:15:00+00:00 Adam wrote:

Created attachment 1001545
success log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/14


On 2015-03-15T03:13:58+00:00 Zbigniew wrote:

In the upcoming systemd update there's a fix for socket path handling.
I'm not sure if this could be the same issue, but it'd be good if you
could test if it helps.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/15


On 2015-03-15T04:00:46+00:00 Fedora wrote:

systemd-219-9.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/systemd-219-9.fc22

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/16


On 2015-03-15T08:35:54+00:00 Adam wrote:

Nope, sorry, doesn't help :/ saw the bug on 2 of 3 test boots with
219-9.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/17


On 2015-03-16T01:41:00+00:00 Fedora wrote:

Package systemd-219-9.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-219-9.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3949/systemd-219-9.fc22
then log in and leave karma (feedback).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/18


On 2015-03-18T12:52:31+00:00 Lukáš wrote:

This is definitely a bug in 219. I have the same issue with my rhel build.
Unfortunately on my machine it occurs quite rarely so its hard to debug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/19


On 2015-03-20T18:00:02+00:00 Marek wrote:

I see similar problem, my case is described in bug 1204023.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/20


On 2015-03-25T19:33:02+00:00 Adam wrote:

Lukas: it occurs frequently for me, I'm happy to do any debugging anyone
requests, but I'd really like to see this fixed. It's kind of
unfortunate that my system neither starts up nor shuts down properly
most of the time! (I suffer from one or other of the bugs in the
disaster zone that is
https://bugzilla.redhat.com/show_bug.cgi?id=1088619 ).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/21


On 2015-03-26T17:07:36+00:00 Michal wrote:

Just guessing... This could be the same problem:
http://lists.freedesktop.org/archives/systemd-devel/2015-February/028640.html
Martin Pitt is reverting commit 13790add4bf648fed816361794d8277a75253410 in 
Ubuntu as a workaround.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1423811/comments/22


On 2015-03-26T

[Bug 539814] Re: tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels < 2.6.22

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=552320.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2010-01-04T17:10:01+00:00 Michal wrote:

Description of problem:
When I create tar archive with new tar (tar-1.22-10.fc12.x86_64) old tar is not 
able to open this archive. 

Version-Release number of selected component (if applicable):
tar-1.22-10.fc12.x86_64

How reproducible:
always

Steps to Reproduce:
1.create archive with new tar
2.try to extract it with old tar
3.

Actual results:
/bin/tar: squirrelmail-1.4.20-RC2/images/folder.png: Cannot utime: Bad file 
descriptor

I've got this error in koji when updating package:

http://koji.fedoraproject.org/koji/getfile?taskID=1901164&name=build.log

Expected results:
extracted archive

Additional info:
this breaks package updates where maintainer has to recreate tar archive. Also 
upstream tarballs where upstream uses Fedora system may produce broken tarballs 
which is even worse, so I consider this to be high severity.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/0

On 2010-01-04T17:24:39+00:00 Kamil wrote:

We figured out off-list the "old tar" from original report is
1.22-11.fc13, which is more likely a newer one :-)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/1

On 2010-01-04T20:53:45+00:00 Ondrej wrote:

As a sidenote - there were more such reports off-the-bugzlla - most
likely caused by recent change in the new glibc - anyway - as the glibc
maintainers are quite sure the problem is in tar, we should probably fix
it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/2

On 2010-01-05T14:32:52+00:00 Ondrej wrote:

> > That looks like a bug in tar, trying to call futimens with a bad file
> > descriptor.
> > Andreas Schwab
>  Probably, possibly exposed by this recent change in glibc-2.11.90-5:
> - Handle AT_FDCWD in futimens (BZ#10992).
> Tomas Bzatek

Adding relevant part of the off-the-bugzilla conversation.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/3

On 2010-01-05T15:25:18+00:00 Ondrej wrote:

Here is duplicate report in debian (they have same problems with eglibc
updated to POSIX2008) - patch fixing the issue is available there -
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563726 - However - I
tend to use latest gnulib lib/utimens.c - though - as they are other
utimens/utimensat call related fixes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/4

On 2010-01-05T19:29:13+00:00 Ondrej wrote:

Ah - even the latest gnulib doesn't handle this new recent change - so
touch from coreutils might be affected as well as mentioned in debian
bugzilla from comment #4. Therefore adding coreutils/gnulib upstream
maintainer into CC.

Jim, what do you think? Is the patch from http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=563726#66 good way to go and should be applied to
gnulib/coreutils-8.3 to prevent touch (or better said futimens() with
AT_FDCWD file descriptor) failures after glibc update?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/5

On 2010-01-05T21:27:01+00:00 Ondrej wrote:

Fixed in tar-1.22-12.fc13, closing RAWHIDE.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/6

On 2010-01-05T21:50:02+00:00 Jim wrote:

Hi Ondrej,

Thanks again for the heads up.
I've replied on bug-gnulib and Cc'd the debian bug address.
(too bad bugzilla doesn't have a reply-to-via-email option):

http://bugs.debian.org/563726#88

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/7

On 2010-01-05T23:54:41+00:00 Ondrej wrote:

Thanks Jim for replies/confirmation of bugfix correctness. Yep - it
would be good bugzilla improvement to have such thing.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/539814/comments/8

** Changed in: tar (Fedora)
   Status: Unknown => Fix Released

** Changed in: tar (Fedora)
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub

[Bug 385561] Re: broken fonts in firefox with kms enabled

Launchpad has imported 67 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=495323.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-04-11T22:05:18+00:00 Tomasz wrote:

Created attachment 339197
web browser with corrupted text

Description of problem:
Sometimes some letters became corrupted. It happens after running compiz, but 
even after stopping compiz and staring metacity (within one session) text stays 
corrupted.
I'm not using xorg.conf, so I have whatever configuration is default in F11 (so 
KMS, UXA, DRI2 I believe).

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.6.99.902-2.fc11.x86_64
mesa-libGL-7.5-0.8.fc11.x86_64
kernel-2.6.29.1-52.fc11.x86_64
compiz-0.7.8-18.fc11.x86_64
xorg-x11-server-Xorg-1.6.0-19.fc11.x86_64

How reproducible:
Always, corruption appear withing hour of running compiz. If compiz is started 
as part of session (by enabling Desktop Effects), corruption is visible in 
terminal at once.

Steps to Reproduce:
1. Start compiz
2. Do anything for some time.
3.
  
Actual results:
Some letters became garbled, see screenshot.

Expected results:
Ponies.


Additional info:
Hardware is Lenovo Thinkpad T400 with Centrino 2, 4GB RAM.
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/0


On 2009-04-11T22:06:10+00:00 Tomasz wrote:

Created attachment 339198
Xorg.0.log while text corrupted

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/1


On 2009-04-13T17:12:30+00:00 Edney wrote:

Seeing this here also. Running KDE 4.2 with compositing enabled, no
xorg.conf either and the texts get corrupted after a long period of use.
Anothere way to make it happen is to run wine, in my case i run it to
play Warcraft. When i get back, texts are messy. Any information, i can
get.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/2


On 2009-04-14T00:54:24+00:00 Edney wrote:

Created attachment 339402
Weird screen

Just in case it wasn't clear yet.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/3


On 2009-04-17T22:37:34+00:00 James wrote:

Seen here, too. Most often noticed in Firefox, but corruption of glyphs
shows up elsewhere.

xorg-x11-server-Xorg-1.6.1-6.fc11.x86_64
freetype-2.3.9-3.fc11.x86_64
freetype-2.3.9-3.fc11.i586
xorg-x11-drv-intel-2.6.99.902-3.fc11.x86_64

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/4


On 2009-04-22T16:10:41+00:00 Jesse wrote:

I'm seeing this as well with i965

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/5


On 2009-04-22T16:10:55+00:00 Jesse wrote:

Oh and yes, I'm using compiz.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/6


On 2009-04-24T16:27:59+00:00 Kevin wrote:

I am seeing this here as well with Xfce.

Some observations:

It seems that it's just some random font that gets corrupted glyphs
after some time, then any use of that font results in the corrupted
glyphs.

I have seen it in: midori, xchat, Terminal. It varies.

I have COMPOSITE enabled, but disabling it doesn't bring back the fonts
once they are corrupted.

My card is: 
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller (rev 03)

I don't see anything out of the ordinary in my /var/log/Xorg.0.log.

An example of corruption: 
http://www.scrye.com/~kevin/fedora/fonts-20090423.png

I'm happy to help with any additional debugging. This would be a very
good one to fix before release.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/385561/comments/7


On 2009-04-24T17:02:53+00:00 Wade wrote:

Getting the same thing,

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)

http://www.freeima

[Bug 390423] Re: system-config-lvm needs to support ext4

Launchpad has imported 28 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=432065.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-02-08T17:39:49+00:00 Eric wrote:

system-config-lvm needs some smarts for ext4.  I did xfs too while I was at it,
will attach a patch.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/0


On 2008-02-08T17:43:19+00:00 Eric wrote:

Created attachment 294387
initial patch

Here's a patch to implement ext4dev, xfs, and fix a "raiserfs" typo.

Note: ext4dev will at some point change to "ext4" so some changes will need to
be made at that point.

A test for the fully ext4-capable version of e2fsprogs would probably also be
good.

I felt a little bad with all the cut and paste; perhaps ext2/3/4 could use some
class inheritance?

If you'd like a simpler test for get_label, you could just call e2label rather
than parsing out tune2fs output.

Thanks,

-Eric

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/1


On 2008-03-29T03:56:27+00:00 Jim wrote:

This is very nice! Thanks kindly. I am in the middle of gitifying the s-c-lvm
repo, but will have all settled by early next week and will get this built.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/2


On 2008-04-23T20:29:54+00:00 Jon wrote:

Adding FutureFeature keyword to RFE's.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/3


On 2008-10-09T14:26:31+00:00 Deji wrote:

Can the patch in comment #1 be applied before F-10 release. And given
the latest update to the ext4 support, I believe all the reference to
ext4dev can now be changed to ext4.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/4


On 2008-10-09T14:56:54+00:00 Eric wrote:

Created attachment 319868
Updated patch

Here's an updated patch.  This has been open for almost a year, is there
a reason these changes can't be included?

Thanks,
-Eric

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/5


On 2009-02-04T19:39:15+00:00 Deji wrote:

Fedora 11 will default to ext4, it will great if this patch can be
applied now. Thanks.

PS: If its OK with the package owner, I can go ahead and apply the
patch, and build it in koji myself.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/6


On 2009-02-04T21:30:49+00:00 Jim wrote:

This patch is being included now. s-c-lvm is getting some much needed
love. :) There are also a few /etc/fstab issues that are getting ironed
out as well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/7


On 2009-03-22T22:16:26+00:00 Eric wrote:

I wonder if there is anything else I can do (besides providing a patch
over 1 year ago, and a subsequent updated patch...) to make this bug
move.  ext4 is the default fs for F11, and s-c-lvm still doesn't
recognize it.

Perhaps I could commit it to rawhide for you?

Thanks,
-Eric

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/8


On 2009-05-01T19:46:11+00:00 Mike wrote:

another vote for making this work in F11. Seems kind of bad that it
doesn't.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/9


On 2009-05-01T20:52:17+00:00 Eric wrote:

Jim, ping?

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/10


On 2009-06-05T17:43:26+00:00 Robert wrote:

I have Preview Release F11 installed and still does not work. I have
been allowing updates. Checked yum update system-config-lvm and none are
available.

Reply at: https://bugs.launchpad.net/ubuntu/+source/system-config-
lvm/+bug/390423/comments/11


On 2009-06-05T18:11:25

[Bug 413874] Re: [jaunty][iwl3945] WPA fully associate only after many retries

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=487183.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2009-02-24T17:37:44+00:00 Nigel wrote:

Created attachment 333065
syslogd log

Description of problem:
NetworkManager doesn't always connect to Network

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0.97-4.git20090219.fc11.i586
wpa_supplicant-0.6.7-3.fc11.i386
kernel-PAE-2.6.29-0.137.rc5.git4.fc11.i686

How reproducible:
Intermittent

Steps to Reproduce:

Either

1. Resume suspended laptop
2. wait for NM to connect to previously selected SSID
3. observe that NM fails & pops up request for secrets
or

1. Start with NM already connected to an AP
2. Select an alternate (but correctly configured, and available) AP
3. observe that NM fails &^ pops up secrets request

Actual results:
NM fails to connect

Expected results:
NM connects

Additional info:

Basically sometimes this works, sometimes it doesn't. Association
appears to time out. Other non-linux clients (S60/Nokia N95 8Gb/Nokia
N96/Windows 7/Windows Vista) don't *appear* to have a problem

In the log file attached note the "jonesn: " messages in the log. These
were created with the "logger" command to aid in documenting the
scenario

The Ap that I had been connected to ok was "planetf1c". The one that
failed was "planetf1f". Ignore "planetf1e" -- this one is not active and
I clicked on it in the GUI by mistake.

Error seems to hinge around
Activation (wlan0/wireless): association took too long.

Security in use is WPA2-PSK AES
wifi driver is iwl3945

Both AP are "fonera" routers running openwrt with atheros wireless. In
this config the router broadcasts 2 SSIDs.

Same problem has been observed with ddwrt (single SSID)

Log file is attached (kernel debug log, -dddt )

Not entirely clear if the issue is supplicant, NM or driver.

Final note:
I am also seeing issues with WPA Enterprise (LEAP and EAP-TLS) but figure it 
makes sense to address the simpler PSK case first (less variables, more control 
home vs enterprise...)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/413874/comments/0

On 2009-02-24T17:45:02+00:00 Nigel wrote:

I tried restarting NM, and the problem persisted... ie once we get into
this state the "bad" AP cannot be connected to.

I then stopped NM and unloaded the iwl3945 module, followed by
reloading/restarting

NM started and connected to the "good" AP just fine (c). I then clicked
on the "bad" AP in the GUI (f) and again it connected perfectly.

So is this some form of driver blacklisting/bad state info in iwl3945
driver?

>From syslog during driver load:
iwl3945 :03:00.0: PCI INT A disabled
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 
1.2.26kds
iwl3945: Copyright(c) 2003-2008 Intel Corporation
iwl3945 :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 :03:00.0: setting latency timer to 64
iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945: Detected Intel Wireless WiFi Link 3945ABG
wmaster0 (iwl3945): not using net_device_ops yet
phy1: Selected rate control algorithm 'iwl-3945-rs'
wlan0 (iwl3945): not using net_device_ops yet
iwl3945 :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 :03:00.0: irq 31 for MSI/MSI-X
iwl3945 :03:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 loaded firmware version 15.28.2.8
Registered led device: iwl-phy1:radio
Registered led device: iwl-phy1:assoc
Registered led device: iwl-phy1:RX
Registered led device: iwl-phy1:TX

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/413874/comments/1

On 2009-02-24T18:03:25+00:00 Nigel wrote:

Created attachment 333072
wpa supplicant log from same time period 

Added wpa supplicant log -- hopefully from correct times!

Also adding
options iwl3945 debug=0xbc88
for next time (43fff was too verbose)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/413874/comments/2

On 2009-02-24T19:11:14+00:00 Nigel wrote:

>From full wpa_supplicant log it appears that Association timeout is the
issue -- then causing blacklisting.

1235497219.167758: Selecting BSS from priority group 0
1235497219.167805: Try to find WPA-enabled AP
1235497219.167852: 0: 00:18:84:2a:74:67 ssid='planetf1f' wpa_ie_len=0 
rsn_ie_len=20 caps=0x11
1235497219.167921:skip - disabled
1235497219.167973:selected based on RSN IE
1235497219.168020:selected WPA AP 00:18:84:2a:74:67 ssid='planetf1f'
12

[Bug 275998] Re: internal mic capture very low volume when routed through pulseaudio

** Changed in: alsa-lib (Fedora)
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/275998

Title:
  internal mic capture very low volume when routed through pulseaudio

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/275998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 252713] Re: virt-manager has lack of keyboard layout option, thus renderin clients unusable

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=487735.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-02-27T17:47:19+00:00 Klaus-Peter wrote:

Description of problem:
I have created two virtual machines with virt-manager:
- Windows XP (32bit)
- Fedora 10 (64bit).
Both installed without problems, but when I try to make any text input in 
either of the guest OS, I get a strange, 'qwertyu' type keyboard layout.

On the host, I am using KDE 4.2, a German keyboard (evdev-managed) with
DE layout. Changing keyboard model from edev-managed to Generic doesn't
make any noticeable difference.

Version-Release number of selected component (if applicable):
kvm-74-10.fc10.x86_6
qemu-0.9.1-10.fc10.x86_64
virt-manager-0.6.0-5.fc10.x86_64

How reproducible:
always

Steps to Reproduce:
1. Create virtual machine with virt-manager
2. Start guest from virt-manager
3. Enter text in guest
  
Actual results:
Unexpected keyboard layout of unknown type, unusable

Expected results:
German 'qwertzu' keyboard layout

Additional info:
1. Whenever I switch the keyboard layout to "US" on the host, I immediately get 
a layout on the guest which is nearly ok (no symbols obtainable with the AltGr 
key); when I switch back to "DE", the borked layout is back.  

2. When I run any of the guests with the qemu-kvm command, I get a guest
layout which is nearly ok as well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/252713/comments/1


On 2009-03-01T10:54:40+00:00 Klaus-Peter wrote:

There is a workaround:

1. Change a line in the virtual machines's XML file in /etc/libvirt/qemu/ from
 to


2. Restart the libvirtd daemon.

But a bug in virt-manager remains. This tool seems to be made for
virtualization newbies like me who usually don't poke around in xml
configuration files hidden from ordinary users. It would be preferrable
if virt-manager asked for the desired keymap.

I still have the AltGr problem mentioned above, but that is another
story.

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/252713/comments/2


On 2009-03-01T11:50:55+00:00 Daniel wrote:

QEMU has had a VNC extension added so that the keymap is no longer
required - it will use raw scancodes across the wire & into the guest,
so the guest has complete control over keymap without needing this
setting. This will be in Fedora 11

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/252713/comments/3


On 2009-03-01T13:01:20+00:00 Klaus-Peter wrote:

Thanks, Daniel,
that sounds good (as far as I can understand it), and I can wait until Fedora 
11 comes up.

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/252713/comments/4


On 2009-03-04T16:54:54+00:00 Cole wrote:

Danpb, so how will this work? Does qemu just ignore a manually specified
keymap, or should libvirt drop the keymap setting for a sufficiently new
version?

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/252713/comments/5


On 2009-03-04T19:49:32+00:00 Daniel wrote:

No, if you set a keymap, QEMU will always use that keymap. The raw
scancode VNC extension is only activated if no keymap is specified. So
I'd recommend that virt-install never set a keymap, unless the user
explicitly asks for one with "--keymap fr". For virt-manager we should
probably have a globall preference available, which defaults to no
keymap at all, but which lets the user override to an explicit one if
desired (eg, so it works with VNC clients not supporting the extension)

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/252713/comments/6


On 2009-03-09T16:57:07+00:00 Klaus-Peter wrote:

FWIW: If there is no keymap specified in the xml file, i. e. if the above line 
reads

then the host's keymap setting are respected, even the characters accessible by 
means of the AltGr key are reproduced. It seems as if the key codes are mapped 
directly to the guest.

But you can't set this in virt-manager, you have to make changes in the
xml file manually.

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/252713/comments/7


On 2009-04-09T15:22:38+00:00 Cole wrote:

Okay, fixed python-virtinst-0.400.3-5.fc11 (

[Bug 271933] Re: http://user:pass@site/ link asks ‘Is "user" the site you want to visit?’

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=462392.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-09-15T21:07:06+00:00 Jonathan wrote:

I originally reported this upstream as
https://bugzilla.mozilla.org/show_bug.cgi?id=449303
but it appears to be Fedora-specific.

There are screenshots attached to the upstream bug showing the behaviour
I get.

User-Agent:   Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.1)
Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.1)
Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1

If you go to a URL with a basic auth username and password embedded in it, the
confirmation dialog asks if "mybank" is the site I want to visit, where
"mybank" is the username.  If I do want to go to my bank I will click yes, and
be taken to the phishing site.
I believe the dialog should say 'is "www.mozilla.com" the site you want to
visit?' instead, since that's the site the URL goes to.

Reproducible: Always

Steps to Reproduce:
1. click on http://mybank:c...@www.mozilla.com/en-US/
2. click yes, thinking you're going to your bank account
Actual Results:  
dialog says:
You are about to log in to the site "www.mozilla.com" with the user name
"mybank", but the web site does not require authentication. This may be an
attempt to trick you.

Is "mybank" the site you want to visit?

Expected Results:  
dialog says:
You are about to log in to the site "www.mozilla.com" with the user name
"mybank", but the web site does not require authentication. This may be an
attempt to trick you.

Is "www.mozilla.com" the site you want to visit?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/271933/comments/0


On 2008-09-17T12:56:12+00:00 Jonathan wrote:

The attachment I added to the upstream bug is
https://bugzilla.mozilla.org/attachment.cgi?id=332813

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/271933/comments/1


On 2008-09-18T22:58:32+00:00 Anders wrote:

I also see this on Ubuntu intrepid amd64, but upstream says it isn’t
their fault:

https://bugs.launchpad.net/fedora/+source/firefox/+bug/271933
https://bugzilla.mozilla.org/show_bug.cgi?id=455935

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/271933/comments/13


On 2008-12-21T01:28:06+00:00 Jonathan wrote:

Still present in firefox-3.0.4-1.fc10.x86_64

(and in ubuntu's 3.0.3 apparently)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/271933/comments/20


On 2008-12-22T11:25:37+00:00 Matěj wrote:

If you download an upstream binary from http://www.mozilla.com/en-US/
are you able to reproduce this? If yes, then it is conclusively an
upstream issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/271933/comments/22


On 2008-12-22T23:39:24+00:00 Jonathan wrote:

works correctly with upstream build
Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.9.0.5) Gecko/2008120121 
Firefox/3.0.5

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/271933/comments/23


On 2008-12-22T23:48:56+00:00 Jonathan wrote:

still wrong with latest fedora build
Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.5) Gecko/2008121622 
Fedora/3.0.5-1.fc10 Firefox/3.0.5

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/271933/comments/24


On 2009-06-10T02:43:34+00:00 Bug wrote:


This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
agai

[Bug 150721] Re: .xsession-errors: 'Failed to read saved session file'

** Changed in: metacity (Fedora)
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/150721

Title:
  .xsession-errors: 'Failed to read saved session file'

To manage notifications about this bug go to:
https://bugs.launchpad.net/metacity/+bug/150721/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 334657] Re: Subpixel/Lcd mode with VRGB/VBGR makes qt4 applications on Jaunty unreadable

Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=490377.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-15T20:55:12+00:00 Adam wrote:

Created attachment 335275
Qt4 application with RGB subpixel

Description of problem:
When VRGB is selected in subpixel font smoothing options in Gnome, Qt4 
applications display garbage instead of text.


Version-Release number of selected component (if applicable):
qt-4.5.0-3.fc11.x86_64


How reproducible:
Always.


Steps to Reproduce:
1. Select VRGB.
2. Run psi or lmms.

  
Actual results:
Garbage fonts.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/12


On 2009-03-15T20:55:45+00:00 Adam wrote:

Created attachment 335276
Qt4 application with VRGB subpixel

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/13


On 2009-03-15T21:01:54+00:00 Kevin wrote:

Just to ask the obvious: you do have freetype-freeworld or some other
freetype build with subpixel antialiasing support, right?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/14


On 2009-03-15T22:53:13+00:00 Rex wrote:

What X video driver are you using?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/15


On 2009-03-15T23:36:49+00:00 Adam wrote:

I do not have freetype-freeworld, this is the default Fedora 11
freetype. It DOES appear to have subpixel rendering: I can see it with
xmag.

I am using xorg-x11-drv-ati (r300 radeon, not using KMS).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/16


On 2009-03-16T00:00:44+00:00 Kevin wrote:

This is interesting, I just checked, subpixel antialiasing is disabled
in F9, but got reenabled in F10 and devel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/17


On 2009-04-11T07:42:04+00:00 Kevin wrote:

Behdad said enabling subpixel antialiasing in the Fedora freetype was a
mistake (because of patent issues), it's disabled again in current
Rawhide and there's also a new F10 freetype build with it disabled (but
I don't think it got pushed out). Still, Qt should not display garbage
with it...

This is also reproducible with Intel graphics according to:
https://www.redhat.com/archives/fedora-list/2009-April/msg01110.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/31


On 2009-04-14T17:56:52+00:00 José wrote:

I was using an r300 with KMS as it can be seen here:
http://lists.fedoraproject.org/pipermail/fedora-kde/2009-February/001479.html

The fix was to remove the hinting:
http://lists.fedoraproject.org/pipermail/fedora-kde/2009-February/001624.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/33


On 2009-04-14T18:28:24+00:00 Rex wrote:

Interesting, enabled full font hinting here in systemsettings, but I
(still) can't reproduce.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/34


On 2009-04-14T18:32:35+00:00 Rex wrote:

nevermind, reading closer (sorry), missed the vrgb part.  Confirmed
universally broken here, regardless of hinting.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/35


On 2009-04-14T18:42:43+00:00 Rex wrote:

confirmed to that vgbr is broken likewise.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/36


On 2009-04-14T19:48:52+00:00 Rex wrote:

* Tue Apr 14 2009 Rex Dieter  - 4.5.0-14
- fix vrgb/vgbr corruption, disable QT_USE_FREETYPE_LCDFILTER (#490377)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/334657/comments/37


On 2009-04-15T18:02:23+00:00 Fedora wrote:

kdeutils-4.2.2-2.fc10, kdetoys-4.2.2-2.fc10, kdesdk-4.2.2-2.fc10, 
kdeplasma-addons-4.2.2-2.fc10, kdeedu-4.2.2-1.fc10, 
kdebase-runtime-4.2.2-3.fc10, kdeba

[Bug 99368] Re: SVG rotation renderization broken

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=232796.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2007-03-17T22:45:07+00:00 Adam wrote:

Description of problem:
When displaying svg in firefox from default fedora installation the svg image is
garbled. Check e.g.:
http://www.lowlevel.cz/log/images/tuxtosh3.svg

Version-Release number of selected component (if applicable):
firefox-1.5.0.10-5.fc6

How reproducible:
always
  

Expected results:
Check the firefox downloaded from mozilla.com pages.

Additional info:
Could be related to cairo?!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/0


On 2007-03-17T22:50:46+00:00 Matěj wrote:

Created attachment 150321
rendering in Epiphany 2.16.3-3.fc6

Just to add one data-point -- this is rendering in epiphany on FC6. Looks
garbled to me as well.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/1


On 2007-03-18T21:51:09+00:00 Adam wrote:

Definitely. But epiphany is also using gecko - I'll bet on some library
behind.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/2


On 2007-03-26T11:35:46+00:00 Martin wrote:

Hm, all our gecko apps look broken.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/3


On 2007-03-26T13:22:22+00:00 Martin wrote:

Looks like a problem with system cairo library. When firefox is built with
"--disable-system-cairo", svg rendering works fine. Reassigning.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/4


On 2007-03-26T13:23:08+00:00 Martin wrote:

btw. broken in rawhide, too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/5


On 2007-05-23T10:59:42+00:00 Adam wrote:

Still present in latest rawhide liveCD image for F7.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/12


On 2007-05-24T22:47:52+00:00 Sylvain wrote:

Launchpad bug (also affecting Ubuntu):

https://bugs.launchpad.net/fedora/+source/firefox/+bug/99368

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/17


On 2007-07-30T09:51:39+00:00 Sylvain wrote:

This is fixed in version 2.0.0.5-1.fc7

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/30


On 2007-07-30T09:54:05+00:00 Martin wrote:

aha, thanks for the notice.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99368/comments/31


** Changed in: firefox (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/99368

Title:
  SVG rotation renderization broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/99368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 235988] Re: smbldap-passwd failed to modify unix password: shadowMax

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=430105.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2008-01-24T15:28:44+00:00 John wrote:

Upon upgrading from smbldap-tools-0.9.2-3.fc5 to smbldap-tools-0.9.4-1.fc8, I
noticed I could no longer change user passwords. smbldap-passwd would fail with
this error:

[root@myserver ~]# smbldap-passwd jdoe
Changing UNIX and samba passwords for jdoe
New password:
Retype new password:
Use of uninitialized value in string at /usr/sbin/smbldap-passwd line 277,
 line 2.
Failed to modify UNIX password: shadowMax: value #0 invalid per syntax at
/usr/sbin/smbldap-passwd line 285,  line 2.
[root@myserver ~]#

The problem seems to stem from 2 things:
1) I have no defaultMaxPasswordAge set in smbldap.conf. However, this has never
been a problem in the past, and isn't stated as being a required setting. If
possible, I'd like to keep maximum password ages diabled.
2) smbldap-passwd is trying to change attributes to the users account which
don't exist. If I'm reading the code correctly, it's attempting to set 3
attributes which don't apply to the samba schema: userPassword,
shadowLastChange, and shadowMax. They only apply to the nis schema, which we do
not use.

I apologize if I'm misconfiguring something, however as I stated, this worked
fine in 0.9.2.

Reply at: https://bugs.launchpad.net/ubuntu/+source/smbldap-
tools/+bug/235988/comments/0

On 2008-01-24T18:57:25+00:00 John wrote:

Correction: userPassword is in the samba schema, however shadowLastChange and
shadowMax are not.

Additionally, here is the LDIF export of the applicable jdoe user account that
was created using: smbldap-useradd -a -m -c "John Doe" -P jdoe

dn: uid=jdoe,ou=People,dc=mydomain,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
objectClass: sambaSamAccount
cn: jdoe
sn: jdoe
givenName: jdoe
uid: jdoe
uidNumber: 8199
gidNumber: 513
homeDirectory: /var/resource/users/jdoe
loginShell: /bin/bash
gecos: John Doe
userPassword: {crypt}x
sambaLogonTime: 0
sambaLogoffTime: 2147483647
sambaKickoffTime: 2147483647
sambaPwdCanChange: 0
displayName: jdoe
sambaSID: S-1-5-21-2828578859-3132521847-1089271054-17398
sambaPrimaryGroupSID: S-1-5-21-2828578859-3132521847-1089271054-513
sambaLogonScript: jdoe.bat
sambaHomeDrive: H:
sambaAcctFlags: [U]
sambaPwdMustChange: 1516489003
sambaLMPassword: (crypt)
sambaNTPassword: (crypt)
sambaPwdLastSet: 1201187794

Reply at: https://bugs.launchpad.net/ubuntu/+source/smbldap-
tools/+bug/235988/comments/1

On 2008-05-21T16:28:40+00:00 John wrote:

Created attachment 306274
Patch for smbldap-passwd on smbldap-tools-0.9.4-1.fc8

Ok. Seems as though the problem revolves around smbldap-passwd trying to set
shadowMax when no defaultMaxPasswordAge has been set in smbldap.conf. I have
attached a simple patch which seems to resolve the issue without any
side-effects.

Reply at: https://bugs.launchpad.net/ubuntu/+source/smbldap-
tools/+bug/235988/comments/2

On 2008-05-22T11:11:49+00:00 Paul wrote:

Quick query here: if you're not using the nis schema, how are you getting an
"objectClass: shadowAccount" in Comment #1?

Reply at: https://bugs.launchpad.net/ubuntu/+source/smbldap-
tools/+bug/235988/comments/3

On 2008-05-22T13:20:25+00:00 John wrote:

(In reply to comment #3)
> Quick query here: if you're not using the nis schema, how are you getting an
> "objectClass: shadowAccount" in Comment #1?

Sorry. That was incorrect. Somehow I missed the nis.schema include line in my
slapd.conf, which obviously has shadowMax. So my bug subject is inaccurate,
however the problem is still relevant. The new description should probably be
"smbldap-passwd tries to set shadowMax even though defaultMaxPasswordAge is not
defined".

Does my patch make sense?
Thanks!

Reply at: https://bugs.launchpad.net/ubuntu/+source/smbldap-
tools/+bug/235988/comments/4

On 2008-05-23T15:55:58+00:00 Paul wrote:

An almost identical patch has already been applied upstream in version
0.9.5.

See: https://gna.org/bugs/?10230

I've put together some packages for various Fedora releases at:
http://www.city-fan.org/ftp/contrib/sysutils/

The packages there are basically the same as the one I've just built for
Rawhide. If they seem OK, I'll push them as updates fo

[Bug 251039] Re: "Press Ctrl+Alt to release pointer." doesn't belong in the window title

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=475873.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-12-10T21:16:30+00:00 Daniel wrote:

User-Agent:   Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4)
Gecko/2008111318 Ubuntu/8.10 (intrepid) Firefox/3.0.4

In virt-manager, when the mouse is grabbed, "Press Ctrl+Alt to release
pointer." is added to the window title. This makes it excessively long
and can hide the most useful piece of information, the VM name. I
believe this information should be in ONE of the menu bar, the toolbar,
or a (new) status bar (with my preference being in that order).

Reproducible: Always

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/251039/comments/2


On 2012-02-06T21:48:31+00:00 Cole wrote:

The proper place for this to be would be a status bar at the bottom.
However we aren't going to add one just for the message, so changing
this bug to track the actual work that would be needed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/251039/comments/4


On 2012-02-07T16:10:44+00:00 Cole wrote:

*** Bug 640914 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/251039/comments/5


** Changed in: virt-manager
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/251039

Title:
  "Press Ctrl+Alt to release pointer." doesn't belong in the window
  title

To manage notifications about this bug go to:
https://bugs.launchpad.net/virt-manager/+bug/251039/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 185031] Re: [libvorbis] [CVE-2007-4066] multiple buffer overflows in libvorbis before 1.2.0

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=249780.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2007-07-26T23:23:55+00:00 Josh wrote:

Multiple flaws have been found in libvorbis.  These are fixed via libvorbis
version 1.2.0.

It should be noted that libvorbis 1.2.0 also fixes the issue described in bug
245991.

The id number of each flaw is the subversion commit id.  The descriptions were
provided by Chris Montgomery.  The libvorbis subversion repository is located 
here:
http://svn.xiph.org/trunk/vorbis

13217: possible seek infinite loop in libvorbisfile
13215: multiplexed/non Vorbis stream support [heap read, potential heap write]
13211: better return value checking of seeks [heap read, potential heap write]
13179: check legal maximum blocksize [static array read]
13169,13170,13172: correctly handle codebooks with zero entires [heap 
read/write]
13168: low bitrate static mode declaration error [static read, heap read,
potential heap write]
13151,13153,13154,13155,13167: residue decode vector overflow [heap read/write]
13162: static initializer declarations, check-before-free error fixes [heap
read/write]
13149: check legal minimum blocksize [static array read]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/comments/0


On 2007-08-20T20:09:54+00:00 Josh wrote:

Here is the breakdown of CVE id to libvorbis commit id mapping:

CVE-2007-4065: 13217 (infinite loop)

CVE-2007-4029 covers 2 issues with unknown commit IDs.

  According to Monty these two issues are the commit ids:
  13151, 13154, 13155, 13167
  and
  13149, 13153, 13179

CVE-2007-4066: multiple flaws

  13215: multiplexed/non Vorbis stream support
 [heap read, potential heap write]

  13211: better return value checking of seeks
 [heap read, potential heap write]

  13169,13170,13172: correctly handle codebooks with zero entires
 [heap read/write]

  13168: low bitrate static mode declaration error
 [static read, heap read, potential heap write]

  13162: static initializer declarations, check-before-free error fixes
 [heap read/write]


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/comments/1


On 2008-01-17T15:47:49+00:00 Red wrote:

This issue was addressed in:

Red Hat Enterprise Linux:
  http://rhn.redhat.com/errata/RHSA-2007-0845.html
  http://rhn.redhat.com/errata/RHSA-2007-0912.html

Fedora:
  https://admin.fedoraproject.org/updates/F7/FEDORA-2007-1765


Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/comments/2


** Changed in: libvorbis (Fedora)
   Importance: Unknown => High

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2007-4029

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2007-4065

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185031

Title:
  [libvorbis] [CVE-2007-4066] multiple buffer overflows in libvorbis
  before 1.2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/185031/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 118983] Re: compiz & java windows always grey

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=213908.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2006-11-03T18:31:57+00:00 Mario wrote:

Description of problem:

This is a known bug in Sun Java, I think we can do very little, I'm just posting
it here with a small workaround so that other people can find it easily and run
java programs until a fix is released from Sun.

The problem is that Swing applications with Sun Java do not work with Compiz and
Desktop effects enabled.

On the net there are a couple of workaround available, but I have found only one
works with fedora core 6.

One suggest to use MToolkit instead of the XToolKit:

export AWT_TOOLKIT=MToolkit

But this requires a library I was not able to find in fedora core 6 (it was in
the x11-deprecated-libs, but now this package seems to be removed).

The one that works with fedora is to install Xephyr and run java programs inside
Xephir, with metacity or another window manager that is not compiz, like the
following snippet shows:

--- cut ---
#! /bin/bash
# run_java.sh
Xephyr :2 -ac -screen 1430x850 &
metacity --display :2 &
export DISPLAY=:2
$1 &
--- cut ---

Just Create a file named run_java.sh with this content, Then just run
./run_java.sh netbeans or ./run_java.sh limewire and you will get a java program
into a Xephyr session, just change -screen values to suite your needs.

While this is a less than optimal solution, it works.

The last workaround is to disable compiz and desktop effects and use metacity
but it is really difficult to come back to the old desktop after you have tried
compiz :)

Version-Release number of selected component (if applicable):

Sun Java, at least from version 1.5.0_05 to 1.5.0_09 and 1.6.0 beta 2; IBM Java
1.5.0 update 3. Other JDK may have the same issues.

How reproducible:

Always, with compiz, some Swing based applications seem to work, but they froze
as soon as the user tries to resize the window.

Steps to Reproduce:
1. enable compiz
2. run a swing application
  
Actual results:
The application shows a grey windows, froze or does not resize (eventually
stopping to work)

Expected results:
Applications should start and work normally

Additional info:
GCJ seems to work, GNU classpath with Cacao also works. This is a bug in Sun
Java. SWT application are not affected. I have not tested AWT but it seems to
work, too (this is what I've read on the net, at least).

This is a bug enty in Sun Bugzilla that can be tracked:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6429775

Reply at: https://bugs.launchpad.net/ubuntu/+source/beryl-
core/+bug/118983/comments/0


On 2006-11-10T21:09:27+00:00 Mario wrote:

I wanted to add that first workaround proposed (the MToolkit fix), can be
enabled for fedora by installing the package libXp.

I have tested netbeans with this fix and seem to run fine on jdk 1.6 rc and jdk
1.5.0_09, but limewire does not run, maybe other application have issues...

Reply at: https://bugs.launchpad.net/ubuntu/+source/beryl-
core/+bug/118983/comments/1


On 2007-04-10T11:24:56+00:00 Mario wrote:

The jdk 1.6.0-u1 (officially released) works with compiz, I've not tested it
with beryl (I know there is a workaround for 1.6, but I don't know if it is
still valid/needed).

Reply at: https://bugs.launchpad.net/ubuntu/+source/beryl-
core/+bug/118983/comments/2


On 2007-10-22T22:06:51+00:00 Matěj wrote:

Reporter, I am not sure what version of compiz you used in April 2007 (sorry, we
missed this bug's activity), but could you check with the latest updates for FC6
(while it is still supported) whether this bug hasn't gone away in meantime, 
please?

Reply at: https://bugs.launchpad.net/ubuntu/+source/beryl-
core/+bug/118983/comments/13


On 2007-10-23T11:22:08+00:00 Mario wrote:

I'm sorry, I'm not in fedora 7.

The bug is somewhat fixed as of release 1.6.0.

You don't need anymore the workaround proposed, but still you get gray windows
when opening dialog boxes. It seems to be quite random, and I'm not sure how to
fix this (I'm still getting this with an updated compiz-4.0 and jdk 1.6.0.3).

I can check with the latest packages in fedora 8 as soon as it gets out, in the
meantime, I'm trying to install compiz-0.6 and compiz-fusion for fedora 7.

I will also test with IcedTea and let you know.

Mario

Reply at: https://bugs.launchpad.net/ubuntu/+source/beryl-
core/+bug/118983/comments/14

---

[Bug 1727331] Re: NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

2017-10-27 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727331

Title:
  NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1727331/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727242] Re: Cherry-pick upstream warning fix and compatibility with other extensions

2017-10-27 Thread Didier Roche

Tried with this version, no regression to report, +1

** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727242

Title:
  Cherry-pick upstream warning fix and compatibility with other
  extensions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1727242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724657] Re: Boot freeze with Ubuntu 17.10 Live ISO on Surface Book

2017-10-27 Thread Kai-Heng Feng

http://people.canonical.com/~khfeng/lp1724657-2/

We just need to test 12 more kernels to find the regression.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724657

Title:
  Boot freeze with Ubuntu 17.10 Live ISO on Surface Book

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724657/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

2017-10-27 Thread Kai-Heng Feng

Please try the kernel here:

http://people.canonical.com/~khfeng/lp1721345/

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721345

Title:
  ALC295 codec seems to have Master and PCM channels swapped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721345/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 794435] Re: Keyboard LED Applet doesn't show Caps Lock unless all three indicators are set

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=573222.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2010-03-13T14:31:46+00:00 Graeme wrote:

Description of problem:
I have put the LXPanel keyboard LED widget on my panel as I have no hardware 
LEDs to show the status of the Caps/Num/Scroll lock keys.
I have selected to display only the Caps item, but on reboot I get the icon for 
Scroll Lock, which does not change status with any of the keys.
Checking the config (right click settings menu) indicates that Caps-Lock is the 
only selected item.  Deselecting and reselecting the Caps-Lock item simply 
removes and readds the Scroll-Lock image to the panel, again not changing the 
status with any keypresses of any of the locking keys.

To get the desired behaviour I must select the Scroll lock setting, then
remove it and the Caps and Num lock status displays behave properly.

Version-Release number of selected component (if applicable):
This is with version 0.5.4.1-2.fc12

How reproducible:
After every reboot.

Steps to Reproduce:
1.  Add Keyboard settings LED to your panel, selecting only Caps Lock.  Observe 
that an indicator appears in the panel - an uppercase A.
2.  Reboot (or possibly log out).
3.  Log in

Actual results:
Observe that the status indicator is on scroll lock. (a down pointing arrow)

Expected results:
That the indicator would be for the caps lock (an uppercase A)

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/794435/comments/0

On 2010-04-05T21:02:29+00:00 Christoph wrote:

Tracked upstream at 
https://sourceforge.net/tracker/?func=detail&aid=2977158&group_id=180858&atid=894869

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/794435/comments/1

On 2010-05-05T22:21:14+00:00 Chris wrote:

Confirmed for me with the latest lxpanel-0.5.5-3.fc12.i686

It initially gave me num lock and scroll lock indicators, in that order.
I configured it to show me caps lock and num lock instead.  After logout
and login, it showed me num lock and scroll lock again, albeit in
reverse order this time.  Also, the scroll lock indicator doesn't work
at all, but I'm on an EeePC, where the scroll lock is an fn-modified
key.  The num lock is also fn-modified though, and it works.  Anyway, I
don't really care about global scroll lock state, since applications
these days generally interpret it as a toggle, but I'd really like my
caps lock indicator to come back up each time.  Unlike the other two,
it's very easy to fat-finger that key, especially on my 7" EeePC and
other netbooks where LXDE is typically used.

Ooh, I just went to set my Keyboard LED applet config to caps lock and
num lock (num lock and scroll lock came up) and found that the buttons
for caps lock and num lock were already checked, from my previous
session.  The check box for num lock worked properly, but the boxes for
caps lock and scroll lock toggled each other's buttons, until I got it
into a state where the check boxes matched the icons, and then they
controlled the right things.  There's something very screwy going on
with how Keyboard LED is processing that configuration.

It'd be nice if we could bump the priority on this, because while it's
not that severe of a bug, it's very annoying, it makes us look bad to
the many users who may be encountering Linux for the first time on a
netbook, and it should be a fairly obvious fix for anyone who knows that
code.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/794435/comments/2

On 2010-05-06T06:01:49+00:00 Christoph wrote:

(In reply to comment #2)
> It'd be nice if we could bump the priority on this, because while it's not 
> that
> severe of a bug, it's very annoying, it makes us look bad to the many users 
> who
> may be encountering Linux for the first time on a netbook, and it should be a
> fairly obvious fix for anyone who knows that code.

The best way to bump priority is to comment to the upstream bug report
and add your comments there. If Marty knows how many people are
affected/annoyed by this, he will probably invest more time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/794435/comments/3

On 2010-05-17T16:23:23+00:00 Christoph wrote:

Upstream bug report:
https://sourceforge.net/tracker/?func=detail&aid=2977158&group_id=180858&atid=894869

I will build an updated package soon.

Reply at:
https://bugs.launchpad

[Bug 716660] Re: Module b2c2_flexcop_pci error in dmesg.

Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=575873.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-03-22T15:46:49+00:00 Wolfgang wrote:

Description of problem:
In gnome i get this kernel-oops from abrt after the gnome-desktop is staying 
up. But it's no problem for looking tv (dvb-t) with kaffeine.

Version-Release number of selected component (if applicable):
2.6.34-0.15.rc2.git0.fc14.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Backtrace:
[ cut here ]
WARNING: at fs/proc/generic.c:316 __xlate_proc_name+0xbb/0xc2()
Hardware name: To Be Filled By O.E.M.
name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
Modules linked in: b2c2_flexcop_pci(+) snd_hda_codec b2c2_flexcop dvb_core 
cx24123 cx24113 s5h1420 snd_hwdep nvidia(P) snd_seq snd_seq_device i2c_i801 
snd_pcm r8169 snd_timer snd mii soundcore i2c_core snd_page_alloc usblp btrfs 
zlib_deflate libcrc32c sata_sil24
Pid: 697, comm: modprobe Tainted: P   2.6.34-0.15.rc2.git0.fc14.x86_64 
#1
Call Trace:
[] warn_slowpath_common+0x7c/0x94
[] warn_slowpath_fmt+0x41/0x43
[] ? __proc_create+0x44/0x141
[] __xlate_proc_name+0xbb/0xc2
[] __proc_create+0x53/0x141
[] proc_mkdir_mode+0x2e/0x5a
[] proc_mkdir+0x16/0x18
[] register_handler_proc+0xf3/0x120
[] __setup_irq+0x264/0x305
[] ? flexcop_pci_isr+0x0/0x142 [b2c2_flexcop_pci]
[] request_threaded_irq+0x14d/0x1e0
[] flexcop_pci_probe+0x1b4/0x339 [b2c2_flexcop_pci]
[] local_pci_probe+0x17/0x1b
[] pci_device_probe+0xcd/0xfd
[] ? driver_sysfs_add+0x4c/0x71
[] driver_probe_device+0xed/0x21a
[] __driver_attach+0x5d/0x81
[] ? __driver_attach+0x0/0x81
[] bus_for_each_dev+0x59/0x8e
[] driver_attach+0x1e/0x20
[] bus_add_driver+0x120/0x288
[] driver_register+0x9e/0x10f
[] __pci_register_driver+0x68/0xd8
[] ? up_read+0x23/0x3c
[] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
[] flexcop_pci_module_init+0x1e/0x20 [b2c2_flexcop_pci]
[] do_one_initcall+0x72/0x18a
[] sys_init_module+0xd8/0x23d
[] system_call_fastpath+0x16/0x1b

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/716660/comments/0


On 2010-04-05T19:26:39+00:00 Wolfgang wrote:

new kernel,oops again!
kernel-2.6.34-0.28.rc3.git3.fc14.x86_64

---[ cut here ]
WARNING: at fs/proc/generic.c:316 __xlate_proc_name+0xbb/0xc2()
Hardware name: To Be Filled By O.E.M.
name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
Modules linked in: b2c2_flexcop_pci(+) b2c2_flexcop dvb_core 
snd_hda_codec_realtek snd_hda_intel cx24123 nvidia(P) snd_hda_codec snd_hwdep 
cx24113 s5h1420 iTCO_wdt snd_seq snd_seq_device iTCO_vendor_support i2c_i801 
snd_pcm usblp snd_timer snd soundcore r8169 mii i2c_core snd_page_alloc btrfs 
zlib_deflate libcrc32c sata_sil24
Pid: 639, comm: modprobe Tainted: P   2.6.34-0.28.rc3.git3.fc14.x86_64 
#1
Call Trace:
[] warn_slowpath_common+0x7c/0x94
[] warn_slowpath_fmt+0x41/0x43
[] ? __proc_create+0x44/0x141
[] __xlate_proc_name+0xbb/0xc2
[] __proc_create+0x53/0x141
[] proc_mkdir_mode+0x2e/0x5a
[] proc_mkdir+0x16/0x18
[] register_handler_proc+0xf3/0x120
[] __setup_irq+0x264/0x305
[] ? flexcop_pci_isr+0x0/0x142 [b2c2_flexcop_pci]
[] request_threaded_irq+0x14d/0x1e2
[] flexcop_pci_probe+0x1b4/0x339 [b2c2_flexcop_pci]
[] local_pci_probe+0x17/0x1b
[] pci_device_probe+0xcd/0xfd
[] ? driver_sysfs_add+0x4c/0x71
[] driver_probe_device+0xed/0x21a
[] __driver_attach+0x5d/0x81
[] ? __driver_attach+0x0/0x81
[] bus_for_each_dev+0x59/0x8e
[] driver_attach+0x1e/0x20
[] bus_add_driver+0x120/0x288
[] driver_register+0x9e/0x10f
[] __pci_register_driver+0x68/0xd8
[] ? up_read+0x23/0x3c
[] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
[] flexcop_pci_module_init+0x1e/0x20 [b2c2_flexcop_pci]
[] do_one_initcall+0x72/0x18a
[] sys_init_module+0xd8/0x23d
[] system_call_fastpath+0x16/0x1b

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/716660/comments/1


On 2010-05-21T10:04:30+00:00 Wolfgang wrote:

new kernel-2.6.34-2.fc14.x86_64, same oops!

[ cut here ]
WARNING: at fs/proc/generic.c:317 __xlate_proc_name+0xbb/0xc2()
Hardware name: To Be Filled By O.E.M.
name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
Modules linked in: b2c2_flexcop_pci(+) videobuf_core budget_core b2c2_flexcop 
dvb_core cx24123 saa7146 snd_hda_codec_realtek cx24113 iTCO_wdt nvidia(P) 
ttpci_eeprom s5h1420 iTCO_vendor_support snd_hda_intel snd_hda_codec r8169 
i2c_i801 snd_hwdep snd_seq snd_seq_device snd_pcm mii snd_timer snd soundcore 
i2c_

[Bug 757040] Re: stk11xx web-cam driver should be included in the kernel

Launchpad has imported 18 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=573241.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-03-13T16:31:32+00:00 Sergey wrote:

Description of problem:
  Webcam is not recognized.
  Tested on F12 (2.6.32.9-70.fc12.x86_64) and Rawhide.

Steps to Reproduce:
1. Download 
http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/desktop-x86_64-20100310.20.iso
2. Make a bootable USB Flash stick from it
3. Boot

Actual results:
  No /dev/video* and big red sign in Cheese

Expected results:
  Device file in /dev/ and some image in cheese/mplayer

Additional info:

Linux version 2.6.33-1.fc13.x86_64
(mockbu...@x86-07.phx2.fedoraproject.org) (gcc version 4.4.3 20100211
(Red Hat 4.4.3-6) (GCC) ) #1 SMP Wed Feb 24 19:55:32 UTC 2010

Bus 001 Device 004: ID 174f:6a31 Syntek Web Cam - Asus A8J, F3S, F5R,
VX2S, V1S

Related parts of dmesg output:
...
usb 1-7: New USB device found, idVendor=174f, idProduct=6a31

usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=10  

usb 1-7: Product: USB2.0

usb 1-7: Manufacturer: Syntek   

...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/757040/comments/0


On 2010-03-13T16:33:35+00:00 Sergey wrote:

Created attachment 399867
lsusb -vvv

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/757040/comments/1


On 2010-04-06T09:46:01+00:00 Sergey wrote:

Anything else I can help with? I can provide additional information if
needed. And I don't mind to test something, if there's anything to
test...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/757040/comments/2


On 2010-07-30T11:03:47+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 14 
development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/757040/comments/3


On 2010-09-03T13:05:54+00:00 Chuck wrote:

Is this still failing on Fedora 14 Alpha and/or F13 with the 2.6.34
kernel installed?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/757040/comments/4


On 2011-02-06T13:18:13+00:00 Xavier wrote:

Up! Good Sunday everybody.

Yes, here this is still failing on Fedora 14 released with the 2.6.35
kernel (latest stable, as updated via official repositories).

Laptop: Asus V1S-AS004E (Spanish keyboard)
Distro: Fedora 14 x86_64 (KDE)

# uname -a
Linux venus.xapaho.com 2.6.35.10-74.fc14.x86_64 #1 SMP Thu Dec 23 16:04:50 UTC 
2010 x86_64 x86_64 x86_64 GNU/Linux

# lsusb | grep Syntek
Bus 001 Device 003: ID 174f:6a31 Syntek Web Cam - Asus A8J, F3S, F5R, VX2S, V1S

# dmesg | grep "usb 1-3"
[3.578482] usb 1-3: new high speed USB device using ehci_hcd and address 3
[3.942533] usb 1-3: New USB device found, idVendor=174f, idProduct=6a31
[3.942537] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=10
[3.942540] usb 1-3: Product: USB2.0
[3.942542] usb 1-3: Manufacturer: Syntek

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/757040/comments/5


On 2011-02-06T13:19:10+00:00 Xavier wrote:

Created attachment 477300
lsusb -vvv (webcam section)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/757040/comments/6


On 2011-02-07T18:18:44+00:00 Xavier wrote:

Here is a long post, which I wish I found here yesterday :)

*Workaround*

  For my specific system and kernel versions, cf. my previous comment,
just above.

  There is a syntek kernel module out there (on sourceforge), which now works 
for me
  (just like it had worked on the same hardware, with Ubuntu, a couple of years 
ago).
  Googling, one can find many users who have based their solution on this code.

  Below were my steps (exhaustive list, rather simple). It will be required to 
repeat them,
after each kernel update, or until the current svn code

[Bug 587186] Re: libc6 upgrade fails: illegal instruction

Launchpad has imported 48 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=579838.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-04-06T17:28:18+00:00 Dan wrote:

F-13 userspace can't be booted in system with AMD Geode LX CPU. Per
http://fedoraproject.org/wiki/Features/F12X86Support it is a supported
CPU for the x86 Fedora. Because the panic or "Illegal instruction"
exception appears so early when userspace binaries should be run leads
me to think that something is wrong in libc.

The symptoms are
- when booted F-13 kernel + F-13 initramfs => kernel panic when code from 
initramfs should be executed
- when booted F-12 kernel + F-12 initramfs => unable to chroot to the F-13 
userspace, see the attachments for boot logs in 2 situations - first is with 
init=/bin/bash on the kernel command line, second is with rdbreak=pre-pivot and 
manual chroot

Version-Release number of selected component (if applicable):
glibc-2.11.90-16

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/0


On 2010-04-06T17:28:57+00:00 Dan wrote:

Created attachment 404757
f12kernel-f13userspace-1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/1


On 2010-04-06T17:29:25+00:00 Dan wrote:

Created attachment 404758
f12kernel-f13userspace-2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/2


On 2010-04-06T17:29:51+00:00 Dan wrote:

Created attachment 404759
f13kernel-f13userspace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/3


On 2010-04-07T07:43:40+00:00 Dan wrote:

Created attachment 404857
disassembly

I have installed gdb into the initramfs and now I can see the exact
place of the crash. The NOPL instruction throws the exception and it's
really unknown on the Geode LX per
http://support.amd.com/us/Embedded_TechDocs/33234H_LX_databook.pdf.

Buildroot used to build this glibc is
http://koji.fedoraproject.org/koji/buildrootinfo?buildrootID=742936 and
gcc is gcc-4.4.3-8.fc13.i686.rpm

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/4


On 2010-04-07T07:48:56+00:00 Jakub wrote:

So the CPU isn't i686 compatible and thus isn't supported.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/5


On 2010-04-07T08:41:38+00:00 Dan wrote:

Ok, then we should write a new release note for F-13 about the changed
CPU support.

Just for curiosity, where can I get the definition of i686 architecture?
I have "Intel® 64 and IA-32 Architectures Software Developer’s Manual",
but how can one find there what's i686 and what was added in later CPUs?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/6


On 2010-04-07T11:15:39+00:00 Andreas wrote:

That should eventually be fixed in the kernel, see .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/7


On 2010-06-02T09:50:28+00:00 Till wrote:

(In reply to comment #5)
> So the CPU isn't i686 compatible and thus isn't supported.

I opened a Fesco ticket to clarify which CPUs are supported by Fedora:
https://fedorahosted.org/fesco/ticket/387

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186/comments/22


On 2010-06-08T04:26:30+00:00 Dont wrote:

There is no clarification needed by FESCo.  The release was intended to
support the Geode LX -- whether or not it is an "i686" (it isn't).
Nothing in the F13 release specifications says anything about changing
the set of supported CPUs from F12, which clearly supported the Geode LX
(see Comment 1).

Further investigation in the released Fedora 13 i686 LiveCD reveals that
NOPL instructions only occur in binaries produced from glibc, and in a
couple of statically linked binaries (/sbin/sln and /sbin/mdadm.static)
linked with glibc.

NOPL instructions can be generated by the GNU Assembler for .align
commands that occur in executable sections.  GCC can generate .align
when optimizing, to align loop starts on cache line boundaries

[Bug 672643] Re: make test fails on xfs filesystem

Launchpad has imported 19 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=562815.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-02-08T13:26:31+00:00 Anton wrote:

Description of problem:

When I try to rebuild upstart with /tmp - XFS filesystem,
build failed on test Testing conf_source_reload() with new job directory  (see 
log). If tmpfs of ext3 mounted on /tmp, build finishes ok,
but after install and reboot, boot process freezed on init start 
(I have / XFS too).

Version-Release number of selected component (if applicable):
upstart-0.6.3-7.fc13.src.rpm
last working version: upstart-0.3.11-3.1.bcx.src.rpm

How reproducible:
100%

Steps to Reproduce:
1. mount /tmp XFS
2. try to rebuild rpm
3. see failed test.
4. mount /tmp tmpfs
5. rebuild rpm - OK
--  only for mazo:
6. PREPARE for boot error (copy old init)
7. upgrage
8. reboot -- see boot hang.
9. restore old init

  
Actual results:
dont work on XFS.

Expected results:
work on ANY good filesystem
(may be clean request for FS abilities).


Additional info:

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/0


On 2010-02-08T13:27:36+00:00 Anton wrote:

Created attachment 389514
build log with error

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/1


On 2010-02-08T15:23:38+00:00 Casey wrote:

Only interesting thing about upstart and filesystems is its use of
inotify. I've never used XFS, does it support inotify?

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/2


On 2010-02-10T16:44:32+00:00 Anton wrote:

Seems to work
tty3: inotifywait /tmp
tty2: touch /tmp/zzz

tty3 out: /tmp/: CREATE zzz

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/3


On 2010-02-16T20:38:40+00:00 Eric wrote:

Are you certain this is specific to xfs?

I changed the TEST_FILENAME() macro to use /mnt/testfs instead of /tmp,
tried ext3, ext4, and xfs, re-running "make check-TESTS" in the init/
dir, and it seems to fail on each one.

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/4


On 2010-02-16T20:51:48+00:00 Eric wrote:

Hm, or more simply, mount different filesystems on /tmp :)

Well, I get failures with ext4 /tmp as well as with tmpfs on /tmp

Anton, any chance you can try ext3 or ext4 in your setup?

I'm inclined to distrust this "make check" ... but then I can't tell
what it's doing, w/ all the macro cleverness.

Just for examples...

xfs:

Testing nih_dir_walk()
...with no filter
...with filter
...with stat failure and no error handler
BAD: wrong value for logger_called, expected 1 got 0
at tests/test_file.c:934 (test_dir_walk).
/bin/sh: line 4: 28248 Aborted ${dir}$tst
FAIL: test_file

Testing nih_watch_new()
...with file
...with directory only
...with directory and sub-directories
...with create handler
...with non-existant path
...with error with sub-directory
BAD: wrong value for logger_called, expected TRUE got FALSE
at tests/test_watch.c:504 (test_new).
/bin/sh: line 4: 28253 Aborted ${dir}$tst
FAIL: test_watch

Testing nih_main_write_pidfile()
...with successful write
...with overwrite of existing pid
...with failure to write to temporary file
BAD: wrong value for ret, expected less than 0 got 0
at tests/test_main.c:417 (test_write_pidfile).
/bin/sh: line 4: 28258 Aborted ${dir}$tst
FAIL: test_main

ext3:

Same 3 failures.


-Eric

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/5


On 2010-02-17T11:24:24+00:00 Petr wrote:

Are you runninng make check under root user?

Some libnih and upstart tests fail with euid == 0. Typical reason is
that test tries if it is able to read file without read right on file or
"x" right on directory and root user can always read or walk through
these files/directories

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/6


On 2010-02-17T11:30:21+00:00 Petr wrote:

Comment #5 probably refers to another issue than original report see my
previous comment

Reply at: https://bugs.launchpad.net/libnih/+bug/672643/comments/7


On 2010-02-18T16:32:15+00:00 Eric wrote:

Ok, yes, I was running it as root.  Sorry fo

[Bug 586175] Re: Windows XP/2003 doesn't boot

** Changed in: fedora
   Status: Unknown => Won't Fix

** Changed in: fedora
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/586175

Title:
  Windows XP/2003 doesn't boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/586175/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 620751] Re: dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap

** Changed in: poppler (Fedora)
   Status: Unknown => Fix Released

** Changed in: poppler
   Status: Unknown => Fix Released

** Changed in: poppler (Fedora)
   Importance: Unknown => Medium

** Changed in: poppler
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620751

Title:
  dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/620751/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 570836] Re: invalid MIME type in /usr/share/applications/gnumeric.desktop

Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=580725.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2010-04-08T21:19:52+00:00 Michal wrote:

Description of problem:

The following is reported during an installation:

Error in file "/usr/share/applications/fedora-gnumeric.desktop": "zz-
application/zz-winassoc-xls" is an invalid MIME type ("zz-application"
is an unregistered media type)

This is likely an old entry but something started to care.

Version-Release number of selected component (if applicable):
gnumeric-1.10.0-1.fc14

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/0

On 2010-07-30T11:17:28+00:00 Bug wrote:

This bug appears to have been reported against 'rawhide' during the Fedora 14
development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/6

On 2010-08-03T14:18:57+00:00 Dave wrote:

This bug also affects Fedora 13 (gnumeric-1.10.0-1.fc13.i686)
and earlier releases

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/7

On 2010-08-05T22:11:47+00:00 Julian wrote:

*** Bug 587620 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/8

On 2010-10-02T17:31:55+00:00 M wrote:

The problem is in the checker, not in Gnumeric.

"zz-application/zz-winassoc-xls" is real mime type. See, for example,
http://filetonic.com/blog/tag/file-extension/. It is unregistered and
probably violates a spec or two somewhere, but it is real. When the
spec and reality disagree, the spec is due for service.

Upstream bug is here https://bugzilla.gnome.org/show_bug.cgi?id=619303
I am not sure why it is WONTFIX as opposed to NOTABUG.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/9

On 2010-10-02T18:08:03+00:00 Michal wrote:

(In reply to comment #4)
> The problem is in the checker, not in Gnumeric.

> I am not sure why it is WONTFIX as opposed to NOTABUG.

It is clearly a BUG. Maybe not that crucial after all but it is there.
Where and how it should be fixed is another question.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/10

On 2011-02-12T09:19:08+00:00 Julian wrote:

OK, this BUG now starts to interfere with me updating gnumeric:
https://admin.fedoraproject.org/updates/gnome-chemistry-utils-0.12.6-2.fc14,goffice-0.8.13-1.fc14,gnumeric-1.10.13-1.fc14

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/13

On 2011-02-12T09:43:07+00:00 Julian wrote:

Similar to 587566.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/14

On 2011-09-28T10:05:41+00:00 Hans wrote:

I've filed a bug upstream for this:
https://bugs.freedesktop.org/show_bug.cgi?id=41286

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/19

On 2011-11-26T05:40:37+00:00 Cristian wrote:

gnumeric-1.10.17-1.fc16.x86_64 is affected, too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/570836/comments/26

On 2012-08-16T20:08:48+00:00 Fedora wrote:

This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this i

[Bug 612671] Re: Live Migration Guest Network Stops Responding

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=580806.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2010-04-09T05:54:30+00:00 Lijian wrote:

Description of problem:
I'm testing live migration feature following instructions in 
https://fedoraproject.org/wiki/QA:Testcase_Live_Migration_using_libvirt/virsh, 
the migration does work, but the pinging to the guest OS was interrupted just 
after the migration succeeded, and network doesn't work even if I restart the 
NetworkManager in guest OS.
This happens both on Fedora 12 and Windows XP SP3 I've tested, maybe it's a 
bug.
BTW, I'm using bridge network on both source and dest machines, and the 
interface names are all the same("br0").

Version-Release number of selected component (if applicable):
* kernel-2.6.33.1-19.fc13
* libvirt-0.7.7-1.fc13
* python-virtinst-0.500.2-3.fc13
* qemu-0.12.3-6.fc13
* seabios-0.5.1-1.fc13
* virt-manager-0.8.3-2.fc13

How reproducible:
Always.

Steps to Reproduce:
1. Share the image with dest host via NFS.
2. Start Guest OS, and ping it.
3. Run "virsh migrate --live testxp qemu+ssh://10.66.65.51/system"

Actual results:
Ping returns nothing after Guest OS in source host closes, re-ping it, and 
outputs:

>From 10.66.65.190 icmp_seq=2611 Destination Host Unreachable
>From 10.66.65.190 icmp_seq=2612 Destination Host Unreachable
>From 10.66.65.190 icmp_seq=2613 Destination Host Unreachable

The same when pinging from Guest OS to Host OS.

Expected results:
Ping continue uninterrupted.

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/612671/comments/0

On 2010-05-21T17:33:02+00:00 Cole wrote:

Can you still reproduce this issue? On the remote host, if you do 'virsh
define $vmname' for the migrated VM, the reboot the VM, do you get
network connectivity?

Do VMs on the remote host have network connectivity to start? Can you
provide the XML of the migrated guest? Can the guest ping public
websites at all?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/612671/comments/1

On 2010-06-17T17:51:17+00:00 Cole wrote:

Closing as INSUFFICIENT_DATA. Please reopen if you can reproduce with
latest F13 or rawhide packages.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/612671/comments/2

On 2010-08-03T14:08:38+00:00 Moshe wrote:

I have what seems to be an identical issue.

I can confirm that a reboot of the XP SP3 guest OS /does/ return the
networking to operation - at the expense of making live migration a bit
of a pointless exercise since the intention is to avoid the reboot and
keep things running seamlessly.

The identical cluster migrating a Linux VM works properly - there is no
interruption to operation.  NeatX/NoMachine sessions continue to operate
and no pings are lost.

Right now, this seems to affect XP SP3.  I've tried it with and without
the virtio network driver but the result is identical.

My systems are AMD64 quad core CPUs - both servers are identical in all
hardware.

A tcpdump shows the XP guest sends out packets, these are forwarded over
the bridge and the reply packets also come back onto the guest vnet0
device but the guest does not see them.  e.g. a tcpdump shows the ping
request and the reply packet but the guest itself does not receive the
reply packet even though tcpdump shows it is there.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/612671/comments/7

** Changed in: libvirt
   Status: Unknown => Expired

** Changed in: libvirt
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/612671

Title:
  Live Migration Guest Network Stops Responding

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/612671/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 530605] Re: gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu.

Launchpad has imported 33 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=573202.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-03-13T11:55:38+00:00 Flóki wrote:

Description of problem:
Not possible to see samba share in Nautilus. 
Write smb: into location.
Then "Windows Network"  appears in header. Wait over 10 seconds and then 
error window comes. 

Version-Release number of selected component (if applicable):
samba-3.5.1-58.fc13.x86_64
system-config-samba-1.2.86-1.fc13.noarch
samba-winbind-clients-3.5.1-58.fc13.x86_64
samba-common-3.5.1-58.fc13.x86_64

selinux-policy-3.7.11-1.fc13.noarch
libselinux-2.0.90-5.fc13.x86_64
libselinux-utils-2.0.90-5.fc13.x86_64
selinux-policy-targeted-3.7.11-1.fc13.noarch
libselinux-python-2.0.90-5.fc13.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Open Nautilus and Ctrl+l 
2. Write smb:  into Lotstion
3. Wait over 10 seconds 
and error window 
The folder contents could not be displayed.
  
Actual results:
Error window 
The folder contents could not be displayed.
Sorry, could not display all the contents of "Windows Network": DBus error 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

Expected results:
To see enabeld samba shares
There is local sama share

Additional info:
Just rebooted to reapply selinux policy
There is no message in /var/log/messages
It is possible to see local samba share form another computer ( F12 )

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/6


On 2010-03-13T12:31:17+00:00 Flóki wrote:

Created attachment 399847
messages after settin selinux in permissive mode

When setting selinux in permissive mode then it possible to see local samba 
share
but not open it.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/7


On 2010-03-13T17:00:33+00:00 Simo wrote:

Can you check your firewall settings are not blocking samba client
packetes ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/8


On 2010-03-13T18:26:25+00:00 Flóki wrote:

>Can you check your firewall settings are not blocking samba client
packetes ?

samba and samba client  are marked as trusted.  
Fierwall disabled 
The folder contents could not be displayed.
Sorry, could not display all the contents of "Windows Network": DBus error 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

no message i /var/log/messages


If seleinux in permissive 
Mar 13 18:15:25 flokic dbus: avc:  received setenforce notice (enforcing=0)
Mar 13 18:15:25 flokic dbus: avc:  received setenforce notice (enforcing=0)
Mar 13 18:15:25 flokic dbus: Can't send to audit system: USER_AVC avc:  
received setenforce notice (enforcing=0)#012: exe="?" sauid=81 hostname=? 
addr=? terminal=?

and error window
Unable to mount location
Sorry, could not display all the contents of "Windows Network": DBus error 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/9


On 2010-03-13T22:40:42+00:00 Simo wrote:

Sorry but this looks like a nautilus or gnome-vfs problem to me.

Reassigning.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/10


On 2010-03-15T20:25:52+00:00 Flóki wrote:

I see in top that  gvfsd-smb-brows is with cpu over 90%

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/12


On 2010-03-16T16:40:03+00:00 Tomáš wrote:

Can you please post you gvfs, gnome-keyring and libgnome-keyring package
versions? Also, would it be possible to grab a backtrace and post it
here? I'm not seeing this

[Bug 1722454] Re: Duplicity fails with MemoryError

2017-10-27 Thread Juerg Haefliger

*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159

Hmm... Why do you think this is a duplicate of #1720159? My stack trace
looks different.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1722454/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

cdb939456f81878cda1f31ba0ef1a3b1d7be07e8 (rebased) is bad.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724911

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724911/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571864] Re: update-motd.5 manpage references /var/run/motd

2017-10-27 Thread Launchpad Bug Tracker

** Merge proposal linked:
   https://code.launchpad.net/~vorlon/ubuntu/+source/pam/+git/pam/+merge/332890

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571864

Title:
  update-motd.5 manpage references /var/run/motd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1571864/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727956] [NEW] Installer crashes when installing over existing LUKS encryption

2017-10-27 Thread Aku Pietikäinen

Public bug reported:

Trying to install Ubuntu over existing LUKS full disk encryption.
Installer crashes when running grub-installer to /dev/dm-0.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
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
CasperVersion: 1.380
Date: Fri Oct 27 10:24:45 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu-gnome zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727956

Title:
  Installer crashes when installing over existing LUKS encryption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1727956/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

2017-10-27 Thread Peter Wallbridge

Thanks for the info. The answer is yes


On Fri, Oct 27, 2017 at 3:04 AM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> This could be related to OpenGL texture sizes or something similar.
> Unity7 (Compiz) has workarounds to avoid that limitation. And Xfce
> avoids it by not using hardware accelerated compositing at all (last I
> checked). It's not surprising if only Gnome Shell hits a problem like
> this...
>
> Do you get the same bug logging in to "Ubuntu" vs "Ubuntu on Xorg"?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Confirmed
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1695610] Re: Test missing in lists_lists leading to wrong listing when using -V option

Thanks for the FYI Mark,
so this will be picke dup on the merge of 2.1.25 then.

Given the low prio IMHO there is no need to plan for SRUs back to older
releases, objections?

** Changed in: mailman (Ubuntu)
   Status: New => Confirmed

** Changed in: mailman (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695610

Title:
  Test missing in lists_lists leading to wrong listing when using -V
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1695610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1432630] Re: libvirt tunnelled migration fails with "migration job: unexpectedly failed"

Following upstream to Won't Fix for now.

** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432630

Title:
  libvirt tunnelled migration fails with "migration job: unexpectedly
  failed"

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1432630/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727955] Re: nautilus crashed with SIGABRT in g_assertion_message()

2017-10-27 Thread Apport retracing service

*** This bug is a duplicate of bug 1725745 ***
https://bugs.launchpad.net/bugs/1725745

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1725745, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997576/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997578/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997582/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997583/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997584/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997585/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997586/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1725745
   nautilus crashed with SIGABRT in g_assertion_message()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727955

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1727955/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727581] Re: Segmentation fault on map loading (17.10)

2017-10-27 Thread Quin

Solved by using upstream AppImage. Requires SDL2 to be updated in the
distribution channels.

** Changed in: redeclipse (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/redeclipse/+question/660040

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727581

Title:
  Segmentation fault on map loading (17.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redeclipse/+bug/1727581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727581] Re: Segmentation fault on map loading (17.10)

2017-10-27 Thread Quin

Yeah, outdated version of SDL2 then.

Glad you had luck with our AppImage, have fun playing!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727581

Title:
  Segmentation fault on map loading (17.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redeclipse/+bug/1727581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723840] Re: Firefox 56.0 High CPU

2017-10-27 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723840

Title:
  Firefox 56.0 High CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1723840/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727595] Re: package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

*** This bug is a duplicate of bug 1670629 ***
https://bugs.launchpad.net/bugs/1670629

** This bug is no longer a duplicate of bug 1722007
   package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1670629
   postinst runs mysql_upgrade before server is properly started ( Can't 
connect [...] '/var/run/mysqld/mysqld.sock)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727595

Title:
  package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1727595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

Hi,
I see you are updating all bugs upcoming with 2.1.25 - thanks for all your work 
Mark.
Since on mailman I'm more a triage than anything else I fail to rate the 
severity of this.
To me it seems that if this would be rather important mailman would never have 
worked correctly, but it did so I (for now rate it low) and would just pick up 
the fix on next Merge but not plan for an SRU.
Please if you (much better at estimating mailman usage) think this is SRU 
worthy please point that out and maybe add a link to the exact fix commit.

** Changed in: mailman (Ubuntu)
   Status: New => Triaged

** Changed in: mailman (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696066

Title:
  Postfix module - Mailman wrapper - Couldn't write data/aliases.db and
  data/virtual-mailman.db files

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1696066/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1722007] Re: package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

*** This bug is a duplicate of bug 1670629 ***
https://bugs.launchpad.net/bugs/1670629

Hi,
this is a race when upgrading the package and starting the server as part of it.
A known issue in bug 1670629 that is worked on, the bug might have hints and 
workarounds - but usually that resolves on a retry of the upgrade.

** This bug has been marked a duplicate of bug 1670629
   postinst runs mysql_upgrade before server is properly started ( Can't 
connect [...] '/var/run/mysqld/mysqld.sock)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722007

Title:
  package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1722007/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725836] Re: No more than 2 displays work simultaneously

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1720262] Re: gnome-screenshot Actions don't work in default Ubuntu 17.10 session

There is no easy way to have those actions filtered out for
GNOME/wayland only...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720262

Title:
  gnome-screenshot Actions don't work in default Ubuntu 17.10 session

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1720262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727242] Re: Cherry-pick upstream warning fix and compatibility with other extensions

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Artful)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727242

Title:
  Cherry-pick upstream warning fix and compatibility with other
  extensions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1727242/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723840] Re: Firefox 56.0 High CPU

2017-10-27 Thread Simone

** Also affects: firefox (Arch Linux)
   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/1723840

Title:
  Firefox 56.0 High CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1723840/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726017] Re: dnsmasq prematurely returns REFUSED, breaking resolver

2017-10-27 Thread Martin Wilck

** Description changed:

+ 
+ [Impact] 
+ 
+  * DNS name resolution fails in certain network configurations, where
+different DNS servers are responsible for different domains and one or
+more servers reply REFUSED to queries that regard other domains than
+their own. Without the patch, dnsmasq returns a negative reply to
+if only one such negative answer is received from a forwarder, even
+if other forwarders return valid responses.
+ 
+This breaks
+the resolver and practically all internet connectivity, including web 
+browsing, email, and receiving updates.
+ 
+  * This should be backported to stable to fix internet connectivity 
+for users.
+ 
+  * The patch fixes the problem by querying all servers and only returning
+a negative reply to the requestor only if *all* forwarders return negative
+responses.
+ 
+ [Test Case]
+ 
+  * It should be possible to test this in a virtual network. One DNS server
+should be responsible for queries to the outside world, and the other one
+could be a DHCP/DNS instance (perhaps dnsmasq, also) that handles internal
+IP addresses and names. It's important that at least one of these servers
+return REFUSED to queries that don't belong into its realm (assuming the 
+domain name is "my.net", the server for "my.net" would reply REFUSED to
+"ubuntu.com" and every other domain. I am not sure if this is normally the
+case, all I can say is that my Linux-based ASUS router does it.
+ 
+Connect an Ubuntu VM to this network.
+ 
+To aggravate the problem, the DHCP server would put the internal DNS
+server first in the nameservers field. If that's the case, the problem
+would also occur if the client used "strict-order" in dnsmasq.conf.
+ 
+ [Regression Potential]
+ 
+  * I don't see any. Would there be networks where admins rely upon getting
+NXDOMAIN back if just one server fails for a DNS query? I don't know.
+ 
+ [Other Info]
+  
+ Original bug description follows.
+ 
+ 
  Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update.
  
  In my local network, I have two DNS servers; 192.168.1.1 is the local
  DHCP/DNS server configured to reply to queries inside the local network,
  and 192.168.1.4 is the forwarder in my DSL Router, responsible to answer
  queries about the outside world. THe DHCP server returns these in the
  order 192.168.1.4,192.168.1.1. The internal server replies REFUSED to
  queries about external domains.
  
  This configuration has worked well with Ubuntu 14.04 and other Linux
  Distros (using Fedora and OpenSUSE internally here), as well as various
  other OSes.
  
  It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance
  pushes the REFUSED reply from 192.168.1.1 to applications and ignores
  the successful reply from 2.168.1.4. This causes all DNS queries to
  external servers to fail.
  
  I believe this is fixed in dnsmasq 2.76 and related to
  
  http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2016q1/010263.html
  
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=68f6312d4bae30b78daafcd6f51dc441b8685b1e
  http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=4ace25c5d6
  
- According to these sources, the bug was introduced with 
+ According to these sources, the bug was introduced with
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=51967f9807665dae403f1497b827165c5fa1084b
  
  In my local setup at least, I can work around the problem by using the
  "strict-order" option to dnsmasq.
  
  echo strict-order >/etc/NetworkManager/dnsmasq.d/order.conf
  
  But that's not a general solution. If dnsmasq has several forwarders,
  and some return SERVFAIL or REFUSED and others return SUCCESS, the
  successful answer should be returned to clients, independent of the
  strict-order setting.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726017

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1726017/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609700] Re: username is not saved in openconnect connection dialog

Thanks, closing the bug then

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager-openconnect (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager-openconnect (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609700

Title:
  username is not saved in openconnect connection dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1308674] Re: [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked

2017-10-27 Thread Will Cooke

This issue went away for me sometime in the last year.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308674

Title:
  [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken
  when going from docked -> undocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1308674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727308] Re: when you try to change the layout for a long time reacts

thanks

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727308

Title:
  when you try to change the layout for a long time reacts

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1727308/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()

2017-10-27 Thread José Dapena Paz

Workaround: uninstall evolution-indicator package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725315

Title:
  evolution crashed with SIGSEGV in g_hash_table_lookup_node()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1725315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()

2017-10-27 Thread José Dapena Paz

This only happens on gnome-shell on wayland mode. It is evolution
indicator plugin. Unfortunately, even clicking on the checkbox to
disable it (on the list of evolution plugins) crashes evolution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725315

Title:
  evolution crashed with SIGSEGV in g_hash_table_lookup_node()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1725315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727911] Re: fcitx not dispaly

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727911

Title:
  fcitx not dispaly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727911/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727911] Re: fcitx not dispaly

note that GNOME has no fcitx integration but only ibus

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727911

Title:
  fcitx not dispaly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727911/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727967] [NEW] Keyboard layout for password is wrong at first login after boot

2017-10-27 Thread Walter St

Public bug reported:

After upgrading from 16.04 to 17.10 the keyboard layout on the initial
login screen is incorrect. It uses the German layout (z <-> y keys are
exchanged, QWERTZ instead of QWERTY), although I have set the following
in my /etc/defaults/locale:

LANG=en_US.UTF-8
LC_NUMERIC=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
LC_MONETARY=en_GB.UTF-8
LC_PAPER=en_GB.UTF-8
LC_NAME=en_GB.UTF-8
LC_ADDRESS=en_GB.UTF-8
LC_TELEPHONE=en_GB.UTF-8
LC_MEASUREMENT=en_GB.UTF-8
LC_IDENTIFICATION=en_GB.UTF-8

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-release-upgrader-core 1:17.10.8
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 10:03:10 2017
InstallationDate: Installed on 2016-06-29 (484 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to artful on 2017-10-23 (3 days ago)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful dist-upgrade package-from-proposed 
wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727967

Title:
  Keyboard layout for password is wrong at first login after boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1727967/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1663280] Re: Serious performance degradation of math functions

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1421121.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-02-10T12:09:55+00:00 Oleg wrote:

Bug [0] has been introduced in Glibc 2.23 [1] and fixed in Glibc 2.25
[2]. Fedora 24 and Fedora 25 are affected because they use either Glibc
2.23 or 2.24. Bug introduces serious (2x-4x) performance degradation of
math functions (pow, exp/exp2/exp10, log/log2/log10, sin/cos/sincos/tan,
asin/acos/atan/atan2, sinh/cosh/tanh, asinh/acosh/atanh) provided by
libm. Bug can be reproduced on any AVX-capable x86-64 machine.

This bug is all about AVX-SSE transition penalty [3]. 256-bit YMM
registers used by AVX-256 instructions extend 128-bit registers used by
SSE (XMM0 is a low half of YMM0 and so on). Every time CPU executes SSE
instruction after AVX-256 instruction it has to store upper half of the
YMM register to the internal buffer and then restore it when execution
returns back to AVX instructions. Store/restore is required because old-
fashioned SSE knows nothing about the upper halves of its registers and
may damage them. This store/restore operation is time consuming (several
tens of clock cycles for each operation). To deal with this issue, Intel
introduced AVX-128 instructions which operate on the same 128-bit XMM
register as SSE but take into account upper halves of YMM registers.
Hence, no store/restore required. Practically speaking, AVX-128
instructions is a new smart form of SSE instructions which can be used
together with full-size AVX-256 instructions without any penalty. Intel
recommends to use AVX-128 instructions instead of SSE instructions
wherever possible. To sum things up, it's okay to mix SSE with AVX-128
and AVX-128 with AVX-256. Mixing AVX-128 with AVX-256 is allowed because
both types of instructions are aware of 256-bit YMM registers. Mixing
SSE with AVX-128 is okay because CPU can guarantee that the upper halves
of YMM registers don't contain any meaningful data (how one can put it
there without using AVX-256 instructions) and avoid doing store/restore
operation (why to care about random trash in the upper halves of the YMM
registers). It's not okay to mix SSE with AVX-256 due to the transition
penalty. Scalar floating-point instructions used by routines mentioned
above are implemented as a subset of SSE and AVX-128 instructions. They
operate on a small fraction of 128-bit register but still considered
SSE/AVX-128 instruction. And they suffer from SSE/AVX transition penalty
as well.

Glibc inadvertently triggers a chain of AVX/SSE transition penalties due
to inappropriate use of AVX-256 instructions inside
_dl_runtime_resolve() procedure. By using AVX-256 instructions to
push/pop YMM registers, Glibc makes CPU think that the upper halves of
XMM registers contain meaningful data which needs to be preserved during
execution of SSE instructions. With such a 'dirty' flag set every switch
between SSE and AVX instructions (AVX-128 or AVX-256) leads to a time
consuming store/restore procedure. This 'dirty' flag never gets cleared
during the whole program execution which leads to a serious overall
slowdown. Fixed implementation [2] of _dl_runtime_resolve() procedure
tries to avoid using AVX-256 instructions if possible.

Buggy _dl_runtime_resolve() gets called every time when dynamic linker
tries to resolve a symbol (any symbol, not just ones mentioned above).
It's enough for _dl_runtime_resolve() to be called just once to touch
the upper halves of the YMM registers and provoke AVX/SSE transition
penalty in the future. It's safe to say that all dynamically linked
application call _dl_runtime_resolve() at least once which means that
all of them may experience slowdown. Performance degradation takes place
when such application mixes AVX and SSE instructions (switches from AVX
to SSE or back).

There are two types of math routines provided by libm:
(a) ones that have AVX-optimized version (exp, sin/cos, tan, atan, log and 
other)
(b) ones that don't have AVX-optimized version and rely on general purpose SSE 
implementation (pow, exp2/exp10, asin/acos, sinh/cosh/tanh, asinh/acosh/atanh 
and others)

For the former group of routines slowdown happens when they get called
from SSE code (i.e. from the application compiled with -mno-avx) because
SSE -> AVX transition takes place. For the latter one slowdown happens
when routines get called from AVX code (i.e. from the application
compiled with -mavx) because AVX -> SSE transition takes place. Both
situations look realistic. SSE code gets generated by gcc to target
x86-64 and AVX-optimized code gets generated by gcc -march=native on
AVX-capable machines.

[Bug 1219245] Re: soffice.bin crashed with SIGSEGV in ImplDevFontListData::~ImplDevFontListData()

Launchpad has imported 20 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1057977.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-01-26T10:20:39+00:00 Josep wrote:

Version-Release number of selected component:
libreoffice-core-4.1.4.2-4.fc20

Additional info:
reporter:   libreport-2.1.11
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --impress 
--splash-pipe=5
crash_function: ServerFont::Release
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.12.8-300.fc20.x86_64
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ServerFont::Release at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:341
 #1 GlyphCache::UncacheFont at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:236
 #2 X11SalGraphics::setFont at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:166
 #3 X11SalGraphics::SetFont at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:508
 #4 ReleaseFonts at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salgdi.hxx:224
 #5 OutputDevice::ImplUpdateFontData at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:186
 #7 OutputDevice::ImplUpdateAllFontData at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:262
 #8 ImplHandleSalSettings at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2216
 #9 ImplWindowFrameProc at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2597
 #10 CallCallback at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salframe.hxx:243

Potential duplicate: bug 1045497

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/7


On 2014-01-26T10:20:44+00:00 Josep wrote:

Created attachment 855640
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/8


On 2014-01-26T10:20:46+00:00 Josep wrote:

Created attachment 855641
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/9


On 2014-01-26T10:20:48+00:00 Josep wrote:

Created attachment 855642
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/10


On 2014-01-26T10:20:50+00:00 Josep wrote:

Created attachment 855643
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/11


On 2014-01-26T10:20:52+00:00 Josep wrote:

Created attachment 855644
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/12


On 2014-01-26T10:20:54+00:00 Josep wrote:

Created attachment 855645
File: exploitable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/13


On 2014-01-26T10:20:56+00:00 Josep wrote:

Created attachment 855646
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/14


On 2014-01-26T10:20:57+00:00 Josep wrote:

Created attachment 855647
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/15


On 2014-01-26T10:20:59+00:00 Josep wrote:

Created attachment 855648
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/16


On 2014-01-26T10:21:01+00:00 Josep wrote:

Created attachment 855649
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/17


On 2014-01-26T10:21:03+00:00 Josep wrote:

Created attachment 855650
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/18


On 2014-01-27T13:18:00+00:00 David wrote:

It is not reproducible, I presume?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+b

[Bug 1569613] Re: /usr/bin/nm-applet:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all:nma_icons_reload:g_closure_invoke

The reports go up to the 1.2 version so it looks fixed with the newest
series, closing the bug

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569613

Title:
  /usr/bin/nm-
  
applet:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all:nma_icons_reload:g_closure_invoke

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1569613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1413127] Re: WARNING: CPU: 3 PID: 2121 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:47 assert_device_not_suspended.isra.8+0x43/0x50 [i915]()

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1133123.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-08-22T19:41:08+00:00 Fabio wrote:

Additional info:
reporter:   libreport-2.2.3
WARNING: CPU: 1 PID: 79 at drivers/gpu/drm/i915/intel_uncore.c:47 
assert_device_not_suspended.isra.8+0x43/0x50 [i915]()
Device suspended[03]
Modules linked in: cpufreq_stats fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack tun bridge stp llc bnep dm_crypt arc4 hid_sensor_accel_3d 
hid_sensor_rotation hid_sensor_incl_3d x86_pkg_temp_thermal hid_sensor_als 
coretemp hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_trigger 
industrialio_triggered_buffer kfifo_buf iwlmvm kvm_intel industrialio iTCO_wdt 
hid_sensor_iio_common iTCO_vendor_support mac80211 kvm vfat fat 
crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel iwlwifi 
microcode uvcvideo snd_hda_codec_realtek snd_hda_codec_hdmi 
snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops videobuf2_core 
serio_raw cfg80211 btusb v4l2_common videodev hid_multitouch snd_hda_intel 
hid_sensor_hub
 bluetooth snd_hda_controller media snd_hda_codec i2c_i801 snd_seq mei_me mei 
lpc_ich snd_seq_device mfd_core shpchp snd_hwdep snd_pcm ideapad_laptop 
sparse_keymap rfkill snd_timer int3403_thermal snd dw_dmac i2c_hid dw_dmac_core 
soundcore i2c_designware_platform i2c_designware_core btrfs xor i915 raid6_pq 
i2c_algo_bit drm_kms_helper drm i2c_core sdhci_acpi sdhci mmc_core video
CPU: 1 PID: 79 Comm: kswapd0 Not tainted 3.16.1-300.fc21.x86_64 #1
Hardware name: LENOVO 20266/Yoga2, BIOS 76CN31WW 10/31/2013
  56f28f08 88025178f928 8171bcb2
 88025178f970 88025178f960 8108f2dd 880250a3
 00100070 880250a30080 00100070 0020
Call Trace:
 [] dump_stack+0x45/0x56
 [] warn_slowpath_common+0x7d/0xa0
 [] warn_slowpath_fmt+0x5c/0x80
 [] ? invalidate_mapping_pages+0x93/0x1e0
 [] assert_device_not_suspended.isra.8+0x43/0x50 [i915]
 [] hsw_write32+0x3a/0x160 [i915]
 [] i915_gem_write_fence+0xe2/0x580 [i915]
 [] i915_gem_object_update_fence+0x9a/0xd0 [i915]
 [] i915_gem_object_put_fence+0x88/0xd0 [i915][03]
 [] i915_vma_unbind+0x198/0x200 [i915][03]
 [] __i915_gem_shrink+0x274/0x330 [i915]
 [] i915_gem_shrinker_scan+0xb5/0xc0 [i915]
 [] shrink_slab_node+0x129/0x2b0
 [] shrink_slab+0x8b/0x170
 [] kswapd_shrink_zone+0x13e/0x1e0
 [] balance_pgdat+0x343/0x4c0
 [] kswapd+0x18e/0x450[03]
 [] ? abort_exclusive_wait+0xb0/0xb0
 [] ? balance_pgdat+0x4c0/0x4c0
 [] kthread+0xea/0x100[03]
 [] ? insert_kthread_work+0x40/0x40
 [] ret_from_fork+0x7c/0xb0
 [] ? insert_kthread_work+0x40/0x40

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413127/comments/0


On 2014-08-22T19:41:13+00:00 Fabio wrote:

Created attachment 929770
File: dmesg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413127/comments/1


On 2014-11-19T15:49:58+00:00 Adam wrote:

*** Bug 1144255 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413127/comments/2


On 2015-05-27T16:07:00+00:00 Adam wrote:

*** Bug 1196017 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413127/comments/11


On 2015-05-27T16:07:08+00:00 Adam wrote:

*** Bug 1225194 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413127/comments/12


On 2015-11-04T11:26:26+00:00 Fedora wrote:

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it ag

[Bug 627008] Re: Cannot read cd: sound-juicer and gvfs problem (workaround included)

** Changed in: sound-juicer (Fedora)
   Status: Unknown => Won't Fix

** Changed in: sound-juicer (Fedora)
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/627008

Title:
  Cannot read cd: sound-juicer and gvfs problem (workaround included)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-juicer/+bug/627008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver

Launchpad has imported 20 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=488368.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-03T22:14:16+00:00 Russell wrote:

Description of problem:
I have an MGE Ellipse Pulsar 500 UPS (USB ID 0463:), connected via USB, and 
since upgrading to F10 from F8, usbhid-ups will not start.

Version-Release number of selected component (if applicable):
[root@detritus ~]# rpm -qa | grep ^nut
nut-client-2.2.2-4.fc10.x86_64
nut-2.2.2-4.fc10.x86_64
[root@detritus ~]# uname -r
2.6.27.15-170.2.24.fc10.x86_64


How reproducible: Every time


Steps to Reproduce:
1. Configure a UPS with driver = usbhid-ups
2. Attempt to start ups service
  
Actual results:
[root@detritus ~]# service ups start
Starting UPS driver controller:[FAILED]
Starting upsd: [  OK  ]
Starting UPS monitor (master): [  OK  ]

Expected results:
Service should start successfully

Additional info:
[root@detritus ~]# lsusb -d 0463:
Bus 003 Device 002: ID 0463: MGE UPS Systems UPS
[root@detritus ~]# usbhid-ups -D -a mge -x vendorid=0463 -x productid=
Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2)

debug level is '5'
upsdrv_initups...
[snipped checking other USB devices here]
Checking device (0463/) (003/002)
- VendorID: 0463
- ProductID: 
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 003
Trying to match device
Device matches
failed to claim USB device, trying 2 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 1 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 0 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
Unable to get HID descriptor (error sending control message: Operation not 
permitted)
i=0, extra[i]=09, extra[i+1]=21
HID descriptor, method 2: (9 bytes) => 09 21 00 01 21 01 22 14 02
HID descriptor length 532
Unable to get Report descriptor: Operation not permitted
[snipped checking other USB devices here]
No appropriate HID device found
No matching HID UPS found

This looks very similar to bug 461374, but that was apparently fixed.
The documentation tells me that this is definitely the correct driver to
use (I think I could use mge-shut if I used a serial cable instead, but
my serial port is in use for something else).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/comments/0


On 2009-03-10T16:09:33+00:00 Michal wrote:

could you try check if

usbhid-ups -u root -DD -a 

works?  is name of your ups in ups.conf  - in square brackets

also, do you have any selinux denial messages?

do you see any messages in /var/log/messages related to this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/comments/1


On 2009-03-14T19:01:17+00:00 Russell wrote:

"usbhid-ups -u root -DD -a mge" is successful.

When I start usbhid-ups on its own, without "-u root", /var/log/messages
doesn't contain anything (and just a "Connection refused" message when I
try to start NUT via the initscript), and I don't see any selinux
messages.

Adding "user = root" to ups.conf seems to allow it to start OK but (having 
amended my config to use IPv4, as upsd doesn't seem to want to listen on IPv6) 
upsd still can't connect until I fix a socket permission problem:
[root@detritus ~]# ls -l /var/run/nut/usbhid-ups-mge
srw-rw 1 root root 0 2009-03-14 18:44 /var/run/nut/usbhid-ups-mge
[root@detritus ~]# chmod o+rw /var/run/nut/usbhid-ups-mge

After doing this (after NUT startup) everything works, but obviously
this is a dirty hack - but I imagine the problem will go away once we
get to the bottom of why usbhid-ups needs to run as root in order to
work.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/comments/2


On 2009-03-17T12:49:59+00:00 Michal wrote:

First, I've got the same errors when starting ups service. Then I've
fully configured it and it works for me now without any errors.

could you upload all your nut config files in this bz?
/etc/sysconfig/ups
/etc/ups/ups.conf
/etc/ups/upsd.conf
/etc/ups/upsd.users
/etc/ups/upsmon.conf
/etc/ups/upssched.conf

[Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam

Launchpad has imported 37 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1241930.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-07-10T12:50:50+00:00 Kevin wrote:

Description of problem:  After updating to wpa_supplicant 2.4-3 on July
1, was unable to connect to my corporate wifi access point.  Subsequent
downgrade to wpa_supplicant 2.3-3 fixed access problem, so I think this
is a wpa_supplicant bug


Version-Release number of selected component (if applicable): wpa_supplicant 
2.4-3


How reproducible:  Upgrade to 2.4-3 try to access wpa/wpa2 wifi with TTLS 
authentication that has been working for well over a year now.  Fails.  
Downgrade to 2.3-3 and it works again.


Steps to Reproduce: See above
1. Select network in NetworkManager
2. Does not connect
3. Keeps asking for password

Actual results:

>From /etc/wpa_supplicant.log after upgrade:

wlp12s0: SME: Trying to authenticate with e0:1c:41:34:19:e9 (SSID='CICS' 
freq=5220 MHz)
wlp12s0: Trying to associate with e0:1c:41:34:19:e9 (SSID='CICS' freq=5220 MHz)
wlp12s0: Associated with e0:1c:41:34:19:e9
wlp12s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
wlp12s0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlp12s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
wlp12s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty' hash=c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty' hash=c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=1 
subject='/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, 
Inc./OU=http://certificates.g
odaddy.com/repository/CN=Go Daddy Secure Certification 
Authority/serialNumber=07969287' hash=09ed6e991fc3273d8fea317d339c0204
1861973549cfa6e1558f411f11211aa3
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/OU=Domain Control 
Validated/CN=cicsnc.org' hash=598c9bcc63d9e114262181d14
dfed5372381b7ae0eb762e701b689b0e309f9b7
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:cicsnc.org
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:www.cicsnc.org
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:osx.cicsnc.org
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:osx2.cicsnc.org
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:handshake failure
OpenSSL: openssl_handshake - SSL_connect error:14082174:SSL 
routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small
wlp12s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlp12s0: Authentication with e0:1c:41:34:19:e9 timed out.
wlp12s0: CTRL-EVENT-DISCONNECTED bssid=e0:1c:41:34:19:e9 reason=3 
locally_generated=1
wlp12s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CICS" auth_failures=1 
duration=10 reason=AUTH_FAILED
wlp12s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CICS" auth_failures=2 
duration=35 reason=CONN_FAILED


After downgrade:

wlp12s0: Trying to associate with e0:1c:41:34:19:e9 (SSID='CICS' freq=5220 MHz)
wlp12s0: Associated with e0:1c:41:34:19:e9
wlp12s0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlp12s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
wlp12s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
wlp12s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty'
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty'
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=1 
subject='/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, 
Inc./OU=http://certificates.g
odaddy.com/repository/CN=Go Daddy Secure Certification 
Authority/serialNumber=07969287'
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/OU=Domain Control 
Validated/CN=cicsnc.org'
EAP-MSCHAPV2: Authentication succeeded
wlp12s0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
wlp12s0: WPA: Key negotiation completed with e0:1c:41:34:19:e9 [PTK=CCMP 
GTK=CCMP]
wlp12s0: CTRL-EVENT-CONNECTED - Connection to e0:1c:41:34:19:e9 completed [id=0 
id_str=]
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-62 noise= txrate=6000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise= txrate=81000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise= txrate=135000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise= txrate=6000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise= txrate=121500
wlp12s0: CTRL-EVENT-SIGNAL-C

[Bug 379228] Re: screen starts flashing and freezes or crashes X

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=490237.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-13T23:06:31+00:00 Dark wrote:

I use evdev for both mouse and keyboard because I have a two-head setup
on this machine. I recently upgraded to

xorg-x11-drv-evdev-2.1.3-1.fc10.i386

After this upgrade, my usb optical mouse periodically stops working. The
light will brighten when moved, but the cursor does not move. If I kill
X and restart, it works fine again. This happens 1-3 times a day.

I have downgraded to

xorg-x11-drv-evdev-2.1.2-1.fc10.i386

and the problem has disappeared. The second mouse works fine to my
knowledge.

---

Mouse configuration (Mouse0):

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "evdev"
Option  "Device" 
"/dev/input/by-id/usb-HP_Multimedia_Keyboard_Hub-event-kbd"
Option  "XkbModel" "evdev"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "IMPS/2"
Option  "Device" "/dev/input/by-id/usb-HP_HP_USB_WHEEL_MOUSE-mouse"
EndSection

Section "InputDevice"
Identifier  "Keyboard1"
Driver  "evdev"
Option  "Device" "/dev/input/by-id/usb-_USB_Keyboard-event-kbd"
Option  "XkbModel" "evdev"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Mouse1"
Driver  "mouse"
Option  "Protocol" "IMPS/2"
Option  "Device" 
"/dev/input/by-id/usb-Logitech_Optical_USB_Mouse-mouse"
EndSection

---

End of XOrg logs:

While X is running normally:
(II) config/hal: Adding input device Sleep Button (CM)
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device Power Button (FF)
(EE) config/hal: NewInputDeviceRequest failed
 
Killed X with mouse working:
(II) config/hal: Adding input device Sleep Button (CM)
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device Power Button (FF)
(EE) config/hal: NewInputDeviceRequest failed
(II) UnloadModule: "mouse"
(II) Keyboard0: Close
(II) UnloadModule: "evdev"
 
Killed X after mouse stopped working:
(II) config/hal: Adding input device Sleep Button (CM)
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device Power Button (FF)
(EE) config/hal: NewInputDeviceRequest failed
(II) 3rd Button detected: disabling emulate3Button
(II) config/hal: Adding input device HP HP USB WHEEL MOUSE
(EE) config/hal: NewInputDeviceRequest failed
(II) UnloadModule: "mouse"
(II) Keyboard0: Close
(II) UnloadModule: "evdev"

Reply at: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-180/+bug/379228/comments/0


On 2009-03-14T19:13:53+00:00 Dark wrote:

Seems to be USB disconnects. I think this is a hardware issue. I will
reopen this report if a new mouse does not fix.

dmesg snip

input: HP HP USB WHEEL MOUSE as 
/devices/pci:00/:00:1a.7/usb1/1-2/1-2.1/1-2.1:1.0/input/input19
input,hidraw1: USB HID v1.00 Mouse [HP HP USB WHEEL MOUSE] on 
usb-:00:1a.7-2.1
usb 1-2.1: New USB device found, idVendor=0458, idProduct=0007
usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.1: Product: HP USB WHEEL MOUSE
usb 1-2.1: Manufacturer: HP
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
usb 1-2.1: USB disconnect, address 24
usb 1-2.1: new low speed USB device using ehci_hcd and address 25
usb 1-2.1: configuration #1 chosen from 1 choice
input: HP HP USB WHEEL MOUSE as 
/devices/pci:00/:00:1a.7/usb1/1-2/1-2.1/1-2.1:1.0/input/input20
input,hidraw1: USB HID v1.00 Mouse [HP HP USB WHEEL MOUSE] on 
usb-:00:1a.7-2.1
usb 1-2.1: New USB device found, idVendor=0458, idProduct=0007
usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.1: Product: HP USB WHEEL MOUSE
usb 1-2.1: Manufacturer: HP
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
usb 1-2.1: USB disconnect, address 25
usb 1-2.1: new low speed USB device using ehci_hcd and address 26
usb 1-2.1: configuration #1 chosen from 1 choice
input: HP HP USB WHEEL MOUSE as 
/devices/pci:00/:00:1a.7/usb1/1-2/1-2.1/1-2.1:1.0/input/input21
input,hidraw1: USB HID v1.00 Mouse [HP HP USB WHEEL MOUSE] on 
usb-:00:1a.7-2.1
usb 1-2.1: New USB device found, idVendor=0458, idProduct=0007
usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.1: Product: HP USB WHEEL MOUSE
usb 1-2.1: Manufacturer: HP
usb 1-2.1: USB disconnect, address 26
usb 1-2.1: new low speed USB dev

[Bug 582347] Re: etags screw filenames starting with ./

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=545398.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-12-08T13:26:05+00:00 Sjoerd wrote:

Created attachment 376898
Patch for the problem described, replacing strcpy with memmove.

Description of problem:
This is a bug against etags.emacs which is packaged in emacs-common, but there 
is no separate component called emacs-common.  This same bug exists in 
etags.xemacs, packaged in xemacs-common.

When etags is run with filenames starting with "./", it normalizes them
to start without "./", but does so incorrectly, messing up the result.


Version-Release number of selected component (if applicable):
emacs-common-23.1-13.fc12.x86_64
xemacs-common-21.5.29-8.fc12.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a file with a C function and path e.g. src/gdk/gdk_atoms.c
2. Run /usr/bin/etags.emacs ./src/gdk/gdk_atoms.c
3. Observe the filename in TAGS
  
Actual results:
The filename recorded in the TAGS file is src/gdk/gdk_otoms.c (note "o" after 
underscore).

Expected results:
The filename should be src/gdk/gdk_atoms.c

Additional info:
The problem is a call to strcpy on overlapping buffers.  In Fedora 11 and 
before that seems to have worked, but in Fedora 12 it often does not work, at 
least not for slightly longer filenames.

The attached patch should also work for etags.xemacs in xemacs-common,
except for differing line numbers.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/0


On 2009-12-08T13:31:25+00:00 Sjoerd wrote:

Also see bug 545399 for the XEmacs version of the bug.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/1


On 2009-12-08T16:52:30+00:00 Karel wrote:

I cannot reproduce it on 32-bit Fedora, but the usage of strcpy in the
code is clearly wrong. Moreover, this bug is already fixed in the
upstream CVS.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/2


On 2009-12-08T17:29:57+00:00 Karel wrote:

http://koji.fedoraproject.org/koji/taskinfo?taskID=1863033

The fix will be a part of next update.

Thanks for nicely detailed bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/3


On 2010-03-30T23:18:05+00:00 Fedora wrote:

emacs-23.1-11.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/emacs-23.1-11.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/4


On 2010-04-01T01:41:57+00:00 Fedora wrote:

emacs-23.1-11.fc11 has been pushed to the Fedora 11 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update emacs'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/emacs-23.1-11.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/5


On 2010-04-01T16:10:06+00:00 Fedora wrote:

emacs-23.1-13.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/emacs-23.1-13.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/6


On 2010-04-09T01:45:18+00:00 Fedora wrote:

emacs-23.1-13.fc11 has been pushed to the Fedora 11 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update emacs'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/emacs-23.1-13.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/7


On 2010-04-20T13:08:50+00:00 Fedora wrote:

emacs-23.1-13.fc11 has been pushed to the Fedora 11 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/8


** Changed in: emacs23 (Fedo

[Bug 430203] Re: bell.ogg is unresponsive (outside HIG response times) [regression]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=498608.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-05-01T13:20:42+00:00 Davide wrote:

Description of problem:

If multiple alert-triggering events occur too close in time, the alert
sound is only played upon the first event, whereas no alert sound is
played for the remaining alert-triggering events.

Consider the case of two successive alert-triggering events. If the
delay between the two alert events is longer than the duration of the
alert sound, two distinct alert sounds are played. If, however, the
second alert event is triggered before the sound for the first alert
event has finished playing, no alert sound for the second alert event is
played. If more than two event-triggering events occur within a time
window shorter than the duration of the alert sound, only one alert
sound is played. This is bad because all alerts but the first one
essentially vanish.

In a situation where an alert is triggered every time a given key is
pressed, pressing the key twice must lead to two alert sounds, no matter
how quickly the two keypresses are done. This way, the user receives
feedback on each of the two keypresses. Issuing a single alert sound
would leave the user without feedback about the second keypress.

In order to combine the two alert sounds, two solutions come to my mind:
1. the first alert sound is interrupted and the second alert sound is played 
immediately afterwards
2. the second alert sound is superimposed to the first one
Note that when the system beep was used for alerts (prior to the introduction 
of libcanberra (*), I think), solution 1 was in place. The first beep would be 
interrupted to give way to the second beep. The user would (sloppily speaking) 
hear "Bee-bep" and hence receive the information that two separate beeps 
had been issued.

(*) Thanks to bug 498594, this situation can currently be observed by
turning the desktop effects on.


Version-Release number of selected component (if applicable):

As in the 2009-04-30 rawhide. In particular:
libcanberra-0.12-1.fc11.x86_64
pulseaudio-0.9.15-11.fc11.x86_64
alsa-lib-1.0.19-3.fc11.x86_64


How reproducible:

always


Steps to Reproduce:

1. Ensure desktop effects are disabled (see bug 498594) and that the sound 
theme is set to
"Default"
2. Open a gnome-terminal window
3. Push the "down" arrow very quickly two times within the gnome-terminal 
window to trigger two consecutive alert events
4. Keep the "down" arrow pressed to trigger a large number of consecutive alert 
events


Actual results:

In step 3, a single alert sound is heard.
In step 4, the alert sound is played periodically, with the period equal to the 
duration of the alert sound.


Expected results:

In step 3, two alert sounds be heard (either with the first one being 
interrupted to give way to the second one, as in solution 1, or with the second 
one superimposing on the first one, as in solution 2).
In step 4, multiple alert sounds be heard (again, either according to solution 
1 or to solution 2), with the speed at which new alert sounds are started being 
equal to the keypress repeat speed specified in the keyboard preferences.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
sounds/+bug/430203/comments/0


On 2009-06-06T08:50:40+00:00 Davide wrote:

I found more information to support my request. The GNOME Human Interface 
Guidelines contain the following:
(Source:
http://library.gnome.org/devel/hig-book/stable/feedback-response-times.html.en)

"Verify that your application provides feedback within 100 milliseconds
(0.1 second) after each key press, movement of the mouse, or other
physical input from the user."

In the scenario described in the bug report, this clearly does not
happen.

I hope that libcanberra is the correct component to report the bug
against.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
sounds/+bug/430203/comments/1


On 2009-06-09T14:56:44+00:00 Bug wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 11 
development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
sounds/+bug/430203/comments/2


On 2009-08-28T03:35:06+00:00 Lennart wrote:

This is actually a "feature" in metacity:

http://git.gnome.org/cgit/metacity/tree/src/core/display.c#n2387

It limits bell events

[Bug 344751] Re: Disable stack protector for gdal

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=446607.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-05-15T10:48:08+00:00 Balint wrote:

Description of problem:
gdal segfault sometimes

Version-Release number of selected component (if applicable):
gdal-1.5.1-5.fc9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/344751/comments/0


On 2008-05-15T10:48:37+00:00 Balint wrote:

solved disabling stack protector at compile time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/344751/comments/1


On 2008-05-15T10:49:19+00:00 Fedora wrote:

gdal-1.5.1-6.fc9 has been submitted as an update for Fedora 9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/344751/comments/2


On 2008-05-17T22:26:38+00:00 Fedora wrote:

gdal-1.5.1-6.fc9 has been pushed to the Fedora 9 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/344751/comments/3


On 2009-03-18T21:38:12+00:00 Even wrote:

I'd like to post here the following message I've posted on gdal-dev
yesterday :


cited from:

http://lists.osgeo.org/pipermail/gdal-dev/2009-March/020022.html
[gdal-dev] [SOLVED] GDAL crashing on Ubuntu 8.10

--- begin citation -
Even Rouault even.rouault at mines-paris.org
Tue Mar 17 19:33:57 EDT 2009

Hi all,

Several users have reported over the past few weeks various crashes when
running GDAL, in particular in OGRFeature::GetFieldAsString(). It has been
finally identified that it was due to stricter guard logic in GCC that was
enabled in Ubuntu 8.10 and later versions because -D_FORTIFY_SOURCE=2 is set
by default and is activated when -O is set to 2 or higher.
A similar issue was detected in DTEDDataset::CreateCopy() a few weeks ago and
was also fixed.

The fixes have been applied to current development version, 1.6 stable branch
and 1.5 branch. Please refer to http://trac.osgeo.org/gdal/ticket/2896 and
http://trac.osgeo.org/gdal/ticket/2824 if you need to apply the relevant
patches without waiting for next stable releases.

However, it might be possible that similar issues still remain, especially in
less popular drivers, so please report it.

Best regards,

Even
--- end citation -

I'm also a bit disappointed to see that such bugs are not reported to
GDAL trac and gdal-dev mailing list. It appears that Ubuntu 8.10 has
also had this problem and they did not properly report either... We,
upstream, are not always good at fixing bugs, but it is hard to fix
unreported bugs...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/344751/comments/6


** Changed in: gdal (Fedora)
   Importance: Unknown => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344751

Title:
  Disable stack protector for gdal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/344751/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 412922] Re: Gnome power manager dies when AC unplugged

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=459906.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-08-24T09:15:49+00:00 Edouard wrote:

Created attachment 314879
my dmesg

Description of problem:
Gnome-power-man applet disappear when removing AC. In dmesg the error is:
gnome-power-man[6470] general protection ip:4105c1 sp:7fff3726ec20 error:0 in 
gnome-power-manager[40+4b000]

Version-Release number of selected component (if applicable):
gnome-power-manager-2.23.6-1.fc10.x86_64

How reproducible:
static

Steps to Reproduce:
1. Log in with AC plugged
2. Unplug AC
3. Move the mouse cursor over the g-p-m applet to see how much battery left. 
After a couple of seconds the applet crashs.
  
Actual results:
General protection fault, g-p-m applet is dead.

Expected results:
Shouldn't crash of course. Should show the time remaining on battery.

Additional info:
After that some other applets seems to crash:
gpk-update-icon[6439] general protection ip:3b21c104a8 sp:7fffd1850e18 error:0 
in libpackagekit.so.4.0.0[3b21c0+24000]

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/412922/comments/0


On 2008-09-10T12:42:13+00:00 Richard wrote:

I'm guessing the problem is now fixed in rawhide?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/412922/comments/1


On 2008-09-11T07:47:58+00:00 Edouard wrote:

yes it's fixed in rawhide. You can close this bug. Thanks

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/412922/comments/2


** Changed in: gnome-power-manager (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/412922

Title:
  Gnome power manager dies when AC unplugged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/412922/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 384920] Re: iwconfig bitrate is not set properly

Launchpad has imported 62 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=469120.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-10-30T00:56:59+00:00 Gian wrote:

Description of problem:
When connecting to a security enabled network (WEP/WPA), the computer cannot 
stablish a connection using the right key and security protocol.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.11.svn4229.fc10.x86_64
wpa_supplicant-0.6.4-2.fc10.x86_64
kernel-2.6.27.4-58.fc10.x86_64


How reproducible:
Always, since last update.

Steps to Reproduce:
1. Try to establish a connection to a network with security enabled.
2. Enter the key according to the security protocol.
  
Actual results:
Connection fails

Expected results:
Establish a connection.

Additional info:
NetworkManager does not seem to store the right key or protocol in the 
connections when editing the stored connection settings. When attempting to 
connect dmesg shows this:

[dmesg]
wlan0: authenticate with AP 00:40:10:10:00:03
wlan0: authenticate with AP 00:40:10:10:00:03
wlan0: authenticated
wlan0: associate with AP 00:40:10:10:00:03
wlan0: RX AssocResp from 00:40:10:10:00:03 (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)
[/dmesg]

When negotiating, I can see both dots green, then the prmpt again.

Hardware: Realtek 8187B

Reply at: https://bugs.launchpad.net/ubuntu/+source/wireless-
tools/+bug/384920/comments/0


On 2008-11-01T16:25:51+00:00 Mark wrote:

I have a similar problem, only I can't connect to an unencrypted
network.

The last two kernels I've gotten from updates have been unable to
connect to the wireless network (2.6.27.4-58.fc10.i686 and
2.6.27.3-44.fc10.i686). The last one that worked was
2.6.27-0.352.rc7.git1.fc10.i686, which I am running now with no other
network-related problems.

Other packages:
NetworkManager-0.7.0-0.11.svn4229.fc10.i386
wpa_supplicant-0.6.4-2.fc10.i386

This machine uses an old Microsoft MN-520 wireless card which has worked
flawlessly on various linux distributions (including the last several
Fedora releases) for the last 4 years. It has an Orinoco chipset.

The end of my dmesg output:
eth2: no IPv6 routers present
fuse init (API version 7.9)
wifi0: CMD=0x0121 => res=0x7f, resp0=0x0004
wifi0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=127, rid=fc48, len=2)
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
eth2: Preferred AP (SIOCSIWAP) is used only in Managed mode when host_roaming 
is enabled
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:50:f2:72:bb:ba
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=00:50:f2:72:bb:ba
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:50:f2:72:bb:ba

ifup output:
# ifup wifi0
Error for wireless request "Set Mode" (8B06) :
SET failed on device eth2 ; Operation not supported.

Determining IP information for eth2...Nothing to flush.

Then it just hangs there until I hit ctrl-C, after which dmesg says

wifi0: LinkStatus: BSSID=00:50:f2:72:bb:ba
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:50:f2:72:bb:ba
wifi0: invalid skb->cb magic (0x0168, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x0168, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x0168, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x0168, expected 0xf08a36a2)

Reply at: https://bugs.launchpad.net/ubuntu/+source/wireless-
tools/+bug/384920/comments/1


On 2008-11-02T04:09:32+00:00 Gian wrote:

I should have mentioned that I don't seem to be able to connect to
unencrypted networks either. Just tried today at a local hotspot and
while getting very good signal readings in Fedora Rawhide (and confirmed
later in Vista), I couldn't connect to the network. Unencrypted network
connection negotiation takes longer than protected networks, and both
take a LONG time (1+ minute negotiation) before stating that the
connection couldn't be stablished, or prompting for the Network
passphrase/security token.

Reply at: https://bugs.launchpad.net/ubuntu/+source/wireless-
tools/+bug/384920/comments/2


On 2008-11-02T16:19:13+00:00 Mark wrote:

For what it's worth, I tried compiling and installing the vanilla
2.6.27.4 kernel, and t

[Bug 293484] Re: "New" Real Time Clock driver won't work on HP DL380 G4/G5

Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451188.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-06-13T09:57:21+00:00 shr wrote:

Description of problem:
Fedora 9 use the "new" Real Time Clock Driver (Device Drivers  ---> Real Time
Clock), but it don't work on HP DL380 G4/G5.
I don't know

Version-Release number of selected component (if applicable):
All the kernel released for Fedora 9 (kernel-2.6.25-14.fc9.x86_64 ~
kernel-2.6.25.4-30.fc9.x86_64)

How reproducible:
Install Fedora9 on HP DL380 G4/G5

Steps to Reproduce:
1. Just install Fedora9 on HP DL380 G4/G5
2.
3.
  
Actual results:
/dev/rtc0 won't be created.

Expected results:
/dev/rtc0 will be created and a symbolic link /dev/rtc will link to /dev/rtc0

Additional info:
It will work with "old" Real Time Clock driver, 
(Device Drivers  ---> Character devices  ---> Enhanced Real Time Clock Support
(and Generic /dev/rtc emulation) ).
If "new" Real Time Clock Driver won't work on HP DL380 G4/G5 even in the future,
could you please compile the "old" Real Time Clock driver as module?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293484/comments/0


On 2008-06-14T08:32:32+00:00 Chuck wrote:

Are there any error messages in the log about the driver not loading/working?
Does the output of 'lsmod' show it is loaded?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293484/comments/1


On 2008-06-16T06:28:02+00:00 shr wrote:

I don't know how to get the right information, could you please tell me what
information I can provide and how can I get it(what command should I execute) to
help solve this problem? 
It is ok If you need all the output of dmesg and lsmod. (about 578 + 48 lines)
Following is the information I can get.

Fedora 9 On HP DL380G4 (use new rtc driver and don't work)
# ls -al /dev/rtc*
ls: cannot access /dev/rtc*: No such file or directory

# dmesg | grep -i rtc


#lsmod | grep -i rtc


# clock --systohc --debug
hwclock from util-linux-ng 2.13.1
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.


Fedora 9 On IBM BladeCenter HS21 (use new rtc driver and working)
# ls -al /dev/rtc*
lrwxrwxrwx 1 root root  4 2008-06-16 22:07 /dev/rtc -> rtc0
crw-r--r-- 1 root root 254, 0 2008-06-16 22:07 /dev/rtc0

# dmesg | grep -i rtc
ACPI: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one year

#lsmod | grep -i rtc



Fedora 8 On HP DL380G4 (Use old char -> rtc and working)
# ls -alt /dev/rtc*
crw-r--r-- 1 root root 10, 135 2008-06-10 20:32 /dev/rtc

# dmesg | grep -i rtc


#lsmod | grep -i rtc



Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293484/comments/2


On 2008-08-14T04:17:36+00:00 shr wrote:

The same for HP DL 360G5, does HP use strange rtc chip on it's Server?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293484/comments/3


On 2008-09-04T19:23:18+00:00 Chuck wrote:

Please post the entire boot messages file (/var/log/dmesg) after booting
the broken kernel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293484/comments/4


On 2008-09-05T09:18:37+00:00 manuel wrote:

Although I'm not sure, I think the problem is that the HP servers are
not exporting the RTC via PNP.

>From ./drivers/rtc/rtc-cmos.c:
static const struct pnp_device_id rtc_ids[] = {
{ .id = "PNP0b00", },
{ .id = "PNP0b01", },
{ .id = "PNP0b02", },
{ },
};

# cat /sys/devices/pnp0/*/id
PNP0a03
PNP0c02
IPI0001
PNP0103
PNP0200
PNP0800
PNP0303
PNP0f13
PNP0f0e
PNP0a06
PNP0501
PNP0500



dmesg
storage1:~ # dmesg
Initializing cgroup subsys cpuset
Linux version 2.6.25.14-108.fc9.x86_64 (mockbuild@) (gcc version 4.3.0 20080428 
(Red Hat 4.3.0-8) (GCC) ) #1 SMP Mon Aug 4 13:46:35 EDT 2008
Command line: ro root=/dev/VolGroup00/LogVol00
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f400 (usable)
 BIOS-e820: 0009f400 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - cfe56000 (usable)
 BIOS-e820: cfe56000 - cfe5e000 (ACPI data)
 BIOS-e820: cfe5e000 - cfe5f000 (usable)
 BIOS-e820: cfe5f000 - d000 (reserve

[Bug 237443] Re: Crash during playback with CPU time limit error

** Changed in: pulseaudio (Fedora)
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/237443

Title:
  Crash during playback with CPU time limit error

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/237443/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 284994] Re: bluetooth-wizard unable to pair to fixed pin devices

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=472686.

On 2008-11-23T13:19:42+00:00 Jóhann wrote:

Description of problem:

Have been trying to connect a RIKALINE GPS Bluetooth dongle
and to do so I need to be able to enter the devices pin code
but when using the Bluetooth device wizard it detects the device
fine then it tries to pair with the devices with some random pin number it ask
me to enter a pin on the device ( for a split second ) the fails to connect

Now the problem here is on this particular device I cannot enter
a pin code I need to set the pin code manually on the client that is trying to
connect to the device to be able to pair with it.

I believe this causing a trouble for a lot of people since theres a lot of
devices out there that have a default pin of 1234 or etc...

[root@localhost bluetooth]# hcitool scan && hcitool inq
Scanning ...
00:00:00:00:54:4D Rikaline
Inquiring ...
00:00:00:00:54:4D clock offset: 0x75a1class: 0x00

The default pin is

Version-Release number of selected component (if applicable):

gnome-bluetooth-0.11.0-5.fc10.x86_64
gnome-bluetooth-libs-0.11.0-5.fc10.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Click the bluetooth icon
2. Setup new device
3.

Actual results:

The wizard fails to pair with device.

Expected results:

The wizard to be able to pair with the device
if it fails with a random pin then try common ones ( 1234 or etc ) if that
fails prompt the user to enter the pin then try to pair with it again.

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/87

On 2008-11-26T05:49:01+00:00 Bug wrote:

This bug appears to have been reported against 'rawhide' during the Fedora 10
development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/91

On 2009-02-23T23:23:47+00:00 Andrey wrote:

This seems to be upstream issue. Ubuntu 8.10 has the same issue:

https://bugs.launchpad.net/fedora/+source/bluez-gnome/+bug/284994

Upstream Gnome bug (with a bit hot discussion) posted here:

http://bugzilla.gnome.org/show_bug.cgi?id=560316

Follow-up in Gnome mailing list here:

http://thread.gmane.org/gmane.linux.bluez.kernel/717/focus=721

Does anybody (from Fedora developers) know if there are any [positive]
change ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/110

On 2009-02-25T09:06:43+00:00 Andrey wrote:

Some updates:

1. Upstream bugzilla has more than 20 bugs opened with requests to
support specific devices (including one from me personally):

http://bugzilla.gnome.org/buglist.cgi?product=bluez-
gnome&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&bug_status=UNCONFIRMED&component=wizard

2. Vincent Untz has proposed a patch to solve the issue here:

http://bugzilla.gnome.org/show_bug.cgi?id=570457

He also posted this patch in the mailing list:

http://article.gmane.org/gmane.linux.bluez.kernel/1399

I have not found any feedback so far (2 weeks away now) neither in
Bugzilla, nor in mailing list, nor in the code tree.

Jiri, can you please be so kind to discuss the issue with responsible
Gnome developer (Bastien Nocera) ? He seems to be a bit hard talking to
regular users, may be developer-to-developer discussion will be more
efficient ? Of course, if this is acceptable for you.

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/111

On 2009-02-25T11:38:04+00:00 Jiri wrote:

Hi, I take a look at this asap (tommorow probably) and try to come up
with some solution.

Jirka

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/112

On 2009-02-28T12:21:59+00:00 Andrey wrote:

Jiri, it seems that Bastien has made pretty substantial changes in the
upstream. I wonder what should be further steps with this bug - should
we wait until the next release of gnome-bluetooth ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez-
gnome/+bug/284994/comments/114

On 2009-03-04T16:11:56+

[Bug 220463] Re: unable to boot linux vm's that are not Debian derived.

Launchpad has imported 19 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=452355.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-06-21T09:43:23+00:00 Andy wrote:

Description of problem:

When installing fedora 9 64bit under KVM, the VM is created and the console
opens, and loads from the DVD, but at the boot: prompt the message "attempted
DOS system call" occurs.

If I select QEMU instead of KVM as the hypervisor, the installation does
continue past the boot: prompt.

Version-Release number of selected component (if applicable):

libvirt.x86_64   0.4.3-1.fc10   installed
libvirt-python.x86_640.4.3-1.fc10   installed
python-virtinst.noarch   0.300.3-7.fc9  installed
virt-manager.x86_64  0.5.4-4.fc9installed

How reproducible:
100%

Steps to Reproduce:
1. create new VM
2. installation source /dev/sr0

Additional info:

N.B I had to install libvirt 0.4.3 from rawhide to work around problem
with

libvirtError: virDomainCreateLinux() failed internal error Timed out while
reading monitor startup output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/11


On 2008-07-08T02:54:15+00:00 Jonathan wrote:

Created attachment 311221
Screenshot of issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/12


On 2008-07-08T02:55:47+00:00 Jonathan wrote:

/usr/bin/qemu-kvm -S -M pc -m 512 -smp 1 -name f9testlvm -monitor pty -boot c
-drive file=/home/jon/f9testlvm.img,if=ide,index=0,boot=on -drive
file=/home/jon/Downloads/Fedora-9-x86_64-netinst.iso,if=ide,media=cdrom,index=2
-net nic,macaddr=00:16:3e:2e:7b:73,vlan=0 -net
tap,fd=13,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc
127.0.0.1:0 -k en-us

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/13


On 2008-07-08T08:23:30+00:00 Martin wrote:

Seen on f9 32bit.

Fails with libvirt-0.4.4-1.fc9.i386.rpm  libvirt-
python-0.4.4-1.fc9.i386.rpm

Reverting to libvirt-0.4.2-3.fc9.i386.rpm  libvirt-python-0.4.2-3.fc9.i386.rpm 
removes the problem


Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/14


On 2008-07-08T08:26:30+00:00 Daniel wrote:

This is a KVM bug when using the -drive parameter

The following two commands should be identical:

# qemu-kvm -cdrom /home/berrange/boot.iso -boot d -m 500

# qemu-kvm -drive
file=/home/berrange/boot.iso,if=ide,media=cdrom,index=2,boot=on -m 500

But the 2nd fails with 'Attempted DOS system call'. New libvirt uses the -drive
argument, hence why you see it the problem with newer libvirt. 

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/15


On 2008-07-08T09:34:45+00:00 Daniel wrote:

Upstream thread shows that boot=on doesn't work reliably with CDROMs

http://thread.gmane.org/gmane.comp.emulators.kvm.devel/19242

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/16


On 2008-07-08T11:51:15+00:00 Daniel wrote:

Please try using this libvirt scratch build and tell me if CDROM booting
works

http://koji.fedoraproject.org/koji/taskinfo?taskID=702183

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/17


On 2008-07-08T11:52:35+00:00 Daniel wrote:

Oh, don't forget to do 'service libvirtd restart' after installing the scratch
RPM to make sure it uses the new code. NB this will terminate all active guests,
so you might want to shut them down cleanly before this.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/18


On 2008-07-08T12:05:28+00:00 Martin wrote:

Test packages seem to allow a CD/DVD boot.


Reply at: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/19


On 2008-07-08T15:45:23+00:00 Fedora wrote:

libvirt-0.4.4-2.fc9 has been submitted as an update for Fedora 9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/220463/comments/20


On 2008-07-08T20:08:31+00:00 Andy

[Bug 237001] Re: Java applet not initialized in Firefox 3 RC1

Launchpad has imported 27 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=520777.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-09-02T10:36:26+00:00 Klaas wrote:

Description of problem:
When I try to start my typingcourse with Firefox I get the message: Applet not 
initialized

Version-Release number of selected component (if applicable):
Firefox 3.5.2

How reproducible:
See below.

Steps to Reproduce:
1. Go to: http://online3.typingmaster.com/tmonline3/login?id=unp5pb2f9
2. login with user 'test' and password 'geheim01' (just a trial-user  ;-)  )
3. try to start the first lesson of the typing course
  
Actual results:
'Applet not initialized'

Expected results:
I expect to see the lessons.. (It worked fine under Fedora 9)

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/icedtea-
gcjwebplugin/+bug/237001/comments/7


On 2009-09-02T10:38:27+00:00 Klaas wrote:

Created attachment 359502
Screenprint with text 'Applet not initialized'

Reply at: https://bugs.launchpad.net/ubuntu/+source/icedtea-
gcjwebplugin/+bug/237001/comments/8


On 2009-09-07T15:31:48+00:00 Matěj wrote:

Shouldn't this go to Java component? Reassigning for further
investigation.

Reply at: https://bugs.launchpad.net/ubuntu/+source/icedtea-
gcjwebplugin/+bug/237001/comments/9


On 2009-09-07T16:57:50+00:00 Mark wrote:

Confirmed, starting firefox from a terminal produces:

net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not 
initialize applet.
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:495)
at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:441)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:620)
Caused by: java.lang.NullPointerException
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:481)
... 2 more
Caused by: 
java.lang.NullPointerException
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:481)
at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:441)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:620)
java.lang.NullPointerException
at net.sourceforge.jnlp.NetxPanel.runLoader(NetxPanel.java:102)
at sun.applet.AppletPanel.run(AppletPanel.java:380)
at java.lang.Thread.run(Thread.java:636)
java.lang.NullPointerException
at sun.applet.AppletPanel.run(AppletPanel.java:430)
at java.lang.Thread.run(Thread.java:636)

with java-1.6.0-openjdk-plugin-1.6.0.0-27.b16.fc11.x86_64

Reply at: https://bugs.launchpad.net/ubuntu/+source/icedtea-
gcjwebplugin/+bug/237001/comments/10


On 2009-10-18T14:16:08+00:00 Juha wrote:

I see the same:

ICEDTEAPLUGIN_DEBUG=true firefox \
http://www.java.com/en/download/help/testvm.xml \
2>&1 | tee console.log

Writing to JVM: plugin PluginCookieInfo 
http://www.java.com/applet/testVM_en_US.properties 
gpName=javac%3ASupport%3AHelp%3Atestvm.xml; gpChannel=javac%3ASupport%3AHelp; 
gpServer=www.java.com; JSESSIONID=7f0c2885e168c0c256760463e922; s_cc=true; 
s_sq=%5B%5BB%5D%5D
Wrote 247 bytes to pipe
ICEDTEA PLUGIN: Instance::SendMessageToAppletViewer return
Processing complete
ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM return
ICEDTEA PLUGIN: plugin_in_pipe_callback
Received message: instance 1 status exception: 
java.lang.StringIndexOutOfBoundsException: String index out of range: 8.
  PIPE: plugin read: instance 1 status exception: 
java.lang.StringIndexOutOfBoundsException: String index out of range: 8.
ICEDTEA PLUGIN: plugin_in_pipe_callback return
ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM
received message: instance 1 status exception: 
java.lang.StringIndexOutOfBoundsException: String index out of range: 8.
Processing complete
ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM return
Pending event processed (this) ... 1
ICEDTEA PLUGIN: plugin_in_pipe_callback
Received message: instance 1 status Start: applet not initialized.
  PIPE: plugin read: instance 1 status Start: applet not initialized.
ICEDTEA PLUGIN: plugin_in_pipe_callback return
ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM
received message: instance 1 status Start: applet not initialized.
Processing complete
ICEDTEA PLUGIN: Instance::ConsumeMsgFromJVM return
Pending event processed (this) ... 1
^C

Should i attach the whole log here?

Reply at: https://bugs.launchpad.net/ubuntu/+source/icedtea-
gcjwebplugin/+bug/237001/comments/11

-

[Bug 248509] Re: Hardy CPU physical hot plugging is broken

Launchpad has imported 23 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=448588.

On 2008-05-27T18:19:14+00:00 Alok wrote:

Description of problem:

There have been a series of patches committed to the mainline kernel
recently that address a performance issue for gettimeofday when running
on hypervisors that enable hardware assisted virtualization. The
non-ideal performance occurs because a CPUID instruction is used to
serialize the pipeline before RDTSC, and when using hardware
virtualization, CPUID always exits to the hypervisor.

The code in question also exists in the RHEL 5.2 64-bit kernel (see
get_cycles_sync in include/asm-x86_64/timex.h).

The fix is to use MFENCE/LFENCE instead of CPUID. Here are links to
relevant patches by Andi Kleen which are now in git:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=de4218634e3df6d73a3e6cdfdf3a17fa3bc7e013
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=707fa8ed923b1b6a3d7af0d386b0b3abad28ed19
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fde1b3fa947c2512e3715962ebb1d3a6a9b9bb7d
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6d63de8dbcda98511206897562ecfcdacf18f523
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f06e4ec1c15691b0cfd2397ae32214fa36c90d71

Would you be able to make a similar change to the RHEL 5.2 kernel, to
address this issue ?

Thanks,
Alok

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/248509/comments/0

On 2008-07-31T10:14:11+00:00 C. wrote:

(In reply to comment #0)

We're also seeing this problem - a little test script (doing 90,000,000
gettimeofday() calls) takes two minutes on our RH VMs... and thirty seconds on
my desktop.

Applying that kernel patch to the RH kernel isn't trivial - there have been a
*lot* of changes since 2.6.18 was cut. I'm giving it a go here, but I'm not
really a kernel coder.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/248509/comments/4

On 2008-08-27T10:55:10+00:00 Jon wrote:

Currently this appears to be an issue with 64 bit architectures and the
implementation behind the syscalls within the xen kernel in the VM and the way
they all exit the vm to the hypervisor. Is this related to not taking advantage
of segmentation protection?

#include

int main(int argc,char **argv) {

int i;
for ( i = 0 ; i < 9000 ; i++ ) {
gettimeofday();

}

32 bit VM:
time ./time

real 1m42.460s
user 0m8.565s
sys 1m33.834s

64-bit VM:
time ./time_64

real 6m3.259s
user 0m26.750s
sys 5m36.501s

Not 100% sure on a gettimeofday why it requires to exit out of the VM
completely? Is it not possible to take advantage of the generic 'vsyscalls'
implementation which is in the 2.6.x branches?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/248509/comments/5

On 2008-09-03T11:03:33+00:00 Prarit wrote:

*** Bug 460983 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/248509/comments/6

On 2008-09-03T15:33:33+00:00 Chris wrote:

Well, I think there are actually two things at play in this BZ. The
original request is to shift from using CPUID to serialize gettimeofday
to using MFENCE/LFENCE for serializing. This should be faster under
*full* virtualization, so a backport to RHEL-5 might be desirable.

Comment #3, however, talks about something different. In particular,
it's talking about the Xen kernel, which does indeed have the vsyscall
stuff off in 64-bit. I'm not entirely sure why; I don't think
segmentation protection should have anything to do with it. In a quick
test, I turned it on, and your little benchmark there went from 2m17s on
this box to about 30s. I'm going to make a new BZ about that issue,
since it doesn't really belong here.

Chris Lalancette

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/248509/comments/7

On 2008-10-22T16:57:36+00:00 Alok wrote:

(In reply to comment #4)
> Well, I think there are actually two things at play in this BZ. The original
> request is to shift from using CPUID to serialize gettimeofday to using
> MFENCE/LFENCE for serializing. This should be faster under *full*
> virtualization, so a backport t

[Bug 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check