[Bug 825243] Re: tab completion converts input to uppercase

2017-10-26 Thread Rainer Schöpf
Just for the record: This happens with the commandline version, not with
wxMaxima.

-- 
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 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-10-26 Thread Steve Langasek
** Changed in: pam (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

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

[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response

2017-10-26 Thread Bruce Pieterse
Seeing this with other services now:

...
Setting up apport (2.20.7-0ubuntu3.1) ...
Installing new version of config file /etc/apport/crashdb.conf ...
Job for apport.service failed because a timeout was exceeded.
See "systemctl  status apport.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript apport, action "start" failed.
● apport.service - LSB: automatic crash report generation
   Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
   Active: failed (Result: timeout) since Fri 2017-10-27 08:32:10 SAST; 10ms ago
 Docs: man:systemd-sysv-generator(8)
  Process: 28855 ExecStart=/etc/init.d/apport start (code=killed, signal=TERM)
Tasks: 2 (limit: 4915)
   CGroup: /system.slice/apport.service
   └─28858 plymouth --ping

Oct 27 08:27:10 hostname systemd[1]: Starting LSB: automatic crash report 
generation...
Oct 27 08:32:10 hostname systemd[1]: apport.service: Start operation timed out. 
Terminating.
Oct 27 08:32:10 hostname systemd[1]: Failed to start LSB: automatic crash 
report generation.
Oct 27 08:32:10 hostname systemd[1]: apport.service: Unit entered failed state.
Oct 27 08:32:10 hostname systemd[1]: apport.service: Failed with result 
'timeout'.
Setting up gir1.2-mutter-1:amd64 (3.26.1-2ubuntu2) ...
Setting up mutter (3.26.1-2ubuntu2) ...
...

strace as requested.

** Attachment added: "strace-plymouth-ping.txt"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+attachment/4997508/+files/strace-plymouth-ping.txt

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

Title:
  Virtualbox service fails to start due to hanging plymouth --ping
  response

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

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

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

2017-10-26 Thread Dima
Thank you for your reply in this world of silence :).

I think "UpgradeStatus:" means status of distro upgrade (apt-get dist-
upgrade). But I've tried "apt-get update && apt-get upgrade" and
redeclipse still crashes.

I will try your second move soon. Thank you!

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

Title:
  Segmentation fault on map loading (17.10)

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

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

[Bug 1724487] Re: Quirk for 2-button mouse Logitech M560

2017-10-26 Thread Timo Aaltonen
What's the point of this bug? You're not saying what to quirk, the
driver you're using is not -evdev and any quirks should really go
upstream anyway.. (libinput)

** Changed in: xserver-xorg-input-evdev (Ubuntu)
   Status: New => Invalid

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

Title:
  Quirk for 2-button mouse Logitech M560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1724487/+subscriptions

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

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

2017-10-26 Thread Ajinkya Kulkarni
Public bug reported:

occurs while updating

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Oct 27 12:08:14 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2017-02-11 (257 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu15.3 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.keyboard-setup: [deleted]

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

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

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

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

[Bug 1727942] [NEW] Remote log are not merged

2017-10-26 Thread Alessio Tomelleri
Public bug reported:

Hi,

in a phisical machine I'm starting to collect remote journal, but I
think I'm falling in this bug :

https://github.com/systemd/systemd/pull/4970

and it seems has been fixed... is it possible backport the fix ?

thx


$ uname -a
Linux pandorax 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"

$ journalctl --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

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

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

Title:
  Remote log are not merged

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

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

[Bug 1592561] Re: Doesn't work on arm64

2017-10-26 Thread Timo Aaltonen
the driver has been removed from the archive, the hw should use the
default modesetting driver instead

** Changed in: xserver-xorg-video-ast (Ubuntu)
   Status: New => Invalid

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

Title:
  Doesn't work on arm64

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

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

[Bug 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing

2017-10-26 Thread Timo Aaltonen
besides, the driver has been removed from the archive since xenial which
would explain why there's no -hwe-16.04

** Package changed: xorg (Ubuntu) => xserver-xorg-video-ast (Ubuntu)

** Changed in: xserver-xorg-video-ast (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package xserver-xorg-video-ast-hwe-16.04 missing

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

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

[Bug 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing

2017-10-26 Thread Timo Aaltonen
why on earth would you need that for nvidia hardware?

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package xserver-xorg-video-ast-hwe-16.04 missing

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

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

[Bug 1727877] Re: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop

2017-10-26 Thread Timo Aaltonen
glxgears is not a benchmark

** No longer affects: xorg-server (Ubuntu)

** Changed in: xorg-server
   Status: New => Invalid

** Project changed: wayland => gnome-control-center (Ubuntu)

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

Title:
  AMD Radeon 520 graphics card not detected in wayland session when
  using AMD/Intel hybrid laptop

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

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

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

2017-10-26 Thread Peter Wallbridge
I see both.

During power up, the messages appear on displays 1 and 3.
The sign in is on screen 2 (primary display).

The display manager shows 3 displays, but after the apply is selected, only
two work.

Why do they work with Xfce and not with gnome?

Thanks

Peter



On Fri, Oct 27, 2017 at 2:20 AM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thanks. Perhaps we jumped the gun though...
>
> On your login screen do you see two options "Ubuntu" and "Ubuntu on
> Xorg", or only one?
>
> It looks like you might be experiencing a problem with Xorg judging by
> comment #4:
>
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
>
> ** Bug watch added: GNOME Bug Tracker #789540
>https://bugzilla.gnome.org/show_bug.cgi?id=789540
>
> ** Also affects: mutter via
>https://bugzilla.gnome.org/show_bug.cgi?id=789540
>Importance: Unknown
>Status: Unknown
>
> ** Also affects: xorg-server (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: xorg-server (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: mutter (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

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

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1284196] Re: Install to 3TB disk fails with "attempt to read or write outside of disk" error on reboot

2017-10-26 Thread Aaditya Bagga
I was hit by this bug too when installing Zentyal server 5.0 (based on
Ubuntu Server 16.04 with Ubiquity) [1] on a Dell Poweredge R530 with a
4Tb Raid 5 hard disk.

If I chose guided partitioning, Ubiquity created 3 partitions, 1 Mb
bios_boot partition, ~ 4 Tb root partition, and 16 Gb Swap partition.

With above partitioning and booting in BIOS mode, I got "Error: attempt
to read or write outside of disk `hd0'.".

While reinstalling I added a 2Gb /boot partition before the root (/)
partition, it worked and was able to boot into the installed system.

TL;DR: Grub failed on 4Tb / partition *in BIOS mode*, worked when a
/boot partition was created.

[1]: https://wiki.zentyal.org/wiki/Installation_Guide#Zentyal_Installer

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

Title:
  Install to 3TB disk fails with "attempt to read or write outside of
  disk" error on reboot

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

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

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

2017-10-26 Thread alpreston
1.0.27-1~experimental2ubuntu2 doesn't help - i still get the "libsane
not available" error message when trying to install iscan-
gt-x820-bundle-1.0.1.x64.deb. My Epson V600 is still not accessible.

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

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

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

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

[Bug 1727940] [NEW] re-installing kodi failed due to permssions in writing to addon.xml

2017-10-26 Thread Davie Robertson
Public bug reported:

sudo apt remove kodi
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  fonts-noto-hinted fonts-roboto-hinted kodi-bin kodi-data 
kodi-visualization-spectrum libcec4 libcrossguid0 libjs-iscroll libmicrohttpd12 
libnfs8 python-imaging
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED
  kodi
0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade.
After this operation, 60.4 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 205125 files and directories currently installed.)
Removing kodi (2:17.3+dfsg1-3) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Processing triggers for bamfdaemon (0.5.3+17.10.20170810-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
davidr@davidr-ASM100:~$ sudo apt install kodi
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  kodi-repository-kodi
The following NEW packages will be installed
  kodi kodi-repository-kodi
0 to upgrade, 2 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/43.8 kB of archives.
After this operation, 152 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Selecting previously unselected package kodi.
(Reading database ... 205115 files and directories currently installed.)
Preparing to unpack .../kodi_2%3a17.3+dfsg1-3_amd64.deb ...
Unpacking kodi (2:17.3+dfsg1-3) ...
Preparing to unpack .../kodi-repository-kodi_2%3a17.3+dfsg1-3_all.deb ...
Unpacking kodi-repository-kodi (2:17.3+dfsg1-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/kodi-repository-kodi_2%3a17.3+dfsg1-3_all.deb 
(--unpack):
 trying to overwrite '/usr/share/kodi/addons/repository.xbmc.org/addon.xml', 
which is also in package kodi-data 2:17.3+dfsg1-3
Errors were encountered while processing:
 /var/cache/apt/archives/kodi-repository-kodi_2%3a17.3+dfsg1-3_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Oct 27 10:17:10 2017
ErrorMessage: trying to overwrite 
'/usr/share/kodi/addons/repository.xbmc.org/addon.xml', which is also in 
package kodi-data 2:17.3+dfsg1-3
InstallationDate: Installed on 2017-05-06 (173 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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: 
trying to overwrite '/usr/share/kodi/addons/repository.xbmc.org/addon.xml', 
which is also in package kodi-data 2:17.3+dfsg1-3
UpgradeStatus: Upgraded to artful on 2017-10-23 (3 days ago)

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

Title:
  re-installing kodi failed due to permssions in writing to addon.xml

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

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

[Bug 1727331] Comment bridged from LTC Bugzilla

2017-10-26 Thread bugproxy
--- Comment From sthou...@in.ibm.com 2017-10-27 02:13 EDT---
We need official build ..

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

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

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

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

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

2017-10-26 Thread Daniel van Vugt
Thanks. Perhaps we jumped the gun though...

On your login screen do you see two options "Ubuntu" and "Ubuntu on
Xorg", or only one?

It looks like you might be experiencing a problem with Xorg judging by
comment #4:

Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
flip queue failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
Page flip failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): 
present flip failed
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
flip queue failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
Page flip failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): 
present flip failed
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
flip queue failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
Page flip failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): 
present flip failed

** Bug watch added: GNOME Bug Tracker #789540
   https://bugzilla.gnome.org/show_bug.cgi?id=789540

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=789540
   Importance: Unknown
   Status: Unknown

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

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

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1723055] Re: Artful: Fix FTBS on test-rebuild-20170922

2017-10-26 Thread ChristianEhrhardt
Builds fine now, no further breakage seen.
The dep8 test sof tgt and iscsi are good to test and they seem still happy as 
well - so set verified.

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

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

Title:
  Artful: Fix FTBS on test-rebuild-20170922

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

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

[Bug 1727877] [NEW] AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop

2017-10-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This is a new laptop HP 15-BS576TX which has Intel HD 620 Integrated
graphics and a 2GB AMD Radeon 520 Graphics card running on Ubuntu
wayland session. Intel integrated graphics is only  listed, if you check
gnome-control-centre details page (See attached images). But, if I run
[code]DRI_PRIME=1 gnome-control-centre[/code] to reach details info it
shows "AMD HAINAN" as the only card available. So, it seems the Xwayland
session not automatically managing hybrid graphics (shifts to dedicated
card for resource hungry apps). What I expected is Gnome control centre
will list both the cards.

tl;dr: AMD/Intel hybrid graphics not configured correctly in wayland.
Dedicated Card is not showing up in system informations.

Here are the details: lspci -knnn shows that AMD Radeon 520 card is
detected:

01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun 
XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev 83)
Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 
M330 / M430] [103c:832b]
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

and Integrated Intel HD 620 graphics:

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02)
Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b]
Kernel driver in use: i915
Kernel modules: i915

lshw -C video
  *-display

   description: VGA compatible controller
   product: HD Graphics 620
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 02
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:128 memory:b000-b0ff memory:a000-afff 
ioport:6000(size=64) memory:c-d
  *-display
   description: Display controller
   product: Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:01:00.0
   version: 83
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi bus_master cap_list rom
   configuration: driver=radeon latency=0
   resources: irq:129 memory:9000-9fff memory:b120-b123 
ioport:5000(size=256) memory:b124-b125

Now, if I run any app with DRI_PRIME=1 it works and shows below info:

:~$ DRI_PRIME=1 glxinfo |grep -i Opengl*
OpenGL vendor string: X.Org
OpenGL renderer string: AMD HAINAN (DRM 2.50.0 / 4.13.0-16-generic, LLVM 5.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2
OpenGL core profile shading language version string: 4.50

So, I assumed Radeon 520 is working fine. Then, noticed that there is no 
mention of gallium 3d? 
I see that there is amdgpu driver module also loaded. From the list, R520 card 
seems to be supported by the radeon driver.

lsmod |grep radeon
radeon   1470464  0
ttm94208  2 amdgpu,radeon
i2c_algo_bit   16384  3 amdgpu,radeon,i915
drm_kms_helper167936  3 amdgpu,radeon,i915
drm   356352  28 amdgpu,radeon,i915,ttm,drm_kms_helper

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.5-0ubuntu2
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
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Oct 27 03:50:59 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b]
   Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 
M330 / M430] [103c:832b]
InstallationDate: Installed on 2017-10-22 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: HP HP Laptop 15-bs0xx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=50b901ea-f329-4a72-ae11-f7203ae53c2e ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 832B
dmi.board.vendor: HP
dmi.board.version: 23.38
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.38:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-bs0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
ver

[Bug 1724857] Re: Artful: Fix FTBS on test-rebuild due to gcc-7

2017-10-26 Thread ChristianEhrhardt
Builds fine now, no further breakage seen (I'm not the best tester, but
this was mostly for the FTBFS anyway) - set verified.

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

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

Title:
  Artful: Fix FTBS on test-rebuild due to gcc-7

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

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

[Bug 1719196] Re: [arm64 ocata] newly created instances are unable to raise network interfaces

2017-10-26 Thread ChristianEhrhardt
Thanks for the FYI Brian.
I see it in pending-SRUs as it should be.
I added the -needed tags to be "correct".

@Andrew/Sean - could you test proposed and set verified then (assuming
it works like the ppa did)


Odd - this really seems to hit everything, not only LP timeouts.
There are also dep8 regressions listed on systemd which make no sense in 
relation to the fix.
The test history on arm is borked since February [1], so I ask you to override 
and ignore that.
On s390x it at least works sometimes, but the log [2] doesn't look much better, 
but there at least it hits a different issue than before - I'm retriggering 
this for now - but likely ask to ignore that as well - but I'll take a look at 
the retry first.


[1]: http://autopkgtest.ubuntu.com/packages/s/systemd/zesty/armhf
[2]: http://autopkgtest.ubuntu.com/packages/s/systemd/zesty/s390x

** Tags added: verification-needed verification-needed-zesty

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

Title:
  [arm64 ocata] newly created instances are unable to raise network
  interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1719196/+subscriptions

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

[Bug 19066] Re: Pango-enabled firefox breaks MathML support

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

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 2005-03-05T13:53:40+00:00 Joao wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 
Firefox/1.0

Description of problem:
Install the recommended fonts for MathML 
(http://www.mozilla.org/projects/mathml/fonts/)

Compare display with firefox 1.0.1 installed as suggested in
http://fedoranews.org/tchung/firefox

Version-Release number of selected component (if applicable):
firefox-1.0.1-1.3.1, firefox-1.0.1-1.3.2

How reproducible:
Always

Steps to Reproduce:
1. Install the recommended fonts for MathML 
(http://www.mozilla.org/projects/mathml/fonts/)
2. Access http://www.mozilla.org/projects/mathml/demo/texvsmml.xhtml or some 
other MathML test page


  

Actual Results:  Alignement all wrong

Expected Results:  Compare display with firefox 1.0.1 installed as suggested in
http://fedoranews.org/tchung/firefox

Additional info:

Local fonts for MathML include
Acrobat Reader PS fonts
Mathematica 4.1 tt
LaTeX fonts

This font set works for Mozilla and other Firefox releases. Additional
details if requested.

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


On 2005-03-24T09:46:17+00:00 Joao wrote:

Now it is also present on mozilla-1.7.6-1.3.2 under FC3

It is _not_ present in 
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.6/contrib/mozilla-i686-pc-linux-gnu-1.7.6-gtk2+xft.tar.gz

So it seems to be introduced by Fedora packaging

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


On 2005-03-24T10:11:19+00:00 Joao wrote:

I have changed severity to high as this potentially messes up any MathML site
accessed from Fedora.

Screenshots are available at

the good:
http://www.math.ist.utl.pt/~jmatos/CapturaEcra-13.png

the ugly (the latest mozilla-1.7.6-1.3.2):
http://www.math.ist.utl.pt/~jmatos/CapturaEcra-14.png


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


On 2005-03-28T19:54:52+00:00 Matt wrote:

This seems to be due to Pango, as is assumed do to the timing, since it was
enabled default around the beginning of March.  If you run:

> MOZ_DISABLE_PANGO=1 firefox

you can view all the MathML sites correctly (albeit with that annoying Symbol
dialog, i.e., #133709).  A ye olde post here:

http://mail.gnome.org/archives/gtk-i18n-list/2003-February/msg00042.html

seems to say that Pango and MathML (Mango?) don't play nicely.  Another out
there says that Blizzard was working on a corrolary to this problem:

http://lists.gnu.org/archive/html/lilypond-devel/2004-05/msg00084.html

So, I guess you can't have both worlds right now.  I suppose a "Disable Pango if
you want to read math" statement is needed in rather BOLD letters at Moz/Firefox
Fedora pages/release notes.

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


On 2005-03-29T00:02:10+00:00 Joao wrote:

(In reply to comment #3)
> 
> So, I guess you can't have both worlds right now.  I suppose a "Disable Pango 
> if
> you want to read math" statement is needed in rather BOLD letters at 
> Moz/Firefox
> Fedora pages/release notes.

This is an update to a release (FC3) for which MathML support existed so release
notes wouldn't make much sense. Breaking upstream features in an update does not
seem a good policy anyway...

>From the point of view someone writing MathML pages this situation is a total
mess. It would be acceptable, but a pain, if one could detect from "Mozilla/5.0
(X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Fedora/1.7.6-1.3.2" that
"This Mozilla MathML rendering has been broken for the sake of pango by your
Linux distribution. Get a copy from mozilla.org". Come on: one can do something
similar with IE with or without MathPlayer but not with Mozilla/Firefox with or
without MathML support?!

If the maintainer ever reads please consider (from the SPEC file I gather it was
not intentional):
-- reinstating MathML support in an update for FC3;
-- making lack of MathML support for FC4 or FC5 and later detectable by dynamic
pages;

or get pango vs. MathML fixed!

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


On 2005-03-29T00:23:30+00:00 Warren wrote:

*

[Bug 216049] Re: window list restore to current workspace does not work

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=484842.

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


On 2009-02-10T09:05:13+00:00 Cao wrote:

Description of problem:
Window List cannot restore the windows in another workspace 
to current workspace.


Version-Release number of selected component (if applicable):
gnome-panel-2.25.90-1.fc11


How reproducible:
100% reproducible.


Steps to Reproduce:
1. make sure there is a window list on the panel.
2. set the properties of the Window List by right click on the 
left part of the window list and choose 'Preferences'.
3. set 'Window list content' to 'show windows from all workspaces'.
4. set 'restoring minimized windows' to 'restore to current workspace'
5. open gedit in workspace 2, minimize gedit. and go to worspace 1.
6. left click the icon of gedit in the window list on the panel.
  

Actual results:
the program (gedit) cannot be restored. the lable (or icon) of program, 
which is in the window list, just blinks.


Expected results:
the program (gedit) can be restored in the current workspace.


Additional info:
uname -r 

2.6.29-0.96.rc3.git12.fc11.i586


Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/7


On 2009-02-13T06:24:11+00:00 Matthias wrote:


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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/9


On 2009-02-13T06:59:50+00:00 Matthias wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/10


On 2009-06-09T11:12:15+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/metacity/+bug/216049/comments/13


On 2010-01-06T02:02:19+00:00 Christopher wrote:


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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/216049/comments/17


** Changed in: gnome-panel (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/216049

Title:
  window list restore to current workspace does not work

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

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

[Bug 172937] Re: SQUASHFS error while booting from live cd

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=432549.

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


On 2008-02-12T19:18:27+00:00 Peter wrote:

Description of problem:
Fails on install

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

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


On 2008-02-12T19:18:27+00:00 Peter wrote:

Created attachment 294692
anaconda dump

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


On 2008-02-12T21:53:54+00:00 Jeremy wrote:

Did you verify your media?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/comments/10


On 2008-02-13T00:56:12+00:00 Peter wrote:

several times and every time it verified ok

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/comments/11


On 2008-02-16T18:18:53+00:00 Chris wrote:

Reassigning to kernel based on the following error messages, which are
indicative of driver problems, hardware problems, or media problems (which seem
to be ruled out by running media check):

<3>SQUASHFS error: zlib_inflate returned unexpected result 0xfffd, srclength
65536, avail_in 630, avail_out 65536
<3>SQUASHFS error: sb_bread failed reading block 0xd7a1
<3>SQUASHFS error: Unable to read page, block 35e2988, size 5d76

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/comments/12


On 2008-02-18T12:34:39+00:00 Peter wrote:

Some hardware stats : Compaq Proliant 1600, 2x 500Mhz, 1Gb Memory, Smart Array 
3200 Raid Controler, 1 floppy drive, 1 DVD IDE drive.

Tried Fedora 7 installs ok only mouse is not working, Fedora 3 installs ok 
mouse works, will test other versions after download.

Fedora-8-i386-DVD.iso - not working when English for language is used Keyboard 
choice crash, Dutch language partitioning is reached.

F-7-i386-DVD.iso - during install no mouse.

FC3-i386-disc1.iso - floppy does not mount during install.


Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/comments/13


On 2008-05-02T15:19:30+00:00 Martin wrote:

Also met this on a Tyan motherboard with Intel 5000 chipset.

F8 i386 & x86_64 both fail.

F9 i386 pre-release does work.

dmidecode being attached here for reference.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/comments/19


On 2008-05-02T15:26:44+00:00 Martin wrote:

Created attachment 304393
dmi decode from TYAN-Tempest-i5000VS-S5372-LC/LH

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/comments/20


On 2008-11-26T09:47:53+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/linux/+bug/172937/comments/35

-

[Bug 160944] Re: [xpdf] multiple security vulnerabilities

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=345101.

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-10-22T12:37:39+00:00 Tomas wrote:

Alin Rad Pop of the Secunia Research discovered a vulnerability in
xpdf/Stream.cc code:

An array indexing error exists within the "DCTStream::readProgressiveDataUnit()"
method in xpdf/Stream.cc. This can be exploited to corrupt memory via a
specially crafted PDF file.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/0


On 2007-10-26T06:56:09+00:00 Tomas wrote:

Created attachment 238491
xpdf-3.02pl2 first draft from Derek B. Noonburg addressing 
CVE-2007-{4352,5392,5393}

Comments from Derek:

The fixes for the first two bugs (in DCTStream) are pretty
straightforward.

The CCITTFaxStream inner loop code has been rewritten (because I was
unhappy with the design, and it was resulting in too many problems).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/1


On 2007-11-07T16:27:39+00:00 Josh wrote:

This is now public:
http://marc.info/?l=full-disclosure&m=119445179723160&w=2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/2


On 2007-11-08T06:03:33+00:00 Fedora wrote:

cups-1.3.4-2.fc8 has been pushed to the Fedora 8 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/3


On 2007-11-08T08:38:17+00:00 Tomas wrote:

KDE security advisory with official patches for kdegraphics and koffice:

http://www.kde.org/info/security/advisory-20071107-1.txt


Reply at: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/4


On 2007-11-09T10:33:38+00:00 Tomas wrote:

Official xpdf patch is available on xpdf upstream page:

http://www.foolabs.com/xpdf/download.html
ftp://ftp.foolabs.com/pub/xpdf/xpdf-3.02pl2.patch


Reply at: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/7


On 2007-11-09T23:51:51+00:00 Fedora wrote:

cups-1.2.12-7.fc7 has been pushed to the Fedora 7 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/8


On 2008-02-08T08:17:24+00:00 Fedora wrote:

poppler-0.5.4-8.fc7 has been submitted as an update for Fedora 7

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/12


On 2008-02-13T05:19:45+00:00 Fedora wrote:

poppler-0.5.4-8.fc7 has been pushed to the Fedora 7 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/13


On 2008-02-13T15:00:40+00:00 Fedora wrote:

poppler-0.5.4-8.fc7 has been pushed to the Fedora 7 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/14


On 2008-02-13T15:09:43+00:00 Fedora wrote:

poppler-0.5.4-8.fc7 has been pushed to the Fedora 7 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/160944/comments/15


On 2008-02-15T15:01:19+00:00 Red wrote:

This issue was addressed in:

Red Hat Enterprise Linux:
  cups:
http://rhn.redhat.com/errata/RHSA-2007-1021.html
http://rhn.redhat.com/errata/RHSA-2007-1022.html
  gpdf:
http://rhn.redhat.com/errata/RHSA-2007-1025.html
  poppler:
http://rhn.redhat.com/errata/RHSA-2007-1026.html
  xpdf:
http://rhn.redhat.com/errata/RHSA-2007-1029.html
http://rhn.redhat.com/errata/RHSA-2007-1030.html
  tetex:
http://rhn.redhat.com/errata/RHSA-2007-1027.html
  kdegraphics:
http://rhn.redhat.com/errata/RHSA-2007-1024.html

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

[Bug 487362] Re: xorg is eating up memory

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=560668.

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-01T15:09:26+00:00 Alan wrote:

Description of problem:
[RHEL5.3] Xorg Consumes all memory

This problem is across a number of systems, about 15 machines, All use KDE.
It is possible to make some changes on some systems.

What we found out so far is that the machine with the new nVidia driver
consumed all memory again.

Machines with Vesa drivers are OK so far but the user of that
workstation claims that it usually takes some time till it the
phenomenon occurs.

This case is about one customer who has some sites worldwide.
All sites run with same configuration under Sun ULTRA20 M2 Workstation,with 
nVidia Video card.

About 15 of his systems experience this phenomenon worldwide.
We tried on one machine to update to a newer nVidia driver, and on another 
machine to use Vesa driver.

It is very problematic for the customer to work with Vesa drivers since
he needs to use 1600x1200 screen resolution, and we couln't run this
system with such resolution using Vesa driver.

After analysing his sar data of workstation with nVidia driver we found
out that Xorg begins to consume alot of memory when the user is not
working during evening hours.


We configured one of the problematic machines to use Vesa drivers,today on that 
machine Xorg consumes 1.4GB of memory.

We configured another machine to use Vesa drivers with an ATI card to make sure 
that nVidias drivers cause consumption of all memory.
(as mentioned previously, we couldn't use 1200x1600 resolution with Vesa driver 
and nVidia card)

In this case we've already seen that the problem reproduces also with
ATI video card using Redhat's VESA drives, so this is not video card
driver related problem.

The customer is currently preparing to deploy RHEL 5 within their organization.
The mentioned problem also reproduces on RHEL 4 systems.


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


How reproducible:

It takes a very long time to see this problem
One thought about this bug:

 "how does xorg manage memory for quitting application" question:

12:42 < ofourdan|lunch> pamadio: you can always tell the X server to retain the 
resources, but that's for very specific use and hardly ever used  - But if you 
want you can :)
12:43 < ofourdan|lunch> one of the use is to set a pixmap to the root window, 
the app that sets the pixmaps needs to specify thatthe pixmap must not be freed 
once the app terminates
12:44 < ofourdan|lunch> another use is to make an app to self-recover from a 
network disconnection. Although this is theorically possible, I am yet to find 
an apps that implement this :)

12:54 < ofourdan> pamadio: see "man XSetCloseDownMode"
12:55 < ofourdan> pamadio: by default all connections start in DestroyAll mode.

>From alanm: I've never seen this in practice either.

Steps to Reproduce:

Customer s/w has to run for a very long time before this problem is seen
  
Actual results:
X.org Server consumes all memory

Expected results:

Normal operation of Xserver


Notes from SEG

This looks to be an issue that was supposed to have been fixed in the
VESA driver

https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=81559
https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=83772

The problem here is that there wasn't a reproducer. Since it took so
long for this problem to reappear I gather that there isn't an easy way
to reproduce this ?

I could create a BZ for this but I know that engineering will want to
have some way of reproducing this. This looks to me to be a slow memory
leak and without some way of reproducing this I don't know if they will
do anything about this.

The earlier IT's seem to indicate that this is a leak that occurs when
closing a client so I would ask the customer if this is something that
happens over a long period of time or does the memory consumption occur
all of a sudden ?

I also don't see any indication of any long running applications that
would eat up memory so it looks to be a VESA driver problem where memory
isn't being released when a client closes down.

Let me know as soon as you can and I'll create a BZ for this but I'm
really not sure if engineering will do much about it. The best I can do
is pass it on to them and let them decide.

1) given where we are in the development cycle with RHEL 4. It's pretty late in 
the cycle.
2) the fact that these are U4 systems. I know that they will want to know why 
the customer systems have not been updated to U8.
3) the lack of a reproducer.

While there have been other reporters of similar behaviour from a couple
of othe cus

[Bug 502076] Re: bzr-handle-patch doesn't like patch files containing "diff" lines before each patch

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

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-21T20:50:38+00:00 Felix wrote:

abrt 1.0.3 detected a crash.

How to reproduce: Try to open the patch file from 
https://mozilla-plugin.forge.funambol.org/servlets/TrackerDownload/remcurreport/true/template/ViewAttachment.vm/attachid/453/filename/0001-fix-preferences.patch
 and you will get the attached crash.
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/bzr-handle-patch 
/home/fm/0001-fix-preferences.patch
component: bzr-gtk
executable: /usr/bin/bzr-handle-patch
kernel: 2.6.31.9-174.fc12.i686.PAE
package: bzr-gtk-0.97.0-2.fc12
uuid: 4b0c976f

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/1


On 2010-01-21T20:50:41+00:00 Felix wrote:

Created attachment 386005
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/2


On 2010-01-22T04:25:45+00:00 Toshio wrote:

This has been filed upstream before.  Putting upstream bug# in.
However, this looks like a bug in bzr code rather than bzr-gtk.  Looking
further.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/3


On 2010-01-22T11:12:03+00:00 Toshio wrote:

I'm able to fix this bug with a patch to bzr's patch handling to make it
more lenient.  (Currently, that patch handling code doesn't accept
"junk" before and after the individual patches within a file.).  Will
attach a patch.

hno, do you know if the patches.py code is meant to handle any patch
file?  If so, this is appropriate.  If it's really only meant to handle
bzr-generated patches, then bzr-gtk is misusing the bzrlib code.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/6


On 2010-01-22T11:12:50+00:00 Toshio wrote:

Created attachment 386120
Patch to make bzr's patch handling more lenient

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/7


On 2010-02-08T16:55:34+00:00 Toshio wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/12


On 2010-03-16T20:24:26+00:00 Damian wrote:


How to reproduce
-
1. open the following url in firefox:
http://www.splitted-desktop.com/~gbeauchesne/libva/patches/
2. click on the link 033_g45_add_rgba_subpic.patch 
3. open the file with Baazar (crash is reproducible in 100%)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/14


On 2010-04-13T13:18:48+00:00 Toshio wrote:

My patch to bzr to fix this is in bzr-2.2b1.  We could safely backport
it to current bzr packages.  Also need a patch to bzr-gtk to turn this
functionality on.  I have a patch for that linked  to the upstream bug
report but upstream needs it cconditionalized on having a new enough
bzr.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/16


On 2010-04-13T17:09:22+00:00 Toshio wrote:

New fix for bzr-gtk submitted upstream:
https://code.launchpad.net/~toshio/bzr-gtk/handle-patch-
dirty/+merge/23330

If accepted, we'll likely want to backport both the bzr and bzr-gtk
fixes back to F-12 and F-13.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/18


On 2010-07-30T19:37:22+00:00 Damian wrote:

Package: bzr-gtk-0.97.0-4.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


How to reproduce
-
1. Add patch as an attachment in the thunderbird program
2. Double click the patch to see its content
3.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/19


On 2010-10-11T18:18:21+00:00 Damian wrote:

Package: bzr-gtk-0.98.0-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


Comment
-
Just tried to open a C source file.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/502076/comments/21


On 2010-11-04T00:18

[Bug 246659] Re: Backuppc no compression when change topdir

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=473944.

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-01T15:17:20+00:00 Filipe wrote:

Created attachment 325239
Patch for lib/BackupPC/Lib.pm

Description of problem:
Changing TopDir in config file does not affect pool and cpool, BackupPC still 
thinks those are under the default directory /var/lib/BackupPC


Version-Release number of selected component (if applicable):
3.1.0-3.fc10


How reproducible:
Every time.


Steps to Reproduce:
1. Set $Conf{TopDir} = '/whatever'; in config.pl
2. Create /whatever with the default BackupPC directories (pool, cpool, pc, 
trash) and right permissions.
3. Run a backup.
  

Actual results:
cpool will be empty, and this will be the output in /var/log/BackupPC/LOG:
2008-11-29 10:23:40 BackupPC_link got error -4 when calling 
MakeFileLink(/whatever/pc/xxxname/0/f%2fetc/fDIR_COLORS, 
a1fbdaecae5425dc9d24653e5c87a22e, 1)


Expected results:
The files in cpool would be correctly created.


Additional info:
This mailing list post has a patch for the problem:
http://sourceforge.net/mailarchive/message.php?msg_name=20080808032558.GG13869%40gratch.parplies.de

I'm attaching the same patch here.

I applied this patch to an already installed BackupPC from the Fedora
RPM, and after that it worked as supposed to.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/246659/comments/1


On 2008-12-07T12:03:33+00:00 Johan wrote:

I understand the problem...

But these patch is not included upstream, and seems not well tested...

I'll keep this in mind, but won't include it for now, I'd like to have
more come backs before.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/246659/comments/2


On 2008-12-07T15:52:53+00:00 Filipe wrote:

The same problem has been reported several other times in the backuppc-devel 
list:
http://sourceforge.net/mailarchive/forum.php?thread_name=48CEEE9A.3080106%40resheteva.lan&forum_name=backuppc-devel
http://sourceforge.net/mailarchive/forum.php?thread_name=20080917151648.GC22362%40localhost.localdomain&forum_name=backuppc-devel
http://sourceforge.net/mailarchive/forum.php?thread_name=491B3BD2.4080301%40gmail.com&forum_name=backuppc-devel
http://sourceforge.net/mailarchive/forum.php?thread_name=4921C17B.1050905%40resheteva.lan&forum_name=backuppc-devel

The problem has been reported to the list since August, but so far the
developers have not said anything about it. If you have another way of
contacting them, please do, since this is a problem that should be
simple to solve.

There is an alternative patch suggested by a Debian user, but it's
setting the variables on the wrong place, inside the function that reads
the config file instead of after calling that function where TopDir may
potentially be changed.

If you look at the patch, it's extremely straighforward, all it's doing
is setting CPool and Pool *after* resetting TopDir instead of before.
You can also do the steps on the reported bug and verify that it indeed
happens, and cpool will be empty. In fact, you will have a directory
structure created under /var/lib/backuppc, no matter what you set TopDir
to.

There is also the Debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495504

But there they took a ridiculous approach of saying that if you want to
do that, you should use a symbolic link in /var/lib/backuppc to wherever
you want to move it, but that is ridiculous since it breaks the
installed RPM (rpm --verify will point that out), and also, if that's
the case, the possibility to redefine TopDir should be removed from the
config.

I still think you should go ahead and apply the patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/246659/comments/3


On 2008-12-07T18:08:53+00:00 Johan wrote:

The symlink is what I've used for long times, it was not possible to
change the backup dir in BackupPC 2.x ; and I've kept this method.

But I'm okay, I'll take a look to push the new patched version on
testing this week ; the patch is very simple, thanks for it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/246659/comments/4


On 2008-12-10T22:39:32+00:00 Filipe wrote:

Hi,

Please see this message by Paul Mantz from the backuppc-devel mailing list:
http://sourceforge.net/mailarchive/forum.php?thread_name=42f28fe0812101410v5d625b3g68693c28e1a8b258%40mail.gmail.com&forum_name=backuppc-devel

[Bug 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends

2017-10-26 Thread Bug Watch Updater
** Changed in: bluez (Fedora)
   Status: Unknown => Confirmed

** Changed in: bluez (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/446657

Title:
  Bluetooth's on/off status doesn't update from the SetProperty D-Bus
  method that bluetoothd sends

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

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

[Bug 317587] Re: posix apis unreliable on files mounted over gvfs, e.g. truncate, open, causes OpenOffice.org to fail to save

2017-10-26 Thread Bug Watch Updater
** Changed in: gvfs (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/317587

Title:
  posix apis unreliable on files mounted over gvfs, e.g. truncate, open,
  causes OpenOffice.org to fail to save

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

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

[Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

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=546179.

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-10T10:20:34+00:00 Glen wrote:

abrt 1.0.0 detected a crash.

How to reproduce
-
1.  Create a rectangle
2.  Click with the text tool on top of the rectangle you've created.

Comment: Clicking with text tool on a rectangle causes crash.
Attached file: backtrace
cmdline: inkscape
component: inkscape
executable: /usr/bin/inkscape
kernel: 2.6.31.6-162.fc12.x86_64
package: inkscape-0.47-0.17.pre4.20091101svn.fc12
rating: 3
reason: Process was terminated by signal 6

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/42


On 2009-12-10T10:20:37+00:00 Glen wrote:

Created attachment 377421
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/43


On 2009-12-13T04:55:46+00:00 Máirín wrote:

Hi Glen!

Thank you very much for your bug report.

This bug looks like a bug we've seen a lot of users experience lately. I
believe it is caused by a bug in the gtk2 package, not Inkscape.

We have a fix for the text-tool issue in Inkscape addressed by an update
to gtk2 which I believe will resolve your problem (we've had several
testers confirm it resolved text tool crashes in Inkscape for them)

To get the fix, run the following command as root:

yum update gtk2 --enablerepo=updates-testing

Let me know how it goes! And thanks again for the bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/44


On 2009-12-13T21:07:17+00:00 Glen wrote:

Yep, fixed me right up.  Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/45


On 2009-12-15T16:47:00+00:00 Karel wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/49


On 2009-12-15T18:48:24+00:00 Joel wrote:

The gtk2 update fixed the problem for me, too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/50


On 2009-12-22T12:12:52+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/51


On 2009-12-22T12:12:58+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/52


On 2009-12-22T12:13:30+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/53


On 2009-12-22T12:13:41+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/54


On 2009-12-22T12:13:51+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/55


On 2009-12-22T12:15:24+00:00 Lubomir wrote:

GTK2 was fixed. Big thanks to everyone involved in reporting/triaging.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/56


On 2009-12-22T12:31:55+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/57


On 2009-12-22T12:32:11+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/58


On 2010-02-08T00:04:46+00:00 Máirín wrote

[Bug 304623] Re: ssh client disconnected after successful login

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=466818.

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


On 2008-10-13T20:33:20+00:00 Jan wrote:

Description of problem:
After a recent upgrade I am no longer able to log in to the embedded devices 
like HP ProCurve ethernet switches or APC master switches - the remote device 
just closes the connection after receiving the password.

Version-Release number of selected component (if applicable):
openssh-server-5.1p1-2.fc9.i386
openssh-clients-5.1p1-2.fc9.i386
openssh-askpass-5.1p1-2.fc9.i386
openssh-5.1p1-2.fc9.i386

How reproducible:
100 %

Steps to Reproduce:
1. install the above version of openssh
2. try to log in to the remote device using password
  
Actual results:
connection is closed by the remote side. APC master switches do not
say anything, with HP ProCurve ssh says the following:

Received disconnect from XXX: 2: protocol error: rcvd type 80

Expected results:
Command-line prompt on HP ProCurve (tested 2650, 2848, 4300), menu screen on
APC (tested version 7920).

Additional info:
Downgrading to 5.0p1-1.fc9 fixes the problem. The problem happens at least on 
i386 and x86_64.

I will attach the two ssh -v sessions (one with 5.0p1-1.fc9, the other
one with 5.1p1-2.fc9).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/0


On 2008-10-13T20:41:04+00:00 Jan wrote:

Created attachment 320228
ssh -v with 5.0p1 and 5.1p1 to the APC master switch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/1


On 2008-10-14T11:17:09+00:00 Tomas wrote:

Do you see anything suspicious in ssh -vvv session with the 5.1p1?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/2


On 2008-10-14T16:34:06+00:00 Jan wrote:

Created attachment 320323
ssh -vvv to the APC master switch (5.0p1)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/3


On 2008-10-14T16:37:56+00:00 Jan wrote:

Created attachment 320325
ssh -vvv to the APC master switch (5.1p1)

OK, here you are. Running diff -u on the above two files did not show
anything I can make sense of :-)

[Meta: is it just me, or is Bugzilla these days _awfully_ slow? Just
opening the bug page took about half a minute here, the same for adding
attachments and every other page]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/4


On 2008-10-17T09:31:39+00:00 Fedora wrote:

openssh-5.1p1-3.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/openssh-5.1p1-3.fc9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/5


On 2008-10-17T09:35:51+00:00 Jan wrote:

Works for me (tested x86_64 arch only, against both HP and APC boxes).
Thanks for solving the problem this fast!

[Meta from the comment #4 stil holds, bugzilla is still very slow here]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/6


On 2008-10-17T10:43:57+00:00 Tomas wrote:

Upstream solved it just today, not me :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/7


On 2008-11-07T02:51:38+00:00 Fedora wrote:

openssh-5.1p1-3.fc9 has been pushed to the Fedora 9 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/304623/comments/8


** Changed in: openssh (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/304623

Title:
  ssh client disconnected after successful login

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

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

[Bug 251065] Re: VM performance numbers should be relative to the guest, not the host

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

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-10T20:09:34+00:00 Daniel wrote:

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

Imagine a host with 4 CPUs and 4 GB of RAM. Imagine a guest with one CPU
and 512 MB of RAM. If it maxes out its resources, it'll show as using
25% CPU and 12.5% of RAM. This is relative to the host, but that's not
really meaningful when you're looking at the guest. Instead, those
numbers should be relative to the guest, so it'd be 100% and 100%. As a
special case, when the startup and maximum RAM are the same, it should
just show the amount (512 MB) because a constant 100% isn't really
useful.

The numbers on the main virt-manager screen (as opposed to on the detail
of a specific host) are harder to define. I can make a case for both
sets of numbers. I would argue that both should be available (in
separate columns), but the relative-to-guest columns should be hidden by
default.

Reproducible: Always

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


On 2011-07-12T13:58:47+00:00 Cole wrote:

The memory issues are gone in recent virt-manager, since we don't really
show a graph for it anymore (since historically we haven't had _actual_
memory usage statistics from inside the guest, so it wasn't all that
useful to show a graph here).

The CPU issue is tracked in other bugs, so closing as a dup

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

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


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

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

Title:
  VM performance numbers should be relative to the guest, not the host

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

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

[Bug 368903] Re: apachetop 0.12.6-9 report buffer overflow all the time

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=446199.

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-13T14:00:05+00:00 Robert wrote:

Description of problem:
Please note, that the following problem also applies to Fedora 9.

robert@tux:~ > apachetop -f /var/log/httpd/access_log
*** buffer overflow detected ***: apachetop terminated
=== Backtrace: =
/lib/libc.so.6(__fortify_fail+0x48)[0x3cec48]
/lib/libc.so.6[0x3ccd40]
/lib/libc.so.6[0x3cd4a8]
apachetop(__gxx_personality_v0+0x46d)[0x80496a5]
apachetop[0x804a2d6]
/lib/libc.so.6(__libc_start_main+0xe6)[0x2ee5d6]
apachetop(__gxx_personality_v0+0xd9)[0x8049311]
=== Memory map: 
0011-0012c000 r-xp  68:02 2965506/lib/ld-2.8.so
0012c000-0012d000 r-xp 0001c000 68:02 2965506/lib/ld-2.8.so
0012d000-0012e000 rwxp 0001d000 68:02 2965506/lib/ld-2.8.so
0012e000-0012f000 r-xp 0012e000 00:00 0  [vdso]
0012f000-0016 r-xp  68:02 2965525/lib/libreadline.so.5.2
0016-00164000 rwxp 00031000 68:02 2965525/lib/libreadline.so.5.2
00164000-00165000 rwxp 00164000 00:00 0
00165000-00186000 r-xp  68:02 2965732/lib/libncurses.so.5.6
00186000-00187000 rwxp 0002 68:02 2965732/lib/libncurses.so.5.6
00187000-001b r-xp  68:02 2965518/lib/libpcre.so.0.0.1
001b-001b1000 rwxp 00028000 68:02 2965518/lib/libpcre.so.0.0.1
001b1000-00296000 r-xp  68:02 393288 /usr/lib/libstdc++.so.6.0.10
00296000-0029a000 r-xp 000e4000 68:02 393288 /usr/lib/libstdc++.so.6.0.10
0029a000-0029b000 rwxp 000e8000 68:02 393288 /usr/lib/libstdc++.so.6.0.10
0029b000-002a1000 rwxp 0029b000 00:00 0
002a1000-002c8000 r-xp  68:02 2965678/lib/libm-2.8.so
002c8000-002c9000 r-xp 00026000 68:02 2965678/lib/libm-2.8.so
002c9000-002ca000 rwxp 00027000 68:02 2965678/lib/libm-2.8.so
002ca000-002d7000 r-xp  68:02 2965617
/lib/libgcc_s-4.3.0-20080428.so.1
002d7000-002d8000 rwxp c000 68:02 2965617
/lib/libgcc_s-4.3.0-20080428.so.1
002d8000-0043b000 r-xp  68:02 2965520/lib/libc-2.8.so
0043b000-0043d000 r-xp 00163000 68:02 2965520/lib/libc-2.8.so
0043d000-0043e000 rwxp 00165000 68:02 2965520/lib/libc-2.8.so
0043e000-00441000 rwxp 0043e000 00:00 0
00441000-00457000 r-xp  68:02 2965736/lib/libtinfo.so.5.6
00457000-0045a000 rwxp 00015000 68:02 2965736/lib/libtinfo.so.5.6
0045a000-0045d000 r-xp  68:02 2965644/lib/libdl-2.8.so
0045d000-0045e000 r-xp 2000 68:02 2965644/lib/libdl-2.8.so
0045e000-0045f000 rwxp 3000 68:02 2965644/lib/libdl-2.8.so
08048000-08051000 r-xp  68:02 33 /usr/bin/apachetop
08051000-08052000 rw-p 9000 68:02 33 /usr/bin/apachetop
0960c000-0962d000 rw-p 0960c000 00:00 0
b7f3c000-b7f4 rw-p b7f3c000 00:00 0
bfb28000-bfb3d000 rw-p bffea000 00:00 0  [stack]
Canceled
robert@tux:~ > 

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

How reproducible:
Everytime, just: apachetop -f /var/log/httpd/access_log

Actual results:
*** buffer overflow detected ***: apachetop terminated

Expected results:
Just working...

Additional info:
(gdb) bt
#0  0x0012e402 in __kernel_vsyscall ()
#1  0x00302660 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0x00304028 in abort () at abort.c:88
#3  0x0033f5bd in __libc_message (do_abort=2, fmt=0x411bbd "*** %s ***: %s
terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:170
#4  0x003cec48 in __fortify_fail (msg=0x411b8c "buffer overflow detected") at
fortify_fail.c:32
#5  0x003ccd40 in __chk_fail () at chk_fail.c:29
#6  0x003cd4a8 in __realpath_chk (buf=0xbffdd9c8 "/var/log/httpd/access_log",
resolved=0xbffd3e48 "8 /\tpáC", resolvedlen=128) at realpath_chk.c:30
#7  0x080496a5 in new_file ()
#8  0x0804a2d6 in main ()
(gdb) bt full
#0  0x0012e402 in __kernel_vsyscall ()
No symbol table info available.
#1  0x00302660 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
resultvar = 
pid = 148
selftid = 5642
#2  0x00304028 in abort () at abort.c:88
act = {__sigaction_handler = {sa_handler = 0xbffd36ac, sa_sigaction =
0xbffd36ac}, sa_mask = {__val = {4131897, 1233472, 0, 1233472, 0, 3221043000,
134517521, 1234520, 3, 951, 134514798, 3,
  134513068, 134513140, 3858732, 9, 3221042928, 3, 3233108, 148, 9, 7,
3221043044, 3980792, 3, 3221042928, 9, 0, 4263955, 4263951, 4267973, 4266865}},
sa_flags = 4266889, sa_restorer = 0x411b85}
sigs = {__val = {32, 0 }}
#3  0x0033f5bd in __libc_message (do_abort=2, fmt=0x411bbd "*** %s ***: %s
terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:170
ap = 0

[Bug 419662] Re: devkit-disks-helper-ata-smart-collect assert failure: devkit-disks-helper-ata-smart-collect: atasmart.c:2687: sk_disk_get_blob: Assertion `(size_t) ((uint8_t*) p - (uint8_t*) d->blob)

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=529230.

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-10-15T15:46:27+00:00 Martin wrote:

libatasmart 0.16

We get quite a number of duplicates about an assertion failure in
sk_disk_set_blob() when being called from DeviceKit-disks' devkit-disks-
helper-ata-smart-collect:

#3  0x7ff8d256c7b2 in sk_disk_get_blob (d=0xb01010, blob=0x7fffdc256578, 
rsize=0x7fffdc256570) at atasmart.c:2687
size = 1572
good = 1
have_good = 1
p = 
__PRETTY_FUNCTION__ = "sk_disk_get_blob"
#4  0x00400b7e in main (argc=, 
argv=) at job-ata-smart-collect.c:89
ret = 
device = 0x7fffdc256ede "/dev/sdb"
d = (SkDisk *) 0xb01010
smart_is_available = 1
awake = 1
blob = 
blob_size = 

The 25ish duplicates distribute pretty evenly between i386 and x86_64,
so I don't think it's an architecture specific problem.

Is there something the reporters could do to collect further information
here?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/419662/comments/4


On 2009-10-23T21:33:25+00:00 David wrote:

Hey Martin,

Lennart showed me this bug. FWIW, never seen this on Fedora. Btw,
there's a libatasmart bugtracker on fd.o now:
https://bugs.freedesktop.org/enter_bug.cgi?product=libatasmart

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/419662/comments/12


On 2009-10-23T21:41:20+00:00 Lennart wrote:

Should be fixed by
http://git.0pointer.de/?p=libatasmart.git;a=commit;h=cfe49b30af32b5b631b2a055c6d10197a70d90ff

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/419662/comments/13


** Changed in: libatasmart (Fedora)
   Status: Fix Released => Won't Fix

** Changed in: libatasmart (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/419662

Title:
  devkit-disks-helper-ata-smart-collect assert failure: devkit-disks-
  helper-ata-smart-collect: atasmart.c:2687: sk_disk_get_blob: Assertion
  `(size_t) ((uint8_t*) p - (uint8_t*) d->blob) == size' failed.

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

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

[Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

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=524403.

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-19T20:51:57+00:00 MartinG wrote:

Description of problem:

My system runs into a soft lockup after some time, seemingly at random,
but it could be that it only happens after ~30 min of idling.

The display goes blank, the monitor says "No signal", but I can still
ssh into the machine. I am not able to wake it up by ctrl-alt-f2 or the
like.

"init 3" as root does not work, and I can't seem to kill any running
programs (over ssh, as root - the shell never returns)

In /var/log/messages I get:

INFO: task events/0:9 blocked for more than 120 seconds.
 
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.   
 
events/0  D 88012de02024 0 9  2 
 
 88012fb31d60 0046 0001 a04774eb
 
 88012fb31cf0 81046bf0 88012fb31cf0 8604ee9e
 
 88012fb060e8 e2e8 88012fb060e8 00012cc0
 
Call Trace: 
 
 [] ? mantis_query_rc+0x0/0x89 [mantis]   
 
 [] ? dequeue_entity+0x2f/0x1e8   
 
 [] ? dequeue_task_fair+0x81/0xa0 
 
 [] ? __switch_to+0x19c/0x23c 
 
 [] __mutex_lock_common+0x12c/0x1a8   
 
 [] __mutex_lock_slowpath+0x2c/0x42   
 
 [] mutex_lock+0x43/0x71  
 
 [] i915_gem_retire_work_handler+0x40/0x96 [i915] 
 
 [] ? i915_gem_retire_work_handler+0x0/0x96 [i915]
 
 [] worker_thread+0x1ab/0x25d 
 
 [] ? autoremove_wake_function+0x0/0x5f   
 
 [] ? worker_thread+0x0/0x25d 
 
 [] kthread+0x6d/0xae 
 
 [] child_rip+0xa/0x20
 
 [] ? restore_args+0x0/0x30   
 
 [] ? kthread+0x0/0xae
 
 [] ? child_rip+0x0/0x20  
 
INFO: task events/0:9 blocked for more than 120 seconds.
 
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.   
 
events/0  D 88012de02024 0 9  2 
 
 88012fb31d60 0046 0001 a04774eb
 
 88012fb31cf0 81046bf0 88012fb31cf0 8604ee9e
 88012fb060e8 e2e8 88012fb060e8 00012cc0
Call Trace:
 [] ? mantis

[Bug 511033] Re: anki crashed with SIGSEGV in QAbstractItemView::dataChanged()

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

** Changed in: anki (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/511033

Title:
  anki crashed with SIGSEGV in QAbstractItemView::dataChanged()

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

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

[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 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=570629.

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


On 2010-03-04T21:31:33+00:00 Marc wrote:

Created attachment 397928
Patch to autodetect netcat parameters

Debian/Ubuntu hosts need to add "-q 0" to netcat to properly quit. A
similar bug existed in virt-manager:

https://bugzilla.redhat.com/show_bug.cgi?id=517778

Attached is a patch for libvirt that uses the same technique as virt-
manager now does to autodetect if the remote netcat tool needs the -q
parameter.

Based on the following virt-manager commit:

http://hg.fedorahosted.org/hg/virt-manager/rev/1f781890ea4a

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


On 2010-03-04T22:53:16+00:00 Cole wrote:

I posted a similar patch upstream last month:

https://www.redhat.com/archives/libvir-list/2010-February/msg00444.html

Danpb wasn't a fan of it (understandably) and suggested a long term
approach of making a custom helper to drop in /usr/libexec so that we
don't need to rely on 'nc'.

However, until that work is done, it would be nice if one of these
patches could be applied.

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


On 2012-04-18T19:46:39+00:00 Eric wrote:

Fixed in 0.9.7 with this commit:

commit a2b5c57db83559d4fe32ee90fbb668388e06
Author: Guido Günther 
Date:   Fri Jul 8 21:07:29 2011 +0200

Autodetect if the remote nc command supports the -q option

Based on a patch by Marc Deslauriers 

RH: https://bugzilla.redhat.com/show_bug.cgi?id=562176
Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/517478
Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573172

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


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

** Changed in: libvirt
   Importance: Unknown => Medium

** Bug watch added: Debian Bug tracker #573172
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573172

-- 
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 505452] Re: eeepc_laptop module not loading on kernel 2.6.32

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=564544.

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-13T05:50:52+00:00 Usama wrote:

Description of problem:
Many function keys aren't working on Asus Eee 1005HA laptop
F1 sleep Yes
F2 Wifi No
F3 disables touch-pad No
F4 control Screen No
F5 decrease screen brightness Yes
F6 increase screen brightness Yes
F7 turn off screen Yes
F8 switches display No
F9 shows Task Managers No
F10 mutes sound No
F11 decreases sound No
F12 increases sound No
Space switch Hybird Engine modes No
Insert Works as NumLk Yes
Delete Works as ScrLK Unknown
Arrows Works as Home\End\Page(up,Down) Yes

Most of those keys are working with Karmic 9.10

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

How reproducible:
press the Fn button with F1 to F12 the only working function is F1,F5,F6 and F7

  
Actual results:
nothing happens

Expected results:
function keys should work

Additional info:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/518007

Most of those keys are working with Ubuntu Karmic 9.10 but not with
10.04 which has the same kernel of rawhide kernel.

couldn't know if the function keys are working on F12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505452/comments/19


On 2010-03-06T03:11:02+00:00 Usama wrote:

more info:
http://bbs.archlinux.org/viewtopic.php?id=87316
http://bugs.archlinux.org/task/17616

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505452/comments/21


On 2010-03-15T14:33:04+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/linux/+bug/505452/comments/23


On 2010-04-05T02:19:35+00:00 Usama wrote:

please look here,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505452/comments/28

adding "acpi_osi=Linux" fixed many keys but broke others that was
working before the change.

F7 turn off screen
brightness key no longer show pop-up but works

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505452/comments/33


On 2010-04-09T18:25:24+00:00 Pavel wrote:

acpi_osi=Linux does noot help me :(
Brightness indication still work, but real brightness not changed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505452/comments/38


On 2010-04-12T08:14:45+00:00 Paulo wrote:

There is a new driver for WMI based hotkeys on Eee PC laptops, see
https://patchwork.kernel.org/patch/87210/.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505452/comments/41


On 2011-06-02T16:35:28+00:00 Bug wrote:


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

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 13'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 13 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/linux/+bug/505452/comments/69


On 2011-06-2

[Bug 1020212] Re: gtk apps keep polling for $HOME/.config/ibus/bus dir

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=572611.

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


On 2010-03-11T17:05:59+00:00 Matthew wrote:

If the ~/.config/ibus/bus directory doesn't exist, any gtk app will wake
up once per second in an attempt to add a notify on it. The directory
should be automatically created to work around this.

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


On 2010-04-08T03:18:50+00:00 Peng wrote:

This issue has been fixed in upstream source code. I will build new
release for fedora soon.

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


On 2010-04-21T10:24:14+00:00 Fedora wrote:

ibus-1.3.2-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/ibus-1.3.2-1.fc13

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


On 2010-04-21T21:55:00+00:00 Fedora wrote:

ibus-1.3.2-1.fc13 has been pushed to the Fedora 13 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 ibus'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/ibus-1.3.2-1.fc13

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


On 2010-04-27T02:18:41+00:00 Fedora wrote:

ibus-1.3.2-1.fc13 has been pushed to the Fedora 13 stable repository.
If problems still persist, please make note of it in this bug report.

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


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

Title:
  gtk apps keep polling for $HOME/.config/ibus/bus dir

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

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

[Bug 525462] Re: FFe: Support Application Indicators

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

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-22T18:51:53+00:00 Marc wrote:

Created attachment 395534
Initial version of application indicator support

Description of problem:

We would like to support application-indicators for virt-manager as
proposed at this page:

https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators

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


On 2010-03-01T01:31:06+00:00 Cole wrote:

Thanks for the patch, I've applied it upstream with one important change: lack
of the 'appindicator' module caused the app to fail to start. I would HIGHLY
recommend making use of the patch I applied upstream:

http://hg.fedorahosted.org/hg/virt-manager/rev/1cfeb4fd523d

Thanks for the contribution!

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


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

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

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

Title:
  FFe: Support Application Indicators

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

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

[Bug 665956] Re: Theme änd keyböärd läyöüt göing cräzy

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

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-15T22:03:07+00:00 Matthew wrote:

Description of problem:

I've been using "keycode 135 = Mode_switch" in my ~/.xmodmap for years,
to change my "menu" key into something useful.

Starting sometime fairly recently (not sure exactly; sorry) occasionally
(no repeatable case, but happens regularly enough to be annoying), the
mode_switch gets stuck in on, such that pressing the key and a letter
gives its normal version rather than its mode_switch version. (It's as
if the equivalent of caps-lock for mode_switch is on.)

There doesn't seem to be any cure but hitting mode_switch a bunch of
times and other random typing -- eventually it goes off again.


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

Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev
because it's convenient -- could be a lot of things, I suppose.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/0


On 2009-11-16T15:34:40+00:00 Bug wrote:


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

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/1


On 2009-11-16T21:32:27+00:00 Matěj wrote:

(In reply to comment #0)
> Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev 
> because
> it's convenient -- could be a lot of things, I suppose.  

Let's try to blame Xserver itself :) (it doesn't matter that much
because issues of input go to Peter anyway).

Please attach your X server config file (/etc/X11/xorg.conf, if
available), output of the dmesg command, and X server log file
(/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this
information.

Thanks in advance.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/2


On 2009-12-14T20:59:09+00:00 Matthew wrote:

Created attachment 378349
dmesg output

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/3


On 2009-12-14T21:00:19+00:00 Matthew wrote:

Created attachment 378350
Xorg.0.log

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/4


On 2009-12-14T21:06:01+00:00 Matthew wrote:

Attached requested logs. This is on my Rawhide box.

It also happens on my F12 system at home, which has a different radeon
card and generally different hardware overall. I can attach that if you
think it might be helpful.

I think *maybe* the problem is related to the key _next_ to this one;
I've defined that to be Multi_key, and it may be related to hitting that
accidentally in some way. I still can't reproduce _on purpose_ though.
(But it does happen once every couple of days.)

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/5


On 2009-12-14T21:06:56+00:00 Matthew wrote:

Created attachment 378354
xmodmap

I must add that the ability to type hearts and flowers was added at the
request of my 4-year-old daughter. Just sayin'.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/6


On 2010-01-23T22:18:50+00:00 Chris wrote:


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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/7


On 2010-01-23T22:25:17+00:00 Matthew wrote:

This is still happening, by the way. And I removed the definition for
Multi_key, so that's _not_ it.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/665956/comments/8


On 2010-03-13T11:43:17+00:00 Matthew wrote:

This is still happening. It is very annoying. I attached the requested
informat

[Bug 1010926] Re: HP Folio 13: Lid close event is never fired => no suspend on lid close

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

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

Title:
  HP Folio 13: Lid close event is never fired => no suspend on lid close

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

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

[Bug 691590] Re: libvirt should not take ownership of ISO images

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=568935.

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-27T00:33:18+00:00 Cristian wrote:

Description of problem:
When I use an install ISO image labeled public_content_t, virt-manager will 
relabel it as virt_content_t without any warnings. It will also change its 
owner and group to qemu. It should allow virtual machines to read those files 
(which might also be shared via http, samba or nfs).

Version-Release number of selected component (if applicable):
virt-manager-0.8.2-1.fc12.noarch.rpm

How reproducible:
Every time.

Steps to Reproduce:
1. Create a new VM.
2. Select an ISO image labeled public_content_t.
3. Continue all the steps until the machine is started.
  
Actual results:
The ISO image will be labeled virt_content_t and its owner and group will be 
changed to qemu.

Expected results:
A warning should be displayed if the permissions of the file need to be changed 
or even better allow the virtual machine to read public_content_t files.

Additional info:
I'm also using the following packages:
libvirt-0.7.1-15.fc12.x86_64.rpm
selinux-policy-targeted-3.6.32-89.fc12.noarch.rpm

A related RFE is bug #568933.

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


On 2010-02-27T01:42:34+00:00 Cole wrote:

Libvirt is doing the relabeling here. Reassigning.

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


On 2010-06-05T16:28:07+00:00 Cristian wrote:

It's still present in libvirt-0.7.7-4.fc13.x86_64.rpm.

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


On 2010-08-24T16:59:57+00:00 Cristian wrote:

It's still present in libvirt-0.8.2-1.fc13.x86_64.rpm.

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


On 2012-04-18T19:44:06+00:00 Eric wrote:

Done with this commit in 0.9.9:
commit b43432931aef92325920953ff92beabfbe5224c8
Author: Eric Blake 
Date:   Thu Dec 22 17:47:50 2011 -0700

seclabel: allow a seclabel override on a disk src

Implement the parsing and formatting of the XML addition of
the previous commit.  The new XML doesn't affect qemu command
line, so we can now test round-trip XML->memory->XML handling.

I chose to reuse the existing structure, even though per-device
override doesn't use all of those fields, rather than create a
new structure, in order to reuse more code.

* src/conf/domain_conf.h (_virDomainDiskDef): Add seclabel member.
* src/conf/domain_conf.c (virDomainDiskDefFree): Free it.
(virSecurityLabelDefFree): New function.
(virDomainDiskDefFormat): Print it.
(virSecurityLabelDefFormat): Reduce output if model not present.
(virDomainDiskDefParseXML): Alter signature, and parse seclabel.
(virSecurityLabelDefParseXML): Split...
(virSecurityLabelDefParseXMLHelper): ...into new helper.
(virDomainDeviceDefParse, virDomainDefParseXML): Update callers.
* tests/qemuxml2argvdata/qemuxml2argv-seclabel-dynamic-override.args:
New file.
* tests/qemuxml2xmltest.c (mymain): Enhance test.
* tests/qemuxml2argvtest.c (mymain): Likewise.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/691590/comments/21


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

** Changed in: libvirt
   Importance: Unknown => Medium

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

Title:
  libvirt should not take ownership of ISO images

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

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

[Bug 539350] Re: X does not behave properly with the -16 kernel in Lucid

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

** Changed in: xorg (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/539350

Title:
  X does not behave properly with the -16 kernel in Lucid

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

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

[Bug 1436772] Re: /usr/bin/nautilus:11:_gtk_css_value_unref:gtk_css_value_shadows_free:_gtk_css_value_unref:g_ptr_array_foreach:ptr_array_free

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=1199731.

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


On 2015-03-07T15:16:15+00:00 Tim wrote:

Description of problem:
Locking an encrypted block device from Disks.

Version-Release number of selected component:
nautilus-3.15.90-1.fc22

Additional info:
reporter:   libreport-2.4.0
backtrace_rating: 4
cmdline:/usr/bin/nautilus --gapplication-service
crash_function: _gtk_css_value_unref
executable: /usr/bin/nautilus
kernel: 4.0.0-0.rc2.git0.1.fc22.x86_64
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _gtk_css_value_unref at gtkcssvalue.c:65
 #1 gtk_css_value_shadow_free at gtkcssshadowvalue.c:60
 #2 gtk_css_value_shadows_free at gtkcssshadowsvalue.c:47
 #3 g_ptr_array_foreach at garray.c:1502
 #4 ptr_array_free at garray.c:1088
 #5 g_ptr_array_unref at garray.c:1036
 #6 gtk_css_static_style_dispose at gtkcssstaticstyle.c:98
 #8 g_hash_table_remove_all_nodes at ghash.c:548
 #10 g_hash_table_remove_all at ghash.c:1428
 #11 g_hash_table_destroy at ghash.c:1122

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/0


On 2015-03-07T15:16:19+00:00 Tim wrote:

Created attachment 999159
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/1


On 2015-03-07T15:16:20+00:00 Tim wrote:

Created attachment 999160
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/2


On 2015-03-07T15:16:21+00:00 Tim wrote:

Created attachment 999161
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/3


On 2015-03-07T15:16:23+00:00 Tim wrote:

Created attachment 999162
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/4


On 2015-03-07T15:16:26+00:00 Tim wrote:

Created attachment 999163
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/5


On 2015-03-07T15:16:29+00:00 Tim wrote:

Created attachment 999164
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/6


On 2015-03-07T15:16:32+00:00 Tim wrote:

Created attachment 999165
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/7


On 2015-03-07T15:16:33+00:00 Tim wrote:

Created attachment 999166
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/8


On 2015-03-07T15:16:35+00:00 Tim wrote:

Created attachment 999167
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/9


On 2015-03-07T15:16:36+00:00 Tim wrote:

Created attachment 999168
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/10


On 2015-03-09T18:36:30+00:00 Matthias wrote:

which gtk3 version is this with ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/11


On 2015-03-10T09:18:57+00:00 Tim wrote:

That was with gtk3-3.15.9-1.fc22.x86_64.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436772/comments/12


On 2016-07-19T12:56:55+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 prob

[Bug 545755] Re: system-config-printer.py assert failure: *** glibc detected *** python: realloc(): invalid next size: 0x091d93e0 ***

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

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-22T20:04:46+00:00 Edgar wrote:

abrt 1.0.6 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/system-config-printer/applet.py
component: system-config-printer
executable: /usr/bin/python
kernel: 2.6.31.12-174.2.3.fc12.x86_64
package: system-config-printer-1.1.16-13.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

How to reproduce
-
I don't know how to reproduce.
I just printed something and deleted some jobs from the print server queue, and 
then the printer applet crashes.

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/0


On 2010-02-22T20:04:48+00:00 Edgar wrote:

Created attachment 395557
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/1


On 2010-02-23T10:29:42+00:00 Jiri wrote:

Can you describe how exactly did you deleted those jobs ? Thanks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/2


On 2010-02-23T15:36:19+00:00 Tim wrote:

So the crash was from freeing the list of Connection objects, and it was
most likely caused by some kind of memory scribble.

The only thing I can see wrong in that code is that it assumes the to-
be-dealloc'd Connection object appears in the list.  However, it ought
to.

Anyway, I can harden that (to protect against e.g. bit-errors) by only
removing the object from the list if it appears there in the first
place.  Hopefully that will prevent this kind of problem.

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/3


On 2010-02-23T16:31:10+00:00 Tim wrote:

Fixed upstream.

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/4


On 2010-03-08T15:18:00+00:00 Tim wrote:

I've discovered the reason for this, and have confirmed that the
upstream fix is correct.

First, a reproducer:

==>
import signal
import cups

def alarmclock (signum, frame):
raise KeyboardInterrupt

signal.signal (signal.SIGALRM, alarmclock)
connections = []
while True:
# Create
signal.alarm (10)
connections.append (cups.Connection ())
signal.alarm (0)
<==

This just keeps creating more and more connections until cupsd stops
accepting them (when it hits its maximum file descriptor count).  At
that point, the program raises an exception and exits.

What happens is that Connection_init() fails *before* the newly-
allocated Connection object is added into the list.  As the
initialization failed, the object is deallocated with
Connection_dealloc(), and of course that assumes the object is in the
list.

So the correct behaviour is to verify that the connection is in the list
before trying to remove it.

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/5


On 2010-03-08T15:48:01+00:00 Jiri wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/6


On 2010-03-08T15:49:29+00:00 Jiri wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/7


On 2010-03-10T10:48:13+00:00 Fedora wrote:

system-config-printer-1.1.93-6.fc13 has been submitted as an update for Fedora 
13.
http://admin.fedoraproject.org/updates/system-config-printer-1.1.93-6.fc13

Reply at: https://bugs.launchpad.net/ubuntu/+source/python-
cups/+bug/545755/comments/8


On 2010-03-11T07:20:10+00:00 Fedora wrote:

system-config-printer-1.1.93-6.fc13 has been pushed to the Fedora 13 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 her

[Bug 539708] Re: /usr/lib/cups/filter/pdftoraster failed

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

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-09T19:43:50+00:00 Richard wrote:

Description of problem:
After updating to ghostscript-8.70-5.fc12.x86_64, the printer only prints black 
pages with small vertical lines and some patterns on it. After downgrading to 
ghostscript-8.70-2.fc12.x86_64.rpm, everything works fine again.

Version-Release number of selected component (if applicable):
ghostscript-8.70-5.fc12.x86_64
cups-1.4.2-20.fc12.x86_64
turboprint-2.12-1.x86_64 (from http://www.turboprint.de/)

How reproducible:
Always

Steps to Reproduce:
1. Update to ghostscript-8.70-5.fc12.x86_64
2. Print something (e.g. a PDF file or a test page).
  
Actual results:
The printed page is mostly black with only some vertical stripes and patterns 
on it.

Expected results:
The page is printed correctly.

Additional info:
I am using turboprint as driver for my Canon Pixma IP 4000. I don't know if 
this is a bug in ghostscript or an incompatibility with turboprint. Anyhow I 
could reproduce this behaviour on two Fedora 12 x86_64 machines.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/0


On 2010-02-11T13:10:11+00:00 Tim wrote:

Please attach the PPD for the queue you are using.  You can find this in
the /etc/cups/ppd directory.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/1


On 2010-02-11T22:15:15+00:00 Richard wrote:

Created attachment 390356
ppd of the printer queue

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/2


On 2010-02-12T15:21:26+00:00 Tim wrote:

Thanks.  This is some kind of regression in the ghostscript cups driver.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/3


On 2010-02-12T15:29:07+00:00 Tim wrote:

Created attachment 390508
in.ps.bz2 (PostScript input for reproducer)

This file, along with the PPD, shows the problem.

1. bunzip2 in.ps.bz2
2. PPD=tp0.ppd gs -sDEVICE=cups -r600x600 -dSAFER -dNOPAUSE -dBATCH 
-sOutputFile=out.rast
3. rasterview out.rast

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/4


On 2010-02-16T12:57:34+00:00 Tim wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/5


On 2010-02-16T12:58:46+00:00 Fedora wrote:

ghostscript-8.70-6.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/ghostscript-8.70-6.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/6


On 2010-02-16T22:01:38+00:00 Richard wrote:

ghostscript-8.70-6.fc12 fixes the bug for me. Thank you!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/7


On 2010-02-17T18:22:30+00:00 Fedora wrote:

ghostscript-8.71-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/ghostscript-8.71-1.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/8


On 2010-02-18T22:50:22+00:00 Peter wrote:

8.71-1.fc12 works for me

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/9


On 2010-02-19T11:55:34+00:00 Fedora wrote:

ghostscript-8.71-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/ghostscript-8.71-2.fc12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/539708/comments/10


On 2010-02-19T18:54:02+00:00 John wrote:

Using Fedora 12 and turboprint-2.13-2.i586.rpm. Update from
ghostscript-8.70-2.fc12.i686.rpm to ghostscript-8.70-5.fc12.i686.rpm
started the black print page problem.

Update to ghostscript-8.71-1.fc12.i686.rpm initially fixed it but after
reboot black page again. Tried ghostscript-8.71-2.fc12.i686

[Bug 1609700] Re: username is not saved in openconnect connection dialog

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

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-05-03T10:46:54+00:00 Matthias wrote:

Description of problem:
When connecting with NetworkManager-openconnect on Fedora 23 and before, the  
username and password could be saved. On Fedora 24 (Alpha-7) only the password 
is saved but the username field is empty, so the username has to be entered 
each time newly.

Version-Release number of selected component (if applicable):
 1.2.0-1.fc24

How reproducible:
Connect to a vpn twice

Steps to Reproduce:
1. enter vpn connection 
2. connect and check password save dialog
3. disconnect and connect again

Actual results:
username is not shown in dialog (only password bullets)
login failed is shown if connecting witout entering the username again.

Expected results:
username should be shown as well 

Additional info:

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


On 2016-05-25T07:54:07+00:00 Robert wrote:

Seeing the same problem here on F24 Beta

$ rpm -qa|grep openconnect
openconnect-7.06-4.fc24.x86_64
NetworkManager-openconnect-1.2.2-1.fc24.x86_64

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


On 2016-05-25T07:56:29+00:00 David wrote:

Going to blame NM itself for this. Will strip the stored username from
my own config (it was there before I upgraded) and attempt to
reproduce...

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


On 2016-05-25T07:59:18+00:00 David wrote:

Note: NM-openconnect "makes up" secrets as it goes, to remember the
authentication form entries (the 'input' ones, not the 'password' ones
which end up being stored via libsecret.

So at the first *authentication*, because the server offers a form named
'main' which has a 'username' field, I end up with the auth-dialog
spitting out an extra secret that was never previously known, which (in
F23 and previously at least) resulted in:

# grep form: /etc/NetworkManager/system-connections/Intel\ AnyConnect\ VPN 
form:main:password-flags=1
form:main:username=david.woodho...@intel.com

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


On 2016-06-23T12:09:09+00:00 Matthias wrote:

The problem still exists in final Fedora 24.

Is there a workaround?

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


On 2016-07-03T11:13:26+00:00 Lubomir wrote:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=lr
/openconnect-secrets-rh1332491

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


On 2016-07-04T14:39:54+00:00 Thomas wrote:

>> setting-vpn: get the flags property name only up to the first ":" in
secret

According to example from comment 3,

  form:main:password-flags=1
  form:main:username=david.woodho...@intel.com

it seems the secret name would be "form:main:username". Wouldn't the patch then 
lookup for "form-main-flags"? How does that fit with "form:main:password-flags"?
Surely the patch does it right, but the commit message does not explain the 
meaning of the ':'. It should show concrete examples of what openconnect does, 
and why we would truncate secret names at a colon.


It seems to me, that NMSettingVpn:get_secret_flags() should instead allow for a 
missing flags entry, but also consider whether there is an entry in the secrets.

Having a password in the @secrets hash, but no flags in @data, might
anyway be considered in inconsistent state. I think, NMSettingVpn should
treat "name" as secret if at least one of the following is true:

  - @secrets hash has an entry "name".
  - @data hash has an entry "name" + "-flags".

If the flags entry is missing, it should assume "0".


Above would make sense to me, regardless of any openconnect hacks. Wouldn't 
that fix the openconnect issue?

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


On 2016-07-04T15:31:04+00:00 David wrote:

(In reply 

[Bug 1666109] Re: Optimal I/O size isn't calculated properly with uas module, and it may make data inconsistent on the disk and logical volume

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=1420935.

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


On 2017-02-09T22:28:47+00:00 Yasuaki wrote:

Description of problem:
I connect a second USB-UAS drive to the single USB interface card,
the second drive is failed to probe. 
When I connect it to another USB interface card, it works fine.

Version-Release number of selected component (if applicable):
Fedora 25 x86_64, 4.9.7-201.fc25.x86_64
Dell XPS 8700, 
SD-PEU3R-2EL2 x2 (Renesas Technology Corp. uPD720202 USB 3.0 Host Controller 
(rev 02)),
RS-EC32-U31R x4 (USB 3.1 RAID1 external drives)


How reproducible:
Always


Steps to Reproduce:
1. Connect 2 USB-UAS drives on the same interface card.
2. Boot Fedora 25 

Actual results:
Only 1 drive works.


Expected results:
Two drives work.

Additional info:
On Windows 10, it works fine.

lspci ( dev 04:00.0 and 06:00.0) ==
[root@nas01 ~]# lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #5 (rev d5)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #7 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 
6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit 
X540-AT2 (rev 01)
01:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit 
X540-AT2 (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0c)
04:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host 
Controller (rev 02)
05:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller 
(rev 01)
06:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host 
Controller (rev 02)
===

== lsusb =
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 003: ID 0584:0276 RATOC System, Inc.
Bus 008 Device 002: ID 0584:0276 RATOC System, Inc.
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 003: ID 0584:0276 RATOC System, Inc.
Bus 006 Device 002: ID 0584:0276 RATOC System, Inc.
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 003 Device 004: ID 0557:2213 ATEN International Co., Ltd CS682 2-Port USB 
2.0 DVI KVM Switch
Bus 003 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


=== lsusb -t  Bus 8.0 Port 1,2 and Bus 6 Port 1,2===
[root@nas01 ~]# lsusb -t
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xh

[Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2017-10-26 Thread Kai-Heng Feng
Can you attach the output of `nvme get-feature -f 0x0c -H /dev/nvme0`?

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

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

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

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

2017-10-26 Thread Peter Wallbridge
Did it. I hope I did it correctly.

On Thu, Oct 26, 2017 at 10:14 PM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Peter, we're here to help. And Sebastien is right... The fastest way to
> a fix for you now is for you to report the bug directly on the Gnome bug
> tracker:  https://bugzilla.gnome.org/
>
> We ask you to do this because the conversation that will happen with the
> Gnome guys needs to be with someone who experiences the problem first-
> hand (yourself).
>
> After a fix is available there we will pull it down to here again for
> release in Ubuntu.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in gnome-shell package in Ubuntu:
>   New
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1725836/+subscriptions
>

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

Title:
  No more than 2 displays work simultaneously

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

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

[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 2008

[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 comm

[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 "/usr/lib/python

[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 S-vid

[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 more

[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&revision=1946
and status file note:
  http://ganglia.svn.sourceforge.net/viewvc/ganglia?view=rev&revision=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&r2=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&revision=1953

Whole patch:
http://ganglia.svn.sourceforge.net/viewvc/ganglia/trunk/monitor-core/gmetad/server.c?r1=1233&r2=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 fu

[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 2

[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 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 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 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 o

[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 n

[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 1

[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 ../nptl

  1   2   3   4   5   6   7   8   9   10   >