date:20171027

** Changed in: gnome-settings-daemon (Fedora)
   Status: Unknown => Won't Fix

** Changed in: gnome-settings-daemon (Fedora)
   Importance: Unknown => Undecided

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

Title:
  "slow keys" can turn on surreptitiously & cause confusion.

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

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

[Bug 886820] Re: [Kubuntu 11.10] Screen brightness control does not work on Samsung RV511 laptop

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

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 2012-02-23T11:00:12+00:00 carasin wrote:

Description of problem:

There is a laptop Samsung RV520 with installed Fedora 16. Some hotkeys (Fn + 
) don't work, e.g. [Fn + Up/Down] (backlight brightness control), [Fn + 
F5] (display backlight off/on), [Fn + F9] (wireless devices on/off). At the 
same time, hotkeys [Fn + Esc] (suspend), [Fn + Right/Left] (volume level 
up/down) and [Fn + F6] (volume off/on) work fine.
 shows that  module isn't loaded. Attempt to load this 
module fails with error "No such device".
When I press [Fn + Up/Down], the contents of the files (, 
) at the path 
 
change. But actually brightness level doesn't change.
___

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

kernel-3.1.0-7.fc16.i686 / kernel-3.2.6-3.fc16.i686, udev-173-3.fc16.i686
___

How reproducible:
always
___

Steps to Reproduce:
1. Press [Fn + Up/Down/F9] (Samsung RV520, Fedora 16)
2. Backlight level doesn't change, wireless devices don't switch
___

Actual results:
Some [Fn + ] hotkeys don't work.
___

Expected results:
All [Fn + ] hotkeys (e.g. brightness control and wireless devices on/off) 
work fine.

Additional info:
 command returns 
.
The passing the

[Bug 370675] Re: No easy way to have a fully free install

** Changed in: fedora
   Status: Unknown => Won't Fix

** Changed in: 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/370675

Title:
  No easy way to have a fully free install

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

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

[Bug 915037] Re: zim crashed with ValueError in select_page(): invalid tree path

** Changed in: fedora
   Status: Unknown => Fix Released

** Changed in: 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/915037

Title:
  zim crashed with ValueError in select_page(): invalid tree path

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

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

[Bug 920454] Re: juju bootstrap hangs for local environment under precise on vmware

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

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 2012-02-22T21:55:47+00:00 Matt wrote:

Created attachment 565119
gdb backtrace of virsh

Description of problem:
Using FC16 as VMware Workstation 8 guest with Intel VT-x virtualisation so that 
I can test KVM.  When installing libvirt & qemu-kvm I am unable to connect to 
the local hypervisor with virsh (or virt-manager for that matter).

Running fallback Gnome desktop environment and latest updates

Have tried disabling auth (set to none) in the libvirtd.conf and
disabling selinux (setenforce 0).  Also tried with std user & root user.

Version-Release number of selected component (if applicable):
* FC16 stock with all updates (also tested with testing updates)
* Kernel 3.2.6-3.fc16.x86_64
* libvirt 0.9.6-4.fc16

How reproducible:
Have reproduced on another system, using fresh FC16 install as VMware 
Workstation 8 guest.  Same results.

Steps to Reproduce:
1. Install FC16 as VMware guest with Intel VT-x virtualisation
2. Install qemu-kvm & libvirt
3. Type qemu --connect qemu:///system

  
Actual results:
Process hangs until ^C

Expected results:
Virsh prompt connected to local hypervisor


Additional info:
In the hope that it is useful, I have attached a gdb backtrace while it is 
hanging.  I ran debuginfo-install libvirt then:

virsh --connect qemu:///system &
gdb
attach [processid]
backtrace
See attachment for backtrace

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/1


On 2012-02-22T22:03:43+00:00 Dave wrote:

Can you provide a backtrace of all the libvirtd threads with bt -a when
this problem is occurring?

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/2


On 2012-02-22T22:05:07+00:00 Cole wrote:

And when you reproduce the hang, is dmidecode running?

ps axwww | grep dmide

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/3


On 2012-02-22T22:18:23+00:00 Matt wrote:

Hi,

1. Attachment created: backtrace of libvirtd attached
I did not fully understand your instructions, I hope this is the information 
that you require, let me know if there's anything more that you want - the gdb 
commands that I used are in the attachment,

2. Results of ps axwww | grep dmide:

1484 ?S  0:00 /usr/sbin/dmidecode -q -t 0,1,4,17

Matt

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/4


On 2012-02-22T22:19:31+00:00 Matt wrote:

Created attachment 565125
libvirtd backtrace (all threads)

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/5


On 2012-02-22T22:25:47+00:00 Cole wrote:

Yeah I've heard of this issue before, the dmidecode hang in vmware
guests. I think there's a patch upstream for it

Eric, do you know more about this?

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/6


On 2012-02-22T22:30:44+00:00 Dave wrote:

Matt, that's what I was looking for.  I have the same thought Cole did
which is that this is dmidecode related.

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/7


On 2012-02-22T22:33:45+00:00 Dave wrote:

Are you willing to try building upstream libvirt to see if it makes the
problem go away?  I'm not convinced it's fixed upstream yet, but if you
can repro this at will and test builds I'm sure we can figure it out.

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/8


On 2012-02-22T22:37:07+00:00 Matt wrote:

Sure Dave.  Can you provide me some high-level instructions, or point me
to a site that might have something similar?

Thanks,

Matt

Reply at: https://bugs.launchpad.net/pyjuju/+bug/920454/comments/9


On 2012-02-22T22:50:36+00:00 Eric wrote:

bug 783453 is another example of a dmidecode hang; F16 does not (yet)
have the two patches mentioned in that bug:

commit 06b9c5b9231ef4dbd4b5ff69564305cd4f814879
Author: Michal Privoznik 
Date:   Tue Jan 3 18:40:55 2012 +0100

virCommand: Properly handle POLLHUP

It is a good practise to set revents to zero before doing any poll().

[Bug 915173] Re: soffice.bin crashed after entering chars using ibus-chewing

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

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 2012-03-03T16:58:24+00:00 Cheng-Chia wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --writer 
--splash-pipe=7
crash_function: SwViewImp::PaintLayer
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.2.7-1.fc16.x86_64
pid:2469
pwd:/home/realplus
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed 
by signal 11 (SIGSEGV)
time:   西元2012年03月03日 (週六) 22時49分36秒
uid:1000
username:   realplus
xsession_errors: 

backtrace:  Text file, 55881 bytes
dso_list:   Text file, 19994 bytes
maps:   Text file, 79246 bytes
smolt_data: Binary file, 2916 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=HiHeHo-S205
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GIO_LAUNCHED_DESKTOP_FILE_PID=2458
:GPG_AGENT_INFO=/tmp/keyring-nCFoPC/gpg:0:1
:SHELL=/bin/bash
:TERM=dumb
:DESKTOP_STARTUP_ID=gnome-shell-1478-HiHeHo-S205-libreoffice-2_TIME938020
:HISTSIZE=1000
:XDG_SESSION_COOKIE=f01d1509c87b498c5f6afb820011-1330785281.685158-1562711213
:GJS_DEBUG_OUTPUT=stderr
:OLDPWD=/usr/lib64/libreoffice/program
:GNOME_KEYRING_CONTROL=/tmp/keyring-nCFoPC
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:IMSETTINGS_MODULE=IBus
:USER=realplus
:SSH_AUTH_SOCK=/tmp/keyring-nCFoPC/ssh
:USERNAME=realplus
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1270,unix/unix:/tmp/.ICE-unix/1270
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/libreoffice-writer.desktop
:MAIL=/var/spool/mail/realplus
:PATH=/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/realplus/.local/bin:/home/realplus/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/realplus
:XMODIFIERS=@im=ibus
:KDE_IS_PRELINKED=1
:GNOME_KEYRING_PID=1266
:LANG=zh_TW.utf8
:GDM_LANG=zh_TW.utf8
:KDEDIRS=/usr
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/realplus
:XDG_SEAT=seat0
:SHLVL=1
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SAL_ENABLE_FILE_LOCKING=1
:LOGNAME=realplus
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-byxwqDMbCA,guid=44acabacb82f64ac946f2ed10044
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/realplus
:DISPLAY=:0
:CCACHE_HASHDIR=
:XAUTHORITY=/var/run/gdm/auth-for-realplus-WEJbpk/database
:LD_LIBRARY_PATH=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/client:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/native_threads:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64

var_log_messages:
:Feb 28 22:12:23 HiHeHo-S205 kernel: [24034.753725] soffice.bin[4998]: segfault 
at 0 ip 003625c3b311 sp 7fffc7a101d0 error 6 in 
libuno_sal.so.3[3625c0+57000]
:Feb 28 22:12:27 HiHeHo-S205 abrt[9456]: Saved core dump of pid 4998 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-02-28-22:12:24-4998 (162369536 bytes)
:Feb 28 22:35:22 HiHeHo-S205 kernel: [25412.904196] soffice.bin[9502] general 
protection ip:3625c3b160 sp:7fffa677fa20 error:0 in 
libuno_sal.so.3[3625c0+57000]
:Feb 28 22:35:24 HiHeHo-S205 abrt[11526]: Saved core dump of pid 9502 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-02-28-22:35:22-9502 (130383872 bytes)
:Feb 28 23:22:15 HiHeHo-S205 kernel: [28225.956775] soffice.bin[11587]: 
segfault at a20 ip 0030f509bd53 sp 7fff7beb0d80 error 4 in 
libX11.so.6.3.0[30f500+139000]
:Feb 28 23:22:17 HiHeHo-S205 abrt[14599]: Saved core dump of pid 11587 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-02-28-23:22:15-11587 (120573952 bytes)
:Mar  2 01:37:35 HiHeHo-S205 kernel: [ 5635.377290] soffice.bin[7328] general 
protection ip:3625c3b160 sp:7fff4abdc7d0 error:0 in 
libuno_sal.so.3[3625c0+57000]
:Mar  2 01:37:37 HiHeHo-S205 abrt[9803]: Saved core dump of pid 7328 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-03-02-01:37:35-7328 (106672128 bytes)
:Mar  3 22:49:36 HiHeHo-S205 kernel: [  963.258543] soffice.bin[2469] general 
protection ip:7fa238e9c3fc sp:7fff4e933990 error:0 in 
libswlx.so[7fa238748000+bd7000]
:Mar  3 22:49:37 HiHeHo-S205 abrt[2563]: Saved core dump of pid 2469 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-03-03-22:49:36-2469 (95752192 bytes)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915173/comments/6


On

[Bug 929378] Re: [power]: gnome-control-center crashed with SIGSEGV in got_power_proxy_cb()

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

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 2012-04-07T17:21:47+00:00 Anthony wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:gnome-control-center power
comment:This problem appears while the update process.
crash_function: got_power_proxy_cb
executable: /usr/bin/gnome-control-center
kernel: 3.1.0-7.fc16.i686
pid:2325
pwd:/home/liveuser
reason: Process /usr/bin/gnome-control-center was killed by signal 11 
(SIGSEGV)
smolt_data: Unable to save UUID to /etc/smolt/hw-uuid.  Please run once as 
root.
time:   sam. 07 avril 2012 18:58:02 CEST
uid:1000
username:   liveuser
var_log_messages: Apr  7 18:58:21 localhost abrt[2333]: Saved core dump of pid 
2325 (/usr/bin/gnome-control-center) to 
/var/spool/abrt/ccpp-2012-04-07-18:58:02-2325 (35676160 bytes)
xsession_errors: (gnome-control-center:2325): GLib-GObject-WARNING **: invalid 
cast from `(null)' to `CcPowerPanel'

backtrace:  Text file, 24841 bytes
dso_list:   Text file, 25288 bytes
maps:   Text file, 48178 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=1
:HOSTNAME=localhost.localdomain
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=495788586481488e27d23a810010-133387.304575-1370187989
:IMSETTINGS_MODULE=none
:USER=liveuser
:USERNAME=liveuser
:MAIL=/var/spool/mail/liveuser
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/liveuser/.local/bin:/home/liveuser/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/liveuser
:XMODIFIERS=@im=none
:LANG=fr_FR.utf8
:GDM_LANG=fr_FR.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/liveuser
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=liveuser
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-1NHPl5Nbnt,guid=08534546278c0afee139653e0056
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/liveuser
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-liveuser-WGn5Nc/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1056,unix/unix:/tmp/.ICE-unix/1056
:GNOME_KEYRING_CONTROL=/tmp/keyring-5wOdEP
:SSH_AUTH_SOCK=/tmp/keyring-5wOdEP/ssh
:GPG_AGENT_INFO=/tmp/keyring-5wOdEP/gpg:0:1
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:DESKTOP_STARTUP_ID=gnome-shell-1321-localhost.localdomain-gnome-control-center-7_TIME2923369
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/gnome-power-panel.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=2325

event_log:
:2012-04-07-19:01:28> Interrogation des paramètres de serveur
:2012-04-07-19:01:30  Préparation de l'archive à envoyer
:2012-04-07-19:01:37  Envoi de 2 mégaoctets
:2012-04-07-19:01:47  Transfert en cours 32%
:2012-04-07-19:01:57  Transfert en cours 67%
:2012-04-07-19:02:05  Transfert réussi
:2012-04-07-19:02:07  Le travail de retrace a commencé
:2012-04-07-19:02:18  Analyzing crash data
:2012-04-07-19:02:29  Analyzing crash data
:2012-04-07-19:02:40  Analyzing crash data
:2012-04-07-19:02:51  Initializing virtual root
:2012-04-07-19:03:02  Initializing virtual root
:2012-04-07-19:03:13  Initializing virtual root
:2012-04-07-19:03:24  Initializing virtual root
:2012-04-07-19:03:35  Initializing virtual root
:2012-04-07-19:03:46  Initializing virtual root
:2012-04-07-19:03:57  Initializing virtual root
:2012-04-07-19:04:08  Initializing virtual root
:2012-04-07-19:04:19  Initializing virtual root
:2012-04-07-19:04:30  Initializing virtual root
:2012-04-07-19:04:41  Initializing virtual root
:2012-04-07-19:04:52  Initializing virtual root
:2012-04-07-19:05:03  Initializing virtual root
:2012-04-07-19:05:13  Initializing virtual root
:2012-04-07-19:05:24  Initializing virtual root
:2012-04-07-19:05:35  Initializing virtual root
:2012-04-07-19:05:46  Initializing virtual root
:2012-04-07-19:05:57  Initializing virtual root
:2012-04-07-19:06:08  Initializing virtual root
:2012-04-07-19:06:19  Initializing virtual root
:2012-04-07-19:06:30  Initializing virtual root
:2012-04-07-19:06:41  Initializing virtual root
:2012-04-07-19:06:52  Initializing virtual root
:2012-04-07-19:07:03  Initializing virtual root
:2012-04-07-19:07:13  Initializing virtual root
:2012-04-07-19:07:24  Initializing virtual root
:2012-04-07-19:07:35  Initializing virtual root
:2012-04-07-19:07:46  Initializing virtual root
:2012-04-07-19:07:57  Initializing virtual root
:2012-04-07-19:08:08  Initializing virtual root
:2012-04-07-19:08:19  Initializing virtual root
:2012-04-07-19:08:29  Initializing virtual root
:2012-04-07-19:08:40  Initializing

[Bug 931542] Re: using the gcc-4.7.0 prerelease as packaged by Fedora Rawhide, there is a segfault in the program that results from compiling sha512-hash.c

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

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 2012-02-13T17:06:33+00:00 Zooko wrote:

This program (pycryptopp) segfaults when compiled on Rawhide, but not on
several other platforms. I've reported the issue on the gcc tracker,
here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52236 The issue was
originally noticed in the pycryptopp project, here: https://tahoe-
lafs.org/trac/pycryptopp/ticket/80 The pycryptopp buildbot reliably
reproduces the segfault on Rawhide and the lack of segfault on several
other systems.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/931542/comments/2


On 2012-02-13T17:17:41+00:00 Zooko wrote:

I opened a ticket on launchpad.net with which to track the progress of
this issue across multiple other issue trackers: pycryptopp, GCC,
Fedora, and possibly DJB's "nacl" crypto library if there is any way to
track such issues other than emailing the author.
https://bugs.launchpad.net/pycryptopp/+bug/931542

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/931542/comments/5


On 2012-02-14T16:33:20+00:00 Jakub wrote:

You've filed lots of bugreports, but haven't provided easy steps how to
reproduce, what exactly when built with gcc 4.7 fails, what (if possible
minimal) command to reproduce it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/931542/comments/7


On 2012-02-14T19:03:37+00:00 Zooko wrote:

By the way, I don't know for sure that this is a bug in
gcc-4.7.0-prerelease. It could also be a bug in our code which is
uncovered by a recent change in gcc, for example. I do know that the
same segfault doesn't happen on the other buildbots, none of which have
gcc >= 4.7.0-prerelease.

I can explain how to reproduce it, but I can't conveniently generate a
minimal case, since I don't currently have access to system (e.g.
Rawhide) with gcc-4.7.0-prerelease on.

To reproduce (not minimally):

git checkout git://github.com/tahoe-lafs/pycryptopp.git
cd pycryptopp
git reset --hard 36a666d4514e21a71c934bcfc62438b8bab97f32

# Note that an equivalent git checkout is done automatically by the
buildbot. The exact command-line, environment, and stdout+stderr are
logged, e.g. here: https://tahoe-lafs.org/buildbot-
pycryptopp/builders/Ruben%20Fedora/builds/49/steps/git/logs/stdio

python setup.py build --test-double-load

# This builds the C and C++ modules. I would assume that the option
--test-double-load to the command-line is irrelevant to this bug (it
causes another module to be built which isn't used by the program which
segfaults). Here's a log of the buildbot executing this step and the
resulting output: https://tahoe-lafs.org/buildbot-
pycryptopp/builders/Ruben%20Fedora/builds/49/steps/compile/logs/stdio

valgrind --error-exitcode=1 --log-file=valgrind.log.txt
--suppressions=misc/coding_helpers/python.supp --gen-suppressions=all
python setup.py test

# This runs the pycryptopp unit tests, which trigger the segfault. Here's a log 
of the command-line, env var, and stdout+stderr of buildbot executing this 
step: 
https://tahoe-lafs.org/buildbot-pycryptopp/builders/Ruben%20Fedora/builds/49/steps/test%20valgrind/logs/stdio
# Here's the valgrind log file that results from that command-line as executed 
by the buildbot: 
https://tahoe-lafs.org/buildbot-pycryptopp/builders/Ruben%20Fedora/builds/49/steps/test%20valgrind/logs/valgrind

# By the way, here is some information about the system on which that buildbot 
test runs:
# 
https://tahoe-lafs.org/buildbot-pycryptopp/buildslaves/buildbot.rubenkerkhof.com
# 
https://tahoe-lafs.org/buildbot-pycryptopp/builders/Ruben%20Fedora/builds/49/steps/show-tool-versions/logs/stdio

If I were going to minimize this, I would start by looking at the Python
unit test which reliably executes, the bug:
pycryptopp.test.test_ed25519.Basic.test_OOP . First I would run that
test alone and not the other tests, by changing "python setup.py test"
to "python setup.py test -s
pycryptopp.test.test_ed25519.Basic.test_OOP", just to be sure the other
tests running doesn't change the behavior. If it doesn't, then I would
add some debug print statements in the source code of test_OOP:
https://github.com/tahoe-
lafs/pycryptopp/blob/36a666d4514e21a71c934bcfc62438b8bab97f32/pycryptopp/test/test_ed25519.py#L124
to see which of its calls to ed25519, and with what arguments, triggers
the segfault. Then I would write equivalent C code and see if that
triggers

[Bug 929128] Re: deja-dup backup window is white on lightgrey, white text on white background in details

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

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 2012-05-03T12:14:54+00:00 Branislav wrote:

Created attachment 581845
On left screen is F17 TC2 and on right screen is F16 for comparison.

Description of problem:
  Backup connection window fonts are not readable.

Version-Release number of selected component (if applicable):
  deja-dup-20.2-2.fc17.x86_64

How reproducible:
  always

Steps to Reproduce:
  1. Open deja-dup (Backup from activities)
  2. Select - Backup now
  3. New window appears
  
Actual results:
  Fonts are not readable. They have white color on grey background.

Expected results:
  Readable font.

Additional info:
  Screenshot attached.

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/9


On 2012-05-03T14:59:34+00:00 Michael wrote:

This is upstream bug https://bugs.launchpad.net/deja-dup/+bug/929128

Which is really GTK+_bug
https://bugzilla.gnome.org/show_bug.cgi?id=670018

But this was worked around in deja-dup 22.0.  You should really use the
latest stable version, 22.1!

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/10


On 2012-06-17T03:44:26+00:00 Ankur wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/11


On 2012-06-17T03:47:26+00:00 Ankur wrote:

Issue persists on:

deja-dup-20.2-2.fc17.x86_64

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/12


On 2012-09-07T09:18:11+00:00 Michal wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/14


On 2012-09-13T17:31:56+00:00 Paul wrote:

Three months without any response?

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/15


On 2012-09-13T21:43:05+00:00 Chris wrote:

This is only a problem for me if I use Adwaita GTK+ theme. Switching to
another theme such as Elementary or one that's contrasted the text is
readable.

Although Michael wrote in upstream ticket:
"Turns out this is a bug in light-themes, not GTK+. Adwaita does the right 
thing. See https://bugzilla.gnome.org/show_bug.cgi?id=670018 for a test program 
and reproduction steps."

Rawhide has the same problem as it's only a minor release.

I did a test build of latest stable 22.1 from 2012-04-16 and the problem
no-longer exists. We might need to do a new major version bump for f17.

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/16


On 2013-04-24T20:01:20+00:00 Rahul wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/18


On 2013-04-24T20:16:44+00:00 Rahul wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/19


On 2013-04-24T20:18:54+00:00 Fedora wrote:

deja-dup-22.1-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/deja-dup-22.1-1.fc17

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/20


On 2013-04-26T01:00:50+00:00 Fedora wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/929128/comments/21


On 2013-07-04T07:01:50+00:00 Fedora wrote:

[Bug 964796] Re: wallpaper drawing is shifted for some seconds at gnomeshell starting up

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

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 2012-04-01T14:49:39+00:00 Jonathan wrote:

Created attachment 574335
screen shot of the upper left corner of my screen

When I restart gnome-shell with Alt-F2 r, my desktop "shifts" down and
to the right. Check out the attached screen shot of the upper left
corner of my screen after a restart.

I suspected this might be due to the fact that I had the dock extension
enabled, but I disabled it and the problem didn't go away. Might it have
something to do with the fact that I have two monitors?

Note that if I restart multiple times, it does not shift further and
further; it only shifts as far as shown above.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/964796/comments/3


On 2012-04-03T00:37:53+00:00 Matthias wrote:

Sounds more like a gnome-shell (or mutter) issue than a nautilus issue

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/964796/comments/4


On 2012-04-05T18:40:00+00:00 Owen wrote:

I added a patch to the upstream bug

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/964796/comments/5


On 2012-04-05T19:34:29+00:00 Owen wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/964796/comments/6


On 2012-04-05T19:38:36+00:00 Owen wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/964796/comments/7


On 2012-04-19T17:22:33+00:00 Owen wrote:

Fixed by Mutter update in
https://admin.fedoraproject.org/updates/FEDORA-2012-6123/aisleriot-3.2.3.2-2.fc17
,at-
spi2-core-2.4.1-1.fc17,baobab-3.4.1-1.fc17,brasero-3.4.1-1.fc17,cheese-3.4.1-1.fc17
,control-
center-3.4.1-1.fc17,devhelp-3.4.1-1.fc17,empathy-3.4.1-1.fc17,eog-3.4.1-1.fc17
,file-
roller-3.4.1-1.fc17,folks-0.6.9-1.fc17,gcalctool-6.4.1.1-1.fc17,gcr-3.4.1-1.fc17,gedit-3.4.1-1.fc17
,glib-networking-2.32.1-1.fc17,gnome-applets-3.4.1-1.fc17,gnome-
backgrounds-3.4.1-1.fc17,gnome-boxes-3.4.1-1.fc17,gnome-
desktop3-3.4.1-2.fc17,gnome-devel-docs-3.4.1-1.fc17,gnome-
documents-0.4.1-1.fc17,gnome-games-3.4.1-1.fc17,gnome-
keyring-3.4.1-1.fc17,gnome-online-accounts-3.4.1-1.fc17,gnome-
panel-3.4.1-1.fc17,gnome-screenshot-3.4.1-1.fc17,gnome-
session-3.4.1-1.fc17,gnome-shell-3.4.1-2.fc17,gnome-system-
monitor-3.4.1-1.fc17,gnome-terminal-3.4.1.1-1.fc17,gnome-user-
docs-3.4.1-1.fc17,gtksourceview3-3.4.1-1.fc17,gucharmap-3.4.1.1-1.fc17,gvfs-1.12.1-2.fc17,libgdata-0.12.0-1.fc17
,libgnome-
keyring-3.4.1-2.fc17,librsvg2-2.36.1-1.fc17,libsoup-2.38.1-1.fc17,mutter-3.4.1-2.fc17,orca-3.4.1-2.fc17,sushi-0.4.1-1.fc17,vinagre-3.4.1-1.fc17,vino-3.4.1-1.fc17,vte3-0.32.1-1.fc17,yelp-3.4.1-1.fc17
,yelp-tools-3.4.1-1.fc17,yelp-xsl-3.4.1-1.fc17

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/964796/comments/11


** Changed in: gnome-shell (Fedora)
   Status: Unknown => Fix Released

