date:20171026

Thanks. Perhaps we jumped the gun though...

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

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

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

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

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

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

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

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

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

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

Title:
  No more than 2 displays work simultaneously

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

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

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

You have been subscribed to a public bug:

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

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

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

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

and Integrated Intel HD 620 graphics:

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

lshw -C video
  *-display

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

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

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

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

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

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

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

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

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


On 2007-10-22T12:37:39+00:00 Tomas wrote:

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

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

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


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

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

Comments from Derek:

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

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

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


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

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

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


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

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

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


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

KDE security advisory with official patches for kdegraphics and koffice:

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


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


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

Official xpdf patch is available on xpdf upstream page:

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


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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

This issue was addressed in:

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

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

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

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

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


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

abrt 1.0.0 detected a crash.

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

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

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


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

Created attachment 377421
File: backtrace

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


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

Hi Glen!

Thank you very much for your bug report.

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

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

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

yum update gtk2 --enablerepo=updates-testing

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

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


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

Yep, fixed me right up.  Thanks!

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


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

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

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


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

The gtk2 update fixed the problem for me, too.

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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

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


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

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


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


How reproducible:
100% reproducible.


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

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


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


Additional info:
uname -r 

2.6.29-0.96.rc3.git12.fc11.i586


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


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


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

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


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

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

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


On 2009-06-09T11:12:15+00:00 Bug wrote:


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

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

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


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


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

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


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

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

Title:
  window list restore to current workspace does not work

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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


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

Created attachment 999159
File: backtrace

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


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

Created attachment 999160
File: cgroup

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


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

Created attachment 999161
File: core_backtrace

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


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

Created attachment 999162
File: dso_list

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


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

Created attachment 999163
File: environ

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


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

Created attachment 999164
File: limits

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


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

Created attachment 999165
File: maps

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


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

Created attachment 999166
File: open_fds

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


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

Created attachment 999167
File: proc_pid_status

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


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

Created attachment 999168
File: var_log_messages

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


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

which gtk3 version is this with ?

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


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

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

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


On 2016-07-19T12:56:55+00:00 Fedora wrote:

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience prob

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

2017-10-26 Thread Peter Wallbridge

Did it. I hope I did it correctly.

On Thu, Oct 26, 2017 at 10:14 PM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Peter, we're here to help. And Sebastien is right... The fastest way to
> a fix for you now is for you to report the bug directly on the Gnome bug
> tracker:  https://bugzilla.gnome.org/
>
> We ask you to do this because the conversation that will happen with the
> Gnome guys needs to be with someone who experiences the problem first-
> hand (yourself).
>
> After a fix is available there we will pull it down to here again for
> release in Ubuntu.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in gnome-shell package in Ubuntu:
>   New
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:  core-9.20160110ubuntu5-amd64:
> core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.
> 20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1725836/+subscriptions
>

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

Title:
  No more than 2 displays work simultaneously

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

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

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

2017-10-26 Thread Khurshid Alam

They work fine on Unity. it's a wayland problem. But why deny xorg users
because of that?

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

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

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

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

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

2017-10-26 Thread Doug Reese

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

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

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

Title:
  gnome-calendar keeps asking for my google password

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

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

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

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

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


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

Description of problem:

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

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


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

Created attachment 306027
Screenshot

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


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

Probably an upstream bug:

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

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

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


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

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

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


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


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

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

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

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

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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


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


Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

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

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


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

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

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

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

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

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

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

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


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

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

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

How reproducible:
Always

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

Title:
  FTP Transfer from whole directorys fails

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

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

[Bug 79078] Re: Receive hangs regularly

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

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


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

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

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


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

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

Expected results:


Additional info:

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

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


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

Created attachment 142312
screenshot of the send/receive popup

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


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

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


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


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

I have this issue constantly also.  Beta2.

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

I will open other bzs on those



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


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

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

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


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

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

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

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


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

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

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

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


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

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

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


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

Corresponding for fc6 is bug 208724

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


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

Created attachment 145255
Fix for EMsgPort race

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

This patch fixes it by making cache a list.

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

-

[Bug 33072] Re: Pulling AC plug suspends computer

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

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


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

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

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

How reproducible:
always

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

Expected results:
keep running

Additional info:
my system:
ibm g40

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


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

As root, can you do:

cat /var/log/messages | grep gnome

and reply with the output here.

Thanks.

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


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

Here the output ..

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


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


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


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

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

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


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

Created attachment 127129
gpm verbose trace

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


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

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

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


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

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

Thanks.

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


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

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

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


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

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


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


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

Created attachment 127140
full gpm verbose output

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

-

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

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

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


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

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

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

How reproducible:
Always.

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

Expected results:
Normal work

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

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


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

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

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

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


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

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

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


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

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

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


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

I believe AOL have fixed their servers.

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


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

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

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

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

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

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

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

