[Bug 1657256] Re: Percona crashes when doing a a 'larger' update

2017-10-26 Thread ChristianEhrhardt
Ok, then we have
- code review and fixups done
- Fixed in latest Dev release
- SRU Template ready
- Tested build from PPAs
- Tested fix from PPAs
=> I'm merging the MPs and sponsoring the fix now for SRU.

I see it in the -unapproved queues - from now on it is up to the SRU
Team.

@Jorge - Please help tracking proposed migration and verification in all
three releases after acceptance.

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

Title:
  Percona crashes when doing a a 'larger' update

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-test-infra/+bug/1657256/+subscriptions

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

[Bug 1727929] [NEW] package kodi-repository-kodi (not installed) failed to install/upgrade: Versuch, »/usr/share/kodi/addons/repository.xbmc.org/addon.xml« zu überschreiben, welches auch in Paket kodi

2017-10-26 Thread Kannitverstan
Public bug reported:

I tried to install Kodi on a fresh installed Shuttle DX30

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: kodi-repository-kodi (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Oct 27 07:19:40 2017
ErrorMessage: Versuch, »/usr/share/kodi/addons/repository.xbmc.org/addon.xml« 
zu überschreiben, welches auch in Paket kodi-data 2:17.3+dfsg1-3 ist
InstallationDate: Installed on 2017-10-27 (0 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: kodi
Title: package kodi-repository-kodi (not installed) failed to install/upgrade: 
Versuch, »/usr/share/kodi/addons/repository.xbmc.org/addon.xml« zu 
überschreiben, welches auch in Paket kodi-data 2:17.3+dfsg1-3 ist
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kodi (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package kodi-repository-kodi (not installed) failed to
  install/upgrade: Versuch,
  »/usr/share/kodi/addons/repository.xbmc.org/addon.xml« zu
  überschreiben, welches auch in Paket kodi-data 2:17.3+dfsg1-3 ist

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

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

[Bug 1720262] Re: gnome-screenshot Actions don't work in default Ubuntu 17.10 session

2017-10-26 Thread Khurshid Alam
They work fine on Unity. it's a wayland problem. But why deny xorg users
because of that?

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

Title:
  gnome-screenshot Actions don't work in default Ubuntu 17.10 session

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1720262/+subscriptions

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

[Bug 1726922] Re: gnome-calendar keeps asking for my google password

2017-10-26 Thread Doug Reese
Could it be that I had previously allowed me in due to having performed
the second auth before the upgrade?  Aside from that, it's possible I
performed the auth during the initial stages of the upgrade and don't
remember now.

That said, it just seemed strange and potentially relevant that I am
repeatedly asked for my Google account login without being asked for an
auth code.

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

Title:
  gnome-calendar keeps asking for my google password

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

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

[Bug 1706247] Re: It should not be possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV

2017-10-26 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  It should not be possible to turn on 16g huge pages on Ubuntu 16.04.2
  PowerNV

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

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

[Bug 232170] Re: EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu (8.04 Hardy LTS, Intrepid Alpha 1)

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 41 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451182.

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


On 2008-06-13T08:51:47+00:00 Carlo wrote:

Description of problem: FN keys in eeePC don't work out of the box, there is the
need to write down some scripts to handle these events

  
Actual results:
we got working wireless on/off, display to external monitor, volume controls,
with these scripts (just workarounds):
http://fedoraproject.org/wiki/EeePc#ACPI_support_in_Fedora_9

Expected results:
OOTB Acpi support in fedora, without need of manual tweaking

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


On 2008-06-13T18:25:40+00:00 Bastien wrote:

This should be done in the kernel, with the module handling the Eeepc using the
input layer to push the events to user-space.

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


On 2008-06-14T08:21:31+00:00 Chuck wrote:

(In reply to comment #1)
> This should be done in the kernel, with the module handling the Eeepc using 
> the
> input layer to push the events to user-space.

I've replaced the preliminary eeepc driver in F9 with the final eeepc-laptop
driver from rawhide/2.6.26.  If that one doesn't work by using the input layer
to push the events then you are asking for a rewrite of the driver.


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


On 2008-06-14T08:22:29+00:00 Chuck wrote:

(In reply to comment #0)
> Description of problem: FN keys in eeePC don't work out of the box, there is 
> the
> need to write down some scripts to handle these events
> 
>   
> Actual results:
> we got working wireless on/off, display to external monitor, volume controls,
> with these scripts (just workarounds):
> http://fedoraproject.org/wiki/EeePc#ACPI_support_in_Fedora_9

Is there any way you can test rawhide to see if it works any better out
of the box?

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


On 2008-06-14T09:41:50+00:00 Carlo wrote:

1-rawnhide kernel
2-F9 upgraded to rawhide
3-Rawhide fresh install

which one?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/232170/comments/7


On 2008-06-14T10:57:54+00:00 Carlo wrote:

Tried kernel-2.6.26-0.67.rc6.git1 (rawihide)
reverted tweaks, acpid, etc. So stock fedora setup.

Fn+F1 (suspend) WORKS...also backlight resume (yeah!! very nice)

Fn+F2 (WIFI TOGGLE) NOT WORK... :-( (this is very useful...)

Fn+F3 and Fn+F4 (BACK LIGHT ADJUST) WORK

Fn+F5 (LCD/EXTERNAL MONITOR SWITCH) I don't know if works..because I can't test
it out... My ext monitor is broken

Fn+F6 (originally was for opening terminal in xandros) OBVIOUSLY doesn't
work..This fn is unuseful with stock linux distributions I used it in
scripts, to toggle webcam (as mandriva and other distributions do)...so it
should be an idea to let this key toggle webcam

Fn+F7 (Toggle MUTE) NOT WORK
Fn+F8 (VOLUME DOWN) NOT WORK
Fn+F9 (VOLUME UP ) NOT WORK

Thanks for attention :)


Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/232170/comments/8


On 2008-06-14T12:50:59+00:00 Bastien wrote:

(In reply to comment #5)
> Tried kernel-2.6.26-0.67.rc6.git1 (rawihide)
> reverted tweaks, acpid, etc. So stock fedora setup.
> 
> Fn+F1 (suspend) WORKS...also backlight resume (yeah!! very nice)

> Fn+F3 and Fn+F4 (BACK LIGHT ADJUST) WORK

> Fn+F7 (Toggle MUTE) NOT WORK
> Fn+F8 (VOLUME DOWN) NOT WORK
> Fn+F9 (VOLUME UP ) NOT WORK

The backlight and suspend keys working is good (I guess this gets through ACPI,
and is captured by hal and passed onto gnome-power-manager). Do the backlight
keys show a popup when in GNOME?

The other keys not working is a bit of a problem, but they're not expected to
work out-of-the-box for the most part.

I checked out the eeepc-laptop driver in the linux-next git tree, and it doesn't
pass those extra keys through the input layer (so the keys aren't visible in
user-space).

Could you check whether you see any error messages in dmesg when using the keys,
or whether the keys work using "xev" while running X?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/232170/comments/9


On 

[Bug 464031] Re: Cannot do screen capture of xclock window

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=548654.

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


On 2009-12-18T02:36:58+00:00 Ian wrote:

Created attachment 379140
Incorrect title bar colors with zorder of xclock(top) then gedit then terminal.

Description of problem:

xclock title bar does not change to reflect that xclock window has
focus. Using default Fedora 12 setup, title bar should change to blue,
but stays off-white/light gray when desktop effects = Compiz is enabled.
Not a problem if desktop effects = standard.

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

System AMD X86-64 with Radeon HD3450 graphics using 
mesa-dri-drivers-experimental-7.6-0.13.fc12.x86_64 and 
xorg-x11-apps-7.4-8.fc12.x86_64
Linux attic4 2.6.31.6-166.fc12.x86_64 #1 SMP Wed Dec 9 10:46:22 EST 2009 x86_64 
x86_64 x86_64 GNU/Linux

How reproducible:

Install mesa-dri-drivers-experimental-7.6-0.13.fc12.x86_64
Run xclock
Click on title bar of xclock

Actual results:
Title bar does not hcange color.

Expected results:
Title bar should change to blue (or whatever is appropriate to current theme)

Additional info:

Note the attached screenshot. Even though xclock has been dragged over
gedit, alt-print-screen geenrates a file name for the saved screen image
as if gedit still has focus. Note also that gedit still has the blue
title bar.

Reply at: https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer/+bug/464031/comments/6


On 2010-01-14T02:16:16+00:00 Ian wrote:

I had previously reported a related bug against Ubuntu 9.10. On further
analysis, I believe the underlying cause is probably the same. The other
report is at https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer/+bug/464031

Reply at: https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer/+bug/464031/comments/9


On 2010-01-27T21:31:07+00:00 Matěj wrote:

Colors of windows is a matter of the window manager. Reassigning to
compiz.

Reply at: https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer/+bug/464031/comments/10


On 2010-11-04T03:04:00+00:00 Bug wrote:


This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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/fglrx-
installer/+bug/464031/comments/71


On 2010-11-19T16:14:19+00:00 Ian wrote:

The bug is reproducible on Fedora 13 with desktop effects enabled on an
AMD X86_64 system with Nvidia graphics.

Reply at: https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer/+bug/464031/comments/72


On 2010-12-04T01:30:53+00:00 Bug wrote:


Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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/fglrx-
installer/+bug/464031/comments/73


[Bug 79078] Re: Receive hangs regularly

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=217568.

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


On 2006-11-28T18:05:55+00:00 John wrote:

Description of problem:
After using evolution for a while, I get to a point when I can no longer send
mail.  Clicking on "Send/Recieve" hangs waiting for the SMTP transaction to
complete, which doesn't.  I attached a screenshot of that dialog.  Trying to
quit out of evolution at this point just hangs.  killall evolution is the only
way out.

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


How reproducible:
2 for 2 so far since installing RHEL5 Beta2

Steps to Reproduce:
1. start evolution
2. use for a while
3. click "send/receive" and watch the SMTP send "waiting"
  
Actual results:
no mail gets sent;

Expected results:


Additional info:

So, to get out of this, one must quit evolution. BUT, evolution hangs exiting.
killall evolution.  Upon restart, sending mail works again.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/0


On 2006-11-28T18:05:55+00:00 John wrote:

Created attachment 142312
screenshot of the send/receive popup

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/1


On 2006-11-29T14:56:06+00:00 John wrote:

I'm finding myself having to "killall evolution" at least 6 times a day now. 
I'd say that's a useability issue.  Probably something that needs to get fixed
before we ship IMHO.  Setting blocker to ?


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/79078/comments/2


On 2006-11-29T15:14:30+00:00 Rod wrote:

I have this issue constantly also.  Beta2.

It is worth noting that I have other issues with evolution (every quit causes a
crash and bug buddy pops up, find contacts does not work by any field, etc.)

I will open other bzs on those



Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/79078/comments/3


On 2006-12-15T14:52:25+00:00 Matthias wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/4


On 2006-12-15T16:08:21+00:00 Tim wrote:

As described in Bug 219819, I can trigger this pretty readily on some machines
by performing two send/receives in quick succession or by performing a
send/receive right after a single mail send. In other words, the problem occurs
immediately instead of after a few hours.

For what it's worth, the fedora evolution has, so far, not shown me this
error.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/5


On 2007-01-08T17:20:43+00:00 Matthew wrote:

I found a couple similar upstream bugs, but there's been no progress on either
of them.  One was from an Ubuntu user.

http://bugzilla.gnome.org/show_bug.cgi?id=382540
http://bugzilla.gnome.org/show_bug.cgi?id=384183

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/6


On 2007-01-09T12:15:12+00:00 Alexander wrote:

Its also mentioned in:
http://bugzilla.gnome.org/show_bug.cgi?id=317213

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/7


On 2007-01-09T12:17:36+00:00 Alexander wrote:

Corresponding for fc6 is bug 208724

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/8


On 2007-01-10T14:09:18+00:00 Alexander wrote:

Created attachment 145255
Fix for EMsgPort race

I figured this out. Its a race condition in the new EMsgPort implementation.
e_msgport_wait() saves the message in msgport->cache and returns it later in
e_msgport_get(). However, two threads can end up running e_msgport_wait() (if
two threads are waiting and two messages are put), which will result in cache
being overwritten with the last message.

This patch fixes it by making cache a list.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/79078/comments/9


[Bug 445009] Re: Eclipse SIGSEGVs in libpango

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 47 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=522187.

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


On 2009-09-09T17:28:11+00:00 Mark wrote:

Eclipse 3.5 crashes. As I understand the problem is with java and
libpango (pango_layout_new).

OS: Fedora 12 Alpha (last updated on 9.9.2009 from rawhide) (OS:Fedora
release 11.91 (Rawhide))

Java: tried on many versions e.g. j2sdk1.4.2_19, jdk1.5.0_20,
jdk1.6.0_16 and even jdk1.7.0M4 (7.0 milestone 4).

To reproduce the problem open in Eclipse: Help -> Install New Software
-> and just press "Cancel". What I get is:

(That was produced using java 7.0 M4 but as I wrote it can be reproduced using 
older java vesions too):
 
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00e04059, pid=13953, tid=3086444224
#
# JRE version: 7.0-b66
# Java VM: Java HotSpot(TM) Client VM (16.0-b06 mixed mode, sharing linux-x86 )
# Problematic frame:
# C  [libpango-1.0.so.0+0x23059]  pango_layout_new+0x39
#
# An error report file with more information is saved as:
# /home/mel/hs_err_pid13953.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

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


On 2009-09-09T17:28:51+00:00 Mark wrote:

Created attachment 360285
the error attachement

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


On 2009-09-14T16:01:35+00:00 Mat wrote:

Created attachment 360967
OpenJDK Client VM Droppings

I am seeing this using the current OpenJDK in Rawhide too about every
quarter of an hour or so.

java-1.6.0-openjdk-devel-1.6.0.0-31.b16.fc12.i686
pango-1.25.5-1.fc12.i686

Its making Eclipse pretty unusable.

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


On 2009-09-24T11:21:22+00:00 Fabian wrote:

Created attachment 362472
error log, after crash.

I'm also experiencing those pango/java/crahs problems with eclipse. Also
attaching a log.

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


On 2009-09-24T15:20:47+00:00 Mat wrote:

CC'ing the Eclipse brothers to see if they know anything about this.

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


On 2009-09-24T15:29:38+00:00 Andrew wrote:

I saw this in my rawhide VM (been having a hard time installing it on
bare metal) and was going to try to reproduce.

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


On 2009-09-26T04:06:37+00:00 Behdad wrote:

There's no way a legit crash can happen in pango_layout_new().  Here's
the code for that function:

PangoLayout * 
pango_layout_new (PangoContext *context) 
{ 
  PangoLayout *layout; 
 
  g_return_val_if_fail (context != NULL, NULL); 
 
  layout = g_object_new (PANGO_TYPE_LAYOUT, NULL); 
 
  layout->context = context; 
  g_object_ref (context); 
 
  return layout; 
} 


So, either context passed to it is NULL, or this is a memory corruption 
happening somewhere else.  I can't do anything about it.

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


On 2009-09-28T18:10:58+00:00 Mark wrote:

After updating to rawhide on 28.09.2009 I have not noticed previous
behaviour since then. I cannot reproduce any more Java (Eclipse) crash
with these new rpms.

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


On 2009-09-29T17:50:11+00:00 Matthias wrote:

Could you reproduce them reliably before that update ?

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


On 2009-09-29T18:32:18+00:00 Mark wrote:

Tell me what do you need. I have been updating every day but I did not
check every day if all is ok with Java and Eclipse. I am sure that
before that update Eclipse crashed but after that update 

[Bug 218070] Re: Nautilus not showing the desktop icons & wallpaper on login

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=447446.

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


On 2008-05-19T22:47:17+00:00 Ilya wrote:

Description of problem:

After system logon no file manager is started and desktop does not display any
icons. An attachment shows the bug. This happens not always, but roughly 1/3
times the system starts. Also no greeting sound is played (but the sound system
works OK in other applications), tray applets mixed and loose their usual
positions. Sometimes network connection tooltip appears in the middle of screen,
not in the right lower corner as usual.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070/comments/16


On 2008-05-19T22:47:17+00:00 Ilya wrote:

Created attachment 306027
Screenshot

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070/comments/17


On 2008-11-02T19:48:28+00:00 Craig wrote:

Probably an upstream bug:

http://bugzilla.gnome.org/show_bug.cgi?id=545481
https://bugs.launchpad.net/fedora/+source/nautilus/+bug/218070

I see this issue on my dual-core2 Fedora 9 desktop from time to time.
Running "killall nautilus" forces Nautilus to restart, which always
fixes it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070/comments/29


On 2008-11-05T19:17:11+00:00 Michael wrote:

same on my system, dell optiplex gx280. i corroborate prior poster,
"killall nautilus" fixes it every time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070/comments/30


On 2009-06-10T01:01:24+00:00 Bug wrote:


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

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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/nautilus/+bug/218070/comments/43


On 2009-07-14T16:36:04+00:00 Bug wrote:


Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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/nautilus/+bug/218070/comments/44


** Changed in: nautilus (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/218070

Title:
  Nautilus not showing the desktop icons & wallpaper on login

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

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

[Bug 33072] Re: Pulling AC plug suspends computer

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 46 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=187396.

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


On 2006-03-30T18:23:10+00:00 Teguh wrote:

Description of problem:
When i unplugged the AC adapter, my laptop goes to hibernate (my battere is 
full)

Version-Release number of selected component (if applicable):
gnome-power-manager-2.14.0-1

How reproducible:
always

Steps to Reproduce:
1. Open gnome-power-manager preference
2. Click on 'Running on AC' tab
3. Change 'actions when laptop lid is closed' to 'hibernate'
4. Unplug the AC adapter
  
Actual results:
system is hibernate

Expected results:
keep running

Additional info:
my system:
ibm g40

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/15


On 2006-03-30T18:35:21+00:00 Richard wrote:

As root, can you do:

cat /var/log/messages | grep gnome

and reply with the output here.

Thanks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/16


On 2006-03-31T03:59:47+00:00 Teguh wrote:

Here the output ..

Mar 31 11:02:25 gazebo gnome-power-manager: Hibernating computer because the lid
has been closed, and the ac adapter removed


I'm not close the lid (just unplugged the ac adaptor), don't know why the
messages say the lid is closed


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/33072/comments/17


On 2006-03-31T09:39:44+00:00 Richard wrote:

Can you grab me a g-p-m verbose trace when this happens please. Thanks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/19


On 2006-03-31T15:07:57+00:00 David wrote:

Created attachment 127129
gpm verbose trace

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/20


On 2006-03-31T16:25:28+00:00 Richard wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/21


On 2006-03-31T16:30:19+00:00 Richard wrote:

Okay, that was exactly what I was expecting. Can you please try to reproduce the
problem again, but this time run "lshal -m" as the computer (wrongly) suspends.

Thanks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/22


On 2006-03-31T16:37:21+00:00 Richard wrote:

Also, I need the complete gpm verbose trace, including the initialisation stuff.
Thanks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/23


On 2006-03-31T16:38:42+00:00 Daniel wrote:

Start monitoring devicelist:
-
acpi_AC property ac_adapter.present = false
acpi_BAT0 property battery.charge_level.percentage = 94 (0x5e)
acpi_BAT0 property battery.remaining_time = 13464 (0x3498) (new)
acpi_BAT0 property battery.charge_level.rate = 18925500 (0x120c7bc)
acpi_BAT0 property battery.charge_level.current = 70784700 (0x43816bc)
acpi_BAT0 property battery.voltage.current = 12265 (0x2fe9)
acpi_BAT0 property battery.reporting.rate = 1705 (0x6a9)
acpi_BAT0 property battery.reporting.current = 6377 (0x18e9)
acpi_BAT0 property battery.rechargeable.is_discharging = true
acpi_AC property ac_adapter.present = true
acpi_BAT0 property battery.charge_level.percentage = 100 (0x64)
acpi_BAT0 property battery.remaining_time removed
acpi_BAT0 property battery.charge_level.rate = 0 (0x0)
acpi_BAT0 property battery.charge_level.current = 75013800 (0x4789ea8)
acpi_BAT0 property battery.voltage.current = 12417 (0x3081)
acpi_BAT0 property battery.reporting.rate = 1 (0x1)
acpi_BAT0 property battery.reporting.current = 7200 (0x1c20)
acpi_BAT0 property battery.rechargeable.is_discharging = false


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/33072/comments/24


On 2006-03-31T17:55:07+00:00 David wrote:

Created attachment 127140
full gpm verbose output

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/33072/comments/25


[Bug 1637709] Re: Lenovo Ideapad 100 webcam always on

2017-10-26 Thread Kai-Heng Feng
Please try the kernel here:
http://people.canonical.com/~khfeng/lp1637709/

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

Title:
  Lenovo Ideapad 100 webcam always on

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

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

[Bug 1720304] Re: lsvpd: Do not run vpdupdate during installation

2017-10-26 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   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/1720304

Title:
  lsvpd: Do not run vpdupdate during installation

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

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

[Bug 1296085] Re: HP LaserJet 1020 io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1047135.

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


On 2013-12-29T11:12:05+00:00 Kuznetsov wrote:

Description of problem:
After upgrade to Fedora 20 printer HP 1020 stopped to print. Usually in such 
case I just run hp-setup and re-install the driver. But after upgrade to Fedora 
20 hp-setup cannot find the printer. Now I see the following: 

% hp-setup

HP Linux Imaging and Printing System (ver. 3.13.11)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-13 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Searching... (bus=usb, search=(None), desc=0)
error: No devices found on bus: usb

Version-Release number of selected component (if applicable):
hplip.x86_64 3.13.11-4.fc20
hplip-common.x86_64 3.13.11-4.fc20
hplip-gui.x86_64 3.13.11-4.fc20
hplip-libs.x86_64 3.13.11-4.fc20


How reproducible:
every time

Steps to Reproduce:
1. connect HP 1020 to workstation with USB cable
2. run hp-setup
3. Chose 'Universal Serial Bus (USB)' as Connection Type.
4. Click Next

Actual results:
No devices found.


Expected results:
Utility found the printer.


Additional info:

On other hand lsusb shows the printer:

% lsusb
Bus 002 Device 004: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 09da:024f A4 Tech Co., Ltd RF Receiver and G6-20D 
Wireless Optical Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1296085/comments/0


On 2014-01-06T15:31:01+00:00 Jiri wrote:

Can you show me output of:
# sudo /usr/lib/cups/backend/usb

Also can you try the following commands and let me know if there's any change:
# hp-setup -g -i 03f0:2b17
# hp-setup -g -i -a 03f0:2b17
# hp-setup -g -i -b usb

If  you want to show me output longer then few lines, please save it
into a file and use 'Add an attachment' link above.

See http://hplipopensource.com/hplip-web/tech_docs/man_pages/setup.html
for description of the options.


Thanks

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1296085/comments/1


On 2014-01-07T14:32:41+00:00 Kuznetsov wrote:

Hi Jiri,

Thank you for the reply.
Here is the additional info.

> Can you show me output of:
> # sudo /usr/lib/cups/backend/usb

[neuron@sshost]~% sudo /usr/lib/cups/backend/usb
[sudo] password for neuron: 
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 68 quirks.
DEBUG: list_devices
DEBUG: libusb_get_device_list=11
DEBUG2: Printer found with device ID:  Device URI: usb://Unknown/Printer
direct usb://Unknown/Printer "Unknown" "Unknown" "" ""

> Also can you try the following commands and let me know if there's any change:
> # hp-setup -g -i 03f0:2b17
> # hp-setup -g -i -a 03f0:2b17
> # hp-setup -g -i -b usb

Please refer to hp-setup1.log, hp-setup2.log, hp-setup3.log
respectively.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1296085/comments/2


On 2014-01-07T14:34:12+00:00 Kuznetsov wrote:

Created attachment 846700
hp-setup -g -i 03f0:2b17

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1296085/comments/3


On 2014-01-07T14:34:48+00:00 Kuznetsov wrote:

Created attachment 846701
hp-setup -g -i -a 03f0:2b17

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1296085/comments/4


On 2014-01-07T14:35:40+00:00 Kuznetsov wrote:

Created attachment 846702
hp-setup -g -i -b usb

Reply at:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1296085/comments/5


On 2014-01-08T16:45:58+00:00 Jiri wrote:

(In reply to Kuznetsov Vyacheslav from comment #0)
> Bus 002 Device 004: ID 03f0:2b17 Hewlett-Packard LaserJet 1020

(In reply to Jiri Popelka from 

[Bug 517478] Re: remotely executed netcat (nc) uses -q option which is not universally supported

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=562176.

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


On 2010-02-05T14:36:43+00:00 Ziegler wrote:

Description of problem:

>From debian-based distributions (Ubuntu in my case) I can't connect to 
>none-debian based distros with remote tunel over SSH (qemu+ssh) - virsh / 
>virt-manager.
 
I attach patch from Ubuntu (Debian) which is applied on nc. This patch adds q 
option [quit after EOF on stdin and delay of secs (-1 to not quit)].


How reproducible:
Ubuntu 9.10 (10.04) as administrator desktop system.
RedHat as server system.


Steps to Reproduce:
1. From Ubuntu to RedHat (xxx.xxx.xxx.xxx)
$ virsh -c qemu+ssh://r...@xxx.xxx.xxx.xxx/system

  
Actual results:
Can't connect to libvirt via virsh / virt-manager from Ubuntu.

Expected results:
Can connect to libvirt via virsh / virt-manager from Ubuntu.


Additional info:
I use Fedora and CentOS on my host machines (servers) and Ubuntu on my desktop.

Reported as bug:
for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478
for CentOS: http://bugs.centos.org/view.php?id=4188

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478/comments/5


On 2010-02-05T14:46:40+00:00 Jan wrote:

I'm setting proper flags for product management to consider inclusion in
RHEL 5.6

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478/comments/6


On 2010-02-05T14:46:47+00:00 Ziegler wrote:

Created attachment 389086
nc -q option patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478/comments/7


On 2010-03-13T14:57:54+00:00 Ziegler wrote:

Created attachment 399858
autodetect nc params

This patch was written by Marc Deslauriers from Ubuntu and inspired by
http://hg.fedorahosted.org/hg/virt-manager/rev/1f781890ea4a and I hope
that Marc sent this patch to upstream.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478/comments/18


On 2011-04-01T12:07:38+00:00 Petr wrote:

I don't really like the idea of adding more options not accepted upstream.
Moreover, EL5+ and Fedora netcats quit after SIGHUP so I don't really see a 
problem there.

If anything, libvirt shouldn't rely on such made-up option.

Could you elaborate on what's actually expected?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478/comments/24


On 2011-08-25T13:01:31+00:00 Petr wrote:

Apparently Debian patched their client.

There's no need to add an exception to server for this; closing.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478/comments/25


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

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

** Bug watch added: bugs.centos.org/ #4188
   https://bugs.centos.org/view.php?id=4188

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

Title:
  remotely executed netcat (nc) uses -q option which is not universally
  supported

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

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

[Bug 1278529] Re: Using S3, "BackendException: No connection to backend"

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1108947.

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


On 2014-06-12T23:55:15+00:00 Eric wrote:

Description of problem: When using Duplicity I receive the error
"BackendException: No connection to backend" when attempting to backup
to Amazon S3.


Version-Release number of selected component (if applicable):
0.6.24-2.fc20

How reproducible: Always


Steps to Reproduce:
1. Attempt to backup using Deja-Dup to Amazon S3
2.
3.

Actual results:
BackendException: No connection to backend

Expected results:
Backup occurs.

Additional info:

Reply at: https://bugs.launchpad.net/duplicity/+bug/1278529/comments/28


On 2014-07-01T01:42:34+00:00 Dave wrote:

On F19 I experienced the same behavior.  I haven't tested exhaustively,
but I believe I have it working by *both*:

1) creating ~/.boto per
http://boto.readthedocs.org/en/latest/getting_started.html

2) manually creating the buckets I wanted to use for the backups

Reply at: https://bugs.launchpad.net/duplicity/+bug/1278529/comments/29


On 2014-07-04T15:35:04+00:00 David wrote:

Experiencing the same issue here

F19 x64 deja-dup-26.0-1.fc19.x86_64

Dave Allan's workaround is functional; to findout the correct bucket
it's trying to use however run:

DEJA_DUP_DEBUG=1 deja-dup --backup

Pay attention to the

DUPLICITY: . Args: /usr/bin/duplicity collection-status line,

--s3-use-new-style s3+http://deja-dup-auto-/YOUR_FOLDER


DUPLICITY: INFO 1
DUPLICITY: . Backend error detail: Traceback (most recent call last):
DUPLICITY: .   File "/usr/bin/duplicity", line 1502, in 
DUPLICITY: . with_tempdir(main)
DUPLICITY: .   File "/usr/bin/duplicity", line 1496, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: .   File "/usr/bin/duplicity", line 1345, in main
DUPLICITY: . do_backup(action)
DUPLICITY: .   File "/usr/bin/duplicity", line 1374, in do_backup
DUPLICITY: . sync_archive(decrypt)
DUPLICITY: .   File "/usr/bin/duplicity", line 1104, in sync_archive
DUPLICITY: . remlist = globals.backend.list()
DUPLICITY: .   File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", 
line 429, in list
DUPLICITY: . return map(tobytes, self._list())
DUPLICITY: .   File 
"/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 
297, in _list
DUPLICITY: . raise BackendException("No connection to backend")
DUPLICITY: . BackendException: No connection to backend
DUPLICITY: . 

DUPLICITY: ERROR 23 BackendException
DUPLICITY: . BackendException: No connection to backend


1) The error is miss leading the connection to s3 appears fine; this is instead 
the absense of a bucket being present (additional checking required).
2) deja _used_ to auto create buckets; but no longer does so (regression?)
3) From the gui you may specify the folder but not the bucket compounding the 
issue.

Reply at: https://bugs.launchpad.net/duplicity/+bug/1278529/comments/31


On 2014-07-04T15:59:09+00:00 David wrote:

ok spoke too soon now seeing:


DUPLICITY: WARNING 1
DUPLICITY: . Upload 
's3+http://deja-dup-auto-XX/YY/duplicity-full.20140704T155414Z.vol1.difftar.gpg'
 failed (attempt #2, reason: error: [Errno 104] Connection reset by peer)

DUPLICITY: DEBUG 1
DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
DUPLICITY: .   File 
"/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 
248, in put
DUPLICITY: . self.upload(source_path.name, key, headers)
DUPLICITY: .   File 
"/usr/lib64/python2.7/site-packages/duplicity/backends/_boto_single.py", line 
365, in upload
DUPLICITY: . num_cb=(max(2, 8 * globals.volsize / (1024 * 1024)))
DUPLICITY: .   File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 
1315, in set_contents_from_filename
DUPLICITY: . encrypt_key=encrypt_key)
DUPLICITY: .   File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 
1246, in set_contents_from_file
DUPLICITY: . chunked_transfer=chunked_transfer, size=size)
DUPLICITY: .   File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 
725, in send_file
DUPLICITY: . chunked_transfer=chunked_transfer, size=size)
DUPLICITY: .   File "/usr/lib/python2.7/site-packages/boto/s3/key.py", line 
914, in _send_file_internal
DUPLICITY: . query_args=query_args
DUPLICITY: .   File "/usr/lib/python2.7/site-packages/boto/s3/connection.py", 
line 633, in make_request
DUPLICITY: . retry_handler=retry_handler
DUPLICITY: .   File 

[Bug 513011] Re: [drm:radeon_cs_ioctl] Failed to parse relocation error when switching resolutions on HP NX7000 on Lucid

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=547598.

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


On 2009-12-15T03:52:37+00:00 Dan wrote:

Created attachment 378424
X log from resolution switch attempt

Switching resolution on my T42 results in a black screen, though I can
hit ESC and return to the previous mode without problems.  Happens 100%
of the time when switching to 800x600 (since the S-Video output only
does 800x600).  This didn't happen shortly before F12 Gold but regressed
some time after that.

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility
M7 LW [Radeon Mobility 7500]

kernel-2.6.31.6-166.fc12.i686
xorg-x11-drv-ati-6.13.0-0.12.20091119git437113124.fc12.i686
libdrm-2.4.15-6.fc12.i686
xorg-x11-server-Xorg-1.7.1-7.fc12.i686
mesa-libGL-7.6-0.17.fc12.i686

Running in AGP mode.

Interesting log bits:


[drm] LVDS-13: set mode  18
Unpin not necessary for f2881e00 !
[drm] LVDS-13: set mode  1a

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


On 2009-12-15T03:54:44+00:00 Dan wrote:

Attempting to switch to any mode other than 1024x768 (native panel
resolution) fails.  Other dmesg logs from other attempts:

[drm] LVDS-13: set mode  1b
Unpin not necessary for f320de00 !
[drm] LVDS-13: set mode  1d
[drm] LVDS-13: set mode  1e
Unpin not necessary for f3141300 !
[drm] LVDS-13: set mode  20

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


On 2010-01-14T08:15:42+00:00 Dave wrote:

Please retry with kernel 2.6.32.3-24 along with libdrm/xorg-x11-drv-
ati/mesa from updates-testing

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


On 2010-02-15T19:31:35+00:00 Dan wrote:

On rawhide with this laptop (t42) now, and resolution switching does not
work.

I don't get any error messages in the kernel logs, *or* in Xorg.0.log,
but I simply get a black screen.  Xorg.0.log says:

[   336.852] (II) RADEON(0): EDID for output VGA-0
[   336.856] (II) RADEON(0): EDID for output DVI-0
[   336.856] (II) RADEON(0): EDID for output LVDS
[   336.857] (II) RADEON(0): Not using default mode "320x240" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "400x300" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "400x300" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "512x384" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "640x480" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "640x512" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "800x600" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "896x672" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "928x696" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "960x720" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "700x525" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Not using default mode "1024x768" (doublescan mode 
not supported)
[   336.857] (II) RADEON(0): Printing probed modes for output LVDS
[   336.858] (II) RADEON(0): Modeline "1024x768"x60.4   65.00  1024 1040 1176 
1336  768 769 775 805 (48.7 kHz)
[   336.858] (II) RADEON(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz)
[   336.858] (II) RADEON(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz)
[   336.858] (II) RADEON(0): Modeline "800x600"x59.9   38.25  800 832 912 1024  
600 603 607 624 -hsync +vsync (37.4 kHz)
[   336.858] (II) RADEON(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  
600 601 603 625 +hsync +vsync (35.2 kHz)
[   336.858] (II) RADEON(0): Modeline "848x480"x59.7   31.50  848 872 952 1056  
480 483 493 500 -hsync +vsync (29.8 kHz)
[   336.858] (II) RADEON(0): Modeline "720x480"x59.7   26.75  720 744 808 896  
480 483 493 500 -hsync +vsync (29.9 kHz)
[   336.858] (II) RADEON(0): Modeline "640x480"x59.9   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz)
[   336.858] (II) RADEON(0): Modeline "640x480"x59.4   23.75  640 664 720 800  
480 483 487 500 -hsync +vsync (29.7 kHz)
[   336.864] (II) RADEON(0): EDID for output 

[Bug 542731] Re: [gm45] Xorg crash - Failed to submit batchbuffer: No space left on device

2017-10-26 Thread Bug Watch Updater
** 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/542731

Title:
  [gm45] Xorg crash - Failed to submit batchbuffer: No space left on
  device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/542731/+subscriptions

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

[Bug 1496357] Re: XML error: ram attribute only supported for type of qxl

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1169295.

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


On 2014-12-01T09:37:43+00:00 zhoujunqin wrote:

Description of problem:
virt-manager should remove "vgamem" from guest automatically when change video 
from "qxl" to "vga"

Version-Release number of selected component (if applicable):
libvirt-1.2.8-9.el7.x86_64
virt-manager-1.1.0-8.el7.noarch
qemu-kvm-rhev-2.1.2-13.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install a guest via virt-manager with qxl video:
...

  
  

...

2. Launch virt-manager, change guest video from qxl to vga: Double click
guest name-->Show virtual hardware details-->change video from qxl to
vga-->Apply

Actual results:
After click "Apply" button, get such error message:

Error changing VM configuration: XML error: vgamem attribute only
supported for type of qxl

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/addhardware.py", line 1384, in 
change_config_helper
vm.redefine_cached()
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 222, in 
redefine_cached
self._redefine_xml(xml)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 247, in 
_redefine_xml
return self._redefine_helper(origxml, newxml)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 239, in 
_redefine_helper
self._define(newxml)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1041, in _define
self.conn.define_domain(newxml)
  File "/usr/share/virt-manager/virtManager/connection.py", line 694, in 
define_domain
return self._backend.defineXML(xml)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3442, in defineXML
if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self)
libvirtError: XML error: vgamem attribute only supported for type of qxl

Expected results:
No such error showing and can change guest video successfully.

Additional info:
1. Can also reproduce this issue when change video from qxl to cirrus.

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


On 2014-12-01T15:43:53+00:00 Giuseppe wrote:

fix proposed upstream:

https://www.redhat.com/archives/virt-tools-
list/2014-December/msg3.html

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


On 2014-12-03T03:16:51+00:00 zhoujunqin wrote:

Try to verify this bug with new build:
virt-manager-1.1.0-9.el7.noarch

Steps as Comment 0:

1. Install a guest via virt-manager with qxl video:
...

  
  

...

2. Launch virt-manager, change guest video from qxl to vga: Double click
guest name-->Show virtual hardware details-->change video from qxl to
vga-->Apply

Result: video changed to VGA successfully with no error and guest can
boot up.

 
-  
-  
+  
 
 
 

3. Rerun step2 and change video from qxl to cirrus.

 
-  
-  
+  
 

Result: video changed to Cirrus successfully with no error and guest can
boot up.

so move this bug from ON_QA to VERIFIED.

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


On 2015-03-05T10:07:37+00:00 errata-xmlrpc wrote:

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

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

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

https://rhn.redhat.com/errata/RHBA-2015-0427.html

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


** Changed in: virt-manager
   Status: Unknown => Fix Released

** 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/1496357

Title:
   XML error: ram attribute only supported for type of qxl

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

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

[Bug 205370] Re: FTP Transfer from whole directorys fails

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=448560.

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


On 2008-05-27T17:13:59+00:00 Martin wrote:

Description of problem:
The ftp file transfer of whole directories containing more than one file fails.
The error is "Datei nicht verfügbar" which means something like "File not
available".

Version-Release number of selected component (if applicable):
gvfs-0.2.3-11.fc9.i386

How reproducible:
Always

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/205370/comments/6


On 2008-05-28T09:23:57+00:00 Tomáš wrote:

Reproducible here, raising severity as this is a major issue.
Thanks for the link to Gnome bugzilla.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/205370/comments/7


On 2008-06-06T14:46:48+00:00 Tomáš wrote:

Fix for Samba shares should be included in updated gvfs-0.2.4-1 package.
Fix for FTP is under development and will be available soon.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/205370/comments/10


On 2008-06-10T15:01:55+00:00 Fedora wrote:

gvfs-0.2.4-3.fc9 has been submitted as an update for Fedora 9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/205370/comments/11


On 2008-06-11T04:36:46+00:00 Fedora wrote:

gvfs-0.2.4-3.fc9 has been pushed to the Fedora 9 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gvfs'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/F9/FEDORA-2008-5197

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/205370/comments/12


On 2008-09-03T18:50:30+00:00 Martin wrote:

Well this has been pushed to stable, hasn't it? So I'd say it can be
closed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/205370/comments/24


On 2008-09-04T08:49:53+00:00 Tomáš wrote:

gvfs-0.2.5-1.fc9 has been pushed to stable, which includes this fix.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/205370/comments/25


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

Title:
  FTP Transfer from whole directorys fails

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

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

[Bug 159026] Re: Lenovo Thinkpad x41 Tablet, X60 Tablet and X200 Tablet rotate events

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=366211.

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


On 2007-11-04T22:57:07+00:00 Luis wrote:

When I rotate my tablet, I see this in dmesg:
thinkpad_acpi: unknown LID-related hotkey event: 0x5009
thinkpad_acpi: unknown LID-related hotkey event: 0x500a


The first is 'down', the second 'up. They are unknown, so nothing happens :)

I'm not sure, frankly, exactly what should happen in F8- I have a script that
calls the following on 'down'

/usr/bin/xrandr --output LVDS --rotate right
/usr/bin/xsetwacom set stylus rotate 1

and the following on 'up':

/usr/bin/xrandr --output LVDS --rotate normal
/usr/bin/xsetwacom set stylus rotate 0

Those work OK. Not sure how to configure that, though. But it should happen by
default.

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/2


On 2007-11-04T22:58:50+00:00 Luis wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/3


On 2007-11-05T09:25:21+00:00 Matěj wrote:

Luis, could we get our usual combo -- /etc/X11/xorg.conf and
/var/log/Xorg.0.log, please? This probably *is* hardware independent, but still
I would prefer to see what Xorg thinks about your hardware and whether there are
any error messages or warnings available.

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/4


On 2007-11-05T15:27:42+00:00 Luis wrote:

Created attachment 248311
xorg.conf

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/5


On 2007-11-05T15:28:14+00:00 Luis wrote:

Created attachment 248321
xorg.0.log

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/6


On 2007-11-05T15:28:53+00:00 Luis wrote:

Created attachment 248331
special bonus- lshal!

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/7


On 2008-11-26T08:12:14+00:00 Bug wrote:


This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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/acpi-
support/+bug/159026/comments/28


On 2008-12-01T02:54:36+00:00 Luis wrote:

Still a problem in F10.

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/29


On 2009-02-08T07:54:22+00:00 Adam wrote:

Fixing component, XFree86 isn't really a thing anymore.

Do you still get the same messages in dmesg?  Do you see an event for
this in xev?

Reply at: https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/159026/comments/30


On 2009-02-08T18:39:16+00:00 Luis wrote:

thinkpad_acpi no longer seems to emit those messages, and nothing in
xev. This is even 

[Bug 319111] Re: gmetad: stack based buffer overflow in interactive port

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=480236.

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


On 2009-01-15T20:23:49+00:00 Tomas wrote:

A stack-based buffer overflow was discovered in the gmetad server, part
of the ganglia monitoring system.  Quoting original report:

  In process_path() a char element[256] is allocated to contain the pieces
  of the path as it is processed. If a request is made with a path element
  longer than that the strncpy call will write to invalid memory location,
  since there is no length checking performed on the input data to make sure
  it is less than the size of element.

Full report:
http://www.mail-archive.com/ganglia-developers@lists.sourceforge.net/msg04929.html

Upstream bug:
  http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=223

Upstream fix:
  http://ganglia.svn.sourceforge.net/viewvc/ganglia?view=rev=1946
and status file note:
  http://ganglia.svn.sourceforge.net/viewvc/ganglia?view=rev=1947

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/0


On 2009-01-15T21:28:57+00:00 Kostas wrote:

Unfortunately the fix introduces an off by one error so it still needs
work.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/1


On 2009-01-16T10:04:31+00:00 Tomas wrote:

This overflow occurs in the strncpy call (which uses input length as a
bound, not a destination buffer size) and it is detected by the
FORTIFY_SOURCE.  Therefore, this can no be exploited for code execution,
overflow is detected before data are written past the end of the buffer
and program execution is terminated.  This is DoS-only flaw on Fedora or
Red Hat HPC Solution.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/2


On 2009-01-18T07:31:22+00:00 Arenas wrote:

could a CVE be requested by redhat's CNA to easy up tracking for all
affected parties?, AFAIK there is a securityfocus BID already assigned
in :

  http://www.securityfocus.com/bid/33299

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/3


On 2009-01-19T08:09:25+00:00 Tomas wrote:

We do not assign ids for already public issues, to minimize the risk of 
duplicating Mitre's assignments.  Request for id was done couple of days ago 
via a list that is monitored by Mitre for new issues:
  http://www.openwall.com/lists/oss-security/2009/01/15/3

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/4


On 2009-01-19T08:22:24+00:00 Tomas wrote:

(In reply to comment #1)
> Unfortunately the fix introduces an off by one error so it still needs work.

Current version of the patch, including your fix for off-by-one:
http://ganglia.svn.sourceforge.net/viewvc/ganglia/trunk/monitor-core/gmetad/server.c?r1=1233=1950

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/5


On 2009-01-20T08:24:48+00:00 Tomas wrote:

The patch was updated again upstream, fixing another off-by-one in the 
request[] buffer:
http://ganglia.svn.sourceforge.net/viewvc/ganglia?view=rev=1953

Whole patch:
http://ganglia.svn.sourceforge.net/viewvc/ganglia/trunk/monitor-core/gmetad/server.c?r1=1233=1953

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/7


On 2009-01-20T22:11:56+00:00 Fedora wrote:

ganglia-3.1.1-3.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/ganglia-3.1.1-3.fc10

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/8


On 2009-01-20T22:13:27+00:00 Fedora wrote:

ganglia-3.0.7-4.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/ganglia-3.0.7-4.fc9

Reply at: https://bugs.launchpad.net/ubuntu/+source/ganglia-monitor-
core/+bug/319111/comments/9


On 2009-01-21T14:14:34+00:00 Tomas wrote:

CVE-2009-0241:
Stack-based buffer overflow in the process_path function in
gmetad/server.c in 

[Bug 424655] Re: using module-udev-detect leaks memory

2017-10-26 Thread Bug Watch Updater
** Changed in: pulseaudio (Fedora)
   Status: Unknown => Fix Released

** Changed in: pulseaudio (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/424655

Title:
  using module-udev-detect leaks memory

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

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

[Bug 506647] Re: Can't login to ICQ or AIM servers "Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession"

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=554978.

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


On 2010-01-13T09:59:15+00:00 Lev wrote:

Description of problem:
Today I was not able to login to ICQ using pidgin. I've got the message
"Received unexpected response from 
http://api.oscar.aol.com/aim/startOSCARSession; instead.

Version-Release number of selected component (if applicable):
pidgin-2.6.5-1.fc12.i686
libpurple-2.6.5-1.fc12.i686

How reproducible:
Always.

Steps to Reproduce:
1. Install pidgin
2. Setup an icq account with default options.
3. Try to login
  
Actual results:
"Received unexpected response from 
http://api.oscar.aol.com/aim/startOSCARSession;

Expected results:
Normal work

Additional info:
The problem can be 'fixed' by disabling 'use clientLogin' in the advanced 
settings tab.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/7


On 2010-01-13T17:30:47+00:00 Chris wrote:

I am able to replicate this same error message in Windows 7 x64 using
Pidgin 2.6.4.

I am trying to sign-in to a AIM account.  Figured I'd append it to this
ticket, it may be a AOL issue causing this error, and not a bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/10


On 2010-01-13T22:35:10+00:00 Warren wrote:

There will be a package update that forces this option... but only after
upstream decides what to do about this.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/13


On 2010-01-14T15:04:56+00:00 Christopher wrote:

Similar problems in Empathy after update to libpurple-2.6.5-1 (Bug
554923 for AIM, possibly Bug 555297 for ICQ), but the noted workaround
cannot be applied.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/14


On 2010-01-17T12:09:16+00:00 Stu wrote:

I believe AOL have fixed their servers.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/506647/comments/16


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

** Changed in: pidgin (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/506647

Title:
  Can't login to ICQ or AIM servers "Received unexpected response from
  http://api.oscar.aol.com/aim/startOSCARSession;

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

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

[Bug 511558] Re: skype has lag after 0.9.21+stable-queue-24-gfa64

2017-10-26 Thread Bug Watch Updater
** Changed in: pulseaudio (Fedora)
   Status: Unknown => Fix Released

** Changed in: pulseaudio (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/511558

Title:
  skype has lag after 0.9.21+stable-queue-24-gfa64

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

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

[Bug 502375] Re: Wine randomly cannot initialize sound [ Wine and Pulseaudio fight for address space; workaround found ]

2017-10-26 Thread Bug Watch Updater
** Changed in: wine (Fedora)
   Status: Unknown => Won't Fix

** Changed in: wine (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/502375

Title:
  Wine randomly cannot initialize sound [ Wine and Pulseaudio fight for
  address space; workaround found ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-plugins/+bug/502375/+subscriptions

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

[Bug 533636] Re: ibus languagebar doesn't show MenuItem on menu.

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=552796.

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


On 2010-01-06T07:03:38+00:00 fujiwara wrote:

I'd like to add MenuItem on ibus languagebar with bug 550001.

Currently ibus supports CheckMenuItem() and RadioMenuItem() but it seems
ImageMenuItem() doesn't work.

When I apply the patch on bug 550001, ibus puts an error:
ibus.Menu receives type == ibus.PROP_TYPE_NORMAL and call 
gtk.ImageMenuItem(prop)
but the argument is not correct.
I'm attaching the patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/0


On 2010-01-06T07:05:38+00:00 fujiwara wrote:

Created attachment 381928
Patch for ibus menu.py

Attached the patch.
It seems to get an error when gtk.ImageMenuItem.__init__() is called so I 
removed it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/1


On 2010-01-06T08:48:45+00:00 fujiwara wrote:

Comment on attachment 381928
Patch for ibus menu.py

>diff --git a/ui/gtk/menu.py b/ui/gtk/menu.py

One typo. Both icon and label can be shown:

  self.set_image(icon.IconWidget(prop.icon, size[0]))
-+elif self._prop.label:
++if self._prop.label:
 +self.set_property("label", prop.label.get_text())

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/2


On 2010-01-07T03:44:26+00:00 fujiwara wrote:

Put ibus-anthy for ImageMenuItem:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1906442

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/533636/comments/3


On 2010-01-07T04:22:06+00:00 fujiwara wrote:

F11 pygtk2 had a problem:
http://git.gnome.org/browse/pygtk/commit/?id=fbb3e653ab1c4f467d7aae61e8444fab8c839af1
--- a/gtk/gtk.override
+++ b/gtk/gtk.override
@@ -2064,24 +2066,20 @@ _wrap_gtk_image_menu_item_new(PyGObject *self, PyObject 
*args,PyObject *kwargs)
-
- if (pyg_type_from_object((PyObject *) self) != GTK_TYPE_IMAGE_MENU_ITEM) {
- PyErr_SetString(PyExc_RuntimeError, "__gobject_init__ must be used "
- "when subclassing gtk.ImageMenuItem");
- return -1;
- }
-
- pygobject_register_wrapper((PyObject *)self);

The previous pygtk sent the error: "__gobject_init__ must be used when
subclassing gtk.ImageMenuItem".

But I confirmed f12 _gtk.so is fixed so this part is not needed now.
I logged this issue for the reference.

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


On 2010-01-07T05:15:26+00:00 Peng wrote:

Fixed in upstream. I will build it soon.

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


On 2010-01-11T06:49:37+00:00 Peng wrote:

Fixed in ibus-1.2.0.20100111-1.fc13

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


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

** Changed in: ibus (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/533636

Title:
  ibus languagebar doesn't show MenuItem on menu.

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

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

[Bug 1425447] Re: pulseaudio crashed with SIGABRT in core_free() at login

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1194177.

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


On 2015-02-19T09:33:02+00:00 Lubomir wrote:

Version-Release number of selected component:
pulseaudio-6.0-1.fc22

Additional info:
reporter:   libreport-2.3.0
backtrace_rating: 4
cmdline:/usr/bin/pulseaudio --start --log-target=syslog
crash_function: core_free
executable: /usr/bin/pulseaudio
kernel: 3.20.0-0.rc0.git6.1.fc22.x86_64
runlevel:   N 5
type:   CCpp
uid:42

Truncated backtrace:
Thread no. 1 (2 frames)
 #2 core_free at pulsecore/core.c:179
 #3 pa_core_unref at pulsecore/core.h:202

Potential duplicate: bug 714401

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/0


On 2015-02-19T09:33:05+00:00 Lubomir wrote:

Created attachment 993499
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/1


On 2015-02-19T09:33:06+00:00 Lubomir wrote:

Created attachment 993501
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/2


On 2015-02-19T09:33:08+00:00 Lubomir wrote:

Created attachment 993503
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/3


On 2015-02-19T09:33:10+00:00 Lubomir wrote:

Created attachment 993504
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/4


On 2015-02-19T09:33:11+00:00 Lubomir wrote:

Created attachment 993505
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/5


On 2015-02-19T09:33:12+00:00 Lubomir wrote:

Created attachment 993506
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/6


On 2015-02-19T09:33:14+00:00 Lubomir wrote:

Created attachment 993507
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/7


On 2015-02-19T09:33:15+00:00 Lubomir wrote:

Created attachment 993509
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/8


On 2015-02-19T09:33:17+00:00 Lubomir wrote:

Created attachment 993511
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/9


On 2015-02-19T09:33:18+00:00 Lubomir wrote:

Created attachment 993512
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/10


On 2016-07-19T12:50:03+00:00 Fedora wrote:

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1425447/comments/30


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

** Changed in: pulseaudio (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/1425447

Title:
  pulseaudio crashed with SIGABRT in core_free() at login

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

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

[Bug 905095] Re: qemu-img can't convert vmdk file: Operation not permitted

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=548723.

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


On 2009-12-18T11:36:07+00:00 Richard wrote:

Description of problem:

qemu-img convert cannot convert a VMDK4 format file to (eg) raw (or
anything else).  It silently produces a large file that mostly
contains zero bytes, and is completely unusable.

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

Tested with qemu-img 0.10.5, 0.11.0, and
git d9a50a366f2178 (2009-12-11).

How reproducible:

Always.

Steps to Reproduce:
1. Export to OVF from VMWare vSphere / ESX 4.0.0.
2. Copy the resultant disk image to a Fedora machine.
3. Check the SHA1 sums (from *.mf file) to make sure image was not
   corrupted during the copy.
4. Run:
 qemu-img convert -O raw TestLinux-disk1.vmdk TestLinux-disk1.raw
5. Try to mount / use the resulting raw file, eg. using guestfish.
  
Actual results:

The raw file contains mostly zeroes, see below.  It contains zeroes
where there should be partition tables, superblocks etc. and so is
totally unusable.

Expected results:

A usable disk image.

Additional info:

Compare the entropy of the VMDK file with the resulting raw disk.
I would expect the entropy to be about the same, but you can see the
raw disk is mostly compressible (zeroes).

  $ ls -l TestLinux-disk1.vmdk
  -rw-rw-r--  1 rjones rjones  887312896 2009-12-18 10:35 TestLinux-disk1.vmdk
  $ gzip -c TestLinux-disk1.vmdk | wc -c
  860846320
  $ gzip -c TestLinux-disk1.raw | wc -c
  8744715

VMWare's OVF metadata says the following about the disk format:

  

  
  
Virtual disk information
http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized;
 />
  

qemu-img 0.10.5 fails in a different way.  It gives the error
message:

  qemu-img: error while reading

qemu-img >= 0.11.0 fail silently, no error message or error code.

I've tried this with several disk images exported from vSphere 4
and they have all failed to convert in the same way.

Test files (at time of writing these are STILL UPLOADING, with ETA
of 2009-12-19).

http://homes.merjis.com/~rich/TestLinux-disk1.vmdk
  SHA1: 2C81BAE89210B075ACC51DA9D025935470149D55
http://homes.merjis.com/~rich/TestLinux.ovf
  SHA1: 30831689B8C6F1B1A1FCBB728769B5F71056A580

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


On 2010-03-09T16:53:51+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

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


On 2010-03-09T17:19:45+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

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


On 2010-03-11T19:25:48+00:00 Justin wrote:

You don't happen to know if this reproduces with qemu-img > 0.12.x or
have a test image I can convert to reproduce handy?

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


On 2010-03-11T22:04:16+00:00 Richard wrote:

Nothing much has changed in the qemu vmdk block
driver since I looked at it before (I just checked upstream
git), so it's very likely to be still broken.

I have some VMDK images, but I warn you that they
are very large!  If you have somewhere I can upload
them to, I can send some your way ...

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


On 2010-03-15T13:36:49+00:00 Bug wrote:


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

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

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


On 2011-03-23T12:40:49+00:00 Richard wrote:

I just checked upstream git for the driver again,
and apart from code cleanups the code is still the
same as ever.  Therefore moving the bug -> Rawhide.

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


On 

[Bug 1413446] Re: [Dell XPS 13 9343] Audio broken with I2S mode

2017-10-26 Thread Bug Watch Updater
** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (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/1413446

Title:
  [Dell XPS 13 9343] Audio broken with I2S mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

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

[Bug 561892] Re: gcjwebplugin doesn't build against xulrunner 1.9.2 without MOZILLA_INTERNAL_API

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=548783.

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


On 2009-12-18T15:40:50+00:00 Jakub wrote:

gcc (including 4.5) doesn't build against xulrunner-devel-1.9.2:

In file included from /usr/include/xulrunner-sdk-1.9.2/nsAString.h:43,
 from /usr/include/xulrunner-sdk-1.9.2/nsSubstring.h:40,
 from /usr/include/xulrunner-sdk-1.9.2/nsString.h:44,
 from /usr/include/xulrunner-sdk-1.9.2/nsIPluginInstance.h:26,
 from 
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:65:
/usr/include/xulrunner-sdk-1.9.2/nsStringFwd.h:49:2: error: #error Internal 
string headers are not available from external-linkage code.
In file included from /usr/include/xulrunner-sdk-1.9.2/nsAString.h:64,
 from /usr/include/xulrunner-sdk-1.9.2/nsSubstring.h:40,
 from /usr/include/xulrunner-sdk-1.9.2/nsString.h:44,
 from /usr/include/xulrunner-sdk-1.9.2/nsIPluginInstance.h:26,
 from 
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:65:
/usr/include/xulrunner-sdk-1.9.2/nsTSubstring.h:40:2: error: #error Cannot use 
internal string classes without MOZILLA_INTERNAL_API defined. Use the frozen 
header nsStringAPI.h instead.
In file included from /usr/include/xulrunner-sdk-1.9.2/nsAString.h:69,
 from /usr/include/xulrunner-sdk-1.9.2/nsSubstring.h:40,
 from /usr/include/xulrunner-sdk-1.9.2/nsString.h:44,
 from /usr/include/xulrunner-sdk-1.9.2/nsIPluginInstance.h:26,
 from 
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:65:
/usr/include/xulrunner-sdk-1.9.2/nsTSubstring.h:40:2: error: #error Cannot use 
internal string classes without MOZILLA_INTERNAL_API defined. Use the frozen 
header nsStringAPI.h instead.
In file included from /usr/include/xulrunner-sdk-1.9.2/nsReadableUtils.h:51,
 from /usr/include/xulrunner-sdk-1.9.2/nsString.h:52,
 from /usr/include/xulrunner-sdk-1.9.2/nsIPluginInstance.h:26,
 from 
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:65:
/usr/include/xulrunner-sdk-1.9.2/nsTArray.h:46:15: error: new: No such file or 
directory
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:66:35: error: 
nsIPluginInstancePeer.h: No such file or directory
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:67:31: error: 
nsIPluginTagInfo2.h: No such file or directory
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:149: error: 
'NS_IPLUGINTAGINFO2_IID' was not declared in this scope
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:207: error: 
ISO C++ forbids declaration of 'nsIPluginTagInfo2' with no type
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:207: error: 
expected ';' before '*' token
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc: In function 
'gchar* plugin_get_documentbase(NPP_t*)':
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:877: error: 
'nsIPluginInstancePeer' was not declared in this scope
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:877: error: 
'peer' was not declared in this scope
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:879: error: 
'nsIPluginTagInfo2' was not declared in this scope
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:879: error: 
'pluginTagInfo2' was not declared in this scope
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:891: error: 
'class nsIPluginInstance' has no member named 'GetPeer'
../../../../../../libjava/classpath/native/plugin/gcjwebplugin.cc:898: error: 
'union info_union' has no member named 'info_field'

Google found
http://icedtea.classpath.org/hg/icedtea6?cmd=changeset;node=8353f4e67ec1
changes to IcedTea plugin, perhaps those might be usable to some extent.
This is a blocker for gcc in f13..

Reply at:
https://bugs.launchpad.net/ubuntu/+source/classpath/+bug/561892/comments/0


On 2009-12-18T17:18:13+00:00 Andrew wrote:

I believe the plan is to remove gcjwebplugin entirely.

As far as I am aware it's simply a matter of removing

--enable-plugin

from the specfile

Deepak, please confirm.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/classpath/+bug/561892/comments/1


On 2009-12-22T03:03:02+00:00 Deepak wrote:

Created attachment 379759
Patch to remove gcjwebplugin from the gcc rpm

(In reply to 

[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1180810.

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


On 2015-01-10T14:29:42+00:00 mkwadee wrote:

Additional info:
reporter:   libreport-2.2.3
WARNING: CPU: 3 PID: 17078 at drivers/gpu/drm/i915/intel_display.c:3361 
intel_crtc_wait_for_pending_flips+0x1a5/0x1b0 [i915]()
Modules linked in: rfcomm fuse ccm fcoe libfcoe libfc scsi_transport_fc 8021q 
garp mrp ip6t_rpfilter ip6t_REJECT xt_conntrack bnep ebtable_nat ebtable_broute 
bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 
nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw 
ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw 
arc4 iwldvm mac80211 iTCO_wdt iTCO_vendor_support x86_pkg_temp_thermal coretemp 
kvm_intel kvm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
v4l2_common videodev snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec iwlwifi 
snd_hwdep cfg80211 dell_laptop dell_wmi btusb media sparse_keymap dcdbas 
crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel snd_seq 
snd_seq_device snd_pcm bluetooth snd_timer rfkill snd shpchp wmi lpc_ich mei_me 
mei soundcore mfd_core serio_raw microcode i2c_i801 binfmt_misc i915 
i2c_algo_bit drm_kms_helper r8169 drm mii video analog gameport joydev
CPU: 3 PID: 17078 Comm: kworker/u16:14 Not tainted 3.17.7-200.fc20.x86_64 #1
Hardware name: Dell Inc.  Dell System Inspiron N7110/0YH79Y, BIOS A08 
10/24/2011
Workqueue: events_unbound async_run_entry_fn
  a8f86698 88004e367b30 8172758c
  88004e367b68 81092e7d 
 88013811a000 8800360c82c0 880137046000 
Call Trace:
 [] dump_stack+0x45/0x56
 [] warn_slowpath_common+0x7d/0xa0
 [] warn_slowpath_null+0x1a/0x20
 [] intel_crtc_wait_for_pending_flips+0x1a5/0x1b0 [i915]
 [] ? prepare_to_wait_event+0xf0/0xf0
 [] intel_crtc_disable_planes+0x34/0x160 [i915]
 [] ironlake_crtc_disable+0x4d/0x7c0 [i915]
 [] ? drm_modeset_lock+0x6a/0xc0 [drm]
 [] intel_crtc_control+0x49/0x100 [i915]
 [] i915_drm_freeze+0xaa/0x1f0 [i915]
 [] i915_pm_suspend+0x2f/0x50 [i915]
 [] pci_pm_suspend+0x76/0x140
 [] ? pci_pm_freeze+0xf0/0xf0
 [] dpm_run_callback+0x4e/0x100
 [] __device_suspend+0x11e/0x340
 [] async_suspend+0x1f/0xa0
 [] async_run_entry_fn+0x39/0x120
 [] process_one_work+0x149/0x3d0
 [] worker_thread+0x11b/0x490
 [] ? rescuer_thread+0x2e0/0x2e0
 [] kthread+0xd8/0xf0
 [] ? kthread_create_on_node+0x190/0x190
 [] ret_from_fork+0x7c/0xb0
 [] ? kthread_create_on_node+0x190/0x190

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384342/comments/55


On 2015-01-10T14:29:46+00:00 mkwadee wrote:

Created attachment 978525
File: dmesg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384342/comments/56


On 2015-05-27T15:47:33+00:00 Adam wrote:


*** This bug has been marked as a duplicate of bug 1136531 ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384342/comments/99


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

** Changed in: linux (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/1384342

Title:
  kernel messages intel_crtc_wait_for_pending_flips correlate to compiz
  hang

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

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

[Bug 1727816] Re: cannot enter encryption password in GUI

2017-10-26 Thread stuartbh
Steve, et alia:

Your welcome, I am happy to take the time to report bugulance in Ubuntu
so it can be markedly improved. Moreover, I marked this as a security
based bug since it involves an issue with the entrance of a password,
thus one would think it obvious to be impactive to security! I had no
idea if it was because some rouge software was installed or what, just
that it seemed patently dysfunctional on a prima facia basis. I also was
not entirely sure if security based developers were involved with its
code management or not.

The foregoing notwithstanding, I have been using Ubuntu for many years
(ever since RedHat Workstation was withdrawn from marketing) and
appreciate the goodness of Debian coupled with the ease of use Ubuntu
adds (while subtracting the extremism of some of the Debian folks that
make it difficult to install).

I can try to install 17.04 and see what occurs as well as to see if
kernel replacement under 17.10 manages to effectuate different
functionality.

Thank you for looking into it so quickly.


V/R,

Stuart

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

Title:
  cannot enter encryption password in GUI

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

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

[Bug 1688508] Re: libvirt-guests.sh fails to shutdown guests in parallel

2017-10-26 Thread Bug Watch Updater
** Changed in: libvirt
   Status: Unknown => In Progress

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

Title:
  libvirt-guests.sh fails to shutdown guests in parallel

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

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

[Bug 1726935] Re: Ubuntu dock won't start after Dash to dock uninstalled

2017-10-26 Thread frenchy82
ubuntu dock 0.7.1 solve the problem for me too.

I can now uninstall dash to dock and ubuntu dock will be active

thanks a lot

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

Title:
  Ubuntu dock won't start after  Dash to dock uninstalled

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

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

[Bug 1705870] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

2017-10-26 Thread James M Knock
Not virtual. Occurs a few minutes after boot.

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

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

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

[Bug 1727921] [NEW] installer crashed

2017-10-26 Thread davrukin
Public bug reported:

it crashed, wouldn't install grub with efi

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.387
Date: Thu Oct 26 21:22:12 2017
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  installer crashed

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

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

[Bug 1581772] Re: Cannot install Epson L355

2017-10-26 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (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/1581772

Title:
  Cannot install Epson L355

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

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

[Bug 620463] Re: If run "sudo apt-file update" only, run apt-file without sudo display nothing

2017-10-26 Thread Launchpad Bug Tracker
[Expired for apt-file (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apt-file (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/620463

Title:
  If run "sudo apt-file update" only, run apt-file without sudo display
  nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-file/+bug/620463/+subscriptions

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

[Bug 1640934] Re: copying jpg from exfat SD to ext4 HDD corrupts some jpg

2017-10-26 Thread Launchpad Bug Tracker
[Expired for fuse-exfat (Ubuntu) because there has been no activity for
60 days.]

** Changed in: fuse-exfat (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/1640934

Title:
  copying jpg from exfat SD to ext4 HDD corrupts some jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-exfat/+bug/1640934/+subscriptions

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

[Bug 1705127] Re: GTK bubble menu arrows have jaggies when not pointing straight up

2017-10-26 Thread Launchpad Bug Tracker
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gtk+3.0 (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/1705127

Title:
  GTK bubble menu arrows have jaggies when not pointing straight up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1705127/+subscriptions

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

[Bug 1713365] Re: ogg to ogg : Error initializing output stream 0:0 @ 44999 b/s

2017-10-26 Thread Launchpad Bug Tracker
[Expired for ffmpeg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ffmpeg (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/1713365

Title:
  ogg to ogg : Error initializing output stream 0:0 @ 44999 b/s

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

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

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

2017-10-26 Thread Chatty
** Summary changed:

- Boot freeze with Ubuntu 17.10-beta2 on Surface Book
+ Boot freeze with Ubuntu 17.10 Live ISO on Surface Book

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

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

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

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

[Bug 67188] Re: "Error activating XKB configuration." - Requires manual xorg.conf editing

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=446684.

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


On 2008-05-15T17:00:10+00:00 Eelco wrote:

Description of problem:
[Actually, the problem occurs in gnome-keyboard-properties, but that one was not
in the components list.]
Choosing keyboard layout Macbook/Macbook Pro (Intl) produces an error in Fedora 
9. 

Version-Release number of selected component (if applicable):
GNOME gnome-keyboard-properties 2.22.1

How reproducible:
1. start gnome-keyboard-properties
2. select layouts tab
3. select keyboard model MacBook/MacBook Pro (Intl)
4. close

Error message:
==
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
10499901

If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd



Additional info:

Hardware: Macbook (late 2006 model)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/36


On 2008-05-15T17:00:10+00:00 Eelco wrote:

Created attachment 305510
screenshot of the error message

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/37


On 2008-05-17T08:31:35+00:00 Eelco wrote:

$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "intl", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "intl", ""

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = []
 model = macbook79
 options = [Compose key compose:rwin]
 overrideSettings = true



Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/38


On 2008-05-17T13:05:12+00:00 Lubomir wrote:

Eelco: Thank you for reporting the problem, I am reassigning it to the right
component owner.

The following command might be useful to find out which component does the
binary belong to:

$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/39


On 2008-05-17T13:08:02+00:00 Eelco wrote:

$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)
control-center


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/40


On 2008-05-22T23:29:09+00:00 Jose wrote:

I'm having the same problem (MacBook with a Portuguese keyboard layout):

$ xprop -root | grep  XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "pt", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "pt", "", ""

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
 layouts = [pt  mac,pt]
 model = macbook79
 options = [grp grp:alts_toggle]
 overrideSettings = true

/jpo


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/41


On 2008-09-11T12:33:50+00:00 Peter wrote:

Eelco:

The problem is that the keysyms for mac don't provide a intl variant. The error 
can be reproduced on the commandline by running:
setxkbmap -layout us -model macbook79 -variant intl -print | xkbcomp - :0

Error:No Symbols named "intl" in the include file 
"macintosh_vndr/us"
  Exiting

If this used to work, or you think it should work, please file a bug on
upstream bugzilla: https://bugs.freedesktop.org/enter_bug.cgi?product
=xkeyboard-config

Jose:
I can't reproduce your problem. Can you try to run:
setxkbmap -layout pt -model macbook79 -option grp:alts_toggle -print | xkbcomp 
- :0
and check for an error message. If there is one, please attach it. If there is 
none, please try if the macbook79 model works with any other layout (e.g. us). 
If it does, please try to find which setting triggers the error - it could be 
the layout or the alts_toggle option (unlikely).

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/44


On 2008-10-20T21:33:16+00:00 Matěj wrote:

Reporter, could you please reply to the previous question? If you won't
reply in 

[Bug 180179] Re: [PATCH] Fix nspr warnings with -Wstrict-prototypes

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451616.

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


On 2008-06-16T08:04:25+00:00 Dan wrote:

Description of problem:
Using nspr header gives a warning in the prlink.h file when -Wstrict-prototypes
is included in the CFLAGS. And when -Werror is used, then it is not possible to
compile at all.

Version-Release number of selected component (if applicable):
nspr-devel-4.6.7-3.fc8
but the header was not changed since Apr/06/2006, so all current Fedora and RHEL
versions are affected.

How reproducible:
100%

Steps to Reproduce:
1. run the script from attachments
  
Actual results:
In file included from /usr/include/nspr4/nspr.h:55,
 from nspr-test.c:2:
/usr/include/nspr4/prlink.h:52: warning: function declaration isn’t a prototype
/usr/include/nspr4/prlink.h:209: warning: function declaration isn’t a prototype


Expected results:
No warnings

Additional info:
There was a thread in gcc mailing list about the meaning of the warning -
http://gcc.gnu.org/ml/gcc-help/2006-07/msg00033.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/8


On 2008-06-16T08:04:25+00:00 Dan wrote:

Created attachment 309468
test case

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/9


On 2008-06-16T08:08:50+00:00 Dan wrote:

Created attachment 309471
patch to remove the warnings

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/10


On 2008-07-01T13:33:41+00:00 Kai wrote:

Wan-Teh, what do you think about the proposed patch?

I should probably file an upstream bug.


Reply at: https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/11


On 2008-11-26T10:52:33+00:00 Bug wrote:


This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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/nspr/+bug/180179/comments/20


On 2009-01-09T06:36:21+00:00 Bug wrote:


Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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/nspr/+bug/180179/comments/23


On 2010-08-16T14:40:02+00:00 Elio wrote:

See https://bugzilla.mozilla.org/show_bug.cgi?id=410677
When we next re-base to NSPR 4.8.6 we will pick-up the fix.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/180179/comments/38


** Changed in: nspr (Fedora)
   Status: Won't Fix => Fix Released

** Changed in: nspr (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/180179

Title:
  [PATCH] Fix 

[Bug 268141] Re: no ssh-agent after resume from hibernate

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=454186.

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


On 2008-07-06T09:15:54+00:00 Julian wrote:

Description of problem:
After resume from either suspend or hibernate, seahorse agent does not ask for
keyring password, so for instance to commit to Fedora cvs I have to enter the
ssh keys password a few times. Before the resume a window pops out and the
password is required only once.

Version-Release number of selected component (if applicable):
2.22.2-1.fc9

How reproducible:
every time

Steps to Reproduce:
1. suspend/hibernate the machine
2. resume
3. do something that requires entering ssh key password
  
Actual results:
password prompt appears in the console every time ssh key is needed

Expected results:
a window pops out and asks for password only once

Additional info:
I don't know if it's related, but ssh-add does not work either (says “Could not
open a connection to your authentication agent.”), so there is really no way to
avoid the need for entering the password several times, apart from reboot.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/0


On 2008-08-19T17:35:07+00:00 Julian wrote:

I think you need to do something that requires entering ssh key password
before suspend as well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/1


On 2008-11-26T06:45:51+00:00 Julian wrote:

Erm, it is still present with Fedora 10. After thorough testing, I found
out that this bug is only triggered by hibernation, and that you don't
have do to anything prior to it. Do I need to say it makes hibernation
pretty much useless, since once you resume you need to input your
keyring password every time? Imagine updating a package in cvs like
that...

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/9


On 2008-12-13T19:18:07+00:00 Matthias wrote:

This is a somewhat confused bug report.

If you are talking about ssh, seahorse is not involved, gnome-keyring-
daemon is acting as ssh agent.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/10


On 2009-01-13T11:46:54+00:00 Julian wrote:

$ gnome-keyring-daemon
** Message: another SSH agent is running at: /tmp/keyring-XZf6Tg/ssh
GNOME_KEYRING_SOCKET=/tmp/keyring-SR9ZYj/socket
SSH_AUTH_SOCK=/tmp/keyring-SR9ZYj/ssh
GNOME_KEYRING_PID=17745

This is what happens if I try to start gnome-keyring-daemon manually
after waking up from hibernation.

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


On 2009-01-13T12:33:24+00:00 Julian wrote:

On the other hand, gnome-keyring-daemon does not show up in the list of
running processes.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/12


On 2009-02-05T02:26:23+00:00 Ian wrote:

Possibly related to this - gnome-keyring-daemon *sometimes* dies if left
running overnight.  For example yesterday afternoon I had this:

   > set | grep SSH
   SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
   SSH_AUTH_SOCK=/tmp/keyring-y0Zso0/ssh

   > fuser $SSH_AUTH_SOCK
 2674
   > ps h `fuser $SSH_AUTH_SOCK`
2674 ?S  0:37 /usr/bin/gnome-keyring-daemon -d --login

All working nicely.  This morning I got:

   > set | grep SSH
   SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
   SSH_AUTH_SOCK=/tmp/keyring-y0Zso0/ssh

   > fuser $SSH_AUTH_SOCK

which means the gnome-keyring-daemon process has died.

It seems like the process dies (or is killed) when the screensaver is
unlocked in the morning rather than during the night.  (screensaver
unlock doesn't always do that though).


--
Ian

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/28


On 2009-02-18T09:05:46+00:00 Julian wrote:

I checked with gdb and got the following:
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7f68bc4f4950 (LWP 5401)]
0x0032b3432f05 in raise (sig=)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0  0x0032b3432f05 in raise (sig=)
at 

[Bug 245107] Re: virt-manager should be clearer about adding hardware to running virtual machine

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=477761.

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


On 2008-12-23T14:11:09+00:00 Martin wrote:

Originally reported on https://bugs.launchpad.net/ubuntu/+source/virt-
manager/+bug/245107

When I change the hardware configuration for a running virtual machine,
using virt-manager, it does not work. That's OK, changing hardware while
a machine is running is usually not something works on real hardware
either. The problem here is one of usability: either virt-manager should
not let me add the hardware, or it should tell me that the hardware
change will occur when the virtual machine is booted up the next time.
Right now, it gives me an error message saying that it couldn't add the
hardware, yet it is there when the virtual machine boots.

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


On 2008-12-23T15:10:07+00:00 Cole wrote:

This is fixed in virt-manager 0.6.0: if we can't hotplug the hardware,
we pop up a dialog warning the user that attach will only take effect
after next VM reboot. Closing as CURRENTRELEASE.

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


On 2008-12-23T19:15:25+00:00 Martin wrote:

Thank you, Cole, for your quick answer and telling us that this is
fixed.

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


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

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

Title:
  virt-manager should be clearer about adding hardware to running
  virtual machine

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

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

[Bug 324808] Re: [Toshiba Satellite L300] suspend/resume problem

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=476392.

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


On 2008-12-14T01:09:49+00:00 Joshua wrote:

Description of problem:
Suspend and Hibernate cause the SATA controller to hang when waking up from 
Suspend or Hibernate

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


How reproducible:100%


Steps to Reproduce:
1.Change the Power Management to Suspend or Hibernate when the lid is closed
2.close the lid
3.
  
Actual results: The disk doesn't respond during wake up, the only way to 
recover is to power cycle the machine.


Expected results:


Additional info:
=== START OF INFORMATION SECTION ===
Device Model: WDC WD3200BEVT-60ZCT0
Serial Number:WD-WXH808A30493
Firmware Version: 12.01A12
User Capacity:320,072,933,376 bytes
Device is:Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:Sat Dec 13 19:57:47 2008 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


00:00.0 Host bridge: Intel Corporation Cantiga Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Cantiga PCI Express Graphics Port (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 
(rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 
(rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 
(rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 
(rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 
(rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 
03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) 
Thermal Subsystem (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation Device 06e8 (rev a1)
02:00.0 Network controller: Intel Corporation Device 4237
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI 
Express Gigabit Ethernet controller (rev 02)
06:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. Device 2380
06:00.1 System peripheral: JMicron Technologies, Inc. Device 2382
06:00.2 SD Host controller: JMicron Technologies, Inc. Device 2381
06:00.3 System peripheral: JMicron Technologies, Inc. Device 2383
06:00.4 System peripheral: JMicron Technologies, Inc. Device 2384

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


On 2009-02-22T08:09:35+00:00 khiraly wrote:

Hi!

Looks like the Toshiba L300 model has the same problem, because it has the same 
SATA controller.
I tried with 2.6.28 kernel (from ubuntu 9.04) and with 2.6.29-rc5 kernel too.
The symptom is exactly the same. Here is the relevant bugreport filed to ubuntu:
#324808 " [Toshiba Satellite L300] suspend/resume problem "
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324808

There are some additional info, hardware details, etc.

Best regards, 
 Khiraly

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/324808/comments/20


On 2009-11-18T09:40:51+00:00 Bug wrote:


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 

[Bug 99547] Re: [apport] depmod crashed with SIGSEGV in strcmp()

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=474525.

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


On 2008-12-04T10:02:45+00:00 Zdenek wrote:

Description of problem:

during some installation of linux 2.6.28-rcx kernel I've got this
coredump:

#0  0x7f5012df3880 in strcmp () from /lib64/libc.so.6
#1  0x00405da2 in load_section64 (hdr=0x67a420, secname=0x415ab9 
"__ksymtab_strings", size=0x7fff1b303438, conv=0)
at moduleops_core.c:18
#2  0x004070bd in load_symbols64 (module=0x651940) at 
moduleops_core.c:34
#3  0x004039c9 in parse_modules (list=0x652290) at depmod.c:714


Version-Release number of selected component (if applicable):
module-init-tools-3.5-3.fc10.x86_64

How reproducible:
no idea

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/module-init-
tools/+bug/99547/comments/7


On 2009-06-09T10:06:50+00:00 Bug wrote:


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

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/module-init-
tools/+bug/99547/comments/9


On 2010-01-18T23:16:28+00:00 Jon wrote:

Was this ever reproduced?

Reply at: https://bugs.launchpad.net/ubuntu/+source/module-init-
tools/+bug/99547/comments/28


On 2010-01-19T10:20:34+00:00 Zdenek wrote:

Hmm, 2 years old bug - I'm running rawhide - thus I cannot try to
reproduce this bug anyway. It's been most probably fixed with some
package update.

As I said originally, I had no idea, how I did manage to produce such
crash.

Reply at: https://bugs.launchpad.net/ubuntu/+source/module-init-
tools/+bug/99547/comments/29


On 2010-04-27T12:27:46+00:00 Bug wrote:


This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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/module-init-
tools/+bug/99547/comments/31


On 2010-06-28T10:53:52+00:00 Bug wrote:


Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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/module-init-
tools/+bug/99547/comments/32


** Changed in: module-init-tools (Fedora)
   Status: Confirmed => Won't Fix

** Changed in: module-init-tools (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/99547

Title:
  [apport] depmod crashed with SIGSEGV in strcmp()

To manage notifications about this bug go to:

[Bug 308713] Re: vim-gnome freezing from any GTK event at Jaunty

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 28 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=463908.

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


On 2008-09-25T10:12:29+00:00 Aioanei wrote:

Description of problem:

After starting gvim, either from commandline or from the menu, gnome, or
xfce, regardless, the window becomes unresponsive and the whole desktop
becomes unresponsive also. Only issuing 'killall gvim' or 'kill -9
' from a VT gives me back my desktop.

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

How reproducible:
every time

Steps to Reproduce:
1.start gvim
2.
3.
  
Actual results:
The window and the desktop stop responding.

Expected results:
A useful gvim window

Additional info:
If it's indeed a gvim bug, since plain vim works great, from my little 
programming backround i'd say it's line 508 from src/gui.c 
[gui_create_initial_menus(root_menu)]; hope it's of any help.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/0


On 2008-09-29T10:25:11+00:00 Karsten wrote:

does gvim start with 'gvim -u NONE -U NONE' ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/1


On 2008-09-30T10:04:29+00:00 Karsten wrote:

Got requested info per mail:
It does start, but the problem persists, eg if i try to use its menus(file, 
edit, ehlp, etc), it locks up and it
locks my desktop too, and only a killall from a VT solves it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/2


On 2008-10-28T07:00:13+00:00 Joachim wrote:

Same problem here on an x86_64 system in sync with the "rawhide" tree.
After launching gvim, mouse input seems to be grabbed by gvim and only
gets released after doing a 'killall gvim' from a virtual console.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/3


On 2008-11-12T07:44:33+00:00 Joachim wrote:

Issue does not occur on an equivalent x86 system updated to F10 + updates from 
Koji. Whereas the x86_64 system from comment #3 is using an ATI Radeon X800 
video card, the x86 system is equipped with an Intel Corporation 
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device
This bug is -really- annoying ..
Any suggestions how to investigate further into this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/4


On 2008-11-13T11:38:44+00:00 Joachim wrote:

After installing FC10-Snap3 x86_64 from scratch from the live CD after
updating several packages of the live system including anaconda, and
updating the installed system to current Koji immediately after the
first boot from run level 1, gvim behaves correctly. One of the updates
(which one?) did the job, so this issue should not be one anymore for
F10 final [plus updates].

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/5


On 2008-11-13T11:39:53+00:00 Joachim wrote:

Well, I meant to write "After installing F10-PR-x86_64 from scratch ..".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/6


On 2008-11-13T11:53:53+00:00 Karsten wrote:

Have you tried to reproduce this with a newly created user ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/7


On 2008-11-13T12:30:06+00:00 Joachim wrote:

Yes, but I had done either this or removed all dot directories also during the 
last weeks after installing each F10 snapshot and preview release respectively.
But only now, the focus problem is gone ..
As pointed out in comment #4, I hadn't observed this issue on a different x86 
system with the same Koji setup.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/8


On 2008-11-13T13:42:16+00:00 Karsten wrote:

There were no changes in vim which could have fixed this, I think it is save to 
assume that something in gtk/glib2 has caused this issue.
Does everyone agree that this bugzilla can be closed ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/308713/comments/9


On 

[Bug 281044] Re: [needs-packaging] sound-theme- freedesktop 0.2

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451587.

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


On 2008-06-16T02:04:23+00:00 Lennart wrote:

Spec URL: http://0pointer.de/public/sound-theme-freedesktop.spec
SRPM URL: http://0pointer.de/public/sound-theme-freedesktop-0.1-1.fc10.src.rpm
Description: The default sound theme of the X sound theming spec

This is all kinds of sounds stolen from gnome-audio, KDE, Ekiga,
Pidgin/Purple, ALSA, put together as XDG sound theme. This goes well
along with libcanberra.

Licenses vary, the README lists them. Predominantly GPLv2.

Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/0


On 2008-06-16T02:06:28+00:00 Lennart wrote:

Assigning to Mathias, since he already reviewed libcanberra (#450975) and this
package kind of belongs to libcanberra.

Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/1


On 2008-06-16T03:09:30+00:00 Matthias wrote:

"Builds" fine in mock.rpmlint is silent.
I'll do a formal review in a bit, for now just this: you need to list all the
licenses in the license field, ideally with a comment that points to README for 
details what files each one covers.


Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/2


On 2008-06-16T13:08:54+00:00 Lennart wrote:

Licenses are fixed now. spec and srpm are at the same place.

Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/3


On 2008-06-16T13:32:41+00:00 Matthias wrote:

Formal review:

rpmlint is silent

package name: ok
spec file name: ok
packaging guidelines: ok
license: ok
license field: ok
license file: ok
spec file language: American English
spec file legibility: excellent
upstream sources: ok
buildable: yes
ExcludeArch: n/a
BuildRequires: ok
locale handling: ok
shared libs: ok
relocatable: n/a
directory ownership: ok, but I notice that /usr/share/sounds seems to be owned
by both alsa-utils and kde-filesystem. Might be worthwhile to move that to the
filesystem package, now that it is needed by yet another package. Can you
initiate that (ie file bugs) ?
duplicate filenames: ok
file permissions: ok
%clean: ok
macro use: consistent
content: permissible
large docs: n/a
%doc content: ok
headers: n/a
static libs: n/a
pc files: n/a
shared libs: n/a
devel package: n/a
libtool archives: n/a
gui apps: n/a
file ownership: ok
utf8 filenames: ok

Approved



Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/4


On 2008-06-16T13:40:01+00:00 Lennart wrote:

New Package CVS Request
===
Package Name: sound-theme-freedesktop
Short Description: The default sound theme of the XDG sound theming spec
Owners: lennart
Branches: devel
InitialCC: 
Cvsextras Commits: yes


Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/5


On 2008-06-16T16:20:29+00:00 Kevin wrote:

cvs done.

Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/6


On 2008-06-16T17:43:47+00:00 Lennart wrote:

Imported to CVS and built.

Reply at: https://bugs.launchpad.net/ubuntu/+bug/281044/comments/7


** 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/281044

Title:
  [needs-packaging] sound-theme- freedesktop 0.2

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

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

[Bug 251338] Re: Defective AMI BIOS on multiple Foxconn, MSI, and ASUS Intel LGA 775 motherboards breaks ACPI support

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=456352.

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


On 2008-07-23T02:43:57+00:00 Ryan wrote:

Description of problem:

Multiple ACPI problems and warnings on boot, PC will suspend and resume, but on
the next reboot, it hangs and requires a hard reset, Thermal Zone and Fan
control support also appear to be missing, I had to set the BIOS to take control
of the fans, or else they run at 100% at all times.

The website for this motherboard:

http://www.foxconnchannel.com/product/Motherboards/detail_overview.aspx?ID
=en-us327

I am using latest BIOS, which seems to allow CPU Frequency scaling to
function.


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

Kernel 2.6.25.10-86

Running a 2.6.26-git9 kernel appears to fix (some?) of this in that ACPI: Failed
To Attach Device messages are gone and PC suspends, resumes, and reboots, still
get checksum error relating to tbautils.

Behaviour is the same with ACPI 1, 2, or 3.

How reproducible:


Steps to Reproduce:

1. Install Foxconn G33M or G33M-S motherboard.
2. Boot Fedora
3. Try a suspend, resume reboot.
  
Actual results:

Depdning on your kernel, either resume no worky, reboot no worky, and in all
cases, ugly kernel error messages.

Expected results:

Suspend, resume, reboot all worky, kernel gives no error messages.


Additional info:

I've attached a lot of all my kernel related messages.

I've attempted to ask Foxconn about this, and they recommended I remove all of
my RAM and see if the problem continues. (OK, not as useful as funny, but still)

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


On 2008-07-23T02:43:57+00:00 Ryan wrote:

Created attachment 312410
Clip of kernel messages on boot, with shoddy Foxconn motherboard

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


On 2008-07-23T03:53:40+00:00 Ryan wrote:

Created attachment 312417
Clip from /var/log/messages with 2.6.25.11-97

System log messages with kernel 2.6.25.11-97, I installed this kernel because
it appears to be more verbose.

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


On 2008-07-27T00:06:44+00:00 Matthew wrote:

Linux correctly reports that the table has an incorrect checksum, but that
should be purely cosmetic. The only obvious remaining bug is that the machine
fails to reboot after a suspend to RAM? Does booting with

reboot=b

as a kernel command option work around this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/18


On 2008-07-27T02:58:49+00:00 Matthew wrote:

Man I suck at bugzilla. Reopening since I closed it by accident.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/20


On 2008-07-27T03:08:09+00:00 Ryan wrote:

reboot-b has no effect.

I've sent you my ACPI dump.

Foxconn is apparently working on some kind of a patch, and has stated that they
will make an official announcement over why this happened on Monday.

They've been frantically working on getting the BIOS to boot up Linux and
correctly interface with it on their test machines.

>From what I can tell an improved BIOS ROM is on the way?

I will post link to the ROM when they put it on their site so we can
close this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/21


On 2008-07-27T03:16:51+00:00 Matthew wrote:

Just to confirm, you tried

reboot=b

and not

reboot-b

, right? It needs to be passed as a kernel option from grub.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/22


On 2008-07-27T03:53:18+00:00 Ryan wrote:

yes, I put reboot=b in menu.lst, same behavior

Get an error on resume that I couldn't make out before.

Something like:

ATA 6 revalidation error.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/251338/comments/23


On 2008-07-27T07:27:58+00:00 Ryan wrote:

Just to go over what Matthew has stated on his blog, paraphrasing:

"There's no way altering the DSDT fixes any of the errors, especially not the
checksum"

It 

[Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=446631.

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


On 2008-05-15T14:05:51+00:00 Tom wrote:

Description of problem:

The traditional way to provide information which cannot be provided by
DHCP (specifically in my case additional DNS domain names in search path)
has been by writing an /etc/dhclient-exit-hooks script which can be used
to edit the /etc/resolv.conf file after it is created by DHCP. This script
is no longer being run when NetworkManager creates resolv.conf

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

NetworkManager-0.7.0-0.9.3.svn3623.fc9.x86_64

How reproducible:

Every time I boot.

Steps to Reproduce:
1. Boot system, observe NetworkManager generated resolv.conf does not
   have the changed dhclient-exit-hooks would have made.
  
Actual results:

see above

Expected results:

augmented search path in resolv.conf

Additional info:

I'd be happy to learn the "new way" to achieve the same thing
dhclient-exit-hooks did, but on the other hand, I'd really wonder
why there would need to be a "new way" other than obsessive OCD
on the part of developers. How hard is it to just run the dadgum
script if it exists?

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


On 2008-05-18T22:51:47+00:00 Todd wrote:

NetworkManager provides its own hooks into dhclient so that it can do its thing.
 You can get NetworkManager to call your script though.  NetworkManager runs all
scripts that are in /etc/NetworkManager/dispatcher.d.  There should be at least
one script in there to show you how things work. 

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


On 2008-07-10T18:51:02+00:00 Mike wrote:

Scripts in /etc/NetworkManager/dispatcher.d/ do work, but they don't fully
handle the sorts of things the dhclient-script and friends did.  It's certainly
less featureful.

For example, when dhclient does a renew, NetworkManager does not run any script
in /etc/NetworkManager/dispatcher.d/.  Those only seem to be run when
NetworkManager changes state on a device using either "up" or "down". 
NetworkManager's actions after the renew causes some other services to have to
rediscover the interface:

Jul 10 01:48:22 laptop dhclient: DHCPREQUEST on wlan0 to 192.168.1.1 port 67
Jul 10 01:48:22 laptop dhclient: DHCPACK from 192.168.1.1
Jul 10 01:48:22 laptop dhclient: bound to 192.168.1.6 -- renewal in 42559 
seconds.
Jul 10 01:48:22 laptop NetworkManager:   DHCP: device wlan0 state changed
bound -> renew
Jul 10 01:48:22 laptop NetworkManager: address 192.168.1.6
Jul 10 01:48:22 laptop NetworkManager: netmask 255.255.255.0
Jul 10 01:48:22 laptop NetworkManager: gateway 192.168.1.1
Jul 10 01:48:22 laptop NetworkManager: nameserver '127.0.0.1'
Jul 10 01:48:22 laptop avahi-daemon[2579]: Withdrawing address record for
192.168.1.6 on wlan0.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Leaving mDNS multicast group on
interface wlan0.IPv4 with address 192.168.1.6.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Interface wlan0.IPv4 no longer
relevant for mDNS.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Joining mDNS multicast group on
interface wlan0.IPv4 with address 192.168.1.6.
Jul 10 01:48:22 laptop avahi-daemon[2579]: New relevant interface wlan0.IPv4 for
mDNS.
Jul 10 01:48:22 laptop avahi-daemon[2579]: Registering new address record for
192.168.1.6 on wlan0.IPv4.
Jul 10 01:48:23 laptop NetworkManager:   Policy set (wlan0) as default
device for routing and DNS.

I run openvpn as a service, outside of NetworkManager.  Using the normal
dhclient-script hooks, I can detect this action and restart the openvpn service
when it happens.  The /usr/libexec/nm-dhcp-client.action script NetworkManager
runs from dhclient doesn't appear to be able to handle the same idea of hooks. 
Without a cronjob watching things, or modifying NetworkManager's init script to
use the normal dhclient-script, I have to manually restart openvpn everytime
DHCP renews.  It tends to be less than transparent.

Should this replacement for dhclient-script read and handle the same hooks files
that dhclient-script itself uses, or should NetworkManager itself not make
changes to an interface like this when a simple renew happens?  Ideally,
functionality replaced should not be a reduction.  I'd like to see the hooks 
work.

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


[Bug 343749] Re: LSI SAS 1078 not detected when installing

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=541615.

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


On 2009-11-26T14:01:47+00:00 Luc wrote:

Description of problem:
When doing "intensive" I/O, the mpt* drivers crashes the filesystem, on Fedora 
12.

The problem is on an IBM x3580 M2 machine, using the integrated LSI
SAS1078 C1 PCI-express Fusion-MPT SAS.

Steps to Reproduce:
1. Create a big allocated space (20GB for example)
2. dd if=/dev/vg/mybigspace of=/dev/null
3. After a few minutes, the filesystem access becomes impossible. Looking at 
dmesg, you get the following:

Calgary: DMA error on CalIOC2 PHB 0x3
Calgary: 0x8000@CSR 0x@PLSSR 0xb0008000@CSMR 0x@MCK
Calgary: 0x@0x810 0x@0x820 0x@0x830 0x@0x840 
0x@0x850 0x@0x860 0x@0x870 
Calgary: 0x4000@0xcb0
irq 46: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Not tainted 2.6.31.5-127.fc12.x86_64 #1
Call Trace:
   [] __report_bad_irq+0x3d/0x8c
 [] note_interrupt+0x118/0x17d
 [] handle_fasteoi_irq+0xa1/0xc6
 [] handle_irq+0x8b/0x93
 [] do_IRQ+0x5c/0xbc
 [] ret_from_intr+0x0/0x11
   [] ? mwait_idle+0x91/0xae
 [] ? mwait_idle+0x91/0xae
 [] ? mwait_idle+0x33/0xae
 [] ? atomic_notifier_call_chain+0x13/0x15
 [] ? enter_idle+0x25/0x27
 [] ? cpu_idle+0xa6/0xe9
 [] ? start_secondary+0x1f3/0x234
handlers:
[] (mpt_interrupt+0x0/0x8bb [mptbase])
Disabling IRQ #46
mptscsih: ioc0: attempting task abort! (sc=880a0d8fa400)
sd 2:1:4:0: [sda] CDB: Write(10): 2a 00 00 fb 5b a7 00 00 60 00
mptscsih: ioc0: WARNING - TaskMgmt type=1: IOC Not operational (0x)!
mptscsih: ioc0: WARNING - Issuing HardReset from mptscsih_IssueTaskMgmt!!
mptbase: ioc0: Initiating recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: WARNING - NOT READY WARNING!
mptbase: WARNING - (-1) Cannot recover ioc0
mptscsih: ioc0: WARNING - TaskMgmt HardReset FAILED!!
mptscsih: ioc0: task abort: FAILED (sc=880a0d8fa400)
mptscsih: ioc0: attempting task abort! (sc=880a04bb3100)
sd 2:1:4:0: [sda] CDB: Write(10): 2a 00 00 28 f5 ff 00 00 08 00
mptscsih: ioc0: WARNING - TaskMgmt type=1: IOC Not operational (0x)!
mptscsih: ioc0: WARNING - Issuing HardReset from mptscsih_IssueTaskMgmt!!
mptbase: ioc0: Initiating recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: WARNING - NOT READY WARNING!
mptbase: WARNING - (-1) Cannot recover ioc0
mptscsih: ioc0: WARNING - TaskMgmt HardReset FAILED!!
mptscsih: ioc0: task abort: FAILED (sc=880a04bb3100)
mptscsih: ioc0: attempting task abort! (sc=880a04bb2600)
sd 2:1:4:0: [sda] CDB: Write(10): 2a 00 00 61 de 27 00 00 08 00
mptscsih: ioc0: WARNING - TaskMgmt type=1: IOC Not operational (0x)!
mptscsih: ioc0: WARNING - Issuing HardReset from mptscsih_IssueTaskMgmt!!
mptbase: ioc0: Initiating recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
[root@flanders ubuntu]# 
Message from syslogd@mymachine at Nov 26 10:38:28 ...
 kernel:mpage_da_map_blocks block allocation failed for inode 11762 at logical 
offset 2 with max blocks 1 with error -30

Message from syslogd@mymachine at Nov 26 10:38:28 ...
 kernel:This should not happen.!! Data will be lost


The first error message ("Calgary: DMA error on CalIOC2 PHB 0x3") seems to be 
related to a bug in the Calgary code, as detailed in a thread in LKML:
"The calgary code can give drivers addresses above 4GB which is very bad for 
hardware that is only 32bit DMA addressable" 
(http://www.archivum.info/linux-ker...@vger.kernel.org/2008-06/05248/Re:_%5BPATCH_-mm%5D_x86_calgary:_fix_handling_of_devces_that_aren%27t_behind_the_Calgary
 ).
But it's from 2008, I thought this would have been corrected...

After looking on another bug report
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343749 ), the
temporary solution seems to be to set iommu=soft at boot. But I guess
this affects performance... Acccording to that bug report, the bug seems
to be corrected on RH 9 ?!


The bug exists in Fedora 12, and makes it unusable on a x3580 M2.

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


On 2009-12-29T00:03:03+00:00 David wrote:

I also had a SERIOUS problem installing Fedora 12 on a Dell Optiplex
GX620 which *appears* to be the same thing.

I tried to install Fedora 12 on a Dell Optiplex GX620 as a 64-bit OS (x86_64), 
using BIOS revision A10.  When the disk was busy installing things it suddenly 
hung with this message:
 kernel: mpage_da_map_blocks block allocation failed for inode 211 at logical 
offset 0 with max blocks 1 with error -30
 

[Bug 410407] Re: Buttons don't respond to mouse clicks

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=542424.

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


On 2009-11-29T19:24:18+00:00 Hicham wrote:

Description of problem:
With compiz enabled flash objects become unresponsive.

Version-Release number of selected component (if applicable):
nspluginwrapper-1.3.0-8.fc12.i686

How reproducible:
always

Steps to Reproduce:
1.Enable compiz on F12
2.Open a webpage with flash objects
3.Try to click on them
  
Actual results:
no response to mouse clicks

Expected results:
response to mouse clicks

Additional info:
a temporary workaround would be to add the line
export GDK_NATIVE_WINDOWS=1 
to npviewer.sh

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/196


On 2009-12-01T05:02:40+00:00 Walter wrote:

Is this directly related to Adobe Reader not functioning?  At work we've
also discovered that Lotus Notes 8.5 has a "grey screen" which
unfortunately the GDK_NATIVE_WINDOWS workaround does not help with (it
doesn't make it to eclipse for whatever reason when executing the main
notes bin with the workaround env set, which is the GUI with the
problem) and the only workaround so far is to LD_PRELOAD 2.16 GTK libs.

Is a fix at the GTK level in the works, or is there a GTK bug at all?
I'm sure more of these things will be found, hopefully most of them
easily fixed with the GDK_NATIVE_WINDOWS workaround.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/198


On 2009-12-01T12:50:02+00:00 Hicham wrote:

No, it is not, and it is not Fedora specific, it is introduced by gtk
2.18. Official Adobe Flash are suffering from this bug, I don't know
about gnash. I think of it as a third party issue, since current Adobe
Flash Plugin have been released before gtk-2.18.

I was confused about where to file the bug, but since we can have a
temporary fix in Fedora, i preferred filing the bug here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/199


On 2009-12-04T13:15:55+00:00 Ben wrote:

A work around is described here:

http://forums.fedoraforum.org/showthread.php?t=233489

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/202


On 2009-12-04T13:22:48+00:00 Walter wrote:

Already documented in the F12 Common Bugs..
https://fedoraproject.org/wiki/Common_F12_bugs#Non_Responsive_Flash_Objects

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/203


On 2009-12-04T15:22:28+00:00 Martin wrote:

Added to nspluginwrapper-1.3.0-10.fc12

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/204


On 2009-12-04T15:34:03+00:00 Fedora wrote:

nspluginwrapper-1.3.0-10.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/nspluginwrapper-1.3.0-10.fc12

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/205


On 2009-12-04T18:02:34+00:00 Hicham wrote:

Thanks Martin for the fix ! can we close this bug report now ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/206


On 2009-12-07T07:32:29+00:00 Fedora wrote:

nspluginwrapper-1.3.0-10.fc12 has been pushed to the Fedora 12 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/207


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

** Changed in: nspluginwrapper (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/410407

Title:
  Buttons don't respond to mouse clicks

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/410407/+subscriptions

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

[Bug 368679] Re: wifi module rtl8180 freezes the system

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 16 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=501109.

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


On 2009-05-16T14:11:17+00:00 Olivier wrote:

Created attachment 344269
sosreport of the system

Description of problem:

Ther system experiences hard hang when using WIFI with the rtl8180
kernel module. The system ends in such a state that sysrq is inefficient
(sysrq-t, sysrq-m, sysrq-c do nothing) and quite often require a
complete electrical unplug for several seconds to be able to reboot.

Console logs or /var/log/message show no oops or kernel backtrace.

Blacklisting the module rtl8180 or removing the Belkin WIFI G PCI card
cures the problem but does not help with WIFI connectivity ^_~

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

kernel-PAE-2.6.29.3-140.fc11.i686 (But occurs on older kernel as well,
including F10)

How reproducible:

100% reproducible

Steps to Reproduce:

1. Install the Belkin Wireless G dektop PCI card Based on the Realtek 818x
2. Boot the system
  
Actual results:

System will hang either at login or at logout

Expected results:

System remains stable and functional

Additional info:

The WIFI connection uses hidden ESSID and WPA/WPA2 security. The problem
occurs either when NetworkManager connects to the network or when it
terminates (logging out from the user session leads to a 100% hang).

Same happens if NetworkManager exits or needs to reconnect. The same
hardware works perfectly under Windows with Belkin's provided driver
though.

I am attaching the sosreport of the system, unfortunately I am unable to
debug this issue much further and I could not come up with a usable
workaround for the issue.

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


On 2009-06-09T15:55:39+00:00 Bug wrote:


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

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

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


On 2009-12-29T21:50:55+00:00 Skippy wrote:

I can confirm this bug for Fedora 12 with the following wifi card :
Zyxel G-302 v3.

For some other reason I cannot achieve a proper install right now so I
can confirm only with the live CD, but symptoms are exactly the same as
above : boot ok, user session ok, if I click on the NetworkManager icon
I can select the network, then connect to it, enter my WEP key, and then
the system will freeze (while asking for the keyring password,
secondarily). If I don't try to connect, everything works fine but the
system won't shutdown (didn't try to logout).

Similar issues happen with Ubuntu, cf
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/11


On 2010-03-16T18:14:38+00:00 Sylvain wrote:

I too confirm this kernel hang with a TRENDdet TEW-423PI (C1.0R) on a up to 
date Fedora 12 the only message when manually activating the connection was 
some "invalid parameter" message when using the GUI 
Otherwise when on startup or command line nothing is showing but only the 
endless hang

BTW this is a blocker on the rescue mode if the interface is checked on as 
managed by the NetworkManager
My workaround has been to let this card disabled :( 
obviously that was not my goal

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/18


On 2010-04-27T14:21:20+00:00 Bug wrote:


This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 

[Bug 472057] Re: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

2017-10-26 Thread Bug Watch Updater
** Changed in: fedora
   Status: Unknown => Won't Fix

** 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/472057

Title:
  NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

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

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

[Bug 543183] Re: Updating system certificates requires rebuild

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 43 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=546221.

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


On 2009-12-10T13:37:00+00:00 David wrote:

There is a system-wide NSS db in /etc/pki/nssdb. I have added my
company's internal CA certificates there.

However, firefox still doesn't trust our internal web sites. It doesn't
seem to be using the system database.

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


On 2009-12-10T13:59:20+00:00 Martin wrote:

I don't believe it's a firefox bug...

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


On 2009-12-12T09:57:57+00:00 David wrote:

I tried installing the nss-sysinit package and installing certs with
'certutil -d /etc/pki/nssdb'. But it doesn't seem to make any difference
-- neither Evolution nor Firefox seem to know anything about these
certificates.

/proc/$PID/maps seems to suggest that they don't have
/usr/lib64/libnsssysinit.so mapped.

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


On 2009-12-13T14:18:11+00:00 David wrote:

Test procedure... First we fetch a signing cert (just an example; it doesn't 
matter which it is), import it into a new application-specific NSS DB, and it 
works. We remove it from the app's DB, and it doesn't. 
All is well so far...

[root@macbook dwmw2]# curl -k https://www.cacert.org/certs/root.crt > cacert.crt
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
102  2569  102  25690 0  10740  0 --:--:-- --:--:-- --:--:-- 51380
[root@macbook dwmw2]# mkdir /tmp/nssdb
[root@macbook dwmw2]# certutil -d /tmp/nssdb -t TC,TC,TC -E -i cacert.crt -n 
cacert
[root@macbook dwmw2]# /usr/lib64/nss/unsupported-tools/tstclnt -d /tmp/nssdb -h 
www.cacert.org -p 443
subject DN: E=supp...@cacert.org,CN=www.cacert.org,O=CAcert 
Inc.,L=Sydney,ST=NSW,C=AU
issuer  DN: E=supp...@cacert.org,CN=CA Cert Signing 
Authority,OU=http://www.cacert.org,O=Root CA
0 cache hits; 1 cache misses, 0 cache not reusable
0 stateless resumes
^C
[root@macbook dwmw2]# certutil -d /tmp/nssdb -D -n cacert
[root@macbook dwmw2]# /usr/lib64/nss/unsupported-tools/tstclnt -d /tmp/nssdb -h 
www.cacert.org -p 443
tstclnt: read from socket failed: Peer's Certificate issuer is not recognized.

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


On 2009-12-13T14:26:31+00:00 David wrote:

And this shows the failure... this one ought to _work_, surely?

[root@macbook dwmw2]# setup-nsssysinit.sh on
[root@macbook dwmw2]# certutil -d /etc/pki/nssdb -t TC,TC,TC -E -i cacert.crt 
-n cacert
[root@macbook dwmw2]# /usr/lib64/nss/unsupported-tools/tstclnt -d /tmp/nssdb -h 
www.cacert.org -p 443
tstclnt: read from socket failed: Peer's Certificate issuer is not recognized.

The issuer _should_ be recognised -- I just added it to the system database!
It's not just tstclnt that fails; evolution and firefox fail too.

curl does work, but I think that's because it actually uses
/etc/pki/nssdb as its "application" database.

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


On 2009-12-13T14:30:31+00:00 Kamil wrote:

The behavior looks slightly similar to bug 545779. Could you please try
the patch from there (including the change from comm. #20)?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/543183/comments/6


On 2009-12-13T14:55:50+00:00 David wrote:

You mean just the patch to nsssysinit.c in comm. #18, with the extra one-liner?
I built that and installed the resulting libnsssysinit.so library. But when I 
run 'tstclnt' as described, the atime on the library doesn't change -- it isn't 
even being loaded. The atime on /etc/pki/nssdb/pkcs11.txt doesn't change either.

Are you able to reproduce the problem using the commands given above? It
should be fairly simple.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/543183/comments/7


On 2009-12-13T16:32:41+00:00 David wrote:

I've been playing with this, and reading the documentation at

[Bug 461303] Re: generates-bad-code regression

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=544358.

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


On 2009-12-04T17:34:33+00:00 nucleo wrote:

Description of problem:
cryptest from cryptopp hangs up when built for fc13.
cryptest is running in %check section of cryptopp.spec, so cryptopp can't be 
built for fc13.
For fc12 cryptopp builds fine.


Version-Release number of selected component (if applicable):
binutils 2.20.51.0.2-8.fc13


See the same issues here:

http://sourceware.org/bugzilla/show_bug.cgi?id=10856

https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/32


On 2009-12-09T12:09:27+00:00 Nick wrote:

Hi Alec,

  I have imported Alan Modra's patch for PR 10856 into the devel
binutils rpm.  Please try using the latest release (2.20.51.0.2-9), and
if you still have problems, let us know.

Cheers
  Nick

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/33


On 2009-12-09T15:06:21+00:00 nucleo wrote:

Hi Nick,

With binutils 2.20.51.0.2-9.fc13 cryptopp test not fails.

Finally cryptopp-5.6.1-0.1.svn479.fc13 built:
http://koji.fedoraproject.org/koji/buildinfo?buildID=143094

Should I close this bug?

Alexey

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/34


On 2009-12-13T21:03:18+00:00 Zooko wrote:

This page on launchpad is tracking the progress of this issue through
several different operating systems and open source projects that are
affected by this bug.  I added a link to this ticket on
bugzilla.redhat.com:

https://bugs.launchpad.net/fedora/+source/binutils/+bug/461303

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/37


On 2010-04-21T16:53:22+00:00 Michal wrote:

Notes: Changing version to 13 from 12, since wrt comment 0 it is clear
that F-13 had that issue not F-12. Closing, we have update.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/39


On 2012-01-11T19:58:39+00:00 Zooko wrote:

If anybody reading this has the authority to change the status of
tickets in launchpad, please mark this as fixed there:
https://bugs.launchpad.net/fedora/+source/binutils/+bug/461303 . Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/45


** Changed in: binutils (Fedora)
   Status: In Progress => Fix Released

** Changed in: binutils (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/461303

Title:
  generates-bad-code regression

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

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

[Bug 460205] Re: 'GwibberClient' object has no attribute 'tabs'

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 23 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=539643.

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


On 2009-11-20T18:56:55+00:00 Filipe wrote:

abrt detected a crash.

Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gwibber 
component: gwibber
executable: /usr/bin/gwibber
kernel: 2.6.31.6-134.fc12.x86_64
package: gwibber-1:2.0.0-1.478bzr.fc12
uuid: c3c0aa03

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/5


On 2009-11-20T18:57:14+00:00 Filipe wrote:

Created attachment 372578
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/6


On 2009-11-21T01:24:00+00:00 Ian wrote:

Can you explain what you were doing when the crash occurred?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/7


On 2009-11-21T01:47:07+00:00 Filipe wrote:

Steps to reproduce:

1. Open gwibber (configured with one twitter account)
2. Gwibber Menu -> Clear Stream (Ctrl + L)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/9


On 2009-11-27T16:22:26+00:00 Ian wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/10


On 2010-01-23T06:08:26+00:00 Dagan wrote:

 I got this same error when also trying to 'Clear Stream'.

I have been getting a lot of errors trying to receive messages from
Twitter. I was trying to work out how to clear the errors list.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/11


On 2010-02-24T05:10:51+00:00 Filipe wrote:

I believe that this bug is solved on gwibber-1.2.0-3.349bzr.fc12.noarch
Please test more and closed this bug when done.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/13


On 2010-02-24T05:26:15+00:00 Dagan wrote:

I am using gwibber-2.0.0-2.478bzr.fc12.noarch from updates-testing, and
I still occassionally get this. But I am happy to close, and log against
specific version if this is fixed in 1.2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/14


On 2010-03-23T13:09:39+00:00 Fedora wrote:

gwibber-2.29.92.1-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gwibber-2.29.92.1-1.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/15


On 2010-03-23T13:24:46+00:00 Tom wrote:

I have just pushed a test update for gwibber-2.29.92.1.

While I would not normally perform a major update to gwibber for
released distributions, this update is important for the following
reasons:

* Gwibber 1.2.0 and 2.0.0 crash. A lot. Most of the reasons for these
crashes are exposed feature functionality which was never implemented
completely. These features are generally implemented properly in the
2.29.92.1 code, and so far, it has yet to crash on me in extensive
testing.

* Upstream is not maintaining the 1.2 or 2.0 branches at all, so any
work done in those spaces is wasteful.

I need your help to test this package, but first, you need to upgrade to
it! There are two ways you can do this:

1. You can wait for it to go into updates-testing (this will happen in
the next day or so), and then run: yum update --enablerepo=updates-
testing gwibber

2. You can run these two commands:
koji download-build --arch=noarch gwibber-2.29.92.1-1.fc12
yum update gwibber-2.29.92.1-1.fc12.noarch.rpm --nogpgcheck

*
Once you have the new gwibber installed, you should be able to immediately 
start using it, as it will migrate your old settings. Test it out, make sure it 
works, and if it looks like it resolves your issues, please, go to:

https://admin.fedoraproject.org/updates/gwibber-2.29.92.1-1.fc12

Once there, leave a comment and give a +1. If it doesn't work well for
you, please leave a comment and give a -1.

Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/460205/comments/16


[Bug 449401] Re: nm 0.8 lacks feature to unlock SIM by PUK

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=542319.

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


On 2009-11-29T09:51:33+00:00 Didier wrote:

Description of problem:

NetworkMananger configuration screen for large band connections does not
longer display field to specify PUK code for 3G modem

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

NetworkManager-0.7.996-7.git20091113.fc12.rpm

How reproducible:

n/a

Steps to Reproduce:
1. n/a
2.
3.
  
Actual results:

NetworkMananger does not longer display field to specify PUK code for 3G
modem

Expected results:

NetworkManager should dispaly field to specify PUK code for 3G modem
when configuring large band connection

Additional info:

Log of a case where PUK is needed :

Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) starting 
connection 'SFR Par défaut 1'
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 3 -> 4 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) scheduled...
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) started...
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 4 -> 6 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) complete.
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) scheduled...
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) started...
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 6 -> 4 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) Stage 1 
of 5 (Device Prepare) complete.
Nov 29 01:31:36 localhost modem-manager: (ttyUSB0) opening serial device...
Nov 29 01:31:36 localhost NetworkManager:   stage1_prepare_done(): GSM 
modem connection failed: SIM PUK required
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 4 -> 9 (reason 1)
Nov 29 01:31:36 localhost NetworkManager:   Marking connection 'SFR Par 
défaut 1' invalid.
Nov 29 01:31:36 localhost NetworkManager:   Activation (ttyUSB0) failed.
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): device state 
change: 9 -> 3 (reason 0)
Nov 29 01:31:36 localhost NetworkManager:   (ttyUSB0): deactivating 
device (reason: 0).
Nov 29 01:31:36 localhost NetworkManager: flush_routes: assertion `iface_idx >= 
0' failed
Nov 29 01:31:36 localhost NetworkManager: flush_addresses: assertion `iface_idx 
>= 0' failed
Nov 29 01:31:36 localhost modem-manager: (ttyUSB0) closing serial device...

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


On 2009-12-21T11:46:15+00:00 Didier wrote:

My previous entry above is incomplete.

When I get message

<< NetworkManager:   stage1_prepare_done(): GSM modem connection
failed: SIM PUK required >>

the only solution with current version of NetworkManager is to boot on
Windows or to remove SIM from USB stick and insert it in mobile phone to
unlock it with the PUK code.

With previous versions of NetworkManager who accepted PUK code during
configuration, behavior was different and NetworkManager was able to
unlock the SIM so current behavior is a regression.

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


On 2010-01-23T15:30:00+00:00 Johan wrote:

I just updated to Fedora-rawhide my kernel, ModemManager, NetworManager... but 
have the same problem.
I found another solution to unlock the sim, using wvdial to send:
AT+CPIN="puk","pin"

One thing to try may be to use the PIN field of the NetworkManager to send
puk,pin and not just the pin.

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


On 2010-06-26T00:19:35+00:00 Dan wrote:

Recent versions of NM & ModemManager from updates will request the PUK
when the card is plugged in, if the card is locked enough to require the
PUK.

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


** Changed in: network-manager (Fedora)
   Status: Confirmed => 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/449401

Title:
  nm 0.8 lacks 

[Bug 487314] Re: Toner levels make the Printer Properties dialog too wide for my screen

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=540826.

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


On 2009-11-24T09:56:22+00:00 Tim wrote:

Description of problem:
When there are many marker levels and their names are long the properties 
dialog becomes too wide.  See the linked Ubuntu bug report for a screenshot.

The marker-names labels should be word-wrapped, and perhaps we need a
smarter way of sizing the ink drops table.  Perhaps the ink drops table
could be put inside a scrolled viewport?

Version-Release number of selected component (if applicable):
system-config-printer-1.1.13-10.fc12.x86_64

How reproducible:
Should be easy

Steps to Reproduce:
1.Create a backend shell script to write out 'ATTR:' lines to stderr to set the 
marker-* attributes as shown in the screenshot, and end it like:

if [ -z "$6" ]; then cat >/dev/null; fi

2.Create a queue using that backend and send a job to it.
3.Run system-config-printer and view the ink levels tab in the properties 
dialog.
  
Actual results:
Dialog is too wide and cannot be resized smaller.

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


On 2009-11-24T09:58:24+00:00 Tim wrote:

(Release set to 11 but both F-11 and F-12 are affected.)

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


On 2009-11-26T16:00:35+00:00 Tim wrote:

Created attachment 374032
test backend

For reference, here is the backend shell script I used to reproduce this
problem.

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


On 2009-12-02T04:45:18+00:00 Fedora wrote:

system-config-printer-1.1.15-1.fc11 has been pushed to the Fedora 11 testing 
repository.  If problems still persist, please make note of it in this bug 
report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update system-config-printer'.  You 
can provide feedback for this update here: 
http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10893

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


On 2009-12-04T23:54:17+00:00 Fedora wrote:

system-config-printer-1.1.15-3.fc11 has been pushed to the Fedora 11 testing 
repository.  If problems still persist, please make note of it in this bug 
report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update system-config-printer'.  You 
can provide feedback for this update here: 
http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10893

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


On 2009-12-10T04:07:40+00:00 Fedora wrote:

system-config-printer-1.1.15-6.fc11 has been pushed to the Fedora 11
stable repository.  If problems still persist, please make note of it in
this bug report.

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


** Changed in: system-config-printer
   Status: Unknown => Fix Released

** Changed in: system-config-printer
   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/487314

Title:
  Toner levels make the Printer Properties dialog too wide for my screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/487314/+subscriptions

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

[Bug 493766] Re: Multi_key / compose does not work when XMODIFIERS="@im=SCIM"

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 24 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=479336.

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


On 2009-01-08T22:36:43+00:00 Johan wrote:

Description of problem:

When a "Compose Key" is configured (using xmodmap or System >
Preferences > Hardware > Keyboard > Layouts > Layout options > Compose
key position) all X applications use it. However, Emacs doesn't. When
the compose key is pressed, Emacs complains: " is undefined".

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

emacs-22.2-5.fc9.i386.rpm (from F10 release)
emacs-22.3-1.fc10.i386 (from F10 updates-testing)

How reproducible:

Always.

Steps to Reproduce:

1. Start a Gnome session
2. Configure Right Control as Compose Key using System > Preferences > Hardware 
> Keyboard > Layouts > Layout options > Compose key position
3. From a command line, start "emacs -q"
4. Open a new, empty buffer.
5. Press the right control key, followed by keys [e] and ['].
 
Actual results:

Emacs will complain: " is undefined". The characters "e" and
"'" will appear in the buffer.

Expected results:

No complaints, and the character "é" (e with acute accent) in the
buffer.

Additional info:

This bug makes it impossible to enter texts that are beyond ASCII.
Therefore this bug is actually a show stopper.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/493766/comments/0


On 2009-01-11T22:00:17+00:00 Johan wrote:

Some additional information (that I hope could be useful).

I have a Fedora 8 system running Emacs 21.4.1 and a Fedora 10 system
with Emacs 22.x (see previous message).

On the F10 system, Emacs 22 complains about the multi_key.
When run on the F10 system with display to the F8 system, it behaves normally 
(multi_key compose works).

On the F8 system, Emacs 21 behaves normally.
When run on the F8 system with display to the F10 system, it behaves normally.

Java application jEdit shows similar behaviour.

F10 has java version "1.6.0_0"
IcedTea6 1.4 (fedora-7.b12.fc10-i386) Runtime Environment (build 1.6.0_0-b12)
OpenJDK Server VM (build 10.0-b19, mixed mode)

F8 has java version "1.6.0_04"
Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
Java HotSpot(TM) Server VM (build 10.0-b19, mixed mode)

Both systems are running jEdit-4.3pre15.

On the F10 system, jEdit ignores the multi_key.
When run on the F10 system with display to the F8 system, it behaves normally 
(multi_key compose works).

On the F8 system, jEdit behaves normally.
When run on the F8 system with display to the F10 system, it behaves normally.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/493766/comments/1


On 2009-01-22T13:25:37+00:00 Daniel wrote:

because both jEdit and Emacs share the same bug and when you use F8
version of xorg, the problem disappears, can there be perhaps something
wrong with X configuration on F10? reassigning to xorg (feel free to
reassign back to me, if there's nothing wrong on X side)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/493766/comments/2


On 2009-01-22T17:28:09+00:00 Johan wrote:

I can reproduce the problem when booted from the F10 Live CD. I'm not
saying that this eliminates the possibility that the problem is related
to X settings, but it does eliminate *my* particular X settings.

Steps:
- boot from Live CD
- login
- open terminal window
- $ su -
- # yum install emacs
- # ^D
- $ emacs

Try e.g., right-control. Nothing happens.

System -> Preferences > Hardware > Keyboard > Layouts
Layout Options > Compose Key Position
Select Right Control as Compose
Close

Back to Emacs. Press right-control. Emacs complains " is not
defined".

Other applications (e.g. the terminal window) treat control-right now as
a compose key.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/493766/comments/3


On 2009-01-23T10:19:42+00:00 Daniel wrote:

(In reply to comment #3)

> but it does eliminate *my* particular X settings.
that's exactly what I thought: because two distinct applications (jEdit and 
emacs) present the same buggy behavior, there might be something rotten in the 
default X config in F10 - I reassigned the bug to xorg component, so they can 
see if there's something wrong

Reply at:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/493766/comments/4


On 2009-01-23T16:46:06+00:00 Matěj wrote:

Thanks for the bug 

[Bug 658198] Re: Fn key control of backlight broken after upgrade to 10.10

2017-10-26 Thread Bug Watch Updater
** Changed in: linux (Fedora)
   Status: Unknown => Won't Fix

** Changed in: linux (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/658198

Title:
  Fn key control of backlight broken after upgrade to 10.10

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

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

[Bug 568164] Re: iptraf stop showes eth0/eth1 interface

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=539740.

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


On 2009-11-20T22:36:47+00:00 Guillermo wrote:

Description of problem:

iptraf does not list the ethernet nic (eth0 in my case).

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


How reproducible:

Always

Steps to Reproduce:
1. su -
2. iptraf
3. ip traffic monitor

  
Actual results:

Lists 
 All interfaces
 lo

Expected results:
 All interfaces
 eth0
 lo


Additional info:

Just discovered that it does not list my wifi nic either.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/0


On 2009-12-10T10:33:48+00:00 Nikola wrote:

strange I cannot reproduce it.

ip traffic monitor does not exist

try ifconfig eth0 up and than run again iptraf

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/1


On 2009-12-10T14:03:15+00:00 Guillermo wrote:

same results, the nic is up and configured. it also happens with wlan0.

ip traffic monitor i mean > run iptraf, select ip traffic monitor (m),
select interface (list appears, does not show eth0 nor wlan0)

[root@movix ~]# uname -r
2.6.31.6-145.fc12.x86_64
[root@movix ~]# rpm -q iptraf
iptraf-3.0.1-8.fc12.x86_64
[root@movix ~]# ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:1B:38:72:A6:06  
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  Interrupt:18 

noticed its just a listing problem, when packets goes through the
interface, iptraf shows the name of the interface correctly (eth0,
wlan0).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/2


On 2009-12-10T16:00:25+00:00 Nikola wrote:

I cannot reproduce even on x86_64. I have only newer kernel.

[root@nec-em18 ~]# uname -r
2.6.31.6-162.fc12.x86_64
[root@nec-em18 ~]# rpm -q iptraf
iptraf-3.0.1-8.fc12.x86_64
[root@nec-em18 ~]# ifconfig | egrep "eth|lo"
eth0  Link encap:Ethernet  HWadr 00:16:17:55:47:C0  
eth1  Link encap:Ethernet  HWadr 00:16:17:55:47:C1  
eth2  Link encap:Ethernet  HWadr 00:04:23:C0:07:DE  
lo   Link encap:loop back

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/3


On 2009-12-10T17:44:23+00:00 Guillermo wrote:

Created attachment 377538
iptraf not listing wlan0, nor eth0

Just to make it graphic.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/4


On 2009-12-14T10:28:01+00:00 Nikola wrote:

update your kernel. This should help. I have same issue with
2.6.31.5-127.fc12.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/5


On 2009-12-15T15:14:27+00:00 Guillermo wrote:

(In reply to comment #5)
> update your kernel. This should help. I have same issue with
> 2.6.31.5-127.fc12.x86_64  

Still, with

# uname -r
2.6.31.6-166.fc12.x86_64

same results :(

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/6


On 2010-01-06T10:56:10+00:00 Nikola wrote:

send me your ifconfig -a

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/568164/comments/7


On 2010-01-06T20:35:20+00:00 Guillermo wrote:

g# ifconfig -a
eth0  Link encap:Ethernet  HWaddr 00:1B:38:72:A6:06  
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  Interrupt:18 

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:23 errors:0 dropped:0 overruns:0 frame:0
  TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:1867 (1.8 KiB)  TX bytes:1867 (1.8 KiB)


[Bug 651876] Re: Gnome Planner hangs (planner:4303): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' failed

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=537854.

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


On 2009-11-16T15:21:32+00:00 Pierre-YvesChibon wrote:

Description of problem:
When I click on the 'Zoom to fit' button on my project on plannet it seems to 
go into an infinite loop

Version-Release number of selected component (if applicable):
planner-0.14.4-3.fc12.x86_64

How reproducible:
In my project always

Steps to Reproduce:
1. Open planner
2. Open a project
3. Click on 'Zoom to fit'
  
Actual results:
Unresponsive planner + large output on the console

Expected results:
Zoom to fit

Additional info:
In the console I see:
** (planner:8862): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' 
failed
** (planner:8862): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' 
failed
** (planner:8862): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' 
failed
** (planner:8862): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' 
failed

--help does not show if there is a debug mode

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/0


On 2009-11-16T15:36:43+00:00 Caolan wrote:

known upstream, but unfixed

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/1


On 2009-11-17T10:50:39+00:00 Caolan wrote:

Submitted a fix upstream and checked in in, will be in >= 0.14.4-4

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/2


On 2009-11-17T11:00:18+00:00 Pierre-YvesChibon wrote:

If you have a build on koji I can test it :-)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/3


On 2009-11-17T11:04:34+00:00 Fedora wrote:

planner-0.14.4-4.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/planner-0.14.4-4.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/4


On 2009-11-18T14:07:51+00:00 Fedora wrote:

planner-0.14.4-4.fc12 has been pushed to the Fedora 12 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update planner'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/F12/FEDORA-2009-11648

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/5


On 2009-11-23T12:27:49+00:00 Fedora wrote:

planner-0.14.4-5.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/planner-0.14.4-5.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/6


On 2009-11-25T15:16:59+00:00 Fedora wrote:

planner-0.14.4-5.fc12 has been pushed to the Fedora 12 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/planner/+bug/651876/comments/7


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

** Changed in: planner (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/651876

Title:
  Gnome Planner hangs (planner:4303): CRITICAL **:
  mrp_time2_add_seconds: assertion `secs >= 0' failed

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

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

[Bug 552681] Re: Mouse cursor trapped with right-click in menu, lose input control

2017-10-26 Thread Bug Watch Updater
** Changed in: grace (Fedora)
   Status: Unknown => Fix Released

** Changed in: grace (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/552681

Title:
  Mouse cursor trapped with right-click in menu, lose input control

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

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

[Bug 825243] Re: tab completion converts input to uppercase

2017-10-26 Thread PeterPall
Weird: The autocompletion code of wxMaxima doesn't contain any command
that converts things to uppercase. And it doesn't happen on my computer.
Still it happens fore some users => We'll have to find out what is the
difference between the computers that work and the computers that don't.

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

Title:
  tab completion converts input to uppercase

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

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

[Bug 1011839] Re: [Patch] libytnef buffer overflow

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=543965.

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


On 2009-12-03T15:42:32+00:00 Paul wrote:

Description of problem:
There are a number of issues with the code of ytnef.c

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

How reproducible:
By using libytnef.

Steps to Reproduce:
1. Run the code (eg, run evolution with the experimental TNEF Attachment 
Decoder plugin).
2.
3.
  
Actual results:
Leaks. Invalid reads.

Expected results:
None of the above.

Additional info:
I'll try to attach a patch shortly.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libytnef/+bug/1011839/comments/0


On 2009-12-03T16:05:10+00:00 Paul wrote:

Created attachment 375822
Fix several issues in ytnef.c

0) This patch is the result of a discussion started at a evolution
bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=602177

1) The patch tries to fix these issues:
- SwapWord(), SwapDWord() and SwapDDWord() can return a pointer to a local 
value (in big endian mode). They can also be simplified (though some might 
argue with my idea of simple here);
- TNEFRendData() reads a 14 byte (packed) value in a TNEF stream as if it were 
a 16 byte (unpacked) struct;
- leaks related to MAPIProps->properties->propnames;
- buffer overflow in comp_Prebuf.data (in DecompressRTF()), fixed by a minor 
code reorganization;
- one "if branch" in DecompressRTF() should have a return (though I have no way 
to test what that return should be).

2) Note that the code (even with this patch) generates a lot of compiler
warnings. I haven't really looked at those.

3) Upstream looks dead to me. If (something like) the patch is accepted
will the packager contact other packagers (as the patch does fix a
buffer overflow)? Or should (something like) the patch just be dropped
as upstream's page (at sf.net)?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libytnef/+bug/1011839/comments/1


On 2009-12-03T16:09:42+00:00 Paul wrote:

(In reply to comment #1)
> 1) The patch tries to fix these issues:
> - SwapWord(), SwapDWord() and SwapDDWord() can return a pointer to a local
> value (in big endian mode). They can also be simplified (though some might
> argue with my idea of simple here);
> - TNEFRendData() reads a 14 byte (packed) value in a TNEF stream as if it were
> a 16 byte (unpacked) struct;
> - leaks related to MAPIProps->properties->propnames;
> - buffer overflow in comp_Prebuf.data (in DecompressRTF()), fixed by a minor
> code reorganization;
> - one "if branch" in DecompressRTF() should have a return (though I have no 
> way
> to test what that return should be).

Furthermore:
- TNEFPriority() accesses a 2 byte WORD value as if it were a 4 byte DWORD 
value.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libytnef/+bug/1011839/comments/2


On 2009-12-04T11:34:50+00:00 Paul wrote:

Created attachment 376060
[RFC] Address all current gcc (default) warnings

(In reply to comment #1)
> 2) Note that the code (even with this patch) generates a lot of compiler
> warnings. I haven't really looked at those.

- gcc will compile ytnef.c without any warnings with this patch (that should be 
applied on top of my previous patch).
- Most of the fixes are entirely trivial: one wonders why those changes have 
not been done earlier.
- I had to resort to casting a few times; as far as I know all casts should be 
safe (but a review whether that is actually correct would be much appreciated).
- I changed the definition of to_utf8(), which, sadly, is included in 
. Still seemed the best thing to do.
- Please note the few remarks I added about the current interface.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libytnef/+bug/1011839/comments/3


On 2009-12-18T11:13:40+00:00 Milan wrote:

These are warnings I see on my 64bit machine.
> ytnef.c: In function 'TNEFFillMapi':
> ytnef.c:474: warning: format '%i' expects type 'int', but argument 2 has type
> 'long int'
> ytnef.c:475: warning: format '%i' expects type 'int', but argument 2 has type
> 'long int'
> ytnef.c:480: warning: format '%i' expects type 'int', but argument 2 has type
> 'long int'
> ytnef.c:481: warning: format '%i' expects type 'int', but argument 2 has type
> 'long int'

There is a format for them, like G_GUINT32_FORMAT, which might help
here. I tested both patches and it otherwise looks good. I would
recommend to use them 

[Bug 149127] Re: Guest root can escape to domain 0 through grub.conf and pygrub

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=302801.

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


On 2007-09-24T09:06:33+00:00 Mark wrote:

Reported to secur...@redhat.com but was also entered into public bz at
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1068

...
Pygrub is a Xen utility which emulates the Grub bootloader
such that boot parameters of a guest domain can be configured
from inside that guest domain. Pygrub is distributed with Xen.

When booting a guest domain, pygrub uses Python exec() statements
to process untrusted data from grub.conf.  By crafting a grub.conf
file, the root user in a guest domain can trigger execution of
arbitrary Python code in domain 0.

The offending code is in xen/tools/pygrub/src/GrubConf.py, in lines
such as

  exec("%s = r\"%s\"" %(self.commands[com], arg.strip()))

This can be exploited from within a guest domain, for example by
modifying /boot/grub/grub.conf and changing the 'default' statement
into something like

  default "+str(0*os.system(" insert evil command here "))+"

On the next boot of the guest domain, the evil command will execute
in domain 0.

Whether this is a security problem depends on how Xen is used.
It definitely is a problem in the case where pygrub is used to boot
a guest domain while system administration of that guest domain
is delegated to an untrusted party.
...

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


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

** 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/149127

Title:
  Guest root can escape to domain 0 through grub.conf and pygrub

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

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

[Bug 136837] Re: Mixer applet randomly decides to consider my sound card to be "muted" when changing volume

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=295311.

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


On 2007-09-18T18:53:05+00:00 Ugo wrote:

Description of problem:
just updated my devel system to today rawhide release, and
gnome-applets-2.20.0-1.fc8 was updated, now when i change the volume level via
mixer applet, the tooltip doesn't update the current volume any more... always
show the old one (the volume level at user logon)

i think this could be a symptom of a wider problem caused by the latest gtk2
tooltip's framework rewrite... i also noted a increase of delay when showing
tooltips and updating his contents in realtime (in Fedora7 it's almost 
immediate)

Version-Release number of selected component (if applicable):
gnome-applets-2.20.0-1.fc8

How reproducible:
click in the volume mixer applet and change the volume

Steps to Reproduce:
1.
2.
3.
  
Actual results:
the tooltips remain stucked to login volume

Expected results:
change the volume tooltip content in realtime as volume change from the mixer

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/10


On 2007-09-19T06:02:58+00:00 Matthias wrote:

I don't think that GTK is to blame for this; there is other brokenness in the
mixer applet right now, e.g. the values dont' always go from 0 to 100, and 
the muting/unmuting happens semi-randomly when changing the level. This may 
be fallout from the switch from polling to notification.

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


On 2007-09-19T07:52:15+00:00 Ugo wrote:

Yes i agree, i verified other apps and the tooltips visualization is
working fine.

Best Regards

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/12


On 2007-09-20T00:19:13+00:00 Bastien wrote:

(In reply to comment #1)
> I don't think that GTK is to blame for this; there is other brokenness in the
> mixer applet right now, e.g. the values dont' always go from 0 to 100, and 
> the muting/unmuting happens semi-randomly when changing the level. This may 
> be fallout from the switch from polling to notification.

I've fixed those bits, should be in 1:2.20.0-2. The problem also exists upstream
(without the notification patch) when changing the volume fast, some calls to
alsa-lib fail, but we don't know that. So we ignore the failed gets/sets and
just use the value that's in the UI.

The obvious problem is that the hardware and the UI might get out of sync, but
that's better than the UI going bananas and the mute state switching all over
the place. I filed http://bugzilla.gnome.org/show_bug.cgi?id=478498 against
GStreamer, and http://bugzilla.gnome.org/show_bug.cgi?id=478485 against the 
applet.

Let me know how the new build works for you. Should be at:
http://koji.fedoraproject.org/koji/taskinfo?taskID=166805

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/13


On 2007-09-20T01:13:44+00:00 Ugo wrote:

Hi Bastien,

just tried your patch and now the mixer applet is working good!

i also noted the out of sync mixer bug, but it happened  only on fast volume
change... however the mixer applet is now fully usable...
many thanks for your light fast patch, very very good job Bastien.

Best Regards

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/14


On 2007-09-20T10:15:35+00:00 Bastien wrote:

Excellent, thanks for testing Ugo.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/16


On 2007-09-24T20:55:35+00:00 Bastien wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/19


On 2007-09-24T23:48:32+00:00 Thomas wrote:

Is this patch supposed to be in rawhide yet? The referenced packages are older
than what's currently there.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/20


On 2007-09-25T11:50:51+00:00 Bastien wrote:

(In reply to comment #7)
> Is this patch supposed to 

[Bug 207744] Re: Clicking notification panel icon doesn't switch desktops

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=371161.

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


On 2007-11-08T13:53:02+00:00 Adrian wrote:

Description of problem:

With this patch (metacity-firefox-workaround-2.patch) the used behaviour of
pidgin when clicking on the tray icon changed/broke.

Up until this patch it was possible to click on the tray icon of pidgin and no
matter on which workspace this is done the buddy list appears on that workspace.

Now if clicking the tray icon the buddy list just disappears on the workspace it
is displayed and clicking it again lets it appear on the other workspace.

>From my point of view this is a regression in the usability of my usage of the
whole desktop.

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

metacity-2.20.0-3.fc8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/0


On 2007-11-11T11:25:59+00:00 Pedro wrote:

I confirm this behaviour and also think this is a regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/1


On 2007-11-11T11:48:30+00:00 Yanko wrote:

Same thing with liferea and its behavior on clicking the notification
icon.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/2


On 2007-11-11T20:56:07+00:00 Matthias wrote:

CCing Colin, who did that patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/3


On 2007-11-12T17:28:37+00:00 Colin wrote:

What's happening here is that the Pidgin buddy list feels very similar to a menu
popup, but is actually implemented as a regular window.  Pidgin seems to be one
of the few applications where the application relied on the behavior of
gtk_window_present() bringing windows to the current workspace.

On Compiz it seems to have the same behavior, which is interesting, because
before Compiz and Metacity differed on the gtk_window_present(), so there must
be some Pidgin-specific differentiation occuring somehow.

Anyways, since the Firefox patch was removed before Fedora 8, there isn't much
point to having this patch in Fedora 8 either.  I will remove it and add an 
update.

We will figure out how to fix Firefox and Metacity together for Fedora 9, and
update them in sync.



Reply at: 
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/4


On 2007-11-13T05:41:37+00:00 Elijah wrote:

This sounds like pidgin is trying to use _NET_ACTIVE_WINDOW as a hack to
simulate "launching" the buddy window?  It could just launch it and then we know
to move it to the right workspace...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/5


On 2008-04-16T17:43:10+00:00 Etan wrote:

For the record pidgin has no policy decisions on what should or shouldn't 
happen when the use clicks the tray icon. All pidgin wants is that the buddy 
list window be presented to the user as such using gtk_window_present is the 
correct thing for us to be doing. Any policy decisions on what that means for 
pidgin are squarely in the realm of the window manager, desktop environment, 
and user preference. So again, pidgin itself relies on no specific behaviour 
out of gtk_window_present other than that of 'presenting the window to the 
user'.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/9


On 2008-05-14T03:51:43+00:00 Bug wrote:

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/10


On 2009-06-09T23:09:39+00:00 Bug wrote:


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

Package Maintainer: If you wish for this bug to remain open because you

[Bug 137738] Re: [gutsy] suspend / hibernate works fine, but after resume, I get a "Failed to suspend" popup

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=312761.

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


On 2007-09-29T22:21:48+00:00 Matthew wrote:

Description of problem:
I hibernate my Thinkpad T61 and that seems to work fine, but on resume the pm
applet pops up a balloon saying it failed.

Version-Release number of selected component (if applicable):
pm-utils-0.99.4-3.fc8

How reproducible:
Always

Steps to Reproduce:
1. Hibernate using pm applet.
2. Resume.
3.
  
Actual results:
Error balloon pops up claiming hibernate failed.

Expected results:
No error ballon.  (Either because it worked or because whatever error occured
has been fixed...)

Additional info:

I'm attaching pm-suspend.log and relevant secctions of messages.  I had SELinux
in permissive mode for this test, but you will see some AVCs in the log.

(Looking at the log, I'm not sure if this is a pm-utils issue or a kernel issue,
but I'll file here first.)

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/137738/comments/5


On 2007-09-29T22:25:09+00:00 Matthew wrote:

Created attachment 211441
pm-suspend log from "failed" hibernate

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/137738/comments/6


On 2007-09-29T22:26:07+00:00 Matthew wrote:

Created attachment 211451
portion of /var/log/messages related to "failed" hibernate

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/137738/comments/7


On 2007-09-30T09:38:31+00:00 Till wrote:

Afaik, the applet belongs to gnome-power-manager, the pm-suspend does not
contain any warnings, therefore I guess it is an applet issue.
Maybe you need to increase verbosity to get a helping log, because the critical
log entries seem to be:

Sep 29 18:02:37 valkyrie gnome-power-manager: (mjs) Resuming computer
Sep 29 18:02:37 valkyrie gnome-power-manager: (mjs) hibernate failed

But a reason why it failed is missing.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/137738/comments/8


On 2007-09-30T21:15:37+00:00 Matthew wrote:

OK How do I get better debug logs?  Thanks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/137738/comments/9


On 2007-10-05T03:15:33+00:00 Matthias wrote:

David, any clue about this ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/137738/comments/10


On 2007-10-05T15:17:39+00:00 David wrote:

g-p-m is expect the wrong return types from hal; so I wrote a patch (will attach
in the next comment) but for some reason beyond me I still get the "Sleep
problem" dialog from g-p-m. Richard, what gives?

FWIW, it works fine using dbus-send:

[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.DBus.Introspectable.Introspect |grep -2 Suspend
  
  

  
  


  
  
[davidz@oneill ~]$ 
[davidz@oneill ~]$ 
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
method return sender=:1.4 -> dest=:1.434 reply_serial=2
   int32 0
[davidz@oneill ~]$ 
[davidz@oneill ~]$ 
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.DBus.Introspectable.Introspect |grep -2 Hibernate
  


  

[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
[davidz@oneill ~]$ 
[davidz@oneill ~]$ 
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
method return sender=:1.4 -> dest=:1.487 reply_serial=2
   int32 0


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137738/comments/11


On 2007-10-05T15:18:54+00:00 David wrote:

Created attachment 217621
Patch to fix expected return types

This patch should go upstream.

Reply at: 

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 29 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=214446.

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


On 2006-11-07T17:53:46+00:00 Travis wrote:

Description of problem:  
The screen does not refresh when connecting to a VNC Server (remote desktop) 
that has 'Desktop Effects' enabled.

When connecting to a Server with Desktop Effects enabled, a screen shot of the 
desktop is displayed in the client but never again updates.  You can monitor 
the Server's display and see that the mouse and keyboard function, however no 
output can be seen through the VNC client.

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


How reproducible:
This is consistent with my configuration.  Disabling Desktop Effects 
immediately resolved the problem.

Steps to Reproduce:
1.  Enable desktop effects
2.  Establish a VNC connection to FC6 from remote machine
3.  Note the screen displays, but you do not recieve and screen updates
  
Actual results:


Expected results:


Additional info:  The configuration is on a Dell D610 with Intel video drivers.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/0


On 2006-11-07T17:56:06+00:00 Travis wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/1


On 2006-11-08T10:22:26+00:00 Adam wrote:

please, could you specify more when is the desktop effect options?? I can't find
it + which window manager're you using. thanks

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/2


On 2006-11-08T12:35:17+00:00 Travis wrote:

In gnome, under System/Preferences/Desktop Effects.  You can 'Enable Desktop 
Effects' which change the behavior of the Windows to wobble when dragged.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/3


On 2006-11-20T16:31:08+00:00 Victor wrote:

I have the same problem, my window manager is the default one, compiz, it shows
up in the ps command as following : 

compiz --sm-client-id default1 gconf

If you exits the vncviewer and restart the session the image is updated.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/4


On 2006-12-05T13:43:21+00:00 Adam wrote:

Could you please write me if you join to native vncserver (from vnc-server
package) or to gnome's vino server?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/5


On 2006-12-05T16:31:54+00:00 Travis wrote:

It is the vino server, activated by the Remote Desktop features within Gnome.  
This is from a very generic installation of FC6.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/6


On 2007-01-18T16:37:18+00:00 Adam wrote:

This bug isn't in vnc. Reassigning to proper component.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/7


On 2007-08-17T15:29:49+00:00 Didier wrote:

Confirmed on a fully updated F7, with components :

vino-2.18.0-1.fc7
vnc-4.1.2-18.fc7 (for vncviewer)
compiz-0.4.0-1.fc7 (for desktop effects)


Disclaimer : tested with the proprietary nvidia driver
(kmod-nvidia-100.14.11-1.2.6.22.1_41.fc7 and 
xorg-x11-drv-nvidia-100.14.11-1.lvn7)


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/8


On 2007-09-03T10:10:53+00:00 Tomasz wrote:

This bug is a duplicate of
https://bugzilla.redhat.com/show_bug.cgi?id=208983

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/12


On 2007-11-04T01:19:33+00:00 Aaron wrote:

x11vnc apparently works where vino fails:
http://ubuntuforums.org/showthread.php?t=470306

Perhaps the '-noxdamage' option for x11vnc can be reproduced for vino to
fix this?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/13



[Bug 1502155] Re: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop

2017-10-26 Thread Bug Watch Updater
** Changed in: fedora
   Status: Unknown => Invalid

** 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/1502155

Title:
  [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while
  booting Unity-Desktop

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

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

[Bug 1485213] Re: Compile error: ‘QT_STATIC_CONST’ does not name a type

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1164515.

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


On 2014-11-16T02:25:34+00:00 Brallan wrote:

Description of problem:
The current version of Qwt works only with Qt4. Some errors are produced while 
build a Qt5 project using it in QtCreator.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a Qwt plot
2. Configure properly .pro file in QtCreator (add LIBS += -lqwt)
3. Compile. Segmentation fault is produced

Actual results:
The Qwt Fedora package was compiled using Qt4 instead of Qt5

Expected results:
Depending of the Qt version of the project, there would be a Qwt for it

Additional info:
http://stackoverflow.com/questions/21682219/segfault-in-qt-code-when-linking-qwt-libraries

Reply at: https://bugs.launchpad.net/ubuntu/+source/qwt-
qt5/+bug/1485213/comments/0


On 2014-11-16T02:50:39+00:00 Rex wrote:

Hrm, last I tried, qwt didn't support qt5

I'll check again.

Reply at: https://bugs.launchpad.net/ubuntu/+source/qwt-
qt5/+bug/1485213/comments/1


On 2014-11-16T02:52:39+00:00 Rex wrote:

http://qwt.sourceforge.net/qwtinstall.html

claims it does, but

[ qwt-6.1.1]$ qmake-qt5 .
[ qwt-6.1.1]$ make
cd src/ && ( test -e Makefile || /usr/bin/qmake-qt5 
/home/rdieter1/SCM/pkgs.fedoraproject.org/BUILDROOT/qwt-6.1.1/src/src.pro -o 
Makefile ) && make -f Makefile 
make[1]: Entering directory 
`/home/rdieter1/SCM/pkgs.fedoraproject.org/BUILDROOT/qwt-6.1.1/src'
g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 
-mtune=generic -O2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_NO_KEYWORDS 
-DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
-I/usr/lib64/qt5/mkspecs/linux-g++ -I. -isystem /usr/include/qt5 -isystem 
/usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg -isystem 
/usr/include/qt5/QtOpenGL -isystem /usr/include/qt5/QtWidgets -isystem 
/usr/include/qt5/QtGui -isystem /usr/include/qt5/QtConcurrent -isystem 
/usr/include/qt5/QtCore -Imoc -o obj/qwt_abstract_scale_draw.o 
qwt_abstract_scale_draw.cpp
In file included from qwt_scale_map.h:14:0,
 from qwt_abstract_scale_draw.cpp:14:
qwt_transform.h:110:5: error: ‘QT_STATIC_CONST’ does not name a type
 QT_STATIC_CONST double LogMin;
 ^
qwt_transform.h:111:5: error: ‘QT_STATIC_CONST’ does not name a type
 QT_STATIC_CONST double LogMax;
 ^
make[1]: *** [obj/qwt_abstract_scale_draw.o] Error 1
make[1]: Leaving directory 
`/home/rdieter1/SCM/pkgs.fedoraproject.org/BUILDROOT/qwt-6.1.1/src'
make: *** [sub-src-make_first-ordered] Error 2


I'll try to contact upstream to find out what's going wrong here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/qwt-
qt5/+bug/1485213/comments/2


On 2014-11-16T03:52:00+00:00 Rex wrote:

I found upstream has a couple of Qt-5.4-specific fixes committed since
6.1.1 release, which look promising.

Reply at: https://bugs.launchpad.net/ubuntu/+source/qwt-
qt5/+bug/1485213/comments/3


On 2014-11-16T04:00:21+00:00 Rex wrote:

Oh, it's too bad, upstream's Qt5 support is ... poor.

They currently do not support parallel-installs of both Qt4 and Qt5
versions (library names and support files are all named the same).

Fixing this is likely a prerequisite before we can ship a qt5-enabled
qwt build in fedora.

Reply at: https://bugs.launchpad.net/ubuntu/+source/qwt-
qt5/+bug/1485213/comments/4


On 2014-11-16T04:02:31+00:00 Rex wrote:

marking RFE/FutureFeature

Reply at: https://bugs.launchpad.net/ubuntu/+source/qwt-
qt5/+bug/1485213/comments/5


On 2014-11-26T16:31:07+00:00 Rex wrote:

Fwiw, appended is the patch opensuse currently uses, referenced in upstream ml 
discussion on this topic,
http://sourceforge.net/p/qwt/mailman/message/33075738/

diff -urN qwt-6.1.0-orig/designer/designer.pro qwt-6.1.0/designer/designer.pro
--- qwt-6.1.0-orig/designer/designer.pro2013-05-30 18:18:27.753341938 
+0300
+++ qwt-6.1.0/designer/designer.pro 2013-09-16 18:10:22.317441101 +0300
@@ -95,7 +95,7 @@
 LIBS  += -L$${QWT_ROOT}/lib
 }

-qwtAddLibrary(qwt)
+

[Bug 1569613] Re: /usr/bin/nm-applet:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all:nma_icons_reload:g_closure_invoke

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1350136.

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


On 2016-06-25T23:45:42+00:00 Yonatan wrote:

Version-Release number of selected component:
network-manager-applet-1.2.0-1.fc24

Additional info:
reporter:   libreport-2.7.1
backtrace_rating: 3
cmdline:nm-applet
crash_function: g_hash_table_remove_all_nodes
executable: /usr/bin/nm-applet
global_pid: 1432
kernel: 4.5.7-300.fc24.i686+PAE
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
reproducible:   Not sure how to reproduce the problem
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 6 (1 frames)
 #0 ??

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


On 2016-06-25T23:45:56+00:00 Yonatan wrote:

Created attachment 1172382
File: backtrace

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


On 2016-06-25T23:46:00+00:00 Yonatan wrote:

Created attachment 1172383
File: cgroup

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


On 2016-06-25T23:46:05+00:00 Yonatan wrote:

Created attachment 1172384
File: core_backtrace

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


On 2016-06-25T23:46:11+00:00 Yonatan wrote:

Created attachment 1172385
File: dso_list

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


On 2016-06-25T23:46:15+00:00 Yonatan wrote:

Created attachment 1172386
File: environ

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


On 2016-06-25T23:46:19+00:00 Yonatan wrote:

Created attachment 1172387
File: limits

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


On 2016-06-25T23:46:27+00:00 Yonatan wrote:

Created attachment 1172388
File: maps

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


On 2016-06-25T23:46:31+00:00 Yonatan wrote:

Created attachment 1172389
File: mountinfo

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1569613/comments/9


On 2016-06-25T23:46:36+00:00 Yonatan wrote:

Created attachment 1172390
File: namespaces

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1569613/comments/10


On 2016-06-25T23:46:40+00:00 Yonatan wrote:

Created attachment 1172391
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1569613/comments/11


On 2016-06-25T23:46:43+00:00 Yonatan wrote:

Created attachment 1172392
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1569613/comments/12


On 2016-06-25T23:46:47+00:00 Yonatan wrote:

Created attachment 1172393
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1569613/comments/13


On 2016-09-26T11:34:09+00:00 Beniamino wrote:

Should be fixed by:

https://git.gnome.org/browse/network-manager-
applet/commit/?id=f0f11106eb988229ec6a813457ec504f64c2f22d

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1569613/comments/14


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

** Changed in: network-manager-applet
   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/1569613

Title:
  /usr/bin/nm-
  

[Bug 1375555] Re: global static TLS slot limit breaks the x86 emulator

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 35 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1124987.

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


On 2014-07-30T19:22:15+00:00 Adam wrote:

Description of problem:
Crashes on startup in current F21.

Version-Release number of selected component:
calibre-1.46.0-1.fc21

Additional info:
reporter:   libreport-2.2.3
cmdline:python2 /usr/bin/calibre --detach
executable: /usr/bin/calibre
kernel: 3.16.0-0.rc6.git2.2.fc22.x86_64
runlevel:   N 5
type:   Python
uid:1001

Truncated backtrace:
#1  in /usr/lib64/calibre/calibre/utils/magick/__init__.py:14
#2  in /usr/lib64/calibre/calibre/db/backend.py:31
#3  in /usr/lib64/calibre/calibre/db/legacy.py:17
#4  in /usr/lib64/calibre/calibre/gui2/ui.py:26
#5 run_gui in /usr/lib64/calibre/calibre/gui2/main.py:320
#6 main in /usr/lib64/calibre/calibre/gui2/main.py:458
#7  in /usr/bin/calibre:20

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/0


On 2014-07-30T19:22:18+00:00 Adam wrote:

Created attachment 922690
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/1


On 2014-07-30T19:22:19+00:00 Adam wrote:

Created attachment 922691
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/2


On 2014-08-06T13:17:25+00:00 Colin wrote:

I suspect this is a glibc change.  We're seeing the same error message
in an Anaconda environment from trying to dlopen(libgtk.so).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/3


On 2014-08-06T13:20:12+00:00 Adam wrote:

So, let's CC the glibc maintainer (at least, the person to whom glibc
bugs appear currently to be assigned).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/4


On 2014-08-08T12:41:54+00:00 Adam wrote:

Created attachment 925164
LD_DEBUG log from crash (requested by carlos)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/5


On 2014-08-08T12:51:31+00:00 Carlos wrote:

Please get the list of all shared libraries loaded by python then run
`readelf -a -W` against all of them and dump that to a file. I want to
know which if the libraries is using static TLS.

The error you are seeing is not a bug in glibc. The dynamic loader has a
fixed amount of "super fast" static TLS for use by core libraries which
are always loaded and can use this static TLS. Normal libraries should
not be using static TLS and you should not be running out of static TLS,
those loaded libraries should be using dynamic TLS which has no limits
(not quite as fast as static TLS but still fast).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/6


On 2014-08-08T13:30:38+00:00 Colin wrote:

This is a good post on the issue:

http://stackoverflow.com/questions/19268293/matlab-error-cannot-open-
with-static-tls

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/7


On 2014-08-08T13:32:52+00:00 Kevin wrote:

"Please get the list of all shared libraries loaded by python then run
`readelf -a -W` against all of them and dump that to a file."

Is there some easy way to get this list without parsing the strace
output?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/8


On 2014-08-08T19:26:34+00:00 Adam wrote:

I thought it might be in the abrt data, but I don't see it in there at
least in an obvious way. I can do the parsing, I just didn't want to
embarrass myself doing it in my monkey way in front of carlos :P when I
have some privacy to pore over the 'cut' manpages without anyone seeing,
I'll get it done...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/137/comments/9


On 2014-08-09T07:20:38+00:00 Carlos wrote:

(In reply to Adam Williamson (Red Hat) from comment #9)
> I thought it might be in the abrt data, but I don't see it in there at least
> in an obvious way. I can do the 

[Bug 1512848] Re: Radeon VCE Init Error

2017-10-26 Thread Bug Watch Updater
** Changed in: linux (Fedora)
   Status: Unknown => Won't Fix

** Changed in: linux (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/1512848

Title:
  Radeon VCE Init Error

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

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

[Bug 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

2017-10-26 Thread Bug Watch Updater
** Changed in: pulseaudio (Fedora)
   Status: Unknown => Won't Fix

** Changed in: pulseaudio (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/1710060

Title:
  Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

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

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

[Bug 1727321] Re: drag and drop through the side panel to activate the window is not working.

2017-10-26 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Confirmed

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

Title:
  drag and drop through the side panel to activate the window is not
  working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1727321/+subscriptions

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

[Bug 1324095] Re: [Lenovo Yoga 2 Pro] ideapad_laptop kernel module breaks wireless

2017-10-26 Thread Andreas Olsson
I no longer have that Yoga 2 Pro laptop.

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

Title:
  [Lenovo Yoga 2 Pro] ideapad_laptop kernel module breaks wireless

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

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

[Bug 1642163] Re: virtualbox-dkms: virtualbox kernel module failed to build [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type]

2017-10-26 Thread Daniel van Vugt
** Summary changed:

- virtualbox-dkms 5.1.8-dfsg-6build1: virtualbox kernel module failed to build 
with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from 
incompatible pointer type]
+ virtualbox-dkms: virtualbox kernel module failed to build [error: passing 
argument 5 of ‘get_user_pages’ from incompatible pointer type]

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

Title:
  virtualbox-dkms: virtualbox kernel module failed to build [error:
  passing argument 5 of ‘get_user_pages’ from incompatible pointer type]

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

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

Re: [Bug 1723994] Re: Keyboard plugged in to monitor USB hub does not work at password prompt

2017-10-26 Thread Kai-Heng Feng
> On 26 Oct 2017, at 11:20 PM, Dan Watkins  wrote:
> 
> On Thu, Oct 26, 2017 at 03:09:12PM -, Kai-Heng Feng wrote:
>> They should work, at least at initramfs stage. You can use the keyboard
>> to decrypt rootfs proves that.
> 
> I can use the keyboard to decrypt the rootfs if it's plugged in after
> boot.  If it's plugged in before boot, it doesn't work.
> 
> (It also continues to work on _reboot_; it's just on a power cycle that
> it doesn't.)
> 
>> Does your lsusb in #11 captured when the keyboards didn't work?
> 
> I'm not sure I understand the question; could you clarify?

I’d like to see the dmesg when the issue happens, because the dmesg here
says both keyboards were detected (and should work).

So I guess the dmesg here was collected when you reboot instead of cold
boot.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1723994
> 
> Title:
>  Keyboard plugged in to monitor USB hub does not work at password
>  prompt
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  I have my external keyboard plugged in to my monitor's USB hub.
>  Unless I unplug and replug the USB cable that connects the monitor hub
>  to my machine, I can't use my keyboard on boot.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: cryptsetup 2:1.7.3-4ubuntu1
>  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>  Uname: Linux 4.13.0-16-generic x86_64
>  ApportVersion: 2.20.7-0ubuntu3
>  Architecture: amd64
>  Date: Mon Oct 16 11:45:42 2017
>  EcryptfsInUse: Yes
>  InstallationDate: Installed on 2014-09-04 (1138 days ago)
>  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
> (20140722.2)
>  SourcePackage: cryptsetup
>  UpgradeStatus: Upgraded to artful on 2016-12-05 (315 days ago)
>  cmdline: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
> root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
> vt.handoff=7
>  crypttab:
>   sda3_crypt UUID=dc873bc3-22f0-491d-9f5b-50d322f31987 none luks,discard
>   #cryptswap1 UUID=f44f685a-f520-4e81-b35a-0b9cba44a8a9 /dev/urandom 
> swap,cipher=aes-cbc-essiv:sha256
>  --- 
>  ApportVersion: 2.20.7-0ubuntu3
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC1:  daniel 9156 F pulseaudio
>   /dev/snd/controlC0:  daniel 9010 F volumeicon
>daniel 9156 F pulseaudio
>  DistroRelease: Ubuntu 17.10
>  EcryptfsInUse: Yes
>  InstallationDate: Installed on 2014-09-04 (1145 days ago)
>  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
> (20140722.2)
>  MachineType: LENOVO 20ANCTO1WW
>  Package: linux (not installed)
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
> root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
> vt.handoff=7
>  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>  RelatedPackageVersions:
>   linux-restricted-modules-4.13.0-16-generic N/A
>   linux-backports-modules-4.13.0-16-generic  N/A
>   linux-firmware 1.169
>  Tags:  artful
>  Uname: Linux 4.13.0-16-generic x86_64
>  UpgradeStatus: Upgraded to artful on 2016-12-05 (321 days ago)
>  UserGroups: adm audio cdrom dip disk docker fuse libvirt libvirtd lpadmin 
> lxd plugdev sambashare sbuild sudo
>  _MarkForUpload: True
>  dmi.bios.date: 05/21/2014
>  dmi.bios.vendor: LENOVO
>  dmi.bios.version: GLET70WW (2.24 )
>  dmi.board.asset.tag: Not Available
>  dmi.board.name: 20ANCTO1WW
>  dmi.board.vendor: LENOVO
>  dmi.board.version: SDK0E50512 STD
>  dmi.chassis.asset.tag: No Asset Information
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: LENOVO
>  dmi.chassis.version: Not Available
>  dmi.modalias: 
> dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
>  dmi.product.family: ThinkPad T440p
>  dmi.product.name: 20ANCTO1WW
>  dmi.product.version: ThinkPad T440p
>  dmi.sys.vendor: LENOVO
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723994/+subscriptions

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

Title:
  Keyboard plugged in to monitor USB hub does not work at password
  prompt

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

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

[Bug 1716359] Re: Unplugging headset with audio panel open mutes internal mic

2017-10-26 Thread Hui Wang
Tested the patch in #14, it works.

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

Title:
  Unplugging headset with audio panel open mutes internal mic

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

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

[Bug 1727918] [NEW] package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-10-26 Thread agahowa23
Public bug reported:

Happened while installing gparted

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-apport 2.20.4-0ubuntu4.5
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.5
AptOrdering:
 libgtkmm-2.4-1v5:amd64: Install
 libparted-fs-resize0:amd64: Install
 gparted:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CrashReports: 600:0:122:252397:2017-10-26 21:36:05.151989698 -0600:2017-10-26 
21:36:06.151989698 -0600:/var/crash/python3-apport.0.crash
Date: Thu Oct 26 21:36:05 2017
DuplicateSignature:
 package:python3-apport:2.20.4-0ubuntu4.5
 Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
 dpkg: error processing package python3-apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-10-27 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: apport
Title: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to zesty on 2017-10-27 (0 days ago)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

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

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

[Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change

2017-10-26 Thread Daniel van Vugt
** Also affects: libinput (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libinput via
   https://bugs.freedesktop.org/show_bug.cgi?id=103298
   Importance: Unknown
   Status: Unknown

** Changed in: libinput (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell frozen and using 100% CPU after docking and display
  configuration change

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

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

[Bug 1727802] Re: virtualbox-dkms 5.0.18-dfsg-2build1: virtualbox kernel module failed to build [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type]

2017-10-26 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1642163 ***
https://bugs.launchpad.net/bugs/1642163

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1642163, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- virtualbox-dkms 5.0.18-dfsg-2build1: virtualbox kernel module failed to build
+ virtualbox-dkms 5.0.18-dfsg-2build1: virtualbox kernel module failed to build 
[error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type]

** This bug has been marked a duplicate of bug 1642163
   virtualbox-dkms 5.1.8-dfsg-6build1: virtualbox kernel module failed to build 
with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from 
incompatible pointer type]

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

Title:
  virtualbox-dkms 5.0.18-dfsg-2build1: virtualbox kernel module failed
  to build [error: passing argument 5 of ‘get_user_pages’ from
  incompatible pointer type]

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

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

[Bug 1727918] Re: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-10-26 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/1727918

Title:
  package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

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

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

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-26 Thread Kai-Heng Feng
I don't know. Maybe just install Ubuntu to local disk and install the
kernel?

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

Title:
  touchpad not working (elan_i2c invalid report id data)

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

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

[Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-26 Thread Steve Langasek
ec085c5a51b768947ca481f90b66653e36b3c566 (rebased) is bad.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

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

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

[Bug 1727039] Re: Xorg crash

2017-10-26 Thread Daniel C Aragao
** Package changed: xorg (Ubuntu) => ubuntu

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

Title:
  Xorg crash

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

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

[Bug 1721762] Re: Cancelled installation of snap continues

2017-10-26 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  Cancelled installation of snap continues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1721762/+subscriptions

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

[Bug 1721762] Re: Cancelled installation of snap continues

2017-10-26 Thread Robert Ancell
Note the UI didn't support cancelling in Xenial.

** No longer affects: gnome-software (Ubuntu Xenial)

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

Title:
  Cancelled installation of snap continues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1721762/+subscriptions

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

[Bug 1727742] Re: "peek" hangs Wayland display server

2017-10-26 Thread Daniel van Vugt
"Wayland" is only a protocol. The product you are using is gnome-shell.

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

Title:
  "peek" hangs Wayland display server

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

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

[Bug 1727770] Re: wayland does not have logic for a Lenovo laptop on the dock

2017-10-26 Thread Daniel van Vugt
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu)

** Summary changed:

- wayland does not have logic for a Lenovo laptop on the dock
+ If I resume on the dock, Gnome Shell seems to recognize the lid as closed and 
suspends

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

Title:
  If I resume on the dock, Gnome Shell seems to recognize the lid as
  closed and suspends

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

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

[Bug 1727603] Re: gnome-shell crashed with signal 5 in __GI___libc_free() from g_free() from g_key_file_parse_key_value_pair()

2017-10-26 Thread Daniel van Vugt
Thanks, but that bug seems to be less conclusive for some reason. Maybe
repeat a couple of times? Or maybe the MALLOC_CHECK_ is now hitting a
much earlier issue not related to this one.

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

Title:
  gnome-shell crashed with signal 5 in __GI___libc_free() from g_free()
  from g_key_file_parse_key_value_pair()

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

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

[Bug 1727902] Re: gnome-shell crashed with signal 5 in __GI___poll() from g_main_context_poll() from g_main_context_iterate() from g_main_loop_run()

2017-10-26 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed with signal 5 in __GI___poll()
+ gnome-shell crashed with signal 5 in __GI___poll() from g_main_context_poll() 
from g_main_context_iterate() from g_main_loop_run()

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

Title:
  gnome-shell crashed with signal 5 in __GI___poll() from
  g_main_context_poll() from g_main_context_iterate() from
  g_main_loop_run()

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

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

[Bug 1714101] Re: RM: rsplib fails to build from source: ‘SCTP_GET_PEER_ADDRS_NUM_OLD’ undeclared

2017-10-26 Thread Steve Langasek
Removing packages from bionic:
rsplib 3.0.1-1ubuntu3 in bionic
libcpprspserver-dev 3.0.1-1ubuntu3 in bionic amd64
libcpprspserver-dev 3.0.1-1ubuntu3 in bionic armhf
libcpprspserver-dev 3.0.1-1ubuntu3 in bionic i386
libcpprspserver2 3.0.1-1ubuntu3 in bionic amd64
libcpprspserver2 3.0.1-1ubuntu3 in bionic armhf
libcpprspserver2 3.0.1-1ubuntu3 in bionic i386
librsplib-dev 3.0.1-1ubuntu3 in bionic amd64
librsplib-dev 3.0.1-1ubuntu3 in bionic armhf
librsplib-dev 3.0.1-1ubuntu3 in bionic i386
librsplib2 3.0.1-1ubuntu3 in bionic amd64
librsplib2 3.0.1-1ubuntu3 in bionic armhf
librsplib2 3.0.1-1ubuntu3 in bionic i386
rsplib-dbg 3.0.1-1ubuntu3 in bionic amd64
rsplib-dbg 3.0.1-1ubuntu3 in bionic armhf
rsplib-dbg 3.0.1-1ubuntu3 in bionic i386
rsplib-docs 3.0.1-1ubuntu3 in bionic amd64
rsplib-docs 3.0.1-1ubuntu3 in bionic arm64
rsplib-docs 3.0.1-1ubuntu3 in bionic armhf
rsplib-docs 3.0.1-1ubuntu3 in bionic i386
rsplib-docs 3.0.1-1ubuntu3 in bionic ppc64el
rsplib-docs 3.0.1-1ubuntu3 in bionic s390x
rsplib-fgp-cfgfiles 3.0.1-1ubuntu3 in bionic amd64
rsplib-fgp-cfgfiles 3.0.1-1ubuntu3 in bionic arm64
rsplib-fgp-cfgfiles 3.0.1-1ubuntu3 in bionic armhf
rsplib-fgp-cfgfiles 3.0.1-1ubuntu3 in bionic i386
rsplib-fgp-cfgfiles 3.0.1-1ubuntu3 in bionic ppc64el
rsplib-fgp-cfgfiles 3.0.1-1ubuntu3 in bionic s390x
rsplib-legacy-wrappers 3.0.1-1ubuntu3 in bionic amd64
rsplib-legacy-wrappers 3.0.1-1ubuntu3 in bionic armhf
rsplib-legacy-wrappers 3.0.1-1ubuntu3 in bionic i386
rsplib-registrar 3.0.1-1ubuntu3 in bionic amd64
rsplib-registrar 3.0.1-1ubuntu3 in bionic armhf
rsplib-registrar 3.0.1-1ubuntu3 in bionic i386
rsplib-services 3.0.1-1ubuntu3 in bionic amd64
rsplib-services 3.0.1-1ubuntu3 in bionic armhf
rsplib-services 3.0.1-1ubuntu3 in bionic i386
rsplib-tools 3.0.1-1ubuntu3 in bionic amd64
rsplib-tools 3.0.1-1ubuntu3 in bionic armhf
rsplib-tools 3.0.1-1ubuntu3 in bionic i386
Comment: FTBFS, Ubuntu-only, no maintainer; LP: #1714101
1 package successfully removed.
Removing packages from bionic-proposed:
rsplib 3.0.1-1ubuntu4 in bionic
Comment: FTBFS, Ubuntu-only, no maintainer; LP: #1714101
1 package successfully removed.


** Changed in: rsplib (Ubuntu)
   Status: Triaged => 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/1714101

Title:
  RM: rsplib fails to build from source: ‘SCTP_GET_PEER_ADDRS_NUM_OLD’
  undeclared

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

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

[Bug 1727867] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from _int_realloc() from __GI___libc_realloc() from g_realloc() from g_string_maybe_expand() from g_string_

2017-10-26 Thread Daniel van Vugt
Confirmed by:
https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0

** Description changed:

+ https://errors.ubuntu.com/problem/61214d7f12303ee9de1d1b8a7621c6f5dc47d8f0
+ 
+ ---
+ 
  While trying to pair with a mouse (microsoft sculpt mouse)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 26 23:42:52 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-06-22 (125 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FBCTO1WW
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
-  LANG=fr_FR.UTF-8
-  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/vg--hostname-root--ubuntu ro quiet splash vt.handoff=7
  SegvAnalysis:
-  Segfault happened at: 0x7f6907f6d108 :   mov
0x8(%rbx),%rax
-  PC (0x7f6907f6d108) ok
-  source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f6907f6d108 :   mov
0x8(%rbx),%rax
+  PC (0x7f6907f6d108) ok
+  source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
-  malloc_consolidate (av=av@entry=0x7f69082bec20 ) at malloc.c:4489
-  _int_malloc (av=av@entry=0x7f69082bec20 , 
bytes=bytes@entry=1025) at malloc.c:3705
-  _int_realloc (av=av@entry=0x7f69082bec20 , 
oldp=oldp@entry=0x559621487250, oldsize=oldsize@entry=544, nb=nb@entry=1040) at 
malloc.c:4626
-  __GI___libc_realloc (oldmem=0x559621487260, bytes=1024) at malloc.c:3245
-  g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  malloc_consolidate (av=av@entry=0x7f69082bec20 ) at malloc.c:4489
+  _int_malloc (av=av@entry=0x7f69082bec20 , 
bytes=bytes@entry=1025) at malloc.c:3705
+  _int_realloc (av=av@entry=0x7f69082bec20 , 
oldp=oldp@entry=0x559621487250, oldsize=oldsize@entry=544, nb=nb@entry=1040) at 
malloc.c:4626
+  __GI___libc_realloc (oldmem=0x559621487260, bytes=1024) at malloc.c:3245
+  g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to artful on 2017-10-09 (17 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: E4:A4:71:4F:31:79  ACL MTU: 1021:4  SCO MTU: 96:6
-   UP RUNNING PSCAN ISCAN 
-   RX bytes:980135 acl:0 sco:0 events:12127 errors:0
-   TX bytes:605335 acl:0 sco:0 commands:2477 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: E4:A4:71:4F:31:79  ACL MTU: 1021:4  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN
+   RX bytes:980135 acl:0 sco:0 events:12127 errors:0
+   TX bytes:605335 acl:0 sco:0 commands:2477 errors:0

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

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate() from
  _int_malloc() from _int_realloc() from __GI___libc_realloc() from
  g_realloc() from g_string_maybe_expand() from
  g_string_append_vprintf()

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

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

  1   2   3   4   5   6   7   8   9   10   >