** Changed in: gnome-shell (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/964796

Title:
  wallpaper drawing is shifted for some seconds at gnomeshell starting
  up

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

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

[Bug 933250] Re: cell cleared

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

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 2012-04-17T01:59:49+00:00 Luke wrote:

Description of problem:
ibus generates a pre-edit-changed signal on focus switch, with an empty preedit 
string. It appears the purpose of this is to clear preedit context when you 
switch windows. Unfortunately this can cause some bad bugs, which various 
projects have had to work around (e.g. OpenOffice), and even data loss -- see 
the Gnumeric bug here: https://bugzilla.gnome.org/show_bug.cgi?id=663371  
Andreas states in this bug that it needs to be fixed in ibus, not in apps that 
are broken by this behavior.

How reproducible:
Every time.

Steps to Reproduce:
See the Gnumeric bug linked above.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/933250/comments/4

On 2012-04-17T06:25:05+00:00 fujiwara wrote:

(In reply to comment #0)
> How reproducible:
> Every time.

I don't understand your problem. I don't see any problems.

Do you mean you showed a preedit text on a sheet cell and switch the windows 
with Alt+Tab?
I don't understand why you need to enable input method on a cell during the 
switching windows.
I don't see any zero length preedits.

I checked cb_gnm_pane_preedit_changed() and it's called only when the preedit 
is opened.
I don't understand which codes are problem in cb_gnm_pane_preedit_changed().

Which ibus engines do you use?

If you use ibus-anthy, it provides a property to choose the behavior on
focus out with /usr/libexec/ibus-setup-anthy .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/933250/comments/5

On 2012-04-17T15:13:03+00:00 Luke wrote:

The behavior manifests with Alt+Tab, but the simplest way to see it is
when Gnumeric is opened -- Gnumeric gets a preedit_changed signal with
zero-length pre-edit string, and this puts Gnumeric into edit mode, as
if F2 had been pushed. This is dangerous because the zero-length preedit
string replaces whatever was in the cell if the user does anything other
than pressing Esc. So basically if the cursor is over meaningful
content, whenever you open a doc in Gnumeric, you *must* press Esc after
opening every document.

Please see the screencast here:
http://web.mit.edu/~luke_h/www/gnumeric.ogv

I don't have any special ibus engines in use. In the panel applet, I
only see "English (Dvorak)" and "English (US)".

cb_gnm_pane_preedit_changed() is what I traced the problem to when
hitting Alt-Tab (i.e. the code was definitely called in that situation
-- on that computer I also had Pinyin and Hangeul input methods set up
as options, but was only using Dvorak at the time). I assume that the
same procedure is called when gnumeric is opened, the symptoms are the
same -- although Gnumeric going into edit mode right after starting is a
new symptom in recent Fedora updates.

Please let me know what other information I can provide so you can
duplicate the problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/933250/comments/6

On 2012-04-18T11:15:31+00:00 fujiwara wrote:

OK, I can reproduce your problem when open an existent sheet but could not 
reproduce when I use Alt+Tab.
I think this is not reproduced in Fedora 17 or later.

I agree it's an ibus bug. The ibus gtk client sends the preedit signal when the 
disable signal is received from ibus-daemon.
The disable signal is added to notify the switching engines to ibus engines but 
it's not needed when the initial engine is assigned.

The following is the tentative patch for ibus-daemon:
https://github.com/fujiwarat/ibus/commit/9c63ecc4e36479242b2b763da8c66fa171bcc23e

I created the test rpms:
http://fujiwara.fedorapeople.org/ibus/20120418/4001269/
Could you try the ibus-1.4.1-2.fc16.x86_64.rpm if the problem is fixed?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/933250/comments/7

On 2012-04-19T01:31:04+00:00 Luke wrote:

On the computer I'm on right now, I can't duplicate the problem of
Gnumeric going into edit mode right on document open, but I can
duplicate the problem on Alt+Tab, even after installing your patched
RPMs, killing every process containing the string "ibus", and re-
starting ibus.

With the Alt+Tab case, you have to actually have multiple keyboard
layouts installed, and switch layouts once, before Alt+Tab causes
Gnumeric to enter edit mode with an empty preedit string.

I also found a new case

[Bug 940539] Re: libvirt deletes VM configuration file after editing uuid

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

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 2012-02-24T18:45:01+00:00 Shevek wrote:

Description of problem:

libvirt deleted the XML configuration file for a VM after an edit.

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

ii  libvirt-bin 0.9.2-4ubuntu15
ii  libvirt00.9.2-4ubuntu15

How reproducible: 100%

Steps to Reproduce:
1. Create and define a VM, but do not start it.
2. virsh edit the VM.
3. Change the UUID
4. Save and exit the editor.
5. Error message appears:
error: operation failed: domain 'orchestra' already exists with uuid 
4dd4e4bc-ec46-d7b8-5935-cbd727dd89c0
6. Observe XML file in /etc/libvirt/qemu now gone, and never called me mother.
  
Actual results:
XML file vanished, and VM config lost to posterity.

Expected results:
VM config should still exist, with an updated UUID.
libvirt should honour the updated UUID.

Reply at: https://bugs.launchpad.net/nova/+bug/940539/comments/0


On 2012-02-24T19:48:07+00:00 Dave wrote:

Hmm, I tried your steps to reproduce, but I am unable to reproduce this
behavior on libvirt 0.9.6.  I see the message about domain already
exists with uuid..., but the VM is unaffected following the attempt to
edit it.  What version of libvirt are you using?

Reply at: https://bugs.launchpad.net/nova/+bug/940539/comments/4


** Changed in: libvirt
   Status: Unknown => Expired

** Changed in: libvirt
   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/940539

Title:
  libvirt deletes VM configuration file after editing uuid

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

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

[Bug 954353] Re: Connection to graphics console doesn't work if graphics configuration uses listen attribute in libvirt XML config

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

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 2012-03-13T13:35:30+00:00 Tuomas wrote:

Created attachment 569683
Attempt to fix reported problem related to graphics console with listen address 
defined

Description of problem:
If I define a VM with graphics with listen address other than 127.0.0.1, 
virt-manager can't connect to this console.

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

DistroRelease: Ubuntu 12.04
Package: virt-manager 0.9.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
Architecture: amd64
SourcePackage: virt-manager

How reproducible:
Always


Steps to Reproduce:

1. Define a VM with the following kind of graphics config in libvirt XML

   
  
   

2. Start the VM

3. Switch to the graphical console of the VM

Actual results:
virt-manager console stays black when trying to connect to the console. The 
Spice URI is incorrect, KVM is listening 10.10.0.16:5904 for Spice clients, not 
127.0.0.1:5904.

Relevant output of virt-manager --debug when connecting without the
attached patch applied:

2012-03-13 15:25:42,624 (console:1081): Starting connect process for 
proto=spice trans=None connhost=localhost connuser=None connport=None 
gaddr=127.0.0.1 gport=5904 gsocket=None
2012-03-13 15:25:42,624 (console:496): spice uri: spice://localhost?port=5904


Expected results:
virt-manager displays the console by connecting to 10.10.0.16:5904.

Relevant output of virt-manager --debug when connecting without the attached 
patch applied:
2012-03-13 15:26:36,552 (console:1081): Starting connect process for 
proto=spice trans=None connhost=10.10.0.16 connuser=None connport=5904 
gaddr=10.10.0.16 gport=5904 gsocket=None
2012-03-13 15:26:36,552 (console:496): spice uri: spice://10.10.0.16?port=5904


Additional info:
Attached is a small patch that fixes this issue for me. But please review 
carefully, I really don't know if this is the proper way to fix this issue.

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


On 2012-03-13T15:36:35+00:00 Cole wrote:

Thanks for the patch! Pushed now:

http://git.fedorahosted.org/git?p=virt-
manager.git;a=commit;h=422c0216d806f7c71e7197279c032b7f58a42db3

But after inspecting the code I realize there are a few corner cases
here where we aren't doing the right thing, so this code is about to be
refactored :)

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


** Changed in: virt-manager
   Status: Unknown => Won't Fix

** Changed in: virt-manager
   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/954353

Title:
  Connection to graphics console doesn't work if graphics configuration
  uses listen attribute in libvirt XML config

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

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

[Bug 957131] Re: btrfs kernel bug

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

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 2012-02-07T11:20:27+00:00 Tomasz wrote:

Description of problem:
I have 4 1TB disk in raid10. Everytime I run following fio load, after few 
hours I got BUG() like below. Btrfs mounted with compress=lzo,space_cache

#v+
[write-test]


rw=randwrite
ioengine=libaio 


blocksize=4k


iodepth=32  


size=1512G   
#v-

[64354.305737] [ cut here ]
[64354.306009] kernel BUG at fs/btrfs/inode.c:1668!
[64354.306009] invalid opcode:  [#1] SMP 
[64354.306009] CPU 1 
[64354.306009] Modules linked in: lockd bnep bluetooth rfkill snd_intel8x0 
snd_ac97_codec ac97_bus snd_seq snd_seq_device ppdev snd_pcm snd_timer snd 
soundcore iTCO_wdt tg3 parport_pc iTCO_vendor_support parport snd_page_alloc 
dcdbas serio_raw i2c_i801 microcode sunrpc uinput aoe btrfs zlib_deflate 
libcrc32c sata_promise i915 drm_kms_helper drm i2c_algo_bit i2c_core video 
[last unloaded: scsi_wait_scan]
[64354.330470] 
[64354.330470] Pid: 5149, comm: btrfs-endio-wri Tainted: GW
3.3.0-0.rc2.git3.2.fc17.x86_64 #1 Dell Inc. OptiPlex GX620  
 /0FH884
[64354.330470] RIP: 0010:[]  [] 
insert_reserved_file_extent.constprop.50+0x251/0x260 [btrfs]
[64354.330470] RSP: 0018:8800757ffbd0  EFLAGS: 00010286
[64354.330470] RDX:  RSI: ea00033c3700 RDI: 0246
[64354.330470] RBP: 8800757ffc60 R08: 8800cf0dc760 R09: 000100110002
[64354.330470] R10: 8800cf0dc7f0 R11:  R12: 8800a453a290
[64354.330470] R13: 8800cf0dc1d8 R14: 8800a3a69868 R15: 002e8f0b2000
[64354.330470] FS:  () GS:8800db00() 
knlGS:
[64354.330470] CS:  0010 DS:  ES:  CR0: 8005003b
[64354.330470] CR2: 003238285240 CR3: 23ba8000 CR4: 06e0
[64354.330470] DR0:  DR1:  DR2: 
[64354.330470] DR3:  DR6: 0ff0 DR7: 0400
[64354.330470] Process btrfs-endio-wri (pid: 5149, threadinfo 8800757fe000, 
task 880097978000)
[64354.330470] Stack:
[64354.330470]  00ff8800757ffc00 1000 001d7ab1f000 
8800a453a290
[64354.330470]  1000 8800cf207a90 8800757ffc50 
a0123455
[64354.330470]  8800757ffc30  00cc 
8800a3a69868
[64354.330470] Call Trace:
[64354.330470]  [] ? start_transaction+0x85/0x3b0 [btrfs]
[64354.330470]  [] btrfs_finish_ordered_io+0x232/0x350 [btrfs]
[64354.330470]  [] btrfs_writepage_end_io_hook+0x4c/0x150 
[btrfs]
[64354.330470]  [] end_bio_extent_writepage+0x122/0x170 
[btrfs]
[64354.330470]  [] bio_endio+0x1d/0x40
[64354.330470]  [] end_workqueue_fn+0x64/0x150 [btrfs]
[64354.330470]  [] worker_loop+0x149/0x5d0 [btrfs]
[64354.330470]  [] ? btrfs_queue_worker+0x310/0x310 [btrfs]
[64354.330470]  [] kthread+0xb7/0xc0
[64354.330470]  [] ? trace_hardirqs_on+0xd/0x10
[64354.330470]  [] kernel_thread_helper+0x4/0x10
[64354.330470]  [] ? _raw_spin_unlock_irq+0x30/0x50
[64354.330470]  [] ? retint_restore_args+0x13/0x13
[64354.330470]  [] ? kthread_worker_fn+0x1a0/0x1a0
[64354.330470]  [] ? gs_change+0x13/0x13
[64354.330470] Code: ff 84 0f 85 67 fe ff ff e9 5e fe ff ff 0f 1f 44 00 00 41 
80 be 78 fb ff ff 84 75 9a eb 94 0f 1f 40 00 b8 f4 ff ff ff eb b9 0f 0b <0f> 0b 
0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 48 83 
[64354.330470] RIP  [] 
insert_reserved_file_extent.constprop.50+0x251/0x260 [btrfs]
[64354.330470]  RSP 
[64354.557410] ---[ end trace 6288379729f3c564 ]---
[64354.650352] [ cut here ]
[64354.651007] kernel BUG at fs/btrfs/inode.c:1668!
[64354.651007] invalid opcode:  [#2] SMP 
[64354.651007] CPU 0 
[64354.651007] Modules linked in: lockd bnep bluetooth rfkill snd_intel8x0 
snd_ac97_codec ac97_bus snd_seq snd_seq_device ppdev snd_pcm snd_timer snd

[Bug 953922] Re: When cloning a VM with qcow2 disk, the cloned VM will have its disk defined as raw format in its config

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

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 2012-03-13T22:17:44+00:00 Tuomas wrote:

Created attachment 569802
Patches CloneDesign to generate the XML required for the
element

Description of problem:

Cloning of a VM doesn't duplicate the driver type of the disk images to
be cloned.

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

DistroRelease: Ubuntu 12.04
Package: virtinst 0.600.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
Architecture: amd64
SourcePackage: virtinst

How reproducible:
Always

Steps to Reproduce:
1. Create a new QEMU/KVM VM called "foo" with a disk in qcow2 format like this

2. Clone the disk by running
sudo virt-clone -o foo --auto-clone
or using virt-manager GUI

Actual results:
The resulting VM foo-clone has the following disk configuration

The type of the disk is raw, not qcow2 as in the original VM.

Expected results:

The configuration of the clone should define the disk as the same type
as in the original VM, i.e. qcow2 in this case.

Additional info:
The file is properly cloned in the qcow2 format, though, so the issue only
affects generation of the clone configuration.

About the patches:

virtinst-0.600.1-generate-cloned-disk-driver-type-xml.diff patches
CloneDesign to generate the XML required for the
element. Only this patch is needed to fix the described malfunction with
virt-manager. After applying this, cloned VMs created with virt-manager
will have their configuration correctly cloned.

virtinst-0.600.1-hack-virt-clone-to-support-cloning-of-disk-driver-
type.diff is a really ugly hack for virt-clone which makes it work
around this problem. Also the previous patch is required so that correct
XML is actually generated. This patch overrides the CloneDesign API by
directly modifying the list of cloned drives in its CloneDesign object.
The problem is that these drives are created in
CloneDesign::set_cloned_devices using a fresh instance of VirtualDisk.
No info about the original disk is available here, only the filename of
the cloned image. Obviously, this isn't enough to supply the driver type
to the constructor of VirtualDisk (driverType argument), so this info is
effectively lost for the cloned disk. This code should be refactored so
that the driver type from the original disk is somehow automatically
preserved so the caller (e.g. virt-clone or virt-manager) doesn't have
to do anything special. But since I'm not familiar with the code, I
don't know where and how to start such refactoring.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/virtinst/+bug/953922/comments/2

On 2012-03-13T22:18:25+00:00 Tuomas wrote:

Created attachment 569803
Hack for virt-clone to work around this problem

Reply at:
https://bugs.launchpad.net/ubuntu/+source/virtinst/+bug/953922/comments/3

On 2012-03-13T22:31:16+00:00 Tuomas wrote:

My initial bug report for Ubuntu regarding this issue
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/953922

Reply at:
https://bugs.launchpad.net/ubuntu/+source/virtinst/+bug/953922/comments/5

On 2012-04-02T20:59:32+00:00 Cole wrote:

Thanks for the report. This has actually been fixed independently
upstream:

http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=f0195e95d57deda83daed5231582ca86bde519ae
http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=c9ae2ac4668213c03614842d92327737a25cf9ec

Unfortunately those probably won't backport cleanly, in which case I
think your hack is sufficient for a distro backport. Closing as UPSTREAM

Reply at:
https://bugs.launchpad.net/ubuntu/+source/virtinst/+bug/953922/comments/6

** Changed in: virtinst
Status: Unknown => Won't Fix

** Changed in: virtinst
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/953922

Title:
When cloning a VM with qcow2 disk, the cloned VM will have its disk
defined as raw format in its config

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

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

[Bug 969343] Re: Unable to connect to WPA enterprise wireless

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

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 2012-02-28T09:29:00+00:00 Fabrice wrote:

Created attachment 566264
with openssl-1.0.0g-1.fc17.x86_64

Authentication in wpa_supplicant fails with
openssl-1.0.1-0.1.beta2.fc17.x86_64 (security : wpa/wpa2 enterprise,
authentication ttls). Here is the output of wpa_supplicant, debug
enabled, with current openssl and with previous version. The
authentication problem occurs just after the occurence of "no matching
PMKID found"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/969343/comments/0


On 2012-02-28T09:29:59+00:00 Fabrice wrote:

Created attachment 566265
with openssl-1.0.1-0.1.beta2.fc17.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/969343/comments/1


On 2012-02-29T08:25:14+00:00 Tomas wrote:

The problem is indicated by this line:
EAP-TTLS: Failed to derive key

This message means that eap_peer_tls_derive_key() function failed. I'd
need more low level debugging output to find out which function called
from OpenSSL library fails or behaves differently.

I suppose it is related to the new TLS-1.2 support in openssl-1.0.1.
Perhaps the wpa_supplicant should forcibly limit the TLS version to 1.0?

Reassingning to wpa_supplicant for better insight from wpa_supplicant
maintainers.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/969343/comments/2


On 2013-04-03T14:23:34+00:00 Fedora wrote:

This bug appears to have been reported against 'rawhide' during the Fedora 19 
development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 
19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 
End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/969343/comments/143


On 2015-01-09T17:02:29+00:00 Fedora wrote:

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/969343/comments/151


On 2015-01-13T12:30:14+00:00 Fabrice wrote:

I cannot reproduce the bug with current versions. So closing this bz.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/969343/comments/152


** Changed in: wpasupplicant (Fedora)
   Status: Unknown => Invalid

** Changed in: wpasupplicant (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/969343

Title:
  Unable to connect to WPA enterprise wireless

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/969343/+subscriptions

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

[Bug 972826] Re: nautilus crashed with SIGSEGV in find_subtree_recurse()

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

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 2012-02-25T15:36:55+00:00 Bastian wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:nautilus
comment:I enable Bluetooth on my Nokia 7500 Prism. My laptop is paired 
with the device, so I press the Bluetooth Icon in the top bar, find the name of 
my cell phone in the drop-down menu. Upon pressing the name I choose to "Browse 
Files".  The file browser appears and I navigate into /Memory Card/Images/ 
which is empty. I then press Ctrl+T to open a new tab in the file browser and 
navigate to Home/Temp/ where I have 41 images stored, all shot by the 
cellphone's camera. I drag and drop the images into the folder I previously 
navigated to on my cellphone and then error appear.
crash_function: find_subtree_recurse
executable: /usr/bin/nautilus
kernel: 3.2.6-3.fc16.i686
pid:30084
pwd:/home/bh
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
time:   Sat 25 Feb 2012 03:54:43 PM CET
uid:1000
username:   bh

backtrace:  Text file, 33937 bytes
build_ids:  Text file, 6519 bytes
dso_list:   Text file, 14738 bytes
maps:   Text file, 44010 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=HTX-2402MQ.home
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=cd206d2fb9e379319ff75a3f000f-1330181057.159580-1950516298
:GNOME_KEYRING_CONTROL=/tmp/keyring-nUbhgk
:IMSETTINGS_MODULE=none
:USER=bh
:USERNAME=bh
:MAIL=/var/spool/mail/bh
:PATH=/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/bh/.local/bin:/home/bh/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/bh
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1439
:LANG=en_US.UTF-8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/bh
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=bh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-rVoQ3FxoL9,guid=7305a90e0870c6c7492279830041
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/bh
:DISPLAY=:0
:CCACHE_HASHDIR=
:XAUTHORITY=/var/run/gdm/auth-for-bh-0LH81j/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1445,unix/unix:/tmp/.ICE-unix/1445
:SSH_AUTH_SOCK=/tmp/keyring-nUbhgk/ssh
:GPG_AGENT_INFO=/tmp/keyring-nUbhgk/gpg:0:1
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:DESKTOP_STARTUP_ID=gnome-shell-1679-HTX-2402MQ.home-nautilus-3_TIME640598
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/nautilus.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=30084

smolt_data:
:
:
:General
:=
:UUID: 63a8ab61-51b7-4d3e-9f78-b7c478b16b83
:OS: Fedora release 16 (Verne)
:Default run level: Unknown
:Language: en_US.UTF-8
:Platform: i686
:BogoMIPS: 4521.72
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Core(TM) i3 CPU   M 350  @ 2.27GHz
:CPU Stepping: 2
:CPU Family: 6
:CPU Model Num: 37
:Number of CPUs: 4
:CPU Speed: 2266
:System Memory: 2946
:System Swap: 4991
:Vendor: Hewlett-Packard
:System: HP ProBook 4520s 
:Form factor: Notebook
:Kernel: 3.2.6-3.fc16.i686
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Enforcing
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Devices
:=
:(4332:33128:4156:5139) pci, r8169, ETHERNET, RTL8111/8168B PCI Express Gigabit 
Ethernet controller
:(32902:11362:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath 
Architecture Generic Non-core Registers
:(32902:11521:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath 
Architecture System Address Decoder
:(32902:68:4156:5139) pci, agpgart-intel, HOST/PCI, Core Processor DRAM 
Controller
:(32902:11536:32902:32902) pci, None, HOST/PCI, Core Processor QPI Link 0
:(32902:11537:32902:32902) pci, None, HOST/PCI, Core Processor QPI Physical 0
:(32902:11538:32902:32902) pci, None, HOST/PCI, Core Processor Reserved
:(32902:11539:32902:32902) pci, None, HOST/PCI, Core Processor Reserved
:(32902:15151:4156:5139) pci, ahci, STORAGE, 5 Series/3400 Series Chipset 6 
port SATA AHCI Controller
:(32902:15115:4156:5139) pci, None, PCI/ISA, Mobile 5 Series Chipset LPC 
Interface Controller
:(32902:15154:4156:5139) pci, intel ips, NONE, 5 Series/3400 Series Chipset 
Thermal Subsystem
:(5772:43:4156:12352) pci, ath9k, NETWORK, AR9285 Wireless Network Adapter 
(PCI-Express)
:(32902:9288:4156:5139) pci, None, PCI/PCI, 82801 Mobile PCI Bridge
:(32902:15164:4156:5139) pci, ehci_hcd, USB, 5 Series/3400

[Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)

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

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 2012-04-12T09:36:10+00:00 Mikhail wrote:

Description of problem:
When I leave the computer on overnight, it is often in the morning discover the 
computer hangs and constantly swap, and the processes of gnome-settings-daemon 
and dconf consume all CPU resources.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/7


On 2012-04-12T09:40:06+00:00 Mikhail wrote:

Created attachment 577019
htop

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/8


On 2012-05-05T10:14:41+00:00 Mikhail wrote:

Created attachment 582274
htop

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/27


On 2012-05-14T11:15:16+00:00 Fabio wrote:

Same bug on Ubuntu: https://bugs.launchpad.net/fedora/+source/gnome-
settings-daemon/+bug/969359

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/35


On 2012-05-29T08:14:16+00:00 Mikhail wrote:

Created attachment 587339
backtrace for gnome-settings-daemon 1-process

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/51


On 2012-05-29T08:15:09+00:00 Mikhail wrote:

Created attachment 587340
backtrace for gnome-settings-daemon 2-process

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/52


On 2012-05-29T08:16:08+00:00 Mikhail wrote:

Created attachment 587342
backtrace for dconf-service process

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/53


On 2012-05-29T08:17:33+00:00 Mikhail wrote:

Created attachment 587343
backtrace for dbus-daemon process

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/54


On 2012-06-04T04:49:45+00:00 Mikhail wrote:

Created attachment 589027
backtrace for gnome-settings-daemon

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/67


On 2012-06-04T04:50:49+00:00 Mikhail wrote:

Created attachment 589028
backtrace for dconf worker process

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/68


On 2012-06-04T04:51:53+00:00 Mikhail wrote:

Created attachment 589033
backtrace for Compositor

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/69


On 2012-06-04T04:52:49+00:00 Mikhail wrote:

Created attachment 589035
backtrace for dconf-service

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/70


On 2012-06-04T04:55:14+00:00 Mikhail wrote:

when it occurs Num Lock indicator is often blink.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/71


On 2012-07-12T13:17:58+00:00 Mikhail wrote:

Killing dconf worker process seems stop this, but something wrong after this:
Not work hot keys (Ctrl +Shift + L - lock comkputer, Prt Scr - make 
screenshot), decrease font...

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/102


On 2012-07-12T13:18:19+00:00 Mikhail wrote:

Killing dconf worker process seems stop this, but something wrong after this:
Not work hot keys (Ctrl +Shift + L - lock computer, Prt Scr - make screenshot), 
decrease font...

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/969359/comments/103


On 2012-07-12T13:19:01+00:00

[Bug 973088] Re: tracker-miner-fs crashed with SIGABRT in g_assertion_message()

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

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 2012-03-12T15:36:42+00:00 Stef wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:/usr/libexec/tracker-miner-fs
comment:Tracker was abusing my disk heavily on boot.
crash_function: __GI_raise
executable: /usr/libexec/tracker-miner-fs
kernel: 3.3.0-0.rc6.git0.2.fc17.x86_64
pid:1386
pwd:/data
reason: Process /usr/libexec/tracker-miner-fs was killed by signal 6 
(SIGABRT)
time:   2012-03-12T16:35:18 CET
uid:1000
username:   stef
var_log_messages: Mar 12 16:35:19 stef-desktop abrt[1723]: Saved core dump of 
pid 1386 (/usr/libexec/tracker-miner-fs) to 
/var/spool/abrt/ccpp-2012-03-12-16:35:18-1386 (18919424 bytes)

backtrace:  Text file, 17375 bytes
dso_list:   Text file, 5007 bytes
maps:   Text file, 23909 bytes

build_ids:
:b033b2025009f19c9e322929810998f45cf483f6
:97317d1518e70c97ab14100f4510f2360865cbc3
:6a6f7e91aa12548505e8302f27282865ff2842d3
:174e128892385c6bb2b4e4a4213d31f9dc49466f
:0d78b752f0d9e83f0f4eb9e6f0ae186ad0b2a13c
:e850c9c2577f79b97ad4c53dbf9b0964682dcbaa
:4d9f1e9a6e14bb126793e5796a5951874dd83038
:2348d82efc78d838cb28f784c3a61c627d45278a
:3e9f65a1ee01419219fb006790eb394dab35d0b7
:666abf228c966f37766ad17cd64ba794136e9ac9
:a625841a963b5765aa9c0b4f827a8235f2697ccc
:f0ff7bf178355b5a8690e7d6c6751d4ebdf643c5
:49ff2bf2bc331d1033b5e96f3b4372347889ba17
:8eb096dfd0ffd6744062e82b158bd1d4268afd1c
:dc0e0e2829f4097ed6088d91e7b42fc2db9c5e49
:c879875e907f7695ca18dfd6e007621e8af15ea3
:cdc5b8cd84a20c1f21b10595d129a60345510396
:89071323dc419820c49b8c25c7cfd972c2d949f6
:b1e3a6defd2119a017e2c5b43fbaf7d48d46a9cd
:00d6e8a5d861940c0a1e47bae30bc1972f576705
:3deed610a4a5e058c663c5800450b5cfe9c37a75
:5bbbe16527d496a0e0fefc6ba0c0219a71a0e4c1
:a2d5b50b07df0fb9c52fcc682c6121d3e7276249
:093bb56117e9818caa13d7a83e4975d5477533c5
:63651cdc0224824a9c9324c77c3b5887378e871d
:816a568132698192f252ff462ca0c988434bf8b3
:4f9a85443f33acbad2eb0068b0d8128b38944b9f
:8d72d96e568ee72b2fe9a478eb54ad2d289bbcd8
:b5797b67e070ac4ccaff8d7180cf635fa0f31cbf
:766fa7124150058af0f9ce4c39148868b4dbb47f
:822e9b3523e8312240f41a25722d539bc77ed436
:14eca14fab7e7f37bc37a80ec50e773bf93252c4
:652697d945b4084f8ecf3bbd2eeb5d33b69aff4f
:5bc2d347a293d92e3c373d09875abb8a267a9fc4
:fe58d8fb04b8db326ab41ab7a98b0f3b73e06618
:63b8b24e78f9956bfba3d0a95500d9a25e21d594
:5b7cdec9dba117156a6e5568a103fb5b44087566
:a9eb9e4d2da6b047bad0601ad65f06ea8afb3603
:7c35310fc506498c612d5d982ab03becc4b4817c
:cd5b354188380a59735021c133d1cec7f4c46fdc
:80dcf30321dbc04511d9cbf399a83b8f3dc75d5d
:4149ff67ae395df1bf3f3f0b9e960c1883bbeb6f
:a095f564bf20c90a6e26a32fe83d4d04c5eadbcb
:fc0dbdb3dc7f13b00e9c5975adc55256920871b5
:d804f8ee47797da9213a92f00cd095ecada8d79f
:2ac8e124ff368269ee692eef71e48cddaff7c731
:1fa4aa0f57b72034546fd97a1e0520e7d6502e0d
:e3f83e6ed76d65ff9d0d4aa5fcc7bf0c6bfaaadd
:277d74794a8d683ef066f298ec72b16b3a5ea5b2
:fa73f07676b8a455c4d3a6ce2c4fd689f2417ad5
:f0264e76a3f8ec444874b1a23d68c2ecaeba5e1c
:9e27816c18322e53c8465a18aa3a8043f3434781
:3aa364e64dd370c14adc27be6df2d70960406d7e
:46fe2763c4865dc6cd3b28818e63f42f4e3b0139
:cb4d385c55c522feae9fb39650f6f365f568796c

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=stef-desktop.thewalter.lan
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:LOGIN_SITE=/data/projects/login-provider/site
:HISTSIZE=1000
:XDG_SESSION_COOKIE=13946642489734c5e44302c102dd-1331566414.537865-747174292
:GNOME_KEYRING_CONTROL=/tmp/keyring-1FJA21
:IMSETTINGS_MODULE=none
:USER=stef
:MEM_SITE=/data/projects/members/site
:MAILER_SITE=/data/projects/login-mailer/site
:MAIL=/var/spool/mail/stef
:PATH=/data/bin:/data/.local/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/data/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/data
:JAVA_HOME=/opt/jdk_1.4.2/
:XMODIFIERS=@im=none
:EDITOR=vi
:GNOME_KEYRING_PID=1151
:LANG=en_US.utf8
:GDM_LANG=en_US.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:XDG_SEAT=seat0
:HOME=/data
:SHLVL=1
:LOGNAME=stef
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-wR84YqKk1i,guid=501eec4e14ff4b3f304dc2520022
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:UDB_CONFFILE=/data/projects/udb-test/unit-test/udb.conf
:XDG_RUNTIME_DIR=/run/user/stef
:DISPLAY=:0
:LC_TIME=en_DK.utf8
:CCACHE_HASHDIR=
:XAUTHORITY=/var/run/gdm/auth-for-stef-vBKgsS/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1155,unix/unix:/tmp/.ICE-unix/1155
:GPG_AGENT_INFO=/tmp/keyring-1FJA21/gpg:0:1

[Bug 978458] Re: CVE-2012-1182: "root" credential remote code execution

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

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 2012-04-10T21:35:42+00:00 Vincent wrote:


This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
versions.

For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When creating a Bodhi update request, please include this bug ID and the
bug IDs of this bug's parent bugs filed against the "Security Response"
product (the top-level CVE bugs).  Please mention the CVE IDs being fixed
in the RPM changelog when available.

Bodhi update submission link:
https://admin.fedoraproject.org/updates/new/?type_=security=804093

Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please ensure that it is only closed
when all affected versions are fixed.


[bug automatically created by: add-tracking-bugs]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/4


On 2012-04-11T13:06:14+00:00 Jan wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/8


On 2012-04-12T14:49:04+00:00 Fedora wrote:

samba-3.6.4-82.fc17.1 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/samba-3.6.4-82.fc17.1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/9


On 2012-04-12T14:49:36+00:00 Fedora wrote:

samba-3.6.4-82.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/samba-3.6.4-82.fc16

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/10


On 2012-04-12T14:50:38+00:00 Fedora wrote:

samba-3.5.14-73.fc15.1 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/samba-3.5.14-73.fc15.1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/11


On 2012-04-13T06:12:11+00:00 Fedora wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/23


On 2012-04-13T21:34:14+00:00 Fedora wrote:

samba-3.6.4-82.fc16 has been pushed to the Fedora 16 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/26


On 2012-04-18T23:09:15+00:00 Fedora wrote:

samba-3.6.4-82.fc17.1 has been pushed to the Fedora 17 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/27


On 2012-04-22T03:27:08+00:00 Fedora wrote:

samba-3.5.14-73.fc15.1 has been pushed to the Fedora 15 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/28

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

Title:
  CVE-2012-1182: "root" credential remote code execution

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

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

[Bug 974838] Re: Wireless Dropout - Tx aggregation enabled on ra (workaround: iwlwifi requires 11n_disable=1)

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

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 2012-02-05T06:18:30+00:00 Simon wrote:

After a period of time, the wireless simply stops functioning... NetworkManager 
thinks its still connected.. but no network traffic works.
After a period of time (if left) sometimes it reconnects at G-54Mbit speed.. vs 
'N' at around 270Mbit

The following are observed in dmesg:

[  505.669220] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  555.202192] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  588.834218] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  617.740773] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  690.116581] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  742.430541] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  788.704026] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  801.676020] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[  962.686813] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1015.634260] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1099.420837] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1107.568703] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1119.465765] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1147.984058] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1213.937449] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1239.211977] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1352.128153] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1428.874172] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1467.239910] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1501.816674] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1585.802417] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1638.777505] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1669.836635] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1706.886181] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0
[ 1733.298790] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 0