[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Expired

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

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

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

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

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

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

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


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

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

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

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

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

X server version data:
The X.Org Foundation
10499901

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



Additional info:

Hardware: Macbook (late 2006 model)

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


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

Created attachment 305510
screenshot of the error message

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


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

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

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



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


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

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

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

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

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


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

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


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


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

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

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

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

/jpo


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


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

Eelco:

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

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

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

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

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


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

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

[Bug 268141] Re: no ssh-agent after resume from hibernate

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

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

On 2008-07-06T09:15:54+00:00 Julian wrote:

Description of problem:
After resume from either suspend or hibernate, seahorse agent does not ask for
keyring password, so for instance to commit to Fedora cvs I have to enter the
ssh keys password a few times. Before the resume a window pops out and the
password is required only once.

Version-Release number of selected component (if applicable):
2.22.2-1.fc9

How reproducible:
every time

Steps to Reproduce:
1. suspend/hibernate the machine
2. resume
3. do something that requires entering ssh key password

Actual results:
password prompt appears in the console every time ssh key is needed

Expected results:
a window pops out and asks for password only once

Additional info:
I don't know if it's related, but ssh-add does not work either (says “Could not
open a connection to your authentication agent.”), so there is really no way to
avoid the need for entering the password several times, apart from reboot.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/0

On 2008-08-19T17:35:07+00:00 Julian wrote:

I think you need to do something that requires entering ssh key password
before suspend as well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/1

On 2008-11-26T06:45:51+00:00 Julian wrote:

Erm, it is still present with Fedora 10. After thorough testing, I found
out that this bug is only triggered by hibernation, and that you don't
have do to anything prior to it. Do I need to say it makes hibernation
pretty much useless, since once you resume you need to input your
keyring password every time? Imagine updating a package in cvs like
that...

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

On 2008-12-13T19:18:07+00:00 Matthias wrote:

This is a somewhat confused bug report.

If you are talking about ssh, seahorse is not involved, gnome-keyring-
daemon is acting as ssh agent.

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

On 2009-01-13T11:46:54+00:00 Julian wrote:

$ gnome-keyring-daemon
** Message: another SSH agent is running at: /tmp/keyring-XZf6Tg/ssh
GNOME_KEYRING_SOCKET=/tmp/keyring-SR9ZYj/socket
SSH_AUTH_SOCK=/tmp/keyring-SR9ZYj/ssh
GNOME_KEYRING_PID=17745

This is what happens if I try to start gnome-keyring-daemon manually
after waking up from hibernation.

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

On 2009-01-13T12:33:24+00:00 Julian wrote:

On the other hand, gnome-keyring-daemon does not show up in the list of
running processes.

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

On 2009-02-05T02:26:23+00:00 Ian wrote:

Possibly related to this - gnome-keyring-daemon *sometimes* dies if left
running overnight.  For example yesterday afternoon I had this:

   > set | grep SSH
   SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
   SSH_AUTH_SOCK=/tmp/keyring-y0Zso0/ssh

   > fuser $SSH_AUTH_SOCK
 2674
   > ps h `fuser $SSH_AUTH_SOCK`
2674 ?S  0:37 /usr/bin/gnome-keyring-daemon -d --login

All working nicely.  This morning I got:

   > set | grep SSH
   SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
   SSH_AUTH_SOCK=/tmp/keyring-y0Zso0/ssh

   > fuser $SSH_AUTH_SOCK

which means the gnome-keyring-daemon process has died.

It seems like the process dies (or is killed) when the screensaver is
unlocked in the morning rather than during the night.  (screensaver
unlock doesn't always do that though).

--
Ian

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/268141/comments/28

On 2009-02-18T09:05:46+00:00 Julian wrote:

I checked with gdb and got the following:
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7f68bc4f4950 (LWP 5401)]
0x0032b3432f05 in raise (sig=)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0  0x0032b3432f05 in raise (sig=)
at ../nptl

[Bug 410407] Re: Buttons don't respond to mouse clicks

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

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


On 2009-11-29T19:24:18+00:00 Hicham wrote:

Description of problem:
With compiz enabled flash objects become unresponsive.

Version-Release number of selected component (if applicable):
nspluginwrapper-1.3.0-8.fc12.i686

How reproducible:
always

Steps to Reproduce:
1.Enable compiz on F12
2.Open a webpage with flash objects
3.Try to click on them
  
Actual results:
no response to mouse clicks

Expected results:
response to mouse clicks

Additional info:
a temporary workaround would be to add the line
export GDK_NATIVE_WINDOWS=1 
to npviewer.sh

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/196


On 2009-12-01T05:02:40+00:00 Walter wrote:

Is this directly related to Adobe Reader not functioning?  At work we've
also discovered that Lotus Notes 8.5 has a "grey screen" which
unfortunately the GDK_NATIVE_WINDOWS workaround does not help with (it
doesn't make it to eclipse for whatever reason when executing the main
notes bin with the workaround env set, which is the GUI with the
problem) and the only workaround so far is to LD_PRELOAD 2.16 GTK libs.

Is a fix at the GTK level in the works, or is there a GTK bug at all?
I'm sure more of these things will be found, hopefully most of them
easily fixed with the GDK_NATIVE_WINDOWS workaround.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/198


On 2009-12-01T12:50:02+00:00 Hicham wrote:

No, it is not, and it is not Fedora specific, it is introduced by gtk
2.18. Official Adobe Flash are suffering from this bug, I don't know
about gnash. I think of it as a third party issue, since current Adobe
Flash Plugin have been released before gtk-2.18.

I was confused about where to file the bug, but since we can have a
temporary fix in Fedora, i preferred filing the bug here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/199


On 2009-12-04T13:15:55+00:00 Ben wrote:

A work around is described here:

http://forums.fedoraforum.org/showthread.php?t=233489

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/202


On 2009-12-04T13:22:48+00:00 Walter wrote:

Already documented in the F12 Common Bugs..
https://fedoraproject.org/wiki/Common_F12_bugs#Non_Responsive_Flash_Objects

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/203


On 2009-12-04T15:22:28+00:00 Martin wrote:

Added to nspluginwrapper-1.3.0-10.fc12

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/204


On 2009-12-04T15:34:03+00:00 Fedora wrote:

nspluginwrapper-1.3.0-10.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/nspluginwrapper-1.3.0-10.fc12

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/205


On 2009-12-04T18:02:34+00:00 Hicham wrote:

Thanks Martin for the fix ! can we close this bug report now ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/206


On 2009-12-07T07:32:29+00:00 Fedora wrote:

nspluginwrapper-1.3.0-10.fc12 has been pushed to the Fedora 12 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/flashplugin-
nonfree/+bug/410407/comments/207


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

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

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

Title:
  Buttons don't respond to mouse clicks

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/410407/+subscriptions

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

[Bug 136837] Re: Mixer applet randomly decides to consider my sound card to be "muted" when changing volume

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

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

On 2007-09-18T18:53:05+00:00 Ugo wrote:

Description of problem:
just updated my devel system to today rawhide release, and
gnome-applets-2.20.0-1.fc8 was updated, now when i change the volume level via
mixer applet, the tooltip doesn't update the current volume any more... always
show the old one (the volume level at user logon)

i think this could be a symptom of a wider problem caused by the latest gtk2
tooltip's framework rewrite... i also noted a increase of delay when showing
tooltips and updating his contents in realtime (in Fedora7 it's almost 
immediate)

Version-Release number of selected component (if applicable):
gnome-applets-2.20.0-1.fc8

How reproducible:
click in the volume mixer applet and change the volume

Steps to Reproduce:
1.
2.
3.

Actual results:
the tooltips remain stucked to login volume

Expected results:
change the volume tooltip content in realtime as volume change from the mixer

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/10

On 2007-09-19T06:02:58+00:00 Matthias wrote:

I don't think that GTK is to blame for this; there is other brokenness in the
mixer applet right now, e.g. the values dont' always go from 0 to 100, and 
the muting/unmuting happens semi-randomly when changing the level. This may 
be fallout from the switch from polling to notification.

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

On 2007-09-19T07:52:15+00:00 Ugo wrote:

Yes i agree, i verified other apps and the tooltips visualization is
working fine.

Best Regards

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/12

On 2007-09-20T00:19:13+00:00 Bastien wrote:

(In reply to comment #1)
> I don't think that GTK is to blame for this; there is other brokenness in the
> mixer applet right now, e.g. the values dont' always go from 0 to 100, and 
> the muting/unmuting happens semi-randomly when changing the level. This may 
> be fallout from the switch from polling to notification.

I've fixed those bits, should be in 1:2.20.0-2. The problem also exists upstream
(without the notification patch) when changing the volume fast, some calls to
alsa-lib fail, but we don't know that. So we ignore the failed gets/sets and
just use the value that's in the UI.

The obvious problem is that the hardware and the UI might get out of sync, but
that's better than the UI going bananas and the mute state switching all over
the place. I filed http://bugzilla.gnome.org/show_bug.cgi?id=478498 against
GStreamer, and http://bugzilla.gnome.org/show_bug.cgi?id=478485 against the 
applet.

Let me know how the new build works for you. Should be at:
http://koji.fedoraproject.org/koji/taskinfo?taskID=166805

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/13

On 2007-09-20T01:13:44+00:00 Ugo wrote:

Hi Bastien,

just tried your patch and now the mixer applet is working good!

i also noted the out of sync mixer bug, but it happened  only on fast volume
change... however the mixer applet is now fully usable...
many thanks for your light fast patch, very very good job Bastien.

Best Regards

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/14

On 2007-09-20T10:15:35+00:00 Bastien wrote:

Excellent, thanks for testing Ugo.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/16

On 2007-09-24T20:55:35+00:00 Bastien wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/19

On 2007-09-24T23:48:32+00:00 Thomas wrote:

Is this patch supposed to be in rawhide yet? The referenced packages are older
than what's currently there.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
applets/+bug/136837/comments/20

On 2007-09-25T11:50:51+00:00 Bastien wrote:

(In reply to comment #7)
> Is this patch supposed to

[Bug 137738] Re: [gutsy] suspend / hibernate works fine, but after resume, I get a "Failed to suspend" popup

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

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


On 2007-09-29T22:21:48+00:00 Matthew wrote:

Description of problem:
I hibernate my Thinkpad T61 and that seems to work fine, but on resume the pm
applet pops up a balloon saying it failed.

Version-Release number of selected component (if applicable):
pm-utils-0.99.4-3.fc8

How reproducible:
Always

Steps to Reproduce:
1. Hibernate using pm applet.
2. Resume.
3.
  
Actual results:
Error balloon pops up claiming hibernate failed.

Expected results:
No error ballon.  (Either because it worked or because whatever error occured
has been fixed...)

Additional info:

I'm attaching pm-suspend.log and relevant secctions of messages.  I had SELinux
in permissive mode for this test, but you will see some AVCs in the log.

(Looking at the log, I'm not sure if this is a pm-utils issue or a kernel issue,
but I'll file here first.)

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


On 2007-09-29T22:25:09+00:00 Matthew wrote:

Created attachment 211441
pm-suspend log from "failed" hibernate

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


On 2007-09-29T22:26:07+00:00 Matthew wrote:

Created attachment 211451
portion of /var/log/messages related to "failed" hibernate

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


On 2007-09-30T09:38:31+00:00 Till wrote:

Afaik, the applet belongs to gnome-power-manager, the pm-suspend does not
contain any warnings, therefore I guess it is an applet issue.
Maybe you need to increase verbosity to get a helping log, because the critical
log entries seem to be:

Sep 29 18:02:37 valkyrie gnome-power-manager: (mjs) Resuming computer
Sep 29 18:02:37 valkyrie gnome-power-manager: (mjs) hibernate failed

But a reason why it failed is missing.

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


On 2007-09-30T21:15:37+00:00 Matthew wrote:

OK How do I get better debug logs?  Thanks.

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


On 2007-10-05T03:15:33+00:00 Matthias wrote:

David, any clue about this ?

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


On 2007-10-05T15:17:39+00:00 David wrote:

g-p-m is expect the wrong return types from hal; so I wrote a patch (will attach
in the next comment) but for some reason beyond me I still get the "Sleep
problem" dialog from g-p-m. Richard, what gives?

FWIW, it works fine using dbus-send:

[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.DBus.Introspectable.Introspect |grep -2 Suspend
  
  

  
  


  
  
[davidz@oneill ~]$ 
[davidz@oneill ~]$ 
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
method return sender=:1.4 -> dest=:1.434 reply_serial=2
   int32 0
[davidz@oneill ~]$ 
[davidz@oneill ~]$ 
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.DBus.Introspectable.Introspect |grep -2 Hibernate
  


  

[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
[davidz@oneill ~]$ 
[davidz@oneill ~]$ 
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
method return sender=:1.4 -> dest=:1.487 reply_serial=2
   int32 0


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


On 2007-10-05T15:18:54+00:00 David wrote:

Created attachment 217621
Patch to fix expected return types

This patch should go upstream.

Reply at: https://bugs.launchpad.net/ubun

[Bug 207744] Re: Clicking notification panel icon doesn't switch desktops

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

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


On 2007-11-08T13:53:02+00:00 Adrian wrote:

Description of problem:

With this patch (metacity-firefox-workaround-2.patch) the used behaviour of
pidgin when clicking on the tray icon changed/broke.

Up until this patch it was possible to click on the tray icon of pidgin and no
matter on which workspace this is done the buddy list appears on that workspace.

Now if clicking the tray icon the buddy list just disappears on the workspace it
is displayed and clicking it again lets it appear on the other workspace.

>From my point of view this is a regression in the usability of my usage of the
whole desktop.

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

metacity-2.20.0-3.fc8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/0


On 2007-11-11T11:25:59+00:00 Pedro wrote:

I confirm this behaviour and also think this is a regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/1


On 2007-11-11T11:48:30+00:00 Yanko wrote:

Same thing with liferea and its behavior on clicking the notification
icon.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/2


On 2007-11-11T20:56:07+00:00 Matthias wrote:

CCing Colin, who did that patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/3


On 2007-11-12T17:28:37+00:00 Colin wrote:

What's happening here is that the Pidgin buddy list feels very similar to a menu
popup, but is actually implemented as a regular window.  Pidgin seems to be one
of the few applications where the application relied on the behavior of
gtk_window_present() bringing windows to the current workspace.

On Compiz it seems to have the same behavior, which is interesting, because
before Compiz and Metacity differed on the gtk_window_present(), so there must
be some Pidgin-specific differentiation occuring somehow.

Anyways, since the Firefox patch was removed before Fedora 8, there isn't much
point to having this patch in Fedora 8 either.  I will remove it and add an 
update.

We will figure out how to fix Firefox and Metacity together for Fedora 9, and
update them in sync.



Reply at: 
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/4


On 2007-11-13T05:41:37+00:00 Elijah wrote:

This sounds like pidgin is trying to use _NET_ACTIVE_WINDOW as a hack to
simulate "launching" the buddy window?  It could just launch it and then we know
to move it to the right workspace...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/5


On 2008-04-16T17:43:10+00:00 Etan wrote:

For the record pidgin has no policy decisions on what should or shouldn't 
happen when the use clicks the tray icon. All pidgin wants is that the buddy 
list window be presented to the user as such using gtk_window_present is the 
correct thing for us to be doing. Any policy decisions on what that means for 
pidgin are squarely in the realm of the window manager, desktop environment, 
and user preference. So again, pidgin itself relies on no specific behaviour 
out of gtk_window_present other than that of 'presenting the window to the 
user'.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/207744/comments/9


On 2008-05-14T03:51:43+00:00 Bug wrote:

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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


On 2009-06-09T23:09:39+00:00 Bug wrote:


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

Package Maintainer: If you wish for this bug to remain open because you
pl

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

** Also affects: libinput (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libinput via
   https://bugs.freedesktop.org/show_bug.cgi?id=103298
   Importance: Unknown
   Status: Unknown

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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

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

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

[Bug 1727770] Re: wayland does not have logic for a Lenovo laptop on the dock

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

** Summary changed:

- wayland does not have logic for a Lenovo laptop on the dock
+ If I resume on the dock, Gnome Shell seems to recognize the lid as closed and 
suspends

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

Title:
  If I resume on the dock, Gnome Shell seems to recognize the lid as
  closed and suspends

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

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

[Bug 1721762] Re: Cancelled installation of snap continues

2017-10-26 Thread Robert Ancell

Note the UI didn't support cancelling in Xenial.

** No longer affects: gnome-software (Ubuntu Xenial)

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

Title:
  Cancelled installation of snap continues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1721762/+subscriptions

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

[Bug 1727902] Re: gnome-shell crashed with signal 5 in GI_poll() from g_main_context_poll() from g_main_context_iterate() from g_main_loop_run()

** Summary changed:

- gnome-shell crashed with signal 5 in __GI___poll()
+ gnome-shell crashed with signal 5 in __GI___poll() from g_main_context_poll() 
from g_main_context_iterate() from g_main_loop_run()

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

Title:
  gnome-shell crashed with signal 5 in __GI___poll() from
  g_main_context_poll() from g_main_context_iterate() from
  g_main_loop_run()

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

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

[Bug 1727742] Re: "peek" hangs Wayland display server

"Wayland" is only a protocol. The product you are using is gnome-shell.

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

Title:
  "peek" hangs Wayland display server

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

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

[Bug 1727603] Re: gnome-shell crashed with signal 5 in GI_libc_free() from g_free() from g_key_file_parse_key_value_pair()

Thanks, but that bug seems to be less conclusive for some reason. Maybe
repeat a couple of times? Or maybe the MALLOC_CHECK_ is now hitting a
much earlier issue not related to this one.

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

Title:
  gnome-shell crashed with signal 5 in __GI___libc_free() from g_free()
  from g_key_file_parse_key_value_pair()

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

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

[Bug 1727770] [NEW] wayland does not have logic for a Lenovo laptop on the dock

You have been subscribed to a public bug:

I have a Lenovo T440s (haswell) and an ultradock with external monitor.

If I resume on the dock, wayland seems to recognize the lid as closed
and suspends. The work around is to (1) open the lid, bring up the
display control tab and switch to single monitor, choose the external
one (on the DP); and (3) apply.  Then I can close the lid.

The laptop will boot correctly on the dock with the lid closed.

I tried changing the dconf parameter org.gnome.settings-
daemon.plugins.power to 'nothing' but that doesn't seem to matter.

Obviously, this is not a critical issue, but it sure is annoying.  This
should "just work".

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libwayland-server0 1.14.0-1
Uname: Linux 4.13.9-041309-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:59:35 2017
Dependencies:
 gcc-7-base 7.2.0-8ubuntu3
 libc6 2.26-0ubuntu2
 libffi6 3.2.1-6
 libgcc1 1:7.2.0-8ubuntu3
DistUpgraded: 2017-10-20 11:39:46,873 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 4.13.0-16-generic, x86_64: installed
 acpi-call, 1.1.0, 4.13.9-041309-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2016-05-06 (537 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20ARA0S100
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.9-041309-generic 
root=UUID=0a196d38-a419-4a42-b659-7108068e6ce5 ro quiet splash vt.handoff=7
SourcePackage: wayland
UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
dmi.bios.date: 03/19/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET74WW (2.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ARA0S100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20ARA0S100
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
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 N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu wayland-session
-- 
wayland does not have logic for a Lenovo laptop on the dock
https://bugs.launchpad.net/bugs/1727770
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

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

[Bug 1725888] Re: Ubuntu 17.10: clipboard contents lost if app is closed (Wayland)

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

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

Title:
  Ubuntu 17.10: clipboard contents lost if app is closed (Wayland)

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

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

[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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

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

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

[Bug 1727330] Re: is not adjusted for natural scrolling in the mouse control panel

Sorry the image in comment #3 seems to have gone missing.

Please open:  Settings > Devices > Mouse & Touchpad
Now take a screenshot with Alt+PrtScn and attach it here.

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

Title:
  is not adjusted for natural scrolling in the mouse control panel

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

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

[Bug 1727322] Re: tasks in the calendar are not added and not synced with Google

OK then. Unlinking https://bugzilla.gnome.org/show_bug.cgi?id=546088 so
that this bug doesn't appear in the bug list any more.

** No longer affects: gnome-shell

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

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

Title:
  tasks in the calendar are not added and not synced with Google

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

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

[Bug 1727310] Re: change screen brightness not working

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

** Summary changed:

- change screen brightness not working
+ Screen brightness slider isn't working  on Acer Aspire v5 571g

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

Title:
  Screen brightness slider isn't working  on Acer Aspire v5 571g

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

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

[Bug 328277] Re: can not login using ssh anymore

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

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


On 2009-02-06T22:27:00+00:00 John wrote:

Description of problem:
Some rawhide update today broke ssh, but I can't work out what!  I tried 
backing down openssh to an earlier release, but that didn't fix it.  Reporting 
against openssh anyway.

As a regular user, ssh fails with:
   buffer_get_ret: trying to get more bytes 4 than in buffer 0
   buffer_get_int: buffer error

(Really helpful error message, NOT!   Try googling for:
  "buffer_get_ret: trying to get more bytes 4 than in buffer 0"
to see how common it is!)

As root, ssh to the same target works.

Version-Release number of selected component (if applicable):
openssh-5.1p1-6.fc11.x86_64

How reproducible:
100%

Steps to Reproduce:
1.ssh -vvv bock
2.
3.
  
Actual results:
...
debug1: Host 'bock' is known and matches the RSA host key.
debug1: Found key in /home/ellson/.ssh/known_hosts:57
debug2: bits set: 514/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
buffer_get_ret: trying to get more bytes 4 than in buffer 0
buffer_get_int: buffer error
 


Expected results:
1. Working ssh.
2. Greatly improved errors messages!


Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/328277/comments/0


On 2009-02-06T22:51:00+00:00 John wrote:

The problem seems to be caused by my id_dsa key ???   Removing that and
the id_rsa key works fine.

I use that dsa key in a lot of places, so I don't want to remove it permanently.
Whats going on?

A working rsa public key:

debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/ellson/.ssh/id_rsa (0x2880550)
debug3: input_userauth_banner


Same site, with the id_dsa & id_dsa.pub restored into .ssh/ 

debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
buffer_get_ret: trying to get more bytes 4 than in buffer 0
buffer_get_int: buffer error

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/328277/comments/1


On 2009-02-09T11:18:43+00:00 Tomas wrote:

What have you upgraded - client or server? What is the openssh version
on the other end? What happens if you do 'unset SSH_AUTH_SOCK' before
running the ssh client?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/328277/comments/2


On 2009-02-09T12:22:23+00:00 Tomáš wrote:

Same here, today's rawhide, cannot connect from client to server.

client:
openssh-5.1p1-6.fc11.x86_64
openssl-0.9.8j-7.fc11.x86_64
glibc-2.9.90-3.x86_64
gcc-4.4.0-0.16.x86_64

server:
openssh-5.1p1-6.fc11.i386
openssl-0.9.8j-6.fc11.i686
glibc-2.9.90-3.i686
gcc-4.3.2-7.i386


Removing ~/.ssh/known_hosts didn't help.

Unsetting SSH_AUTH_SOCK helped.

$ echo $SSH_AUTH_SOCK
/tmp/keyring-c543Ad/socket.ssh

So... this looks like gnome-keyring error :-/

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


On 2009-02-09T12:29:05+00:00 Tomas wrote:

Yes, if unsetting SSH_AUTH_SOCK helps and it points to gnome-keyring and
not regular ssh_agent it is gnome-keyring bug.

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


On 2009-02-09T18:07:58+00:00 John wrote:

Using ssh from a ssh login session, without a desktop and with no SSH_AUTH_SOCK
set, works ok.When I get back home tonight I'll see if SSH_AUTH_SOCK
is set and if unsetting it helps me,  but that seems likely based on Comment #4.

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

[Bug 329881] Re: Weather applet uses defunct station for Berlin weather

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

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-05T18:53:12+00:00 Lebenskuenstler wrote:

I hope I report against the right package. If not so, please reassign.

Description of problem:

I am using the weather forecast feature at the GNOME Desktop. Since the
airport Berlin Tempelhof was closed at Oct 31rd it does not send correct
weather data anymore. Since this date, I at always has says something
about a weather of 4 degrees. Luckily it is currently not that cold
around here :)

If I use instead of Berlin Tempelhof Schönefeld or Tegel instead, I get
the correct weather data.

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

Gnome 2.22, also Gnome 2.24

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/0

On 2008-11-26T04:50:00+00:00 Bug wrote:

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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/1

On 2009-01-10T13:46:59+00:00 Steve wrote:

Confirming this bug with:
gnome-panel-2.24.2-1.fc10.i386
libgweather-2.24.2-1.fc10.i386

A Wireshark capture shows that the applet sends this query for Berlin-
Tempelhof:

http://weather.noaa.gov/cgi-bin/mgetmetar.pl?=EDDI

The reply includes this date/time: 2008/10/30 23:50 UTC

The panel applet could display this date/time so that a user would know
how old the observations are. It might also be useful to flag stale
observations (older than 24 hours, say).

Another enhancement would be to display the full location name.
For example, the "Current Conditions" tab could show "Berlin-Tempelhof" instead 
of  "Berlin".

Also, the label "City" is misleading. It would more accurate to say
"Location".

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/2

On 2009-01-10T13:49:39+00:00 Steve wrote:

For completeness, here is the full reply from:
http://weather.noaa.gov/cgi-bin/mgetmetar.pl?=EDDI

Latest METAR Observation(s) for: EDDI
EDDI

The most recent METAR observation from EDDI in our system was generated
at the source at:

2008/10/30 23:50 UTC

The observation is:
EDDI 302350Z 26007KT  FEW006 BKN011 04/04 Q1003

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/3

On 2009-01-10T19:04:07+00:00 Steve wrote:

It appears that inactive stations are removed with the aid of a Python script.
http://svn.gnome.org/viewvc/libgweather/trunk/data/sources/README.sources?view=markup

However, Berlin-Tempelhof is in SVN rev. 534.
http://svn.gnome.org/viewvc/libgweather/trunk/data/Locations.xml.in?view=log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/4

On 2009-01-10T22:07:50+00:00 Steve wrote:

(In reply to comment #2)

> The panel applet could display this date/time so that a user would know how 
> old
> the observations are. It might also be useful to flag stale observations 
> (older
> than 24 hours, say).

See Bug 479539 -  Weather Report applet may report incorrect month for
"Last update"

> Another enhancement would be to display the full location name.
> For example, the "Current Conditions" tab could show "Berlin-Tempelhof" 
> instead
> of  "Berlin".

See Bug 479529 -  Weather Report applet does not display enough of the
location name

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/5

On 2009-01-13T14:52:33+00:00 Dan wrote:

re-filed upstream as http://bugzilla.gnome.org/show_bug.cgi?id=567607.
This will likely be fixed for F11.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/329881/comments/6

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

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

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

Title:
  Weather applet uses defunct station for Berlin weather

To manage notifications a

[Bug 1070006] Re: Mobile Broadband Fails to Configure on Ubuntu-Gnome (ZTE MF622)

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

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-08T18:34:12+00:00 Need wrote:

My modem is not supported by Fedora rawhide. I have installed and run
usb_modeswitch. It now shows:

# lsusb
Bus 002 Device 005: ID 19d2:0031 ONDA Communication S.p.A. 

I have also added a new fdi file and rebooted:

# cat /usr/share/hal/fdi/information/20thirdparty/20-zte-mf636.fdi


   

  
 

GSM-07.07
GSM-07.05
modem

 
  
   


Unfortunately it does not seem to be detected by NetworkManager.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/0


On 2009-11-16T15:19:28+00:00 Bug wrote:


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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/1


On 2009-11-25T14:10:13+00:00 robledo wrote:

I have found that with modem ZTE MF626, F12 automatically mounts a usb-
mass-storage device, and if ejected (while keeping the usb-modem
connected), the modem is recognized, and connections are possible.

Pls see output in bug report
https://bugzilla.redhat.com/show_bug.cgi?id=541314

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/2


On 2009-12-01T08:59:09+00:00 Dan wrote:

lsof, can you attach some 'dmesg' output from right when you plug the
device in, through when it's modeswitched, through when NM fails to
recognize the device?  I'd like to see if it's correctly modeswitched or
not.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/3


On 2009-12-01T09:54:29+00:00 robledo wrote:

Dan, if you need output for the ZTE MF 626 (not 636), let me know.  Same
issue.  Pls give precise instructions on how to "dmesg", however.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/4


On 2009-12-01T22:36:03+00:00 Need wrote:

It's not modeswitched, I have to wrong the usb_modeswitch utility
manually with a custom config file. I will post the output before and
after tomorrow. Before the modeswitch the virtual cdrom is mounted.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/5


On 2009-12-01T22:49:55+00:00 Need wrote:

s/wrong/run/;

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/6


On 2009-12-01T22:57:20+00:00 robledo wrote:

Created attachment 375229
dmesg output for zte mf626


attached output from dmesg > ztemf626.log, when 1) attached usb modem ZTE MF 
626, 2) eject mass-storage device, leading to 3) recognition of mf 626 modem in 
NW, to 4) establish the 3G connection (disable wifi), and then 5) disconnect 
the 3G connection, and finally 6) try to reconnect the 3G connection. 
hope it helps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1070006/comments/7


On 2009-12-02T08:53:42+00:00 Need wrote:

I plug in the usb stick:

# dmesg -c
usb 2-2: new high speed USB device using ehci_hcd and address 5
usb 2-2: New USB device found, idVendor=19d2, idProduct=2000
usb 2-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-2: Product: ZTE CDMA Technologies MSM
usb 2-2: Manufacturer: ZTE, Incorporated
usb 2-2: configuration #1 chosen from 1 choice
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 7:0:0:0: CD-ROMZTE  USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 0
sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
sr 7:0:0:0: Attached scsi CD-ROM sr0
sr 7:0:0:0: Attached scsi generic sg1 type 5
ISO 9660 Extensions: Microsoft Joliet Level 1
ISOFS: changing to secondary root
SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts

# lsusb 
Bus 002 Device 005: ID 19d2:2000 ONDA

[Bug 1609874] Re: Close button on windows in Activities Overview still works, but is not visible

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

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-07-17T16:28:30+00:00 Michael wrote:

Created attachment 1299949
Screenshot

Description of problem:
When opening the Gnome Shell Activities view the small "X" circle button is not 
visible anymore on top right corner of the window screenshot of a running 
application. I'm attaching a screenshot with a red circle highlighting the area 
where the close window button was normally visible. If you click your mouse in 
the area the button would be the window is closed.

Version-Release number of selected component (if applicable):
gnome-shell-3.24.2-1.fc26.x86_64

How reproducible: Always


Steps to Reproduce:
1. Open Activities view
2.
3.

Actual results: No icon visible.
Everytime I open the "Activities" view my system log is spammed with a dozen 
duplicate messages:
Jul 17 10:32:04 melchior.cchtml.com gnome-shell[1725]: Failed to load 
resource:///org/gnome/shell/theme/close-window.svg: Unrecognized image file 
format


Expected results: Icon visible. No log spam.


Additional info:
https://bugzilla.gnome.org/show_bug.cgi?id=769524

Reply at: https://bugs.launchpad.net/ubuntu-
gnome/+bug/1609874/comments/2


On 2017-07-21T15:01:19+00:00 Michael wrote:

This problem is only present on one of three systems I use regularly. On
the problem system: The GdkPixbuf SVG loader is present just as it is on
the other two systems. However, I notice that it is not loaded into
memory as it is on the two working systems.

I then checked out the loader.cache. Bingo. The cache had been
regenerated recently, but was smaller than the other systems that work.
After regenerating the cache (gdk-pixbuf-query-loaders-64 --update-
cache) and restarting gnome-shell the SVG icons appear in Activities and
the log messages stop. The 32-bit cache was correct.

Before:
-rw-r--r--. 1 root root 3035 Jul 11 21:05 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache

After:
-rw-r--r--. 1 root root 3355 Jul 21 09:52 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache

I would assume the gdk-pixbuf-query-loaders did not get called when the
SVG loader was installed? An issue during the upgrade from Fedora 25 to
Fedora 26?

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


On 2017-08-16T14:17:51+00:00 Kalev wrote:

Hm, not sure what happened, but the way it should work is that librsvg2
drops the loader in %{_libdir}/gdk-pixbuf-2.0/2.10.0/loaders and then
these two file triggers in gdk-pixbuf2 should take care of rebuilding
the cache:

%transfiletriggerin -- %{_libdir}/gdk-pixbuf-2.0/2.10.0/loaders
gdk-pixbuf-query-loaders-%{__isa_bits} --update-cache

%transfiletriggerpostun -- %{_libdir}/gdk-pixbuf-2.0/2.10.0/loaders
gdk-pixbuf-query-loaders-%{__isa_bits} --update-cache

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


On 2017-09-09T08:39:19+00:00 Jan wrote:

I have this issue as well. I have also this error in my logs:

Failed to load resource:///org/gnome/shell/theme/close-window.svg:
Unrecognized image file format

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


On 2017-09-09T09:02:07+00:00 Jan wrote:

Also for me the issue was resolved after regenerating the cache:

[root@nyx ~]# ls -slah /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 3.0K 25 aug 20:20 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 2.8K 25 aug 20:20 
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
[root@nyx ~]# gdk-pixbuf-query-loaders-32 --update-cache
[root@nyx ~]# gdk-pixbuf-query-loaders-64 --update-cache
[root@nyx ~]# ls -slah /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 3.3K  9 sep 10:54 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache
4.0K -rw-r--r--. 1 root root 2.8K  9 sep 10:53 
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache

Reply at: https://bugs.launchpad.net/ubuntu-
gnome/+bug/1609874/comments/8


** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Undecided

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

Title:
  Close button on windows

[Bug 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome

I have put your two screenshots side by side, flipped, and zoomed in.
See attached.

It appears there is no difference in the window decoration edges
(although the different wallpaper colour behind makes them look
different).

There is definitely a change in the X button design that is now visible.

** Attachment added: "decor.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+attachment/4997372/+files/decor.png

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

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

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

Title:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome

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

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

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

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=789523
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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

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

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

[Bug 31709] Re: Brasero, GNOME's burn:/// and K3b slow dvd burn speed

2017-10-26 Thread Christopher M. Penalver

** No longer affects: brasero (Ubuntu)

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

Title:
  Brasero, GNOME's burn:/// and K3b slow dvd burn speed

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

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

[Bug 1727902] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727902/+attachment/4997336/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in __GI___poll()

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

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

[Bug 1727902] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1727902/+attachment/4997335/+files/StacktraceSource.txt

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

Title:
  gnome-shell crashed with signal 5 in __GI___poll()

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

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

[Bug 1725888] Re: Ubuntu 17.10: clipboard contents lost if app is closed (Wayland)

2017-10-26 Thread dennyg...@gmail.com

I gave all the information needed. not incomplete.

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

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Ubuntu 17.10: clipboard contents lost if app is closed (Wayland)

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

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

[Bug 1727902] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1727902/+attachment/4997334/+files/Stacktrace.txt

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

Title:
  gnome-shell crashed with signal 5 in __GI___poll()

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

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

[Bug 1727902] gnome-shell crashed with signal 5 in GI_poll()

StacktraceTop:
 __GI___poll (fds=0x55811f323800, nfds=16, timeout=2771) at 
../sysdeps/unix/sysv/linux/poll.c:29
 g_main_context_poll (priority=, n_fds=16, fds=0x55811f323800, 
timeout=, context=0x558118379dd0) at 
../../../../glib/gmain.c:4187
 g_main_context_iterate (context=0x558118379dd0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
../../../../glib/gmain.c:3881
 g_main_loop_run (loop=0x55811865ce50) at ../../../../glib/gmain.c:4082
 meta_run () at core/main.c:648

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

Title:
  gnome-shell crashed with signal 5 in __GI___poll()

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

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

[Bug 1727902] [NEW] gnome-shell crashed with signal 5 in GI_poll()

2017-10-26 Thread Hiruna Wijesinghe

Public bug reported:

How I was able to recreate the crash multiple times:

1. Login
2. Open terminal, run sudo nautilus
--> I get this error :

Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
Connection refused

(nautilus:4129): Gtk-WARNING **: cannot open display: :0

3. Run su, login and run nautilus
4. Navigate to /opt/
5. Open a file and close it
6. Copy that file to my non root desktop (/home/hiruna/Desktop in my case)
7. Open the file normally from the non root user
--> Immediate freeze

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
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 12:32:17 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-05-24 (155 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 __GI___poll (fds=0x55811f323800, nfds=16, timeout=2771) at 
../sysdeps/unix/sysv/linux/poll.c:29
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? ()
Title: gnome-shell crashed with signal 5 in __GI___poll()
UpgradeStatus: Upgraded to artful on 2017-10-19 (7 days ago)
UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo video

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace package-from-proposed 
third-party-packages wayland-session

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in __GI___poll()

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

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

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

Peter, we're here to help. And Sebastien is right... The fastest way to
a fix for you now is for you to report the bug directly on the Gnome bug
tracker:  https://bugzilla.gnome.org/

We ask you to do this because the conversation that will happen with the
Gnome guys needs to be with someone who experiences the problem first-
hand (yourself).

After a fix is available there we will pull it down to here again for
release in Ubuntu.

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

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1727603] Re: gnome-shell crashed with signal 5 in GI_libc_free() from g_free() from g_key_file_parse_key_value_pair()

2017-10-26 Thread Hiruna Wijesinghe

Hi Daniel,


Here is the new bug report. 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727902

After changing the /etc/environment, the crash didn't freeze the whole
computer instead it froze the desktop.

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

Title:
  gnome-shell crashed with signal 5 in __GI___libc_free() from g_free()
  from g_key_file_parse_key_value_pair()

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

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

[Bug 260918] Re: needed: libv4l and associated application patches (or "gspca stopped working in 2.6.27")

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

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-27T20:49:53+00:00 Hans wrote:

As you probably know I'm one of the authors of the v4l2 rewrite of the gspca usb
webcam driver framework (which supports more then 100 different cams), this v4l2
rewrite has been merged into the 2.6.27 kernel and thus will become available in
the official Linux kernel soon.

One of the parts of the v4l2 rewrite has been removing conversion from various
manufacturer cam specific video formats to more normal videoformats from the
drivers, as this really does not belong in userspace.

As a result of this the gspca subdrivers can generate raw video frames in the
following formats:

#define V4L2_PIX_FMT_SN9C10X  v4l2_fourcc('S', '9', '1', '0') /* SN9C10x
compressed bayer
#define V4L2_PIX_FMT_SPCA501  v4l2_fourcc('S', '5', '0', '1') /* YUYV per line 
#define V4L2_PIX_FMT_SPCA505  v4l2_fourcc('S', '5', '0', '5') /* YYUV per line 
#define V4L2_PIX_FMT_SPCA508  v4l2_fourcc('S', '5', '0', '8') /* YUVY per line 
#define V4L2_PIX_FMT_SPCA561  v4l2_fourcc('S', '5', '6', '1') /* compressed GBRG
bayer
#define V4L2_PIX_FMT_PAC207   v4l2_fourcc('P', '2', '0', '7') /* compressed BGGR
bayer

As we do not want to see each application implement (nor having to implement)
support for these various formats, as we like to have one code base and only one
code base for these formats. A library has been written (with me as the main
author) to convert from these formats to BGR24 or YUV420. For more on this
library see:
http://hansdegoede.livejournal.com/3636.html

The attached patch adds support to the gstreamer v4l2 plugin to use this library
if available on the system, it has also been submitted upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=545033

libv4l will show up in rawhide as soon as a cvsadmin gets around to creating a
cvs module for it, see libv4l'2 review request: bug 456772

Getting this patch into Fedora is important for the F-10 better webcam support
feature:
https://fedoraproject.org/wiki/Features/BetterWebcamSupport


###

A note about the patch, the patch is actually quite simple, as libv4l has been
designed for quick porting of existing apps to libv4l, for this reason libv4l
fully mimicks the raw /dev/video interface (and if no conversion is needed and
for non relevant calls like setting ctrl's, passes through all calls 
unmodified).

All that the patch does and all that needs to be changed to use libv4l is
replace the relevant xxx calls on /dev/video with v4l2_xxx calls.

The only special thing about the patch is that it passes the
V4L2_ENABLE_ENUM_FMT_EMULATION flag to libv4l2 on open, this patch tells libv4l2
to report the "emulated" formats in the ENUM_FMT ioctl results. Which libv4l2
does not do be default so that ENUM_FMT only reports the really supported
formats (a TRY_FMT with one of the 2 supported emulated formats can then be done
to see if conversion is supported for the specific device). Given the working of
the v4l2 plugin, enabling the ENUM_FMT emulation is needed.

I've successfully tested this patch with cheese and 2 spca561 cams (quite
popular IC, used by both logitech and creative), 2 pac207 cams (another quite
popular IC), 3 SN9C10X cams (also very popular) and 1 spca501 cam. All of which
do not work without this patch, as gstreamer does not support their proprietary
video formats (and rightfully so).

###

p.s.

While doing a local rpm testbuild of gstreamer-plugins-good with this patch, it
failed because it build a couple of plugins not in the %files list due to me
having to much foo-devel packages installed, can you please add:
"--disable-esd --disable-libcaca --disable-aalib" to the %configure flags to fix
this?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/0


On 2008-07-27T20:49:53+00:00 Hans wrote:

Created attachment 312745
PATCH adding support for using libv4l to the v4l2 plugin

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/1


On 2008-07-28T09:28:03+00:00 Hans wrote:

libv4l has just been build for rawhide, and should show up in the next rawhide
push, in the mean time you can get it from koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57774


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918/comments/2


On 2008-07-28T13:45:56+00:00 Adam wrote:

Patch looks plausible, but I'm no expert.  I'm curious to see how the upstream
bug go

[Bug 426587] Re: Very large latency in gstreamer-based voip apps

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

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

On 2009-09-04T15:55:35+00:00 Matěj wrote:

Created attachment 359824
stderr from Empathy

Description of problem:
Frist I tried to make a call with Pidgin (XMPP/Jingle) and in one case (with
upstream developer ;-)) I have managed to have a call. Except that my voice was
approx. 15 sec delayed on the other side of the communication.

Same happened to me now when using Empathy with SIP.

Version-Release number of selected component (if applicable):
empathy-2.27.91.1-6.fc12.x86_64
telepathy-sofiasip-0.5.17-1.fc12.x86_64
gstreamer-plugins-good-0.10.16-1.fc12.x86_64
pidgin-2.6.1-1.0.mc.1.fc12.x86_64

How reproducible:
100%

Steps to Reproduce:
1.just use VoIP application using GStreamer
2.
3.

Actual results:
my voice is delayed for approx. 15 sec

Expected results:
delay in reasonable amount (less than few sec, I guess)

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/0

On 2009-09-08T17:11:43+00:00 Johan wrote:

This bug is fixed by the patch http://cgit.freedesktop.org/gstreamer
/gst-plugins-base/commit/?id=058776bcf1ab218b509d19685a0b528d71c65f98 .

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/1

On 2009-10-05T19:36:49+00:00 Fedora wrote:

gstreamer-0.10.25-1.fc11,gstreamer-plugins-base-0.10.25-1.fc11 has been
submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/gstreamer-0.10.25-1.fc11,gstreamer-plugins-base-0.10.25-1.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/4

On 2009-10-07T03:14:19+00:00 Fedora wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/5

On 2009-10-07T10:48:57+00:00 Fedora wrote:

gstreamer-plugins-good-0.10.16-1.fc11 has been submitted as an update for
Fedora 11.
http://admin.fedoraproject.org/updates/gstreamer-plugins-good-0.10.16-1.fc11

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/6

On 2009-10-09T03:39:09+00:00 Fedora wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/7

On 2009-10-15T16:42:37+00:00 Matěj wrote:

Yes, quality of the call is still unusable, but that's not GStreamer (or
PA) fault. This has been fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-
base0.10/+bug/426587/comments/8

On 2009-10-21T00:47:04+00:00 Fedora wrote:

gstreamer-0.10.25-1.fc11, gstreamer-plugins-base-0.10.25-1.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/gst-plugins-
base0.10/+bug/426587/comments/9

On 2009-10-27T06:54:55+00:00 Fedora wrote:

gstreamer-plugins-good-0.10.16-1.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/gst-plugins-
base0.10/+bug/426587/comments/10

** Changed in: gst-plugins-base
Importance: Unknown => High

--
You received this bug notifica

[Bug 610600] Re: Serious video performance regression in cheese (2.28.1->2.30.1)

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

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-22T20:00:37+00:00 A. wrote:

Description of problem:
I have an asus eee 1000hd, with a built in webcam (according to kinfocenter it 
is from Vendor ID 0x4f2, Product ID 0xb071, Revision 15.44). The webcam works 
well (I used it recently for a video call with skype, under Fedora 10, and just 
recorded a  clip under windows XP. It also worls well under cheese as long as 
the "start recording" button is not pressed). However, when attempting to 
record video with cheese, once the button "start recording" is pressed, the 
video display within the cheese window goes dark, and afterwards, as the image 
reappears, it seems to do one frame per minute or so, and barely records any 
audio, which is of a totally useless quality.


Version-Release number of selected component (if applicable):
$ rpm -q cheese
cheese-2.26.2-1.fc11.i586


How reproducible:
every time

Steps to Reproduce:
1.start cheese
2.click video
3.click start recording
4.see how it breaks down, as above
5.also, check the resulting recording, and see how there is no useful output, 
perhaps only two or three frames and some clicking audio
  
Actual results:
useless recording, as per point 5 above

Expected results:
a useful ogv recording with 30 frames per second video at the chosen 
resolution, and useful audio, all in a ogv file.

Additional info:
I read some of the other bug reports on cheese, but couldn't find one that 
matched my bug

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/0


On 2009-06-22T20:47:33+00:00 A. wrote:

I just updated to rwahide's cheese, and while the problem is less
severe, it is  still very much present, and the resulting video is still
useless. However, perhaps the developers are already onto improving
something, which needs to be continued, as I can see *some* improvement.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/1


On 2009-11-23T20:11:47+00:00 A. wrote:

I just updated to Fedora 12, and I still get the same problem. Recording
video with cheese is choppy and broken. I updated the distribution this
bug relates to, to Fedora 12.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/2


On 2010-09-21T10:41:36+00:00 Adam wrote:

closing as a dupe of the newer bug more informative 572169.

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/610600/comments/21


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

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

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

Title:
  Serious video performance regression in cheese (2.28.1->2.30.1)

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

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

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

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:01:30+00:00 Nrbrtx wrote:

Description of problem:
When pressing any global keyboard shourtcut (configurable via System settings 
-> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), 
focus temporary switches from active text input to something else, then 
restores back shortly. Maybe even active window loses focus, but window frame 
does not shows this (window header remains to look active).

For example: when I press ctrl+shift here to switch keyboard layout,
when writing this description, yellow frame disappears from text input
box, text caret disappears too; they appear again when releasing
ctrl+shift. The same occurs in all other programs, i.e. terminal.

It causes serious annoyance, for example in Twitter when losing focus in
Reply text box, reply rolls up and I have to click it again with mouse
and set caret to correct place each time I switch keyboard layouts.

Other key combinations, not only ctrl+shift, also cause this.

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:
1. Open for example gedit
2. Press Ctrl+S
3. Press Create Folder button
4. Try to change keyboard layout or volume up/down
5. Focus will be removed from new folder, folder will not be created

Actual results:
Focus is removed from new folder, folder will not be created.

Expected results:
Layout changed, folder name is on desired layout, folder is created and named 
as user wants.

Additional info:
This bug exists at least in Ubuntu (see 
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090 for more 
reproduce scenarios ). The bug is reported to upstream too 
(https://bugzilla.gnome.org/show_bug.cgi?id=700316) with no luck.

Reply at: https://bugs.launchpad.net/gnome-settings-
daemon/+bug/1244090/comments/13


On 2014-04-27T08:52:13+00:00 Nrbrtx wrote:

Bug exists in Fedora 20 too.

Reply at: https://bugs.launchpad.net/gnome-settings-
daemon/+bug/1244090/comments/15


On 2014-04-28T09:25:03+00:00 Bastien wrote:

gnome-shell is responsible for capturing the media keys.

Reply at: https://bugs.launchpad.net/gnome-settings-
daemon/+bug/1244090/comments/16


On 2014-09-01T17:57:54+00:00 Nrbrtx wrote:

Fedora 20 with all installed updates. Bug is still here. Please fix it.

Reply at: https://bugs.launchpad.net/gnome-settings-
daemon/+bug/1244090/comments/32


On 2015-03-04T18:19:36+00:00 Egor wrote:

Fedora 21 with all installed updates. Bug is still present in GNOME.

Reply at: https://bugs.launchpad.net/gnome-settings-
daemon/+bug/1244090/comments/45


On 2015-05-12T15:03:58+00:00 Michal wrote:

Still an issue in GNOME-3.14.

Reply at: https://bugs.launchpad.net/gnome-settings-
daemon/+bug/1244090/comments/48


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

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

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions

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

[Bug 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland crashes on AMD graphics

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  Totem with gstreamer1.0-vaapi and Wayland crashes on AMD graphics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions

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

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

2017-10-26 Thread Andrés Alcarraz

doug are you sure you didn't allow it in online accounts settings?
That's the account and authorization used by calendar, I have 2 factor 
authentication and when I set it up in online accounts it asked me for the 
second face auth.
There's no way an app can access your calendar or other info if you have two 
factor authentication in google.

Else it would be a google bug.

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

Title:
  gnome-calendar keeps asking for my google password

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

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

[Bug 1727899] Re: gvfsd-mtp crashed with SIGSEGV

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

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 #1706097, 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/1727899/+attachment/4997312/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 486296] Re: Evolution Mail is showing unsubscribed folders for an account.

2017-10-26 Thread Patrick Dunford

Unsubscribe from folder
Folder disappears
Close evolution
Open evolution
Folder re-appears

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

Title:
  Evolution Mail is showing unsubscribed folders for an account.

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

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

[Bug 486296] Re: Evolution Mail is showing unsubscribed folders for an account.

2017-10-26 Thread Patrick Dunford

This is ridiculous, it is very easy to verify. I can confirm this is an
issue in the latest version of Evolution, 3.22.6

** Changed in: evolution (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  Evolution Mail is showing unsubscribed folders for an account.

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

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

[Bug 1727897] [NEW] 'Use system theme' option in Dash to Dock breaks Ubuntu Dock theme on revert

2017-10-26 Thread Ads20000

Public bug reported:

To reproduce

Enable Dash to Dock.
Go into its settings.
Set 'use system theme'.
Disable Dash to Dock (to revert to Ubuntu Dock).
It will be a completely solid darker colour and won't go transparent when you 
move windows away from it.

Expected behavior
-
After enabling 'use system theme' and reverting to Ubuntu Dock, the Ubuntu Dock 
uses its usual theme.

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  'Use system theme' option in Dash to Dock breaks Ubuntu Dock theme on
  revert

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

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

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

Note that if the workarounds at the top of this bug don't work for you
then you're subscribed to the wrong bug. In that case, please open a new
one.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

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

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

[Bug 1727894] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

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

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 #1631434, 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/1727894/+attachment/4997285/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1631434
   gnome-control-center crashed with SIGSEGV in _cogl_check_extension()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

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

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

[Bug 1723874] Re: First installation of a snap reports an error "Connection reset by peer"

2017-10-26 Thread Robert Ancell

This appears not to be an issue in Zesty/Xenial since that didn't use
snapd-glib and makes a new connection for each request.

** No longer affects: gnome-software (Ubuntu)

** No longer affects: gnome-software (Ubuntu Xenial)

** No longer affects: gnome-software (Ubuntu Zesty)

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

Title:
  First installation of a snap reports an error "Connection reset by
  peer"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1723874/+subscriptions

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

[Bug 1721762] Re: Cancelled installation of snap continues

2017-10-26 Thread Robert Ancell

** Changed in: snapd-glib (Ubuntu Artful)
   Status: New => Fix Committed

** No longer affects: gnome-software (Ubuntu Bionic)

** Also affects: gnome-software (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: snapd-glib (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: snapd-glib (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: snapd-glib (Ubuntu Zesty)

** No longer affects: snapd-glib (Ubuntu Xenial)

** No longer affects: gnome-software (Ubuntu Artful)

** Changed in: gnome-software (Ubuntu Zesty)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Fix Committed

** No longer affects: gnome-software (Ubuntu)

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: gnome-software (Ubuntu Zesty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Cancelled installation of snap continues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1721762/+subscriptions

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

[Bug 29787] Re: Backspace key in GNU Screen not detected correctly

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

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


On 2009-03-13T03:40:27+00:00 Ray wrote:

Description of problem:
When using 'screen' from within an XFCE terminal, hitting backspace does 
nothing.  From a vi session it seems that a '^@' or NUL is being sent instead 
of ^H or ^?.  Workaround is to configure the XFCE Terminal to explicitly sent 
^H or ^?, but Auto Detect should really do the "right thing" within screen.

Version-Release number of selected component (if applicable):
vte-0.17.4-1.fc10.i386

How reproducible:
So far, always.

Steps to Reproduce:
1. Start XFCE
2. Open an XFCE Terminal
3. Start screen (enter 'screen')
4. Type some text then try backspacing.
  
Actual results:
No backspace occurs.

Expected results:
Backspacing!

Additional info:
I'm not sure if this is VTE's fault (bugs from other distro's led me to believe 
it was), XFCE Terminal's or screen's

My TERM is set to xterm in XFCE Terminal before starting up screen.  I
have tried with vt100, tried starting screen with TERM=screen screen,
and various .vimrc and .Xresources tricks to no avail.

I notice that if I ssh from the machine to somewhere else and start
screen on the remote server, backspace works fine.  Odd?

I have been able to reproduce this on multiple Fedora 10 installs with
virgin configs.  I tried older versions of screen (back to the one
included in RHEL5).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vte/+bug/29787/comments/37


On 2009-11-18T11:20:35+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/vte/+bug/29787/comments/42


On 2009-12-18T09:00:53+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/vte/+bug/29787/comments/43


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

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

Title:
  Backspace key in GNU Screen not detected correctly

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

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

[Bug 31709] Re: Brasero, GNOME's burn:/// and K3b slow dvd burn speed

** Changed in: brasero (Ubuntu)
   Importance: Unknown => Medium

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

Title:
  Brasero, GNOME's burn:/// and K3b slow dvd burn speed

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

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

[Bug 198951] Re: gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855, fglrx, radeonhd

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

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-03-09T17:46:17+00:00 Charles wrote:

Description of problem:

Booting the new kernel with "i915.modeset=1" causes gnome-settings-daemon to
crash after logging in.

>From kernel changelog:

* Thu Mar 06 2008 Dave Airlie 
- Add initial i915 drm modesetting tree - needs i915.modeset=1 on command
  line + new libdrm + new intel driver to actually be useful

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

gnome-settings-daemon-2.21.92-2.fc9.x86_64
kernel-2.6.25-0.101.rc4.git3.fc9.x86_64
libdrm-2.4.0-0.9.fc9.i386
libdrm-2.4.0-0.9.fc9.x86_64
xorg-x11-drv-evdev-1.99.1-0.1.fc9.x86_64
xorg-x11-drv-i810-2.2.1-9.fc9.x86_64
xorg-x11-server-Xorg-1.4.99.901-1.20080307.fc9.x86_64

How reproducible:

always

Steps to Reproduce:
1. boot above kernel version with i915.modeset=1 command line
2. log into GNOME, note dialog about gnome-settings-daemon failing to start
3. try running "/usr/libexec/gnome-settings-daemon" manually
  
Actual results:

> /usr/libexec/gnome-settings-daemon 
** (gnome-settings-daemon:3497): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:3497): DEBUG: Starting settings manager
** (gnome-settings-daemon:3497): DEBUG: Loading settings plugins from dir:
/usr/lib64/gnome-settings-daemon-2.0/
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/sound.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/sound for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/clipboard for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/media-keys for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/xrandr for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/xrdb for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/font.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/font for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/typing-break for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/xsettings for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/keybindings for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/dummy for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/mouse for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/keyboard for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/screensaver for changes
** (gnome-settings-daemon:3497): DEBUG: Loading plugin:
/usr/lib64/gnome-settings-daemon-2.0/background.gnome-settings-plugin
** (gnome-settings-daemon:3497): DEBUG: Monitoring dir
/apps/gnome_settings_daemon/plugins/background for changes
** (gnome-settings-daemon:3497): DEBUG: Loa

[Bug 325973] Re: gnome-session keeps respawning nautilus when no desktop is drawed

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

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

On 2009-02-13T05:12:32+00:00 Allen wrote:

Description of problem:
Turning off the desktop by setting GConf 
/apps/nautilus/preferences/show_desktop to false causes gnome-session to 
continually attempt to launch nautilus over and over.

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

How reproducible:
Always

Steps to Reproduce:
1. set apps/nautilus/preferences/show_desktop to false

Actual results:
Desktop disappears.  gnome-session launches nautilus over and over, filling 
Window List taskbar applet with "Starting File Manager ..." buttons.  Nautilus 
never successfully launches, however.  Each Nautilus process exits as soon as 
it starts.

Expected results:
Desktop disappears.

Additional info:
Removing filemanager from GConf /desktop/gnome/session/required_components_list 
*really* makes the desktop go away.  Ideally gnome-session should be able to 
figure out that it shouldn't start Nautilus if it's not needed in the first 
place.

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

On 2009-02-18T08:15:00+00:00 Matthias wrote:

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

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

On 2009-03-12T04:04:09+00:00 Matthias wrote:

I can't reproduce this problem in current rawhide (admittely because the
autorestart for nautilus appears to be broken...)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/325973/comments/25

On 2009-03-12T04:56:50+00:00 Mamoru wrote:

Umm.. still reproducible for me with

nautilus-2.25.93-1.fc11.i586
gnome-session-2.25.92-2.fc11.i586
metacity-2.25.144-6.fc11.i586

As suggested in bug 485883 when I comment out the line X-GNOME-AutoRestart
in /usr/share/applications/gnome-nautilus.desktop this issue
disappears for me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/325973/comments/26

On 2009-03-12T13:11:18+00:00 Matthias wrote:

Hmm, too bad I can't reproduce this anymore.

Does adding

AutostartCondition=GNOME /apps/nautilus/preferences/show_desktop

fix things for you ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/325973/comments/27

On 2009-03-12T13:45:58+00:00 Mamoru wrote:

(In reply to comment #4)
> Does adding  
> AutostartCondition=GNOME /apps/nautilus/preferences/show_desktop
> fix things for you ?  

Yes. With adding this line in gnome-nautilus.desktop I don't
see this issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/325973/comments/28

On 2009-03-12T15:03:12+00:00 Matthias wrote:

Ok, I've added that in 2.25.93-2.fc11

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

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

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

Title:
  gnome-session keeps respawning nautilus when no desktop is drawed

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

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

[Bug 378361] Re: Loss of lines when resizing and creating tab

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

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-14T12:34:34+00:00 Mads wrote:

Description of problem:
When tab headers are shown in maximized window then the 2nd and 3rd lines from 
the bottom are hidden.

Version-Release number of selected component (if applicable):
gnome-terminal-2.24.0-2.fc10.i386

Steps to Reproduce:
1. start gnome-terminal and maximize
2. run for example "seq 100" and write your name without hitting enter and 
memorize the topmost and last lines
3. start new tab with shift-ctrl-tab
4. back to tab 1 with alt-1
  
Actual results:
5. notice how the top and bottom lines have been preserved even though the 
available area has shrinked - but in the example the lines 99 and 100 have 
disappeared

Expected results:
The window should threat the introduction of tabs as a resize and scroll the 
topmost lines out of view.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/378361/comments/0


On 2008-11-26T03:51:30+00:00 Bug wrote:


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

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/378361/comments/1


On 2009-02-19T12:24:12+00:00 Mads wrote:

Same problem with gnome-terminal-2.25.91-1.fc11.i586 in rawhide

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/378361/comments/2


On 2009-03-20T22:43:45+00:00 Josh wrote:

I discovered that this actually happens with ANY event that reduces the
number of lines, which makes this a bit nastier.  It doesn't have to be
maximized:

1. Start a gnome-terminal with two tabs.
2. Run "seq 100" in both tabs.
3. Resize the window so that it's a few lines shorter.

The active tab will scroll lines off the top, so nothing is lost.  The
other tab will permanently lose a few lines from the bottom, as in the
initial report.

Also note that the loss doesn't occur until you actually switch to the
background tab.  If you resize the window shorter, return it to the
original size, and then look at the background tab, then nothing will be
lost.

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


On 2009-03-26T04:44:54+00:00 Behdad wrote:

Humm.  Can't reproduce.

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


On 2009-03-26T09:47:55+00:00 Mads wrote:

I still can with gnome-terminal-2.25.91-2.fc11.i586:
shift-ctrl-n
alt-f10
seq 100
shift-ctrl-t
alt-1
- and notice that 98 now is the last number

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


On 2009-04-15T03:30:08+00:00 Josh wrote:

Created attachment 339613
[vte] ensure that scroll_delta is always adjusted

When gnome-terminal's height is reduced, the active tab's terminal gets
a vte_terminal_size_allocate() call, which queues an adjustment to the
scroll_delta based on visible_rows to ensure that the scrollback moves
correctly.

However, when you then switch to a different tab, that terminal gets a
vte_terminal_set_size() first, which will update terminal->row_count
with the new height.  Only after it's visible does it get
vte_terminal_size_allocate(), and there the computation of visible_rows
thinks that there's no reduction (since terminal->row_count already
matches the new height), so it doesn't compute the new scroll_delta.

This patch moves the scroll_delta computation into set_size so it is
always kept current.

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


On 2009-04-15T22:14:37+00:00 Mads wrote:

I am running with the patch and can confirm that it works.

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


On 2009-06-09T09:47:05+00:00 Bug wrote:


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

More in

[Bug 531880] Re: gvfsd-burn leaves /tmp/virtual-USER.XXXXX clutter

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

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-17T01:02:20+00:00 Tom wrote:

Description of problem:
I've noticed a growing number of '/tmp/virtual-USER.X' directories.

'strings /usr/libexec/gvfsd-burn | grep virtual-' seems to point the
finger at gvfsd-burn.  [I have 17 of then on a 4 day old freshly
installed system.]

If this is the case, shouldn't gvfsd-burn clean this up on exit?

Version-Release number of selected component (if applicable):
gvfs-obexftp-1.2.2-3.fc11.x86_64
gvfs-fuse-1.2.2-3.fc11.x86_64
gvfs-smb-1.2.2-3.fc11.x86_64
gvfs-gphoto2-1.2.2-3.fc11.x86_64
gvfs-1.2.2-3.fc11.x86_64
gvfs-archive-1.2.2-3.fc11.x86_64


How reproducible:
A new directory every login, it appears.

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


Expected results:


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/0


On 2009-04-17T17:45:45+00:00 Tom wrote:

Or should /etc/rc.d/rc.sysinit clean them out on boot?

--- /etc/rc.d/rc.sysinit2009-04-07 08:58:41.0 -0700
+++ ./rc.sysinit2009-04-17 10:44:05.057453505 -0700
@@ -772,7 +772,7 @@
 rm -f /tmp/.X*-lock /tmp/.lock.* /tmp/.gdm_socket /tmp/.s.PGSQL.*
 rm -rf /tmp/.X*-unix /tmp/.ICE-unix /tmp/.font-unix /tmp/hsperfdata_* \
/tmp/kde-* /tmp/ksocket-* /tmp/mc-* /tmp/mcop-* /tmp/orbit-*  \
-   /tmp/scrollkeeper-*  /tmp/ssh-* \
+   /tmp/scrollkeeper-*  /tmp/ssh-*  /tmp/virtual-* \
/dev/.in_sysinit
 
 # Make ICE directory

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/1


On 2009-04-17T22:26:08+00:00 Matthias wrote:

It probably should, but thats no reason for gvfs not to clean up after
itself.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/2


On 2009-04-20T10:25:23+00:00 Alexander wrote:

Yes, we should try to clean up on exit, but there are various cases
where exit is unclean so I agree that rc.sysinit should clean them out
on boot too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/3


On 2009-04-21T05:42:24+00:00 Matthias wrote:

seahorse-agent (in the seahorse-plugins package) has some code to deal
with cleaning up on SIGTERM or SIGINT.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/4


On 2009-04-21T14:49:49+00:00 Matthias wrote:

Actually, what is probably needed here is either an xioerrorhandler or a
handling the dbus disconnected signal.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/5


On 2009-06-09T13:58:23+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/gvfs/+bug/531880/comments/6


On 2009-07-24T18:42:14+00:00 Tom wrote:

I'm changing this to Rawhide, since I'm still seeing this:

[root@tlondon ~]# ls -d /tmp/virtual* | wc
 95  952280
[root@tlondon ~]# 

And these are all from 2 July -> 24 July.

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


On 2009-07-24T18:46:09+00:00 Tom wrote:

Forgot to add versions:

gvfs-1.3.2-1.fc12.x86_64
gvfs-gphoto2-1.3.2-1.fc12.x86_64
gvfs-debuginfo-1.3.2-1.fc12.x86_64
gvfs-archive-1.3.2-1.fc12.x86_64
gvfs-fuse-1.3.2-1.fc12.x86_64
gvfs-obexftp-1.3.2-1.fc12.x86_64
gvfs-smb-1.3.2-1.fc12.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/8


On 2009-07-24T18:51:09+00:00 Tom wrote:

Would it make sense to create this kind of file/directory in a tmpfs?
Perhaps something like "/ephemeral" or some such?

Cleanup issues would go away..

[I suppose mounting /tmp as a tmpfs would do the same.]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/531880/comments/9

[Bug 505029] Re: Keyboard repeat rate is often reset

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

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-09T14:21:02+00:00 Richard wrote:

Description of problem:
After reconnecting a USB keyboard, the default auto-repeat delay and rate is 
used. The user's auto-repeat parameters are not restored.

When using a USB capable KVM switch, this means that the user's auto-
repeat parameters are gone when switching back to the machine.

Version-Release number of selected component (if applicable):
xorg-x11-drv-evdev-2.2.1-3.fc11.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Change your auto-repeat settings. For example, increase the auto-repeat rate 
to something you would notice.
2. Disconnect your USB keyboard, then reconnect it. Alternatively, use a KVM 
switch to switch to another machine, then switch back.
3. Test the auto-repeat settings by pressing a key.

Actual results:
The keyboard is reset to the default auto-repeat parameters.

Expected results:
The user's auto-repeat parameters are actually set.

Additional info:
On F10, the user's auto-repeat parameters were restored, so this seems to be a 
regression in Rawhide.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/505029/comments/0


On 2009-05-12T21:52:46+00:00 Matěj wrote:

Thanks for the bug report.  We have reviewed the information you have
provided above, and there is some additional information we require that
will be helpful in our diagnosis of this issue.

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

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

Thanks in advance.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/505029/comments/1


On 2009-05-13T18:12:19+00:00 Richard wrote:

Created attachment 343837
Xorg.0.log

Xorg.0.log before disconnecting the keyboard.

There is no xorg.conf file.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/505029/comments/2


On 2009-05-13T18:14:20+00:00 Richard wrote:

(Note: this is the very same log file as in Bug 499961.)

After disconnecting the keyboard, these lines were appended to the
logfile:

(II) config/hal: removing device Microsoft Microsoft? Digital Media Keyboard 
3000
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Close
(II) UnloadModule: "evdev"
(II) config/hal: removing device Microsoft Microsoft? Digital Media Keyboard 
3000
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Close
(II) UnloadModule: "evdev"

After reconnecting the keyboard, these lines were appended to the
logfile:

(II) config/hal: Adding input device Microsoft Microsoft? Digital Media 
Keyboard 3000
(**) Microsoft Microsoft? Digital Media Keyboard 3000: always reports core 
events
(**) Microsoft Microsoft? Digital Media Keyboard 3000: Device: 
"/dev/input/event8"
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Found 1 mouse buttons
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Found scroll wheel(s)
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Found x and y absolute 
axes
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Found keys
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Configuring as mouse
(II) Microsoft Microsoft? Digital Media Keyboard 3000: Configuring as keyboard
(**) Microsoft Microsoft? Digital Media Keyboard 3000: YAxisMapping: buttons 4 
and 5
(**) Microsoft Microsoft? Digital Media Keyboard 3000: EmulateWheelButton: 4, 
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft? Digital Media 
Keyboard 3000" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(**) Option "xkb_options" "terminate:ctrl_alt_bksp"
(**) Microsoft Microsoft? Digital Media Keyboard 3000: (accel) keeping 
acceleration scheme 1
(**) Microsoft Microsoft? Digital Media Keyboard 3000: (accel) filter chain 
progression: 2.00
(**) Microsoft Microsoft? Digital Media Keyboard 3000: (accel) filter stage 0: 
20.00 ms
(**) Microsoft Microsoft? Digital Media Keyboard 3000: (accel) set acceleration 
profile 0
(II) config/hal: Adding input device Microsoft Microsoft? Digital Media 
Keyboard 3000
(**) Microsoft Microsoft? Digital Media Keyboard 3000:

[Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

2017-10-26 Thread tom

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

@Tristram Very interesting theory!

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

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

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

[Bug 1721315] Re: On-screen keyboard shows up on first touch even when touch does not activate a text-field

2017-10-26 Thread tom

Thanks Tristram. I wrote the same thing, but the powers that be still
haven't even responded. This bug is paper-thin compared to 1723857.

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

Title:
  On-screen keyboard shows up on first touch even when touch does not
  activate a text-field

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

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

[Bug 187217] Re: [hardy] weird Home icon in clock locations panel

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

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-12-29T19:26:32+00:00 Tom wrote:

Description of problem:
I have 6 locations configured in intlclock, including 2 in my 'home timezone':
Mountain View and Los Angeles, CA.

The summary on the gnome panel indicates the weather in the second location (Los
Angeles), but when I place the cursor over the weather glyphs, it changes to the
first (Mountain View).

There seems no way to get it to 'know' that I am really in Mountain View and
would like that weather highlighted in the panel.

Version-Release number of selected component (if applicable):
gnome-panel-2.20.2-2.fc9

How reproducible:
Yup

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


Expected results:


Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/187217/comments/0


On 2008-02-14T15:10:30+00:00 Tom wrote:

Has this applet been dropped?

close?

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


On 2008-02-15T14:05:21+00:00 Ray wrote:

The applet hasn't been dropped.  It got upstreamed into the regular gnome-panel.
 Are you still seeing the bug?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/187217/comments/8


On 2008-02-15T17:39:54+00:00 Tom wrote:

Created attachment 295023
calendar and weather no temperature

The bug occurred when the applet displayed weather/temperature when the cursor
was placed over the icon in the "system tray".

This version of the applet doesn't seem to do that. so I don't see it.

Should the applet display weather only when you "expand" the calendar and
locations?

Also, I don't get temperature listed unless I have cursor over "weather icon"
for the location

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/187217/comments/9


On 2008-02-26T01:46:21+00:00 Tom wrote:

Latest version now shows temperature, but the old problem has returned:

If you enter 2 locations in the "local timezone", the temperature shown in the
"system tray" seems to be the "other" location.

Specifically, I'm in PST.  I add a location for Mountain View, CA, and for Los
Angeles, CA.  Both appear in the "detail pull down" with the nice "home" icon.

However, I did not find a way to tell the applet that my real "home" is
"Mountain View", not "Los Angeles". 

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/187217/comments/10


On 2008-03-05T04:43:48+00:00 Matthias wrote:

I've fixed the 'multiple locations in the same timezone' problem
recently.

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


** Changed in: gnome-panel (Fedora)
   Importance: Unknown => Low

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

Title:
  [hardy] weird Home icon in clock locations panel

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

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

[Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts

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

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


On 2005-03-30T14:15:37+00:00 Leonid wrote:

Description of problem:

If Russian xkb layout is active, it's impossible to use keyboard shortcuts like
ctrl-c (copy), ctrl-v (paste) etc. It makes this build of openoffice absolutely
unusable for somebody who was using other office (microsoft) or other build of
openoffice.org for a long time.

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

1.9.87-2

How reproducible:

always

Steps to Reproduce:
1. Start gnome keyboard properties and select Russian layout
2. Start openoffice writer and verify that keyboard produces kyrillic 
characters.
3. Try to use ctrl-c and ctrl-v for copy and paste text
  
Actual results:

Nothing will happen

Expected results:

Ctrl-c and ctrl-v should work for copy and paste

Additional info:

This bug was not reproduced with openoffice.org build from
http://www.openoffice.org.

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/0


On 2005-04-08T14:37:35+00:00 Caolan wrote:

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

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/1


On 2005-05-04T17:14:27+00:00 Leonid wrote:

Looks like it's not openoffice.org bug, because it works great in KDE. It's
gnome bug, and it's hanging on gnome bugzilla for a long time, see
http://bugzilla.gnome.org/show_bug.cgi?id=103331

no idea what component shoud be chosen :(

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/2


On 2013-12-24T09:22:13+00:00 Nrbrtx wrote:

This bug exists in Ubuntu too
https://bugs.launchpad.net/unity/+bug/1226962 (200 users affected).

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/147


On 2013-12-24T09:27:17+00:00 Nrbrtx wrote:

GNOMErs think that corresponding bug is
https://bugzilla.gnome.org/show_bug.cgi?id=678001 .

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/148


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

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

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

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

Title:
  Keyboard shortcuts (hotkeys) not functional in some cases in non-latin
  keyboard layouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

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

2017-10-26 Thread Doug Reese

I just upgraded from 17.04 to 17.10 today and am experiencing the issue
as described.  One thing not previously mentioned by others: I have two
factor auth enabled on my account. I was never asked for the 2nd auth,
yet I still see my calendar data being updated.

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

Title:
  gnome-calendar keeps asking for my google password

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

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

[Bug 337926] Re: vino: mouse cursor stays in upper left corner

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

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


On 2009-03-18T19:10:19+00:00 Fabrice wrote:

With current rawhide, I experience the same problem than the one
described here:

https://bugs.launchpad.net/ubuntu/+source/libxtst/+bug/337926

It can be very simply reproduced with the xevent program as described in
the ubuntu bug report. I filled this bug for the xorg intel driver
component, instead of libXtst, because it seems to me specific to the
intel driver. I could not reproduce it on another rawhide box, with the
radeon driver.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/337926/comments/10


On 2009-03-20T10:32:13+00:00 Fabrice wrote:

reassigning to xorg-x11-server, as it seems its a bug in the XTEST
extension. I think that GetPointerEvents() in ProcXTestFakeInput()
should be called with POINTER_SCREEN flag set.

The problem is visible on the eeepc (like described in the ubuntu bug),
because of the synaptics driver, that changes
pDev->valuator->axes->min_value and max_value. On my other rawhide box,
these values are -1, and the bug is somewhat hidden is that case.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/337926/comments/11


On 2009-03-25T06:51:43+00:00 Peter wrote:

Fixed with xorg-x11-server-1.6.0-15. Thanks for reporting.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/337926/comments/12


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

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

Title:
  vino: mouse cursor stays in upper left corner

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

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

[Bug 385067] Re: gnome-panel consumes excessive memory

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

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


On 2009-02-21T23:09:53+00:00 Nadim wrote:

Description of problem:
gnome-panel appears to have a memory leak that may consume up to 4GB of memory 
within 24 hours if the program is left running. By default, gnome-panel runs, 
and is necessary, on Fedora 10 installations.


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

How reproducible:
Here are my gnome-panel settings:
I have gnome-panel running on a dual-monitor setup, only on the main monitor. 
I'm using kmod-nvidia, and compiz. I have verified that the memory leak is 
indeed coming from gnome-panel using top. gnome-panel is using a transparency 
effect and runs the following widgets:
NetworkManager icon, sound icon, date and time, fast user switching, desktop 
icon, virtual desktop, and taskbar.

Steps to Reproduce:
1. Run gnome-terminal
2. Configure it as above
  
Actual results:
Everything runs perfectly but with a huge memory leak that leads eventually to 
Fedora being unable to fork new processes.

Expected results:
gnome-panel without any memory leaking.

Additional info:
N/A

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/385067/comments/0


On 2009-06-23T19:32:26+00:00 Alex wrote:

I believe this is still present in Fedora 11, gnome-panel-2.26.2-1.fc11.

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


On 2009-07-09T17:48:32+00:00 Christian wrote:

I can confirm that it is still present in Fedora 11, gnome-
panel-2.26.2-1.fc11.x86_64 and gnome-panel-2.26.3-1.fc11.x86_64(from
updates-testing). I am using wallpapoz to change the background
periodically, and every time the wallpaper changes, memory usage of
gnome-panel goes up. Disabling compiz does not help.

Walkaround: disable transparency in gnome-panel and restart gnome-panel.
Memory usage of gnome-panel then stays around 10 MB, even with compiz
and wallpapoz enabled. Transparency of gnome-panel can also be enabled
within compiz with the opacity settings for "Dock"-type windows. While
this affects the transparency of all the icons as well, it does not lead
to the memory leak.

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


On 2009-07-09T21:09:00+00:00 Alex wrote:

I'm using the default FC11 config; no compiz, no transparency, no
wallpaper changing.

I have a total of three gnome-panels, one for the Window List and Show
Desktop on top of one for the menus, several launchers, Music Applet,
seahorse-applet, Pulse Audio Volume Control, gweather, update applet,
tracker, sound preferences, Bluetooth applet, Tomboy, User switch applet
and Clock. Along the right vertical edge, I have another panel with
sensors-applet and system monitor.

gnome-panel can use upto 4GB whilst I leave the desktop idle and blanked
for ~10 hours. Killing it brings everything back to normal.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/385067/comments/8


On 2009-07-29T17:34:00+00:00 Alex wrote:

Doesn't seem as bad since recent gnome-panel-2.26.3-1.fc11 update,
though I see nothing in its changelog to indicate bugfix. Perhaps a fix
in some other recently-updated GNOME library?

Memory usage still suspiciously high and rising, though, just not into
the GB range. :-]

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/385067/comments/9


On 2009-08-04T22:10:35+00:00 Alex wrote:

I saw it again this morning. Most days I run a check on my md RAID
arrays (e.g. 'echo check >/sys/block/md0/md/sync_action'), but I've not
been doing that for the last week or so.

Is there any possibility that gnome-panel, or some library it uses,
doesn't respond well to IO operations taking rather longer than normal?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
panel/+bug/385067/comments/10


On 2009-08-19T10:02:54+00:00 Alex wrote:

OK, for me, gnome-panel's memory leak appears to definitely be caused by
an md sync_action check happening in the background. To reproduce:

1. /home in a LVM LV in VG in a PV on a md RAID1 array (e.g. /dev/md3)
2. Log into a GNOME session that includes gnome-panel
3. As root, echo check >/sys/block/md3/m

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

2017-10-26 Thread Dimitri John Ledkov

** Changed in: systemd (Ubuntu Zesty)
   Status: Fix Released => Confirmed

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Released => Confirmed

** Changed in: systemd (Ubuntu Zesty)
   Importance: Undecided => Critical

** Changed in: systemd (Ubuntu Artful)
   Status: Fix Released => Confirmed

** Changed in: systemd (Ubuntu Artful)
   Importance: Undecided => Critical

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

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

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

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

[Bug 1721315] Re: On-screen keyboard shows up on first touch even when touch does not activate a text-field

2017-10-26 Thread Tristram Oaten

IMO this bug is a duplicate of
https://bugs.launchpad.net/ubuntu/+bug/1723857, as there's far more
activity on it.

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

Title:
  On-screen keyboard shows up on first touch even when touch does not
  activate a text-field

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

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

[Bug 291840] Re: gphoto2 backend unable to mount MTP audio player

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

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-28T16:09:43+00:00 Martin wrote:

Description of problem:
with fedora 9 nautilus automatically mounts your mtp devices when you plug them 
in to your computer.

this does not work with fedora rawhide anymore.

Version-Release number of selected component (if applicable):
gvfs-1.0.2-2.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1. Plug in your MTP music player
2.
3.
  
Actual results:
Nothing happens

Expected results:
Should be mounted

Additional info:
-/-

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/291840/comments/0


On 2008-10-29T10:37:41+00:00 Bastien wrote:

gvfs doesn't mount the MTP music players any more, as accessing the
device conflicts with Rhythmbox/Banshee's direct device access.

We'll be working on making the gphoto/MTP backend of gvfs ready for use
in music players in the future, so that MTP players are available on the
desktop again.

See also the upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=520121

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/291840/comments/1


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

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

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

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

Title:
  gphoto2 backend unable to mount MTP audio player

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

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

[Bug 306310] Re: Resume (from memory) goes back to sleep automatically

** Changed in: linux
   Status: In Progress => Fix Released

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

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

Title:
  Resume (from memory) goes back to sleep automatically

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

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

[Bug 331428] Re: crash when right clicking on a calendar entry

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

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-20T19:27:05+00:00 David wrote:

Created attachment 327551
gecko-bugreport.txt generated with crash described

Description of problem:

Thunderbird crashes with attached gecko bugreport while using lightning
extension. It is reproducable with certain existing events but also
happened when exporting the calendar to an ICS file.

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

[settle ~/] 4% rpm -q thunderbird thunderbird-lightning
thunderbird-2.0.0.18-1.fc10.i386
thunderbird-lightning-0.9-3.fc10.i386

How reproducible:

Open a specific event in my calendar to edit. not all events, just some.  Also 
happened this morning when exporting one calendar to an ICS file.

Steps to Reproduce:
1. open thunderbird and switch to calendar mode
2. select file->export calendar, select calendar, press Ok.
3. choose file name and location, select iCalendar format, press "save"
4. crash 

Actual results:

crash with attached gecko-bugreport.txt file.

Expected results:

save the file in iCalendar format and return to program.

Additional info:

exporting to an HTML file doesn't cause the same crash.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/0

On 2008-12-20T19:30:59+00:00 David wrote:

Created attachment 327552
gecko-bugreport.txt generated with crash after editing an event

This gecko-bugreport.txt file was generated after editing an event and
closing the window with the window manager close button.  not all events
cause the crash but there isn't anything special about the event that
does cause the crash.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/1

On 2008-12-28T11:02:40+00:00 Lubomir wrote:

It's probably either ICAL with unsupported features or broken; but
libical definitely shouldn't abort here anyways. I'm building a
replacement package with aborts on such conditions disabled.

Until it builds -- could you please install debugging symbols ("yum
install yum-utils; debuginfo-install libical sunbird") and reproduce the
problem again? We'd get a backtrace that would let us know more to find
out what's wrong with your calendar.

Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/2

On 2008-12-28T11:47:56+00:00 Lubomir wrote:

This is the package where the fatal aborts should be disabled, so you
will probably see an error message in thunderbird, but no crash:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/3

On 2008-12-28T20:57:59+00:00 David wrote:

(In reply to comment #2)
> It's probably either ICAL with unsupported features or broken; but libical
> definitely shouldn't abort here anyways. I'm building a replacement package
> with aborts on such conditions disabled.
> 
> Until it builds -- could you please install debugging symbols ("yum install
> yum-utils; debuginfo-install libical sunbird") and reproduce the problem 
> again?
> We'd get a backtrace that would let us know more to find out what's wrong with
> your calendar.
> 
> Thanks!

since i haven't installed any debug packages yet this will be a ~176MB
download to get installed.  if this will still be useful i can do it
when i have better connectivity tomorrow.  please let me know.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/4

On 2008-12-29T22:54:31+00:00 David wrote:

Created attachment 327937
gecko-bugreport.txt from crash after installing debuginfo rpms

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/331428/comments/5

On 2008-12-29T22:58:27+00:00 David wrote:

(In reply to comment #4)
> (In reply to comment #2)
> > It's probably either ICAL with unsupported features or broken; but libical
> > definitely shouldn't abort here anyways. I'm building a replacement package
> > with aborts on such conditions disabled.
> > 
> > Until it builds -- could you please install debugging symbols ("yum install
> > yum-utils; debuginfo-install libical sunbird") and reproduce the problem 
> > again?
> > We'd get a backtrace that would let us kno

[Bug 1506816] Re: Dropbox crash? "nautilus crashed with SIGSEGV in gtk_application_impl_window_added()"

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

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-16T18:08:00+00:00 dobs wrote:

Description of problem:
Dropbox show notifications...

Version-Release number of selected component:
nautilus-3.16.2-2.fc22

Additional info:
reporter:   libreport-2.6.0
backtrace_rating: 4
cmdline:nautilus --no-desktop --select '/home/dobs/Dropbox/Camera 
Uploads/2015-07-16 17.01.29.jpg'
crash_function: gtk_application_impl_window_added
executable: /usr/bin/nautilus
global_pid: 3474
kernel: 4.0.7-300.fc22.x86_64
runlevel:   N 5
type:   CCpp
uid:1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_application_impl_window_added at gtkapplicationimpl.c:90
 #1 gtk_application_window_added at gtkapplication.c:709
 #2 nautilus_application_window_added at nautilus-application.c:1167
 #3 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102
 #4 _g_closure_invoke_va at gclosure.c:831
 #7 gtk_application_add_window at gtkapplication.c:1036
 #8 gtk_window_set_application at gtkwindow.c:3405
 #9 nautilus_window_constructed at nautilus-window.c:1974
 #10 g_object_new_internal at gobject.c:1814
 #11 g_object_new_valist at gobject.c:2033

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


On 2015-07-16T18:08:03+00:00 dobs wrote:

Created attachment 1052807
File: backtrace

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


On 2015-07-16T18:08:04+00:00 dobs wrote:

Created attachment 1052808
File: cgroup

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


On 2015-07-16T18:08:06+00:00 dobs wrote:

Created attachment 1052809
File: core_backtrace

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


On 2015-07-16T18:08:07+00:00 dobs wrote:

Created attachment 1052810
File: dso_list

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


On 2015-07-16T18:08:08+00:00 dobs wrote:

Created attachment 1052811
File: environ

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


On 2015-07-16T18:08:10+00:00 dobs wrote:

Created attachment 1052812
File: limits

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


On 2015-07-16T18:08:11+00:00 dobs wrote:

Created attachment 1052813
File: maps

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


On 2015-07-16T18:08:12+00:00 dobs wrote:

Created attachment 1052814
File: mountinfo

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


On 2015-07-16T18:08:14+00:00 dobs wrote:

Created attachment 1052815
File: namespaces

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


On 2015-07-16T18:08:15+00:00 dobs wrote:

Created attachment 1052816
File: open_fds

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


On 2015-07-16T18:08:16+00:00 dobs wrote:

Created attachment 1052817
File: proc_pid_status

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


On 2015-07-16T18:08:17+00:00 dobs wrote:

Created attachment 1052818
File: var_log_messages

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


On 2016-07-19T15:23:18+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 fee

[Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

2017-10-26 Thread Tristram Oaten

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

I think I have a theory about this bug: It's caused by the 
swipe-up-from-bottom-screen-edge gesture that is configured to show caribou.
I think that the cursor is swept off the screen to the bottom when you change 
input devices (touch/pen/mouse), and when you re-enable them by pressing or 
tapping the screen, it counts as this gesture.

Is there a way to disable this swipe-up gesture to test?

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

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

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

[Bug 1716633] Re: /usr/bin/gnome-software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  /usr/bin/gnome-
  
software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular

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

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

[Bug 1725649] Re: Fullscreen games lose "fullscreen" after an Alt+Tab

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

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

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

Title:
  Fullscreen games lose "fullscreen" after an Alt+Tab

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

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

[Bug 1725649] Re: Fullscreen games lose "fullscreen" after an Alt+Tab

2017-10-26 Thread Jeremy Bicha

** Description changed:

  Impact
  ==
  Using Alt-Tab to leave a fullscreen game and then return breaks the game by 
offsetting the display by the size of the GNOME Shell top bar.
  
  Test Case
  =
  1. Run a game full screen.
  
  I installed Steam and used Team Fortress 2 because it's free (but a very
  large download)
  
  2. Press Alt-Tab to switch to another window and then press Alt-Tab to
  switch back to the game.
  
  The game should display and function normally.
  
  Regression Potential
  
  This is fixed by cherry-picking 3 patches from the gnome-3-26 mutter branch. 
We are eventually expecting a mutter 3.26.2 release but I don't think there is 
a planned release date yet.
  
  These patches also fix LP: #1725821 but I was having trouble coming up
  with a specific test case for that issue that I could reproduce with my
  Intel graphics card.
  
  The upstream bug mentions that this may re-introduce tearing with full-
  screen videos with Firefox because Firefox disables hardware graphics
  acceleration on Linux. Personally, I feel that is a Firefox bug and
- shouldn't block this fix.
+ shouldn't block this fix. (The workaround for that is to visit
+ about:config in Firefox and set layers.acceleration.force-enabled to
+ true and restart Firefox.)
  
  The issue of poor performance with full-screen games with GNOME 3.26 (a
  regression from GNOME 3.24) is a popular complaint in forums and should
  be fixed by these patches.
  
  The upstream branch
  
  https://git.gnome.org/browse/mutter/log?h=gnome-3-26
  
  Original Bug Report
  ===
  When playing a steam game in "fullscreen" (in this case stellaris) if I 
alt-tab out and then back the game is no longer full screen and a portion the 
size of the menu bar at the top is reserved, not showing the menu just a 
portion of the background colour. Also after this happens all mouse clicks are 
offset by that same margin.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  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: Sat Oct 21 12:16:27 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['ubuntu-bug']"
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'terminator.desktop', 'emacs25.desktop', 'quodlibet.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'thunderbird.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-13 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

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

Title:
  Fullscreen games lose "fullscreen" after an Alt+Tab

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

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

[Bug 1721762] Re: Cancelled installation of snap continues

This bug was fixed in the package snapd-glib - 1.24-0ubuntu1

---
snapd-glib (1.24-0ubuntu1) bionic; urgency=medium

  * New upstream release:
- Fix QSnapd::install() not working async.
- Move Qt enums to an enum class and rename to avoid collisions (API break).
- Fix multiple async operations not working at the same time. (LP: #1722183)
- When async requests are cancelled abort change in snapd. (LP: #1721762)
- Connect to snapd on demand. (LP: #1723874)
- Add ability to set snapd socket to connect to.
- Add support for channels.
- Fix runtime assertion when snapd socket is NULL.
- Fix sudoer flag not being correctly set for create-user.
- Make clients using provided sockets non-blocking.
- Don't install snapd-qt.pc if not compiling snapd-qt.
  * debian/libsnapd-glib1.symbols:
  * debian/libsnapd-qt1.symbols:
- Updated

 -- Robert Ancell   Thu, 26 Oct 2017
12:40:05 +1300

** Changed in: snapd-glib (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Cancelled installation of snap continues

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

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

[Bug 1722183] Re: When several snaps are being installed, cancelling an installation does not cancel the right one.

This bug was fixed in the package snapd-glib - 1.24-0ubuntu1

---
snapd-glib (1.24-0ubuntu1) bionic; urgency=medium

  * New upstream release:
- Fix QSnapd::install() not working async.
- Move Qt enums to an enum class and rename to avoid collisions (API break).
- Fix multiple async operations not working at the same time. (LP: #1722183)
- When async requests are cancelled abort change in snapd. (LP: #1721762)
- Connect to snapd on demand. (LP: #1723874)
- Add ability to set snapd socket to connect to.
- Add support for channels.
- Fix runtime assertion when snapd socket is NULL.
- Fix sudoer flag not being correctly set for create-user.
- Make clients using provided sockets non-blocking.
- Don't install snapd-qt.pc if not compiling snapd-qt.
  * debian/libsnapd-glib1.symbols:
  * debian/libsnapd-qt1.symbols:
- Updated

 -- Robert Ancell   Thu, 26 Oct 2017
12:40:05 +1300

** Changed in: snapd-glib (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  When several snaps are being installed, cancelling an installation
  does not cancel the right one.

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

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

[Bug 1723874] Re: First installation of a snap reports an error "Connection reset by peer"

This bug was fixed in the package snapd-glib - 1.24-0ubuntu1

---
snapd-glib (1.24-0ubuntu1) bionic; urgency=medium

  * New upstream release:
- Fix QSnapd::install() not working async.
- Move Qt enums to an enum class and rename to avoid collisions (API break).
- Fix multiple async operations not working at the same time. (LP: #1722183)
- When async requests are cancelled abort change in snapd. (LP: #1721762)
- Connect to snapd on demand. (LP: #1723874)
- Add ability to set snapd socket to connect to.
- Add support for channels.
- Fix runtime assertion when snapd socket is NULL.
- Fix sudoer flag not being correctly set for create-user.
- Make clients using provided sockets non-blocking.
- Don't install snapd-qt.pc if not compiling snapd-qt.
  * debian/libsnapd-glib1.symbols:
  * debian/libsnapd-qt1.symbols:
- Updated

 -- Robert Ancell   Thu, 26 Oct 2017
12:40:05 +1300

** Changed in: snapd-glib (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  First installation of a snap reports an error "Connection reset by
  peer"

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

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

[Bug 1716633] Re: /usr/bin/gnome-software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  /usr/bin/gnome-
  
software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular

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

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

[Bug 1716633] Re: /usr/bin/gnome-software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  /usr/bin/gnome-
  
software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular

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

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

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2017-10-26 Thread Sam Thomas

I am having the same issue with Ubuntu 17.10 running on XORG. This is a
VM inside vmware fusion pro 10. The mouse can move around but the clicks
dont work anywhere. I start a terminal session with ctrl + alt + t and
then alt + tab and then click on the terminal that i opened earlier for
the clicks to start working again.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

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

[Bug 249373] Re: gnome-session storing broken since intrepid

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

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-02T19:15:44+00:00 Jeremy wrote:

Description of problem:
The "Remember currently running application" button doesn't seem to work.  I 
would expect that it adds the currently running application*s* to the session 
to start up.

Version-Release number of selected component (if applicable):
gnome-session-2.24.0-5.fc10.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start gnome-session-properties
2. Go to "Options" tab
3. Press "Remember currently running application"
  
Actual results:
Nothing

Expected results:
Adds running applications to list of startup programs.

Additional info:

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


On 2008-10-03T04:21:31+00:00 Matthias wrote:

Upstream bug tracking this issue:
http://bugzilla.gnome.org/show_bug.cgi?id=552387

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


On 2008-11-12T15:32:07+00:00 Ray wrote:

Not going to get this fixed before F10 and it should be fixed upstream
before F11, so I'm going to close this bug UPSTREAM.b

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/47


On 2008-11-12T15:56:57+00:00 Peter wrote:

I thought that closed as UPSTREAM meant that it was already fixed
upstream?

How do we track this issue with this bz closed?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/48


On 2008-11-12T16:09:45+00:00 Ray wrote:

Hi Peter,

Not necessarily.  Since development primarily happens upstream, we like
to move the issues that we aren't tracking for a particular release
upstream to make sure everyone is on the same page (it doesn't always go
down that way because bug triage is time consuming, but that's the
general rule).

If you want to follow along, CC yourself on the upstream report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/49


On 2008-11-13T15:26:07+00:00 Ray wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/50


On 2008-12-01T12:26:23+00:00 Daniel wrote:

So Fedora won't try to resolve this problem for F10 at all?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/53


On 2008-12-01T13:29:13+00:00 Bernd wrote:

Could the original reporter of this bug please re-open it?

Honestly, how can a bug that prevents a major functionality in the
default desktop environment just be ignored with CLOSED UPSTREAM,
especially as session management was working just fine in older Fedora
releases.

So, this is a major regression and should be fixed ASAP.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/54


On 2008-12-01T14:30:22+00:00 Matthias wrote:

If you want this to be fixed earlier, feel free to chime in with a
patch.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/55


On 2008-12-01T15:36:49+00:00 Ray wrote:

It's not that this won't get fixed for F10.  It's that there's already
traction upstream for this, and there's not reason to duplicate effort.
We can always backport the patch and do an update when it's ready.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/56


On 2008-12-02T22:29:01+00:00 Ray wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/57


On 2009-01-14T21:15:27+00:00 Derek wrote:

So when will this be ready?   Honestly, guys, this is a MAJOR
regression!

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/249373/comments/62

---

[Bug 200009] Re: yelp crashed with SIGSEGV in rrn_info_find_from_uri()

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

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

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

Title:
  yelp crashed with SIGSEGV in rrn_info_find_from_uri()

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

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

[Bug 260918] Re: needed: libv4l and associated application patches (or "gspca stopped working in 2.6.27")