date:20171027

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

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

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

Title:
  No more than 2 displays work simultaneously

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have three displays that worked fine in 17.04.
  Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
  All three seem to be properly specified in monitors.xml.
  The display setup scree detects all three.
  UBUNTU 17.10
  AMD PitcairnLSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-02-23 (242 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-10-27 Thread Muhammad Darwish

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

Happened right after logging in to a google account

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724738

Title:
  gnome-control-center crashed with SIGSEGV

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  g-c-c hangs then crashes after successful adding online account

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  Uname: Linux 4.13.7-041307-generic x86_64
  NonfreeKernelModules: 8723bu
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 19 11:13:19 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-08-30 (49 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center background
  SegvAnalysis:
   Segfault happened at: 0x7f85caf39b3b:mov0x8(%rax),%rax
   PC (0x7f85caf39b3b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  UserGroups: adm cdrom dip i2c lpadmin plugdev sambashare sudo video

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-10-27 Thread Adam Conrad

Hello PeterPall, or anyone else affected,

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

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

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

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

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

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

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

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

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


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

Created attachment 1228916
failed_wayland_gnome_shell_log.txt (journalctl)

Description of problem:

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

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

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


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

How reproducible:
Always.

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

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

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


Additional info:

kernel 4.8.11-300

extract from lspci:

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

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

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

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


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

Created attachment 1228917
failed_gdm_log.txt (journalctl)

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


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

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

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


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

I can confirm this also happens on my system.

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

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

Hardware name: Dell Inc. Latitude E6540/0725FP

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

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

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

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

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

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


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

Same with these two cards on F25:

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

nouveau is the primary with the i915 unused.

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


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

Seems to be a similar problem to bug #1403512

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


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

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

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

2017-10-27 Thread Daniel van Vugt

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

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

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

Title:
  No more than 2 displays work simultaneously

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have three displays that worked fine in 17.04.
  Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
  All three seem to be properly specified in monitors.xml.
  The display setup scree detects all three.
  UBUNTU 17.10
  AMD PitcairnLSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-02-23 (242 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-10-27 Thread Alex Lohr

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

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashed on connecting with VNC Client. Using vnc4server.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.18.4-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 17 12:28:21 2017
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2017-02-06 (38 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86PostProbe ()
   InitOutput ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

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

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

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

Status in Mozilla Thunderbird:
  Expired
Status in thunderbird package in Ubuntu:
  Fix Released
Status in icedove package in Debian:
  New
Status in thunderbird package in Fedora:
  Fix Released

Bug description:
  Binary package hint: thunderbird

  After starting Thunderbird, then open any available nntp-server
  (news.gmane.org, or news.individual.org (you'll need an account to
  access this server)). Thunderbird will immediately block on any
  newsgroup with a reasonable amount of new messages. It will consume
  100% CPU, slow down the whole system significantly. After a while
  Thunderbird is grayed out most of the time. You can't access it
  anymore. Sometimes this lasts for hours. Working with Thunderbird is
  impossible.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1
  Uname: Linux 2.6.36.2 x86_64
  Architecture: amd64
  Date: Tue Jan 18 21:29:52 2011
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

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

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

Status in Linux:
  Invalid
Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid
Status in alsa-lib package in Fedora:
  Won't Fix
Status in pulseaudio package in openSUSE:
  Invalid

Bug description:
  Hi,

  I have a dell xps m1530 laptop with the following internal audio
  device:

  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
  Controller (rev 02)

  In hardy, sound recording from the internal mic works great, but in
  Ibex sound recording with the internal mic is very silent. I can't
  make it louder with the gnome volume control and alsamixer.

  See
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/275998/comments/109
  for a temporary solution

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

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


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

Created attachment 339197
web browser with corrupted text

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

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

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

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

Expected results:
Ponies.


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

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


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

Created attachment 339198
Xorg.0.log while text corrupted

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


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

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

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


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

Created attachment 339402
Weird screen

Just in case it wasn't clear yet.

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


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

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

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

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


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

I'm seeing this as well with i965

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


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

Oh and yes, I'm using compiz.

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


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

I am seeing this here as well with Xfce.

Some observations:

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

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

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

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

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

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

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

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


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

Getting the same thing,

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

http://www.freeima

[Desktop-packages] [Bug 99368] Re: SVG rotation renderization broken

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

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


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

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

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

How reproducible:
always
  

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

Additional info:
Could be related to cairo?!

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


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

Created attachment 150321
rendering in Epiphany 2.16.3-3.fc6

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

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


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

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

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


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

Hm, all our gecko apps look broken.

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


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

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

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


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

btw. broken in rawhide, too.

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


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

Still present in latest rawhide liveCD image for F7.

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


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

Launchpad bug (also affecting Ubuntu):

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

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


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

This is fixed in version 2.0.0.5-1.fc7

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


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

aha, thanks for the notice.

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


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

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

Title:
  SVG rotation renderization broken

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox package in Fedora:
  Fix Released

Bug description:
  Binary package hint: firefox

  Firefox 2.0.0.3 in Ubuntu Feisty doesn't render properly the SVG
  rotations, some parts of the image disappear or are corrupted.

  It can be tested with
  http://croczilla.com/svg/samples/opacity1/opacity1.xml or with any
  other SVG with rotations.

  It works correctly with the same version of Firefox in Ubuntu Edgy.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

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


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

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

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

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

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

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


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

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

CVE-2007-4065: 13217 (infinite loop)

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

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

CVE-2007-4066: multiple flaws

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

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

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

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

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


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


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

This issue was addressed in:

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

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


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


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

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

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

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

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

Status in libvorbis package in Ubuntu:
  Fix Released
Status in libvorbis source package in Dapper:
  Won't Fix
Status in libvorbis package in Fedora:
  Fix Released

Bug description:
  References:
  DSA-1471-1 (http://www.debian.org/security/2008/dsa-1471)

  Quoting CVE-2007-4066:
  "Multiple buffer overflows in Xiph.Org libvorbis before 1.2.0 allow 
context-dependent attackers to cause a denial of service or have other 
unspecified impact via a crafted OGG file, aka trac Changesets 13162, 13168, 
13169, 13170, 13172, 13211, and 13215, as demonstrated by an overflow in 
oggenc.exe related to the _psy_noiseguards_8 array."

  DSA-1471-1 also mentions CVE-2007-3106 and CVE-2007-4029, which have
  been fixed in USN-498-1.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

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

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

Status in Metacity:
  Invalid
Status in metacity package in Ubuntu:
  Invalid
Status in metacity package in Debian:
  Invalid
Status in metacity package in Fedora:
  Invalid
Status in metacity package in Gentoo Linux:
  Fix Released

Bug description:
  Hi,

   Using Gutsy beta the .xsession-errors file consistently reports the
  following error:

  Refusing to initialize GTK+.
  /etc/gdm/Xsession: Beginning session setup...
  /etc/X11/Xsession.d/40guidance-displayconfig_restore: 11: 
/usr/bin/displayconfig-restore: not found
  SESSION_MANAGER=local/ilium:/tmp/.ICE-unix/5180
  Window manager warning: Failed to read saved session file 
/home/andrew/.metacity/sessions/default0.ms: Failed to open file 
'/home/andrew/.metacity/sessions/default0.ms': No such file or directory
  ** Message: Not starting remote desktop server

  No problems with this, although there appears to be a delay in the
  opening desktop fully loading.

Andrew

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 620751] Re: dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap

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

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/620751

Title:
  dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap

Status in Poppler:
  Fix Released
Status in evince package in Ubuntu:
  Invalid
Status in poppler package in Ubuntu:
  Fix Released
Status in evince source package in Lucid:
  Won't Fix
Status in poppler source package in Lucid:
  Won't Fix
Status in poppler package in Fedora:
  Fix Released

Bug description:
  Binary package hint: evince

  1.) I create a simple LaTeX document (named e.g. sample.tex)
  containing a vector symbol or the \nabla character:

  \documentclass[12pt,a4paper,oneside]{report}
  \begin{document}
  \[
  \vec{F}
  \]
  \end{document}

  (Please note that usual characters will not produce the buggy
  behaviour.)

  2.)  compile it:   latex sample.tex
  3.) convert dvi file to pdf file:dvipdf sample.dvi
  4.) view it running viewer from terminal:  evince sample.pdf

  Several lines of the error messages appear in the terminal window:

  Error: Illegal entry in bfrange block in ToUnicode CMap

  I am using the complete texlive installation (metapackage texlive-
  full).

  Note that I am not the first user who complains about this bug. There is an 
older report which however might not been fully noticed by launchpad team 
because it was filed just as a comment to another bug: see bug 234413 and 
comment #6 in particular:
  https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/234413/comments/6

  There is also an essentially same  bug report for other linux system
  (Fedora) which may be very useful:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Fri Aug 20 00:09:32 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: evince

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 530605] Re: gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu.

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

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


On 2010-03-13T11:55:38+00:00 Flóki wrote:

Description of problem:
Not possible to see samba share in Nautilus. 
Write smb: into location.
Then "Windows Network"  appears in header. Wait over 10 seconds and then 
error window comes. 

Version-Release number of selected component (if applicable):
samba-3.5.1-58.fc13.x86_64
system-config-samba-1.2.86-1.fc13.noarch
samba-winbind-clients-3.5.1-58.fc13.x86_64
samba-common-3.5.1-58.fc13.x86_64

selinux-policy-3.7.11-1.fc13.noarch
libselinux-2.0.90-5.fc13.x86_64
libselinux-utils-2.0.90-5.fc13.x86_64
selinux-policy-targeted-3.7.11-1.fc13.noarch
libselinux-python-2.0.90-5.fc13.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Open Nautilus and Ctrl+l 
2. Write smb:  into Lotstion
3. Wait over 10 seconds 
and error window 
The folder contents could not be displayed.
  
Actual results:
Error window 
The folder contents could not be displayed.
Sorry, could not display all the contents of "Windows Network": DBus error 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

Expected results:
To see enabeld samba shares
There is local sama share

Additional info:
Just rebooted to reapply selinux policy
There is no message in /var/log/messages
It is possible to see local samba share form another computer ( F12 )

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/6


On 2010-03-13T12:31:17+00:00 Flóki wrote:

Created attachment 399847
messages after settin selinux in permissive mode

When setting selinux in permissive mode then it possible to see local samba 
share
but not open it.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/7


On 2010-03-13T17:00:33+00:00 Simo wrote:

Can you check your firewall settings are not blocking samba client
packetes ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/8


On 2010-03-13T18:26:25+00:00 Flóki wrote:

>Can you check your firewall settings are not blocking samba client
packetes ?

samba and samba client  are marked as trusted.  
Fierwall disabled 
The folder contents could not be displayed.
Sorry, could not display all the contents of "Windows Network": DBus error 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

no message i /var/log/messages


If seleinux in permissive 
Mar 13 18:15:25 flokic dbus: avc:  received setenforce notice (enforcing=0)
Mar 13 18:15:25 flokic dbus: avc:  received setenforce notice (enforcing=0)
Mar 13 18:15:25 flokic dbus: Can't send to audit system: USER_AVC avc:  
received setenforce notice (enforcing=0)#012: exe="?" sauid=81 hostname=? 
addr=? terminal=?

and error window
Unable to mount location
Sorry, could not display all the contents of "Windows Network": DBus error 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/9


On 2010-03-13T22:40:42+00:00 Simo wrote:

Sorry but this looks like a nautilus or gnome-vfs problem to me.

Reassigning.

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/10


On 2010-03-15T20:25:52+00:00 Flóki wrote:

I see in top that  gvfsd-smb-brows is with cpu over 90%

Reply at: https://bugs.launchpad.net/ubuntu/+source/libgnome-
keyring/+bug/530605/comments/12


On 2010-03-16T16:40:03+00:00 Tomáš wrote:

Can you please post you gvfs, gnome-keyring and libgnome-keyring package
versions? Also, would it be possible to grab a backtrace and post it
here? I'm not seeing this