Kernel; Linux greenback.local 3.2.2-1.fc16.x86_64 #1 SMP Thu Jan 26
03:21:58 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux




Some details as to the wireless adapter;

[5.214347] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[5.214441] iwlwifi :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[5.214496] iwlwifi :03:00.0: setting latency timer to 64
[5.214542] iwlwifi :03:00.0: pci_resource_len = 0x2000
[5.214544] iwlwifi :03:00.0: pci_resource_base = c900058a
[5.214545] iwlwifi :03:00.0: HW Revision ID = 0x34
[5.214830] iwlwifi :03:00.0: irq 50 for MSI/MSI-X
[5.214919] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[5.214921] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[5.214922] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[5.214924] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
[5.214925] iwlwifi :03:00.0: CONFIG_IWLWIFI_P2P disabled
[5.214956] iwlwifi :03:00.0: Detected Intel(R) Centrino(R) Advanced-N 
6205 AGN, REV=0xB0
[5.215034] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[5.225137] iwlwifi :03:00.0: device EEPROM VER=0x715, CALIB=0x6
[5.225140] iwlwifi :03:00.0: Device SKU: 0x1F0
[5.225142] iwlwifi :03:00.0: Valid Tx ant: 0x3, Valid Rx ant: 0x3
[5.225166] iwlwifi :03:00.0: Tunable channels: 13 802.11bg, 24 802.11a 
channels
[5.241189] iwlwifi :03:00.0: loaded firmware version 17.168.5.3 build 
42301
[9.282736] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[9.282928] iwlwifi :03:00.0: Radio type=0x1-0x2-0x0
[9.565154] iwlwifi :03:00.0: L1 Enabled; Disabling L0S
[9.565344] iwlwifi :03:00.0: Radio type=0x1-0x2-0x0
[   45.937516] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
00:04:ed:bb:c6:fd tid = 6

Reply at:

[Bug 975176] Re: gvfsd-obexftp crashed with SIGSEGV in send_reply()

** Changed in: gvfs (Fedora)
   Status: Unknown => Won't Fix

** Changed in: gvfs (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/975176

Title:
  gvfsd-obexftp crashed with SIGSEGV in send_reply()

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

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

[Bug 974664] Re: Kernel Oops - BUG: unable to handle kernel paging request at ffffffffffffffb8; RIP: 0010:[] [] nfs_have_delegation+0x9/0x40 [nfs]

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

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 2012-04-10T08:59:31+00:00 Bert wrote:

Description of problem:

Kernel traceback on NFS4 locking attempt

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

kernel 3.3.1-2 (and 3.3.1-3)

How reproducible:

Always

Steps to Reproduce:
1. Install kernel 3.3.1-{2,3}; mount a users home over NFS4
2. Start e.g. pidgin, which tries to lock some file
3.
  
Actual results:

*) Pidgin crashes with 'Killed'.  Strace shows that the last activity
   is:

[...]
open("/users/visics/deknuydt/.config/enchant/en_US.dic", O_RDONLY) = 11
flock(11, LOCK_EX 
+++ killed by SIGKILL +++
Killed

*) In dmesg, you see:

 [  322.987247] BUG: unable to handle kernel paging request at ffb8
[  322.987330] IP: [] nfs_have_delegation+0x9/0x40 [nfs]
[  322.987418] PGD 1c07067 PUD 1c08067 PMD 0 
[  322.987495] Oops:  [#1] SMP 
[  322.987565] CPU 1 
[  322.987574] Modules linked in: nfs fscache nf_conntrack_ipv4 nf_defrag_ipv4 
xt_state nf_conntrack sha256_generic dm_crypt nvidia(PO) nfsd uinput lockd 
nfs_acl auth_rpcgss sunrpc snd_hda_codec_realtek snd_hda_intel snd_hda_codec 
snd_hwdep snd_seq snd_seq_device snd_pcm iTCO_wdt i2c_i801 iTCO_vendor_support 
intel_rng microcode r8169 i2c_core mii snd_timer snd soundcore snd_page_alloc 
serio_raw firewire_ohci firewire_core crc_itu_t sata_sil24 video [last 
unloaded: scsi_wait_scan]
[  322.988230] 
[  322.988230] Pid: 1697, comm: pidgin Tainted: P   O 
3.3.1-3.fc16.x86_64 #1 transtec AG /DG31PR
[  322.988230] RIP: 0010:[]  [] 
nfs_have_delegation+0x9/0x40 [nfs]
[  322.988230] RSP: 0018:880112e55dd8  EFLAGS: 00010246
[  322.988230] RAX: 880122411800 RBX: 880112e55e68 RCX: d8ca
[  322.988230] RDX:  RSI: 0001 RDI: 
[  322.988230] RBP: 880112e55dd8 R08: 00016560 R09: ea00044b8400
[  322.988230] R10: a0e0457a R11:  R12: d8ca
[  322.988230] R13: 8801218be000 R14: 88011573cc00 R15: 8801224b0480
[  322.988230] FS:  7fdda2060980() GS:88012fc8() 
knlGS:
[  322.988230] CS:  0010 DS:  ES:  CR0: 80050033
[  322.988230] CR2: ffb8 CR3: 000112c07000 CR4: 06e0
[  322.988230] DR0:  DR1:  DR2: 
[  322.988230] DR3:  DR6: 0ff0 DR7: 0400
[  322.988230] Process pidgin (pid: 1697, threadinfo 880112e54000, task 
880112dd2e60)
[  322.988230] Stack:
[  322.988230]  880112e55e28 a0e01fa1 880112e11e60 

[  322.988230]  8801224b0480 8801224b0780 8801224b0480 
0082
[  322.988230]  880112e55e68 fff5 880112e55eb8 
a0e04b9c
[  322.988230] Call Trace:
[  322.988230]  [] nfs4_handle_exception+0x241/0x3a0 [nfs]
[  322.988230]  [] nfs4_proc_lock+0xec/0x440 [nfs]
[  322.988230]  [] do_setlk+0xed/0x110 [nfs]
[  322.988230]  [] nfs_flock+0x89/0xe0 [nfs]
[  322.988230]  [] sys_flock+0x113/0x1c0
[  322.988230]  [] system_call_fastpath+0x16/0x1b
[  322.988230] Code: fd ff e9 40 fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 55 
48 89 e5 66 66 66 66 90 f0 80 4f 48 04 5d c3 55 48 89 e5 66 66 66 66 90 <48> 8b 
57 b8 31 c0 48 85 d2 74 0c 8b 4a 30 83 e6 03 21 f1 39 f1 
[  322.988230] RIP  [] nfs_have_delegation+0x9/0x40 [nfs]
[  322.988230]  RSP 
[  322.988230] CR2: ffb8
[  322.988230] ---[ end trace 158525064a4030cd ]---


Expected results:

*) No NFS4 delegation problems.

Additional info:

1) Koji kernel 3.3.1-3 has exactly the same problem.

2) Kernel 3.3.0-8 does not have the problem.

3) Sorry for the tainted kernel (nvidia).  I'll confirm with an untainted
   asap.

4) It seems that Ubuntu has this problem too.
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974664

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974664/comments/3


On 2012-04-10T12:37:33+00:00 Tim wrote:

We are suffering the same problem, it occurs right after login when
gnome-keyring tries to access the home directory mounted via NFSv4 with
kernel 3.3.1-3 on the client. Server is CentOS 6.2. Client-side kernel
3.2.10-3.fc16.x86_64 works for us. Kernel is not tainted.

Apr 10 14:26:32 morgan kernel: [   54.179536] BUG: unable to handle kernel 
paging request at ffb8
Apr 10 14:26:32 morgan kernel: [   54.179575] IP: [] 
nfs_have_delegation+0x9/0x40 [nfs]
Apr 10 14:26:32 morgan kernel: [   54.179621] PGD 1c07067 PUD 1c08067

[Bug 981037] Re: The javac executable doesn't produce full paths for files on error

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

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 2012-02-09T23:36:22+00:00 Mike wrote:

Description of problem:

The latest version of javac produces error messages that no longer
display the full path of the file containing the errors.  This means
that the error message no longer unambiguously identifies the offending
file as soon as there is a collision in the leaf file names in a java
project.

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

java-1.6.0-openjdk-devel-1.6.0.0-63.1.11.fc16.*

How reproducible:

Always.

Steps to Reproduce:
1. mkdir tmp; echo "bar" > tmp/foo.java
2. javac tmp/foo.java
  
Actual results:

foo.java:1: reached end of file while parsing
bar
^
1 error

Expected results:

tmp/foo.java:1: reached end of file while parsing
bar
^
1 error

Additional info:

java-1.6.0-openjdk-devel-1.6.0.0-59.1.10.3.fc16.* produces the expected
result above, so for now, yum downgrade allows me to work around this
problem.  Not a long term solution of course.  A better workaround would
be if there is a command line option to restore the full path, but I was
unable to find any.

There are two reasons this is really a bug and not just a cosmetic
issue.