[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError

2017-10-27 Thread Juerg Haefliger

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

Hmm... Why do you think this is a duplicate of #1720159? My stack trace
looks different.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Running the following command:

  /usr/bin/python /usr/bin/duplicity collection-status
  --exclude=/mnt/jabba/juergh/backup/gollum
  --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
  /.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
  --exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
  --exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
  --exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
  --exclude=/home/juergh/tmp --exclude=/home/juergh/git
  --exclude=/home/juergh/Downloads
  --exclude=/home/juergh/.local/share/Trash
  --exclude=/home/juergh/.cache/deja-dup/tmp
  --exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
  dup --exclude=/home/juergh/.cache --include=/home/juergh
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=** --gio
  file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
  --gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
  dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19

  results in:

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1416, in do_backup
  globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
  self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
  add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824, 
in add_to_sets
  if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
  self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
  self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
  mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
  vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in 
from_string
  linelist = s.strip().split("\n")
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 10 08:05:45 2017
  InstallationDate: Installed on 2017-05-25 (137 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-10-27 Thread Peter Wallbridge

Thanks for the info. The answer is yes


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

> This could be related to OpenGL texture sizes or something similar.
> Unity7 (Compiz) has workarounds to avoid that limitation. And Xfce
> avoids it by not using hardware accelerated compositing at all (last I
> checked). It's not surprising if only Gnome Shell hits a problem like
> this...
>
> Do you get the same bug logging in to "Ubuntu" vs "Ubuntu on Xorg"?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Confirmed
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

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

Title:
  No more than 2 displays work simultaneously

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have three displays that worked fine in 17.04.
  Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
  All three seem to be properly specified in monitors.xml.
  The display setup scree detects all three.
  UBUNTU 17.10
  AMD PitcairnLSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-02-23 (242 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727955] Re: nautilus crashed with SIGABRT in g_assertion_message()

2017-10-27 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1725745, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997576/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997578/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997582/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997583/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997584/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997585/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727955/+attachment/4997586/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1725745
   nautilus crashed with SIGABRT in g_assertion_message()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1727955

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Crash on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 19:42:50 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-21 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1723840] Re: Firefox 56.0 High CPU

2017-10-27 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1723840

Title:
  Firefox 56.0 High CPU

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since the Firefox 56 upgrade, CPU utilization has been high during
  idle and light usage.  Just typing this bugreport, here's a sample
  top:

  top - 23:02:20 up 2 days, 41 min,  5 users,  load average: 0.78, 0.80, 0.77
  Tasks: 243 total,   2 running, 240 sleeping,   0 stopped,   1 zombie
  %Cpu(s):  9.0 us,  0.5 sy,  0.0 ni, 90.0 id,  0.5 wa,  0.0 hi,  0.0 si,  0.0 
st
  KiB Mem :  7130052 total,  2096428 free,  2678412 used,  2355212 buff/cache
  KiB Swap:   524280 total,   524280 free,0 used.  4027112 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
   1895 js1   20   0 4701160 2.032g 175340 R 100.0 29.9   1086:22 firefox

  
  Please let me know if I need to provide any additional debug or info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 56.0+build6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  js11957 F pulseaudio
   /dev/snd/controlC1:  js11957 F pulseaudio
  BuildID: 20171003101344
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sun Oct 15 22:57:05 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-05-01 (532 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 10.23.21.1 dev wlp7s4  proto static  metric 600 
   10.23.21.0/26 dev wlp7s4  proto kernel  scope link  src 10.23.21.18  metric 
600 
   169.254.0.0/16 dev wlp7s4  scope link  metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-5bca9619-b74f-4910-9909-6bd1b0170925
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0D881F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/28/2013:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

There is no easy way to have those actions filtered out for
GNOME/wayland only...

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

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

Status in GNOME Shell:
  Confirmed
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-screenshot source package in Artful:
  Fix Released

Bug description:
  Ubuntu 17.10 Beta
  Ubuntu session (Wayland)

  Open the Activities Overview.
  Right-click on Screenshot.

  2 of the 3 extra desktop actions don't work.

  Works
  =
  Take a Screenshot of the Whole Screen

  Doesn't Work
  
  Take a Screenshot of the Current Window
  Take a Screenshot of a Selected Area

  Other Info
  ==
  All 3 functions work if you open Screenshot and click the buttons in the app.

  The Current Window action is upstream, but Selected Area is an Ubuntu
  patch.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1723840] Re: Firefox 56.0 High CPU

2017-10-27 Thread Simone

** Also affects: firefox (Arch Linux)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1723840

Title:
  Firefox 56.0 High CPU

Status in firefox package in Ubuntu:
  Confirmed
Status in firefox package in Arch Linux:
  New

Bug description:
  Since the Firefox 56 upgrade, CPU utilization has been high during
  idle and light usage.  Just typing this bugreport, here's a sample
  top:

  top - 23:02:20 up 2 days, 41 min,  5 users,  load average: 0.78, 0.80, 0.77
  Tasks: 243 total,   2 running, 240 sleeping,   0 stopped,   1 zombie
  %Cpu(s):  9.0 us,  0.5 sy,  0.0 ni, 90.0 id,  0.5 wa,  0.0 hi,  0.0 si,  0.0 
st
  KiB Mem :  7130052 total,  2096428 free,  2678412 used,  2355212 buff/cache
  KiB Swap:   524280 total,   524280 free,0 used.  4027112 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
   1895 js1   20   0 4701160 2.032g 175340 R 100.0 29.9   1086:22 firefox

  
  Please let me know if I need to provide any additional debug or info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 56.0+build6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  js11957 F pulseaudio
   /dev/snd/controlC1:  js11957 F pulseaudio
  BuildID: 20171003101344
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sun Oct 15 22:57:05 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-05-01 (532 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 10.23.21.1 dev wlp7s4  proto static  metric 600 
   10.23.21.0/26 dev wlp7s4  proto kernel  scope link  src 10.23.21.18  metric 
600 
   169.254.0.0/16 dev wlp7s4  scope link  metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-5bca9619-b74f-4910-9909-6bd1b0170925
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0D881F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/28/2013:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

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

Title:
  No more than 2 displays work simultaneously

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

Thanks, closing the bug then

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager-openconnect (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager-openconnect (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1609700

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  
  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  
  openconnect: 7.06-2build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727911] Re: fcitx not dispaly

note that GNOME has no fcitx integration but only ibus

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727911

Title:
  fcitx not dispaly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Choice Fcitx
  No Fcitx`sign on the top right corner

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 11:07:49 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21ce]
  InstallationDate: Installed on 2017-10-24 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 4180AP3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3b93ab4f-c57d-4ccf-94fd-7c43d7fb3c36 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180AP3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4180AP3:pvrThinkPadT420:rvnLENOVO:rn4180AP3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 4180AP3
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727911] Re: fcitx not dispaly

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727911

Title:
  fcitx not dispaly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Choice Fcitx
  No Fcitx`sign on the top right corner

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 11:07:49 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21ce]
  InstallationDate: Installed on 2017-10-24 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 4180AP3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3b93ab4f-c57d-4ccf-94fd-7c43d7fb3c36 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET73WW (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180AP3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4180AP3:pvrThinkPadT420:rvnLENOVO:rn4180AP3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 4180AP3
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()

2017-10-27 Thread José Dapena Paz

This only happens on gnome-shell on wayland mode. It is evolution
indicator plugin. Unfortunately, even clicking on the checkbox to
disable it (on the list of evolution plugins) crashes evolution.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1725315

Title:
  evolution crashed with SIGSEGV in g_hash_table_lookup_node()

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Every few minutes, evolution exits the desktop.  Sometimes it will
  only stay up for seconds, and sometimes it exits in the first second.
  Occasionally it stays up for ~20 minutes.  When it is running, it
  seems to function normally.  This machine was upgraded from 17.04
  (where Evolution was stable) to 17.10 release.

  Apport crashdump analysis attached.

  Looking at /var/log/syslog after one of these crashes, I see the
  following entries:

  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: 
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string 
constant "murrine-scrollbar", expected valid string constant
  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (254): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (287): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (300): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (417): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: 
segfault at 0 ip   (null) sp 7ffee4f96718 error 14 in 
evolution[557e54c52000+7000]

  It is not clear that the first few syslog entries are related.

  Running evolution with debugging enabled:
  CAMEL_DEBUG=all evolution

  I see the following output when the crash occurs:

  ###
  message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not 
(system-flag "deleted")) (not (system-flag "junk" (and  (and  (match-all 
(not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") 
(user-flag "important" (match-all (not (or (= (user-tag "label") "work") 
(user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag 
"label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" 
(match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") 
(user-flag "todo" (match-all (not (or (= (user-tag "label") "later") 
(user-flag "$Labellater") (user-flag "later")))---
 message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1
  Segmentation fault (core dumped)

  Not sure if I can provide further information.  This crash is highly-
  repeatable, happening hundreds of times/day.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:50:57 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2017-05-31 (142 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: evolution -c current
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? ()
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from 
/usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
   org_gnome_mail_new_notify () from 
/usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
  Title: evolution crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: Upgraded to artful on 2017-10

[Desktop-packages] [Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()

2017-10-27 Thread José Dapena Paz

Workaround: uninstall evolution-indicator package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1725315

Title:
  evolution crashed with SIGSEGV in g_hash_table_lookup_node()

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Every few minutes, evolution exits the desktop.  Sometimes it will
  only stay up for seconds, and sometimes it exits in the first second.
  Occasionally it stays up for ~20 minutes.  When it is running, it
  seems to function normally.  This machine was upgraded from 17.04
  (where Evolution was stable) to 17.10 release.

  Apport crashdump analysis attached.

  Looking at /var/log/syslog after one of these crashes, I see the
  following entries:

  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: 
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string 
constant "murrine-scrollbar", expected valid string constant
  Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (254): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (287): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (300): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] 
WARNING: pipe error (417): Connection reset by peer: file 
/build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
  Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: 
segfault at 0 ip   (null) sp 7ffee4f96718 error 14 in 
evolution[557e54c52000+7000]

  It is not clear that the first few syslog entries are related.

  Running evolution with debugging enabled:
  CAMEL_DEBUG=all evolution

  I see the following output when the crash occurs:

  ###
  message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not 
(system-flag "deleted")) (not (system-flag "junk" (and  (and  (match-all 
(not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") 
(user-flag "important" (match-all (not (or (= (user-tag "label") "work") 
(user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag 
"label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" 
(match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") 
(user-flag "todo" (match-all (not (or (= (user-tag "label") "later") 
(user-flag "$Labellater") (user-flag "later")))---
 message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 
(john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1
  Segmentation fault (core dumped)

  Not sure if I can provide further information.  This crash is highly-
  repeatable, happening hundreds of times/day.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.26.1-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:50:57 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2017-05-31 (142 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: evolution -c current
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? ()
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from 
/usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
   org_gnome_mail_new_notify () from 
/usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so
  Title: evolution crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)
  UserGroups: adm cdrom docker libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bug

[Desktop-packages] [Bug 1727308] Re: when you try to change the layout for a long time reacts

thanks

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727308

Title:
  when you try to change the layout for a long time reacts

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  when you try to change the layout for a long time reacts and uses caps
  lock to change the size of letters simultaneously with the change of
  layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 17:06:55 2017
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2015-08-27 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1569613] Re: /usr/bin/nm-applet:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all:nma_icons_reload:g_closure_invoke

The reports go up to the 1.2 version so it looks fixed with the newest
series, closing the bug

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1569613

Title:
  /usr/bin/nm-
  
applet:11:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all:nma_icons_reload:g_closure_invoke

Status in Network Manager Applet:
  Won't Fix
Status in network-manager-applet package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager-applet.  This problem was most recently seen
  with version 1.1.93-1ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/833c21733fe3b1fd581cd129585c5b5ec7f8b4f2
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1569613/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1219245] Re: soffice.bin crashed with SIGSEGV in ImplDevFontListData::~ImplDevFontListData()

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

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


On 2014-01-26T10:20:39+00:00 Josep wrote:

Version-Release number of selected component:
libreoffice-core-4.1.4.2-4.fc20

Additional info:
reporter:   libreport-2.1.11
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --impress 
--splash-pipe=5
crash_function: ServerFont::Release
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.12.8-300.fc20.x86_64
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ServerFont::Release at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:341
 #1 GlyphCache::UncacheFont at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/generic/glyphs/glyphcache.cxx:236
 #2 X11SalGraphics::setFont at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:166
 #3 X11SalGraphics::SetFont at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/unx/generic/gdi/salgdi3.cxx:508
 #4 ReleaseFonts at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salgdi.hxx:224
 #5 OutputDevice::ImplUpdateFontData at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:186
 #7 OutputDevice::ImplUpdateAllFontData at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/gdi/outdev3.cxx:262
 #8 ImplHandleSalSettings at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2216
 #9 ImplWindowFrameProc at 
/usr/src/debug/libreoffice-4.1.4.2/vcl/source/window/winproc.cxx:2597
 #10 CallCallback at /usr/src/debug/libreoffice-4.1.4.2/vcl/inc/salframe.hxx:243

Potential duplicate: bug 1045497

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


On 2014-01-26T10:20:44+00:00 Josep wrote:

Created attachment 855640
File: backtrace

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


On 2014-01-26T10:20:46+00:00 Josep wrote:

Created attachment 855641
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/9


On 2014-01-26T10:20:48+00:00 Josep wrote:

Created attachment 855642
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/10


On 2014-01-26T10:20:50+00:00 Josep wrote:

Created attachment 855643
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/11


On 2014-01-26T10:20:52+00:00 Josep wrote:

Created attachment 855644
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/12


On 2014-01-26T10:20:54+00:00 Josep wrote:

Created attachment 855645
File: exploitable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/13


On 2014-01-26T10:20:56+00:00 Josep wrote:

Created attachment 855646
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/14


On 2014-01-26T10:20:57+00:00 Josep wrote:

Created attachment 855647
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/15


On 2014-01-26T10:20:59+00:00 Josep wrote:

Created attachment 855648
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/16


On 2014-01-26T10:21:01+00:00 Josep wrote:

Created attachment 855649
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/17


On 2014-01-26T10:21:03+00:00 Josep wrote:

Created attachment 855650
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1219245/comments/18


On 2014-01-27T13:18:00+00:00 David wrote:

It is not reproducible, I presume?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+b

[Desktop-packages] [Bug 412922] Re: Gnome power manager dies when AC unplugged

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

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


On 2008-08-24T09:15:49+00:00 Edouard wrote:

Created attachment 314879
my dmesg

Description of problem:
Gnome-power-man applet disappear when removing AC. In dmesg the error is:
gnome-power-man[6470] general protection ip:4105c1 sp:7fff3726ec20 error:0 in 
gnome-power-manager[40+4b000]

Version-Release number of selected component (if applicable):
gnome-power-manager-2.23.6-1.fc10.x86_64

How reproducible:
static

Steps to Reproduce:
1. Log in with AC plugged
2. Unplug AC
3. Move the mouse cursor over the g-p-m applet to see how much battery left. 
After a couple of seconds the applet crashs.
  
Actual results:
General protection fault, g-p-m applet is dead.

Expected results:
Shouldn't crash of course. Should show the time remaining on battery.

Additional info:
After that some other applets seems to crash:
gpk-update-icon[6439] general protection ip:3b21c104a8 sp:7fffd1850e18 error:0 
in libpackagekit.so.4.0.0[3b21c0+24000]

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


On 2008-09-10T12:42:13+00:00 Richard wrote:

I'm guessing the problem is now fixed in rawhide?

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


On 2008-09-11T07:47:58+00:00 Edouard wrote:

yes it's fixed in rawhide. You can close this bug. Thanks

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


** Changed in: gnome-power-manager (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/412922

Title:
  Gnome power manager dies when AC unplugged

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in gnome-power-manager package in Fedora:
  Fix Released

Bug description:
  Binary package hint: gnome-power-manager

  Description:  Ubuntu 9.04
  Release:  9.04

  
  gnome-power-manager:
Installed: 2.24.2-2ubuntu8
Candidate: 2.24.2-2ubuntu8
Version table:
   *** 2.24.2-2ubuntu8 0
  500 http://bg.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

  I removed the AC. I expected the Gnome Power manager would start
  counting how much battery life is left.

  When AC removed gnome power manager exits unexpectedly.
  /var/log/message shows me this:
  Aug 13 11:37:25 gattanegra kernel: [ 2173.541598] gnome-power-man[7054]: 
segfault at b7705fdc ip b5e852d8 sp b676533c error 7

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 430203] Re: bell.ogg is unresponsive (outside HIG response times) [regression]

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

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


On 2009-05-01T13:20:42+00:00 Davide wrote:

Description of problem:

If multiple alert-triggering events occur too close in time, the alert
sound is only played upon the first event, whereas no alert sound is
played for the remaining alert-triggering events.

Consider the case of two successive alert-triggering events. If the
delay between the two alert events is longer than the duration of the
alert sound, two distinct alert sounds are played. If, however, the
second alert event is triggered before the sound for the first alert
event has finished playing, no alert sound for the second alert event is
played. If more than two event-triggering events occur within a time
window shorter than the duration of the alert sound, only one alert
sound is played. This is bad because all alerts but the first one
essentially vanish.

In a situation where an alert is triggered every time a given key is
pressed, pressing the key twice must lead to two alert sounds, no matter
how quickly the two keypresses are done. This way, the user receives
feedback on each of the two keypresses. Issuing a single alert sound
would leave the user without feedback about the second keypress.

In order to combine the two alert sounds, two solutions come to my mind:
1. the first alert sound is interrupted and the second alert sound is played 
immediately afterwards
2. the second alert sound is superimposed to the first one
Note that when the system beep was used for alerts (prior to the introduction 
of libcanberra (*), I think), solution 1 was in place. The first beep would be 
interrupted to give way to the second beep. The user would (sloppily speaking) 
hear "Bee-bep" and hence receive the information that two separate beeps 
had been issued.

(*) Thanks to bug 498594, this situation can currently be observed by
turning the desktop effects on.


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

As in the 2009-04-30 rawhide. In particular:
libcanberra-0.12-1.fc11.x86_64
pulseaudio-0.9.15-11.fc11.x86_64
alsa-lib-1.0.19-3.fc11.x86_64


How reproducible:

always


Steps to Reproduce:

1. Ensure desktop effects are disabled (see bug 498594) and that the sound 
theme is set to
"Default"
2. Open a gnome-terminal window
3. Push the "down" arrow very quickly two times within the gnome-terminal 
window to trigger two consecutive alert events
4. Keep the "down" arrow pressed to trigger a large number of consecutive alert 
events


Actual results:

In step 3, a single alert sound is heard.
In step 4, the alert sound is played periodically, with the period equal to the 
duration of the alert sound.


Expected results:

In step 3, two alert sounds be heard (either with the first one being 
interrupted to give way to the second one, as in solution 1, or with the second 
one superimposing on the first one, as in solution 2).
In step 4, multiple alert sounds be heard (again, either according to solution 
1 or to solution 2), with the speed at which new alert sounds are started being 
equal to the keypress repeat speed specified in the keyboard preferences.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
sounds/+bug/430203/comments/0


On 2009-06-06T08:50:40+00:00 Davide wrote:

I found more information to support my request. The GNOME Human Interface 
Guidelines contain the following:
(Source:
http://library.gnome.org/devel/hig-book/stable/feedback-response-times.html.en)

"Verify that your application provides feedback within 100 milliseconds
(0.1 second) after each key press, movement of the mouse, or other
physical input from the user."

In the scenario described in the bug report, this clearly does not
happen.

I hope that libcanberra is the correct component to report the bug
against.

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
sounds/+bug/430203/comments/1


On 2009-06-09T14:56:44+00:00 Bug wrote:


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

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
sounds/+bug/430203/comments/2


On 2009-08-28T03:35:06+00:00 Lennart wrote:

This is actually a "feature" in metacity:

http://git.gnome.org/cgit/metacity/tree/src/core/display.c#n2387

It limits bell events

[Desktop-packages] [Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam

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

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


On 2015-07-10T12:50:50+00:00 Kevin wrote:

Description of problem:  After updating to wpa_supplicant 2.4-3 on July
1, was unable to connect to my corporate wifi access point.  Subsequent
downgrade to wpa_supplicant 2.3-3 fixed access problem, so I think this
is a wpa_supplicant bug


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


How reproducible:  Upgrade to 2.4-3 try to access wpa/wpa2 wifi with TTLS 
authentication that has been working for well over a year now.  Fails.  
Downgrade to 2.3-3 and it works again.


Steps to Reproduce: See above
1. Select network in NetworkManager
2. Does not connect
3. Keeps asking for password

Actual results:

>From /etc/wpa_supplicant.log after upgrade:

wlp12s0: SME: Trying to authenticate with e0:1c:41:34:19:e9 (SSID='CICS' 
freq=5220 MHz)
wlp12s0: Trying to associate with e0:1c:41:34:19:e9 (SSID='CICS' freq=5220 MHz)
wlp12s0: Associated with e0:1c:41:34:19:e9
wlp12s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
wlp12s0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlp12s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
wlp12s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty' hash=c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty' hash=c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=1 
subject='/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, 
Inc./OU=http://certificates.g
odaddy.com/repository/CN=Go Daddy Secure Certification 
Authority/serialNumber=07969287' hash=09ed6e991fc3273d8fea317d339c0204
1861973549cfa6e1558f411f11211aa3
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/OU=Domain Control 
Validated/CN=cicsnc.org' hash=598c9bcc63d9e114262181d14
dfed5372381b7ae0eb762e701b689b0e309f9b7
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:cicsnc.org
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:www.cicsnc.org
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:osx.cicsnc.org
wlp12s0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:osx2.cicsnc.org
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:handshake failure
OpenSSL: openssl_handshake - SSL_connect error:14082174:SSL 
routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small
wlp12s0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlp12s0: Authentication with e0:1c:41:34:19:e9 timed out.
wlp12s0: CTRL-EVENT-DISCONNECTED bssid=e0:1c:41:34:19:e9 reason=3 
locally_generated=1
wlp12s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CICS" auth_failures=1 
duration=10 reason=AUTH_FAILED
wlp12s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CICS" auth_failures=2 
duration=35 reason=CONN_FAILED


After downgrade:

wlp12s0: Trying to associate with e0:1c:41:34:19:e9 (SSID='CICS' freq=5220 MHz)
wlp12s0: Associated with e0:1c:41:34:19:e9
wlp12s0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlp12s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
wlp12s0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
wlp12s0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty'
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group, 
Inc./OU=Go Daddy Class 2 Certification Authori
ty'
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=1 
subject='/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, 
Inc./OU=http://certificates.g
odaddy.com/repository/CN=Go Daddy Secure Certification 
Authority/serialNumber=07969287'
wlp12s0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/OU=Domain Control 
Validated/CN=cicsnc.org'
EAP-MSCHAPV2: Authentication succeeded
wlp12s0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
wlp12s0: WPA: Key negotiation completed with e0:1c:41:34:19:e9 [PTK=CCMP 
GTK=CCMP]
wlp12s0: CTRL-EVENT-CONNECTED - Connection to e0:1c:41:34:19:e9 completed [id=0 
id_str=]
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-62 noise= txrate=6000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise= txrate=81000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise= txrate=135000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise= txrate=6000
wlp12s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise= txrate=121500
wlp12s0: CTRL-EVENT-SIGNAL-C

[Desktop-packages] [Bug 582347] Re: etags screw filenames starting with ./

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

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


On 2009-12-08T13:26:05+00:00 Sjoerd wrote:

Created attachment 376898
Patch for the problem described, replacing strcpy with memmove.

Description of problem:
This is a bug against etags.emacs which is packaged in emacs-common, but there 
is no separate component called emacs-common.  This same bug exists in 
etags.xemacs, packaged in xemacs-common.

When etags is run with filenames starting with "./", it normalizes them
to start without "./", but does so incorrectly, messing up the result.


Version-Release number of selected component (if applicable):
emacs-common-23.1-13.fc12.x86_64
xemacs-common-21.5.29-8.fc12.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a file with a C function and path e.g. src/gdk/gdk_atoms.c
2. Run /usr/bin/etags.emacs ./src/gdk/gdk_atoms.c
3. Observe the filename in TAGS
  
Actual results:
The filename recorded in the TAGS file is src/gdk/gdk_otoms.c (note "o" after 
underscore).

Expected results:
The filename should be src/gdk/gdk_atoms.c

Additional info:
The problem is a call to strcpy on overlapping buffers.  In Fedora 11 and 
before that seems to have worked, but in Fedora 12 it often does not work, at 
least not for slightly longer filenames.

The attached patch should also work for etags.xemacs in xemacs-common,
except for differing line numbers.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/0


On 2009-12-08T13:31:25+00:00 Sjoerd wrote:

Also see bug 545399 for the XEmacs version of the bug.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/1


On 2009-12-08T16:52:30+00:00 Karel wrote:

I cannot reproduce it on 32-bit Fedora, but the usage of strcpy in the
code is clearly wrong. Moreover, this bug is already fixed in the
upstream CVS.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/2


On 2009-12-08T17:29:57+00:00 Karel wrote:

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

The fix will be a part of next update.

Thanks for nicely detailed bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/3


On 2010-03-30T23:18:05+00:00 Fedora wrote:

emacs-23.1-11.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/emacs-23.1-11.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/4


On 2010-04-01T01:41:57+00:00 Fedora wrote:

emacs-23.1-11.fc11 has been pushed to the Fedora 11 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update emacs'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/emacs-23.1-11.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/5


On 2010-04-01T16:10:06+00:00 Fedora wrote:

emacs-23.1-13.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/emacs-23.1-13.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/6


On 2010-04-09T01:45:18+00:00 Fedora wrote:

emacs-23.1-13.fc11 has been pushed to the Fedora 11 testing repository.  If 
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update emacs'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/emacs-23.1-13.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/7


On 2010-04-20T13:08:50+00:00 Fedora wrote:

emacs-23.1-13.fc11 has been pushed to the Fedora 11 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/exuberant-
ctags/+bug/582347/comments/8


** Changed in: emacs23 (Fedo

[Desktop-packages] [Bug 251038] Re: Right Ctrl and Right Alt don't work

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

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-09T23:57:27+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

Pressing Ctrl-Alt ungrabs the mouse, but only if you use left Ctrl and
left Alt. Using right Ctrl, right Alt will not work nor will left Ctrl,
right Alt.

Reproducible: Always

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


On 2008-12-10T11:29:57+00:00 Daniel wrote:

What version of virt-manager, and gtk-vnc are you using ?

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


On 2008-12-10T18:08:55+00:00 Daniel wrote:

virt-manager v. 0.5.4-2ubuntu1
gtk-vnc v. 0.3.7-0ubuntu2

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


On 2008-12-10T18:16:46+00:00 Daniel wrote:

Ok, the 0.3.8 release of GTK-VNC ought to have fixed this problem. You
should file a Bug against Ubuntu gtk-vnc packages to get them updated.

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


On 2008-12-10T18:57:25+00:00 Daniel wrote:

This bug can probably be closed then.

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk-vnc in Ubuntu.
https://bugs.launchpad.net/bugs/251038

Title:
  Right Ctrl and Right Alt don't work

Status in virt-manager:
  Invalid
Status in gtk-vnc package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  Pressing Ctrl-Alt ungrabs the mouse, but only if you use Left Control
  and Left Alt. Using Right Control or Right Alt will not work. I don't
  see why there should be a difference.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check

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

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-08-24T15:56:52+00:00 Davide wrote:

Description of problem:

If the snd_hda_intel module is loaded into the kernel (for example after
starting X), the computer will not power off when "poweroff" command is called.
My computer has an Asus P5GD1 motherboard.

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


How reproducible:


Steps to Reproduce:
1.Start computer at runlevel 5
2.Log in into X and play some sound just to be sure sound module is loaded
3.System -> Shut down.

  
Actual results:
The computer doesn't power off and hangs after a message "ACPI power down
called" is displayed.

Expected results:
The computer shoud poweroff

Additional info:

I added a 'modprobe -r snd_hda_intel' line  in the stop) section of
/etc/init.d/kudzu and the computer shuts down correctly therafter.

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


On 2006-09-05T15:56:02+00:00 David wrote:

Changing to proper owner, kernel-maint.

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


On 2006-10-16T21:11:48+00:00 Dave wrote:


A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

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


On 2006-10-17T12:43:34+00:00 Davide wrote:

Even with kernel-smp 2.6.18-1.22000.fc5 the problem persists. I tried booting
with the 'acpi=ht' boot option, but the system still doesn't poweroff, the only
thing changed is the last message printed: "System halted" instead of
"acpi_power_off called".
The only way to let the computer shutdown automatically is to call modprobe -r
snd_hda_intel somewhere during the shutdown process (I moved it from kudzu to
the halt script just after the "saving mixer settings" lines).

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


On 2007-10-29T18:52:51+00:00 Stefan wrote:

I can confirm the problem still exists in Fedora 7 with the Asus P5GD1
motherboard. I've had this annoying shutdown problem for five months and finally
I have found a workaround here, thanks Davide!! Unfortunately I found the bug
still exists in Fedora 8 Test 2 as well.

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


On 2007-12-31T03:39:42+00:00 Jon wrote:

Changing version to F7 since that it the last released version that this problem
is reported in.  You mention F8T2, does it exist in released F8?

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


On 2007-12-31T03:40:19+00:00 Jon wrote:

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

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


On 2008-01-08T13:57:35+00:00 Davide wrote:

This bug is still present in F8 - kernel 2.6.23.9-85.fc8

Reply at: https://bugs.launchpad.net/ubuntu/+sou

[Desktop-packages] [Bug 237443] Re: Crash during playback with CPU time limit error

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/237443

Title:
  Crash during playback with CPU time limit error

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio package in Fedora:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  During playback pulseaudio sometimes crashes with the following error
  message:

  philipp@aineko:~$ pulseaudio 
  W: pid.c: Stale PID file, overwriting.
  ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
  ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
  Soft CPU time limit exhausted, terminating.
  Hard CPU time limit exhausted, terminating forcibly.
  Aborted

  The crashes are random and not reproduceable. So far I've only
  experienced the crashes during playback with Quod Libet. I can't say
  for sure, but it looks as if the crashes occur only under a certain
  load.

  What other info can I provide, to help pinning this down?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 548992] Re: Wireless connection frequently drops [deauthenticating by local choice (reason=3)]

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpasupplicant in Ubuntu.
https://bugs.launchpad.net/bugs/548992

Title:
  Wireless connection frequently drops  [deauthenticating by local
  choice (reason=3)]

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in wpasupplicant package in Ubuntu:
  Invalid
Status in linux package in Arch Linux:
  New
Status in Debian:
  Confirmed
Status in Fedora:
  Fix Released
Status in linux package in openSUSE:
  New

Bug description:
  Since about 8.04 or 8.10, perhaps when Ubuntu switched over to
  NetworkManager, my wireless connection has randomly dropped its
  association with the access point, about every ten minutes. For a
  while, the connection will just die, then it will be detected and
  NetworkManager will re-authenticate and re-associate.

  In Lucid Lynx, this problem is now much more frequent (often exactly
  every two or four minutes) and now Ubuntu does not report that the
  connection has dropped. Instead, it re-associates in the background,
  eventually connecting to the access point again, all behind the
  scenes. Thus, the only thing that has changed, aside from the greater
  frequency, is that Ubuntu now doesn't report that it has dropped the
  connection, which seems deceptive from previous versions.

  This may be the same bug as bug 429035, but my dmesg output is a bit
  different.  This problem occurs primarily on a WPA2 Enterprise
  network, but the problem has occurred on other network security
  configurations as well.

  dmesg output after many instances of disconnects:

  [ 5423.541343] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5425.134984] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5425.174916] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
  [ 5425.177083] wlan0: direct probe responded
  [ 5425.177087] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
  [ 5425.179379] wlan0: authenticated
  [ 5425.179399] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
  [ 5425.182881] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 
status=0 aid=68)
  [ 5425.182884] wlan0: associated
  [ 5437.562165] iwlagn :0b:00.0: iwl_tx_agg_start on ra = 
00:26:cb:17:bd:41 tid = 0
  [ 5480.893417] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5482.475859] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5482.515034] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
  [ 5482.517187] wlan0: direct probe responded
  [ 5482.517190] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
  [ 5482.518636] wlan0: authenticated
  [ 5482.518651] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
  [ 5482.522378] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 
status=0 aid=68)
  [ 5482.522381] wlan0: associated
  [ 5508.093339] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5508.107358] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
  [ 5508.107412] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5508.110595] wlan0: direct probe to AP 00:26:cb:16:e8:d1 (try 1)
  [ 5508.113114] wlan0: direct probe responded
  [ 5508.113123] wlan0: authenticate with AP 00:26:cb:16:e8:d1 (try 1)
  [ 5508.115392] wlan0: authenticated
  [ 5508.121973] wlan0: associate with AP 00:26:cb:16:e8:d1 (try 1)
  [ 5508.127254] wlan0: RX AssocResp from 00:26:cb:16:e8:d1 (capab=0x431 
status=0 aid=16)
  [ 5508.127262] wlan0: associated
  [ 5525.110100] iwlagn :0b:00.0: iwl_tx_agg_start on ra = 
00:26:cb:16:e8:d1 tid = 0
  [ 5546.029401] wlan0: deauthenticating from 00:26:cb:16:e8:d1 by local choice 
(reason=3)
  [ 5546.042276] wlan0: direct probe to AP 00:26:cb:16:e8:d1 (try 1)
  [ 5546.042311] wlan0: deauthenticating from 00:26:cb:16:e8:d1 by local choice 
(reason=3)
  [ 5546.045656] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
  [ 5546.048069] wlan0: direct probe responded
  [ 5546.048077] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
  [ 5546.049864] wlan0: authenticated
  [ 5546.077267] wlan0: associate with AP 00:26:cb:17:bd:41 (try 1)
  [ 5546.080885] wlan0: RX AssocResp from 00:26:cb:17:bd:41 (capab=0x431 
status=0 aid=79)
  [ 5546.080888] wlan0: associated
  [ 5562.875489] iwlagn :0b:00.0: iwl_tx_agg_start on ra = 
00:26:cb:17:bd:41 tid = 0
  [ 5571.881150] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5571.928466] wlan0: deauthenticating from 00:26:cb:17:bd:41 by local choice 
(reason=3)
  [ 5571.967725] wlan0: direct probe to AP 00:26:cb:17:bd:41 (try 1)
  [ 5571.969866] wlan0: direct probe responded
  [ 5571.969870] wlan0: authenticate with AP 00:26:cb:17:bd:41 (try 1)
  [ 5571.971428] wlan0: authenticated

[Desktop-packages] [Bug 616517] Re: CVE-2010-1172 dbus-glib: property access not validated

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

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


On 2010-04-23T21:16:19+00:00 Colin wrote:

The desktop team recently discovered a flaw in dbus-glib where it didn't
respect the  "access" flag on properties specified.  Basically, core OS
services like NetworkManager which use dbus-glib were specifying e.g.
the "Ip4Address" as read-only for remote access, but in fact any process
could modify it.

I have a patch for dbus-glib (attached).  However, due to the nature of the way
dbus-glib works where at build time services generate a C data structure from
XML and embed it into their binary, affected services will need to be rebuilt
(though not patched).

This affected list is for F-12; I think for RHEL5 we just need dbus-glib
and NetworkManager.

KNOWN AFFECTED SERVICES:
* DeviceKit-Power
* NetworkManager
* ModemManager

KNOWN NOT AFFECTED that claim to handle org.freedesktop.DBus.Properties:
* ConsoleKit (it denies all Properties access using dbus policy)
* gdm (ditto)
* PackageKit (all of the properties on exposed GObjects are G_PARAM_READONLY)

KNOWN NOT AFFECTED (because I audited them)
* gnome-panel (no dbus properties)
* gnome-system-monitor (ditto)

PROBABLY NOT AFFECTED
* hal (doesn't claim to handle org.freedesktop.DBus.Properties)
* polkit (uses eggdbus)
* rtkit (doesn't use dbus-glib)
* DeviceKit-disks (all its properties appear to be readonly)
* wpa_supplicant (doesn't implement Properties)
* upstart (doesn't use dbus-glib)

Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus-
glib/+bug/616517/comments/0


On 2010-04-23T21:28:02+00:00 Colin wrote:

Created attachment 408742
respect property access flags

Note that affected services will need to be recompiled.

Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus-
glib/+bug/616517/comments/1


On 2010-04-23T21:46:47+00:00 Vincent wrote:

This has been assigned CVE-2010-1172

Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus-
glib/+bug/616517/comments/2


On 2010-04-27T20:46:43+00:00 Colin wrote:

Created attachment 409584
0001-Respect-property-access-flags-for-writing-allow-disa.patch

Updated patch; this one exercises the legacy disabled cased.

Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus-
glib/+bug/616517/comments/3


On 2010-04-27T22:22:28+00:00 Dan wrote:

Latest patch appears to allow setting properties listed as 'access=read'
even though I"ve disabled legacy property access:

NetworkManager: object_registration_message: prop lookup name 'ip4_address'
NetworkManager: check_property_access: iface 
org.freedesktop.NetworkManager.Device name Ip4Address  (is set 0)
NetworkManager: check_property_access: iface 
org.freedesktop.NetworkManager.Device name Ip4Address (access type readwrite)
NetworkManager: object_registration_message: prop lookup name 'ip4_address'
NetworkManager: check_property_access: iface 
org.freedesktop.NetworkManager.Device name Ip4Address  (is set 1)
NetworkManager: check_property_access: iface 
org.freedesktop.NetworkManager.Device name Ip4Address (access type readwrite)
NetworkManager: object_registration_message: prop lookup name 'ip4_address'
NetworkManager: check_property_access: iface 
org.freedesktop.NetworkManager.Device name Ip4Address  (is set 0)
NetworkManager: check_property_access: iface 
org.freedesktop.NetworkManager.Device name Ip4Address (access type readwrite)

but introspection/nm-device.xml lists Ip4Address as access=read.


Also, you can kill the:

  /* Try both forms of property names: "foo_bar" or "FooBar"; for historical
   * reasons we accept both.
   */
  if (object_info
  && !(property_info_from_object_info (object_info, wincaps_propiface, 
requested_propname, &access_type)

'object_info' check there now in check_property_access since there's a
check for if (!object_info) just above.

Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus-
glib/+bug/616517/comments/4


On 2010-04-27T22:52:58+00:00 Dan wrote:

Nevermind about the Ip4Address thing, needed a clean rebuild locally.

So the latest patch looks good to me.

Reply at: https://bugs.launchpad.net/ubuntu/+source/dbus-
glib/+bug/616517/comments/5


On 2010-08-09T15:21:00+00:00 Colin wrote:

Created attachment 437622
patch against dbus-glib

[Desktop-packages] [Bug 583728] Re: NetworkManager ignores the rfcomm port when it gets registered in blueman

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

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


On 2010-04-24T10:33:43+00:00 Zdravko wrote:

Description of problem:


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

ModemManager-0.3-9.git20100409.fc12.i686
NetworkManager-0.8.0-6.git20100408.fc12.i686

How reproducible:

Always

Steps to Reproduce:
1. Connect to a bluetooth dun dial-up network service on a gsm phone using 
blueman

  
Actual results:

Blueman displays a message that the modem connection is available via
NetworkManager but no Wireless Modem connection is available in NM

Expected results:

The connection should be available in NM an it should be able to
connect.

Additional info:

This worked perfect before the update of NM and ModemManager

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


On 2010-04-25T06:22:41+00:00 Dan wrote:

NetworkManager includes built-in Bluetooth DUN support.  You'll want to
set up a DUN connection via the bluetooth icon's "Set up new device..."
wizard.

After you've completed that step, if the connection does not appear in
the NM menu, we'll want to grab some logs to figure out what's going on.

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


On 2010-04-25T12:59:48+00:00 Zdravko wrote:

I have done exactly that but no device shows up in NM. As I said it
worked fine prior to the update (also reverting back to previous NM and
MM made it work again..)

Below is the log..

Apr 25 13:49:35 X41 bluetoothd[2339]: link_key_request (sba=00:14:A4:DC:38:D6, 
dba=34:7E:39:5B:B1:08)
Apr 25 13:49:35 X41 bluetoothd[2339]: pin_code_request (sba=00:14:A4:DC:38:D6, 
dba=34:7E:39:5B:B1:08)
Apr 25 13:49:46 X41 bluetoothd[2339]: link_key_notify (sba=00:14:A4:DC:38:D6, 
dba=34:7E:39:5B:B1:08, type=0)
Apr 25 13:49:46 X41 dbus-daemon: Rejected send message, 2 matched rules; 
type="method_return", sender=":1.69" (uid=500 pid=2362 comm="/usr/bin/python) 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 
destination=":1.64" (uid=0 pid=2338 comm="/usr/sbin/bluetoothd))
Apr 25 13:49:46 X41 bluetoothd[2339]: probe failed with driver input-headset 
for device /org/bluez/2338/hci0/dev_34_7E_39_5B_B1_08
Apr 25 13:49:50 X41 bluetoothd[2339]: link_key_request (sba=00:14:A4:DC:38:D6, 
dba=34:7E:39:5B:B1:08)
Apr 25 13:49:50 X41 modem-manager: (rfcomm0) opening serial device...
Apr 25 13:49:51 X41 modem-manager: (rfcomm0) closing serial device...
Apr 25 13:49:51 X41 modem-manager: Generic: (tty/rfcomm0) WARNING: missing udev 
'device' file
Apr 25 13:49:51 X41 modem-manager: (rfcomm0) opening serial device...
Apr 25 13:49:51 X41 modem-manager: (Generic): GSM modem 
/sys/devices/pci:00/:00:1d.2/usb4/4-1 claimed port rfcomm0
Apr 25 13:49:51 X41 modem-manager: (rfcomm0) closing serial device...
Apr 25 13:49:51 X41 NetworkManager:  ignoring modem 'rfcomm0' (no 
associated Bluetooth device)

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


On 2010-04-26T06:08:53+00:00 Dan wrote:

Ok, this shows that ModemManager is finding the modem correctly, but the
configuration that NM requires (that the bluetooth wizard is supposed to
write to GConf) somehow isn't getting set correctly.

Any chance you can take a screenshot of the applet menu for me after
you've completed the bluetooth wizard?  And you are using the gnome-
bluetooth icon to set up the device, *not* blueman, correct?

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


On 2010-04-26T10:15:13+00:00 Zdravko wrote:

Created attachment 409128
Screenshot

I am using only blueman..A screenshot is attached..

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


On 2010-04-26T22:32:35+00:00 Dan wrote:

You're going to need to use the gnome-bluetooth applet, not blueman.  I
have no idea what blueman is doing underneath, but it's not really a
supported way to interact with NetworkManager.  NM has the functionality
that you're looking for, so if there's a problem with NM or nm-applet's
handling of DUN, then we can try to fix this bug.

But otherwise, it's a blueman bug.  The nm-applet GConf data is an
implementation detail that's not public API,

[Desktop-packages] [Bug 548652] Re: menu mouse-scrolling broken, when themes enable gtk-auto-mnemonics

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

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


On 2010-04-15T20:14:46+00:00 Bruno wrote:

Description of problem:
When I scroll down in a menu (say the graphics menu entries) that is too large 
to fit on the screen the menu items listed scrolls. But when I move the mouse 
back to select an item I made visible, the menu snaps back to the top 
preventing selection of the desired item if it isn't visible while at the top 
of the menu. I am not sure exactly when this changed or which component is 
responsible.

If this can be confirmed it should probably be marked as a release
blocker.

Version-Release number of selected component (if applicable):
gnome-desktop-2.30.0-1.fc13.i686

How reproducible:


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


Expected results:


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/7


On 2010-04-16T15:24:07+00:00 Bruno wrote:

I have another machine at work with a similar package set installed that
isn't exhibiting this problem. So I need to look and see what's
different.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/8


On 2010-04-19T15:10:44+00:00 Bruno wrote:

I still haven't figured out why one machine has that problem. I have
three other f13 machines that I haven't been able to duplicate the
problem on.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/9


On 2010-04-21T02:05:49+00:00 Bruno wrote:

I played with this some more and it doesn't do it on all of the large
menu lists. But it isn't consistent about which ones it happens with.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/10


On 2010-04-28T14:29:08+00:00 Bruno wrote:

I found that this issue is related to the theme being used. On the machine with 
problems I usually use Fedora with Echo icons. When I tried using Bluecurve 
(with or without Echo Icons) I didn't see the problem. Switching back caused it 
to reappear.
I need to check to see if I have a corrupted install of that theme and whether 
or not the same problem is visible on a couple of other machines. (I typically 
don't mess with the theme on my scratchish machines, so they are probably using 
Bluecurve.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/12


On 2010-04-28T14:36:01+00:00 Bruno wrote:

I did see that Fedora really is just Clearlooks. And selecting the
Clearlooks theme also resulted in having the menu selection issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/13


On 2010-04-28T16:10:00+00:00 Bruno wrote:

I am seeing this on a second computer now. I have it occurring on both
i686 and x86_64 arches. I am having trouble reproducing it on an i686
machine that doesn't have the kitchen sink installed on it.

My next plan is try to some older versions of the Clearlooks theme. Even
if that isn't the root of the problem, being able to isolate what
triggers it would be useful to know.

I might also try older desktops, but that seems likely to be a lot more
involved.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/14


On 2010-04-28T18:25:15+00:00 Bruno wrote:

I looked and gnome-theme-curvylooks has changed for about 9 months which
predates me seeing the issue. So it seems unlikely to be something
triggered by a change in that package.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/15


On 2010-05-04T20:15:03+00:00 Colin wrote:

Me too.  Worked in F12 on same hardware.

See also ubuntu: https://bugs.launchpad.net/fedora/+bug/548652

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/16


On 2010-05-29T18:42:28+00:00 Erwan wrote:

Same issue after a upgrade from F12.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/548652/comments/19


On 2010-05-30T1

[Desktop-packages] [Bug 291062] Re: MASTER - Network Manager sometimes has "enable networking" unchecked/disabled when resuming from suspend

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

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-05-05T12:26:11+00:00 Jerry wrote:

Description of problem:
Networking is disabled by state file after power loss drained laptop battery

Version-Release number of selected component (if applicable):
NetworkManager-0.8.0-7.git20100422.fc13.i686

How reproducible:
always

Steps to Reproduce:
1.login to KDE on laptop
2.disconnect power, and let battery die
3.plugin power and boot - no network.
  
Actual results:
no network management

Expected results:
network management

Additional info:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571331

Note in step 3. above there are actually two boots as the resume from
power mgmt suspend never works for me - I force power off and restart.

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


On 2010-05-10T13:11:17+00:00 Oded wrote:

I have the same problem after trying to recover from a failed suspend.

Removing the state file at /var/lib/NetworkManager and restarting
NetworkManager solved the problem for me.

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


On 2010-05-11T03:00:39+00:00 Justin wrote:

Same issue here on a Dell Studio 1558, 03:00.0 Network controller: Intel
Corporation Centrino Advanced-N 6200 (rev 35),
NetworkManager-0.8.0-13.git20100509.fc13

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


On 2010-05-16T11:22:23+00:00 Joel wrote:

Additional evidence:

I had this happen to me, apparently when my daughter accidentally hit
the sleep button on the keyboard or selected hibernate instead of
shutdown from the shutdown menu.

The file mentioned above,

/var/lib/NetworkManager/NetworkManager.state

shows the wired network disabled and the wireless enabled.

The box is a desktop, by the way, not a laptop. No battery. No wireless
hardware of any sort. 32 bit, single CPU Sempron. (Should I attach a
dmesg?)

Oh, and it's running Fedora 12.

Editing the file instead of deleting it also seems to unclog the
networking stuff.

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


On 2010-05-17T23:55:41+00:00 Dan wrote:

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

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


On 2010-05-18T00:10:11+00:00 Dan wrote:

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

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


On 2010-05-19T21:46:39+00:00 Richard wrote:

When this symptom has happened to me, the following command instantly fixes it:
nmcli nm wakeup

The circumstances seem to be that NM sets NetworkingEnabled to false in
the /var/lib/NetworkManager/NetworkManager.state file but the situation
can arise where NM cannot reset it.

My guess is that this flag is set at suspend time (and of course at
'nmcli nm sleep' time as well).  Further, I guess that NM expects a
'suspend' to be followed by a 'resume', which should reset this flag to
be NetworkingEnabled=true.  But if the latter fails, as it stands manual
intervention is reqired.

The failure can occur in at least these two ways:  the hardware's
suspend function is broken and a power-on reboot is required, and the
battery discharges and a power-on reboot is required.  The
NetworkingEnabled=false flag remains set in these cases, and manual
intervention is required.  But a naïve user is at a complete loss what
to do.  Even sophisticated users, e.g., helpers on the #fedora channel
of freenode, are at a loss, as I've seen.  NM should perhaps set the
flag to true when freshly started?

What are the exact and complete semantics of this
NetworkingEnabled=false flag?

Is there a valid case where a freshly started NetworkManager service can
expect NetworkingEnabled=false to be the proper setting?  If there is,
could a freshly started NM pop up a graphic window asking the user if
enabling was okay?

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

--

[Desktop-packages] [Bug 1727975] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程已安装 post-installation 脚本返回错误状态 1

2017-10-27 Thread wangqian

Public bug reported:

it just failed!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Oct 27 16:17:09 2017
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
InstallationDate: Installed on 2017-10-24 (2 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: libxml2
Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 
子进程 已安装 post-installation 脚本 返回错误状态 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1727975

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

Status in libxml2 package in Ubuntu:
  New

Bug description:
  it just failed!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Oct 27 16:17:09 2017
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-10-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727975] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 子进程已安装 post-installation 脚本返回错误状态 1

2017-10-27 Thread Mattia Rizzolo

** Package changed: libxml2 (Ubuntu) => python2.7 (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1727975

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

Status in python2.7 package in Ubuntu:
  New

Bug description:
  it just failed!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Oct 27 16:17:09 2017
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-10-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1727975/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change

** Changed in: libinput
   Status: Unknown => In Progress

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724259

Title:
  gnome-shell frozen and using 100% CPU after docking and display
  configuration change

Status in libinput:
  In Progress
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libinput package in Ubuntu:
  Confirmed

Bug description:
  I have been having regular system freezes after switching from using
  my laptop stand-alone to waking it up on a docking station with an
  external monitor. I have seen this using two identical docking station
  plus monitor combinations. I am still trying to find a pattern.  I was
  able to ssh in and use apport to save this bug information.  The
  gnome-shell process was hung at 100% CPU utilisation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:56:34 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['gnome-terminal']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-05-31 (504 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1726753] Re: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique

2017-10-27 Thread Trochet Yannick

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

Il fonctionne dans LibreOffice Writter, dans Gedit et dans le terminal (c'est 
déjà bien!).
Aujourd'hui, je n'ai pas eu de message d'erreur (jusqu'à maintenant).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1726753

Title:
  Après  le démarrage de la session, et au bout de 30 secondes environ,
  un message apparaît signalant qu'une erreur s'est produite. D'autre
  part le clavier numérique ne fonctionne pas.

Status in nautilus package in Ubuntu:
  New

Bug description:
  Il m'est difficile d'en dire plus. Sauf que je constate que ces bogues 
arrivent après la mise à niveau de Ubuntu 17.04 vers Ubuntu 17.10.
  trochet@trochet-ubuntu16:~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  Quel est le package utilisé juste après l'ouverture de session, étant donné 
que je n'ai rien ouvert?
  What you expected to happen? J'aimerais pouvoir continuer dans ma session.
  What happened instead? Sans etre dérangé par des messages d'erreur.
  Je viens aussi de voir que l'accent grave du verbe etre ne s'affiche pas.
  Avec la version précédente (Ubuntu 16.04 et 17.04) mon clavier (version 
Français-variante) fonctionnait parfaitement.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 08:43:15 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-07 (747 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: nautilus-desktop
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
   XPending () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
  Title: nautilus-desktop crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-10-27 Thread floriankeim

Now the drivers install without problems. However, I still can't connect
to the scanner (neither in iscan nor in simple-scan). Simple scan still
tells me that an epson scanner is recognised, but drivers are missing.

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

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

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1726753] Re: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique

2017-10-27 Thread Trochet Yannick

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

Plus précisément, il semble que le clavier numérique ne fonctionne pas
dans firefox.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1726753

Title:
  Après  le démarrage de la session, et au bout de 30 secondes environ,
  un message apparaît signalant qu'une erreur s'est produite. D'autre
  part le clavier numérique ne fonctionne pas.

Status in nautilus package in Ubuntu:
  New

Bug description:
  Il m'est difficile d'en dire plus. Sauf que je constate que ces bogues 
arrivent après la mise à niveau de Ubuntu 17.04 vers Ubuntu 17.10.
  trochet@trochet-ubuntu16:~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  Quel est le package utilisé juste après l'ouverture de session, étant donné 
que je n'ai rien ouvert?
  What you expected to happen? J'aimerais pouvoir continuer dans ma session.
  What happened instead? Sans etre dérangé par des messages d'erreur.
  Je viens aussi de voir que l'accent grave du verbe etre ne s'affiche pas.
  Avec la version précédente (Ubuntu 16.04 et 17.04) mon clavier (version 
Français-variante) fonctionnait parfaitement.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 08:43:15 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-07 (747 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: nautilus-desktop
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
   XPending () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
  Title: nautilus-desktop crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 617487] Re: pitivi crashed with PipelineError in setState()

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pitivi in Ubuntu.
https://bugs.launchpad.net/bugs/617487

Title:
  pitivi crashed with PipelineError in setState()

Status in PiTiVi:
  Expired
Status in pitivi package in Ubuntu:
  Fix Released
Status in pitivi package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: pitivi

  I was trying to turn multiple videos into one big one and then it
  crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: pitivi 0.13.4-3ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
  Uname: Linux 2.6.35-14-generic i686
  Architecture: i386
  Date: Fri Aug 13 11:52:15 2010
  ExecutablePath: /usr/bin/pitivi
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  InterpreterPath: /usr/bin/python2.6
  PackageArchitecture: all
  ProcCmdline: python /usr/bin/pitivi
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/pitivi']
  SourcePackage: pitivi
  Title: pitivi crashed with PipelineError in setState()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 388063] Re: The small icon in the upper left corner is absent

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

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-01T15:59:13+00:00 Felix wrote:

In todays rawhide inkscape does not have an icon. Therefore it is hard
to find the window in the application switcher.

The icon is present in the start menu and in help -> about inkscape.

See attached screenshot for more information.

[fm@thinkpad scor]$ rpm -q inkscape
inkscape-0.47-0.16.pre3.20091017svn.fc12.i686

Reply at: https://bugs.launchpad.net/inkscape/+bug/388063/comments/21


On 2009-11-01T15:59:48+00:00 Felix wrote:

Created attachment 367014
screenshot

Reply at: https://bugs.launchpad.net/inkscape/+bug/388063/comments/22


On 2009-11-03T19:20:10+00:00 Lubomir wrote:

A work-around for the problem was added in package targeted for F-12:
inkscape-0.47-0.16.pre4.20091101svn.fc12

Reply at: https://bugs.launchpad.net/inkscape/+bug/388063/comments/27


On 2009-11-16T14:49:44+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/inkscape/+bug/388063/comments/28


On 2010-11-04T06:54:32+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/inkscape/+bug/388063/comments/50


On 2010-12-04T03:33: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/inkscape/+bug/388063/comments/51


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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/388063

Title:
  The small icon in the upper left corner is absent

Status in Inkscape:
  Fix Released
Status in inkscape package in Ubuntu:
  Fix Released
Status in inkscape package in Debian:
  Fix Released
Status in inkscape package in Fedora:
  Won't Fix

Bug description:
  The small icon in the left upper corner of the window is absent in the
  prerelease inkscape_0.47~pre0-0ubuntu1~8.04_i386. It is present in the
  0.46 version for Ubuntu 8.04 Intel. See attachment.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https:/

[Desktop-packages] [Bug 460656] Re: Directly use the server/folder given in 'Connect to Server...' dialog

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

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-05-19T20:25:59+00:00 Bill wrote:

Description of problem:

I've been attempting to test the sftp backend by pointing it at
fedorapeople.org.

This appears to be nearly impossible, as it seems wholly unable to
actually switch to the user's home dir, even if you pass it as the
'folder' in the 'Connect to Server' dialog.

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

deja-dup-14.1-1.fc13.x86_64
duplicity-0.6.08b-1.fc13.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Choose 'Connect to Server'
2. Choose sftp, fedorapeople.org
3. Either leave the defaults, or select folder '/home/fedora/'

Actual results:

deja-dup insists on always trying to write to fedorapeople's root
directory. Needless to say, this fails.

Expected results:

Not that.

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

On 2010-06-05T02:23:18+00:00 Michael wrote:

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

Basically, when you use the 'Connect to Server' dialog it would ideally
set your location to the destination you picked.  But it doesn't yet for
technical reasons.

Then, when you try to select the server from the combo box, you are
doing just that -- it's just a standard GtkFileChooserButton.  So to
pick a subfolder, you need to choose 'Other...' and navigate to the
folder you want *again*.

Not a great user interaction, but I'm waiting for
https://bugzilla.gnome.org/show_bug.cgi?id=584871 to be fixed in
Nautilus before I can do something more clever.

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

On 2010-11-06T21:12:02+00:00 Adam wrote:

Even thou there is now a directory and bookmark option in deja-dup it
ignores this setting wish sftp when you enter it, then it calls the
duplicity with no directory to re/store. If I copy the duplicity command
line and add the directory manually then it works. Not to mention your
"Not a great user interaction" describing very well the procedure of
adding any kind of backup directory in deja-dup.

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

On 2010-12-08T08:40:23+00:00 Fedora wrote:

deja-dup-16.1-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/deja-dup-16.1-2.fc14

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

On 2010-12-08T21:36:29+00:00 Fedora wrote:

deja-dup-16.1-2.fc14 has been pushed to the Fedora 14 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 deja-dup'.  You can provide 
feedback for this update here: 
https://admin.fedoraproject.org/updates/deja-dup-16.1-2.fc14

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

On 2010-12-09T13:07:07+00:00 Adam wrote:

This problem is not fixed with this release. IMHO it has to do something
with nautilus but ATM this still does not work.

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

On 2010-12-09T13:13:07+00:00 Michael wrote:

Right, this isn't addressed yet.  I plan to make the whole thing nicer
for Fedora 15.

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

On 2010-12-10T06:59:19+00:00 Rahul wrote:

Excluded this update from the bug fix list

https://admin.fedoraproject.org/updates/edit/deja-dup-16.1-2.fc14

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

On 2011-03-12T14:49:44+00:00 Matěj wrote:

Created attachment 483899
screencast of the issue

(In reply to comment #0)
> This appears to be nearly impossible, as it seems wholly unable to actually
> switch to the user's home dir, even if you pass it as the 'folder' in the
> 'Connect to Server' dialog.

I have actually exactly opposite experiene ... when trying to save
b

[Desktop-packages] [Bug 334626] Re: Xorg intermittent segv in XkbSendMap in ProcXkbGetKbdByName

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

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-11-02T19:51:53+00:00 Noel wrote:

Description of problem:

If I configure a second monitor (projector) using *either* the Fedora
provided nvidia driver *or* the nvidia supported driver, and select a
menu in the Fedora provided OpenOffice 3 Impress application (I am
trying to do a presentation on dual-monitors), the entire X11 session
crashes and restarts.

Please note: the exact same scenario on the same hardware (multi-boot)
works flawlessly with Ubuntu 8.10 using the same 177.80 nvidia driver
and Ubuntu PPA build of OpenOffice 3, both with and without the new
Presenter Mode plugin (Fedora provides the plugin as standard).

This is completely reproducible.

Steps to Reproduce:
1. Connect 2nd display.
2. Configure 2nd display using the appropriate display manager (depending on 
which driver is in use)
3. Open a presentation in OOo3 Impress, and click the Slide Show menu to 
attempt to select Slide Show Settings.

Actual results:

One of two things will happen.  Either the menu will work because OOo3
does not realize that you have configured the 2nd display (and Slide
Show Settings ... will have the option to select a 2nd display grayed
out), or the entire X11 session will terminate, and you'll have to wait
for it to restart at the login dialog.

Expected results:

The menu should appear, and you should be able to select that the
presentation monitor will be on the 2nd display, so that you can start a
slide show using the new Presenter mode.

I'll be happy to provide whatever follow-up information you desire.

ThinkPad T61p 6457-7WU, Fedora 10 with all updates as of today.

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

On 2008-11-02T23:18:11+00:00 Caolan wrote:

The *entire* X session exits ?

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

On 2008-11-02T23:21:38+00:00 Caolan wrote:

There is a few multihead fixes for OOo we're not carrying in that
version which I've since added in, but for the entire session to crash
suggests more a more fundamental X level bogusity.

caolanm->mcepl: Can you see this problem ?

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

On 2008-11-03T11:42:26+00:00 Matěj wrote:

Reporter, there are two things:

a) if you are switching between non-packaged version of nvidia binary-only 
driver and nv open source driver (BTW, have you tried nouveau?) there are some 
things which nvidia driver changes outside of the driver itself. So, please, 
make sure, that your packages are not changed (rpm -Va; or look for more 
detailed instructions at 
https://fedoraproject.org/wiki/Xorg/3rd_Party_Video_Drivers).
b) Please, attach /var/log/Xorg.*.log, /var/log/dmesg, /var/log/messages and 
/etc/X11/xorg.conf (if there is any) as separate uncompressed attachments to 
this log.

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

On 2008-11-04T06:48:02+00:00 Noel wrote:

> The *entire* X session exits ?

As in X restarts, and I have to log back in, yes.

> There is a few multihead fixes for OOo we're not carrying in that
> version which I've since added in

Where can I find those?  I update from rawhide daily.

> if you are switching between non-packaged version of nvidia
> binary-only driver and nv open source driver ...

First of all, I installed the binary only AFTER reproducing this error
in the first place.  Second, I uninstalled the binary, rebooted, and
checked to make sure that Xorg.0.log had no references to any nvidia
provided code.  That said ...

> please, make sure, that your packages are not changed (rpm -Va)

OK (but, again, I reproduced this BEFORE ever installing the nvidia
driver)

> Please, attach /var/log/Xorg.*.log, /var/log/dmesg,
> /var/log/messages and /etc/X11/xorg.conf

Should be able to do that sometime this week.

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

On 2008-11-10T14:39:56+00:00 Noel wrote:

Created attachment 323070
/var/log/dmesg

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

On 2

[Desktop-packages] [Bug 245770] Re: [CVE-2008-2927] MSN integer overflow in Pidgin

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

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-02T13:14:49+00:00 Josh wrote:

An integer overflow in Pidgin's MSN protocol handler could allow malformed SLP
message to cause an integer overflow, which could result in arbitrary code
execution.

This flaw is only exploitable by individuals who can message a user, which is
controlled by the Pidgin privacy setting.  The default setting is to only allow
messages from users in the buddy list.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/245770/comments/0


On 2008-07-02T13:14:49+00:00 Josh wrote:

Created attachment 310788
Proposed upstream patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/245770/comments/1


On 2008-07-02T14:37:24+00:00 Warren wrote:

#
#
# patch "libpurple/protocols/msnp9/slplink.c"
#  from [0148f31961bbe4a9a992377e70db082952505db4]
#to [f65596ea173bf7c9c1114edd7599140f470e7788]
#

--- libpurple/protocols/msnp9/slplink.c 0148f31961bbe4a9a992377e70db082952505db4
+++ libpurple/protocols/msnp9/slplink.c f65596ea173bf7c9c1114edd7599140f470e7788
@@ -597,7 +597,7 @@ msn_slplink_process_msg(MsnSlpLink *slpl
}
else if (slpmsg->size)
{
-   if ((offset + len) > slpmsg->size)
+   if (G_MAXSIZE - len < offset || (offset + len) > slpmsg->size)
{
purple_debug_error("msn", "Oversized slpmsg\n");
g_return_if_reached();

For reference, this is the upstream patch that went into 2.4.3.  I need to
backport this for pidgin-2.3.1 in RHEL4 and RHEL5, and pidgin-1.5.x in RHEL3.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/245770/comments/2


On 2008-07-04T02:01:38+00:00 Josh wrote:

I'm making this bug public in order to avoid creating confusion.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/245770/comments/3


On 2008-08-27T19:50:04+00:00 Tomas wrote:

Upstream advisory:
  http://www.pidgin.im/news/security/?id=25

Fixed upstream in: 2.4.3

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/245770/comments/8


On 2009-06-09T07:14:17+00:00 Red wrote:

This issue was addressed in:

Red Hat Enterprise Linux:
  http://rhn.redhat.com/errata/RHSA-2008-0584.html

Fedora:
  https://admin.fedoraproject.org/updates/F10/FEDORA-2009-5597
  https://admin.fedoraproject.org/updates/F11/FEDORA-2009-5583
  https://admin.fedoraproject.org/updates/F9/FEDORA-2009-5552

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


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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/245770

Title:
  [CVE-2008-2927] MSN integer overflow in Pidgin

Status in pidgin package in Ubuntu:
  Fix Released
Status in pidgin package in Debian:
  Fix Released
Status in pidgin package in Fedora:
  Fix Released

Bug description:
  Binary package hint: pidgin

  CVE-2008-2927 is a remote buffer overflow vulnerability in the MSN
  protocol handler. Apparently it can lead to arbitrary code execution.
  It's not yet in the public vulnerability databases, so please see the
  Debian bug for reference: . I think it is the same issue as
  described in this Bugtraq post
  .

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 207744] Re: Clicking notification panel icon doesn't switch desktops

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

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


On 2007-09-26T18:09:57+00:00 Bill wrote:

Description of problem:

When I open a new tab (via right click on a terminal, clicking on something in
liferea, whatever), firefox immediately jumps onto the current workspace.

This is irritating.

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

firefox-2.0.0.6-11.fc8

Additional info:

Seems related to the startup notification patch, as it worked ok in
2.0.0.6-8.fc8.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/0


On 2007-10-01T00:17:03+00:00 Adam wrote:

I will second this. Very irritating!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/1


On 2007-10-01T19:22:40+00:00 Christopher wrote:

Owen says this is a metacity bug.  The following program also hops
windows.

#!/bin/env python

import gtk
import gobject
w = gtk.Window()
w.set_title("Foo")
w.show()

def on_timeout():
w.present()
return False

gobject.timeout_add(5000, on_timeout)
gtk.main()


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/2


On 2007-10-01T19:23:35+00:00 Christopher wrote:

er, hops workspaces

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/3


On 2007-10-01T19:34:29+00:00 Colin wrote:

To give some background on this issue, Firefox now supports startup 
notification:
https://bugzilla.mozilla.org/show_bug.cgi?id=223492

The issue in this bug only occurs when there are multiple workspaces.

Removing this Firefox patch would be a regression in the single workspace case
because it would require clicking on a flashing browser entry in the task list
after activating an external link.

>From IRC:

 walters: metacity could look at the window role and alter the behavior
based on that


Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/4


On 2007-10-01T19:48:25+00:00 Bill wrote:

FWIW, commenting out the call to gdk_window_focus() in the patch makes it DTRT
for me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/5


On 2007-10-01T20:00:33+00:00 Owen wrote:

Actually, what I meant was that based on the "type" of the window application
vs. dialog, you could do different things.

A application never, under any circumstances, should be moved between
desktops.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/6


On 2007-10-01T20:03:13+00:00 Colin wrote:

Bill, what effect does that have in the single-workspace case?

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


On 2007-10-01T20:04:24+00:00 Colin wrote:

Also, I've filed this bug upstream here:

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

Since there seems to be agreement this is an upstream Metacity issue, please
continue discussion there.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/8


On 2007-10-01T20:10:27+00:00 Bill wrote:

Colin: when it's on the same workspace, I get the throbbing entry in the panel.
When it's on the other workspace, I don't.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/9


On 2007-10-11T20:06:50+00:00 David wrote:

We need to fix this for F8...

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


On 2007-10-11T21:48:48+00:00 Jeremy wrote:

This is also happening in compiz... so more than just metacity at work
here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/11


On 2007-10-11T23:26:44+00:00 Christopher wrote:

Jeremy: not quite...

in metacity, the _window_ switches to the current workspace.

In compiz, the _active workspace_ switches.

[Desktop-packages] [Bug 658069] Re: Empty files written over gvfs by some editors

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/658069

Title:
  Empty files written over gvfs by some editors

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Maverick:
  Fix Released
Status in gvfs package in Fedora:
  Won't Fix

Bug description:
  Non-GIO programs truncate files when saving.

  A bug in either FUSE or gvfs-fuse glue code has been discovered which
  causes some applications to truncate files to 0 bytes on save.

  REGRESSION POTENTIAL: There is currently no patch for fuse, the
  upstream gvfs developer has proposed a patch that deals with truncate
  at the gvfs side. The patch has only been applied to Fedora 15, it
  hasn't yet been backported to neither Fedora 13 nor Fedora 14 so it
  hasn't been tested other than for it fixing the reported issue.

  I guess we should upload it to natty first for preliminary testing but
  the data-loss is quite huge problem for people affected.

  TEST CASE: A write-access to any gvfs powered remote share is required, the 
following options assume you have mounted it through the Places->Connect to 
Server... dialog (or using an existing bookmark).
  Create a file with some content, for example by doing:
  $ echo "test" > test.file
  then edit the file using nano, add some more text and save (^X, Y, [ENTER]), 
after that the file is empty.
  Same actions with proposed update should result in a file that has entered 
text.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 583056] Re: Assertion error (r == n_visible_rows) in gtk_file_system_model_sort causes applications to crash

** 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 Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/583056

Title:
  Assertion error (r == n_visible_rows) in gtk_file_system_model_sort
  causes applications to crash

Status in GTK+:
  Fix Released
Status in OpenOffice:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in Fedora:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  OOo crashes with the following error message:
  
Gtk:ERROR:/build/buildd/gtk+2.0-2.20.0/gtk/gtkfilesystemmodel.c:746:gtk_file_system_model_sort:
 assertion failed: (r == n_visible_rows)

  Steps to reproduce:
  Create a file called /tmp/foo.xls
  Select file->open in oocalc, browse to /tmp and select 'Microsoft Excel 2007 
XML' from the file formats list
  Rename foo.xls to foo.xlsx

  
  Note that the steps to reproduce don't seem to be entirely bullet proof. If 
I, for example, create the file in some other directory than /tmp OOo may not 
crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org (not installed)
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Wed May 19 22:25:26 2010
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727997] [NEW] Missing Save and continue option

2017-10-27 Thread Hannie Dumoleyn

Public bug reported:

When trying to translate the untranslated strings, I do not get the
"Save and continue" option.

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1727997

Title:
  Missing Save and continue option

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  When trying to translate the untranslated strings, I do not get the
  "Save and continue" option.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727995] [NEW] Backup Failed with Unknown Error (MemoryError)

2017-10-27 Thread Julian Felix Rost

Public bug reported:

Description:Ubuntu 17.10
Release:17.10
duplicity:
  Installed: 0.7.12-1ubuntu1
  Candidate: 0.7.12-1ubuntu1
  Version table:
 *** 0.7.12-1ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

Expected behavior: Backs up target data directories at specified scheduled 
times.
Actual behavior: Errors out and aborts backup with stacktrace (see screenshot 
and below). 

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1546, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
  File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
setrorps(overflow, elems)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
elems[i] = iter_list[i].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
tarinfo_list = [tar_iter.next()]
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 763, in get_fileobj_iter
manifest = backup_set.get_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
return self.get_local_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
  File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in 
from_string
self.files_changed = list(map(parse_fileinfo, match.group(3).split('\n')))
MemoryError

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

** Attachment added: "Screenshot of Popup Error Message"
   
https://bugs.launchpad.net/bugs/1727995/+attachment/4997735/+files/Screenshot%20from%202017-10-27%2011-34-08.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1727995

Title:
  Backup Failed with Unknown Error (MemoryError)

Status in duplicity package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10
  duplicity:
Installed: 0.7.12-1ubuntu1
Candidate: 0.7.12-1ubuntu1
Version table:
   *** 0.7.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected behavior: Backs up target data directories at specified scheduled 
times.
  Actual behavior: Errors out and aborts backup with stacktrace (see screenshot 
and below). 

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manif

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

2017-10-27 Thread Andrés Alcarraz

Doug that's exactly what the bug says and why I filled it, you are not
being asked for the auth code simply because there is a bug in the
login. I filled the bug, the annoyance is because the application is
asking for a password it doesn't need.

My feeling is that it is using some remanent pre-update account. In
response Sebastian Bacher, I don't believe it's an upstream bug, since
is generated in the upgrade process, I think the accounts were ill
transformed in the upgrade process, either way I generated a bug report
in gnome-calendar: https://bugs.launchpad.net/ubuntu/+source/gnome-
calendar/+bug/1726922

** Description changed:

  Once in a while, perhaps two or three times a day gnome-calendar pops up
  a dialog asking for my google password.
  
  I have two online google accounts set, but the problem begun after I
  upgraded from zesty, where I had those two accounts as well. They didn't
  appear in the new settings application, but still gnome-calendar was
  asking for the password. One of them has two phase authentication set
  and the other not.
  
  After I added the online accounts in the new settings app, the calendar
  is synchronized but it still popping the authentication window and is
  very annoying.
+ 
+ bug report in gnome-calendar: https://bugs.launchpad.net/ubuntu/+source
+ /gnome-calendar/+bug/1726922
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.2-1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:45:09 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-04-14 (193 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, user)
-  LANGUAGE=es_UY:es
-  LANG=es_UY.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, user)
+  LANGUAGE=es_UY:es
+  LANG=es_UY.UTF-8
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)

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

Title:
  gnome-calendar keeps asking for my google password

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Once in a while, perhaps two or three times a day gnome-calendar pops
  up a dialog asking for my google password.

  I have two online google accounts set, but the problem begun after I
  upgraded from zesty, where I had those two accounts as well. They
  didn't appear in the new settings application, but still gnome-
  calendar was asking for the password. One of them has two phase
  authentication set and the other not.

  After I added the online accounts in the new settings app, the
  calendar is synchronized but it still popping the authentication
  window and is very annoying.

  bug report in gnome-calendar:
  https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726922

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.2-1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:45:09 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-04-14 (193 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=es_UY:es
   LANG=es_UY.UTF-8
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1723370] Re: Processes % CPU column is inaccurate (only ever an integer multiple of the number of CPUs)

2017-10-27 Thread Daniel van Vugt

** Changed in: gnome-system-monitor (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1723370

Title:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs)

Status in Gnome System Monitor:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  In Progress

Bug description:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs).

  So for example on my desktop with 8 CPU threads, the Processes tab
  only ever shows a process is using either 0%, 8%, 16%, 24%, 32%

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-system-monitor 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 13 17:18:24 2017
  InstallationDate: Installed on 2017-05-03 (163 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/1723370/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1725582] Re: System freeze on boot since upgrade to 17.10

2017-10-27 Thread Frederic berat

Changed package to kernel-package as it seems more related to that than
the Xorg.

** Package changed: xorg (Ubuntu) => kernel-package (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1725582

Title:
  System freeze on boot since upgrade to 17.10

Status in kernel-package package in Ubuntu:
  New

Bug description:
  This freeze appears on each boot since the dist upgrade to 17.10 (from 17.04) 
with the following kernel: linux-image-4.13.0-16-generic.
  The ssh connexion becomes available after 3 to 5 minutes, and the login 
screen after more than 20 minutes.

  This issue doesn't show up in recovery mode.
  This issue doesn't show up with the previous kernel (from 17.04): 
linux-image-4.10.0-37-generic.

  I Also tried the mainline drm-current: 
linux-image-4.14.0-996-generic_4.14.0-996.201710202201_amd64.deb
  The issue is not visible then, but I don't have ethernet access any longer 
(which may be completely unrelated).

  lsb_release -rd:
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Oct 21 08:18:25 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] 
[1002:67df] (rev ef) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 [1da2:e366]
  InstallationDate: Installed on 2017-09-30 (20 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=99791e36-3af2-42ca-8376-ce7138f67d70 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0810
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0810:bd08/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1725582/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1705459] Re: Cannot switch to another workspace when an sqlitebrowser window is open

2017-10-27 Thread Sergio Costas

There is a fix published in the main thread at github

https://github.com/kehugter/sqlitebrowser/commit/c4c4cf62a2adf90c7604a920c409c27192f177ce

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1705459

Title:
  Cannot switch to another workspace when an sqlitebrowser window is
  open

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Test Case
  Pre-requisites:
- Several workspaces must be open
- Install sqlitebrowser
  1. Launch sqlitebrowser
  2. Switch to another workspace user the workspace switcher, switching to an 
app on another workspace or a short-cut
  3. Minimize the sqlitebrowser window

  Expected result
  User can switch to another workspace or minimize the window

  Actual result
  The shells switches back to previous state (stays on same workspace or 
remaximize the window)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 20 13:37:34 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1101 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2015-12-08 (589 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1438014] Re: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()

2017-10-27 Thread jean-marc

On a terminal, choosing preferences... and modifying some shortcut keys
on "Artful Aardwark" distro

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1438014

Title:
  gnome-terminal-server crashed with SIGSEGV in
  g_type_check_instance_is_a()

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1728005] Re: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()

2017-10-27 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1724699, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1728005/+attachment/4997746/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1728005/+attachment/4997748/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1728005/+attachment/4997752/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1728005/+attachment/4997753/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1728005/+attachment/4997754/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1728005/+attachment/4997755/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1728005/+attachment/4997756/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1724699
   nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1728005

Title:
  nautilus crashed with SIGSEGV in
  nautilus_file_get_search_fts_snippet()

Status in nautilus package in Ubuntu:
  New

Bug description:
  deshaciendo un sistema de ficheros, se quedó colgado y luego cerró.
  Puede ser la iso, al trasladarla de una carpeta a otra, se haya corrompido. 
  Anoche, esa misma iso, la monté en unetbootin con PPA en ubuntu, luego otro 
arranque distinto, pero me di cuenta que al reiniciar, se queda un cursor 
parpadeante, arriba, a la izquierda. amanecí con una ventana pequeña en el 
centro arriba que decía: algo ha ido mal X. Al instalar desde el centro de 
software, tambien aparecíen de vez en cuando, después de instalar algún 
programa, sea de la categoría que sea. Si necesitais esta explicación en 
francés, me lo decis.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 11:43:34 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-27 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x56490a1c0660 : 
mov0x18(%rdi),%rax
   PC (0x56490a1c0660) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_file_get_search_fts_snippet ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

2017-10-27 Thread Michael Thayer

Just for the sake of adding a comment too... I am getting this in the following 
situation.  I hope the description is correct.
 1) I change the display set-up on my laptop slightly too fast, e.g. close the 
lid, re-open, re-close (I did that quite a bit recently trying to work out bug 
patterns).
 2) GNOME Shell creates a wl_output object for the internal screen, reports it 
to Xwayland, then removes it again because the screen is disabled again.
 3) Xwayland asks GNOME Shell for more information about the no-longer-existing 
wl_output object and GNOME Shell (in the Wayland library code) terminates the 
connection because it considers asking about a non-existing object to be a bug.
 4) Xwayland dutifully terminates and GNOME Shell panics and terminates too.

See: https://phabricator.freedesktop.org/T7722

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1505409

Title:
  gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
  _XEventsQueued() from XPending() from gdk_check_xpending()
  ["Connection to xwayland lost"]

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 source package in Artful:
  Confirmed
Status in gnome-shell source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742

  ---

  Occurred during start-up, before I did anything special...

  1 Ubuntu Wily Werewolf (development branch) 15.10
  2 3.16.3-1ubuntu6
  3&4 not applicable

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gnome-shell 3.16.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 12 19:22:07 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-10-08 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

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

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-04-26T16:36:05+00:00 Nrbrtx wrote:

Description of problem:
Let's assume for clarity that keyboard layout shortcut is set to .
In previous versions of GNOME this key combination did not interfere with other 
hotkey combinations. But nowadays it is broken.

- Set ctrl+shift as shortcut for switching keyboard layouts
- Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

Version-Release number of selected component (if applicable):
Bug exists in Red Hat Enterprise___ Linux Workstation 7.0 (Maipo).
gnome-settings-daemon-3.8.6.1-8.el7.x86_64

How reproducible:
Always

Steps to Reproduce (S); Actual Results (AR); Expected Results (ER)

Test case No. 1:
(S): Open gnome-terminal, type some command, try to copy the command with 
 and to paste it with .
(ER): Text is copied and pasted, keyboard layout is not changed.
(AR): Text is not copied and not pasted, but keyboard layout is changed.

Test case No. 2:
(S): Open Firefox web-browser, open new tab, go to some site, close this tab, 
try to recover tab with 
(ER): Recently closed tab is opened, keyboard layout is unchanged
(AR): Firefox opened new tab, keyboard layout is changed

Test case No. 3:
(S): Open any text editor (gedit libreoffice Writer), type some text with 
several words, try to select some of that words with  or 

(ER): Text is selected by words, keyboard layout is not changed
(AR): Text is not selected, keyboard layout is changed

Test case No. 4:
Open Blender (see 
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1245473/comments/5
 for details)

Test case No. 5:
(S): Try to make a screenshot of desired window region with 

(ER): Cursor is changed to cross, desired area is selected by user, screenshot 
is copied to clipboard, keyboard layout is not changed
(AR): Whole screen screenshot is saved to clipboard, keyboard layout is changed

The aforementioned test-cases works as expected on previous versions of
GNOME (for example 3.4.2 in Ubuntu 12.04).

Additional info:
This bug exists at least in Ubuntu (see 
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1245473), 
the bug is reported to upstream 
(https://bugzilla.gnome.org/show_bug.cgi?id=712667) with no luck.

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

On 2014-04-28T08:04:52+00:00 Vladimir wrote:

(In reply to Nrbrtx from comment #0)
> Description of problem:
> Let's assume for clarity that keyboard layout shortcut is set to
> .
> In previous versions of GNOME this key combination did not interfere with
> other hotkey combinations. But nowadays it is broken.
> 
> - Set ctrl+shift as shortcut for switching keyboard layouts

I wonder how can one set ctrl+shift to switching layouts. I have a
switch mapped to super + space and cannot remap it. In fact this
functionality was removed somewhere around GNOME 3.4 or so. Now, you
have to use some alpha/numeric key in addition to functional ones
(ctrl/alt/shift/super). So setting to ctrl+shift should be forbidden.

> - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work
> (actually Terminal window loses focus when ctrl+shift is pressed, and layout
> is switched)
>

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

On 2014-04-28T09:07:09+00:00 Nrbrtx wrote:

Thank you for reply, Vladimir!

If we talk about Fedora 20, it uses gnome-control-center 3.10.3 
(control-center-3.10.3-1.fc20.i686).
If we talk about RedHat 7, it uses gnome-control-center 3.8.6 
(control-center-3.8.6-15.el7.x86_64).

On both systems one can set almost any shortcut for switching layouts
from "gnome-control-center keyboard" -> Shortcuts -> Typing ->
Modifiers-only switch to next source (here are , , , , , , , , , , , , , , ,
, , , , ).

So there is no problem to set for example  as layout
switcher.

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

On 2014-04-28T12:12:01+00:00 Vladimir wrote:

this was originally solved here with a bit of state juggling. 
https://bugzilla.redhat.com/show_bug.cgi?id=841878

this functionality was removed from all items but Modifiers-only switch
to next source. I think those containing ctrl+shift or alt+s

[Desktop-packages] [Bug 792145] Re: eog (Eye of Gnome) ignores umask settings

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

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-06-27T19:34:54+00:00 Vladimir wrote:

Description of problem:
When saving an image, eog does not retain the original permissions and 
ownership.

Version-Release number of selected component (if applicable):
eog-2.24.3.1-1.fc10.i386

How reproducible:
Do a modification to an image in eog and save it.

Steps to Reproduce:
1. Open image in eog
2. Rotate the image
3. Save the image (File->Save)
  
Actual results:
The original permissions are gone.

Expected results:
The permissions should be retained.

Additional info:

This is painful for multi-user system or file server because it blocks
other users from accessing the file.

In my case the original file attributes looked like this:

rw-rw-r--+ 1 myuser mygroup

After eog saved the image (in place) the attributes changed to:

rw-rw-r--+ 1 myuser myuser

My umask (when run in terminal) is 0002.

It seems this is caused by the way how eog performs the modification and
save; strace output releals the following:

[pid  8643] lstat64("/tmp/eog-save-F87BWU", {st_mode=S_IFREG|0600, st_size=42043
7, ...}) = 0
[pid  8643] lstat64("/var/tmp/bio.jpg", {st_mode=S_IFREG|0664, st_size=409310, .
..}) = 0
[pid  8643] rename("/tmp/eog-save-F87BWU", "/var/tmp/bio.jpg" 
[pid  8638] <... poll resumed> )= 1 ([{fd=15, revents=POLLIN}])

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/792145/comments/0


On 2009-06-27T19:36:41+00:00 Vladimir wrote:

Created attachment 349670
strace output of eog process which rotates and than saves an image

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/792145/comments/1


On 2009-11-18T10:04:38+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 10.  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 '10'.

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 10'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 10 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/eog/+bug/792145/comments/2


On 2009-12-18T09:36:05+00:00 Bug wrote:


Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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/eog/+bug/792145/comments/3


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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eog in Ubuntu.
https://bugs.launchpad.net/bugs/792145

Title:
  eog (Eye of Gnome) ignores umask settings

Status in Eye of GNOME:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in eog package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: eog

  This does not seem to be a generic Gnome or gnome-vfs bug (some
  similar bug reports exist for earlier Ubuntu releases), I have only
  been able to reproduce it in eog.

  Expected Behavior:
  Rotating an image and saving it should not

[Desktop-packages] [Bug 780717] Re: Using PKCS#12 file requires password for private key

2017-10-27 Thread wistle

Confirm the same problem on 16.04 LTS
The random characters do not work for me.
It's a customer's VPN so I cannot insist on changes being make to fit me.  The 
configuration works fine when using he command line "openvpn --config 
.ovpn", but I would prefer to use Network Manager for the simplicity of it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/780717

Title:
  Using PKCS#12 file requires password for private key

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager-openvpn

  network-manager-openvpn allows to specify PKCS#12 files instead of sep. files 
for CA, cert and key. That's wonderful.
  There's one problem though: When specifying a *.p12 file, one HAS to enter a 
"Private key password" even if the PKCS#12 is not password protected at all.
  When specifying sep. files for CA, cert and key, entering the "Private key 
password" is optional. Not when using the PKCS#12 file.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: network-manager-openvpn-gnome 
0.8.1+git.20100810t173015.1711d04-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic x86_64
  Architecture: amd64
  Date: Tue May 10 21:48:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/780717/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1436590] Re: Intel Display i915 driver crashes, Thinkpad X1 carbon Gen 3

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

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-10-16T13:32:28+00:00 Fabio wrote:

Additional info:
reporter:   libreport-2.3.0
WARNING: CPU: 3 PID: 951 at drivers/gpu/drm/i915/intel_display.c:1278 
assert_plane.constprop.78+0x6b/0x70 [i915]()
plane A assertion failure (expected on, current off)
Modules linked in: fuse xt_CHECKSUM ipt_MASQUERADE tun nf_conntrack_netbios_ns 
nf_conntrack_broadcast 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 x86_pkg_temp_thermal coretemp kvm_intel hid_sensor_incl_3d uvcvideo 
hid_sensor_als hid_sensor_gyro_3d hid_sensor_magn_3d hid_sensor_rotation 
hid_sensor_accel_3d hid_sensor_trigger industrialio_triggered_buffer kvm 
kfifo_buf industrialio hid_sensor_iio_common iTCO_wdt iTCO_vendor_support arc4 
videobuf2_vmalloc crct10dif_pclmul crc32_pclmul
 snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic crc32c_intel 
videobuf2_memops btusb vfat videobuf2_core fat snd_hda_intel iwlmvm 
snd_hda_controller ghash_clmulni_intel bluetooth mac80211 snd_hda_codec 
snd_hwdep v4l2_common snd_seq videodev iwlwifi snd_seq_device cfg80211 
serio_raw hid_multitouch hid_sensor_hub media snd_pcm lpc_ich i2c_i801 mfd_core 
ideapad_laptop snd_timer sparse_keymap mei_me snd rfkill int3403_thermal 
i2c_hid dw_dmac dw_dmac_core i2c_designware_platform i2c_designware_core mei 
shpchp soundcore btrfs xor raid6_pq i915 i2c_algo_bit drm_kms_helper drm 
sdhci_acpi sdhci mmc_core video analog gameport joydev
CPU: 3 PID: 951 Comm: Xorg.bin Not tainted 3.17.0-301.fc21.x86_64 #1
Hardware name: LENOVO 20266/Yoga2, BIOS 76CN31WW 10/31/2013
  680449de 88008e7cf760 8173c311
 88008e7cf7a8 88008e7cf798 81096e8d 
 880250cec000 88007f9a1800 8802506c 
Call Trace:
 [] dump_stack+0x45/0x56
 [] warn_slowpath_common+0x7d/0xa0
 [] warn_slowpath_fmt+0x5c/0x80
 [] assert_plane.constprop.78+0x6b/0x70 [i915]
 [] hsw_disable_ips+0x41/0x190 [i915]
 [] intel_crtc_disable_planes+0x49/0x160 [i915]
 [] haswell_crtc_disable+0x57/0x340 [i915]
 [] __intel_set_mode+0x7e1/0x16f0 [i915]
 [] ? __do_readpage+0x614/0x7e0 [btrfs]
 [] intel_set_mode+0x16/0x30 [i915]
 [] intel_crtc_set_config+0xa9a/0xeb0 [i915]
 [] drm_mode_set_config_internal+0x64/0xe0 [drm]
 [] restore_fbdev_mode+0xb3/0xe0 [drm_kms_helper]
 [] drm_fb_helper_restore_fbdev_mode_unlocked+0x23/0x40 
[drm_kms_helper]
 [] drm_fb_helper_set_par+0x28/0x70 [drm_kms_helper]
 [] intel_fbdev_set_par+0x1a/0x60 [i915]
 [] fb_set_var+0x190/0x420
 [] ? free_hot_cold_page_list+0x46/0xa0
 [] fbcon_blank+0x259/0x340
 [] do_unblank_screen+0xba/0x1f0
 [] vt_ioctl+0x13b1/0x1430
 [] ? avc_alloc_node+0x27/0x130
 [] tty_ioctl+0x2ad/0xbf0
 [] ? avc_has_perm+0xd9/0x1a0
 [] do_vfs_ioctl+0x2d0/0x4b0
 [] ? fput+0xe/0x10
 [] SyS_ioctl+0x81/0xa0
 [] system_call_fastpath+0x16/0x1b

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


On 2014-10-16T13:32:35+00:00 Fabio wrote:

Created attachment 947603
File: dmesg

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


On 2014-11-18T20:04:52+00:00 Adam wrote:

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

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


On 2014-11-18T20:04:56+00:00 Adam wrote:

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

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


On 2014-11-18T20:05:00+00:00 Adam wrote:

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

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


On 2014-11-18T20:05:04+00:00 Adam wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-vi

[Desktop-packages] [Bug 640652] Re: Confusing warning message for invalid printer names

** Changed in: system-config-printer (Fedora)
   Status: Unknown => Fix Released

** Changed in: system-config-printer (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/640652

Title:
  Confusing warning message for invalid printer names

Status in system-config-printer package in Ubuntu:
  Fix Released
Status in system-config-printer package in Fedora:
  Fix Released

Bug description:
  Binary package hint: system-config-printer

  1) Create or select an existing printer
  2) Hit F2 or right-click > rename
  3) Type a name CUPS will not accept (e.g. with a space)
  4) Confusing error message and failure to rename

  CUPS Client error: "client-error-bad-request"

  
  Either system-config-printer should disallow entry of invalid names in the 
first place, or it should catch the error and replace it with a more helpful 
description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/640652/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1005418] Re: upowerd crashed with SIGABRT in __libc_message()

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

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-06-15T11:30:37+00:00 Christian wrote:

Description of problem:
Plugging in an iPhone 5S via USB triggers this crash reliably, and the crash 
keeps repeating infinitely.

The issue started about 2 weeks ago. Before that I had no problems with it on 
Fedora 22.
I am running an up-to-date system.

I never told the phone to trust the computer and open its services to the 
computer.
GNOME never shows the message that a phone was connected.

Version-Release number of selected component:
upower-0.99.3-1.fc22

Additional info:
reporter:   libreport-2.5.1
backtrace_rating: 4
cmdline:/usr/libexec/upowerd
crash_function: g_try_malloc
executable: /usr/libexec/upowerd
global_pid: 4263
kernel: 4.0.4-303.fc22.x86_64
runlevel:   N 5
type:   CCpp
uid:0

Truncated backtrace:
Thread no. 1 (8 frames)
 #3 g_try_malloc at gmem.c:244
 #4 get_contents_regfile at gfileutils.c:784
 #5 get_contents_posix at gfileutils.c:886
 #6 g_file_get_contents at gfileutils.c:987
 #7 sysfs_get_bool at sysfs-utils.c:127
 #8 up_device_supply_refresh_battery at up-device-supply.c:523
 #9 up_device_supply_refresh at up-device-supply.c:1128
 #10 up_device_supply_poll_unknown_battery at up-device-supply.c:912

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/6


On 2015-06-15T11:30:40+00:00 Christian wrote:

Created attachment 1038900
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/7


On 2015-06-15T11:30:41+00:00 Christian wrote:

Created attachment 1038901
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/8


On 2015-06-15T11:30:42+00:00 Christian wrote:

Created attachment 1038902
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/9


On 2015-06-15T11:30:43+00:00 Christian wrote:

Created attachment 1038903
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/10


On 2015-06-15T11:30:44+00:00 Christian wrote:

Created attachment 1038904
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/11


On 2015-06-15T11:30:45+00:00 Christian wrote:

Created attachment 1038905
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/12


On 2015-06-15T11:30:47+00:00 Christian wrote:

Created attachment 1038906
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/13


On 2015-06-15T11:30:48+00:00 Christian wrote:

Created attachment 1038907
File: mountinfo

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/14


On 2015-06-15T11:30:49+00:00 Christian wrote:

Created attachment 1038908
File: namespaces

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/15


On 2015-06-15T11:30:50+00:00 Christian wrote:

Created attachment 1038909
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/16


On 2015-06-15T11:30:51+00:00 Christian wrote:

Created attachment 1038910
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/17


On 2015-06-15T11:30:52+00:00 Christian wrote:

Created attachment 1038911
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/18


On 2015-06-15T11:34:05+00:00 Christian wrote:

Created attachment 1038913
systemd journal

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418/comments/19

-

[Desktop-packages] [Bug 788089] Re: C/figures/evo_mail_notifier.png is a broken symlink

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

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-07-24T15:43:21+00:00 Christian wrote:

Description of problem:
evolution-help contains a recursive symbolic link:


# namei -l /usr/share/gnome/help/evolution/en_GB/figures/evo_mail_notifier.png
namei: failed to stat: 
/usr/share/gnome/help/evolution/en_GB/figures/evo_mail_notifier.png: Too many 
levels of symbolic links

# ls -la /usr/share/gnome/help/evolution/C/figures/evo_mail_notifier.png
lrwxrwxrwx 1 root root 37 2010-05-30 00:14 
/usr/share/gnome/help/evolution/C/figures/evo_mail_notifier.png -> 
../../C/figures/evo_mail_notifier.png

Version-Release number of selected component (if applicable):
The issue is present in F12 and F13:
evolution-help-2.28.3-1.fc12.noarch
evolution-help-2.30.2-1.fc13.noarch


How reproducible:
100%

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/788089/comments/0


On 2010-07-25T11:20:12+00:00 Fedora wrote:

evolution-2.30.2-4.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/evolution-2.30.2-4.fc13

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/788089/comments/1


On 2010-07-27T02:47:14+00:00 Fedora wrote:

evolution-2.30.2-4.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 evolution'.  You can provide 
feedback for this update here: 
http://admin.fedoraproject.org/updates/evolution-2.30.2-4.fc13

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/788089/comments/2


On 2010-07-30T08:33:57+00:00 Fedora wrote:

evolution-2.30.2-4.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/evolution/+bug/788089/comments/3


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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/788089

Title:
  C/figures/evo_mail_notifier.png is a broken symlink

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution package in Fedora:
  Fix Released

Bug description:
  Binary package hint: evolution-common

  era@lvcid$ ls -l  
/usr/share/gnome/help/evolution/figures/evo_mail_notifier.png 
  lrwxrwxrwx 1 root root 37 2011-01-27 13:34 
/usr/share/gnome/help/evolution/C/figures/evo_mail_notifier.png -> 
../../C/figures/evo_mail_notifier.png

  era@lvcid$ dpkg -S 
/usr/share/gnome/help/evolution/C/figures/evo_mail_notifier.png
  evolution-common: 
/usr/share/gnome/help/evolution/C/figures/evo_mail_notifier.png

  era@lvcid$ apt-cache policy evolution-common
  evolution-common:
Installed: 2.28.3-0ubuntu10.2
Candidate: 2.28.3-0ubuntu10.2
Version table:
   *** 2.28.3-0ubuntu10.2 0
  500 http://mirrors.nic.funet.fi/ubuntu/ lucid-updates/main Packages
  100 /var/lib/dpkg/status
   2.28.3-0ubuntu9 0
  500 http://mirrors.nic.funet.fi/ubuntu/ lucid/main Packages

  era@lvcid$ lsb_release -rd
  Description:Ubuntu 10.04.2 LTS
  Release:10.04

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 556829] Re: thunderbird-bin crashed with SIGSEGV in nsQueryInterface::operator()

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/556829

Title:
  thunderbird-bin crashed with SIGSEGV in nsQueryInterface::operator()

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird package in Fedora:
  Invalid

Bug description:
  Binary package hint: thunderbird

  Ubuntu 10.4 / Clicked on Sent expand triangle against Google IMAP

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.4+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: openafs nvidia
  Architecture: amd64
  Date: Tue Apr  6 16:27:17 2010
  ExecutablePath: /usr/lib/thunderbird-3.0.4/thunderbird-bin
  ProcCmdline: /usr/lib/thunderbird-3.0.4/thunderbird-bin
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: thunderbird
  StacktraceTop:
   nsQueryInterface::operator()(nsID const&, void**) const () from 
/usr/lib/thunderbird-3.0.4/libxpcom_core.so
   nsCOMPtr_base::assign_from_qi(nsQueryInterface, nsID const&) () from 
/usr/lib/thunderbird-3.0.4/libxpcom_core.so
   ?? ()
   ?? ()
   ?? ()
  Title: thunderbird-bin crashed with SIGSEGV in nsQueryInterface::operator()
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
sambashare video

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 284596] Re: nm-applet fails when another user is logged in

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

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-21T08:10:53+00:00 Avi wrote:

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

Description of problem:
When multiple users are logged in, the NetworkManager applet will only work for 
one of them.  If one of the other users need to interact with NetworkManager, 
they are screwed.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.9.4.svn3675.fc9.x86_64

How reproducible:
Always


Steps to Reproduce:
1. Boot system
2. Log in, nm-applet loads and connects automatically
3. Log in as another user, keeping previous user logged in
4. Look in vain for the applet.  Starting nm-applet from the command line won't 
work.

Actual Results:
No NetworkManager applet.

Expected Results:
NetworkManager applet in all its glory.

Additional info:

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


On 2008-07-22T20:33:24+00:00 Andre wrote:

This might be related to bug #449976 concerning the inability to set whether the
NetworkManager applet appears on a per-user basis.

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


On 2008-09-08T15:07:45+00:00 Alexey wrote:

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

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


On 2008-10-01T13:46:24+00:00 Mitch wrote:

This bug drives me crazy.  If I leave my computer going, and the screen
locks, then someone else (who logs in with their own username) can't
control the wireless network.  Dialog boxes pop up in the person who
first logged in.  Please please fix!

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


On 2008-10-19T22:12:23+00:00 Mitch wrote:

Has this bug been fixed for Fedora 10?  Would really really love to see
it fixed.

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


On 2009-01-10T14:23:05+00:00 Charles-Henri wrote:

Hello,

This bug still apply to Fedora 10 unfortunatly.
I also suffer from this bug ...

Thank you very much for your help !

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


On 2009-01-10T22:45:22+00:00 Mitch wrote:

This one's a royal pain, eh?

I want to tell you about how I have worked around this bug.  It is a
workaround, not a fix.

 - Create a script called /usr/local/bin/grab-network

  #! /bin/bash

  sudo killall -1 nm-applet
  sleep 1
  nohup nm-applet < /dev/null > /dev/null 2>&1 &
  sleep 1

 - chmod a+x /usr/local/bin/grab-network

 - Run visudo, and add these lines:

Cmnd_Alias GRAB_NETWORK = /usr/bin/killall -1 nm-applet

  and

# Allows people in grab_network group to restart wireless.
%grab_network ALL = NOPASSWD: GRAB_NETWORK

 - Create a new group in /etc/group called "grab_network".

 - Add users who you want to be able to grab the network, to this group.

 - On the desktop for each of these users, create a launcher to
/usr/local/bin/grab-network.

As I said, a workaround, not a fix.

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


On 2009-01-11T11:29:22+00:00 Charles-Henri wrote:

Hi !

thanks for the workaround.

In fact this bug is not very annoying as long as the user who logged
first is still logged. But when this user log out other users cannot use
the network any more unless they log out and in again.

Still, should a bug zapper or the maintener mark this bug as belonging
to F10 so that it is still valid when F9 will be end of life ? Thanks !

Cheers,
Ch

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


On 2009-01-13T13:07:42+00:00 Magnus wrote:

This bug may be solved..

I did experience it earlier, but now using:

Fedora 10 on 2.6.27.9-159.fc10.x86_64 #1 SMP

..with..

NetworkManager-0.7.0-1.git20090102.fc1

[Desktop-packages] [Bug 475889] Re: Arial Narrow: not recognised

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

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-12T18:11:52+00:00 Julian wrote:

Created attachment 320146
Confused gtk2 font selector

Description of problem:
Going through various bug reports, mailing list posts and so on I came to the 
conclusion that applications are being currently fixed in order to support 
extended fonts attibutes, and that gtk2 font selector is the one that should 
work properly. Granted, it works for say DejaVu LGC condensed, but does not for 
Arial Narrow (the condensed glyphs are to be found in separate files, copied 
over from XP install into .fonts). fc-list outputs the following:

[jsikorski@snowball ~]$ fc-list | grep Arial
Arial 
Black:style=Normalny,Normal,obyčejné,Standard,Κανονικά,Regular,Normaali,Normál,Normale,Standaard,Обычный,Normálne,Navadno,Arrunta
Arial,Arial 
Narrow:style=Normalny,Narrow,Normal,obyčejné,Standard,Κανονικά,Regular,Normaali,Normál,Normale,Standaard,Обычный,Normálne,Navadno,Arrunta
Arial:style=Pogrubiona kursywa,Negreta cursiva,tučné kurzíva,fed kursiv,Fett 
Kursiv,Έντονα Πλάγια,Bold Italic,Negrita Cursiva,Lihavoitu Kursivoi,Gras 
Italique,Félkövér dőlt,Grassetto Corsivo,Vet Cursief,Halvfet Kursiv,Negrito 
Itálico,Полужирный Курсив,Tučná kurzíva,Fet Kursiv,Kalın İtalik,Krepko 
poševno,nghiêng đậm,Lodi etzana
Arial,Arial Narrow:style=Pogrubiona kursywa,Narrow,Negreta cursiva,tučné 
kurzíva,fed kursiv,Fett Kursiv,Έντονα Πλάγια,Bold Italic,Negrita 
Cursiva,Lihavoitu Kursivoi,Gras Italique,Félkövér dőlt,Grassetto Corsivo,Vet 
Cursief,Halvfet Kursiv,Negrito Itálico,Полужирный Курсив,Tučná kurzíva,Fet 
Kursiv,Kalın İtalik,Krepko poševno,Lodi etzana
Arial:style=Kursywa,Cursiva,kurzíva,kursiv,Πλάγια,Italic,Kursivoitu,Italique,Dőlt,Corsivo,Cursief,Itálico,Курсив,İtalik,Poševno,nghiêng,Etzana
Arial:style=Normalny,Normal,obyčejné,Standard,Κανονικά,Regular,Normaali,Normál,Normale,Standaard,Обычный,Normálne,Navadno,thường,Arrunta
Arial,Arial 
Narrow:style=Pogrubiony,Narrow,Negreta,tučné,fed,Fett,Έντονα,Bold,Negrita,Lihavoitu,Gras,Félkövér,Grassetto,Vet,Halvfet,Negrito,Полужирный,Fet,Kalın,Krepko,Lodia
Arial:style=Pogrubiony,Negreta,tučné,fed,Fett,Έντονα,Bold,Negrita,Lihavoitu,Gras,Félkövér,Grassetto,Vet,Halvfet,Negrito,Полужирный,Fet,Kalın,Krepko,đậm,Lodia
Arial,Arial 
Narrow:style=Kursywa,Narrow,Cursiva,kurzíva,kursiv,Πλάγια,Italic,Kursivoitu,Italique,Dőlt,Corsivo,Cursief,Itálico,Курсив,İtalik,Poševno,Etzana
[jsikorski@snowball ~]$

Gtk2 font selector gets confused and shows each of the 4 basic styles
twice (see attachment), with no visible difference whatsoever. The only
application I have found to be able to distinguish between the Narrow
and normal styles is the KDE's system settings > installed fonts thingy
(also see attachment)

Version-Release number of selected component (if applicable):
fontconfig-2.5.0-2.fc9.x86_64

How reproducible:
always

Steps to Reproduce:
1. install microsoft core fonts using an rpm package
2. copy over arian{n,ni,nb,nbi}.ttf from a windows installation
3. run fc-cache
4. attempt to select one of the narrow glyphs in the font selector
  
Actual results:
Narrow glyphs are unavailable

Expected results:
Able to select narrow glyphs

Additional info:
Feel free to reassing this bug, I wasn't sure what to assign it to

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/475889/comments/7


On 2008-10-12T18:13:05+00:00 Julian wrote:

Created attachment 320147
KDE System Settings aware of the Narrow glyphs

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/475889/comments/8


On 2008-10-12T18:37:14+00:00 Julian wrote:

This might be relat

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/475889/comments/9


On 2008-10-12T18:38:20+00:00 Julian wrote:

This might be related to the mentioned freedesktop bug, but since there
was no response in 4 months, I thought that filing it here as well might
be a good idea.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/475889/comments/10


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


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

[Desktop-packages] [Bug 218202] Re: numlockx does not turn num lock keyboard light on.

** Changed in: x11-xkb-utils (Fedora)
   Status: Unknown => Fix Released

** Changed in: x11-xkb-utils (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/218202

Title:
  numlockx does not turn num lock keyboard light on.

Status in X.Org X server:
  Confirmed
Status in numlockx package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in numlockx package in Debian:
  Confirmed
Status in x11-xkb-utils package in Fedora:
  Fix Released

Bug description:
  Binary package hint: numlockx

  numlockx does not turn num lock keyboard light on. The keypad works,
  although the light is not on. This has always worked, now in Hardy it
  does not?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 61269] Re: Evolution will not fetch new mail after initial connection to Exchange Server

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

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-06-21T02:12:16+00:00 Steffen wrote:

Description of problem:

When evolution is started, the Exchange folders are scanned, available messages
are displayed in the message list pane, and can be read or moved to local 
folders.

After a while (less than 10 minutes I'd say), this breaks. New messages are
still being indicated (counted up) in the folder pane, but upon selecting the
Inbox folder under the Exchange account the message list pane remains empty, and
no Exchange email can be accessed.

Quitting and restarting evolution makes those new message available, but after a
short while the problem re-occurs.

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

evolution-webcal-2.4.1-3.4
evolution-2.6.2-1.fc5.5
evolution-connector-2.6.2-1.fc5.4
evolution-data-server-1.6.2-1.fc5.1

How reproducible:
As described above.

Steps to Reproduce:
1. Start evolution, fetch all available Exchange email
2. Wait a while
3. New Exchange mail is indicated but not accessible


Additional info:

This problem first occured after the upgrade to version 2.6.2-1 and
associated.

Probably related:
When the Inbox problem occurs, the Deleted Messages folder under the Exchange
account is affected as follows: I can expunge the folder, and get a progress
indication in the status bar, but the message list remains unchanged (instead of
being cleared). After restarting evolution the message list for the Deleted
Messages folder is empty and shows that the expunge action did in fact succeed.

When the problem occurs, sending mail via Exchange as well as Exchange Calendar,
Contacts and GAL keep working, i.e. the Exchange Connector isn't dead.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-
exchange/+bug/61269/comments/0


On 2006-07-05T22:06:49+00:00 Frank wrote:

Seeing the exact same problem here, under x86-64.  Can't downgrade to 2.6.1 due
to dependencies.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-
exchange/+bug/61269/comments/1


On 2006-07-06T01:10:15+00:00 Steffen wrote:

On my systems (all i386) the only dependency that has to be downgraded along
with evolution is gnome-panel(-devel). No big deal. I seem to remember that some
other packages depend on evolution (e.g. beagle via evolution-sharp) but I'm not
using those.

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-
exchange/+bug/61269/comments/2


On 2006-07-06T01:42:16+00:00 Frank wrote:

**
[frank@hortense tmp]$ sudo yum localinstall
evolution-connector-2.6.1-1.fc5.1.x86_64.rpm
**SNIP**

Error: Missing Dependency: libedata-cal-1.2.so.1()(64bit) is needed by package
evolution-connector
Error: Missing Dependency: libecal-1.2.so.3()(64bit) is needed by package
evolution-connector

[frank@hortense ~]$ locate libedata-cal
/usr/lib64/libedata-cal-1.2.so.5
/usr/lib64/libedata-cal-1.2.so.5.0.0
[frank@hortense ~]$ locate libecal
/usr/lib64/libecal-1.2.so.6
/usr/lib64/libecal-1.2.so.6.0.0

[frank@hortense ~]$ sudo yum whatprovides libecal
**SNIP**
evolution-data-server.x86_64 1.6.2-1.fc5.1  updates
Matched from:
/usr/lib64/libecal-1.2.so.6
/usr/lib64/libecal-1.2.so.6.0.0

[frank@hortense ~]$ sudo yum deplist evolution-data-server
package: evolution-data-server.x86_64 1.5.92-1
  dependency: libcairo.so.2()(64bit)
   provider: cairo.x86_64 1.0.2-5
   provider: cairo.x86_64 1.0.4-1
  dependency: libldap-2.3.so.0()(64bit)
   provider: openldap.x86_64 2.3.19-4
  dependency: libORBit-2.so.0()(64bit)
ETC. ETC. ETC.


Both seem to be provided by evolution-data-server, but at a rev below the
evolution-data-server I have installed, which means I'd also have to downgrade
that, which means downgrading about a hundred other packages.  I don't want to
get into a downgrade spiral just to downgrade this one package.  Guess that's
why they call it "dependancy hell", eh? :)


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/61269/comments/3


On 2006-07-06T02:51:20+00:00 Steffen wrote:

Here's what I did:
Downloaded the previous versions from the update repo, then

rpm -Uvh --oldversion evolution-2.6.1-1.fc5.2.i386.rpm \
  evolution-connector-2.6.1-1.fc5.1.i386.rpm \
  evolution-data-server-1.6.1-1.fc5.2.i386.rpm \
  gnome-panel-2.14.1-1.f

[Desktop-packages] [Bug 1727995] Re: Backup Failed with Unknown Error (MemoryError)

2017-10-27 Thread Kenneth Loafman

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

** This bug has been marked a duplicate of bug 1720159
   Cannot allocate memory with large manifest file since 0.7.03

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1727995

Title:
  Backup Failed with Unknown Error (MemoryError)

Status in duplicity package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10
  duplicity:
Installed: 0.7.12-1ubuntu1
Candidate: 0.7.12-1ubuntu1
Version table:
   *** 0.7.12-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected behavior: Backs up target data directories at specified scheduled 
times.
  Actual behavior: Errors out and aborts backup with stacktrace (see screenshot 
and below). 

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in 
from_string
  self.files_changed = list(map(parse_fileinfo, match.group(3).split('\n')))
  MemoryError

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727356

Title:
  Wayland does not start up on "Integrated Graphics Chipset: Intel(R)
  G33": Shader compilation failed

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727997] Re: Missing Save and continue option

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low

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

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1727997

Title:
Missing Save and continue option

Status in gnome-control-center package in Ubuntu:
Incomplete

Bug description:
When trying to translate the untranslated strings, I do not get the
"Save and continue" option.

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

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

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

There is no account conversion on upgrades or anything like that, and
yes it's an upstream issue if the code doesn't work as it should

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

Title:
  gnome-calendar keeps asking for my google password

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Once in a while, perhaps two or three times a day gnome-calendar pops
  up a dialog asking for my google password.

  I have two online google accounts set, but the problem begun after I
  upgraded from zesty, where I had those two accounts as well. They
  didn't appear in the new settings application, but still gnome-
  calendar was asking for the password. One of them has two phase
  authentication set and the other not.

  After I added the online accounts in the new settings app, the
  calendar is synchronized but it still popping the authentication
  window and is very annoying.

  bug report in gnome-calendar:
  https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726922

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.2-1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:45:09 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-04-14 (193 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=es_UY:es
   LANG=es_UY.UTF-8
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-10-27 Thread PeterPall

Then one Bug is fixed. Perhaps we should close it and open another one
for all the devices a change in sane has broken.

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

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

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError

2017-10-27 Thread Kenneth Loafman

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

Memory errors hit when you run out of memory.  Sometimes it's a different
spot in the code.  This traceback was from manifest.py, so an easy call.


On Fri, Oct 27, 2017 at 2:18 AM, Juerg Haefliger <1722...@bugs.launchpad.net
> wrote:

> *** This bug is a duplicate of bug 1720159 ***
> https://bugs.launchpad.net/bugs/1720159
>
> Hmm... Why do you think this is a duplicate of #1720159? My stack trace
> looks different.
>
> --
> You received this bug notification because you are subscribed to
> duplicity in Ubuntu.
> https://bugs.launchpad.net/bugs/1722454
>
> Title:
>   Duplicity fails with MemoryError
>
> Status in Duplicity:
>   New
> Status in duplicity package in Ubuntu:
>   New
>
> Bug description:
>   Running the following command:
>
>   /usr/bin/python /usr/bin/duplicity collection-status
>   --exclude=/mnt/jabba/juergh/backup/gollum
>   --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
>   /.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
>   --exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
>   --exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
>   --exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
>   --exclude=/home/juergh/tmp --exclude=/home/juergh/git
>   --exclude=/home/juergh/Downloads
>   --exclude=/home/juergh/.local/share/Trash
>   --exclude=/home/juergh/.cache/deja-dup/tmp
>   --exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
>   dup --exclude=/home/juergh/.cache --include=/home/juergh
>   --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
>   --exclude=/tmp --exclude=** --gio
>   file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
>   --gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
>   dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19
>
>   results in:
>
>   Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1546, in 
>   with_tempdir(main)
> File "/usr/bin/duplicity", line 1540, in with_tempdir
>   fn()
> File "/usr/bin/duplicity", line 1391, in main
>   do_backup(action)
> File "/usr/bin/duplicity", line 1416, in do_backup
>   globals.archive_dir).set_values()
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 710, in set_values
>   self.get_backup_chains(partials + backend_filename_list)
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 836, in get_backup_chains
>   add_to_sets(f)
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 824, in add_to_sets
>   if set.add_filename(filename):
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 101, in add_filename
>   self.set_manifest(filename)
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 148, in set_manifest
>   self.set_files_changed()
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 128, in set_files_changed
>   mf = self.get_manifest()
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 250, in get_manifest
>   return self.get_local_manifest()
> File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 224, in get_local_manifest
>   return manifest.Manifest().from_string(manifest_buffer)
> File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line
> 215, in from_string
>   vi = VolumeInfo().from_string(match.group(1))
> File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line
> 383, in from_string
>   linelist = s.strip().split("\n")
>   MemoryError
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: duplicity 0.7.12-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
>   Uname: Linux 4.13.0-12-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Tue Oct 10 08:05:45 2017
>   InstallationDate: Installed on 2017-05-25 (137 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170412)
>   SourcePackage: duplicity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1722454/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Running the following command:

  /usr/bin/python /usr/bin/duplicity collection-status
  --exclude=/mnt/jabba/juergh/backup/gollum
  --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
  /.uk-pkg --exclude=/home/juergh/Music --ex

[Desktop-packages] [Bug 1727958] [NEW] In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened

2017-10-27 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with the
application's icons. The individual icons show up in the list of
programs, and can be docked in the launcher - but a generic white
libreoffice icon also shows up in the program list, and if any of the
docked, correct, icons are clicked, a new, white icon appears that is
generic across all libreoffice windows (e.g. if I have open writer and
calc, the white icon gets two red dots and to access either the writer
or calc window I have to click on the generic icon). This is annoying
but not crippling, and not solved by a purge and reinstall.

** Affects: gnome-shell (Ubuntu)
 Importance: Low
 Status: Triaged

-- 
In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher 
when opened
https://bugs.launchpad.net/bugs/1727958
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1728013] [NEW] NetworkManager segfaults when starting and an interface is up

Public bug reported:

This is the kernel output I get when restarting NetworkManager with an
interface being up.  This is reproducible across all of my machines.  I
am running Funtoo with gentoo sources 4.13.9 and have been able to
reproduce this problem for over 6 months.


[Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 
00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000]
[Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 
00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000]
[Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 
00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000]
[Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 
00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000]
[Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 
00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000]

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1728013

Title:
  NetworkManager segfaults when starting and an interface is up

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is the kernel output I get when restarting NetworkManager with an
  interface being up.  This is reproducible across all of my machines.
  I am running Funtoo with gentoo sources 4.13.9 and have been able to
  reproduce this problem for over 6 months.

  
  [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 
00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 
00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 
00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 
00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 
00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1728012] [NEW] Many 3rd party scanner drivers are broken by a sane change

2017-10-27 Thread PeterPall

Public bug reported:

Many scanners can no more be used since sane has changed something: The
3rd-party plug-in the vendor provides as .deb package will still
install. But the scanner is no more recognized.

Scanners that are affected are(besides others):
 - Epson Perfection V10
 - Epson Perfection V1000
 - Epson WorkForce GT-1500
 - Brother MFC-8510DN
 - Epson Perfection V33

It is to note that the probability that the scanner manufacturers fix
things others broke is below 100%.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental2ubuntu2
Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Oct 27 12:35:52 2017
EcryptfsInUse: Yes
SourcePackage: sane-backends
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Description changed:

  Many scanners can no more be used since sane has changed something: The
  3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.
  
  Scanners that are affected are(besides others):
-  - Epson Perfection V10
-  - Epson Perfection V1000
-  - Epson WorkForce GT-1500
-  - Brother MFC-8510DN
+  - Epson Perfection V10
+  - Epson Perfection V1000
+  - Epson WorkForce GT-1500
+  - Brother MFC-8510DN
+  - Epson Perfection V33
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Many scanners can no more be used since sane has changed something: The
  3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.
  
  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
-  - Epson Perfection V33
+  - Epson Perfection V33
+ 
+ It is to note that the probability that the scanner manufacturers fix
+ things others broke is below 100%.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1728012

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-10-27 Thread PeterPall

Ok... ...the new bug report for all devices that are still affected is:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012

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

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

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change

** Changed in: libinput (Ubuntu)
   Importance: Undecided => High

** Changed in: libinput (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724259

Title:
  gnome-shell frozen and using 100% CPU after docking and display
  configuration change

Status in libinput:
  In Progress
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libinput package in Ubuntu:
  Triaged

Bug description:
  I have been having regular system freezes after switching from using
  my laptop stand-alone to waking it up on a docking station with an
  external monitor. I have seen this using two identical docking station
  plus monitor combinations. I am still trying to find a pattern.  I was
  able to ssh in and use apport to save this bug information.  The
  gnome-shell process was hung at 100% CPU utilisation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:56:34 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['gnome-terminal']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-05-31 (504 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727958] Re: In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened

https://bugs.documentfoundation.org/show_bug.cgi?id=100158 as well

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727958

Title:
  In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in
  launcher when opened

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with
  the application's icons. The individual icons show up in the list of
  programs, and can be docked in the launcher - but a generic white
  libreoffice icon also shows up in the program list, and if any of the
  docked, correct, icons are clicked, a new, white icon appears that is
  generic across all libreoffice windows (e.g. if I have open writer and
  calc, the white icon gets two red dots and to access either the writer
  or calc window I have to click on the generic icon). This is annoying
  but not crippling, and not solved by a purge and reinstall.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1728013] Re: NetworkManager segfaults when starting and an interface is up

I am also running NetworkManager 1.4.4-r1.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1728013

Title:
  NetworkManager segfaults when starting and an interface is up

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is the kernel output I get when restarting NetworkManager with an
  interface being up.  This is reproducible across all of my machines.
  I am running Funtoo with gentoo sources 4.13.9 and have been able to
  reproduce this problem for over 6 months.

  
  [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 
00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 
00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 
00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 
00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 
00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727958] Re: In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened

Thank you for your bug report.

That seems to be a known gnome-shell upstream issue and a wayland
limitation see https://bugzilla.gnome.org/show_bug.cgi?id=779143 and
https://cgit.freedesktop.org/libreoffice/core/commit/?id=6903066822900a700ccf67ae70fa171c94644a9a

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

** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome-
shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=779143
   Importance: Unknown
   Status: Unknown

** Bug watch added: Document Foundation Bugzilla #100158
   https://bugs.documentfoundation.org/show_bug.cgi?id=100158

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727958

Title:
  In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in
  launcher when opened

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with
  the application's icons. The individual icons show up in the list of
  programs, and can be docked in the launcher - but a generic white
  libreoffice icon also shows up in the program list, and if any of the
  docked, correct, icons are clicked, a new, white icon appears that is
  generic across all libreoffice windows (e.g. if I have open writer and
  calc, the white icon gets two red dots and to access either the writer
  or calc window I have to click on the generic icon). This is annoying
  but not crippling, and not solved by a purge and reinstall.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1728013] Re: NetworkManager segfaults when starting and an interface is up

I see this repeatedly in the logs.  Just prior to the segfault,
NetworkManager is clearing out DNS information.

Oct 26 22:40:37 localhost NetworkManager[484]:   [1509072037.0735] 
dns-mgr: Removing DNS information from /sbin/resolvconf
Oct 26 22:40:37 localhost kernel: NetworkManager[484]: segfault at 8 ip 
00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1728013

Title:
  NetworkManager segfaults when starting and an interface is up

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is the kernel output I get when restarting NetworkManager with an
  interface being up.  This is reproducible across all of my machines.
  I am running Funtoo with gentoo sources 4.13.9 and have been able to
  reproduce this problem for over 6 months.

  
  [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 
00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 
00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 
00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 
00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 
00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1727877

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

Status in X.Org X server:
  Invalid
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  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 [Radeo

[Desktop-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

2017-10-27 Thread pinduvoz

I had this bug in 17.10 and Debian Strecht, both with Gnone

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1717992

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 
root=/dev/mapper/ubu-root ro quiet splash zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-35

[Desktop-packages] [Bug 1728013] Re: NetworkManager segfaults when starting and an interface is up

I think I found the issue:

#cat /etc/resolvconf.conf
# Use the local name server
name_servers=127.0.0.1

# added for dnscrypt + dnssec
options edns0


The options edns0 is clearly invalid, so, once I commented it, it now works.  I 
can restart NetworkManager as often as I like and it appears to come up just 
fine.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1728013

Title:
  NetworkManager segfaults when starting and an interface is up

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is the kernel output I get when restarting NetworkManager with an
  interface being up.  This is reproducible across all of my machines.
  I am running Funtoo with gentoo sources 4.13.9 and have been able to
  reproduce this problem for over 6 months.

  
  [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 
00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 
00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 
00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 
00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000]
  [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 
00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727958] Re: In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened

** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727958

Title:
  In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in
  launcher when opened

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with
  the application's icons. The individual icons show up in the list of
  programs, and can be docked in the launcher - but a generic white
  libreoffice icon also shows up in the program list, and if any of the
  docked, correct, icons are clicked, a new, white icon appears that is
  generic across all libreoffice windows (e.g. if I have open writer and
  calc, the white icon gets two red dots and to access either the writer
  or calc window I have to click on the generic icon). This is annoying
  but not crippling, and not solved by a purge and reinstall.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1716359] Re: Unplugging headset with audio panel open mutes internal mic

2017-10-27 Thread Andrea Azzarone

** Changed in: unity-control-center (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1716359

Title:
  Unplugging headset with audio panel open mutes internal mic

Status in OEM Priority Project:
  Confirmed
Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  This bug was reported by our OEM team, I'm opening this public bug.

  The internal microphone is muted after he headset is unplugged when the 
System Settings is running.
  We can not reproduce this bug when closed the System Settings window before 
unplugged the headset.

  Reproduce steps:
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1717230] Re: InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

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

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-09-09T16:48:44+00:00 Jan wrote:

When I start deja-dup to make an backup to an external USB HDD (which
worked fine in the past), this error is displayed:

InvalidBackendURL: missing // - relative paths not supported for scheme
gio+invalid: gio+invalid://

Reply at: https://bugs.launchpad.net/deja-dup/+bug/1717230/comments/0


On 2017-09-09T17:02:27+00:00 Jan wrote:

The external USB HDD is encrypted. When I first mount the disk, so that
it is available, and then start deja-dup from the command line, I get
window with this message:

Storage location not available
Waiting for '5.0 TB Encrypted' to become connected...

Note that the name of the mount point is different:
ls /run/media/jan/
'5.0 TB Partition'

In the dropdownlistbox for the Storage location in deja-dup, I only see:
'5.0 TB Encrypted', not '5.0 TB Partition'.

Reply at: https://bugs.launchpad.net/deja-dup/+bug/1717230/comments/1


On 2017-09-14T18:28:54+00:00 Jan wrote:

Fixed upstream.

Reply at: https://bugs.launchpad.net/deja-dup/+bug/1717230/comments/7


On 2017-09-14T20:44:26+00:00 Philip wrote:

Shouldn’t this bug remain open to track inclusion of that patch into the
Fedora package for deja-dup?

Reply at: https://bugs.launchpad.net/deja-dup/+bug/1717230/comments/8


On 2017-09-15T09:55:10+00:00 Jan wrote:

In the meanwhile, I worked around the bug by selecting manually the
destination location again. This means that I cannot test whether the
bug is fixed.

For now I will reopen the bug.

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


On 2017-09-15T13:40:40+00:00 Fedora wrote:

deja-dup-36.1-1.fc26 has been submitted as an update to Fedora 26.
https://bodhi.fedoraproject.org/updates/FEDORA-2017-c27d77c788

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


On 2017-09-15T13:41:05+00:00 Fedora wrote:

deja-dup-36.1-1.fc27 has been submitted as an update to Fedora 27.
https://bodhi.fedoraproject.org/updates/FEDORA-2017-51979dace2

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


On 2017-09-15T16:56:04+00:00 Fedora wrote:

deja-dup-36.1-1.fc27 has been pushed to the Fedora 27 testing repository. If 
problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: 
https://bodhi.fedoraproject.org/updates/FEDORA-2017-51979dace2

Reply at: https://bugs.launchpad.net/deja-dup/+bug/1717230/comments/13


On 2017-09-16T04:25:43+00:00 Fedora wrote:

deja-dup-36.1-1.fc26 has been pushed to the Fedora 26 testing repository. If 
problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: 
https://bodhi.fedoraproject.org/updates/FEDORA-2017-c27d77c788

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


On 2017-09-23T20:21:50+00:00 Fedora wrote:

deja-dup-36.1-1.fc26 has been pushed to the Fedora 26 stable repository.
If problems still persist, please make note of it in this bug report.

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


On 2017-09-30T06:35:08+00:00 Fedora wrote:

deja-dup-36.1-1.fc27 has been pushed to the Fedora 27 stable repository.
If problems still persist, please make note of it in this bug report.

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


** Changed in: deja-dup (Fedora)
   Status: Unknown => Fix Released

** Changed in: deja-dup (Fedora)
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1717230

Title:
  InvalidBackendURL

[Desktop-packages] [Bug 1568934] Re: gedit crashed with SIGSEGV in gtk_list_store_clear()

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

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-06-18T06:03:28+00:00 Jiannan wrote:

Description of problem:
Gedit hangs periodically 2-3 minutes and sometime was forced quit. Just open a 
file and type. BTW, my system was updated from Fedora 21 using fedup. Didn't 
see this issue in Fedora 21.

Version-Release number of selected component:
gedit-3.16.2-1.fc22

Additional info:
reporter:   libreport-2.5.1
backtrace_rating: 4
cmdline:/usr/bin/gedit --gapplication-service
crash_function: g_type_check_instance_is_a
executable: /usr/bin/gedit
global_pid: 4144
kernel: 4.0.4-303.fc22.x86_64
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_type_check_instance_is_a at gtype.c:4016
 #1 gtk_list_store_clear at gtkliststore.c:1423
 #2 real_populate_liststore at gedit/gedit-open-document-selector.c:488
 #7 g_main_context_iteration at gmain.c:3869
 #8 g_application_run at gapplication.c:2308

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/0


On 2015-06-18T06:03:33+00:00 Jiannan wrote:

Created attachment 1040253
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/1


On 2015-06-18T06:03:35+00:00 Jiannan wrote:

Created attachment 1040254
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/2


On 2015-06-18T06:03:37+00:00 Jiannan wrote:

Created attachment 1040255
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/3


On 2015-06-18T06:03:39+00:00 Jiannan wrote:

Created attachment 1040256
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/4


On 2015-06-18T06:03:40+00:00 Jiannan wrote:

Created attachment 1040257
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/5


On 2015-06-18T06:03:41+00:00 Jiannan wrote:

Created attachment 1040258
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/6


On 2015-06-18T06:03:44+00:00 Jiannan wrote:

Created attachment 1040259
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/7


On 2015-06-18T06:03:46+00:00 Jiannan wrote:

Created attachment 1040260
File: mountinfo

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/8


On 2015-06-18T06:03:48+00:00 Jiannan wrote:

Created attachment 1040261
File: namespaces

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/9


On 2015-06-18T06:03:49+00:00 Jiannan wrote:

Created attachment 1040262
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/10


On 2015-06-18T06:03:51+00:00 Jiannan wrote:

Created attachment 1040263
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/11


On 2015-06-18T06:03:52+00:00 Jiannan wrote:

Created attachment 1040264
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1568934/comments/12


On 2016-07-19T14:54:00+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

[Desktop-packages] [Bug 1229732] Re: soffice.bin crashed with SIGSEGV in ScRangeList::front()

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

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-08T19:51:58+00:00 Devon wrote:

Description of problem:
Deleted a row from the spread sheet.

Version-Release number of selected component:
libreoffice-core-4.3.5.2-4.fc21

Additional info:
reporter:   libreport-2.3.0
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --calc 
file:///home/djanitz/Downloads/password%20managers%20comparison.xlsx 
--splash-pipe=5
crash_function: ScRangeList::operator[]
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.17.7-300.fc21.x86_64
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ScRangeList::operator[] at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/core/tool/rangelst.cxx:1122
 #1 ScConditionalFormat::DeleteArea at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/core/data/conditio.cxx:2091
 #2 ScConditionalFormatList::DeleteArea at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/core/data/conditio.cxx:2305
 #3 ScTable::CopyToTable at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/core/data/table2.cxx:1188
 #4 ScDocument::CopyToDocument at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/core/data/document.cxx:1971
 #5 ScDocFunc::DeleteCells at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/ui/docshell/docfunc.cxx:2303
 #6 ScViewFunc::DeleteCells at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/ui/view/viewfunc.cxx:1523
 #7 ScCellShell::ExecuteEdit at 
/usr/src/debug/libreoffice-4.3.5.2/sc/source/ui/view/cellsh1.cxx:170
 #8 SfxShell::CallExec at 
/usr/src/debug/libreoffice-4.3.5.2/include/sfx2/shell.hxx:181
 #9 SfxDispatcher::Call_Impl at 
/usr/src/debug/libreoffice-4.3.5.2/sfx2/source/control/dispatch.cxx:283

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


On 2015-01-08T19:52:01+00:00 Devon wrote:

Created attachment 977921
File: backtrace

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


On 2015-01-08T19:52:01+00:00 Devon wrote:

Created attachment 977922
File: cgroup

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


On 2015-01-08T19:52:02+00:00 Devon wrote:

Created attachment 977923
File: core_backtrace

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


On 2015-01-08T19:52:03+00:00 Devon wrote:

Created attachment 977924
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/9


On 2015-01-08T19:52:04+00:00 Devon wrote:

Created attachment 977925
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/10


On 2015-01-08T19:52:04+00:00 Devon wrote:

Created attachment 977926
File: exploitable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/11


On 2015-01-08T19:52:05+00:00 Devon wrote:

Created attachment 977927
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/12


On 2015-01-08T19:52:06+00:00 Devon wrote:

Created attachment 977928
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/13


On 2015-01-08T19:52:07+00:00 Devon wrote:

Created attachment 977929
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/14


On 2015-01-08T19:52:07+00:00 Devon wrote:

Created attachment 977930
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/15


On 2015-01-08T19:52:08+00:00 Devon wrote:

Created attachment 977931
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1229732/comments/16

-

[Desktop-packages] [Bug 1476769] Re: When activating OpenVPN without DHCP6, random traffic will be routed without VPN