1. I have to deal with some medium-to-large Java projects where the leaf file 
names are far from unique.  Indeed there are some places where there is a 
directory containing subdirectories which in turn contain files with 
standardized identical names (50+ and growing of them).  The old error message 
unambiguously identified the broken file.  The new one leaves me guessing.
Changing the naming convention is outside my area of responsibility, its `other 
people's code'.

2. This kills any possibility for an editor to parse the error messages
and bring up the offending source/line.  Please understand that not
everybody uses eclipse!

IMHO the best solution to this problem is to revert the change.

See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638805

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/0


On 2012-03-27T20:13:09+00:00 Deepak wrote:

Assigning to Pavel.

Pavel, I looked into the issue and it looks like it is being caused due to this 
patch:
http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2011-March/013178.html

Can you please take a look when you have time?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/1


On 2012-03-28T12:51:26+00:00 Andrew wrote:

Hmmm, as I recall, that patch was introduced specifically to fix this
problem.  But indeed, testing with 1.11 suggests it doesn't.

I'll check if removing the patch makes HEAD's behave match 7.  If so,
I'll commit the change.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/2


On 2012-03-28T16:34:55+00:00 Andrew wrote:

Indeed, removing the patch does give the same behaviour as in previous
releases, including not only 1.10, but 1.9 and 1.8.  I was under the
impression that this patch was added because 1.10 (to which it was going
to be backported, but seemingly never was) changed the behaviour,
compared to other releases.  But these results suggest not.

Let's see what Pavel has to say.  I think there was a TCK issue
involved, which may since have been excluded, so some of this may have
to happen internally.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/3


On 2012-03-29T09:38:44+00:00 Andrew wrote:

For the benefit of public users, Pavel confirmed that the TCK issues
surrounding this patch have been resolved through other means so the
patch can be dropped.

Pavel, can you remove the patch from HEAD and the 1.11 branch?  I'll
approve on the mailing list.  Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/4


On 2012-03-29T12:02:05+00:00 Pavel wrote:

Of course, I'll do it. Thank you.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/5


On 2012-03-29T14:20:02+00:00 Andrew wrote:

Thanks Pavel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/981037/comments/6


** Changed in: openjdk-6 (Fedora)
   Status: Unknown => Fix Released

** Changed in:

[Bug 978728] Re: Google Calendar broken : Unable to create calendar object : The calendar doesn't exists

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

** Changed in: evolution (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/978728

Title:
  Google Calendar broken : Unable to create calendar object : The
  calendar doesn't exists

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

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

[Bug 978458] Re: CVE-2012-1182: "root" credential remote code execution

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

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 2012-03-16T14:12:07+00:00 Jan wrote:

Multiple heap-based buffer overflow flaws were found in the way the code
generated by Perl-based DCE/RPC IDL (PIDL) compiler of the Samba suite
performed array memory allocation. Memory for an array having an
is_size() attribute has been allocated based on the array length, which
was provided by the Network Data Representation (NDR) marshalling code
(converting parameters provided to the RPC call by the client to the
NDR). On the other hand the loop retrieving array elements for a
particular array used variable indicated by the size_is() attribute. A
remote attacker could provide a specially-crafted remote procedure call
(RPC) parameters, which once processed by the marshalling code of the
Samba server would lead to Samba daemon (smbd) crash, or, potentially
arbitrary code execution with the privileges of the user running the
server.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/0


On 2012-04-10T16:44:20+00:00 Vincent wrote:

This has been corrected in upstream 3.6.4, 3.5.14, and 3.4.16.

External References:

http://www.samba.org/samba/history/samba-3.6.4.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/1


On 2012-04-10T20:22:59+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 5.6 EUS - Server Only
  Red Hat Enterprise Linux 5

Via RHSA-2012:0466 https://rhn.redhat.com/errata/RHSA-2012-0466.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/2


On 2012-04-10T21:13:14+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 5.3 Long Life
  Red Hat Enterprise Linux 5.6 EUS - Server Only
  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6.0 EUS - Server Only
  Red Hat Enterprise Linux 6.1 EUS - Server Only
  Red Hat Enterprise Linux 6

Via RHSA-2012:0465 https://rhn.redhat.com/errata/RHSA-2012-0465.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/3


On 2012-04-10T21:35:49+00:00 Vincent wrote:

Created samba tracking bugs for this issue

Affects: fedora-all [bug 811392]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/4


On 2012-04-12T14:56:29+00:00 Gwyn wrote:

Rawhide has been updated, updates have been created for f17, f16 and
f15.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/7


On 2012-04-13T08:50:14+00:00 Huzaifa wrote:

Created samba4 tracking bugs for this issue

Affects: fedora-all [bug 812257]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/18


On 2012-04-13T13:54:40+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 4 Extended Lifecycle Support

Via RHSA-2012:0478 https://rhn.redhat.com/errata/RHSA-2012-0478.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/19


On 2012-04-25T13:27:15+00:00 Tomas wrote:

Statement:

This issue did not affect the versions of samba packages as shipped with Red 
Hat Enterprise Linux 3. The samba packages are also excluded from the Red Hat 
Enterprise Linux 3 Extended Life Cycle Support coverage:
http://www.redhat.com/rhel/server/extended_lifecycle_support/exclusions/

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/20


On 2012-05-15T23:28:25+00:00 Fedora wrote:

samba4-4.0.0-38.alpha16.fc16 has been pushed to the Fedora 16 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/978458/comments/21


On 2012-09-07T03:52:48+00:00 Huzaifa wrote:

Statement:

This issue affects the version of samba4, openchange and evolution-mapi
packages as shipped with

[Bug 997391] Re: Symbolic links can create recursive loop that causes Baobab to never finish scanning

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

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 2012-04-10T21:58:28+00:00 Simon wrote:

Description of problem:
when i let baobab scan a windows 7 partition it keeps getting into infinite 
loops because of some symlinks.

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

How reproducible:
always

Steps to Reproduce:
1. let baobab scan an ntfs partition with this special kind of symlink
2.
3.
  
Actual results:
baobab follows the symlink

Expected results:
baobab skips the symlink

Additional info:
there is something special about this kind of symlinks,
stat reports that it is a symlink, but that it has 2 links, which is the only 
difference I see from the normal symlinks

Reply at:
https://bugs.launchpad.net/fedora/+source/baobab/+bug/997391/comments/0


On 2012-08-18T13:00:49+00:00 Erik wrote:

This bug is caused by a bug in the ntfs-3g package.

A bugreport was filed upstream and they've already proposed a patch
which resolves this issue:
http://tuxera.com/forum/viewtopic.php?f=2=29578

I just filed a ticket to the ntfs-3g maintainer in Fedora asking to
apply this patch in the Fedora ntfs-3g package: bug 849332

Reply at:
https://bugs.launchpad.net/fedora/+source/baobab/+bug/997391/comments/3


On 2012-08-24T18:45:50+00:00 Fedora wrote:

ntfs-3g-2012.1.15-3.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/FEDORA-2012-12279/ntfs-3g-2012.1.15-3.fc17

Reply at:
https://bugs.launchpad.net/fedora/+source/baobab/+bug/997391/comments/7


On 2012-09-04T22:57:03+00:00 Fedora wrote:

ntfs-3g-2012.1.15-3.fc17 has been pushed to the Fedora 17 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at:
https://bugs.launchpad.net/fedora/+source/baobab/+bug/997391/comments/9


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

** Changed in: baobab (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/997391

Title:
  Symbolic links can create recursive loop that causes Baobab to never
  finish scanning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/997391/+subscriptions

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

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

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

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 2012-03-26T14:30:13+00:00 Yann wrote:

Created attachment 572767
/var/log/messages

It seems that, with the latest kernel, my network connection (Ethernet
100BaseT) is unstable:

The connection is "disconnected" every 10 minutes interval according to
NetworkManager (with a notification on screen).

I'm using
kernel-3.3.0-4.fc16.x86_64
NetworkManager-0.9.2-1.fc16.x86_64.

My network interface is a
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B 
PCI Express Gigabit Ethernet controller (rev 02)

My computer is connected to a FreeBox v5 ADSL router, which provides "native" 
IPv6 broadband access.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/988183/comments/0

On 2012-03-26T15:13:42+00:00 Yann wrote:

Created attachment 572778
log of a a tcpdump ip6 session

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

On 2012-03-26T15:38:15+00:00 Neil wrote:

please see bz 785772.  Upgrading to the latest NM in rawhide fixes this
issue.

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

On 2012-03-26T18:52:34+00:00 Yann wrote:

I'm using Fedora 16. Installing NetworkManager from Rawhide require too
much dependencies to be installed alone safely.

Is it possible to have a test update package ?

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

On 2012-03-27T13:03:04+00:00 Neil wrote:

http://koji.fedoraproject.org/koji/taskinfo?taskID=3936339

There you go, thats the rawhide NetworkManager built for f16.

If you don't want to install that, you can also set your NM IPv6
configuration for all your interfaces to 'ignore'.  That should also fix
the problem.

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

On 2012-03-27T18:32:52+00:00 Yann wrote:

(In reply to comment #4)
> http://koji.fedoraproject.org/koji/taskinfo?taskID=3936339
> 
> There you go, thats the rawhide NetworkManager built for f16.  
> 

Thanks a lot for the packages.

I tried to install them but updated NetworkManager-gnome is missing.

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

On 2012-03-27T18:34:12+00:00 Yann wrote:

Created attachment 573150
NetworkManager install log

(In reply to comment #5)
> 
> I tried to install them but updated NetworkManager-gnome is missing.

Here's the log if needed.

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

On 2012-03-28T16:44:27+00:00 Neil wrote:

Thanks, not sure whats going on there.  I'll have to figure that out.
The spec file isn't explicitly Required:-ing that package.

While I figure it out, please just set the interface settings for the
interface in questions for IPv6 to Ignore or Disable, that will provide
an equally good solution.

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

On 2012-03-30T10:31:13+00:00 Jirka wrote:

(In reply to comment #5)
> (In reply to comment #4)
> > http://koji.fedoraproject.org/koji/taskinfo?taskID=3936339
> > 
> > There you go, thats the rawhide NetworkManager built for f16.  
> > 
> 
> Thanks a lot for the packages.
> 
> I tried to install them but updated NetworkManager-gnome is missing.

Please try F16 update here (it's not in stable at the time of this posting)
http://koji.fedoraproject.org/koji/buildinfo?buildID=310135

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/988183/comments/8

On 2012-04-01T07:15:13+00:00 Nicolas wrote:

I also have the same problem, but the updated NetworkManager doesn't
seem to help:

# yum info NetworkManager
Installed Packages
Name: NetworkManager
Arch: x86_64
Epoch   : 1
Version : 0.9.4
Release : 1.git20120328.fc16
Size: 6.7 M
Repo: installed
>From repo

[Bug 998830] Re: power usage in watts not being displayed (battery discharge rate)

** Changed in: powertop
   Status: Unknown => Fix Released

** Changed in: powertop
   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/998830

Title:
  power usage in watts not being displayed (battery discharge rate)

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

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

[Bug 1082213] Re: libvirt: When installing two or more identical usb devices in a VM, only one works

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

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 2012-04-26T12:01:39+00:00 Ken wrote:

+++ This bug was initially created as a clone of Bug #815755 +++

Description of problem:

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

How reproducible: 100%

Steps to Reproduce:
1. Take 2 RSA Tokens and connect them to a hypervisor
2. Use lsusb -v to find a uniquely identifyable property of each device 
3. Either
a) use virt-manager to attach the device with highest bus:device address to a 
guest
OR
b) write an XML description of the device specifying address bus= device= for 
the highest numbered RSA token
# virsh attach-device  
4) use virsh dumpxml  and see which device is actually attached to 
the guest

Actual results:

The device with the lowest bus:device address and matching
vendor:product id is attached to the guest

Expected results:

The device specified by the address bus= device= in the XML, or the
device selected in the virt-manager GUI should be attached to the guest

Additional info:

In order to confirm the wrong device is attached, login to the guest and
run lsusb -v and search for the uniquely identifyable property of the
device.

e.g. my RSA Token has bMaxPacketSize0 = 64, but for many of my
colleagues it is 32.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1082213/comments/0

On 2012-04-30T23:50:29+00:00 Ken wrote:

Suggested fix ...

$ diff src/qemu/qemu_hostdev.c src/qemu/qemu_hostdev-modified.c
597,599c597,613
< usbDevice *usb
< = usbFindDevice(hostdev->source.subsys.u.usb.vendor,
< hostdev->source.subsys.u.usb.product);
---
> if (hostdev->source.subsys.u.usb.bus) {
> usbDevice *usb
> = usbGetDevice(hostdev->source.subsys.u.usb.bus,
>hostdev->source.subsys.u.usb.device);
> if ((hostdev->source.subsys.u.usb.vendor != usb->vendor) ||
> (hostdev->source.subsys.u.usb.product != usb->product)) {
> qemuReportError(VIR_ERR_OPERATION_INVALID,
> _("USB device %s does not match vendor 
> product id"),
> usbDeviceGetName(tmp));
> usbFreeDevice(usb);
> goto cleanup;
> }
> } else {
> usbDevice *usb
> = usbFindDevice(hostdev->source.subsys.u.usb.vendor,
> hostdev->source.subsys.u.usb.product);
> }

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1082213/comments/1

On 2012-05-08T04:54:24+00:00 Gunannan wrote:

The patch has been pushed in upstream. So I set it to POST 
https://www.redhat.com/archives/libvir-list/2012-May/msg00289.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1082213/comments/2

On 2012-07-04T16:48:33+00:00 Cole wrote:

Fixed in currentrelease

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1082213/comments/3

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

** Changed in: libvirt (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/1082213

Title:
  libvirt: When installing two or more identical usb devices in a VM,
  only one works

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

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

[Bug 1016505] Re: CVE-2012-0862: enables unintentional services over tcpmux port

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

** Changed in: xinetd (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/1016505

Title:
  CVE-2012-0862: enables unintentional services over tcpmux port

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

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

[Bug 1075478] Re: [HP EliteBook 8530w] Bluetooth keyboards and mice not working after suspend/resume

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

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 2012-04-11T11:00:10+00:00 James wrote:

Created attachment 576744
Xorg.0.log from problem session

Description of problem:
After a suspend/resume cycle, X no longer recognises my Bluetooth mouse.

 - There's a confounding issue in that sometimes the Bt subsystem doesn't
   come back properly, see Bug 727106. Devices reappear after restarting
   the bluetooth service.

 - Following this, the mouse appears in the devices list in Gnome Shell,
   and other devices (e.g. file transfer from phone) works properly.

 - Upon reconnecting the mouse, messages like

 (WW) evdev: Bluetooth Mouse: device file is duplicate. Ignoring.

   appear in the Xorg logs (attached).

Sometimes waiting for a few hours and then trying again works.

I don't know if this is strictly an evdev bug. Might be udev or bluez or
kernel or ... please reassign as appropriate.

Version-Release number of selected component (if applicable):
xorg-x11-drv-evdev-2.6.99.901-7.20120118git9d9c9870c.fc16.x86_64
udev-173-3.fc16.x86_64
bluez-4.96-3.fc16.x86_64
kernel-3.3.0-8.fc16.x86_64
kernel-3.3.1-2.fc16.x86_64
kernel-3.3.1-3.fc16.x86_64
xorg-x11-server-Xorg-1.11.4-3.fc16.x86_64

How reproducible:
Intermittent, but frequent.

Steps to Reproduce:
1. Suspend then resume.
2. Restart bluetooth.service if necessary, according to Bug 727106.
3. Reconnect Bluetooth mouse.

Actual results:
Mouse doesn't work.

Expected results:
Mouse works.

Additional info:

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

On 2012-04-20T01:38:27+00:00 Peter wrote:

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

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

On 2012-04-20T02:31:11+00:00 Peter wrote:

Either server or udev bug. The last parts of the log show that we get
the "device added" event, but we never saw the "device removed" for it.

The config_info string changes, so we don't automatically remove the
previous instance when the new one is added.

Lennart, any comments? Is there some race condition that we may suffer
from in the server that we don't see the device removed event?

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

On 2012-08-27T21:29:57+00:00 Dan wrote:

Are there any workarounds known, besides restarting X?  I don't
particularly like having to shut down all programs to restart X.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/3

On 2012-08-27T21:49:57+00:00 Scott wrote:

(In reply to comment #2)
> Either server or udev bug. The last parts of the log show that we get the
> "device added" event, but we never saw the "device removed" for it. 
> 
> The config_info string changes, so we don't automatically remove the
> previous instance when the new one is added.
> 
> Lennart, any comments? Is there some race condition that we may suffer from
> in the server that we don't see the device removed event?

Actually it's increasingly looking like a kernel bug - we're seeing the
kernel netlink events with missing or corrupted components and also
seeing other signs that pointers aren't going where they're supposed
to...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/4

On 2012-08-27T22:00:09+00:00 Pierre-Yves wrote:

Dan, you might probably just unplug and re-plug the mouse

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/5

On 2012-08-27T22:26:09+00:00 Dan wrote:

Pierre-Yves: I have internal bluetooth so there is no possibility to
unplug anything.  However, I have tried cycling power on the mouse and
have tried running "systemctl restart bluetooth.service" without
success.  Restarting X (by logging out and back in) works though.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075478/comments/6

On 2012-08-28T20:51:52+00:00 Andrew wrote:

Scott is referring to the debugging we've been doing on Chromium OS. We
have some more details in the bug: http://code.google.com/p/chromium-
os/issues/detail?id=33813

It's looking like a

[Bug 1028274] Re: xwininfo segfaults if given a non-existent screen with -display option

** Changed in: x11-utils (Fedora)
   Status: Unknown => Won't Fix

** Changed in: x11-utils (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/1028274

Title:
  xwininfo segfaults if given a non-existent screen with -display option

To manage notifications about this bug go to:
https://bugs.launchpad.net/x11-utils/+bug/1028274/+subscriptions

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

[Bug 1003112] Re: The Filter: dropdown in the File Open menu doesn't work

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

On 2012-05-09T22:54:54+00:00 Ian wrote:

Created attachment 583395
Cropped contents of Filter drop-down (actual size extends across display)

Description of problem:
Trying to export from Draw to an EMF file. The Filter drop-down in the Export
dialog is seriously borked; all of the formats other than HTML, XHTML, PDF, and
Flash appear to have gotten corrupted somehow, and they are can only be
selected together. The Export dialog in impress shows the same problem.

Version-Release number of selected component (if applicable):
libreoffice-draw-3.5.2.1-6.fc17.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Open LibreOffice Draw
2. File -> Export
3. Attempt to set Filter to anything except HTML, XHTML, PDF, or Flash

Actual results:
All other formats get selected together. Weird error message ensues.

Expected results:
Should be able to select individual format EMF, BMP, PNG, etc.

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/0

On 2012-05-10T05:45:32+00:00 Ian wrote:

This problem is specific to the KDE-integrated export dialog. Removing
libreoffice-kde is a workaround.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/1

On 2012-05-10T20:47:51+00:00 Caolan wrote:

http://cgit.freedesktop.org/libreoffice/core/commit/?id=5df9e10d27a071f878ed160f99129a7f3c34f5ed

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/2

On 2012-05-10T21:53:27+00:00 Ian wrote:

Created attachment 583685
Patch backported to 3.5.3.2

Currently rebuilding libreoffice-3.5.3.2-3.fc17.src.rpm with this patch.
Will report results.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/3

On 2012-05-11T03:31:55+00:00 Ian wrote:

(In reply to comment #3)
> Created attachment 583685 [details]
> Patch backported to 3.5.3.2

With this patch applied, the KDE export dialog works again.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/4

On 2012-05-11T05:48:18+00:00 David wrote:

will be fixed in libreoffice-3.5.3.2-4.fc17

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/5

On 2012-05-21T05:52:09+00:00 Mitch wrote:

Can someone check to see if this patch fixes what appears to be the same
behavior on the Import dialog? I am unable to select any single file
type.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/6

On 2012-05-21T13:55:17+00:00 Ian wrote:

(In reply to comment #6)
> Can someone check to see if this patch fixes what appears to be the same
> behavior on the Import dialog? I am unable to select any single file type.

I'd be happy to check ... if I could find the Import dialog. Where is
it?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/7

On 2012-05-21T15:26:29+00:00 Mitch wrote:

(In reply to comment #7)
> (In reply to comment #6)
> > Can someone check to see if this patch fixes what appears to be the same
> > behavior on the Import dialog? I am unable to select any single file type.
>
> I'd be happy to check ... if I could find the Import dialog. Where is it?

Sorry - I just mean the ordinary file Open dialog. It's the filter
dropdown at the bottom.

If you want to open a tab-delimited file with an extension .txt as a
spreadsheet you have to go to Open... and then select "text csv" as the
file type. If you don't do this, the file will open as a text document,
not a spreadsheet. That is why this is actually a rather significant
bug. The workaround is to rename the file .csv.

Do we know if this patch has been submitted upstream? I wasn't able to
figure out where it should be sent to.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1003112/comments/8

On 2012-05-21T15:40:16+00:00 Ian wrote:

(In reply to comment #8)
> If you want to

[Bug 1071209] Re: memtest86+ test #7 false positives (random number sequence error)

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

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 2012-03-22T09:08:21+00:00 Karel wrote:

Description of problem:
Trying to run the latest memtest86+ on various hardware, even in qemu, the 
seventh test (Random number sequence) fails and reports errors for each address 
from 129 MiB on.

Version-Release number of selected component (if applicable):
memtest86+ 4.20 from Fedora 17 Alpha DVD

How reproducible:
always

Steps to Reproduce:
1. qemu-kvm -m 1024 -cdrom Fedora-17-Alpha-x86_64.DVD.iso
2. choose Troubleshooting => Run memory test
  
Actual results:
see the attached screenshot

Expected results:
no errors

Additional info:
Initially, I've run this on Intel SandyBridge hardware - Pentium B950 with some 
Samsung memories, and it failed this way, leading me to unjustified warranty 
claim ...
After that, I've verified the same memtest behaviour on T510 with Core i7 M620, 
and on some older desktop with Core i5 - real hardware, proven by months of 
service => seeing the same all the time I've tried in qemu and it fails too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/0


On 2012-03-22T09:09:08+00:00 Karel wrote:

Created attachment 571941
screenshot of the problem

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/1


On 2012-03-22T14:06:12+00:00 Jaroslav wrote:

Created attachment 572002
Temporal workaround

Thanks for reporting. It seems to be related to gcc-4.7 update. Temporal 
workaround patch is attached (it could negatively affect performance).
Scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3922148
I am working on better patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/2


On 2012-03-27T09:13:39+00:00 Fedora wrote:

memtest86+-4.20-6.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/memtest86+-4.20-6.fc17

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/3


On 2012-03-27T18:08:06+00:00 Adam wrote:

Proposing as Final blocker, though it's somewhat arguable. Criterion:
"All release media must include a standalone memory test utility. A boot
menu option to launch this utility must be present and must work
correctly. "

Also proposing as Beta NTH, it would be good to ensure the memtest in
Beta works.


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/4


On 2012-03-28T05:59:57+00:00 Fedora wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/5


On 2012-03-28T21:35:11+00:00 Przemek wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/6


On 2012-03-29T00:11:05+00:00 Adam wrote:

Discussed at 2012-03-28 go/no-go meeting, acting as an NTH review
meeting. Accepted as NTH: this can't be fixed with an update, and it's
obviously visibly bad to have broken memtest on our beta images.


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/7


On 2012-03-29T04:12:23+00:00 Fedora wrote:

memtest86+-4.20-6.fc17 has been pushed to the Fedora 17 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1071209/comments/8


** Changed in: memtest86+
   Status: Unknown => Fix

[Bug 1017125] Re: [SRU quantal] boost::unordered_multimap<>::erase(iterator, iterator) broken in boost1.49

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

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 2012-03-23T09:43:09+00:00 Anton wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --impress 
file:///home/anton/Customer%20Portal%20Internal_03202012.odp --splash-pipe=6
crash_function: std::list::begin
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.3.0-3.tip0.uprobes.fc17.x86_64
pid:18424
pwd:/home/anton
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed 
by signal 11 (SIGSEGV)
time:   Fri 23 Mar 2012 09:42:27 CET
uid:1000
username:   anton

backtrace:  Text file, 69241 bytes
dso_list:   Text file, 20606 bytes
maps:   Text file, 88339 bytes

environ:
:GIT_PS1_SHOWDIRTYSTATE=true
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=bandura.brq.redhat.com
:LC_MONETARY=en_GB.utf8
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GIO_LAUNCHED_DESKTOP_FILE_PID=18410
:GPG_AGENT_INFO=/tmp/keyring-XLyyPc/gpg:0:1
:SHELL=/bin/bash
:TERM=xterm-256color
:DESKTOP_STARTUP_ID=nautilus-18399-bandura.brq.redhat.com-libreoffice-0_TIME6183650
:HISTSIZE=1000
:XDG_SESSION_COOKIE=140f39c967431aadf43a7e320010-1332485955.765921-668108218
:GJS_DEBUG_OUTPUT=stderr
:G_MESSAGES_DEBUG=all
:LC_NUMERIC=en_GB.utf8
:OLDPWD=/usr/lib64/libreoffice/program
:QTDIR=/usr/lib64/qt-3.3
:GNOME_KEYRING_CONTROL=/tmp/keyring-XLyyPc
:QTINC=/usr/lib64/qt-3.3/include
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:IMSETTINGS_MODULE=none
:USER=anton
:SSH_AUTH_SOCK=/tmp/keyring-XLyyPc/ssh
:USERNAME=anton
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1117,unix/unix:/tmp/.ICE-unix/1117
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/libreoffice-impress.desktop
:MAIL=/var/spool/mail/anton
:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/anton/.local/bin:/home/anton/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/anton
:XMODIFIERS=@im=none
:EDITOR=vim
:KDE_IS_PRELINKED=1
:GNOME_KEYRING_PID=1109
:LANG=en_GB.utf8
:GDM_LANG=en_GB.utf8
:KDEDIRS=/usr
:LC_MEASUREMENT=en_GB.utf8
:GIT_PS1_SHOWUNTRACKEDFILES=true
:GDMSESSION=gnome
:SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
:HISTCONTROL=ignoredups
:XDG_SEAT=seat0
:HOME=/home/anton
:SHLVL=1
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SAL_ENABLE_FILE_LOCKING=1
:LOGNAME=anton
:PRINTER=brno1-3rd-cafe
:QTLIB=/usr/lib64/qt-3.3/lib
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-7mbsOmI4UG,guid=a900ddf0010ccf66132eecc7003f
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:BROWSER=google-chrome
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/anton
:DISPLAY=:0.0
:LC_TIME=en_GB.utf8
:XAUTHORITY=/var/run/gdm/auth-for-anton-S0MDkT/database
:LD_LIBRARY_PATH=/usr/java/jre1.7.0_03/lib/amd64/client:/usr/java/jre1.7.0_03/lib/amd64/server:/usr/java/jre1.7.0_03/lib/amd64/native_threads:/usr/java/jre1.7.0_03/lib/amd64

var_log_messages:
:Mar 23 09:42:27 bandura kernel: [ 6247.104768] soffice.bin[18424]: segfault at 
a0 ip 003bc9fba958 sp 7fff1af30e50 error 4 in 
libvcllo.so[3bc9e0+7dd000]
:Mar 23 09:42:28 bandura abrt[18500]: Saved core dump of pid 18424 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-03-23-09:42:27-18424 (129572864 bytes)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/0


On 2012-03-23T09:43:14+00:00 Anton wrote:

Created attachment 572211
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/1


On 2012-03-23T09:43:16+00:00 Anton wrote:

Created attachment 572212
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/2


On 2012-03-23T09:43:19+00:00 Anton wrote:

Created attachment 572214
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/3


On 2012-03-23T12:29:54+00:00 Caolan wrote:

some kind of busted lifecycle.

Was this on closing an impress frame ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/4


On 2012-03-26T06:16:51+00:00 Anton wrote:

I can guess only, but IIRC it was on the close of impress.

Reply at:

[Bug 1097323] Re: SdModule::GetSdOptions: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11

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

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 2012-03-25T21:09:28+00:00 Gerhard wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --impress 
file:///tmp/Ein%20Platz%20genannt%20Erde%201546.pps --splash-pipe=7
comment:Closed presentation and then I closed the email-tab in 
thunderbird with the before opened presentation.
crash_function: SdModule::GetSdOptions
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.2.10-3.fc16.x86_64
pid:10492
pwd:/home/gerhard
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed 
by signal 11 (SIGSEGV)
time:   Son 25 Mär 2012 22:37:25 CEST
uid:1000
username:   gerhard

backtrace:  Text file, 48652 bytes
build_ids:  Text file, 8815 bytes
dso_list:   Text file, 24241 bytes
maps:   Text file, 97418 bytes

environ:
:XDG_VTNR=2
:XSUNTRANSPORT=shmem
:ORBIT_SOCKETDIR=/tmp/orbit-gerhard
:XDG_SESSION_ID=7
:HOSTNAME=freelancer
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GIO_LAUNCHED_DESKTOP_FILE_PID=10479
:GPG_AGENT_INFO=/tmp/keyring-huwKS1/gpg:0:1
:TERM=dumb
:SHELL=/bin/bash
:XDG_SESSION_COOKIE=b1c9ea14cd7a3251ef3dfc960003-1332529364.816593-1417338382
:HISTSIZE=1000
:XRE_PROFILE_NAME=
:OLDPWD=/usr/lib64/libreoffice/program
:GNOME_KEYRING_CONTROL=/tmp/keyring-huwKS1
:MOZILLA_FIVE_HOME=/usr/lib64/thunderbird
:IMSETTINGS_MODULE=none
:USER=gerhard
:XRE_PROFILE_LOCAL_PATH=
:LD_LIBRARY_PATH=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/client:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/native_threads:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib64/thunderbird:/usr/lib64/thunderbird/plugins:/usr/lib64/thunderbird
:XRE_START_OFFLINE=
:SSH_AUTH_SOCK=/tmp/keyring-huwKS1/ssh
:LIBPATH=/usr/lib64/thunderbird:/usr/lib64/thunderbird
:GNOME_DISABLE_CRASH_DIALOG=1
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/13034,unix/unix:/tmp/.ICE-unix/13034
:USERNAME=gerhard
:MOZ_APP_LAUNCHER=/usr/bin/thunderbird
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/libreoffice-impress.desktop
:DESKTOP_SESSION=gnome
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/gerhard/.local/bin:/home/gerhard/bin
:MAIL=/var/spool/mail/gerhard
:QT_IM_MODULE=xim
:PWD=/home/gerhard
:XMODIFIERS=@im=none
:LANG=de_AT.utf8
:GNOME_KEYRING_PID=13029
:GDM_LANG=de_AT.utf8
:XRE_PROFILE_PATH=
:XSUNSMESIZE=512
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:SHLVL=1
:XDG_SEAT=seat0
:HOME=/home/gerhard
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SAL_ENABLE_FILE_LOCKING=1
:DYLD_LIBRARY_PATH=/usr/lib64/thunderbird:/usr/lib64/thunderbird
:LOGNAME=gerhard
:MOZ_LAUNCHED_CHILD=
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-l6hEuOEOpY,guid=796f1e12176edbcccb76c83b1130
:NO_EM_RESTART=
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:SHLIB_PATH=/usr/lib64/thunderbird:/usr/lib64/thunderbird
:MOZ_CRASHREPORTER_RESTART_ARG_1=
:WINDOWPATH=2
:MOZ_CRASHREPORTER_RESTART_ARG_0=/usr/lib64/thunderbird/thunderbird
:XRE_BINARY_PATH=
:DISPLAY=:1.0
:XDG_RUNTIME_DIR=/run/user/gerhard
:'MOZ_CRASHREPORTER_DATA_DIRECTORY=/home/gerhard/.thunderbird/Crash Reports'
:XUL_APP_FILE=
:NO_AT_BRIDGE=1
:XAUTHORITY=/var/run/gdm/auth-for-gerhard-pFxEGN/database

var_log_messages:
:Mar 25 22:37:25 freelancer kernel: [26652.075169] soffice.bin[10492]: segfault 
at 78 ip 7f4dedd0bec8 sp 7fff2e7dc8f0 error 4 in 
libsdlx.so[7f4dedaa7000+5e5000]
:Mar 25 22:37:26 freelancer abrt[10541]: Saved core dump of pid 10492 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-03-25-22:37:25-10492 (157642752 bytes)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097323/comments/0


On 2012-03-25T21:09:33+00:00 Gerhard wrote:

Created attachment 572577
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097323/comments/1


On 2012-03-25T21:09:35+00:00 Gerhard wrote:

Created attachment 572578
File: build_ids

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097323/comments/2


On 2012-03-25T21:09:38+00:00 Gerhard wrote:

Created attachment 572579
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097323/comments/3

[Bug 1097760] Re: sw: better fix for DOCX table import crash

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

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 2012-05-09T14:08:59+00:00 Karolis wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:/usr/lib/libreoffice/program/soffice.bin --writer 
file:///media/D69AC9A59AC9828B/Documents%20and%20Settings/Ingrida/Downloads/CVTemplate-EDITED-KAROLIS.docx
 --splash-pipe=7
crash_function: GetPos
executable: /usr/lib/libreoffice/program/soffice.bin
kernel: 3.3.2-6.fc16.i686
pid:8371
pwd:/home/karolis
reason: Process /usr/lib/libreoffice/program/soffice.bin was killed by 
signal 11 (SIGSEGV)
time:   Wed 09 May 2012 02:31:30 PM IST
uid:1000
username:   karolis
xsession_errors: 

backtrace:  Text file, 40328 bytes
dso_list:   Text file, 19156 bytes
maps:   Text file, 47704 bytes

comment:
:Tried to add a column to a table when it crashed.
:It was a .docx document

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=mothership
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GIO_LAUNCHED_DESKTOP_FILE_PID=8359
:GPG_AGENT_INFO=/tmp/keyring-7H0h2E/gpg:0:1
:SHELL=/bin/bash
:TERM=dumb
:DESKTOP_STARTUP_ID=nautilus-8032-mothership-libreoffice-6_TIME14911677
:HISTSIZE=1000
:XDG_SESSION_COOKIE=6e2bf614b7910041d770f50d000f-1336555375.546154-155461563
:GJS_DEBUG_OUTPUT=stderr
:OLDPWD=/usr/lib/libreoffice/program
:GNOME_KEYRING_CONTROL=/tmp/keyring-7H0h2E
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:IMSETTINGS_MODULE=none
:USER=karolis
:SSH_AUTH_SOCK=/tmp/keyring-7H0h2E/ssh
:USERNAME=karolis
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1576,unix/unix:/tmp/.ICE-unix/1576
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/libreoffice-writer.desktop
:MAIL=/var/spool/mail/karolis
:PATH=/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/go/bin:/home/karolis/.local/bin:/home/karolis/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/karolis
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1568
:LANG=en_US.UTF-8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/karolis
:XDG_SEAT=seat0
:SHLVL=1
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SAL_ENABLE_FILE_LOCKING=1
:LOGNAME=karolis
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-wmU1MWVEZc,guid=55f7a6bfacf75b6ab48fe18e00a0
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/karolis
:DISPLAY=:0.0
:CCACHE_HASHDIR=
:XAUTHORITY=/var/run/gdm/auth-for-karolis-ztVzMc/database
:LD_LIBRARY_PATH=/usr/java/jre1.6.0_31/lib/i386/client:/usr/java/jre1.6.0_31/lib/i386/server:/usr/java/jre1.6.0_31/lib/i386/native_threads:/usr/java/jre1.6.0_31/lib/i386

smolt_data:
:
:
:General
:=
:UUID: 8bef7ae9-3c6f-46da-8f11-494ba7855420
:OS: Fedora release 16 (Verne)
:Default run level: Unknown
:Language: en_US.UTF-8
:Platform: i686
:BogoMIPS: 4748.52
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Core(TM) i5 CPU   M 430  @ 2.27GHz
:CPU Stepping: 2
:CPU Family: 6
:CPU Model Num: 37
:Number of CPUs: 4
:CPU Speed: 2267
:System Memory: 2695
:System Swap: 7602
:Vendor: ASUSTeK Computer Inc.
:System: K52Jc 1.0
:Form factor: Notebook
:Kernel: 3.3.2-6.fc16.i686
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Enforcing
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Devices
:=
:(32902:11536:32902:32902) pci, None, HOST/PCI, Core Processor QPI Link 0
:(32902:11362:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath 
Architecture Generic Non-core Registers
:(32902:11521:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath 
Architecture System Address Decoder
:(32902:68:4163:7287) pci, agpgart-intel, HOST/PCI, Core Processor DRAM 
Controller
:(32902:69:4163:7287) pci, pcieport, PCI/PCI, Core Processor PCI Express x16 
Root Port
:(6523:9092:4163:6663) pci, None, BASE, xD Host Controller
:(6523:592:4163:6405) pci, jme, ETHERNET, JMC250 PCI Express Gigabit Ethernet 
Controller
:(6523:9089:4163:6663) pci, None, BASE, Standard SD Host Controller
:(6523:9091:4163:6663) pci, jmb38x_ms, BASE, MS Host Controller
:(6523:9090:4163:6663) pci, sdhci-pci, BASE, SD/MMC Host Controller
:(32902:11539:32902:32902) pci, None, HOST/PCI, Core Processor Reserved
:(32902:15145:4163:7287) pci, ahci, STORAGE, 5 Series/3400 Series Chipset 4 
port SATA AHCI Controller
:(32902:15113:4163:7287) pci, None, PCI/ISA, Mobile 5 Series Chipset LPC 
Interface Controller
:(32902:15154:4163:7287) pci, intel ips, NONE, 5 Series/3400 Series Chipset 
Thermal Subsystem
:(32902:9288:4163:7287) pci, None, PCI/PCI, 82801 Mobile PCI Bridge

[Bug 1223907] Re: qemu-kvm crashes in qcow2 code

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

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 2012-04-16T02:49:31+00:00 daiwei wrote:

Description of problem:

Install guest with virtio-scsi interface and cluster_size=4096, when
formating disk qemu-kvm gets Aborted.

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

# uname -r;rpm -q qemu-kvm
2.6.32-259.el6.x86_64
qemu-kvm-0.12.1.2-2.269.el6.scsifixes.x86_64


How reproducible:
3/3

Steps to Reproduce:
1. Create a qcow2 image with cluster_size=4096
e.g
# qemu-img create -f qcow2 sysdisk.qcow2 20G -o cluster_size=4096

2.Install guest

/usr/libexec/qemu-kvm -cpu cpu64-rhel6 -rtc
base=localtime,clock=host,driftfix=slew -M rhel6.3.0 -enable-kvm -name
rhel6.3-64 -smp 4,cores=2,threads=1,sockets=2 -m 4G -uuid c944829b-
9aa0-46a2-b3d0-493c135da24d -boot menu=on -drive
file=/home/sysdisk.qcow2,if=none,id=drive-virtio-
disk0,format=qcow2,cache=none,aio=native,media=disk,werror=stop,rerror=stop
-device virtio-scsi-pci,id=bus1 -device scsi-hd,bus=bus1.0,drive=drive-
virtio-disk0,id=virtio-scsi-pci0 -netdev
tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup-switch -device virtio-
net-pci,netdev=hostnet0,id=net0,mac=44:37:E6:5E:A3:F7 -spice port=9000
,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -monitor stdio -usb
-device usb-tablet,id=input1 -drive file=/home/RHEL6.3-20120329.0
-Server-x86_64-DVD1.iso,if=none,id=drive-virtio-
disk1,format=raw,cache=none,aio=native,media=cdrom -device virtio-scsi-
pci,id=bus2 -device scsi-cd,bus=bus2.0,drive=drive-virtio-disk1,id
=virtio-scsi-pci1,bootindex=1

3.
  
Actual results:
When formating disk, qemu-kvm gets Aborted.

Program received signal SIGABRT, Aborted.
0x757788a5 in raise () from /lib64/libc.so.6

(gdb) bt
#0  0x757788a5 in raise () from /lib64/libc.so.6
#1  0x7577a085 in abort () from /lib64/libc.so.6
#2  0x77e3c42e in qcow2_cache_find_entry_to_replace (bs=0x78854c30, 
c=0x787027d0, offset=3279413248,
table=0x7fffd75764b8, read_from_disk=false) at block/qcow2-cache.c:209
#3  qcow2_cache_do_get (bs=0x78854c30, c=0x787027d0, offset=3279413248, 
table=0x7fffd75764b8, read_from_disk=false)
at block/qcow2-cache.c:229
#4  0x77e3a299 in l2_allocate (bs=0x78854c30, offset=6463520768, 
new_l2_table=0x7fffd7576548, new_l2_offset=0x7fffd7576550,
new_l2_index=0x7fffd757655c) at block/qcow2-cluster.c:180
#5  get_cluster_table (bs=0x78854c30, offset=6463520768, 
new_l2_table=0x7fffd7576548, new_l2_offset=0x7fffd7576550,
new_l2_index=0x7fffd757655c) at block/qcow2-cluster.c:512
#6  0x77e3a6e6 in qcow2_alloc_cluster_offset (bs=0x78854c30, 
offset=6463520768, n_start=0, n_end=1008, num=0x7fffd757666c,
m=0x7fffd7576600) at block/qcow2-cluster.c:714
#7  0x77e363bf in qcow2_co_writev (bs=0x78854c30, sector_num=, remaining_sectors=1008,
qiov=0x7fffd855e838) at block/qcow2.c:555
#8  0x77e215fa in bdrv_co_do_writev (bs=0x78854c30, 
sector_num=12624064, nb_sectors=1008, qiov=0x7fffd855e838,
flags=) at block.c:1734
#9  0x77e216a1 in bdrv_co_do_rw (opaque=0x7fffd855e890) at block.c:3032
#10 0x77e26b6b in coroutine_trampoline (i0=, 
i1=) at coroutine-ucontext.c:129
#11 0x75789630 in ?? () from /lib64/libc.so.6
#12 0x7fffedd5a530 in ?? ()
#13 0x in ?? ()

Expected results:
Install guest successfully.

Additional info:
In guest format a data disk with cluster_size=4096, gets the same issue.
With virtio-blk interface no this issue.

Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu-
kvm/+bug/1223907/comments/0


On 2012-04-16T04:55:33+00:00 Xiaoqing wrote:

reproduced on:
2.6.32-262.el6.x86_64
qemu-kvm-0.12.1.2-2.275.el6.x86_64

using virtio-blk

Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu-
kvm/+bug/1223907/comments/1


On 2012-04-16T12:35:41+00:00 daiwei wrote:

Sorry for report this bug on a private tree, i can reproduce this on the
latest qemu-kvm and using virtio-scsi disk :

# uname -r;rpm -q qemu-kvm
2.6.32-262.el6.x86_64
qemu-kvm-0.12.1.2-2.275.el6.x86_64

Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu-
kvm/+bug/1223907/comments/2


On 2012-04-17T12:19:52+00:00 Dor wrote:

Kevin, can you look whether its a symptom of a critical issue?

Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu-
kvm/+bug/1223907/comments/3

[Bug 1097722] Re: a11y: call doShow after we have a valid view

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

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 2012-03-22T01:10:54+00:00 Michal wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --draw 
--splash-pipe=6
crash_function: std::vector 
>::size
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.3.0-1.fc17.x86_64
pid:16895
pwd:/home/mambroz
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed 
by signal 11 (SIGSEGV)
time:   Thu 22 Mar 2012 01:37:43 AM CET
uid:1000
username:   mambroz

backtrace:  Text file, 43957 bytes
dso_list:   Text file, 21044 bytes
maps:   Text file, 96031 bytes

comment:
:1) Edit image in draw.
:2) export it to wmf
:3) import wmf to impress
:4) click back to draw

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=3
:HOSTNAME=mixer.localdomain
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GIO_LAUNCHED_DESKTOP_FILE_PID=16880
:GPG_AGENT_INFO=/tmp/keyring-0KsaOY/gpg:0:1
:SHELL=/bin/bash
:TERM=dumb
:DESKTOP_STARTUP_ID=gnome-shell-16399-mixer.localdomain-libreoffice-0_TIME23270559
:HISTSIZE=1
:GJS_DEBUG_OUTPUT=stderr
:G_MESSAGES_DEBUG=all
:OLDPWD=/usr/lib64/libreoffice/program
:QTDIR=/usr/lib64/qt-3.3
:GNOME_KEYRING_CONTROL=/tmp/keyring-0KsaOY
:QTINC=/usr/lib64/qt-3.3/include
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:IMSETTINGS_MODULE=none
:USER=mambroz
:SSH_AUTH_SOCK=/tmp/keyring-0KsaOY/ssh
:USERNAME=mambroz
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1659,unix/unix:/tmp/.ICE-unix/1659
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/libreoffice-draw.desktop
:MAIL=/var/spool/mail/mambroz
:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/mambroz/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/mambroz
:XMODIFIERS=@im=none
:KDE_IS_PRELINKED=1
:GNOME_KEYRING_PID=1657
:LANG=en_US.UTF-8
:KDEDIRS=/usr
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:XDG_SEAT=seat0
:HOME=/home/mambroz
:SHLVL=1
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SAL_ENABLE_FILE_LOCKING=1
:LOGNAME=mambroz
:QTLIB=/usr/lib64/qt-3.3/lib
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Q7uKbioaA8,guid=d3f84712bfef3b75a64f7ca0082c
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/mambroz
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-mambroz-DigYNU/database
:LD_LIBRARY_PATH=/usr/java/jre1.6.0_31/lib/amd64/client:/usr/java/jre1.6.0_31/lib/amd64/server:/usr/java/jre1.6.0_31/lib/amd64/native_threads:/usr/java/jre1.6.0_31/lib/amd64

var_log_messages:
:Mar 22 01:33:25 mixer kernel: [23256.385025] soffice.bin[14784]: segfault at 0 
ip 0038d833b3c0 sp 7fffb5fcb4d8 error 4 in 
libc-2.15.so[38d820+1ac000]
:Mar 22 01:33:27 mixer abrt[16825]: Saved core dump of pid 14784 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-03-22-01:33:25-14784 (159457280 bytes)
:Mar 22 01:37:43 mixer kernel: [23514.362987] soffice.bin[16895]: segfault at 
80 ip 7effe549dc4c sp 7fff47c31590 error 4 in 
libsdlo.so[7effe51f8000+83a000]
:Mar 22 01:37:44 mixer abrt[17045]: Saved core dump of pid 16895 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-03-22-01:37:43-16895 (132120576 bytes)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097722/comments/0


On 2012-03-22T01:10:59+00:00 Michal wrote:

Created attachment 571893
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097722/comments/1


On 2012-03-22T01:11:04+00:00 Michal wrote:

Created attachment 571894
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097722/comments/2


On 2012-03-22T01:11:06+00:00 Michal wrote:

Created attachment 571895
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1097722/comments/3


On 2012-03-22T08:02:40+00:00 David wrote:

The sd a11y stuff evidently expects that a sd::ViewShell has a valid
sd::View . Unfortunately, that is not the case here.
sd::OutlineViewShell's constructor first calls ViewShell::doShow(),
which triggers this crash, and only _after_ that calls Construct(),
which initializes ViewShell::mpView .

Reply at:

[Bug 1189571] Re: [SRU] "Unable to set up timer: out of range" caused by bad 64_bit timer

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

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 2012-02-11T17:23:27+00:00 John wrote:

dhcpd fails after a while with:

Feb 11 17:19:18 pent dhcpd: Timeout requested too large reducing to 2^^32-1
Feb 11 17:19:18 pent dhcpd: Unable to set up timer: out of range
Feb 11 17:19:18 pent dhcpd[29451]: Timeout requested too large reducing to 
2^^32-1
Feb 11 17:19:18 pent dhcpd:
Feb 11 17:19:18 pent dhcpd[29451]: Unable to set up timer: out of range

dhcp-4.2.3-6.P2.fc16.x86_64

Removing or modifying lease options below seems to make no difference. I
don't know of a work-around.

dhcpd.conf is:

ddns-update-style interim;
authoritative;
ignore client-updates;

subnet 192.168.0.0 netmask 255.255.255.0 {
}

subnet 192.168.1.0 netmask 255.255.255.0 {

# --- default gateway
option routers  192.168.1.1;
option subnet-mask  255.255.255.0;

option nis-domain   "localdomain";
option domain-name  "localdomain";
option domain-name-servers  8.8.8.8;

#   option time-offset  -18000; # Eastern Standard Time

#   option ip-forwarding off;

default-lease-time infinite;
max-lease-time infinite;

host rent {
#   hardware ethernet 0:c0:9f:66:fa:fd;
#   hardware ethernet 0:0b:6b:4c:40:52;
hardware ethernet 0:1a:6b:6a:21:5b;
#   hardware ethernet 00:1b:77:5a:50:7b;
fixed-address 192.168.1.3;
option host-name "rent";
}

host argument {
hardware ethernet 00:12:3f:eb:7f:8f;
fixed-address 192.168.1.4;
option host-name "argument";
}

host sent {
hardware ethernet 00:1c:bf:42:fb:8a;
fixed-address 192.168.1.8;
option host-name "sent";
}

host went {
hardware ethernet 00:0f:b5:9f:c3:78;
fixed-address 192.168.1.100;
option host-name "went";
}

host parent {
hardware ethernet b8:ff:61:11:cc:34;
fixed-address 192.168.1.5;
option host-name "parent";
}

range 192.168.1.9 192.168.1.90;
}

Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/0


On 2012-02-11T17:49:20+00:00 John wrote:

It looks like the client with the request is an Android HTC phone.

Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/1


On 2012-02-13T17:45:16+00:00 John wrote:

In fact, if this really is dhcpd dying due to a bad request, this is a
big security hole.

Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/2


On 2012-02-13T17:53:22+00:00 Jiri wrote:

OK, marking as "Security Sensitive" for now. I'll look at the problem
tomorrow.

Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/3


On 2012-02-14T08:28:55+00:00 Jiri wrote:

Good news first: The problem is in code
(common/dispatch.c:add_timeout()) that was newly added in 4.2.0 so no
RHEL version is affected.

Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/4


On 2012-02-14T08:41:30+00:00 Jiri wrote:

We already once had a problem (bug #628258) with this part of code.
I reported the fix upstream but they chose a different solution, which 
obviously hasn't been perfect.
Their fix was released in 4.2.1b1 with this comment in changelog:
- Limit the timeout period allowed in the dispatch code to 2^^32-1 seconds.
  Thanks to a report from Jiri Popelka at Red Hat.
  [ISC-Bugs #22033], [Red Hat Bug #628258]

Reply at: https://bugs.launchpad.net/ubuntu/+source/isc-
dhcp/+bug/1189571/comments/5


On 2012-02-14T09:06:26+00:00 Jiri wrote:

John,

thank you for the report. It took me some time to get to it because from
the description I hadn't been aware of the fact that the server crashes.

Anyway this really looks like a security problem and to narrow it down
some packet dump is crucial (we need to see the message that came from
the client before server crashes). Are you able to get one ? You can

[Bug 1728198] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of p

2017-10-27 Thread Benjamin Hiebert

Public bug reported:

A problem when attempting to install WINE

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Oct 27 23:13:21 2017
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-mmR5Fg/103-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-10-27 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict package-from-proposed

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

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

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

[Bug 1728198] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of pac

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/1728198

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

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

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

[Bug 1728197] [NEW] Touchpad not working

2017-10-27 Thread Brixter John Lumabi

Public bug reported:

The touchpad of my Dell Inspiron 7460 is not working since I restarted
after upgrading to Ubuntu 17.10.

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

Title:
  Touchpad not working

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

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

[Bug 1719863] Re: ttf-mscorefonts installer error on 17.10

2017-10-27 Thread Andrei B.

I followed the solution on this page (get the .deb from Debian upstream) and it 
worked
https://askubuntu.com/questions/852302/failure-to-download-extra-data-files-ttf-mscorefonts-installer

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

Title:
  ttf-mscorefonts installer error on 17.10

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

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

[Bug 1726717] Re: Alignment of external screen limits placing of icons

** Changed in: nautilus
   Status: Unknown => Won't Fix

** Changed in: nautilus
   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/1726717

Title:
  Alignment of external screen limits placing of icons

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

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

[Bug 1486445] Re: Lots of zeitgeist errors

2017-10-27 Thread jimav

Also happening in 17.04

zeitgeist-datahub.vala:210: Error during inserting events:
GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete
event: interpretation, manifestation and actor are required

etc.

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

Title:
  Lots of zeitgeist errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions

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

[Bug 1715852] Re: Upgrade-software-version request for "pdfpc"

Generally, packages are only updated in stable Ubuntu releases to fix
high-priority bugs. Read this page for more information about how
updates work.

https://wiki.ubuntu.com/StableReleaseUpdates

Many packages in Ubuntu never get updates in stable releases. For a
"universe" package like this, it requires volunteers that are interested
in the package to prepare the update and verify that the updates fixes
the bugs without introducing other bugs.

** Also affects: pdf-presenter-console (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pdf-presenter-console (Ubuntu Xenial)
   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/1715852

Title:
  Upgrade-software-version request for "pdfpc"

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

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

[Bug 1722410] Re: java9: -version output seems wrong: "9-Ubuntu"

This bug was fixed in the package openjdk-9 - 9.0.1+11-1

---
openjdk-9 (9.0.1+11-1) unstable; urgency=medium

  * OpenJDK 9.0.1+11 release.
  * Bump standards version.
  * Configure with an empty --with-version-pre setting. LP: #1722410.
  * Remove JamVM packaging bits. Closes: #877523.
  * Remove Shark packaging bits.
  * Fix java/javac/jar lockups on SMP Alpha (Michael Cree). Closes: #875288.
  * Fix crashes in i386 applications using JNI due to Hotspot workaround for
Exec Shield (Ben Hutchings). Closes: #876069.
  * Re-enable building altzero architectures: Closes: #874292.
  * Update the zero-sparc patch (Adrian Glaubitz). Closes: #874265.
  * Fix recommendation of microhei/zenhei font packages. Closes: #868205.
  * Move jmod files into the openjdk-jdk-headless package. Closes: #878272.

 -- Matthias Klose   Fri, 27 Oct 2017 01:44:31 +0200

** Changed in: openjdk-9 (Ubuntu)
   Status: Confirmed => 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/1722410

Title:
  java9: -version output seems wrong: "9-Ubuntu"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1722410/+subscriptions

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

[Bug 1715852] Re: Upgrade-software-version request for "pdfpc"

This bug was fixed in the package pdf-presenter-console - 4.0.8-2

---
pdf-presenter-console (4.0.8-2) unstable; urgency=medium

  * Merge upstream fix (closes: #855525)

 -- Barak A. Pearlmutter   Mon, 11 Sep 2017 16:40:41
+0100

pdf-presenter-console (4.0.8-1) unstable; urgency=medium

  * New upstream release
  * Bump policy
  * Secure repo URL
  * Merge minor upstream doc mods

 -- Barak A. Pearlmutter   Thu, 31 Aug 2017 10:00:20
+0100

** Changed in: pdf-presenter-console (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/1715852

Title:
  Upgrade-software-version request for "pdfpc"

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

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

[Bug 1728194] [NEW] package libgcc1:i386 1:6.0.1-0ubuntu1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.

2017-10-27 Thread Ernesto Valencia

Public bug reported:

i cant install the update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgcc1:i386 1:6.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 libc6: Install
 libc6: Configure
 libgcc1: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Oct 27 21:35:09 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
DpkgHistoryLog:
 Start-Date: 2017-10-27  21:35:05
 Commandline: apt-get install -f
 Requested-By: ernesto (1000)
 Install: libc6:i386 (2.23-0ubuntu9, automatic)
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-09-22 (35 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gccgo-6
Title: package libgcc1:i386 1:6.0.1-0ubuntu1 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gccgo-6 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libgcc1:i386 1:6.0.1-0ubuntu1 failed to install/upgrade: El
  paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-6/+bug/1728194/+subscriptions

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

[Bug 1728193] Re: Can not upgrade from 17.04 to 17.10 using software updating tool

2017-10-27 Thread Ubuntu Foundations Team Bug Bot

** Tags added: zesty2artful

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

Title:
  Can not upgrade from 17.04 to 17.10 using software updating tool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1728193/+subscriptions

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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

** Changed in: fedora
   Status: Unknown => Expired

** 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/736171

Title:
  168c:002a ath: Failed to stop TX DMA in 100 msec after killing last
  frame

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

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

[Bug 846646] Re: GPL Ghostscript 9.04: Error: Font Renderer Plugin ( FreeType ) return code = -1

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

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 2012-01-27T13:06:06+00:00 Skippy wrote:

Description of problem:
When I run evince on ps files, I get many times the following error message in 
the terminal :
GPL Ghostscript 9.04: Error: Font Renderer Plugin ( FreeType ) return code = -1

Not sure if and how the display is affected.


Version-Release number of selected component (if applicable):
evince i686 3.2.1 2.fc16
ghostscript i686 9.04 7.fc16
ghostscript-fonts noarch 5.50 27.fc16


Additional info:
Ubuntu seems to be affected by a similar bug : 
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/7


On 2012-01-30T11:45:59+00:00 Skippy wrote:

(In reply to comment #0)
> Not sure if and how the display is affected.

Actually on the files I try to read, only the first page is displayed.  I can 
read them correctly if I process them through ps2pdf, although the following 
errors appears when viewing the PDF file with evince (not sure it is related, 
but in case it can help) :

Gtk-Message: Failed to load module "pk-gtk-module"
Entity: line 5: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xFF 0xFF 0xFF 0xFF
 0 && height > 0' failed

(evince:6529): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

I also only see the first page, and running gs directly on the
PostScript file works fine.

Changing component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/11


On 2013-01-16T15:54:22+00:00 Fedora wrote:

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/12


On 2013-02-13T19:04:45+00:00 Fedora wrote:

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/13


** Changed in: evince (Fedora)
   Status: Unknown => Won't Fix

** Changed in: evince (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/846646

Title:
  GPL Ghostscript 9.04: Error: Font Renderer Plugin ( FreeType ) return
  code = -1

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

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

[Bug 766153] Re: soffice.bin crashed with SIGSEGV in ImplServerFontEntry::HandleFontOptions()

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

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 2011-12-07T15:02:33+00:00 Miloslav wrote:

libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --impress 
IV054/CRYPTO0901.ppt IV054/CRYPTO0902.ppt IV054/CRYPTO0903.ppt 
IV054/CRYPTO0904.ppt IV054/CRYPTO0905.ppt IV054/CRYPTO0906.ppt 
IV054/CRYPTO0907.ppt IV054/CRYPTO0908.ppt IV054/CRYPTO0909.ppt 
IV054/CRYPTO0910.ppt IV054/CRYPTO0911a.ppt IV054/CRYPTO0912.ppt 
IV054/CRYPTO0914.ppt --splash-pipe=7
comment:Specified 13 ppt files to open on the command line
crash_function: X11SalGraphics::setFont
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.1.4-1.fc16.x86_64
pid:10780
pwd:/home/mitr/rh/prednasky
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed 
by signal 11 (SIGSEGV)
time:   St 7. prosinec 2011, 15:46:10 CET
uid:1000
username:   mitr

backtrace:  Text file, 94296 bytes
dso_list:   Text file, 22127 bytes
environ:Text file, 3181 bytes
maps:   Text file, 83821 bytes

var_log_messages:
:Dec  7 15:46:10 kulicka kernel: [17401.297261] soffice.bin[10780]: segfault at 
10 ip 7f1edb47a37b sp 7fff28162a40 error 4 in 
libvclplug_genlx.so[7f1edb3ee000+d6000]
:Dec  7 15:46:15 kulicka abrt[10843]: Saved core dump of pid 10780 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2011-12-07-15:46:10-10780 (275402752 bytes)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/2


On 2011-12-07T15:02:37+00:00 Miloslav wrote:

Created attachment 541989
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/3


On 2011-12-07T15:02:39+00:00 Miloslav wrote:

Created attachment 541990
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/4


On 2011-12-07T15:02:41+00:00 Miloslav wrote:

Created attachment 541991
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/5


On 2011-12-07T15:02:43+00:00 Miloslav wrote:

Created attachment 541992
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/6


On 2011-12-07T15:35:47+00:00 Miloslav wrote:

Package: libreoffice-core-3.4.4.2-3.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-
?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/7


On 2011-12-07T16:04:15+00:00 Caolan wrote:

If you can reproduce it, please attach a reproducer. Looks like the kind
of thing that needs a good valgrinding

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/8


On 2011-12-07T16:19:16+00:00 Miloslav wrote:

Created attachment 542027
The relevant files

In two tries, ooimpress didn't crash again just by running it with the
above command line.

However, in both cases it crashed using this procedure:
1. Focus the main slide pane.
2. Hold down Page Down until the last slide is displayed or the program crashes
3. If it didn't crash, close the current file using Ctrl-W and go to 1.

The behavior is somewhat random (once it crashed on the first file, once
it crashed on the 2nd or third), but it crashes often enough.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/9


On 2011-12-09T12:16:18+00:00 Caolan wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/10


On 2011-12-09T12:41:28+00:00 Caolan wrote:

refuses to crash for me. will try valgrind

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/766153/comments/11


On 2011-12-09T16:24:30+00:00 Caolan wrote:

Apparently a deleted font

[Bug 533493] Re: lvremove fails

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

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 2011-11-11T11:03:13+00:00 Artur wrote:

+++ This bug was initially created as a clone of Bug #712100 +++

+++ This bug was initially created as a clone of Bug #577798 +++

Description of problem:

# lvdisplay

  --- Logical volume ---
  LV Name/dev/vg01/.local.backup
  VG Namevg01
  LV UUIDhkAyO4-M31g-LJw5-Kdcu-AfK1-Bquw-buVrWA
  LV Write Accessread only
  LV snapshot status active destination for /dev/vg01/local
  LV Status  available
  # open 0
  LV Size2,00 GiB
  Current LE 512
  COW-table size 1,00 GiB
  COW-table LE   256
  Allocated to snapshot  0,01% 
  Snapshot chunk size4,00 KiB
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   253:29

# /dev/vg01/.local.backup
  Can't remove open logical volume ".local.backup"

  ... repeating this several times ...

# lvremove  /dev/vg01/.local.backup
Do you really want to remove active logical volume .local.backup? [y/n]: y
  Logical volume ".local.backup" successfully removed

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

kernel-2.6.33.1-19.fc13.x86_64
lvm2-2.02.61-1.fc13.x86_64

--- Additional comment from enrico.sch...@informatik.tu-chemnitz.de on
2010-03-29 05:52:00 EDT ---

Created attachment 403250
strace in non-working case

--- Additional comment from enrico.sch...@informatik.tu-chemnitz.de on
2010-03-29 05:52:28 EDT ---

Created attachment 403251
strace in working case

--- Additional comment from prajn...@redhat.com on 2010-03-29 06:08:36
EDT ---

Do you have "udisks" package installed? There is one udev rule that
could have possibly caused this...

For starters, just a quick check - could you please try to kill udev
daemon temporarily and see if you can reproduce the problem? Thanks.

--- Additional comment from enrico.sch...@informatik.tu-chemnitz.de on
2010-03-30 07:36:02 EDT ---

yes; udisks is installed and I can not reproduce the issue after its
removal.

'udevadm control --stop-exec-queue' before lvremove seems to work too.

--- Additional comment from prajn...@redhat.com on 2010-03-30 08:08:22
EDT ---

Just for the record, the rule we have problem supporting is this one
exactly (in /lib/udev/rules.d/80-udisks.rules which is a part of udisks
package):

# Make udevd synthesize a 'change' uevent when last opener of a rw-fd closes 
the fd - this
# should be part of the device-mapper rules
KERNEL=="dm-*", OPTIONS+="watch"

We have added udev synchronisation feature in device-mapper/lvm2
recently so we always wait until udev processing is settled down to cope
with such problems where devices are accessed from within udev rules and
also to provide a way to wait for nodes/symlinks to be created.

However, we can't synchronize with events synthesized as a result of
this rule (like we can't with events originating in "udevadm trigger"
which generates such events as well). The synchronisation could be done
on events we know about (events originated in device-mapper itself).

There are still ongoing discussions with udev team to properly deal with
this issue though...

Now, could you please keep the udisks package and also keep udev running
while having the "watch" rule commented out and see if the problem is
gone? Thanks.

(..so we're really sure this is exactly the case and as a proof)

--- Additional comment from enrico.sch...@informatik.tu-chemnitz.de on
2010-03-30 08:58:11 EDT ---

yes; after commenting out this line I can not reproduce the error
anymore.

--- Additional comment from prajn...@redhat.com on 2010-03-30 09:20:24
EDT ---

So we have another nice and practical example how the "watch" rule
disrupts an idea to properly synchronize with udev events...

--- Additional comment from prajn...@redhat.com on 2010-03-30 09:26:06
EDT ---

...also, CC-ing David (the "udisks" package maintainer).

--- Additional comment from enrico.sch...@informatik.tu-chemnitz.de on
2010-05-13 06:19:18 EDT ---

still with

lvm2-2.02.61-1.fc13.x86_64
udisks-1.0.1-1.fc13.x86_64

--- Additional comment from prajn...@redhat.com on 2010-05-17 09:07:01
EDT ---

(In reply to comment #9)
> still with
> 
> lvm2-2.02.61-1.fc13.x86_64
> udisks-1.0.1-1.fc13.x86_64

Unfortunately, we still don't have a proper solution for synchronization
with the events like the ones originated in the "watch" rule.

--- Additional comment from bugzilla-red...@brianneu.com on 2010-11-06
18:04:08 EDT ---

Is there a command that can be issues to

[Bug 652775] Re: WARNING: at /build/buildd/linux-2.6.35/include/net/mac80211.h:2601 rate_control_send_low+0xc2/0x140 [mac80211]()

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

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 2012-02-01T22:03:04+00:00 Mat wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:BOOT_IMAGE=/vmlinuz-3.2.2-1.fc16.x86_64 
root=/dev/mapper/vg_sd-lv_root ro rd.md=0 rd.dm=0 quiet 
SYSFONT=latarcyrheb-sun16 rhgb KEYTABLE=uk rd.luks=0 rd.lvm.lv=vg_sd/lv_swap 
rd.lvm.lv=vg_sd/lv_root LANG=en_US.UTF-8
kernel: 3.2.2-1.fc16.x86_64
reason: WARNING: at 
/builddir/build/BUILD/kernel-3.2.fc16/compat-wireless-3.3-rc1-2/include/net/mac80211.h:3618
 rate_control_send_low+0x23e/0x250 [mac80211]()
time:   Tue 31 Jan 2012 22:53:53 GMT

backtrace:
:WARNING: at 
/builddir/build/BUILD/kernel-3.2.fc16/compat-wireless-3.3-rc1-2/include/net/mac80211.h:3618
 rate_control_send_low+0x23e/0x250 [mac80211]()
:Hardware name: F3Sr
:Modules linked in: ppdev parport_pc lp parport fuse lockd ip6t_REJECT 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 
nf_defrag_ipv4 xt_state nf_conntrack uvcvideo videodev media 
v4l2_compat_ioctl32 snd_hda_codec_si3054 microcode snd_hda_codec_realtek 
snd_hda_intel arc4 snd_hda_codec snd_hwdep snd_seq snd_seq_device joydev r852 
snd_pcm sm_common nand nand_ids r592 mtd memstick nand_ecc iwl3945(O) iTCO_wdt 
iwlegacy(O) iTCO_vendor_support serio_raw mac80211(O) cfg80211(O) snd_timer 
asus_laptop snd soundcore sparse_keymap rfkill snd_page_alloc atl1 
input_polldev mii uinput sunrpc firewire_ohci sdhci_pci sdhci firewire_core 
crc_itu_t mmc_core video radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core 
[last unloaded: scsi_wait_scan]
:Pid: 3167, comm: kworker/u:50 Tainted: G   O 3.2.2-1.fc16.x86_64 #1
:Call Trace:
: [] warn_slowpath_common+0x7f/0xc0
: [] warn_slowpath_null+0x1a/0x20
: [] rate_control_send_low+0x23e/0x250 [mac80211]
: [] il3945_rs_get_rate+0x42/0x4a0 [iwl3945]
: [] ? il3945_mac_tx+0x5c6/0x8e0 [iwl3945]
: [] rate_control_get_rate+0x96/0x170 [mac80211]
: [] invoke_tx_handlers+0x6ff/0x13e0 [mac80211]
: [] ? ksize+0x1c/0xc0
: [] ? sta_info_get+0x6c/0x80 [mac80211]
: [] ieee80211_tx+0x60/0xc0 [mac80211]
: [] ieee80211_xmit+0x81/0xd0 [mac80211]
: [] ieee80211_tx_skb_tid+0x5f/0x70 [mac80211]
: [] ieee80211_send_probe_req+0x4f/0x70 [mac80211]
: [] ieee80211_mgd_probe_ap_send+0xdf/0x100 [mac80211]
: [] ? mutex_lock+0x1d/0x50
: [] ieee80211_sta_work+0x90/0x150 [mac80211]
: [] ieee80211_iface_work+0x2b8/0x350 [mac80211]
: [] ? ieee80211_teardown_sdata+0xe0/0xe0 [mac80211]
: [] process_one_work+0x11d/0x470
: [] worker_thread+0x15f/0x350
: [] ? manage_workers+0x230/0x230
: [] kthread+0x8c/0xa0
: [] kernel_thread_helper+0x4/0x10
: [] ? kthread_worker_fn+0x190/0x190
: [] ? gs_change+0x13/0x13

smolt_data:
:
:
:General
:=
:UUID: 302c32f3-8bc4-4089-85f1-57b729c25b1f
:OS: Fedora release 16 (Verne)
:Default run level: Unknown
:Language: en_GB.utf8
:Platform: x86_64
:BogoMIPS: 3990.50
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
:CPU Stepping: 13
:CPU Family: 6
:CPU Model Num: 15
:Number of CPUs: 2
:CPU Speed: 2001
:System Memory: 2004
:System Swap: 4031
:Vendor: ASUSTeK Computer Inc.
:System: F3Sr 1.0
:Form factor: Notebook
:Kernel: 3.2.2-1.fc16.x86_64
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Permissive
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Devices
:=
:(32902:17486:32902:17486) pci, None, MEMORY, Turbo Memory Controller
:(32902:10752:4163:5942) pci, None, HOST/PCI, Mobile PM965/GM965/GL960 Memory 
Controller Hub
:(32902:10753:32902:10753) pci, pcieport, PCI/PCI, Mobile PM965/GM965/GL960 PCI 
Express Root Port
:(6523:9056:4163:5942) pci, ahci, STORAGE, JMB360 AHCI Controller
:(32902:10281:4163:5942) pci, ahci, STORAGE, 82801HBM/HEM (ICH8M/ICH8M-E) SATA 
AHCI Controller
:(32902:10320:4163:5942) pci, ata_piix, STORAGE, 82801HBM/HEM (ICH8M/ICH8M-E) 
IDE Controller
:(32902:10261:4163:5942) pci, None, PCI/ISA, 82801HEM (ICH8M) LPC Interface 
Controller
:(6505:4168:4163:5349) pci, atl1, ETHERNET, L1 Gigabit Ethernet
:(32902:10289:4163:5942) pci, uhci_hcd, USB, 82801H (ICH8 Family) USB UHCI 
Controller #2
:(32902:9288:4163:5942) pci, None, PCI/PCI, 82801 Mobile PCI Bridge
:(32902:10290:4163:5942) pci, uhci_hcd, USB, 82801H (ICH8 Family) USB UHCI 
Controller #3
:(32902:10294:4163:5942) pci, ehci_hcd, USB, 82801H (ICH8 Family) USB2 EHCI 
Controller #1
:(32902:10298:4163:5942) pci, ehci_hcd, USB, 82801H (ICH8 Family) USB2 EHCI 
Controller #2
:(4480:2130:4163:5942) pci, r852, BASE, xD-Picture Card Controller

[Bug 846878] Re: empty space between time applet and nm-applet

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

On 2011-12-09T09:01:33+00:00 Thomas wrote:

Description of problem:
Each time I resume my EeePC 901 the notification area in lxpanel becomes bigger
by adding an invisible icon on each side.

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

How reproducible:
Suspend/resume

Steps to Reproduce:
1. Run LXDE with parcellite, xfce power manager and network manager
2. Suspend
3. Resume

Actual results:
Wider notification area

Expected results:
The same notification area as before

Additional info:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/26

On 2011-12-11T18:31:14+00:00 Christoph wrote:

Thanks for reporting this bug. I cannot reproduce, therefor I need more
input from you.

When you right-click on an empty spot in the notification area, do you
see a menu or just nothing happens?

Can you try lxpanel from updates-testing?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/28

On 2011-12-11T20:52:32+00:00 Thomas wrote:

Thanks for responding.
I just see the void of space and nothing happens.
I will try to enable updates-testing and report back.
Greetings from Münster ;-)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/30

On 2011-12-12T20:19:04+00:00 Thomas wrote:

Did the yum update lxpanel with update-testing enabled and the problem
persists.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/31

On 2011-12-16T15:39:26+00:00 Freddy wrote:

I think I have found a workaround for the time being. Put the script
below in /etc/pm/sleep.d dir (for example in 01powermanager). Put your
own username in the right spot, maybe change your display number if
applicable.

#!/bin/bash

case $1 in
thaw|resume)
su - -c "export DISPLAY=:0 &&
/usr/bin/xfce4-power-manager --restart"
exit 0
;;
*) exit $NA
;;
esac

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/34

On 2012-01-10T07:30:14+00:00 Thomas wrote:

The workaround kinda sometimes works, but a real fix it certainly isn't.
The notification area is still expanding. Anybody still working on this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/38

On 2012-02-03T22:52:46+00:00 Michael wrote:

Here is the upstreambug on the xfce4-project
https://bugzilla.xfce.org/show_bug.cgi?id=8424

LXDE project
http://sourceforge.net/tracker/index.php?func=detail=3458395_id=180858=894869

Lubuntu
https://bugs.launchpad.net/xfce4-power-manager/+bug/846878

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/48

On 2012-02-26T10:17:27+00:00 Christoph wrote:

Argh, I had the necessary patch already in the F16 package for quite a
while but I did not update F15. This explains why only a F15 user
complains.

Thanks for Michael to the pointer in the LP bug report!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/56

On 2012-02-26T10:18:01+00:00 Michael wrote:

Please see my last comments:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878

we have a working patch
http://git.xfce.org/xfce/xfce4-power-manager/commit/?id=643962eb2d46d48042db0ab278c46813da8b6e9b

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/57

On 2012-02-26T10:19:10+00:00 Fedora wrote:

xfce4-power-manager-1.0.10-3.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/xfce4-power-manager-1.0.10-3.fc15

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/846878/comments/58

On 2012-02-27T00:47:43+00:00 Fedora wrote:

Package xfce4-power-manager-1.0.10-3.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should

[Bug 889104] Re: virt-manager loses connection to qemu (0.15.X) at guest shuts down (libvirt 0.9.6)

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

** Changed in: libvirt (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/889104

Title:
  virt-manager loses connection to qemu (0.15.X) at guest shuts down
  (libvirt 0.9.6)

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

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

[Bug 786730] Re: [10.04 LTS] emacs spins when ssh is uncleanly terminated

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

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 2011-12-21T17:15:15+00:00 RHEL wrote:

This bug has been copied from bug #732157 and has been proposed
to be backported to 6.2 z-stream (EUS).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/786730/comments/10


On 2012-01-09T12:23:45+00:00 Miroslav wrote:


Technical note added. If any revisions are required, please edit the 
"Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content 
Services team.

New Contents:
Emacs did not properly terminate if it was started remotely and the remote 
client session was closed while Emacs was suspended. Under these conditions, 
Emacs entered an infinite loop in the code and gradually consumed all available 
computer resources, which caused the system to become unstable. With this 
update, Emacs has been modified, and it now terminates correctly when the 
remote session is closed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/786730/comments/11


On 2012-01-23T09:11:33+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.

http://rhn.redhat.com/errata/RHBA-2012-0042.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/786730/comments/12


** Changed in: fedora
   Status: Unknown => Fix Released

** Changed in: fedora
   Importance: Unknown => Critical

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

Title:
  [10.04 LTS] emacs spins when ssh is uncleanly terminated

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

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

[Bug 872044] Re: Bluetooth 'Send files' returns permission denied error

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

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 2011-11-13T19:14:17+00:00 Saurav wrote:

Description of problem:
The Bluetooth userspace utilities do not work properly on kernels newer than
2.6.38. In particular, sending files by Bluetooth from the computer to a remote
device (obex push) fails. The problem occurs on both Fedora 15 with the latest 
updates and Fedora 16. On Fedora 16, the Bluetooth adaptor is functional
only if the bluez-hid2hci package is installed.

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

How reproducible:
On a Fedora 16 system with the bluez-hid-2hci package installed, turn on
Bluetooth and try to send a file via Bluetooth to a remote device such as a
mobile phone.

Steps to Reproduce:
1. On Fedora 16, if package bluez-hid2hci is not installed, install it.
2. Turn on Bluetooth (system adaptor).
3. Try to send a file to a remote device such as a mobile phone.

Actual results:
gnome-blueooth either crashes or fails to send file to remote device.

Expected results:
File gets transferred successfully.

Additional info:
There are various manifestations of this bug on different Linux distributions, 
including crashing, failing with the error message, "Connection refused" and 
failing with the error code 111.

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/21

On 2011-11-13T19:19:11+00:00 Saurav wrote:

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

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/22

On 2011-11-18T02:21:57+00:00 Adam wrote:

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/27

On 2011-11-18T05:03:17+00:00 Michael wrote:

I'm not so sure it's the kernel. I could receive files on Fedora 15 (3.0
kernel) just fine. On F16 it fails to send, receive, or browse. Pairing
works fine, but repairing doesn't fix anything. It fails with SELinux
enabled or in permissive mode.

I see this in my /var/log/messages after trying to send a file.

Nov 17 22:45:04 mcronenworth obex-client[441]: obex-client daemon 0.42
Nov 17 22:45:04 mcronenworth bluetoothd[976]: Mode session 0x7f8c953c4840 with 
:1.470 activated
Nov 17 22:45:04 mcronenworth bluetoothd[976]: bluetoothd[976]: Mode session 
0x7f8c953c4840 with :1.470 activated
Nov 17 22:45:17 mcronenworth obex-client[441]: Transfer(0xf9e630) Error: 
Unknown response
Nov 17 22:45:17 mcronenworth dbus[1100]: [system] Rejected send message, 2 
matched rules; type="method_return", sender=":1.1" (uid=0 pid=976 
comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" error 
name="(unset)" requested_reply="0" destination=":1.470" (uid=502 pid=441 
comm="/usr/libexec/obex-client ")
Nov 17 22:45:17 mcronenworth dbus-daemon[1100]: dbus[1100]: [system] Rejected 
send message, 2 matched rules; type="method_return", sender=":1.1" (uid=0 
pid=976 comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" 
error name="(unset)" requested_reply="0" destination=":1.470" (uid=502 pid=441 
comm="/usr/libexec/obex-client ")

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/28

On 2011-11-18T05:49:21+00:00 Michael wrote:

Installing bluez-hid2hci does allow browsing to work, but file transfers
(to or from) do not work.

Reply at: https://bugs.launchpad.net/gnome-
bluetooth/+bug/872044/comments/29

On 2011-11-18T10:38:33+00:00 Saurav wrote:

(In reply to comment #3)
> I'm not so sure it's the kernel. I could receive files on Fedora 15 (3.0
> kernel) just fine. On F16 it fails to send, receive, or browse. Pairing works
> fine, but repairing doesn't fix anything. It fails with SELinux enabled or in
> permissive mode.
> 
> I see this in my /var/log/messages after trying to send a file.
> 
> Nov 17 22:45:04 mcronenworth obex-client[441]: obex-client daemon 0.42
> Nov 17 22:45:04 mcronenworth bluetoothd[976]: Mode session 0x7f8c953c4840 with
> :1.470 activated
> Nov 17 22:45:04 mcronenworth bluetoothd[976]: bluetoothd[976]: Mode session
> 0x7f8c953c4840 with :1.470 activated
> Nov 17 22:45:17 mcronenworth obex-client[441]: Transfer(0xf9e630) Error:
> Unknown response
> Nov 17 22:45:17 mcronenworth

[Bug 904505] Re: Flash doesn't work in WebKitGTK3 browsers

** Changed in: epiphany-browser (Fedora)
   Status: Unknown => Invalid

** Changed in: epiphany-browser (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/904505

Title:
  Flash doesn't work in WebKitGTK3 browsers

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

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

[Bug 898336] Re: tumblerd crashed with SIGSEGV in g_type_check_instance_is_a()

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

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 2011-11-18T11:52:32+00:00 Ralf wrote:

libreport version: 2.0.6
abrt_version:   2.0.4.981
backtrace_rating: 4
cmdline:/usr/lib64/tumbler-1/tumblerd
comment:No idea how to reproduce it. Machine was unattended when this 
segfault occurred.
crash_function: g_type_check_instance_is_a
executable: /usr/lib64/tumbler-1/tumblerd
kernel: 3.1.1-1.fc16.x86_64
reason: Process /usr/lib64/tumbler-1/tumblerd was killed by signal 11 
(SIGSEGV)
time:   Fri Nov 18 12:46:05 2011
uid:8690
username:   corsepiu

backtrace:  Text file, 48448 bytes
maps:   Text file, 37025 bytes

build_ids:
:1ddf6e597ba6f382f8490a52401f6905b9715abb
:80d1527bdbaa66a7f4467a3432a25332fb76758a
:5ffc709ae37f52d7d0743329a39f1b83e5493827
:1c6a95451ee19617be5abea3d121f0226d21ddda
:08325b64e0774167b3ade9126c3971ae6de9a4a6
:44ece411beb2ef1acdb5eb2161666de41cc2f31d
:98fa95d21e16075ada6df19748c6c133ee9165d0
:b5a67213cba87f4e37046b7b7728a1eb4e7aff07
:e3c88cb9ea428bd61f4064dbd53acae2d396a1ec
:dd09997b3723567329e48ecd0d4bac542c0a903c
:87461d97d0ba0bd94e4d74ff0879190b67b326c5
:72ea6ca9c81b71bba99cb18620abb9029a87927c
:5e8c36ca13a4af14fa6b1b45a0dbfb43ed6aed6e
:722092ce63f29994224c42970e34d60a30a80e46
:a70947162966aa69c7ac92b53dcd9e6748cffe35
:9e3a33f915a032d57db9e51c90f1b295fc9e425c
:a47e3764e7de48ace1ecfcfd8c2e0c49bd8cf1a3
:30af62b93e2ab7dbaf39c52e346cd52101b4b590
:9d1209fc79304f03cc839de1c0036c61b48dfff8
:3e08f14ed2767ff642c7477a25b63214050e42cb
:9af722e8d4717709aa49739efc0ed10d0f952e3e
:fa1cfd183d984f9b0a77a35f5da619fe71da5fe2
:48d3cff26c916dff6cbcb5e67d5cf6d391f6ccca
:8264e35452b2a930c1b9b092b87f32d42d69d8c5
:e7d37d7c1c48886f369bf4cc2eb07134faf900e0
:09834b108bacbb167847d374f4cd9965ce8c78f0
:b502249bcf2a4f465feeb8b9578c80cda6f4103d
:c8a4e40c84c2f52e78c64d31efc0191c565a9049
:921b64859b34786348daf376801c05efbf9bac81
:8acc43df965b3c0a70dcfad11c0ade056bdb055b
:106981fc8c382f3593c7326d039e026b11dd9ba5
:4953d1f613914126bccceb3cb96386647ffba9df
:db0921d37dbfcfc6115a7a4aeb0c6928c08abd1c
:0911ea7c180d733724f89037b8e8a34e64024aec
:6e7d3edc38bf427fb8cb8dd115b5e23b5b1b1854
:48aea888319e1848137073c9cbde54a4c2a731c9
:400aa053edc0e34645dd535201f1a1395573a681
:7055a3f0dc1ecedda325c75912ccb1fbe361013c
:bed3a3de569d0a8795d948f4630b7e6af3566d36
:a07d8451a42fb256942df953f790ded8f6b5b372
:2636afe466ed20d65ac6d8fc08f1b120974f9ceb
:b0eabf9093defbfdd0857ea3ed1a4563b743434e
:fe59af234d3adcdbdfc45a81c2099c3529d5b37d
:4c842320387ff7f6f91b7842b223c16518be909f
:c3df263f0b70a9fff51c727bd49c52f0794b9f9e
:68d260a8e19b5758a2ca3a8bf6a9e3a49a6d6bfd
:ec16722d991717e07e829bef2955435824df5083
:ebb2f0a89bbd1ef97f373a99cb44d4c968d2579f
:017a0c9c46d30256c1d6af189b4809146ef312f6
:7994f114cf7189e482f2665fae8e351ed8bc05e3
:94e29139152ba767534403cf94a672fe6b3fe515
:ee03ac98c3ac61b47aa163886a17cc1e0c491906
:be507c791e34415e8f42f0e6030c889b2895cf9a
:33fcde0445e582dff00a8703873e1863ff1ca547
:3d22dd762f2430ac679e61c98e8d856e5f3423ed
:28f59ffca68245ca3e236e5a26db1e2a1d86e0d7
:437b7f944169cc3842441dd7b9be2973207ee72e
:632e2d2fe66298723101ff693447d3b3fc1af720
:b475123058f5a0538c0592eaf40ec27bac64a2d0
:ccadad4ec7dab3bb6abc23f9d4cdf53ff01cb235
:e5d7ac2dfe435e205e491f7ce827563859fca4f4
:b453c88fcaacf75c19ab1c941fc008d752bce86c
:3e2404bd469800afd61eda83d0292a2165ef0db0
:3b50812827b755646178db9447ced77425add5d8
:c5e42d196957e22b2106b6ed9144f0baff42a9c0
:2e979936a64ecafe4d85a5b4f07e594415691d38
:11307731c4aa95e08b6de3064d064a12d12dee8f
:ea561edd4a545276e281c0c1f3d51fb6d5f7dcb6
:56d0d755b880afdd9ebf2c8c707282384fed90fd
:c85b0533529a1a79855cc4e765885b9af1ef8b9e
:c3a3e49f393f383721c6485dab54a620d7b9da52
:3afcef19b83b4d703cf89db41982aabaa2d1618b
:650b733aecfb9c46bdfc023661f19244a278df04
:b0a2d0b4c09d819887ec7d711c8cf3977a074c4f
:a518a8b1b5c3e80dee813df05e951d205d6ac48c
:375ad839663dc5e07d4b27e624d49c8922895e08
:5f68fecc89bbb7cf2200b4caed6fb26006a189b7
:88d586ed67ebe5227b761b4ab2e02433f29c840f
:b67d01f9230119a215e7151dc3aa43428b886c8f

dso_list:
:/usr/lib64/gstreamer-0.10/libgsta52dec.so 
gstreamer-plugins-ugly-0.10.18-3.fc16.x86_64 (RPM Fusion) 1321275470
:/lib64/libm-2.14.90.so glibc-2.14.90-14.x86_64 (Fedora Project) 1321083865
:/usr/lib64/libxcb.so.1.1.0 libxcb-1.7-3.fc16.x86_64 (Fedora Project) 1321083877
:/usr/lib64/libpoppler.so.18.0.0 poppler-0.18.0-2.fc16.x86_64 (Fedora Project) 
1321241319
:/usr/lib64/libgstaudio-0.10.so.0.24.0 
gstreamer-plugins-base-0.10.35-3.fc16.x86_64 (Fedora Project) 1321086912
:/usr/lib64/libgvfscommon.so.0.0.0 gvfs-1.10.1-2.fc16.x86_64 (Fedora Project) 
1321084238

[Bug 894782] Re: Newline injection in error.log

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

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 2011-12-15T21:53:42+00:00 Kurt wrote:

A security bug was reported by Moritz Naumann against icecast in
Ubuntu. You are being emailed as the upstream contact. Please keep
oss-secur...@lists.openwall.com[1] CC'd for any updates on this issue.

This issue should be considered public and has not yet been assigned a
CVE.

Details from the public bug follow:
https://launchpad.net/bugs/894782

>From the reporter:
"Newline injection in error.log

Running this command against an icecast2 running on 127.0.0.1...

echo -ne "GET /non-existent"'"'"%20No%20such%20file%20or%20directory%0d%
0a[1970-01-01%20%2000:00:00]%20PHUN%20I'm%20feeling%20phunny%0d%
0a["`date "+%Y-%m-%d%%20%%20%H:%M:%S"`"]%20WARN%
20fserve/fserve_client_create%20req%20for%20file%
20"'"'"/usr/share/icecast2/web/ HTTP/1.0\n\n" | nc -vv 127.0.0.1 8000
> /dev/null
...causes the following to be written to /var/log/icecast2/error.log:
[2011-11-25 15:37:31] INFO fserve/fserve_client_create checking for
file /non-existent" No such file or directory
[1970-01-01 00:00:00] PHUN I'm feeling phunny
..."

Thanks in advance for your cooperation in coordinating a fix for this
issue.

[1] oss-secur...@lists.openwall.com is a public mailing list for
people to collaborate on security vulnerabilities and coordinate
security updates.

-- Jamie Strandboge | http://www.canonical.com

Reply at:
https://bugs.launchpad.net/ubuntu/+source/icecast2/+bug/894782/comments/6

On 2011-12-15T22:44:51+00:00 Vincent wrote:

Created icecast tracking bugs for this issue

Affects: fedora-all [bug 768175]
Affects: epel-5 [bug 768176]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/icecast2/+bug/894782/comments/7

On 2012-06-15T18:24:56+00:00 Vincent wrote:

This is corrected in upstream 2.3.3 version (released June 11th):

http://www.icecast.org/

Reply at:
https://bugs.launchpad.net/ubuntu/+source/icecast2/+bug/894782/comments/25

On 2014-02-11T05:45:08+00:00 Murray wrote:

https://bugzilla.novell.com/show_bug.cgi?id=862096 notes the
icecast-2.3.2-CVE-2011-4612.diff introdces a use-after-free flaw and
should be removed (since the issue was fixed upstream). I could not find
this patch in Fedora or EPEL 6.

EPEL 6 is missing from the trackers here ... but it seems to have the
fixed version now, so I will not file one.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/icecast2/+bug/894782/comments/42

** Changed in: icecast2 (Fedora)
   Status: Invalid => Fix Released

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

** Bug watch added: Novell/SUSE Bugzilla #862096
   https://bugzilla.novell.com/show_bug.cgi?id=862096

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

Title:
  Newline injection in error.log

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

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

[Bug 903212] Re: libvirtd stops responding in oneiric

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

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 2011-11-26T19:00:51+00:00 Steven wrote:

Description of problem:
Not exactly sure how to reproduce the problem.  I am doing quite a bit of heavy 
development that uses libvirt.  The libvirtd.log file prints out:

11:25:21.784: 24375: error : virNetServerDispatchNewClient:220 : Too many 
active clients (20), dropping connection from 127.0.0.1;0
11:25:23.926: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:23.926: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:23.926: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:23.926: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:23.926: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:23.926: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:23.935: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.648: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.655: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.656: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.656: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:25:41.656: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:33:39.736: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error
11:33:39.736: 24375: error : virNetSocketReadWire:912 : End of file while 
reading data: Input/output error

A second process is spawned by libvirt as well:
root 22049 24375  0 11:49 ?00:00:00 libvirtd --daemon
root 22353 22671  0 11:58 pts/400:00:00 grep --color=auto libvirt
root 24375 1  2 11:00 ?00:01:40 libvirtd --daemon

kill -9 of the non-init parented libvirt unsticks the system ie:
[root@beast libvirt]# kill -9 22049

Then things start working again.


Version-Release number of selected component (if applicable):
[root@beast libvirt]# rpm -qa | grep libvirt
libvirt-0.9.6-2.fc16.x86_64
libvirt-python-0.9.6-2.fc16.x86_64
libvirt-client-0.9.6-2.fc16.x86_64


How reproducible:
hard to reproduce

Steps to Reproduce:
1. execute vm starts/stops 
2.
3.
  
Actual results:
libvirt launches a second process and wedges

Expected results:
libvirt should not wedge

Additional info:

killing the second process unwedges libvirt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/903212/comments/0


On 2011-11-28T23:08:25+00:00 Steven wrote:

Not sure if too many active clients error from log is related to the
second process being spawned.  They may be separate events.  I have
changed my program behavior not to use so many sockets, but occasionally
the software still wedges.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/903212/comments/1


On 2011-11-28T23:10:51+00:00 Steven wrote:

Notice the CPU time on the forked process is quite high.  This ps was
taken ~1-2 minutes after the system wedged.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/903212/comments/2


On 2011-11-28T23:13:20+00:00 Steven wrote:

ignore comment #2, the 2nd process in the list wasn't the forked child.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/903212/comments/3

[Bug 912030] Re: The auto.net script that comes with autofs5 is broken

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

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 2012-01-16T17:45:00+00:00 Paul wrote:

Created attachment 63
Fix auto.net to ignore duplicate export partitions

Description of problem:

For NFS servers which export the same partition with different options
(for example, a partition might be exported to one system with root
privileges enabled and all other systems with root squash enabled--this
is a common scenario in Enterprise environments), the /net automount map
fails to find ANY exported partitions.

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

This issue is present in all versions of autofs 4 and autofs 5 that I've
checked.

How reproducible:

100%.

Steps to Reproduce:
1. Configure an NFS server to export the same partition in two different ways 
and export them.  When you run showmount -e against that host you should see 
multiple entries like this:
~$ showmount -e snap-dev01
Export list for snap-dev01:
/user 172.0.0.0/8
/tools172.0.0.0/8
/projects 172.0.0.0/8
/user devtools
/toolsdevtools
/projects devtools
The server doesn't have to be running Red Hat (or even Linux); it's not a 
server problem.

2. On a client (running Red Hat), attempt to access one of these
partitions through the /net automount map as it comes configured by
default:

  
Actual results:

~$ ls /net/snap-dev01/tools/.
ls: cannot access /net/snap-dev01/tools/.: No such file or directory

Expected results:

~$ ls /net/snap-dev01/tools/.
bin etc infoman sbin
distinclude lib share   tmp

Additional info:

I filed a bug against Ubuntu autofs4 back in 2007 and they did fix it
there:

https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/111612

I've recently discovered that this problem still exists in the latest
Ubuntu for autofs5 and I filed a bug there as well:

https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030

The bug is in the default auto.net handling script that comes with
autofs, so I also sent a bug report upstream to the autofs maintainers
at aut...@vger.kernel.org but unfortunately that mailing list doesn't
appear to be archived anywhere anymore so I can't give you a link.

I've attached my patch to fix the problem here as well.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030/comments/1


On 2012-05-09T03:34:31+00:00 yanfu wrote:

>From Ian's advice:
This is a change to the auto.net script which is not our recommended way to use 
the hosts map. So, I think sanity only is sufficient for this one. 
The old /etc/auto.net is below:
$SHOWMOUNT | LC_ALL=C sort -k 1 | \
Confirm the /etc/auto.net in new autofs-5.0.5-54.el6:
$SHOWMOUNT | LC_ALL=C cut -d' ' -f1 | LC_ALL=C sort -u | \

Reply at:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030/comments/2


On 2012-06-20T14:46:51+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.

http://rhn.redhat.com/errata/RHBA-2012-0951.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030/comments/3


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

** Changed in: autofs5 (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/912030

Title:
  The auto.net script that comes with autofs5 is broken

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

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

[Bug 911642] Re: system-config-printer.py crashed with SIGSEGV in debug_lookup_classname_int()

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

** Changed in: samba (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/911642

Title:
  system-config-printer.py crashed with SIGSEGV in
  debug_lookup_classname_int()

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

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

[Bug 922821] Re: ecryptfs-utils can't find renamed blowfish kernel modules in >= 3.2

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

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 2012-01-27T03:10:09+00:00 Ling wrote:

ecryptfs doesn't provide blowfish as one of the cipher options.
Rebooting into an old kernel (e.g., 3.1.9) solves the problem.  Does
this mean the blowfish encryption module is removed from the kernel
3.2.1?

Reply at: https://bugs.launchpad.net/ecryptfs/+bug/922821/comments/0


On 2012-01-27T16:58:31+00:00 Josh wrote:

There are now two kinds of blowfish drivers in the 3.2 kernel.
blowfish_generic is the previously existing one renamed, and there is an
assembly version for x86_64 as well.

Can you paste the errors you are seeing, and the dmesg of your working
mount from the previous kernel?

Reply at: https://bugs.launchpad.net/ecryptfs/+bug/922821/comments/1


On 2012-01-27T17:14:48+00:00 Ling wrote:

Here's what I did/saw with the 3.2 kernel:

# ecryptfs-add-passphrase --fnek
Passphrase: 
Inserted auth tok with sig [4c0c36bbcda400d6] into the user session keyring
Inserted auth tok with sig [d697d8aafc7fde3d] into the user session keyring

# mount encrypted encrypted -t ecryptfs
Select key type to use for newly created files: 
 1) passphrase
 2) openssl
 3) tspi
 4) pkcs11-helper
Selection: 1
Passphrase: 
Select cipher: 
 1) aes: blocksize = 16; min keysize = 16; max keysize = 32 (loaded)
 2) des3_ede: blocksize = 8; min keysize = 24; max keysize = 24 (not loaded)
 3) cast6: blocksize = 16; min keysize = 16; max keysize = 32 (not loaded)
 4) cast5: blocksize = 8; min keysize = 5; max keysize = 16 (not loaded)

There's no "blowfish" option.  Passing "-o ecryptfs_cipher=blowfish" in
the mount command leads to some bad option error.


With kernel 3.1.9, the only dmesg of mounting the ecryptfs is this line:

[23314.085489] SELinux: initialized (dev ecryptfs, type ecryptfs), uses
genfs_contexts

There are no new messages in /var/log/messages from the mounting.

Thanks.

Reply at: https://bugs.launchpad.net/ecryptfs/+bug/922821/comments/2


On 2012-01-27T20:06:28+00:00 Josh wrote:

If you run 'sudo modprobe blowfish' before you mount the filesystem, the
blowfish option will be presented.

I'll look at why this isn't done automatically as with previous kernels.

Reply at: https://bugs.launchpad.net/ecryptfs/+bug/922821/comments/3


On 2012-01-27T20:16:47+00:00 Ling wrote:

You are right.  It shows up.  (I remember I did that once but somehow it
didn't find blowfish;  I must have used a wrong cmd.)

Reply at: https://bugs.launchpad.net/ecryptfs/+bug/922821/comments/4


On 2012-01-27T20:49:02+00:00 Josh wrote:

This seems to be a bug in ecryptfs-utils.

During init, ecryptfs-utils will look at /proc/crypto to gather the
already loaded ciphers.  Some of the aes modules are built into the
kernel, so those are already picked up from there, however the blowfish
cipher isn't built in or auto-loaded by anything in either kernel
version.

It's next form of cipher discovery has a map of ciphers and kernel
module names in src/libecryptfs/cipher_list.c that contains (among
others):

{"blowfish", "blowfish.ko", 16, 16, 56, 2, 1},

and during init it will loop over this map and look for modules in
/lib/modules/`uname -r`/kernel/crypto and see if those .ko files exist.
If they do, it presents the cipher name as available.  If the .ko
doesn't exist in that directory, it doesn't present that cipher as an
option.

With the 3.1.x series of kernels, blowfish.ko is present so it's
available.  With the renames/additions mentioned in comment #1, that
specific .ko name isn't present so the cipher isn't available.

Ideally, ecryptfs would be looking at modaliases instead of actual file
names, because the 3.2 (and future) kernels still maintain the
'blowfish' modalias on blowfish_generic.ko.  The newly added optimized
blowfish-x86_64.ko has the same alias as well.  That whole list of
module names seems fairly stale at this point and should probably either
be updated or removed.

I'm reassigning this to ecryptfs-utils for now.  The workaround is to
modprobe the cipher you want if it isn't already listed before trying to
mount an ecryptfs filesystem.  Until ecryptfs-utils is updated, any
system with a 3.2 or newer kernel will have this issue, so that will
shortly include all 3 Fedora releases.

Reply at:

[Bug 929888] Re: ldap_result returns -1 when called from sssd

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

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 2012-01-03T21:06:45+00:00 Ken wrote:

Description of problem:
sssd ID searches break with openldap-2.4.28-1.fc17.

How reproducible:
Always

Steps to Reproduce:
1. Set up sssd on a Rawhide box
2. Run getent passwd , eg. "getent passwd kdreyer"

Actual results:
(user is not found)

Expected results:
kdreyer:*:500:100:Ken Dreyer:/home/kdreyer:/bin/bash

Additional info:

My LDAP server is CentOS 5, openldap-servers-2.3.43-12.el5_7.10

(regular openldap-clients commands in 2.4.28-1.fc17, for example
ldapwhoami, or ldapsearch, work fine against this server. It is only
sssd that breaks here.)

In the sssd_KTDREYER.log:

(Tue Jan  3 12:12:11 2012) [sssd[be[KTDREYER]]] [simple_bind_send] (0x0100): 
Executing simple bind as: (null)
(Tue Jan  3 12:12:11 2012) [sssd[be[KTDREYER]]] [simple_bind_send] (0x2000): 
ldap simple bind sent, msgid = 2
(Tue Jan  3 12:12:11 2012) [sssd[be[KTDREYER]]] [sdap_process_result] (0x2000): 
Trace: sh[0xb8eee4c0], connected[1], ops[0xb8f76e10], ldap[0xb8ee1ca0]
(Tue Jan  3 12:12:11 2012) [sssd[be[KTDREYER]]] [sdap_process_result] (0x0100): 
ldap_result gave -1, something bad happend!
(Tue Jan  3 12:12:11 2012) [sssd[be[KTDREYER]]] [sdap_handle_release] (0x2000): 
Trace: sh[0xb8eee4c0], connected[1], ops[0xb8f76e10], ldap[0xb8ee1ca0], 
destructor_lock[0], release_memory[0]
(Tue Jan  3 12:12:11 2012) [sssd[be[KTDREYER]]] [remove_connection_callback] 
(0x4000): Successfully removed connection callback.
(Tue Jan  3 12:12:11 2012) [sssd[be[KTDREYER]]] [fo_set_port_status] (0x0100): 
Marking port 636 of server 'salt.ktdreyer.com' as 'not working'

My sssd config is working fine on EL5, EL6, and F15. Thanks to sgallagh in 
#sssd, I found out that when I dowgrade openldap to 2.4.26-5.fc17, sssd works 
again.
http://koji.fedoraproject.org/koji/buildinfo?buildID=267220

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/comments/0

On 2012-01-03T21:13:49+00:00 Stephen wrote:

There is a regression in openldap-libs somewhere between 2.4.26-5.fc17
and 2.4.28-1.fc17. We don't get any useful information from openldap, we
only receive -1 back from ldap_result().

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/comments/1

On 2012-01-30T11:47:25+00:00 Jan wrote:

I managed to reproduce this with openldap-2.4.28-2. However, after
playing around with gdb trying to find out some more info about what's
going on, it started to work and I can't reproduce this anymore. I
really have no idea what happened. I didn't change any setting or
anything in ldap database.

Here is roughly what I did:
1. run sssd -d 10 -i
2. find sssd_be pid and run gdb
3. attach gdb to sssd_be process
4. set breakpoint at sdap_async.c:1019
5. run getent passwd jsyna...@domain.com
6. make few steps in gdb, then continue

Any ideas about what might have gone wrong? (or more precisely, gone
'right' in this particular case)

I know that attaching gdb to a process makes the process pause, so maybe
the execution order changed somehow. What really escapes me, though, is
why I can't reproduce this after I restart the sssd and slapd, or even
reboot the machine.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/comments/2

On 2012-01-30T11:53:32+00:00 Jan wrote:

Ah ok, I removed the cache file and it's reproducible again. But still
not sure why it started to work.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/comments/3

On 2012-01-30T11:58:49+00:00 Jakub wrote:

(In reply to comment #3)
> Ah ok, I removed the cache file and it's reproducible again. But still not 
> sure
> why it started to work.

SSSD caches the entries internally into an on-disk cache (as you figured
out). I believe that the second request came straight out of the cache
without even contacting SSSD.

If you set:
entry_cache_timeout = 1
into the [domain/redhat.com] section of your sssd.conf, then all cache entries 
will be only valid for 1 second, so even the second request should go all the 
way into the LDAP code.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888/comments/4

On 2012-01-30T12:04:28+00:00 Jakub wrote:

Actually, one more gotcha..the cache expiration time is stored in the

[Bug 993571] Re: Wifi disconnect/reconnects fairly often (from multiple times an hour to multiple times per day) because of ip-config-unavailable

** Changed in: network-manager (Fedora)
   Status: Unknown => Fix Released

** Changed in: network-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/993571

Title:
  Wifi disconnect/reconnects fairly often (from multiple times an hour
  to multiple times per day) because of ip-config-unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993571/+subscriptions

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

[Bug 935778] Re: Toshiba Tecra R840 - brightness controls work on first boot, but do nothing after suspend/resume

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

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 2011-11-22T01:19:02+00:00 Jim wrote:

Description of problem:
Screen cannot be brightened or dimmed after suspend.

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

How reproducible:
Suspend, then resume. After resume, neither function buttons nor screen setting 
in gnome will allow screen brightness to be changed.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Computer: Toshiba Portege Z830

Specifics:
[jim@toshiba ~]$ uname -r
3.1.1-2.fc16.i686
[jim@toshiba ~]$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/4


On 2012-09-13T06:18:52+00:00 Tom wrote:

Hi

I can second that!

Got the same model and same issue.

In case Fedora-crew need some system output, let me know.

Thanks!

Tom

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/61


On 2012-09-13T06:21:51+00:00 Tom wrote:

Hmm

I can see I were a bit too fast - I use an up-to-date Fedora 17.
Got the latest Intel graphics drivers 2.20.7-1.fc17 32bit.

Cheers!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/62


On 2013-01-16T13:43:51+00:00 Fedora wrote:

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/69


On 2013-02-13T14:37:26+00:00 Fedora wrote:

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/comments/70


** Changed in: fedora
   Status: Unknown => Won't Fix

** Changed in: 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/935778

Title:
  Toshiba Tecra R840 - brightness controls work on first boot, but do
  nothing after suspend/resume

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

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

[Bug 925760] Re: Constant warnings from the kernel: Test WP failed, assume Write Enabled

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

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 2011-12-22T03:41:38+00:00 Ralf wrote:

Description of problem:

Since having upgraded to F16 from F14, I am drowning in messages similar
to the one below on the console (corrupting any console output)

[ 1400.353433] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 1400.356601] sd 4:0:0:0: [sdb] Assuming drive cache: write through

accompanied by a message similar to the one in /var/log/messages
(gradually filling it up)

[ 1400.351374] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 1400.353433] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 1400.356601] sd 4:0:0:0: [sdb] Assuming drive cache: write through 


This machine (a netbook) only has one hard disk. sdb seems to refer to the 
builtin usb card reader.

Version-Release number of selected component (if applicable):
kernel-PAE-3.1.5-6.fc16.i686

How reproducible:
100%


Expected results:
The kernel not to raise these warnings/errors, but to work flawlessly (Older 
kernels did).

I am inclined to believe the kernel is not handling this sdb device
properly.

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


On 2011-12-22T04:02:41+00:00 Dave wrote:

please attach the dmesg output from a fresh boot.
need to see exactly which device we're working with here.

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


On 2011-12-22T04:21:51+00:00 Ralf wrote:

Created attachment 549125
dmesg of the system exposing this issue

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


On 2011-12-22T16:07:24+00:00 Dave wrote:

reported to upstream maintainer. thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/3


On 2011-12-22T17:27:01+00:00 Ralf wrote:

(In reply to comment #3)
> reported to upstream maintainer. thanks.
Welcome.

Any upstream BZ/PR? Any patch proposals, workarounds to try?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/4


On 2011-12-27T21:04:55+00:00 Joe wrote:

I've been getting the same messages during boot on my laptop ever since
"upgrading" from F14 to F16 and the boot process hangs right there.  The
only way I can use my laptop is to boot with the last 2.X kernel from
F14, which works fine.  No matter what 3.X kernel I try, this happens.
My laptop only has one internal HDD, and I never have a CD or flash
drive mounted during boot if that helps.  If there's a way for me to get
some data about a failed boot, please let me know and I'll do what's
needed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/5


On 2012-01-30T22:52:38+00:00 Joe wrote:

More info.  Ever since the "upgrade," the CD/DVD on my laptop has been
unusable.  If I into a 3.x kernel with it empty, I get the endless [sdb]
errors and putting a known-good CD in the drive first doesn't change
anything.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/comments/6


On 2012-02-28T14:57:21+00:00 Mark wrote:

I'm seeing this also on a laptop with builtin card reader. Every 50
seconds or so:

kernel: [  312.932881] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
kernel: [  312.935878] sd 6:0:0:0: [sdb] Asking for cache data failed
kernel: [  312.935888] sd 6:0:0:0: [sdb] Assuming drive cache: write through

But if I remove the plastic fake SD card which fits in the slot to
prevent dust, etc:

kernel: [  317.199029] usb 2-1.6: USB disconnect, device number 4

Then the kernel messages stop. On reinsertion of the fake card:

kernel: [  556.312591] usb 2-1.6: New USB device found, idVendor=0bda, 
idProduct=0138
kernel: [  556.312601] usb 2-1.6: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
kernel: [  556.312608] usb 2-1.6: Product: USB2.0-CRW
kernel: [  556.312612] usb 2-1.6: Manufacturer: Generic
kernel: [  556.312616] usb 2-1.6: SerialNumber: 2009051638820
kernel: [  556.494090] scsi7 : usb-storage 2-1.6:1.0
mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6"
mtp-probe: bus: 2, device: 5 was not an MTP device

[Bug 915018] Re: gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on

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

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 2012-01-11T20:45:06+00:00 Zooko wrote:

Description of problem:

gcc-4.7.0 fixes a bug that various packages rely on

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

4.7.0

How reproducible:

100% deterministic.

Steps to Reproduce:
1. Try to build a package such as Crypto++ v5.6.1 with a pre-release of gcc 
4.7.0.
2.
3.
  
Actual results:

Compile failure.

Expected results:

Compile success.

Additional info:

As reported by Jakub Jellinek: 
http://lists.fedoraproject.org/pipermail/devel/2011-December/160723.html
As tracked on launchpad: https://bugs.launchpad.net/gcc/+bug/915018, which has 
links to the issue trackers for Crypto++ and pycryptopp.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/12


On 2012-01-11T22:51:37+00:00 Jakub wrote:

Why are you filing it against gcc?  It is completely intentional.  Just
fix your package(s).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/13


On 2012-01-11T23:48:09+00:00 Zooko wrote:

I didn't mean to denote that it was a (current) bug in gcc. I just meant
to let myself and others track the fact that the gcc 4.7.0 release (and
pre-releases) interact with this bug, and I meant to link to the
original gcc ticket: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24163

I guess ideally I would mark this ticket as applying to the list of
packages that you posted to the mailing list, but I don't know if that's
possible and if it is I'm not going to take the time to do it manually.
;-)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/14


On 2012-01-11T23:52:57+00:00 Zooko wrote:

P.S. I guess I was thinking of "the package of gcc that is shipped in
Fedora" as being one of the subjects of this ticket, more than "gcc
itself". I figured it might help other people to understand that if they
are seeing these errors, it is the combination of gcc 4.7.0 pre-release
and their other packages that results in the errors. But again, I didn't
intend to say that the errors were caused by gcc having a bug. Also, of
course, Crypto++ and quite a few other packages are also the subjects of
this issue. The launchpad ticket --
https://bugs.launchpad.net/gcc/+bug/915018 -- has links to relevant
tickets in various issue trackers.

For my own future reference:

1. Is there a way to express in bugzilla.redhat.com that an issue
affects a package of software $X version $Y within Fedora release $Z?
Ideally I would have said "This is an issue you may have if you're using
the 4.7.0 pre-release distributed in Fedora Rawhide.". Is there a way to
express that in the bugzilla db?

2. Is there a way to denote "This is an issue that affects $X or that
the presence of $X can trigger, but is not a bug in $X?".

Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018/comments/15


** Changed in: libcrypto++ (Fedora)
   Status: Unknown => Invalid

** Changed in: libcrypto++ (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/915018

Title:
  gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on

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

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

[Bug 1111517] Re: javaws doesn't open Supermicro remote console (IP-KVM)

** Changed in: openjdk-7 (Fedora)
   Status: Unknown => Fix Released

** Changed in: openjdk-7 (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/517

Title:
  javaws doesn't open Supermicro remote console (IP-KVM)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/517/+subscriptions

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

[Bug 978333] Re: xfwm4 is not running after failed shut down / "session manager must be in idle state when requesting a shutdown"

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

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 2011-12-12T20:40:31+00:00 Dimitri wrote:

Description of problem:

Upgraded to centos 6.1 and rebooted. After login: 
1) no window decorations ('xfwm4 --replace' fixes that).
2) no workspaces (used to be 4). (Fixable via settings manager.)

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

xfce4-panel-4.8.3-2.el6.x86_64
xfce4-doc-4.8.3-1.el6.noarch
xfce4-session-4.8.1-4.el6.x86_64
xfce-utils-4.8.3-1.el6.x86_64
xfce4-session-engines-4.8.1-4.el6.x86_64
xfce4-power-manager-1.0.10-1.el6.x86_64
libxfce4ui-4.8.0-4.el6.x86_64
libxfce4util-4.8.1-2.el6.x86_64
xfce4-appfinder-4.8.0-2.el6.x86_64
xfce4-mixer-4.8.0-1.el6.x86_64
xfce4-settings-4.8.3-1.el6.x86_64
xfce4-icon-theme-4.4.3-5.el6.noarch
xfwm4-4.8.1-3.el6.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/978333/comments/17


On 2011-12-12T21:00:16+00:00 Dimitri wrote:

OK, a couple of restarts later: I verified that xfce4-session is not
starting the window manager, and that # of workspaces is reset to 1 on
every login.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/978333/comments/18


On 2011-12-12T21:14:26+00:00 Kevin wrote:

Are you sure you are saving a session with xfwm4 running? and it's
completing ok?

Anything in ~/.xsession-errors related to a xfwm4 crash?

Does making a new clean user show the same behavior?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/978333/comments/19


On 2011-12-12T21:27:08+00:00 Dimitri wrote:

"No", "no", "not tried b/c #1 is the correct answer".

So the best guess is initially, after I ran yum update and hit "restart"
button on the logout dialog, the session got somehow saved with xfwm4
not running?

After that I was starting xfwm4 from an xterm without '&', I can see how
that would kill the wm before saving the session.

Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/978333/comments/20


On 2011-12-13T03:31:36+00:00 Kevin wrote:

Yeah, that seems to be the case. ;(

We have seen sporadic cases where a logout has a xfwm4 crash, then it
doesn't get saved in the session. Causing it to not show up in later
sessions. ;(

We have not been able to track down the issue. ;(

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/978333/comments/21


On 2012-02-11T22:51:36+00:00 Max wrote:

I am not having trouble with window decorations, but I am having trouble
with the number of workspaces being reset to 1.  I can also set the
number of workspaces manually every time I login.  I'm using F16 on 686.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/978333/comments/27


** Changed in: xfwm4 (Fedora)
   Status: Unknown => In Progress

** Changed in: xfwm4 (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/978333

Title:
  xfwm4 is not running after failed shut down / "session manager must be
  in idle state when requesting a shutdown"

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-session/+bug/978333/+subscriptions

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

[Bug 932177] Re: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11

** Changed in: gnome-keyring (Fedora)
   Status: Unknown => Fix Released

** Changed in: gnome-keyring (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/932177

Title:
  XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
  correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/932177/+subscriptions

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

[Bug 940267] Re: USB keyboard and mouse can't be used after shutdown and power on

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

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 2012-01-26T21:16:34+00:00 Andreas wrote:

Description of problem:
If I shutdown the computer finally turns off. If I turn on the computer again, 
the BIOS does not recognize my USB keyboard and mouse. As a result, no OS 
(Fedora nor Windows) is able to initialize and use the keyboard and mouse. I 
have to unplug the power chord and wait until the power supply is discharged. 
After the next power on, the mouse and keyboard functions completely ok.
I had exactly the same bug with kernel 2.6.38 on ubuntu.

Version-Release number of selected component (if applicable):
kernel
3.2.1-3.fc16.x86_64 - BUG PRESENT
3.1.9-1.fc16.x86_64 - BUG PRESENT
3.1.7-1.fc16.x86_64 - bug free!

How reproducible:
all times

Steps to Reproduce:
1. boot with kernel 3.2.1-3 or 3.1.9-1
2. login
3. shutdown the computer
4. after power down, turn on the computer

  
Actual results:
the bios does not recognize the USB keyboard and mouse. The mouse and keyboard 
can't be used.

Expected results:
mouse and keyboard must function

Additional info:
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/786272 for more 
details. The hardware details are the same exept the graphics card.

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


On 2012-02-11T20:36:24+00:00 Andreas wrote:

Linux 3.2.5-3.fc16.x86_64 has the bug, too.

If I boot 3.2.5-3 the logon screen finally appears. But the keyboard and
mouse do not function. If I press a key in this state, the three leds
num lock, caps lock and scroll lock will be turned on for approx. 0.5sec
once or two times.

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


On 2012-10-23T15:37:36+00:00 Dave wrote:

# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been
fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment 
is sufficient).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/940267/comments/5


On 2012-11-14T16:22:47+00:00 Justin wrote:

With no response, we are closing this bug under the assumption that it
is no longer an issue. If you still experience this bug, please feel
free to reopen the bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/940267/comments/6


** Changed in: linux (Fedora)
   Status: Unknown => Expired

** Changed in: linux (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/940267

Title:
  USB keyboard and mouse can't be used after shutdown and power on

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

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

[Bug 991869] Re: New version + Numerous Use of qw(...) as parentheses is deprecated messages

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

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 2012-01-04T22:50:00+00:00 Frank wrote:

Description of problem:
Due to a change in perl syntax for Perl 5.14 and onwards, the use of qw(...) in 
specific contexts is now disallowed.  This generates lots of messages of the 
form:
Use of qw(...) as parentheses is deprecated at /usr/sbin/psad line 4264.

Version-Release number of selected component (if applicable):
psad-2.1.7-2.fc15.x86_64
perl-5.14.2-191.fc16.x86_64

How reproducible:
100% of time

Steps to Reproduce:
1. Run "psad --help" or any other psad options.
2.
3.
  
Actual results:
Numerous messages about deprecated feature.

Expected results:
No deprecated messages

Additional info:
Reading some of the perl list this only occurs in statements of the form:
for my $var qw(...) { ... }
and is fixed by the addition of "()", i.e.
for my $var (qw(...)) { ... }

Reply at:
https://bugs.launchpad.net/ubuntu/+source/psad/+bug/991869/comments/0


On 2012-02-07T11:36:16+00:00 Šimon wrote:

This has been fixed in upstream
e013ca6230a6210ac6e405da08df370fb4818831.

It might be included in the upcoming psad-3.0 release.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/psad/+bug/991869/comments/1


On 2012-02-13T10:05:29+00:00 Fedora wrote:

psad-2.1.7-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/psad-2.1.7-5.fc16

Reply at:
https://bugs.launchpad.net/ubuntu/+source/psad/+bug/991869/comments/2


On 2012-02-14T09:07:09+00:00 Fedora wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/psad/+bug/991869/comments/3


On 2013-01-17T02:13:39+00:00 Fedora wrote:

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/psad/+bug/991869/comments/6


On 2013-02-14T03:03:24+00:00 Fedora wrote:

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/psad/+bug/991869/comments/7


** Changed in: psad (Fedora)
   Status: Unknown => Won't Fix

** Changed in: psad (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/991869

Title:
  New version + Numerous Use of qw(...)

[Bug 1052483] Re: display multiple files broken

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

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 2011-11-22T06:52:06+00:00 Major wrote:

Description of problem:

When asked to display multiple files, display displays the first file
again when it should be displaying the second apparently mistakenly
trying to display some kind of animation scene.

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

Version: ImageMagick 6.7.3-7 2011-11-20 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC
Features: OpenMP  

How reproducible:
100%

Steps to Reproduce:
1. display multiple files (EG: display *.jpg in a directory with more than one 
file)
2. Press space

  
Actual results:
(at 1) first file displayed
(at 2) first file displayed again but the title bar changes to display the 
information: "[scene: 0 frames: 2]"

Expected results:
(at 1) first file displayed
(at 2) second file displayed


Additional info:

this problem has been recognized and corrected upstream
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3=19141

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/0


On 2011-12-10T10:58:38+00:00 Pavel wrote:

Thank you for your bugreport and willing make free software better!

Reported upstream as you say itself. I also ask when it will be fixed.

We close bug now, as it related to upstream developing. But we continue
track changes and whatever it will be fixed ve consider make update in
Fedora.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/1


On 2011-12-11T22:08:08+00:00 Pavel wrote:

Upstream author answer what it is fixed and doesn't reproduced anymore.
Please answer in they forum!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/2


On 2011-12-12T07:12:17+00:00 Major wrote:

Problem is fixed upstream but fix has not been incorporated into Fedora,
how could commenting in THEIR forum possibly help?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/3


On 2011-12-18T13:41:52+00:00 Pavel wrote:

Author said what it is expected behavior. If you disagree, please speak
with author. There nothing do in Fedora.

If some changes happened I can make new build in rawhide then.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/4


On 2012-02-19T19:03:16+00:00 Pavel wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/5


On 2012-02-19T19:24:14+00:00 Corinna wrote:

Pavel,

you seem to have misunderstood what the author said.  The bug is fixed
upstream, but what we're asking for is to get the bugfix into Fedora.
F16 ImageMagick version is 6.7.0.10, but the bug has been fixed upstream
between 6.7.3 and 6.7.4.  So what we're asking for is an update of the
Fedora version.


Corinna

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/6


On 2012-02-23T12:45:31+00:00 Pavel wrote:

Hello, Corinna.

As upstream maintainers not so careful in soname bump [1] it may lead to
ugly errors. Additionaly, there at least ryby-rmagick which explicitly
depends on exact version of IM. So, to push that updates all dependency
rebuild should be happened. As it is not security bug - I'm do not
willing do that. Update already in rawhide - so, who are willing may use
that already.

[1] http://old.nabble.com/Bug-564123%3A--imagemagick--Dear-other-(than-
debian)-imagemagick-maintenair-td27125967.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1052483/comments/7


On 2012-02-23T16:06:30+00:00 Corinna wrote:

There's just the tiny problem that the rawhide version of ImageMagick is too
old as well.  It's 6.7.1.9-3.

Again, the fix has been applied between 6.7.3 and 6.7.4.  So please update at
least rawhide to the latest available ImageMagick version which is 6.7.5-6.
I built and tested it on F16 and can confirm that the problem is fixed in that
upstream release.

[Bug 985848] Re: nautilus crashed with SIGSEGV in icon_rename_ended_cb()

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

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 2011-12-13T13:56:45+00:00 kotofos wrote:

libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 3
cmdline:nautilus -n
comment:open new window, by clicking middle button on side panel, while 
no nautilus windows open and "nautilus handle desktop" is on
crash_function: icon_rename_ended_cb
executable: /usr/bin/nautilus
kernel: 3.1.4-1.fc16.x86_64
pid:1482
pwd:/home/kotofos
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
time:   Вт. 13 дек. 2011 19:10:54
uid:1000
username:   kotofos

backtrace:  Text file, 38487 bytes
dso_list:   Text file, 16442 bytes
maps:   Text file, 77207 bytes
smolt_data: Text file, 2991 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=1
:HOSTNAME=kotofos-laptop
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=1ae78454aedfe02bdcbc0f4b0011-1323669018.425340-735808942
:QTDIR=/usr/lib64/qt-3.3
:QTINC=/usr/lib64/qt-3.3/include
:IMSETTINGS_MODULE=none
:USER=kotofos
:USERNAME=kotofos
:MAIL=/var/spool/mail/kotofos
:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/kotofos/.local/bin:/home/kotofos/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/kotofos
:XMODIFIERS=@im=none
:LANG=en_GB.utf8
:GDM_LANG=en_GB.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/kotofos
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=kotofos
:QTLIB=/usr/lib64/qt-3.3/lib
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-lvSN8ivVxT,guid=bcaf33b2f0a44a31627725bf003e
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/kotofos
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-kotofos-1lg2UE/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1186,unix/unix:/tmp/.ICE-unix/1186
:GNOME_KEYRING_CONTROL=/tmp/keyring-Q31oJo
:SSH_AUTH_SOCK=/tmp/keyring-Q31oJo/ssh
:GPG_AGENT_INFO=/tmp/keyring-Q31oJo/gpg:0:1
:LC_TIME=ru_RU.utf8
:LC_NUMERIC=ru_RU.utf8
:LC_MONETARY=ru_RU.utf8
:LC_MEASUREMENT=ru_RU.utf8
:DESKTOP_AUTOSTART_ID=10c46320ee6320391813236690201374720011860028

var_log_messages:
:Dec 13 19:10:53 kotofos-laptop kernel: [109297.109042] nautilus[1482]: 
segfault at 30 ip 0043862e sp 7fffcc141730 error 4 in 
nautilus[40+159000]
:Dec 13 19:11:17 kotofos-laptop abrt[3397]: Saved core dump of pid 1482 
(/usr/bin/nautilus) to /var/spool/abrt/ccpp-2011-12-13-19:10:54-1482 (132722688 
bytes)

xsession_errors:
:Initializing nautilus-dropbox 0.7.1
:Initializing nautilus-gdu extension
:(nautilus:1482): Gtk-CRITICAL **: _gtk_timeline_rewind: assertion 
`GTK_IS_TIMELINE (timeline)' failed
:(nautilus:1482): GLib-GObject-WARNING **: instance with invalid (NULL) class 
pointer
:(nautilus:1482): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 
`G_TYPE_CHECK_INSTANCE (instance)' failed
:Initializing nautilus-dropbox 0.7.1
:Initializing nautilus-gdu extension

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985848/comments/0


On 2011-12-13T13:56:49+00:00 kotofos wrote:

Created attachment 546222
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985848/comments/1


On 2011-12-13T13:56:51+00:00 kotofos wrote:

Created attachment 546223
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985848/comments/2


On 2011-12-13T13:56:54+00:00 kotofos wrote:

Created attachment 546224
File: smolt_data

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985848/comments/3


On 2011-12-13T13:56:57+00:00 kotofos wrote:

Created attachment 546225
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985848/comments/4


On 2012-06-30T15:38:47+00:00 efreeti wrote:

Create a new folder, crash when I tried to name it as "Radio-Em-DR"
(without double quotes)

backtrace_rating: 4
Package: nautilus-3.4.2-5.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/985848/comments/12


On 2012-06-30T15:38:53+00:00

[Bug 1008385] Re: libapache2-mod-perl2 writes wrong process name in /proc/$$/status

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

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 2012-01-17T10:18:01+00:00 Panos wrote:

Description of problem: An configuration entry to display the number of
httpd processes running does not work on recent SNMP servers.


Version-Release number of selected component (if applicable): 
net-snmp-5.7.1-2.fc16.x86_64


How reproducible: Enable public SNMP community and add the following entry in 
/etc/snmp/snmpd.conf:
proc httpd 30 1

Steps to Reproduce:
1. Edit /etc/snmp/snmpd.conf
2. Enable public SNMP community and add "proc httpd 30 1"
3. Restart snmpd by issuing "systemctl restart snmpd.service" as root
4. Run "snmpwalk -v 1 localhost -c public .1.3.6.1.4.1.2021.2"
  
Actual results:
UCD-SNMP-MIB::prCount.1 = INTEGER: 0
UCD-SNMP-MIB::prErrorFlag.1 = INTEGER: error(1)
UCD-SNMP-MIB::prErrMessage.1 = STRING: No httpd process running

Expected results:
UCD-SNMP-MIB::prCount.1 = INTEGER: 9
UCD-SNMP-MIB::prErrorFlag.1 = INTEGER: noError(0)
UCD-SNMP-MIB::prErrMessage.1 = STRING:


Additional info:
The number of the httpd processes currently run in the system:

# ps -ef | grep -i httpd 
root  1067 1  0 Jan16 ?00:00:02 /usr/sbin/httpd -k start
apache1078  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start
apache1079  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start
apache1080  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start
apache1081  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start
apache1082  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start
apache1083  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start
apache1084  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start
apache1085  1067  0 Jan16 ?00:00:00 /usr/sbin/httpd -k start

The full snmpd.conf configuration is also attached for your convenience.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-
perl2/+bug/1008385/comments/0


On 2012-01-17T10:20:05+00:00 Panos wrote:

Created attachment 555720
SNMPD configuration

Configuration file /etc/snmp/snmpd.conf

Reply at: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-
perl2/+bug/1008385/comments/1


On 2012-01-17T10:20:57+00:00 Panos wrote:

The rest configured processes (smbd & sshd) work fine:

# snmpwalk -v 1 localhost -c public .1.3.6.1.4.1.2021.2
UCD-SNMP-MIB::prIndex.1 = INTEGER: 1
UCD-SNMP-MIB::prIndex.2 = INTEGER: 2
UCD-SNMP-MIB::prIndex.3 = INTEGER: 3
UCD-SNMP-MIB::prNames.1 = STRING: httpd
UCD-SNMP-MIB::prNames.2 = STRING: smbd
UCD-SNMP-MIB::prNames.3 = STRING: sshd
UCD-SNMP-MIB::prMin.1 = INTEGER: 1
UCD-SNMP-MIB::prMin.2 = INTEGER: 1
UCD-SNMP-MIB::prMin.3 = INTEGER: 1
UCD-SNMP-MIB::prMax.1 = INTEGER: 30
UCD-SNMP-MIB::prMax.2 = INTEGER: 25
UCD-SNMP-MIB::prMax.3 = INTEGER: 20
UCD-SNMP-MIB::prCount.1 = INTEGER: 0
UCD-SNMP-MIB::prCount.2 = INTEGER: 2
UCD-SNMP-MIB::prCount.3 = INTEGER: 1
UCD-SNMP-MIB::prErrorFlag.1 = INTEGER: error(1)
UCD-SNMP-MIB::prErrorFlag.2 = INTEGER: noError(0)
UCD-SNMP-MIB::prErrorFlag.3 = INTEGER: noError(0)
UCD-SNMP-MIB::prErrMessage.1 = STRING: No httpd process running
UCD-SNMP-MIB::prErrMessage.2 = STRING: 
UCD-SNMP-MIB::prErrMessage.3 = STRING: 
UCD-SNMP-MIB::prErrFix.1 = INTEGER: noError(0)
UCD-SNMP-MIB::prErrFix.2 = INTEGER: noError(0)
UCD-SNMP-MIB::prErrFix.3 = INTEGER: noError(0)
UCD-SNMP-MIB::prErrFixCmd.1 = STRING: 
UCD-SNMP-MIB::prErrFixCmd.2 = STRING: 
UCD-SNMP-MIB::prErrFixCmd.3 = STRING:

Reply at: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-
perl2/+bug/1008385/comments/2


On 2012-01-19T11:25:15+00:00 Jan wrote:

In my test environment I can see all httpd daemons in prTable. Please note that
net-snmp-5.7.1 uses caches with 30 second timeout to count processes, i.e. the 
prTable is updated every 30 seconds with new/exited processes. Did you wait at 
least half a minute after httpd service start/stop?

BTW, I don't know how this 30 second timeout was chosen, maybe it's too
long.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-
perl2/+bug/1008385/comments/3


On 2012-01-19T13:02:45+00:00 Panos wrote:

Hello Jan,

Something very weird is happening. It now works:

# snmpwalk -v 1 localhost -c public .1.3.6.1.4.1.2021.2
UCD-SNMP-MIB::prIndex.1 = INTEGER: 1
UCD-SNMP-MIB::prIndex.2 = INTEGER: 2
UCD-SNMP-MIB::prIndex.3 = INTEGER: 3

[Bug 918421] Re: gnome-settings-daemon crashed with SIGSEGV in idle_set_mode()

** Changed in: gnome-settings-daemon (Fedora)
   Status: Unknown => Won't Fix

** Changed in: gnome-settings-daemon (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/918421

Title:
  gnome-settings-daemon crashed with SIGSEGV in idle_set_mode()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/918421/+subscriptions

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

[Bug 1034740] Re: 8086:4238 [Lenovo ThinkPad X201] iwlwifi drops connection when using 802.11n

** Changed in: fedora
   Status: Unknown => Fix Released

** Changed in: 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/1034740

Title:
  8086:4238 [Lenovo ThinkPad X201] iwlwifi drops connection when using
  802.11n

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

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

[Bug 1007901] Re: driver crash radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0

** Changed in: fedora
   Status: Unknown => Fix Released

** Changed in: 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/1007901

Title:
  driver crash radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0

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

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

[Bug 929713] Re: audio unreliable with eglibc 2.15

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

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 2011-12-20T18:58:28+00:00 Valdis wrote:

Description of problem:
After installing 2.14.89025, I was seeing lots of weird issues - programs 
trying to talk to pulseaudio would hang, firefox was wedged and flickering the 
X cursor between 2 different cursors, some other weird stuff.

Caught this in gdb of /usr/bin/pidgin hung during startup:

(gdb) c
Continuing.
^C
Program received signal SIGINT, Interrupt.
pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:145
145 movl$1, %r8d
(gdb) where
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:145
#1  0x7f8d189f7740 in pa_threaded_mainloop_wait (m=0x7f8d1c27d650) at 
pulse/thread-mainloop.c:206
#2  0x7f8d18c16cbc in ?? () from /usr/lib64/gstreamer-0.10/libgstpulse.so
#3  0x7f8d18c180aa in ?? () from /usr/lib64/gstreamer-0.10/libgstpulse.so
#4  0x0034bbc070f1 in ?? () from /usr/lib64/libgstaudio-0.10.so.0
#5  0x0034bbc09cc0 in gst_ring_buffer_pause () from 
/usr/lib64/libgstaudio-0.10.so.0
#6  0x0034bbc12c8a in ?? () from /usr/lib64/libgstaudio-0.10.so.0
#7  0x7f8d18c195a9 in ?? () from /usr/lib64/gstreamer-0.10/libgstpulse.so
#8  0x0034b8c41d4c in gst_element_change_state () from 
/usr/lib64/libgstreamer-0.10.so.0

Reverting to 2.14.90-23 and everything started working normally again -
pidgin, pulseaudio, firefox, etc.

Am willing to add instrumentation and re-test if somebody tells me what
they want tried.


Version-Release number of selected component (if applicable):
glibc-2.14.90-25.fc17

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929713/comments/0


On 2011-12-22T00:10:08+00:00 Kazuro wrote:

I had similar weird behaviors of applications in F16 (x86_64) after I
installed glibc-2.14.90-24.fc16.3. I googled and found (in Bug#651899 in
Debian) my problem might be related to glibc-rh552960.patch had been
introduced in 2.14.90-24.fc16.x. I locally build glibc-2.14.90-24.fc16.3
without the patch then everything have been working fine for two days. I
found the patch has been merged into glibc-2.14.90-25.fc17 tarball.

Regards,

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929713/comments/1


On 2011-12-22T02:53:30+00:00 Valdis wrote:

Kazuro: Thank you for digging further into this, and confirming I'm not
crazy (or at least, not hallucinating this particular bug ;)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929713/comments/2


On 2011-12-29T22:40:34+00:00 Valdis wrote:

Got around to testing 2.14.90-26, which contained this:

  - Revert "fix" to pthread_cond_wait (#769421)

and it does appear to be working correctly on my box again.  Thanks..

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929713/comments/3


On 2012-01-02T18:21:03+00:00 Jeff wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929713/comments/4


On 2012-01-02T18:22:28+00:00 Jeff wrote:

Should be fixed by either 2.15-1.fc17 or 2.14.90-26.fc17 (both revert
the problematical pthread_cond_wait patch).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929713/comments/5


On 2012-02-14T03:53:36+00:00 Fedora wrote:

glibc-2.14.90-24.fc16.5 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/glibc-2.14.90-24.fc16.5

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929713/comments/14


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

** Changed in: eglibc (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/929713

Title:
  audio unreliable with eglibc 2.15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com

[Bug 1197395] Re: /run/user/$ID/pulse owned by root and not by the user

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

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 2011-11-14T18:29:34+00:00 Dr wrote:

Description of problem:

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1197395/comments/0

On 2011-11-14T18:36:24+00:00 Dr wrote:

Following 11-11-2011 F16 updates I have following problem
99% certain this did not happen before the updates

Login to the console as fred
Create a konsole window

[fred@naxos ~]$ xhost +  
access control disabled, clients can connect from any host 
[fred@naxos ~]$ su - ja
Password: 
ja@naxos ~ 1$ export DISPLAY=:0.0
ja@naxos ~ 2$ gedit prob.txt
** (gedit:4544): CRITICAL **: unable to create '/run/user/fred/dconf'; dconf 
will not work properly.
ja@naxos ~ 3$ 

Editing is possible but ja preferences are not honoured

Why is gedit trying to create a file in fred's directory?
[root@naxos ~]# ls -l /run/user/
total 0
drwx--. 4 fred fred 80 Nov 11 11:29 fred
drwx--. 2 root root 40 Nov 11 12:00 root

Fully updated F16
Using KDM and XFCE (not GDM or Gnome)

[root@naxos ~]# yum info gconf*
Installed Packages
Name: GConf2
Arch: x86_64
Version : 3.2.3
Release : 1.fc16
Size: 6.2 M
Repo: installed
>From repo   : local-16-update
Summary : A process-transparent configuration system
URL : http://projects.gnome.org/gconf/
License : LGPLv2+
Description : GConf is a process-transparent configuration database API used to
: store user preferences. It has pluggable backends and features to
: support workgroup administration.

[root@naxos ~]# yum info dconf
Installed Packages
Name: dconf
Arch: x86_64
Version : 0.10.0
Release : 1.fc16
Size: 210 k
Repo: installed
>From repo   : anaconda-0
Summary : A configuration system
URL : http://live.gnome.org/dconf
License : LGPLv2+
Description : dconf is a low-level configuration system. Its main purpose is to 
provide a
: backend to the GSettings API in GLib.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1197395/comments/1

On 2011-11-18T01:03:34+00:00 Matthias wrote:

This is because su - does not change the XDG_RUNTIME_DIR environment
variable.

Setting XDG_RUNTIME_DIR=/run/user/ja is not going to solve the problem,
since dconf relies on the system to create (and remove) the runtime dir.

Unsetting XDG_RUNTIME_DIR will make dconf use ~/.cache, and thus avoid
the problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1197395/comments/2

On 2011-11-28T12:15:01+00:00 Dodji wrote:

Matthias, I am sorry, but I don't understand why you close this as
'NOTABUG'.

So what you are essentially saying by doing this is that end users
should not expect dconf to work after they did 'su -', and for what it's
worth, I would find that assertion questionable.  In other words, this
ought to be fixed somehow, IMHO.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1197395/comments/3

On 2011-11-28T12:15:26+00:00 Guillaume wrote:

(In reply to comment #2)
> Setting XDG_RUNTIME_DIR=/run/user/ja is not going to solve the problem, since
> dconf relies on the system to create (and remove) the runtime dir.

Then we have at least one of the following problem:
- dconf shouldn't rely on the sytem to create the runtime dir
- the sytem (systemd?) should create the runtime dir when loging in using "su 
-".

I do need a working environnement when testing with my test user.

Can you please re-open this bug ? Looks like I don't have the rights to
do it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1197395/comments/4

On 2011-11-28T12:17:37+00:00 Dodji wrote:

I am tentatively re-opening the bug.  I don't meant to be rude by doing
this.  It's just that I think we need at least some rationale of why
this should be seen as an expected behaviour.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1197395/comments/5

On 2011-11-28T12:18:58+00:00 Michael

[Bug 1217585] Re: System hangs after some time with nouveau and GT240

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

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 2011-11-18T03:03:52+00:00 Pavel wrote:

Description of problem:
Fresh install of Fedora 16. Hardware 
http://www.smolts.org/client/show/pub_d48e8798-a431-4297-a9c9-9e3fd31afd88. 
System works 10-15 min and freezes. Only SysRQ keys work.  

Version-Release number of selected component (if applicable):
kernel-3.1.1-1.fc16.x86_64
xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.x86_64

Additional info:
Last logs:
Nov 17 23:38:40 fedora16 kernel: [  845.600956] [drm] nouveau :01:00.0: 
PGRAPH TLB flush idle timeout fail: 0x01bfe503 0x0008 0x106d 0x0034da43
Nov 17 23:38:41 fedora16 kernel: [  847.597755] [drm] nouveau :01:00.0: vm 
flush timeout: engine 0

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


On 2011-11-18T12:12:18+00:00 Josh wrote:

Could you install kernel-debug and see if a backtrace is spit out?

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


On 2011-11-20T08:00:30+00:00 Pavel wrote:

Done. Frozen again (SysRQ keys and even reset didn't work, rebooted by
Power ).

last log from messages:

Nov 20 11:53:16 fedora16 kernel: [140558.003181] [drm] nouveau :01:00.0: vm 
flush timeout: engine 0
Nov 20 11:53:19 fedora16 kernel: [140560.650151] [drm] nouveau :01:00.0: 
PFIFO_INTR 0x0400 - Ch 4
Nov 20 11:53:21 fedora16 kernel: [140562.646934] [drm] nouveau :01:00.0: vm 
flush timeout: engine 5
Nov 20 11:53:23 fedora16 kernel: [140564.643725] [drm] nouveau :01:00.0: vm 
flush timeout: engine 5
Nov 20 11:53:25 fedora16 kernel: [140564.643853] [drm] nouveau :01:00.0: 
PGRAPH TLB flush idle timeout fail: 0x00be0001 0x 0x106d 0x00148000
Nov 20 11:53:25 fedora16 kernel: [140566.640644] [drm] nouveau :01:00.0: vm 
flush timeout: engine 0
Nov 20 11:53:26 fedora16 kernel: [140567.964527] [drm] nouveau :01:00.0: vm 
flush timeout: engine 0
Nov 20 11:53:26 fedora16 kernel: [140567.964543] [drm] nouveau :01:00.0: 
PFIFO_INTR 0x0080 - Ch 4
Nov 20 11:53:31 fedora

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


On 2011-11-20T14:38:33+00:00 Sammy wrote:

This may be related to other crashes...I have been trying to figure out why
kde-plasma and other kde stuff keeps crashing on all my machines using the
nouveau driver and perfectly stable on a machine using intel HD3000 (all Fedora 
16).

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


On 2011-11-24T03:17:07+00:00 Anas wrote:

When i install Fedora 16 With GNOME-shell And nvidia Graphics card, the
system crashes after 1 - 2 minutes ([140558.003181] [drm] nouveau
:01:00.0: PGRAPHTLB flush idle timeout fail ...)

When i replace the Graphics card with ATA the system works fine.

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


On 2011-11-27T15:14:06+00:00 Johan wrote:

I might be wrong, but I think certain applications cause the crash.

After de-installing the flash browser plugin some days ago, I didn't
experience the problem any more.  That is, until I started playing
around with Eclipse.  My system has crashed twice this weekend, and each
time I was running Eclipse.

It might be a coincidence though.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1217585/comments/8


On 2011-11-27T15:52:07+00:00 Anas wrote:

The problem cames from nouveau driver for nvidia graphics card. Its not
compatible with geforce 210

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1217585/comments/9


On 2011-11-27T21:35:52+00:00 Johan wrote:

For the record: I just had the crash without running Evolution.  So you
may ignore comment #5.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1217585/comments/10


On 2011-11-28T06:43:08+00:00 Ben wrote:

(In reply to

[Bug 1320402] Re: mdadm resyncs imsm raid in "Normal" state

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

** Changed in: mdadm (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/1320402

Title:
   mdadm resyncs imsm raid in "Normal" state

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

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

[Bug 1728193] [NEW] Can not upgrade from 17.04 to 17.10 using software updating tool

2017-10-27 Thread Scott

Public bug reported:

I wanted to update my distro version from 17.04 to 17.10 and an error
occurs when using the software updating tool. It starts out just fine
but during the second stage it goes into error when calculating.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-release-upgrader-core 1:17.04.7
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
CrashDB: ubuntu
CurrentDesktop: Unity:Unity7
Date: Fri Oct 27 21:17:01 2017
InstallationDate: Installed on 2016-09-27 (395 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to zesty on 2017-10-28 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade third-party-packages zesty zesty2artful

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

Title:
  Can not upgrade from 17.04 to 17.10 using software updating tool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1728193/+subscriptions

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

[Bug 1727759] Re: Please upgrade to 3.17.10

hplip 3.17.10 will be available in Ubuntu 18.04 LTS.

https://launchpad.net/ubuntu/+source/hplip/3.17.10+repack0-1

** Changed in: hplip (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/1727759

Title:
  Please upgrade to 3.17.10

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

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

[Bug 1727768] Re: Please pull latest v0.18 which fixes bugs already reported

Didn't you see the notice at https://github.com/stjerm/stjerm that the
project is abandoned?

The 0.18 release was a few years ago.

Since this isn't maintained in Debian either, I think we should consider
removing it from Ubuntu.

If someone wants it in Ubuntu, they should maintain it in Debian.

** Changed in: stjerm (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/1727768

Title:
  Please pull latest v0.18 which fixes bugs already reported

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

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

[Bug 1708817] Re: Printing with smbspool_krb5_wrapper not working in Ubuntu 16.04

[Expired for samba (Ubuntu) because there has been no activity for 60
days.]

** Changed in: samba (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Printing with smbspool_krb5_wrapper not working in Ubuntu 16.04

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

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

[Bug 1684973] Re: Crashes (segfault) under Wayland in Ubuntu GNOME 17.04

[Expired for gdebi (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gdebi (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Crashes (segfault) under Wayland in Ubuntu GNOME 17.04

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

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

[Bug 1682785] Re: nautilus (nautilus:16762): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client (nautilus:16762): Gtk-WARNIN

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nautilus  (nautilus:16762): Gtk-WARNING **: Failed to register client:
  GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to
  register client  (nautilus:16762): Gtk-WARNING **: Theme parsing
  error: Adwaita.css:51:71: Using one color stop with linear-gradient()
  is deprecated.  (nautilus:16762): Gtk-WARNING **: Theme parsing error:
  Adwaita.css:52:71: Using one color stop with linear-gradient() is
  deprecated. Nautilus-Share-Message: Called "net usershare info" but it
  failed: Klarte ikke å kjøre underprosess «net» (Fila eller mappa
  finnes ikke) ** ERROR:nautilus-canvas-
  container.c:6032:finish_adding_new_icons: assertion failed:
  (!container->details->auto_layout) Avbrutt (SIGABRT) (kjerne lagret i
  fil)

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

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

[Bug 1708661] Re: Nautilus 3.18.5 crashes when dragging icons on the desktop

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Nautilus 3.18.5 crashes when dragging icons on the desktop

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

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

[Bug 1687497] Re: multiple default application settings conflicting

[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  multiple default application settings conflicting

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

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

[Bug 1687510] Re: way to remove "Default Application" defective or makes no sense