[Bug 41427] Re: "slow keys" can turn on surreptitiously & cause confusion.

[Bug Watch Updater]

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

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

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

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

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

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

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

[Bug Watch Updater]

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

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


On 2012-04-01T14:49:39+00:00 Jonathan wrote:

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

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

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

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

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


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

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

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


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

I added a patch to the upstream bug

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


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

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

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


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

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

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


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

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

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


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

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

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

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

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

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

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

[Bug Watch Updater]

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

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


On 2012-04-07T17:21:47+00:00 Anthony wrote:

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

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

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

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

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

[Bug Watch Updater]

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

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


On 2012-04-12T09:36:10+00:00 Mikhail wrote:

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

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


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

Created attachment 577019
htop

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


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

Created attachment 582274
htop

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


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

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

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


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

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

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


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

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

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


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

Created attachment 587342
backtrace for dconf-service process

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


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

Created attachment 587343
backtrace for dbus-daemon process

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


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

Created attachment 589027
backtrace for gnome-settings-daemon

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


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

Created attachment 589028
backtrace for dconf worker process

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


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

Created attachment 589033
backtrace for Compositor

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


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

Created attachment 589035
backtrace for dconf-service

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


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

when it occurs Num Lock indicator is often blink.

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


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

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

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


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

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

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


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

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

[Bug Watch Updater]

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

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


On 2012-02-25T15:36:55+00:00 Bastian wrote:

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

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

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

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

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

[Bug Watch Updater]

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

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

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

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

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

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

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

[Bug Watch Updater]

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

** Changed in: evolution (Fedora)
   Importance: Unknown => Undecided

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

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

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

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

[Bug 1726717] Re: Alignment of external screen limits placing of icons

[Bug Watch Updater]

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

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

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

Title:
  Alignment of external screen limits placing of icons

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

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

[Bug 904505] Re: Flash doesn't work in WebKitGTK3 browsers

[Bug Watch Updater]

** Changed in: epiphany-browser (Fedora)
   Status: Unknown => Invalid

** Changed in: epiphany-browser (Fedora)
   Importance: Unknown => High

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

Title:
  Flash doesn't work in WebKitGTK3 browsers

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

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

[Bug 846646] Re: GPL Ghostscript 9.04: Error: Font Renderer Plugin ( FreeType ) return code = -1

[Bug Watch Updater]

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

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


On 2012-01-27T13:06:06+00:00 Skippy wrote:

Description of problem:
When I run evince on ps files, I get many times the following error message in 
the terminal :
GPL Ghostscript 9.04: Error: Font Renderer Plugin ( FreeType ) return code = -1

Not sure if and how the display is affected.


Version-Release number of selected component (if applicable):
evince i686 3.2.1 2.fc16
ghostscript i686 9.04 7.fc16
ghostscript-fonts noarch 5.50 27.fc16


Additional info:
Ubuntu seems to be affected by a similar bug : 
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/7


On 2012-01-30T11:45:59+00:00 Skippy wrote:

(In reply to comment #0)
> Not sure if and how the display is affected.

Actually on the files I try to read, only the first page is displayed.  I can 
read them correctly if I process them through ps2pdf, although the following 
errors appears when viewing the PDF file with evince (not sure it is related, 
but in case it can help) :

Gtk-Message: Failed to load module "pk-gtk-module"
Entity: line 5: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xFF 0xFF 0xFF 0xFF
 0 && height > 0' failed

(evince:6529): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

I also only see the first page, and running gs directly on the
PostScript file works fine.

Changing component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/11


On 2013-01-16T15:54:22+00:00 Fedora wrote:

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

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/12


On 2013-02-13T19:04:45+00:00 Fedora wrote:

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

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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/846646/comments/13


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

** Changed in: evince (Fedora)
   Importance: Unknown => Undecided

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

Title:
  GPL Ghostscript 9.04: Error: Font Renderer Plugin ( FreeType ) return
  code = -1

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

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

[Bug 932177] Re: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11

[Bug Watch Updater]

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

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

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

Title:
  XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
  correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11

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

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

[Bug 985848] Re: nautilus crashed with SIGSEGV in icon_rename_ended_cb()

[Bug Watch Updater]

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

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


On 2011-12-13T13:56:45+00:00 kotofos wrote:

libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 3
cmdline:nautilus -n
comment:open new window, by clicking middle button on side panel, while 
no nautilus windows open and "nautilus handle desktop" is on
crash_function: icon_rename_ended_cb
executable: /usr/bin/nautilus
kernel: 3.1.4-1.fc16.x86_64
pid:1482
pwd:/home/kotofos
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
time:   Вт. 13 дек. 2011 19:10:54
uid:1000
username:   kotofos

backtrace:  Text file, 38487 bytes
dso_list:   Text file, 16442 bytes
maps:   Text file, 77207 bytes
smolt_data: Text file, 2991 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=1
:HOSTNAME=kotofos-laptop
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=1ae78454aedfe02bdcbc0f4b0011-1323669018.425340-735808942
:QTDIR=/usr/lib64/qt-3.3
:QTINC=/usr/lib64/qt-3.3/include
:IMSETTINGS_MODULE=none
:USER=kotofos
:USERNAME=kotofos
:MAIL=/var/spool/mail/kotofos
:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/kotofos/.local/bin:/home/kotofos/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/kotofos
:XMODIFIERS=@im=none
:LANG=en_GB.utf8
:GDM_LANG=en_GB.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/kotofos
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=kotofos
:QTLIB=/usr/lib64/qt-3.3/lib
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-lvSN8ivVxT,guid=bcaf33b2f0a44a31627725bf003e
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/kotofos
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-kotofos-1lg2UE/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1186,unix/unix:/tmp/.ICE-unix/1186
:GNOME_KEYRING_CONTROL=/tmp/keyring-Q31oJo
:SSH_AUTH_SOCK=/tmp/keyring-Q31oJo/ssh
:GPG_AGENT_INFO=/tmp/keyring-Q31oJo/gpg:0:1
:LC_TIME=ru_RU.utf8
:LC_NUMERIC=ru_RU.utf8
:LC_MONETARY=ru_RU.utf8
:LC_MEASUREMENT=ru_RU.utf8
:DESKTOP_AUTOSTART_ID=10c46320ee6320391813236690201374720011860028

var_log_messages:
:Dec 13 19:10:53 kotofos-laptop kernel: [109297.109042] nautilus[1482]: 
segfault at 30 ip 0043862e sp 7fffcc141730 error 4 in 
nautilus[40+159000]
:Dec 13 19:11:17 kotofos-laptop abrt[3397]: Saved core dump of pid 1482 
(/usr/bin/nautilus) to /var/spool/abrt/ccpp-2011-12-13-19:10:54-1482 (132722688 
bytes)

xsession_errors:
:Initializing nautilus-dropbox 0.7.1
:Initializing nautilus-gdu extension
:(nautilus:1482): Gtk-CRITICAL **: _gtk_timeline_rewind: assertion 
`GTK_IS_TIMELINE (timeline)' failed
:(nautilus:1482): GLib-GObject-WARNING **: instance with invalid (NULL) class 
pointer
:(nautilus:1482): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 
`G_TYPE_CHECK_INSTANCE (instance)' failed
:Initializing nautilus-dropbox 0.7.1
:Initializing nautilus-gdu extension

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


On 2011-12-13T13:56:49+00:00 kotofos wrote:

Created attachment 546222
File: dso_list

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


On 2011-12-13T13:56:51+00:00 kotofos wrote:

Created attachment 546223
File: maps

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


On 2011-12-13T13:56:54+00:00 kotofos wrote:

Created attachment 546224
File: smolt_data

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


On 2011-12-13T13:56:57+00:00 kotofos wrote:

Created attachment 546225
File: backtrace

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


On 2012-06-30T15:38:47+00:00 efreeti wrote:

Create a new folder, crash when I tried to name it as "Radio-Em-DR"
(without double quotes)

backtrace_rating: 4
Package: nautilus-3.4.2-5.fc17
OS Release: Fedora release 17 (Beefy Miracle)

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


On 2012-06-30T15:38:53+00:00 

[Bug 918421] Re: gnome-settings-daemon crashed with SIGSEGV in idle_set_mode()

[Bug Watch Updater]

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

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

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

Title:
  gnome-settings-daemon crashed with SIGSEGV in idle_set_mode()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/918421/+subscriptions

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

[Bug 1682785] Re: nautilus (nautilus:16762): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client (nautilus:16762): Gtk-WARNIN

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nautilus  (nautilus:16762): Gtk-WARNING **: Failed to register client:
  GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to
  register client  (nautilus:16762): Gtk-WARNING **: Theme parsing
  error: Adwaita.css:51:71: Using one color stop with linear-gradient()
  is deprecated.  (nautilus:16762): Gtk-WARNING **: Theme parsing error:
  Adwaita.css:52:71: Using one color stop with linear-gradient() is
  deprecated. Nautilus-Share-Message: Called "net usershare info" but it
  failed: Klarte ikke å kjøre underprosess «net» (Fila eller mappa
  finnes ikke) ** ERROR:nautilus-canvas-
  container.c:6032:finish_adding_new_icons: assertion failed:
  (!container->details->auto_layout) Avbrutt (SIGABRT) (kjerne lagret i
  fil)

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

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

[Bug 1701175] Re: sorting type and inverse sorting flag not persisted in home directory across restarts

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  sorting type and inverse sorting flag not persisted in home directory
  across restarts

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

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

[Bug 1687497] Re: multiple default application settings conflicting

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  multiple default application settings conflicting

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

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

[Bug 1708661] Re: Nautilus 3.18.5 crashes when dragging icons on the desktop

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Nautilus 3.18.5 crashes when dragging icons on the desktop

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

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

[Bug 1681412] Re: Error when clicked on "Recents"

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Error when clicked on "Recents"

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

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

[Bug 1705290] Re: All windows opened are put one over the other and cannot be moved

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  All windows opened are put one over the other and cannot be moved

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

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

[Bug 1687510] Re: way to remove "Default Application" defective or makes no sense

[Launchpad Bug Tracker]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  way to remove "Default Application" defective or makes no sense

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

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

[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21

---
systemd (229-4ubuntu21) xenial; urgency=medium

  * networkd: do not uncoditionally apply NOARP.
  * networkd: fix size of MTUBytes so that it does not overwrites ARP.
  * Fixes regression-updates LP: #1727301

 -- Dimitri John Ledkov   Fri, 27 Oct 2017 09:21:18
+0100

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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 388898] Re: [MIR] empathy dependencies

[Bug Watch Updater]

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

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-19T20:00:10+00:00 Olivier wrote:

Farsight2 0.0.12 no longer depends on gst-plugins-farsight (which you
can prune from you distro along with farsight1).

But it needs gst-plugins-bad 0.0.12

The same applies to 0.0.9 in Fedora 11 (so please push out an update
there, otherwise Empathy calling is just broken).

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/4


On 2009-06-19T20:13:57+00:00 Olivier wrote:

Also, did I mention that the rpmfusion gst-p-bad package doesn't work
because the farsight plugins are disabled (becaues they conflict with
the outdated version of gst-p-farsight in F11)

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/5


On 2009-06-19T23:18:47+00:00 Brian wrote:

(In reply to comment #0)
> Farsight2 0.0.12 no longer depends on gst-plugins-farsight (which you can 
> prune
> from you distro along with farsight1).
> 
> But it needs gst-plugins-bad 0.0.12

If that is a hard dependency on gst-plugins-bad, that means farsight 2
will need to be removed from Fedora and moved to rpmfusion.

It would probably be helpful if the configure.ac was updated to check
for the necessary plugins are available for farsight2 to work correctly.

> The same applies to 0.0.9 in Fedora 11 (so please push out an update there,
> otherwise Empathy calling is just broken).

Ditto here if the gst-plugins-bad is a hard dependency, it will need to
be removed from F11.

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/6


On 2009-06-19T23:26:07+00:00 Brian wrote:

(In reply to comment #2)
> (In reply to comment #0)
> > Farsight2 0.0.12 no longer depends on gst-plugins-farsight (which you can 
> > prune
> > from you distro along with farsight1).
> > 
> > But it needs gst-plugins-bad 0.0.12
> 
> If that is a hard dependency on gst-plugins-bad, that means farsight 2 will
> need to be removed from Fedora and moved to rpmfusion.
> 
> It would probably be helpful if the configure.ac was updated to check for the
> necessary plugins are available for farsight2 to work correctly.

And going a little further, if this is a hard dep on gst-plugins-bad
empathy will also be removed since it depends tp-farsight (which in turn
depends on farsight2).  Not good.

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/7


On 2009-06-19T23:40:13+00:00 Bastien wrote:

What plugins are needed specifically?

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/8


On 2009-06-19T23:58:41+00:00 Olivier wrote:

You need rtpmanager, valve, rtpmux, autoconvert, liveadder, dtmf.

For the upcoming msnwebcam, you also need mimic.. but that one probably
needs to go on rpmfusion.

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/9


On 2009-06-20T22:44:49+00:00 Olivier wrote:

Btw, this will show up as a crash in empathy because of a bug in the
libtelepathy-farsight 0.0.6 GError handling code. So I'm adding the
gnome bug as a dep.

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/10


On 2009-06-20T23:25:12+00:00 Bastien wrote:

Other question, does Empathy support the missing-plugins GStreamer
framework to install missing plugins, should they be needed?

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/11


On 2009-06-20T23:45:50+00:00 Olivier wrote:

No it doesn't. I plan to support it in farsight2 at some point for the
codecs (lets say to install h.263 or h.264 codecs). But it's not going
to happen for the basic elements. I doubt totem uses missing plugins if
playbin is not installed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/telepathy-
farsight/+bug/388898/comments/12


On 2009-06-21T01:09:25+00:00 Bastien wrote:

(In reply to comment #8)
> No it doesn't. 

[Bug 863142] Re: [network]: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

[Bug Watch Updater]

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

** Changed in: gnome-control-center (Fedora)
   Importance: Unknown => Undecided

-- 
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/863142

Title:
  [network]: gnome-control-center crashed with SIGSEGV in
  gtk_builder_get_object()

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

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

[Bug 857603] Re: gnome-sudoku crashed with TypeError in function(): Expected a Gdk.Event, but got EventButton

[Bug Watch Updater]

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

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


On 2011-09-24T17:32:28+00:00 Jeremy wrote:

abrt version: 2.0.5
cmdline:python /usr/bin/gnome-sudoku
comment:Clicking the top or bottom part of the square (used to add a 
hint) doesn't work and spews out a traceback when run from the terminal. The 
game still continues to play though.
executable: /usr/bin/gnome-sudoku
kernel: 3.1.0-0.rc6.git0.3.fc16.x86_64
reason: types.py:43:function:TypeError: Expected a Gdk.Event, but got 
EventButton
time:   Sat Sep 24 13:30:05 2011

backtrace:
:types.py:43:function:TypeError: Expected a Gdk.Event, but got EventButton
:
:Traceback (most recent call last):
:  File "/usr/lib/python2.7/site-packages/gnome_sudoku/number_box.py", line 
194, in button_press_cb
:x, y = e.get_coords()
:  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gdk.py", line 207, in 
cull_success
:result = func(*args)
:  File "/usr/lib64/python2.7/site-packages/gi/types.py", line 43, in function
:return info.invoke(*args, **kwargs)
:TypeError: Expected a Gdk.Event, but got EventButton
:
:Local variables in innermost frame:
:info: 
:args: (,)
:kwargs: {}

smolt_data:
:
:
:General
:=
:UUID: 4352f880-7343-423e-8107-bf8ac078e9f2
:OS: Fedora release 16 (Verne)
:Default run level: Unknown
:Language: en_GB.utf8
:Platform: x86_64
:BogoMIPS: 3990.37
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Core(TM)2 Duo CPU T5800  @ 2.00GHz
:CPU Stepping: 13
:CPU Family: 6
:CPU Model Num: 15
:Number of CPUs: 2
:CPU Speed: 2000
:System Memory: 3826
:System Swap: 4996
:Vendor: TOSHIBA
:System: Satellite L305 PSLB8U-05202F
:Form factor: Notebook
:Kernel: 3.1.0-0.rc6.git0.3.fc16.x86_64
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Enforcing
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Devices
:=
:(32902:10521:4473:65382) pci, None, PCI/ISA, ICH9M LPC Interface Controller
:(4332:33078:4473:65382) pci, r8169, ETHERNET, RTL8101E/RTL8102E PCI Express 
Fast Ethernet controller
:(32902:10818:4473:65382) pci, i915, VIDEO, Mobile 4 Series Chipset Integrated 
Graphics Controller
:(32902:10819:4473:65382) pci, None, VIDEO, Mobile 4 Series Chipset Integrated 
Graphics Controller
:(32902:10560:4473:65382) pci, pcieport, PCI/PCI, 82801I (ICH9 Family) PCI 
Express Port 1
:(32902:10562:4473:65382) pci, pcieport, PCI/PCI, 82801I (ICH9 Family) PCI 
Express Port 2
:(32902:10568:4473:65382) pci, pcieport, PCI/PCI, 82801I (ICH9 Family) PCI 
Express Port 5
:(32902:10558:4473:65382) pci, snd_hda_intel, MULTIMEDIA, 82801I (ICH9 Family) 
HD Audio Controller
:(32902:10537:4473:65382) pci, ahci, STORAGE, ICH9M/M-E SATA AHCI Controller
:(32902:10549:4473:65382) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI 
Controller #2
:(32902:10544:4473:65382) pci, i801_smbus, SERIAL, 82801I (ICH9 Family) SMBus 
Controller
:(32902:9288:4473:65382) pci, None, PCI/PCI, 82801 Mobile PCI Bridge
:(32902:16946:32902:4609) pci, iwlagn, NETWORK, WiFi Link 5100 AGN
:(32902:10548:4473:65382) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI 
Controller #1
:(32902:10551:4473:65382) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI 
Controller #4
:(32902:10552:4473:65382) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI 
Controller #5
:(32902:10816:4473:65382) pci, agpgart-intel, HOST/PCI, Mobile 4 Series Chipset 
Memory Controller Hub
:(32902:10550:4473:65382) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI 
Controller #3
:(32902:10553:4473:65382) pci, uhci_hcd, USB, 82801I (ICH9 Family) USB UHCI 
Controller #6
:(32902:10554:4473:65382) pci, ehci_hcd, USB, 82801I (ICH9 Family) USB2 EHCI 
Controller #1
:(32902:10556:4473:65382) pci, ehci_hcd, USB, 82801I (ICH9 Family) USB2 EHCI 
Controller #2
:
:
:Filesystem Information
:=
:device mtpt type bsize frsize blocks bfree bavail file ffree favail
:---
:/dev/sda9 / ext4 4096 4096 3844092 2548869 2509826 983040 890887 890887
:/dev/sr0 WITHHELD iso9660 UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN 
UNKNOWN UNKNOWN
:

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


On 2011-09-24T17:34:17+00:00 Jeremy wrote:

Added link to Ubuntu ug.

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


On 

[Bug 828623] Re: [Regression] gnome control centre does not allow you to disable the laptop screen while leaving an external DisplayPort connected screen working

[Bug Watch Updater]

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

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

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

Title:
  [Regression] gnome control centre does not allow you to disable the
  laptop screen while leaving an external DisplayPort connected screen
  working

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

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

[Bug 877751] Re: Clicking the Forward Button on an Evolution Email results in no response from the application

[Bug Watch Updater]

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

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


On 2011-09-23T11:29:20+00:00 Tim wrote:

Description of problem:
When clicking the "Forward" button in a message window, the window just closes. 
 These messages appear in .xsession-errors:

(evolution:24838): evolution-shell-CRITICAL **:
e_shell_backend_get_shell: assertion `E_IS_SHELL_BACKEND
(shell_backend)' failed

(evolution:24838): evolution-mail-CRITICAL **: em_utils_forward_message:
assertion `E_IS_SHELL (shell)' failed

Version-Release number of selected component (if applicable):
evolution-3.1.92-1.fc16.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Double click on a message to open its message window
2.Click Forward
  
Actual results:
Window closes, assertion failure in .xsession-errors, no further action.

Expected results:
Compose window for forwarding email.

Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/877751/comments/0


On 2011-09-27T07:05:28+00:00 Milan wrote:

Thanks for a bug report. I was unable to reproduce it for the first
time, only after I set the browser window to close automatically when
the shown message is forwarded/replied to.

I moved this upstream as [1]. Please see [1] for any further updates. If
possible, please CC yourself there, in case upstream developers will
have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=660224

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/877751/comments/1


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

** Changed in: evolution (Fedora)
   Importance: Unknown => Undecided

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

Title:
  Clicking the Forward Button on an Evolution Email results in no
  response from the application

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

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

[Bug 881660] Re: Wired interface cannot be disconnected using Shell network applet

[Bug Watch Updater]

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

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


On 2011-10-19T12:50:45+00:00 Kjartan wrote:

Description of problem:

I have my Dell Latitude E4300 in a docking station at work and when I
try to disable wired ethernet to have the machine use the wireless it
doesn't do anything.

The icon in the top bar still shows the wired network icon and I'm still
connected to it.

I also see this error message in .xsession-errors:

JS ERROR: !!!   Exception was: Error: Error invoking NMClient.disconnect: 
Invalid callback given for argument callback
JS ERROR: !!! lineNumber = '0'
JS ERROR: !!! fileName = '"gjs_throw"'
JS ERROR: !!! stack = '"("Error invoking NMClient.disconnect: Invalid 
callback given for argument callback")@gjs_throw:0
()@/usr/share/gnome-shell/js/ui/status/network.js:371
([object 
_private_Clutter_Event])@/usr/share/gnome-shell/js/ui/status/network.js:232
([object _private_Shell_GenericContainer],[object 
_private_Clutter_Event])@/usr/share/gnome-shell/js/ui/popupMenu.js:81
"'
JS ERROR: !!! message = '"Error invoking NMClient.disconnect: Invalid 
callback given for argument callback"'
Gtk-Message: Failed to load module "pk-gtk-module"
[kmaraas@e4300 ~]$ 


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


How reproducible:


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


Expected results:


Additional info:

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


On 2011-10-26T15:35:09+00:00 Dan wrote:

Can be worked around pretty easily in the shell, but real cause is
missing introspection annotations in libnm-glib.  Fixed by
a7f7e80839b5492ddf16783575e9d2bbbc970b3a upstream.

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


On 2011-12-02T13:06:58+00:00 Fedora wrote:

NetworkManager-0.9.2-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/NetworkManager-0.9.2-1.fc16

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


On 2011-12-02T13:07:50+00:00 Jirka wrote:

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

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


On 2011-12-04T02:23:03+00:00 Fedora wrote:

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

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


On 2011-12-06T01:00:38+00:00 Fedora wrote:

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

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


** Changed in: network-manager (Fedora)
   Status: Unknown => Fix Released

** Changed in: network-manager (Fedora)
   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/881660

Title:
  Wired interface cannot be disconnected using Shell network applet

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

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

[Bug 919549] Re: totem segfaults in gst_stream_get_other_pad_from_pad()

[Bug Watch Updater]

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

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


On 2011-10-01T16:45:27+00:00 denvor wrote:

abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 59573 bytes
cmdline: totem '/home/denvor/Pictures/My 
Pictures/\xe5\x96\x9c\xe6\xac\xa2\xe4\xb8\x8a\xe6\xb5\xb7\xe7\x9a\x84\xe7\x90\x86\xe7\x94\xb1.flv'
component: totem
Attached file: coredump, 109985792 bytes
crash_function: gst_stream_get_other_pad_from_pad
executable: /usr/bin/totem
kernel: 2.6.35.14-96.fc14.i686
package: totem-1:2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/totem was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1317487051
uid: 500

How to reproduce
-
1. I double click on flv file, it's 2MB,
then, crash
2.
3.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/919549/comments/0


On 2011-10-01T16:45:30+00:00 denvor wrote:

Created attachment 525877
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/919549/comments/1


On 2012-08-16T12:40:29+00:00 Fedora wrote:

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/919549/comments/8


** Changed in: gstreamer0.10 (Fedora)
   Status: Unknown => Won't Fix

** Changed in: gstreamer0.10 (Fedora)
   Importance: Unknown => Undecided

-- 
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/919549

Title:
  totem segfaults in gst_stream_get_other_pad_from_pad()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/919549/+subscriptions

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

[Bug 921708] Re: [color]: gnome-control-center crashed with SIGSEGV in gcm_prefs_remove_device()

[Bug Watch Updater]

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

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


On 2011-09-24T12:49:37+00:00 Jurgen wrote:

abrt version: 2.0.5.980
backtrace_rating: 4
cmdline:gnome-control-center --overview
comment:Gnome settings was openend in Overview mode. Grayed out box 
with 'checking for updates'. After a while this crash.
crash_function: gcm_prefs_remove_device
executable: /usr/bin/gnome-control-center
kernel: 3.1.0-0.rc6.git0.3.fc16.x86_64
reason: Process /usr/bin/gnome-control-center was killed by signal 11 
(SIGSEGV)
time:   Sat Sep 24 14:38:13 2011
uid:1000
username:   kramer
var_log_messages: Sep 24 14:38:14 develbox abrt[1800]: saved core dump of pid 
1706 (/usr/bin/gnome-control-center) to 
/var/spool/abrt/ccpp-2011-09-24-14:38:13-1706.new/coredump (36995072 bytes)

backtrace:  Text file, 34714 bytes
maps:   Text file, 77876 bytes

build_ids:
:7343d35696ce251688ece0a26e457e61ca805cfd
:bce8fb6913e0b658c53b896b05d075af7fa5cf73
:aaf7ed41612348bd1141db06cadd428244aa6ea5
:934bb835b5075f81fdfb713b49281ce9aaf49f59
:0ce2f704cf71fa82b26d6fcc508403b606b12626
:d832486d465b142f7d2e92bb172a5fa904d19bb4
:89017ab0b75e533e4294f74ee8f7db3daceea536
:e3c88cb9ea428bd61f4064dbd53acae2d396a1ec
:944ef25e2acd98e7b54925ab04bce5499395e8e7
:5e8c36ca13a4af14fa6b1b45a0dbfb43ed6aed6e
:d0c6e13f00a20952a72a945c929efb175fd760e3
:a594ab36356a9b6dc6ecf25a6124463ccbfd0a29
:17ef36c4f4e8918b9ab1c2e3eaca7c9b584ad5cb
:edebfad67bdac472272d049dc7ec302f47b02f32
:58f90ee2b291c71757299dd2c59594bee447b5c0
:44ece411beb2ef1acdb5eb2161666de41cc2f31d
:f4e5dc4f25af9d5f5d8ba92201a6baad0ce84c29
:00da0e0e356101117459de059fc646d2b757303f
:3f156a456c851b3b5d4b35bb367d55c4a5f57220
:aaf62304b0fc10611d35b4f56005479d4c58868d
:0906a8d09c552fc0824755d349d24aebe70c0a24
:db91fd8ad0a21e25ee99fdba1a858ac65403e2d3
:8acc43df965b3c0a70dcfad11c0ade056bdb055b
:04c0c35c13f6e2955bfe6eac7fc2202187364e26
:cc32e70895d23acd7bde1ef1a3286b5e179e2d49
:a9e9e0c4489c5cc0a7e6a486ab4e9e08e607ee28
:9fd35565043bc57e1d8bf70810b7c6b402a9be93
:400444fb368f79b54959b083f449a1497bf71c13
:83fd1ef1b856a64c7772aa364b1b1f59c046f538
:6bd1330e8e4169846204992730118658bd4358ba
:4a7e68edf2778a9fbd3d4a8fbd3f9d1e7b785fc6
:0e6282316ef2785af671bcdb223c7c4c5c086dc8
:c3cc06ceb6e1a99743164a9db770a23d5a68dd47
:4bc49f23a792210b71dbf308890f191ac2a03336
:7ddde233293b60ff6de1dabd78d95aa43e47fc23
:e81e108ee1e9f0fca2ef39f5d0517483c78ae650
:4fa4bfc3710087639826a7b39cf566261b426bbe
:91689252818532ec13597b6528d38be93b2706c4
:381b7069d555ff62cc543b6f7d3053b9fdcf2c20
:f2f0083eee5c81eaeb79d2e4234dc495b9fca4d4
:3dd00a31cf09e7d59a58bbcf0750e12401a23e53
:e2911f2f841009a6226d0195f224039e7adb39c7
:890ab6679360d786ad73cf5ab210babcc1d9936d
:ff9917a4607f469e2cf236e226ad9b03b7720f62
:9ea81971c14b711655ced0a734db062ab7c4eec7
:954b760933764c15018f3937ab72f5bbe2018a35
:bbe08210c357ba434ea6dc29fff2f2b4eb2a0e27
:e2e9aa46522b1e2189777d91a5666c34fc7d46df
:d440afe7396b3365dcb935f9bf7f2fb28f3839de
:5df361c26dcd06bc301db9bf05251f4f743f8a51
:5cb5f8da286abd58aeab3bd6676e661d52ec2b5d
:fced0590b1aa308509df438f245ec840387ac9e3
:2e0431d5346827d691e6e58ee402c02671774e41
:56f519bae08b00cc5e8c857fb8b2f4ff3f230032
:9afa4a71f0f6a189e8dcf1179b9445a81df0ab28
:6162aef2617fc89176e1bda96ef3cdefc54fa19d
:99745aea093d045c4540ad54749678081eb09af8
:5d265e3bc9831d1d4cdf0eb0e92681b0e9e7398b
:76bb1d8d017f41044bcb4636d7d221bf839d6f05
:e045ea1e1a7ca7dcef670a7ee4dbcfaf77949074
:13df2842f5f3a05e2d93388cebeff2e6787d92a5
:2f2ac36861de485a681e89d5fa0de0517b82e5a0
:0d74576182a86b7b132171701e28ae4c53d6a719
:8ca893c2cf400317322477c03e6b754bd2533a3a
:eacb8020c70b5844d07665eeb30f91e924a92bb2
:4068a212f3244ede26da4f92bc190ff4e2b9e8dc
:33675710cde008d5cb57ea8b650172fc97266d18
:ce596b3ffb0c44a19d7c405b865830535b1b7f8a
:353a61c264385b7feec38c9e34040aa9bc615d6a
:6489fb034cf0a08cc566170a702403c64caddf29
:4b01fe6e705219deca2756ff0720d52ec81b4c87
:3f9c9f9dcc08d0b026ef4049386c326121285262
:f417b25f83a1b878b1a8965478a7eecf0344eaca
:dfc1b11c1ced5c134adca2b29874a41f39f0eeaf
:4b6e12c2d03e09f80c6fda9659b6c5d0c47b6fe5
:48aea888319e1848137073c9cbde54a4c2a731c9
:4684662811a800eb597f106b8614902c24974668
:b038838c10d38141b6ec19b40168be9caaa78286
:f5c5b66226da1a1365a97397b1143bebf777b7b6
:c1f034e216940c41dbe23880c3400ef9cffae35d
:d302fc3213eff0072dfc04d99bf84f28df0f7421
:d382cf9422aa044ad1bc2febeed52db164476b76
:be507c791e34415e8f42f0e6030c889b2895cf9a
:0fccce2fdb46650674ef5b64fae5f25f14c88e08
:29c869a877c1ceade9538f84f5ec70c3901b66b3
:b967cd759e60040c1e0c6457e5a388ed4bbf769f
:46d1755f7ac3cdf76740c31c659511fe3e8b409c
:b3c60343c4ef09307cd644d5da914f6c14107c0b

[Bug 878486] Re: gsd-printer crashed with SIGABRT in __kernel_vsyscall()

[Bug Watch Updater]

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

** Changed in: gnome-settings-daemon (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/878486

Title:
  gsd-printer crashed with SIGABRT in __kernel_vsyscall()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/878486/+subscriptions

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

[Bug 1728184] Re: mozjs38 is no longer supported by Mozilla

[Jeremy Bicha]

** Also affects: 0ad (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mozjs38 is no longer supported by Mozilla

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

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

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

[Bug Watch Updater]

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

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-21T00:21:58+00:00 Edmond wrote:

Description of problem:

hidden window is unable to restore to current workspace

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

Window List 2.20.1

How reproducible:

Every time

Steps to Reproduce:
1. Goto Window list preferences and set "Restore to current workspace", and
"Show windows from all workspace"
2. Minimize a window
3. Move to another workspace
4. click at the minimized windows from window list  

Actual results:

The window is not restore to current workspace

Expected results:

The window is restored, and move to the current workspace

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


On 2008-11-26T08:37:39+00:00 Bug wrote:


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

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

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

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

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

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


On 2009-01-09T07:28:21+00:00 Bug wrote:


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

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

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

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


On 2009-01-09T08:08:48+00:00 Edmond wrote:

still seeing this problem on F10

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


On 2009-11-17T23:09:40+00:00 Owen wrote:

Upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=571588

Presumably this broke when the changes in:

 https://bugzilla.gnome.org/show_bug.cgi?id=482354

Went in, since they changed "activating" a window not to hop workspaces
unless it was a transient window.

The right fix seems to involve two parts:

 A) The pager/libwnck needs to set the source indication properly in the 
_NET_ACTIVE_WINDOW. Right now it is using the legacy/indeterminate 
value of 0.

 B) Metacity should always hop workspaces when it gets a _NET_ACTIVE_WINDOW
message with a value of 2 (from a pager)

The libwnck only fix would be to have the libwnck tasklist explicitly
move of the window it was activating to the current workspace.

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


On 2009-11-18T10:08:50+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

[Bug 1728184] Re: mozjs38 is no longer supported by Mozilla

[Bug Watch Updater]

** Changed in: libproxy
   Status: Unknown => New

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

Title:
  mozjs38 is no longer supported by Mozilla

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

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

[Bug 970146] hey my dear

[Stian Sigbjørnsen]

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

Hi!

I just wished to say how much I miss you  and give out some  important
info, just read  it,  you will not regret
http://www.sosbuyer.ca/somehow.php?UE85NzAxNDZAYnVncy5sYXVuY2hwYWQubmV0

Best wishes, Stian Sigbjornsen


From: Bug 970146 [mailto:970...@bugs.launchpad.net]
Sent: Friday, October 27, 2017 9:30 PM
To: stian.sigbjoern...@hesbynett.no
Subject: You should!

First of all im a Muslim and ive been living in Germany  for 18 years
now.  I  don't really blame the people  for  protesting.   the blame is
on the media like BILD or other "newssources"  just straight up lying
about a lot of stuff that is in relation to Islam. Companies like the
axel springer  Verlag have a  history of being anti Islam.  And the
whole crap about crime  rates and shit.  It's the same in every single
country.  The lower the  income the more crimes will be  committed. And
I have to  say it's getting worse and  worse  living  with racism here
in Germany.   I had  to search for  a house  for  over 6  months even
though my German is perfect,  I  don't  have an accent, a job and  no
conflicts  with the law whatsoever. And people saying it's not racism..
That's bullshit.   The Nazi thrive  in  protests like these and I fear
that I have to someday  leave the country I love.


Sent from Mail for Windows 10

** Attachment added: "99A6DC73596C659E.jpg"
   
https://bugs.launchpad.net/bugs/970146/+attachment/4998394/+files/99A6DC73596C659E.jpg

-- 
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/970146

Title:
  Keyboard language layout changes after reboot

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

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

[Bug 349312] Re: Evolution 2.26 does not support import of outlook .pst

[Bug Watch Updater]

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

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-31T13:37:19+00:00 Espen wrote:

Description of problem:
I can't import pst-files in evolution. I choose "import" and select the 
pst-file. The importer doesn't recognize the filetype and i can't continue.

I looked at the source and AFAIK there should be a pst-import plugin,
but it's not included in the fedora rpm.

Version-Release number of selected component (if applicable):
evolution-2.26.0-1.fc11.i586
evolution-data-server-2.26.0-1.fc11.i586

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/349312/comments/3


On 2009-04-10T15:04:39+00:00 Matthew wrote:

Will be happy to enable this feature as soon as Fedora gets a library
for reading PST files.  I believe libpst-0.6.35 will grow an actual
library.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/349312/comments/4


On 2009-06-09T12:50:42+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/evolution/+bug/349312/comments/18


On 2009-06-17T10:36:31+00:00 Zdravko wrote:

I was able to convert a .pst file to mbox with readpst.

libpst-libs-0.6.36-1.fc11.i586
libpst-0.6.36-1.fc11.i586


So it looks to me that fedora has this incorporated and the plugin should be 
enabled!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/349312/comments/19


On 2009-06-19T20:34:24+00:00 ritz wrote:

BuildRequires would need libpst-devel, and libytnef-devel paclage, to
allow the plugins to be built in.

-- ritz

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/349312/comments/20


On 2009-06-20T07:18:21+00:00 ritz wrote:

Created attachment 348735
patch based on upstream code

We also need to add -
http://bugzilla.gnome.org/show_bug.cgi?id=578945

patch built against evolution-2.27.3 .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/349312/comments/21


On 2009-07-02T21:17:33+00:00 Matthew wrote:

Patch is already outdated against libpst 0.6.41.

libpst has no API stability right now and it's not worth trying to chase.
Once it settles down I'll enable the Evolution plugin.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/349312/comments/22


On 2009-07-28T17:46:02+00:00 Milan wrote:

Back enabled in 2.27.5-3, as Matt told me. Thus closing as such.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/349312/comments/24


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

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

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

Title:
  Evolution 2.26 does not support import of outlook .pst

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

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

[Bug 39554] Re: E-mail "start with" filter requires an extra leading space to work

[Bug Watch Updater]

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

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-09-14T17:36:24+00:00 John wrote:

version: evolution-2.8.0-1.fc6

The "starts with" subject filter does not match the initial string as presented
to the user in the subject line. 

I looked at the raw message source and observed that Subject header line
was:

Subject: foo

but if you set the subject starts with filter to "foo" it fails to match, but if
you set it to " foo" it matches. It appears some part of the code is stripping
leading whitespace and others are not.

Although RFC 822 would say the leading white space after the field-name and
colon is technically part of the subject field body common sense and user
expectation would say leading white space does not count when matching the
beginning of a subject. The leading white space should be stripped (or ignored)
either when performing a "starts with" match.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/39554/comments/8


On 2007-01-02T17:11:57+00:00 Matthew wrote:

Verified on Fedora Core 6 as well as Rawhide.

It works fine for search folders.  I have countless search folders for
particular bugs that are configured as:

   Subject  Starts With  "[Bug xx]"

Strange that Evolution would not be using the same mechanism for evaluating
filter rules and search folder rules.

Closing as UPSTREAM since an equivalent bug report exists upstream.  I will
continue to track the problem there.  Please refer to [1] for further updates.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=343450

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/39554/comments/9


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

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

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

Title:
  E-mail "start with" filter requires an extra leading space to work

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

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

[Bug 214370] Re: Logout/Shutdown Sound Not Working

[Bug Watch Updater]

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

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-06T14:34:55+00:00 Mathias wrote:

User-Agent:   Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.0.2)
Gecko/2008092318 Fedora/3.0.2-1.fc9 Firefox/3.0.2

I've never heard the logout sound (GNOME), but I can hear the login sound. 
It seems like it logs out even before the sound is played. 

Reproducible: Always

Steps to Reproduce:
1. Log in a GNOME session (BTW you should hear the login sound, it's OK) ;
2. Do some stuff or nothing with GNOME (if you want, check, like me, that the 
logout sound is enabled) ;
3. Logout. 
Actual Results:  
It logs out directly. No sound can be heard. 

Expected Results:  
I should have heard the logout sound. 
GNOME desktop should have waited for the logout sound to be fully played, and 
then he could log out. 

Tried on a desktop computer, and on a laptop. 
« Rawhide » installed by the F10 Preview LiveCD (x86_64). All possible rawhide 
updates installed so far.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/214370/comments/19


On 2008-11-26T04:53:03+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/pulseaudio/+bug/214370/comments/20


On 2008-11-30T13:38:20+00:00 Mark wrote:

I can confirm that this bug is still present in the current fedora
releases (Fedora 10).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/214370/comments/21


On 2009-02-28T23:43:47+00:00 Makoto wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/214370/comments/23


On 2009-11-18T09:21:41+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/pulseaudio/+bug/214370/comments/46


On 2009-12-18T06:45:36+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/pulseaudio/+bug/214370/comments/48


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

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

Title:
  Logout/Shutdown Sound Not Working

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

-- 
desktop-bugs 

[Bug 814799] Re: It is possible to create a new tab on the desktop window with Ctrl + T

[Bug Watch Updater]

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

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


On 2011-09-06T11:44:11+00:00 Ferry wrote:

Description of problem:
Doing a CTRL-T on the desktop opens new nautilus tab right there on the desktop

Version-Release number of selected component (if applicable):
gnome-shell.x86_64   
3.0.2-4.fc15   @updates
gnome-shell-extension-alternative-status-menu.noarch 
3.0.2-3.20110630git939994d0.fc15   @updates
gnome-shell-extension-auto-move-windows.noarch   
3.0.2-3.20110630git939994d0.fc15   @updates
gnome-shell-extension-common.noarch  
3.0.2-3.20110630git939994d0.fc15   @updates
gnome-shell-extension-cpu-temperature.noarch 
0-0.2.gitcdc83b0.fc15  @updates
gnome-shell-extension-drive-menu.noarch  
3.0.2-3.20110630git939994d0.fc15   @updates
gnome-shell-extension-mediaplayers.noarch
0-0.1.git259f96e.fc15  @updates
gnome-shell-extension-noim.noarch
1.0-1.fc15 @updates
gnome-shell-extension-places-menu.noarch 
3.0.2-3.20110630git939994d0.fc15   @updates
gnome-shell-extension-presentation-mode.noarch   
0-0.2.gitc3ce6b2.fc15  @updates
gnome-shell-extension-remove-accessibility-icon.noarch   
20110603-1.fc15@updates
gnome-shell-extension-theme-selector.noarch  
0.9-3.fc15 @updates
gnome-shell-extension-user-theme.noarch  
3.0.2-3.20110630git939994d0.fc15   @updates
gnome-shell-extension-windowsNavigator.noarch
3.0.2-3.20110630git939994d0.fc15   @updates
gnome-shell-theme-atolm.noarch   
1.0-1.fc15 @updates
gnome-shell-theme-dark-glass.noarch  
1.0-1.fc15 @updates
gnome-shell-theme-gaia.noarch
1.0-1.fc15 @updates
gnome-shell-theme-orta.noarch
1.0-1.fc15 @updates
gnome-shell-theme-smooth-inset.noarch
1.0-1.fc15

How reproducible:
always

Steps to Reproduce:
1. see description
2.
3.
  
Actual results:
new empty nautilus tab

Expected results:
nothing happens

Additional info:

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


On 2011-09-23T14:15:27+00:00 Ferry wrote:

ping

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


On 2012-08-07T17:51:16+00:00 Fedora wrote:

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more 

[Bug 958139] Re: nautilus crashed with SIGSEGV in nautilus_icon_canvas_item_get_drag_surface()

[Bug Watch Updater]

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_icon_canvas_item_get_drag_surface()

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

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

[Bug 1728184] [NEW] mozjs38 is no longer supported by Mozilla

[Jeremy Bicha]

Public bug reported:

mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It
has not been supported by Mozilla since June 2016.

Please migrate to mozjs52, the only version currently supported by
Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in
Debian Testing.

Currently these packages depend on mozjs38
--
0ad (embedded code copy)
cjs
libproxy1-plugin-mozjs

https://github.com/linuxmint/cjs/issues/52
https://github.com/libproxy/libproxy/issues/71

** Affects: libproxy
 Importance: Unknown
 Status: Unknown

** Affects: cjs (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: libproxy (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: mozjs38 (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: bionic

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

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

** Description changed:

  mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It
  has not been supported by Mozilla since June 2016.
  
  Please migrate to mozjs52, the only version currently supported by
  Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in
  Debian Testing.
  
  Currently these packages depend on mozjs38
  --
  0ad (embedded code copy)
  cjs
- libproxy
+ libproxy1-plugin-mozjs

** Changed in: libproxy (Ubuntu)
   Importance: Undecided => High

** Changed in: libproxy (Ubuntu)
   Status: New => Triaged

** Changed in: cjs (Ubuntu)
   Importance: Undecided => High

** Changed in: cjs (Ubuntu)
   Status: New => Triaged

** Bug watch added: github.com/libproxy/libproxy/issues #71
   https://github.com/libproxy/libproxy/issues/71

** Also affects: libproxy via
   https://github.com/libproxy/libproxy/issues/71
   Importance: Unknown
   Status: Unknown

** Description changed:

  mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It
  has not been supported by Mozilla since June 2016.
  
  Please migrate to mozjs52, the only version currently supported by
  Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in
  Debian Testing.
  
  Currently these packages depend on mozjs38
  --
  0ad (embedded code copy)
  cjs
  libproxy1-plugin-mozjs
+ 
+ https://github.com/linuxmint/cjs/issues/52
+ https://github.com/libproxy/libproxy/issues/71

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

Title:
  mozjs38 is no longer supported by Mozilla

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

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

[Bug 1728181] [NEW] systemd-networkd-wait-online waits when devices are unmanaged

[Mathieu Trudel-Lapierre]

Public bug reported:

I started a system with cloud-init disabled, etc. and a single real
network interface (ens3) that could be configured.

That VM has no configuration whatsoever for systemd-networkd, as that
would have to have been written by netplan, and cloud-init did not
generate netplan config (because it was disabled).

So:

root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
d-networkd-wait-online --ignore=lo
ignoring: lo
Event loop failed: Connection timed out
root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 ens3 ether  off unmanaged 
  3 sit0 sitoff unmanaged 

3 links listed.
root@ubuntu:/etc/systemd/system/network-online.target.wants# 


The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

FWIW, having wait-online look up configuration might later be useful
also to figure out if an interface was configured, but marked as
optional (such that it is explicitly not required to be up at boot), or
if we want to configure network devices but specify that networkd should
*not* bring them online (like "administratively disabled" interfaces in
Cisco world using the "shutdown" command).

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

-- 
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/1728181

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

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

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

[Bug 419777] Re: evince crash when read pdf file

[Bug Watch Updater]

** Changed in: evince (Fedora)
   Status: Confirmed => Won't Fix

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

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

Title:
  evince crash when read pdf file

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

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

[Bug 670128] Re: gnome-open uses firefox while it's not the preferred browser

[Bug Watch Updater]

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

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-11-18T18:13:46+00:00 Bastien wrote:

Created attachment 461347
patch

GNOME switched to using the x-scheme-handler/http(s) for the default
browser, instead of a custom GConf setting.

See also:
http://www.hadess.net/2010/10/new-control-center-and-you.html
http://standards.freedesktop.org/shared-mime-info-spec/shared-mime-info-spec-latest.html#id2869854

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/2


On 2010-11-18T18:16:22+00:00 Bastien wrote:

Note that this is needed for Chromium to detect whether it's the default
browser or not.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/3


On 2010-11-18T18:21:06+00:00 Colin wrote:

In order to upstream this patch, wouldn't we need to make it able to
detect GNOME 2.32 vs 3 and choose the right one?

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/4


On 2010-11-18T18:29:45+00:00 Rex wrote:

Any sh snippet advice on how to detect gnome3?  (and is this change
specific to gnome3)?

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/5


On 2010-11-18T19:31:32+00:00 Bastien wrote:

(In reply to comment #3)
> Any sh snippet advice on how to detect gnome3?  (and is this change specific 
> to
> gnome3)?

It's GNOME3 specific, so this is what we'll need in Fedora going forward
(from F15 onwards).

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/6


On 2010-11-19T02:32:37+00:00 Bastien wrote:

Created attachment 461430
updated patch

Fixes xdg-settings check not working as expected (we were comparing a
desktop name to a binary one).

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/7


On 2010-11-19T02:35:43+00:00 Bastien wrote:

(In reply to comment #2)
> In order to upstream this patch, wouldn't we need to make it able to detect
> GNOME 2.32 vs 3 and choose the right one?

Right, it seems that the upstream isn't as dead as I thought and Rex is
a committer, so I should fix it up.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/8


On 2010-11-19T03:31:02+00:00 Bastien wrote:

Created attachment 461442
new patch

Adds the ability to detect GNOME 3.x, on its own, and also ports the
mailto functionality to x-scheme-handler.

I also tested the GNOME3 code path more thoroughly for the browser
settings, and it works as expected on the command-line, and when used in
chromium ("check" to detect the current browser, and "set" to set
chromium as the default browser).

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/9


On 2011-02-01T12:58:40+00:00 Bastien wrote:

Any news on this?

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/20


On 2011-02-01T13:27:43+00:00 Rex wrote:

Thanks for the poke, I'll work on this today.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/21


On 2011-02-01T15:25:59+00:00 Rex wrote:

Patch upstreamed (with some minor fuzz),

http://cgit.freedesktop.org/xdg/xdg-
utils/commit/?id=6f49c05ceb2a1935d07c49c2e100b5cf3cdf5f26

and snapshot build xdg-utils-1.1.0-0.2.20110201.fc15 submitted,
http://koji.fedoraproject.org/koji/taskinfo?taskID=2754753

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/670128/comments/22


On 2011-07-14T00:26:23+00:00 Mark wrote:

Not sure if this needs to be re-opened or if it's a new issue, but the
functionality is broken in xdg-utils-1.1.0-0.6.20110505.fc15.noarch.

[mark@thinkpad ~]$ xdg-settings get default-web-browserwhich: no 
gnome-default-applications-properties in 

[Bug 382393] Re: keyboard applet flag size to big

[Bug Watch Updater]

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

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-15T06:20:38+00:00 Todor wrote:

Created attachment 323684
screenshot of the applet area

Description of problem:
The keyboard-indicator applet takes all the available space in the gnome panel 
(panel height). This is even more apparent in the case the user has the 
settinhs showFlags in gconf turned on. The applet should strive for a more 
unified look, in order to fit in with the other applets

Version-Release number of selected component (if applicable):
gnome-applets-2.24.1-1.fc10.x86_64

Steps to Reproduce:
1. Download a country flag for your layout (svg or png from Wikipedia will 
work, size doesn't matter) and place under ~/.icons/flags/<2-char-iso-code>.png
2. Turn on flags: `gconftool-2 -t bool -s 
/desktop/gnome/peripherals/keyboard/indicator/showFlags true`
3. Select the "Keyboard Indicator" from the available panel applet list and add 
to panel if not already on.
  
Actual results:
The flag icon is shown on the panel, and it takes all of the panel's height. 
The icon width is scaled accordingly to its height. The applet "feels" much 
bulkier than the other applets.

Expected results:
A more consistent look, some space on top and bottom of the applet.

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


On 2008-11-15T06:26:45+00:00 Todor wrote:

It would be nice, if the flag icon size is configurable via gconf or
gtkrc. Anyway a fast workaround is a small change in the applet code,
delimiting it to only 75% of the available height. (maybe that would be
even better solved as a setting in gconf, named "zoom" or "scale")

diff -uNr a/gswitchit/gswitchit-applet.c b/gswitchit/gswitchit-applet.c
--- a/gswitchit/gswitchit-applet.c  2008-11-15 07:04:17.0 +0100
+++ b/gswitchit/gswitchit-applet.c  2008-11-15 07:06:07.0 +0100
@@ -614,7 +614,7 @@
gtk_widget_show_all (sia->applet);
gtk_widget_realize (sia->applet);
 
-   max_ratio = gkbd_indicator_get_max_width_height_ratio ();
+   max_ratio = 0.75 * gkbd_indicator_get_max_width_height_ratio ();
 
if (max_ratio > 0) {
switch (orient) {

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


On 2008-11-15T06:28:24+00:00 Todor wrote:

Created attachment 323685
PATCH limit the size of the applet to 75% of available height

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


On 2008-11-15T06:32:03+00:00 Todor wrote:

Created attachment 323686
screenshot of the restricted applet

Here's how the applet looks with size fixed at 75% height. The
screenshot is only with the icon, but turning off the flags and using
text only looks good as well.

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


On 2008-11-15T20:01:31+00:00 Ray wrote:

Hi Todor,

Do you mind posting your patch upstream at bugzilla.gnome.org?

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


On 2008-11-26T05:25:46+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-
applets/+bug/382393/comments/5


On 2009-11-18T09:22:49+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 

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

[Bug Watch Updater]

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

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-13T02:17:49+00:00 Sean wrote:

This is filed against Empathy 2.28.2.

After performing a system update, Empathy is unable to login to AIM and
ICQ. Interestingly, Pidgin is also experiencing the same error,
reporting the problem as "Received unexpected response from
https://api.screenname.aol.com/auth/clientLogin;. Empathy didn't specify
what the problem was.

On the basis of that error, I ran Wireshark and watched the login
attempt.

Empathy sends the following request to the server (with personal details
omitted):

--
GET 
http://api.oscar.aol.com/aim/startOSCARSession?a=[...]=xml=[...]=1263348414=1_sha256=[...]
HTTP/1.0

Connection: close

Accept: */*

Host: api.oscar.aol.com
--

The response from the server is then as follows:

--
HTTP/1.1 200 OK

Date: Wed, 13 Jan 2010 02:06:54 GMT

Server: Apache

Content-Length: 286

Pragma: no-cache

Cache-Control: no-store,no-cache,must-revalidate

Keep-Alive: timeout=1, max=61

Connection: Keep-Alive

Content-Type: text/xml



http://developer.aim.com/xsd/aim.xsd;>400useTLS=1
 is not allowed for non secure 
requests.1263348414
--

Empathy then reports that the login failed. I have verified that my
accounts are still valid: they successfully connect using the website
Meebo.

It is interesting that both Empathy and Pidgin are suddenly experiencing
the same error. Thinking that the bug must be on AOL's side, I checked
with other (non-Fedora) Empathy/Pidgin users, but haven't been able to
find anyone else who could reproduce the bug.

The output of `rpm -ql --last` | head -75` is provided in the
attachment.

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


On 2010-01-13T02:18:35+00:00 Sean wrote:

Created attachment 383392
rpm -ql --last | head -75

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


On 2010-01-14T14:33:23+00:00 Christopher wrote:

I am experiencing the same error (confirmed with Wireshark) in Empathy
after updating from libpurple-2.6.4-2.fc12.i686 to 2.6.5-1.fc12.i686.

I undid a batch of updates applied at 2010-01-13 12:54, which brought me
back to libpurple-2.6.3-2.fc12.i686.  After rebooting, I was able to
connect to the AIM network in Empathy.  Then I updated Empathy only, to
2.6.5-1.fc12.i686, and I started getting the same error again.

libpurple is part of the pidgin component, but I don't know whether the
problem is in Empathy or libpurple code.

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


On 2010-01-14T15:06:10+00:00 Christopher wrote:

According to Bug 554978, Pidgin upstream is working on a fix.

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


On 2010-01-16T02:45:21+00:00 Sean wrote:

This bug is closed by empathy-2.28.2-2.fc12, which is currently in
updates-testing.

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


On 2010-01-16T17:54:20+00:00 Christopher wrote:

Fix confirmed.

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


On 2010-02-10T16:06:48+00:00 Jonathan wrote:

I've got empathy-2.8.2-2.fc12.x86_64, and I am still having this problem
this morning.  Pidgin wasn't working for me either, but I was able to
get it to work by disabling clientlogon in the advanced settings.  I
can't find that setting anywhere in empathy, so I believe this is still
an issue.

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


On 2010-02-10T22:00:35+00:00 Reinhard wrote:

I can confirm Jonathans statement for empathy-2.8.2-2.fc12.x86_64.
I receive "network connection error" for AIM as stated and for ICQ and IRC that 
were working before. Jabber (Googlemail) amd YIM are working still fine.

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


On 2010-02-11T15:25:06+00:00 Benjamin wrote:

I still see this problem with empathy-2.8.2-2.fc12.x86_64 and

[Bug 459735] Re: Evince crash opening certain PDF files

[Bug Watch Updater]

** Changed in: evince (Fedora)
   Status: Confirmed => Won't Fix

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

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

Title:
  Evince crash opening certain PDF files

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

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

[Bug 58210] Re: Unable to add tasks in calendar, get "invalid time value" when clicking save

[Bug Watch Updater]

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

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-06-03T01:47:14+00:00 Julian wrote:

Description of problem:
After upgrade from fc6, date +%c gives the following (pl_PL):
N, 3 VI 2007, 02:27:59
before, it was looking like that
nie, 3 cze 2007, 02:27:59
I think that the second format is much more readable.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/17


On 2007-09-25T14:32:23+00:00 Karol wrote:

I think the Fedora should patch the glibc because the upstream does not want to
do it.
File to patching: /localedata/locales/pl_PL (after
installation: /usr/share/i18n/locales/pl_PL ).


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/21


On 2007-09-25T14:39:58+00:00 Karol wrote:

Reasons:
- at now the abmon is archaic mothod of abbreviation
- there are problems with applications (e.g. calendar in evolution)
- now it is useless and not user-friendly
The polish experts opinion says that the previous method of abreviating days and
months IS correct in computer industry.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/22


On 2007-09-25T18:51:10+00:00 Julian wrote:

I think something like Wto, 25 Sie 2007 looks a bit better.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/23


On 2007-09-26T16:36:40+00:00 Jakub wrote:

We now have 3 different groups, each pushing a different format.
For %b wrz vs. IX vs. 9, and then various different layouts of D_T_FMT, D_FMT
and T_FMT.
If you want this changed, can you (or ask somebody else to) please organize an
internet poll among Polish Linux users, which states all the various proposed
changes and let people choose from them, then invite people in various LUGs,
distros, those commenting in the various bugzilla bugs about this, etc.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/26


On 2007-10-01T17:29:43+00:00 Karol wrote:

I organize poll http://karlik.nonlogic.org/blog/wpisy/ogolne/daty-w
-glibc-sonda .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/27


On 2007-10-14T19:01:00+00:00 Karol wrote:

There has not been a lot of interest about poll, but I think I can sum it up.
In conclusion of poll about day abbs:
# pon, wto, śro, czw, pią, sob, nie (47%, 425 Votes)
# Pn, Wt, Śr, Cz, Pt, So, Nd, (27%, 249 Votes)
# pn., wt., śr., czw., pt., sob., ndz. (10%, 95 Votes)
# PN,WT,SR,CZW,PT,SO,ND (5%, 48 Votes)
# pon., wto., śro., czw., pią., sob., nie. (4%, 38 Votes)
# Po,Wt,Śr,Czw,Pt,So,N (3%, 25 Votes)
# inna (podaj w komentarzu) (2%, 18 Votes) <= in comments are e.g. "pn, wt, śr,
cz, pt, so, nd"
# pon., wt., śr., czw., piąt., sob., niedz. (1%, 11 Votes)
Well... in the glibc should be these abbreviations:
nie
pon
wto
śro
czw
pią
sob

Abbreviations of months:
# trzy pierwsze litery (sty,lut,mar,kwi,maj,cze,lip,sie,wrz,paź,lis,gru) (81%,
519 Votes)
# rzymskie liczby (I,II,III,IV,V,VI,VII,VIII,IX,X,XI,XII) (17%, 108 Votes)
# inna zgodna z normami (podaj w komentarzu) (3%, 17 Votes)
So in the glibc should be these abbreviations:
sty
lut
mar
kwi
maj
cze
lip
sie
wrz
paź
lis
gru

The D_FMT:
# liczbowa arabska z uzupełniającym zerem (01,02…12), %d.%m.%Y, np. 01.01.1970
(62%, 528 Votes)
# z użyciem skrótów miesięcy, %d %b %Y, np. 01 I 1970, 01 sty 1970 (36%, 303 
Votes)
# inna (podaj w komentarzu) (3%, 22 Votes) <= most of these votes are for 
iso-8601
I did not organize more polls (e.g. for D_T_FMT). I think good idea is to not
change D_T_FMT (IMHO there should be change only abbs not *FMT, but I made a
poll as you wish).


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/30


On 2007-10-14T20:52:37+00:00 Ulrich wrote:

I've made changes upstream in cvs.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/31


On 2007-10-17T21:27:05+00:00 Karol wrote:

I think I can close the bug. :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/58210/comments/32

[Bug 59781] Re: When placing 1 item in the trash it shows up as 2

[Bug Watch Updater]

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

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-01-22T17:33:06+00:00 Need wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051215 
Epiphany/1.9.4

Description of problem:
The trash applet icon shows a count which is always twice the number of deleted 
items.

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


How reproducible:
Always

Steps to Reproduce:
x

Additional info:

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


On 2006-02-01T05:03:29+00:00 sangu wrote:

See Also : http://bugzilla.gnome.org/show_bug.cgi?id=325834

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


On 2006-02-20T11:22:19+00:00 Rahul wrote:


These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks

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


On 2006-02-20T11:46:19+00:00 Rahul wrote:


Unable to reproduce this on the latest rawhide. gnome-applets-2.13.4-2
Do you have the latest updates?

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


On 2006-02-20T11:54:47+00:00 Need wrote:

Ack you're right :)

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


On 2006-03-16T07:58:17+00:00 Need wrote:

Broken again.
$ rpm -q gnome-applets
gnome-applets-2.13.90-8

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


On 2006-03-27T12:37:36+00:00 Need wrote:

This is still broken for me.

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


On 2006-04-15T09:16:02+00:00 Need wrote:

This is a user facing bug, and it is still broken.

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


On 2006-09-17T11:52:08+00:00 Pavel wrote:

It seems to be an upstream bug all over distros. 
Ubuntu has it commited too :
https://launchpad.net/distros/ubuntu/+source/gnome-applets/+bug/59781

I think the bug first appeared in GNOME >=2.15.x.

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


On 2006-11-17T13:43:29+00:00 Need wrote:

WFM

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


** Changed in: gnome-applets (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/59781

Title:
  When placing 1 item in the trash it shows up as 2

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

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

[Bug 175904] Re: Firefox window moves to current workspace

[Bug Watch Updater]

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

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


On 2007-09-26T18:09:57+00:00 Bill wrote:

Description of problem:

When I open a new tab (via right click on a terminal, clicking on something in
liferea, whatever), firefox immediately jumps onto the current workspace.

This is irritating.

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

firefox-2.0.0.6-11.fc8

Additional info:

Seems related to the startup notification patch, as it worked ok in
2.0.0.6-8.fc8.

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


On 2007-10-01T00:17:03+00:00 Adam wrote:

I will second this. Very irritating!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/6


On 2007-10-01T19:22:40+00:00 Christopher wrote:

Owen says this is a metacity bug.  The following program also hops
windows.

#!/bin/env python

import gtk
import gobject
w = gtk.Window()
w.set_title("Foo")
w.show()

def on_timeout():
w.present()
return False

gobject.timeout_add(5000, on_timeout)
gtk.main()


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/7


On 2007-10-01T19:23:35+00:00 Christopher wrote:

er, hops workspaces

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/8


On 2007-10-01T19:34:29+00:00 Colin wrote:

To give some background on this issue, Firefox now supports startup 
notification:
https://bugzilla.mozilla.org/show_bug.cgi?id=223492

The issue in this bug only occurs when there are multiple workspaces.

Removing this Firefox patch would be a regression in the single workspace case
because it would require clicking on a flashing browser entry in the task list
after activating an external link.

>From IRC:

 walters: metacity could look at the window role and alter the behavior
based on that


Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/9


On 2007-10-01T19:48:25+00:00 Bill wrote:

FWIW, commenting out the call to gdk_window_focus() in the patch makes it DTRT
for me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/10


On 2007-10-01T20:00:33+00:00 Owen wrote:

Actually, what I meant was that based on the "type" of the window application
vs. dialog, you could do different things.

A application never, under any circumstances, should be moved between
desktops.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/11


On 2007-10-01T20:03:13+00:00 Colin wrote:

Bill, what effect does that have in the single-workspace case?

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


On 2007-10-01T20:04:24+00:00 Colin wrote:

Also, I've filed this bug upstream here:

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

Since there seems to be agreement this is an upstream Metacity issue, please
continue discussion there.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/13


On 2007-10-01T20:10:27+00:00 Bill wrote:

Colin: when it's on the same workspace, I get the throbbing entry in the panel.
When it's on the other workspace, I don't.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/14


On 2007-10-11T20:06:50+00:00 David wrote:

We need to fix this for F8...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/15


On 2007-10-11T21:48:48+00:00 Jeremy wrote:

This is also happening in compiz... so more than just metacity at work
here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/175904/comments/16


On 2007-10-11T23:26:44+00:00 Christopher wrote:

Jeremy: not quite...

in metacity, the _window_ switches to the current workspace.

In compiz, the _active 

[Bug 1727210] Re: Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo)

[Ernest Kudron]

libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.40 (libva )
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileNone   : VAEntrypointVideoProc

-- 
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/1727210

Title:
  Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2
  graphics × 2 (Lenovo)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1727210/+subscriptions

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

[Bug 1727210] Re: Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo)

[Ernest Kudron]

MPV will play a choppy video stream, however once open, will not close.
Had to reboot to close the player.

-- 
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/1727210

Title:
  Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2
  graphics × 2 (Lenovo)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1727210/+subscriptions

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

Re: [Bug 1727210] Re: Totum locks up with 17.10

[Ernest Kudron]

MPV will play a choppy video stream, however once open, will not close.
Had to reboot to close the player.


From: boun...@canonical.com  on behalf of Daniel van 
Vugt 
Sent: Wednesday, October 25, 2017 2:11:38 AM
To: wcr...@msn.com
Subject: [Bug 1727210] Re: Totum locks up with 17.10

and tell us if playing videos with mpv works better.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1727210

Title:
  Totum locks up with 17.10

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  when trying to play videos in Totum on AMD® E1-6010 apu with amd
  radeon r2 graphics × 2 (Lenovo), the timer shows it's playing but
  there is no video. After about 10 seconds I get the "Video is not
  responding" "what do you want to do" "wait/force close" window. the
  only way to close it is to force it closed. Same result with MP4 and
  FLV videos.

  totum version= 3.26.0-0ubuntu1

  Ubuntu 17.10

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

-- 
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/1727210

Title:
  Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2
  graphics × 2 (Lenovo)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1727210/+subscriptions

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

[Bug 1728172] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1728172/+attachment/4998364/+files/ThreadStacktrace.txt

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

** Changed in: gnome-control-center (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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1728172

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

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

[Bug 1728172] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1728172/+attachment/4998363/+files/StacktraceSource.txt

-- 
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/1728172

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

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

[Bug 1728172] gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

[Apport retracing service]

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x556f547c8790, 
iface_type=93936654741120) at ../../../../gobject/gtype.c:4057
 ext_ubuntu_dock_placement_changed_callback (settings=, 
key=, user_data=) at cc-ubuntu-panel.c:258
 g_closure_invoke (closure=0x556f54703100, return_value=0x0, n_param_values=2, 
param_values=0x7ffd9dcc9c60, invocation_hint=0x7ffd9dcc9be0) at 
../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x556f53f95a00, 
detail=detail@entry=4427, instance=instance@entry=0x556f544e7700, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7ffd9dcc9c60) at 
../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x556f544e7700, signal_id=, 
detail=4427, var_args=var_args@entry=0x7ffd9dcc9e30) at 
../../../../gobject/gsignal.c:3391

-- 
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/1728172

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

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

[Bug 1728172] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1728172/+attachment/4998362/+files/Stacktrace.txt

-- 
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/1728172

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

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

[Bug 1727980] Re: gdm after suspend loginscreen has wrong keyboard layout

[Gunnar Hjalmarsson]

On 2017-10-27 14:36, Sven wrote:
> So maybe it's not a bug, but the request for a possibility to
> configure keyboard layout for everything in one place.

Actually there is such a place:

Settings -> Region & Language

>From there you can add and remove "input sources" for your user.

If you click the "Login Screen" button at the top right of the window,
you can do the same thing system wide (i.e. changing input sources in
that mode will make changes to /etc/default/keyboard).

> Nope... now, an hour later, the config seems to be totally broken...
> now all my login screens have us layout...

That's not good. To determine if this really is a bug, we'd need a
reproducible step-by-step case.

I'd advise you to make use of the GUI mentioned above. Change things
back and forth a couple of times, to make sure that everything is in
sync, and then reboot.

Please let us know if that makes a difference.

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

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

Title:
  gdm after suspend loginscreen has wrong keyboard layout

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

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

[Bug 1728172] [NEW] gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

[Michal Pasniewski]

Public bug reported:

Crash when changing docking or monitor settings.  I have 3 identical
monitors and I am trying to order them properly (horizontally).

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
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 19:38:18 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-10-27 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fce64b5bde2 :  mov
(%rdi),%rbp
 PC (0x7fce64b5bde2) ok
 source "(%rdi)" (0x6000e2c49100080) not located in a known VMA region (needed 
readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash artful need-amd64-retrace 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1728172

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

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

[Bug 823467] Re: [Latitude 2120] bluetooth is disabled after suspend/resume

[Bug Watch Updater]

** Changed in: fedora
   Status: Unknown => Invalid

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

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

Title:
  [Latitude 2120] bluetooth is disabled after suspend/resume

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

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

[Bug 797947] Re: gnome-settings-daemon crashes frequently with X protocol error

[Bug Watch Updater]

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

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


On 2011-06-16T15:09:01+00:00 Red wrote:

This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: /usr/libexec/gnome-settings-daemon
comment: I'm running cgroups. Basically the NX user has it's own cgroup, and 
then when another use logs in, they are also put into their own cgroup. I think 
this is more of my issue that w/ the code...
component: gnome-settings-daemon
executable: /usr/libexec/gnome-settings-daemon
kernel: 2.6.32-131.2.1.el6.x86_64
package: gnome-settings-daemon-2.28.2-11.el6
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 
(SIGABRT)
release: Red Hat Enterprise Linux Server release 6.1 (Santiago)
reproduce: 1. Login to server using neatx
2. Crash happens everytime
3.

time: 1308236671
uid: 501
backtrace: warning: core file may not match specified executable file.
[New Thread 5103]
[New Thread 5111]
[Thread debugging using libthread_db enabled]
Core was generated by `/usr/libexec/gnome-settings-daemon'.
Program terminated with signal 6, Aborted.
#0  0x003437832a45 in raise () from /lib64/libc.so.6

Thread 2 (Thread 0x7fa19012f700 (LWP 5111)):
#0  0x00343840e56d in read () from /lib64/libpthread.so.0
No symbol table info available.
#1  0x003437439fdb in ?? () from /lib64/libglib-2.0.so.0
No symbol table info available.
#2  0x003437462074 in ?? () from /lib64/libglib-2.0.so.0
No symbol table info available.
#3  0x0034384077e1 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#4  0x0034378e68ed in clone () from /lib64/libc.so.6
No symbol table info available.

Thread 1 (Thread 0x7fa19095a8e0 (LWP 5103)):
#0  0x003437832a45 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x003437834225 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x00343744337a in g_logv () from /lib64/libglib-2.0.so.0
No symbol table info available.
#3  0x003437443413 in g_log () from /lib64/libglib-2.0.so.0
No symbol table info available.
#4  0x003440868196 in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
No symbol table info available.
#5  0x7fa18e456681 in xkl_process_error () from /usr/lib64/libxklavier.so.15
No symbol table info available.
#6  0x00343a846b24 in _XError () from /usr/lib64/libX11.so.6
No symbol table info available.
#7  0x00343a84cf2c in ?? () from /usr/lib64/libX11.so.6
No symbol table info available.
#8  0x00343a84d5c0 in _XReply () from /usr/lib64/libX11.so.6
No symbol table info available.
#9  0x00343a82ae58 in _XGetWindowAttributes () from /usr/lib64/libX11.so.6
No symbol table info available.
#10 0x00343a82aff1 in XGetWindowAttributes () from /usr/lib64/libX11.so.6
No symbol table info available.
#11 0x7fa18e45611c in xkl_engine_select_input_merging () from 
/usr/lib64/libxklavier.so.15
No symbol table info available.
#12 0x7fa18e4561c5 in xkl_engine_resume_listen () from 
/usr/lib64/libxklavier.so.15
No symbol table info available.
#13 0x7fa18e456201 in xkl_engine_start_listen () from 
/usr/lib64/libxklavier.so.15
No symbol table info available.
#14 0x7fa18ec84bd2 in gsd_keyboard_xkb_init () from 
/usr/lib64/gnome-settings-daemon-2.0/libkeyboard.so
No symbol table info available.
#15 0x7fa18ec83af1 in ?? () from 
/usr/lib64/gnome-settings-daemon-2.0/libkeyboard.so
No symbol table info available.
#16 0x003437438f0e in g_main_context_dispatch () from 
/lib64/libglib-2.0.so.0
No symbol table info available.
#17 0x00343743c938 in ?? () from /lib64/libglib-2.0.so.0
No symbol table info available.
#18 0x00343743cd55 in g_main_loop_run () from /lib64/libglib-2.0.so.0
No symbol table info available.
#19 0x00343fd4c2c7 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0
No symbol table info available.
#20 0x004043d5 in main ()
No symbol table info available.
>FromTo  Syms Read   Shared Object Library
0x00343fc66280  0x00343ff030d8  Yes (*) 
/usr/lib64/libgtk-x11-2.0.so.0
0x00344081cff0  0x00344087eb88  Yes (*) 
/usr/lib64/libgdk-x11-2.0.so.0
0x00343f0092f0  0x00343f014908  Yes (*) /usr/lib64/libatk-1.0.so.0
0x00343ac189a0  0x00343ac7aca8  Yes (*) /lib64/libgio-2.0.so.0
0x003440407330  0x003440421048  Yes (*) 
/usr/lib64/libpangoft2-1.0.so.0
0x00343ec05780  0x00343ec17718  Yes (*) 
/usr/lib64/libgdk_pixbuf-2.0.so.0
0x0034410048b0  0x0034410093d8  Yes (*) 
/usr/lib64/libpangocairo-1.0.so.0
0x003440c09c50  0x003440c5b008  Yes (*) /usr/lib64/libcairo.so.2

[Bug 816762] Re: gnome-shell Alt+F2 can’t run anything

[Bug Watch Updater]

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

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


On 2011-07-07T16:14:21+00:00 Adam wrote:

In current Rawhide (Shell 3.1.3), the alt-f2 run dialog is broken:
anything you enter comes up as "command not found".

(Also, I was just testing to see what would happen if I specified an
explicit path, and that's fun: I entered '/usr/bin/gnome-terminal' , and
it got stuck with the 'Please enter a command:' dialog displayed and the
rest of the interface part-greyed-out...)

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


On 2011-08-05T20:10:50+00:00 Jeremy wrote:

Reported at https://bugzilla.gnome.org/show_bug.cgi?id=656054

Confirmed with version 3.1.3 and 3.1.4 on Ubuntu development & Fedora
16.

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


On 2013-04-03T16:37:16+00:00 Fedora wrote:

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

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

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

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


On 2014-12-05T15:19:40+00:00 Ryan wrote:

Closing this one, as the alt+f2 run dialog works correctly in current
versions of Fedora.

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


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

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

-- 
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/816762

Title:
  gnome-shell Alt+F2 can’t run anything

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

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

[Bug 824144] Re: [EeePC 1001 PXD] suspend/resume kills bluetooth

[Bug Watch Updater]

** Changed in: fedora
   Status: Unknown => Invalid

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

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

Title:
  [EeePC 1001 PXD] suspend/resume kills bluetooth

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

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

[Bug 881664] Re: "Share My Desktop" doesn't work with XMPP in 11.10

[Bug Watch Updater]

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

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


On 2011-06-04T18:04:26+00:00 David wrote:

Created attachment 502998
telepathy-gabble log from sender

Description of problem:
I have tried to share desktop with my friend. We both have Jabber account on 
the same server. The remote desktop request is not received on the other side.


Version-Release number of selected component (if applicable):
Empathy 3.0.1 -> Empathy 3.0.2
Empathy 3.0.2 -> Empathy 3.0.2


How reproducible:
Always if versions match above-mentioned.


Steps to Reproduce:
1. Connect to Jabber account via Empathy
2. Select contact, who is connected via Empathy
3. Share your desktop
  
Actual results:
Remote desktop request is not shown on the other side. Impossible to share 
desktop.


Expected results:
Remote desktop request is shown on the other side. When accepted, Vinagre 
should handle remote desktop invitation.


Additional info:
Works when following versions are used:
2.32.1 (person who shares desktop)
3.0.2 (person who receives remote desktop invitation)
Does not work in reversed order.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/881664/comments/0


On 2012-03-02T19:52:08+00:00 Yul wrote:

I can confirm this problem. I used to help my mum with this feature and
it's very bad that it stopped working. Please notify me, if you need any
further information. Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/881664/comments/15


On 2012-08-06T20:00:37+00:00 Fedora wrote:

This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/881664/comments/16


On 2012-08-06T20:01:20+00:00 Fedora wrote:

This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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

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

Reply at:

[Bug 1719797] Re: Firmware update seemingly not working

[Bug Watch Updater]

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

** Changed in: gnome-software
   Importance: Unknown => Medium

-- 
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/1719797

Title:
  Firmware update seemingly not working

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

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

[Bug 1728077] Re: Evince uses wrong encoding when filling out a PDF form

[Bug Watch Updater]

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

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

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

Title:
  Evince uses wrong encoding when filling out a PDF form

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

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

[Bug 1725347] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

[Andrew Moreland]

I have this issue on Ubuntu 17.10, same exact segfault message. Happens
every time I try to execute the program. Using an nvidia 1050 ti with
the 387.12 NVIDIA binary drivers selected from "Additional Drivers"
under "software and updates".

-- 
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/1725347

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/1725347/+subscriptions

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

[Bug 1725347] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

[Andrew Moreland]

If it is relevant, I am using an AMD ryzen processor.

-- 
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/1725347

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/1725347/+subscriptions

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

[Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

[Norbert]

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

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

-- 
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/1728157

Title:
  Unable to open files from MTP-device: : Input/output error

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

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

[Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

[Norbert]

Same problems on Ubuntu 17.10.

** Description changed:

  Steps to reproduce:
  1. Connect MTP-device to laptop
  2. Caja file browser opens
  3. Navigate to the needed file on MTP-device with Caja
  
  4a. Try to open text file with Pluma from Caja or from terminal:
  Unexpected error: libmtp error: Unknown error.
  
  4b. Try to open text file with `cat`:
  
  $ cat /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/file.txt
  cat: '/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/file.txt': 
Input/output error
  
  4c. Try to open video file with `vlc` from Caja or from terminal:
  
  $ vlc /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-
  card/video.mkv
  
  VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
  [00daa088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [7f00c4000f48] filesystem access error: read error: Input/output error
  [7f00c4001408] core stream error: cannot pre fill buffer
  
  4d. Try to open Markdown file with ReText from Caja or from terminal:
  Retext opens with empty document
  
  4e. Try to open docx-file with LibreOffice from Caja or from terminal:
- General input/output error while accessing 
/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/document.docx.
+ get error window with text "General input/output error while accessing 
/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/document.docx."
  
+ 4f. Try to open ppt, pptx, xls, xlsx, odp, odt, or doc-file with LibreOffice 
from Caja or from terminal:
+ get error window with text "General Error.
+ The seek operation could not be run." 
+ or empty document
+ 
+ 4g. Try to open png- or jpg- image file with Eye of MATE from Caja or from 
terminal:
+ "libmtp error: Unknown error."
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 28 00:35:42 2017
  InstallationDate: Installed on 2014-02-07 (1358 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (194 days ago)

** Tags added: artful

-- 
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/1728157

Title:
  Unable to open files from MTP-device: : Input/output error

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

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

[Bug 305695] Re: Jaunty doesnt allow screenshots getting "No command 33 has been defined" error with printscreen

[Bug Watch Updater]

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

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-04T18:23:03+00:00 Christopher wrote:

Description of problem: Hitting the 'Print Screen' key on my keyboard
results in a Metacity popup box that says "No command 33 has been
defined."


Version-Release number of selected component (if applicable):
metacity-2.25.34-1.fc11
also occurs in metacity-2.25.8-4.fc11

How reproducible:
every time

Actual results:
pop up box with warning

Expected results:
should take me to the screen shot window

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/0


On 2008-12-22T17:30:58+00:00 Tom wrote:

Annoyingly, I also get this with the "up" arrow on my Lenovo T60.

metacity-2.25.55-1.fc11.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/12


On 2008-12-22T19:56:04+00:00 Tom wrote:

(In reply to comment #1)
> Annoyingly, I also get this with the "up" arrow on my Lenovo T60.
> 
> metacity-2.25.55-1.fc11.x86_64

Reverting to metacity-2.25.34-1.fc11 fixes it.

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


On 2008-12-22T23:13:22+00:00 John wrote:

Reverting to metacity-2.25.34-1.fc11.x86_64 didn't work for me.


All my "inverted T" arrow keys are broken, but just "Up" opens the "No command 
33 ..." message.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/14


On 2008-12-23T03:09:27+00:00 Tom wrote:

(In reply to comment #3)
> Reverting to metacity-2.25.34-1.fc11.x86_64 didn't work for me.
> 
> 
> All my "inverted T" arrow keys are broken, but just "Up" opens the "No command
> 33 ..." message.

I had to kill the running metacity process after doing the rpm
downgrade, to start the old one.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/15


On 2008-12-23T03:55:24+00:00 John wrote:

Weird.   I tried again:  After downgrading the rpm and leaving X I looked for 
any running metacity processes, there weren't any.  To be sure, I rebooted, but
metacity-2.25.34-1.fc11.x86_64 still gives me "No command 33" for "Up" 
arrow.
As does metacity-2.25.55-1.fc11.x86_64.

I have a Logitech USB keyboard which is being recognized as a "BTC USB
Multimedia Keyboard"   Does that sound right?

(II) XINPUT: Adding extended input device "BTC USB Multimedia Keyboard" (type: K
EYBOARD)
(**) Option "xkb_rules" "evdev"
(**) BTC USB Multimedia Keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "pc105+inet"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/16


On 2008-12-23T03:57:57+00:00 John wrote:

My arrow keys are being recognized normally by bash in a ctrl-alt-2
console.

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


On 2008-12-24T15:24:27+00:00 John wrote:

Seems to be fixed today!?!  Still using metacity-2.25.55-1.fc11.x86_64
Perhaps this was fixed by the Xorg-x11-server updates?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/18


On 2008-12-24T15:44:55+00:00 Yanko wrote:

Created attachment 327820
Re-add some missing defaults

The xorg update would have fixed the up arrow problem. I don't think the
command 33 issue here is related. I think this patch will fix it, at
least temporarily until upstream figures what to do about it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/19


On 2009-06-09T10:07:35+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/305695/comments/25


On 2009-09-10T12:29:48+00:00 Yanko wrote:

The missing defaults bug that was the problem here was fixed sometime
between 

[Bug 1725457] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

[Simon P.]

The reason for my crashes of Rhythmbox seems to be the alternative
appearance extension. With the extension disabled in the program
settings I cannot reproduce those crashes.

** Package changed: rhythmbox (Ubuntu) => rhythmbox-plugin-alternative-
toolbar (Ubuntu)

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1725457/+subscriptions

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

[Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

[Norbert]

** Description changed:

  Steps to reproduce:
  1. Connect MTP-device to laptop
  2. Caja file browser opens
  3. Navigate to the needed file on MTP-device with Caja
  
  4a. Try to open text file with Pluma from Caja or from terminal:
  Unexpected error: libmtp error: Unknown error.
  
  4b. Try to open text file with `cat`:
  
- $ cat /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/file.txt 
+ $ cat /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/file.txt
  cat: '/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/file.txt': 
Input/output error
  
  4c. Try to open video file with `vlc` from Caja or from terminal:
  
- $ vlc /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/video.mkv
-  
+ $ vlc /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-
+ card/video.mkv
+ 
  VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
  [00daa088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [7f00c4000f48] filesystem access error: read error: Input/output error
  [7f00c4001408] core stream error: cannot pre fill buffer
+ 
+ 4d. Try to open Markdown file with ReText from Caja or from terminal:
+ Retext opens with empty document
+ 
+ 4e. Try to open docx-file with LibreOffice from Caja or from terminal:
+ General input/output error while accessing 
/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/document.docx.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 28 00:35:42 2017
  InstallationDate: Installed on 2014-02-07 (1358 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (194 days ago)

-- 
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/1728157

Title:
  Unable to open files from MTP-device: : Input/output error

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

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

[Bug 234875] Re: cannot import thunderbird mbox

[Bug Watch Updater]

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

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


On 2008-09-04T09:03:45+00:00 Frank wrote:

Description of problem: Feature-Request
Cannot import settings from Thunderbird

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


How reproducible: always


Steps to Reproduce:
1. Click Import
2. Follow Steps
3. No Thunderbird found
  
Actual results:
No program found

Expected results:
Thunderbird Imported.

Additional info: Have been using tb while bug-hunting Evo, lots of filters in 
t\b.
Importing would be good as tb\evo often used on Fedora.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/234875/comments/7


On 2008-09-04T09:25:22+00:00 Milan wrote:

Moving this upstream, it would be really better to have such thing in
upstream version, than in Fedora version only. The bug I found partially
fit to this, I believe extending it to general import from tb would
appreciate that reporter too, as he mentioned it there as well.

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/234875/comments/8


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

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

Title:
  cannot import thunderbird mbox

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

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

[Bug 60959] Re: Nautilus and Dbus errors

[Bug Watch Updater]

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

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-09-19T15:17:44+00:00 Daniel wrote:

Description of problem:
If an application displays a GTK FileChooserDialog dialog when there is no DBus
daemon available it ends up trying to use a NULL DBus connection violating DBus
assertions. Fortunately our DBus builds have assertion checking enabled, if this
were turned off the app would likely trigger SEGV deferencing a null pointer.

(vfsdbus.py:3756): libgnomevfs-WARNING **: Failed to open session DBUS
connection: Unable to determine the address of the message bus (try 'man
dbus-launch' and 'man dbus-daemon' for help)
Volume monitoring will not work.
3756: arguments to dbus_connection_send_with_reply_and_block() were incorrect,
assertion "connection != NULL" failed in file dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.
3756: arguments to dbus_connection_send_with_reply_and_block() were incorrect,
assertion "connection != NULL" failed in file dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.


This can be reproduced with the following PyGTK code:

$ cat > vfsdemo.py  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/60959

Title:
  Nautilus and Dbus errors

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

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

[Bug 436188] Re: gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL)

[Bug Watch Updater]

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

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-29T11:50:56+00:00 Bevis wrote:

Description of problem:
When starting a gnome-terminal on a remote host with all X11/TCP infrastructure 
code including CORBA via IPv4 enabled (other apps work fine), the 
gnome-terminal gets a glibc double free error and crashes...

rsh willow gnome-terminal --display $DISPLAY
**
ERROR:terminal-app.c:1525:terminal_app_init: assertion failed: 
(app->default_profile_id != NULL)
*** glibc detected *** gnome-terminal: double free or corruption (out): 
0x0178c0e0 ***

and then hangs...

Other X applications work fine.

Version-Release number of selected component (if applicable):
gnome-terminal-2.24.1-2.fc10.x86_64

How reproducible:
every time

Steps to Reproduce:
1. Enable X11/TCP mode and xauth on NFS - restart GDM/X server
2. Enable ORBIOPIPv4 in /etc/orbitrc
3. Login into GNOME session on Workstation
4. xauth list - take value and xauth -f .Xauthority add with the 
details
5. Enable rsh-server on the file server machine on the local network
6. Test rsh is working (.rhosts etc)
7. Run:  rsh fileserver gnome-terminal --display $DISPLAY
  
Actual results:
Gnome terminal crashes with assertion failure.

Expected results:
Gnome terminal starts on fileserver displaying via X11/TCP

Additional info:
Local network is secure - TCP/X11 tunnelling and SSH is totally unnecessary and 
over the top and produces significant latency and consumes ptys.

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


On 2008-11-30T10:06:50+00:00 Bevis wrote:

This also happens if you login via ssh and try to start gnome-terminal
from the command line like so:

willow% gnome-terminal --display cyane:0 &
[1] 13791
willow% **
ERROR:terminal-app.c:1525:terminal_app_init: assertion failed: 
(app->default_profile_id != NULL)

[1]Abort gnome-terminal --display cyane:0
willow%

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


On 2009-01-21T18:30:25+00:00 George wrote:

I'm getting the same failure when starting gnome-terminal from the GNOME
panel or command line of an existing gnome-terminal.  I have no idea why
I was able to start gnome-terminals then it stopped.  I've seen this in
several login sessions.  I've had to put xterm on the panel as a backup.

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


On 2009-09-28T13:33:08+00:00 Paul wrote:

https://launchpad.net/bugs/436188 + dups, although this was allegedly
fixed before at https://launchpad.net/bugs/298426

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


On 2009-11-18T09:04:04+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/gnome-
terminal/+bug/436188/comments/17


On 2009-11-18T13:50:08+00:00 Paul wrote:

AFAIK, this is still current;  it is 

[Bug 13729] Re: [kernel] CD-RW erasing fails on QSI drives

[Bug Watch Updater]

** Changed in: cdrtools (Fedora)
   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/13729

Title:
  [kernel] CD-RW erasing fails on QSI drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/cdrecord/+bug/13729/+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

[Bug Watch Updater]

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

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


On 2013-09-04T12:08:32+00:00 Alex wrote:

Description of problem:
If Russian xkb layout is active, it's impossible to use keyboard shortcuts in 
non-gtk programs.

Version-Release number of selected component (if applicable):
Gnome Shell - 3.8.4-2.fc19 
GTK: gtk3 - 3.8.4-1.fc19

How reproducible:
always

Steps to Reproduce:
0. Login with gnome-shell
1. Start blender
2. Switch keyboard layout to russian
3. Press hotkey 's' to resize default cube

Actual results:
Nothing will happen

Expected results:
Resize default cube

Additional info:

Hotkeys in russian layout works with gtk-programs, like:
Geany, Gedit, Gnome Terminal, Transmission.

And don't work with any non-gtk programs, like:
LibreOffice, blender, psi, QBittorrent.

It's a gnome problem. If login in KDE - then hotkeys in russian layout
works fine.

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/24


On 2013-12-24T09:22:20+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/149


On 2014-11-04T11:25:27+00:00 Sam wrote:

This bug appears to still exist in Fedora 20 with Gnome 3. Tested with
Hebrew.

Try adding a new Hebrew keyboard layout, opening apps like Caligra,
Kate, LibreOffice, and using Keyboard shortcuts like copy and paste.

For the KDE apps, could this be due to using an unpatched version of Qt
where related bugs still exist? What is the likely cause in LibreOffice?
Independent of this bug?
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=41169

Also related: https://bugs.launchpad.net/unity/+bug/1226962

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/256


On 2015-01-09T19:43:16+00:00 Fedora wrote:

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

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/263


On 2015-02-16T19:52:17+00:00 Alexander wrote:

Still exists in Fedora 21. KDE apps (Konversation, Digikam, ..) don't
respond to shortcuts, even in English keyboard layout when GNOME shell
is in use.

Reply at: https://bugs.launchpad.net/unity/+bug/1226962/comments/264


On 2015-11-04T13:35:50+00:00 Fedora wrote:

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora  'version'
of '21'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible 

[Bug 1728157] [NEW] Unable to open files from MTP-device: : Input/output error

[Norbert]

Public bug reported:

Steps to reproduce:
1. Connect MTP-device to laptop
2. Caja file browser opens
3. Navigate to the needed file on MTP-device with Caja

4a. Try to open text file with Pluma from Caja or from terminal:
Unexpected error: libmtp error: Unknown error.

4b. Try to open text file with `cat`:

$ cat /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/file.txt
cat: '/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/file.txt': 
Input/output error

4c. Try to open video file with `vlc` from Caja or from terminal:

$ vlc /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-
card/video.mkv

VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
[00daa088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
[7f00c4000f48] filesystem access error: read error: Input/output error
[7f00c4001408] core stream error: cannot pre fill buffer

4d. Try to open Markdown file with ReText from Caja or from terminal:
Retext opens with empty document

4e. Try to open docx-file with LibreOffice from Caja or from terminal:
General input/output error while accessing 
/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/document.docx.


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Oct 28 00:35:42 2017
InstallationDate: Installed on 2014-02-07 (1358 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
SourcePackage: gvfs
UpgradeStatus: Upgraded to xenial on 2017-04-15 (194 days ago)

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


** Tags: amd64 apport-bug xenial

-- 
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/1728157

Title:
  Unable to open files from MTP-device: : Input/output error

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

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

[Bug 1719797] Re: Firmware update seemingly not working

[Mario Limonciello]

I've filed that issue upstream.

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

** Also affects: gnome-software via
   https://bugzilla.gnome.org/show_bug.cgi?id=789574
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-software (Ubuntu)
   Status: New => Triaged

-- 
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/1719797

Title:
  Firmware update seemingly not working

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

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

[Bug 1719797] Re: Firmware update seemingly not working

[Mario Limonciello]

I suspect it to actually be gnome-session is the problem, but let's see
what they say.

-- 
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/1719797

Title:
  Firmware update seemingly not working

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

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

[Bug 1694076] Re: No error message on firmware update fail

[Mario Limonciello]

FYI:
Fixed in 3.26 branch here: 
https://git.gnome.org/browse/gnome-software/commit/src/gs-shell.c?h=gnome-3-26=4b1f50c2cee422c2f12c3ca84004082329490106

-- 
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/1694076

Title:
  No error message on firmware update fail

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

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

[Bug 1719797] Re: Firmware update seemingly not working

[Mario Limonciello]

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

** No longer affects: fwupd (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/1719797

Title:
  Firmware update seemingly not working

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

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

[Bug 1727168] Re: Only use a header bar in GNOME shell

[blue239]

Tested patched version of Nautilus and expected behavior of the menubar
is working.

But there is another type of possible small bug under "unity-session" for 
Nautilus.
When the first opened instance of Nautilus is on Home folder and you try to 
open a second instance with the middle click on the Nautilus icon, nothing 
happens.

Under "ubuntu-session" there is no such deviation - another Nautilus instance is
normally opened with the middle click no matter first one being opened at the 
Home folder.

Under "unity-session" with the first instance being opened on the Home folder,  
second instance can 
be repeatedly opened only in two ways:
- by right clik on Nautilus icon and selecting something from context menu
- when the first open instance is opened in any other folder than Home, midlle 
click
  opens second instance of Nautilus normally

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

Title:
  Only use a header bar in GNOME shell

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

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

[Bug 327793] Re: Window decorations in title bar missing with compiz enabled

[Bug Watch Updater]

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

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-08T20:33:31+00:00 David wrote:

Created attachment 331253
blanktitlebars.png

Started happening recently, but I'm not sure if it's a gnome component
or compiz.  I have compiz-0.7.8-12.fc11.x86_64 installed.  rawhide is
current on my system except for the kernel.

Windows are working.  The close, maximize, and minimize buttons all
work, but the title bars are all grey.

Attaching a screen shot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/0


On 2009-02-10T18:15:24+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.

Could you please also try to run without any /etc/X11/xorg.conf (if you
have one) whatsoever and let X11 autodetect your display and video card?
Attach to this bug /var/log/Xorg.0.log from this attempt as well,
please.

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/compiz/+bug/327793/comments/1


On 2009-02-10T19:18:53+00:00 David wrote:

Created attachment 331453
Xorg.0.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/2


On 2009-02-10T19:19:13+00:00 David wrote:

Created attachment 331454
Xorg.1.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/3


On 2009-02-10T19:19:35+00:00 David wrote:

Created attachment 331455
Xorg.3.org

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/4


On 2009-02-10T19:19:57+00:00 David wrote:

Created attachment 331456
Xorg.2.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/5


On 2009-02-10T19:20:20+00:00 David wrote:

Created attachment 331457
Xorg.4.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/6


On 2009-02-10T19:20:40+00:00 David wrote:

Created attachment 331458
Xorg.5.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/7


On 2009-02-10T19:21:54+00:00 David wrote:

I have no xorg.conf.  Attaching all of the Xorg.?.log files that I have.

I disabled desktop effects and title bars are back, for whatever that's
worth.

Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/8


On 2009-02-14T11:48:49+00:00 sangu wrote:

~/.xsession-errors

(gtk-window-decorator:6648): metacity-CRITICAL **: 
meta_frame_style_draw_with_style: assertion `style_gtk->colormap == 
gdk_drawable_get_colormap (drawable)' failed
(gtk-window-decorator:6648): metacity-CRITICAL **: 
meta_frame_style_draw_with_style: assertion `style_gtk->colormap == 
gdk_drawable_get_colormap (drawable)' failed
...

Temporary solution
Use /apps/gwd/use_metacity_theme.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/327793/comments/29


On 2009-06-09T11:08:43+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/compiz/+bug/327793/comments/37


On 2009-11-05T18:21:50+00:00 Matěj wrote:

Since this bugzilla report was filed, there have been several major
updates in various components of the Xorg system, which may have
resolved this issue. Users who have experienced this problem are
encouraged 

[Bug 522639] Re: gnome-settings-daemon crashed with SIGSEGV in gnome_bg_draw()

[Bug Watch Updater]

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

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-04T20:17:16+00:00 Arnaud wrote:

abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: /usr/libexec/gnome-settings-daemon
component: gnome-settings-daemon
executable: /usr/libexec/gnome-settings-daemon
kernel: 2.6.31.9-174.fc12.x86_64
package: gnome-settings-daemon-2.28.1-10.fc12
rating: 4
reason: Process was terminated by signal 11

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


On 2010-01-04T20:17:19+00:00 Arnaud wrote:

Created attachment 381629
File: backtrace

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


On 2010-01-05T00:08:49+00:00 Matthias wrote:

Crash in gnome-desktop

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


On 2010-01-05T01:18:05+00:00 Matthias wrote:

I think we probably need to ensure that rect is entirely contained in
the pixbuf extents, in pixbuf_draw_gradient

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


On 2010-01-05T01:19:16+00:00 Matthias wrote:

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

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


On 2010-01-05T01:22:20+00:00 Matthias wrote:

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

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


On 2010-01-07T07:44:39+00:00 Petr wrote:

I've noticed that since the crash gnome-settings-daemon does not
start (crashes each time) when I log in (e.g. fonts in gnome-panel
& nautils are weirdly huge). Relatively quick workaround is to
open the "Change desktop background" dialog (settings daemon is
launched) and restart nautilus.

Before the first crash it was all OK. Any idea which settings
cause these crashes? Can I do some quick cleanup which could help
me to get rid of this?

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


On 2010-01-07T13:29:33+00:00 Matthias wrote:

run it under gdb and see where it crashes ?

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


On 2010-01-07T14:03:24+00:00 Petr wrote:

I've already submitted the backtrace to my original bug:

https://bugzilla.redhat.com/attachment.cgi?id=381534=edit

It fails in the pixbuf_draw_gradient you mention in comment #3.
Sorry, I don't know any details about what this function does, so
I'm not able to figure our what setting could cause these crashes.

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


On 2010-01-07T15:19:27+00:00 Matthias wrote:

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

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


On 2010-01-07T15:38:39+00:00 Matthias wrote:

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

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


On 2010-01-12T23:49:02+00:00 Fedora wrote:

gnome-desktop-2.28.2-3.fc12 has been pushed to the Fedora 12 testing 
repository.  If problems still persist, please make note of it in this bug 
report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gnome-desktop'.  You can 
provide feedback for this update here: 
http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0469

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


On 2010-01-14T01:20:32+00:00 Fedora wrote:

gnome-desktop-2.28.2-3.fc12 has been pushed to the Fedora 12 stable
repository.  If problems 

[Bug 780109] Re: [regression] Page#+Enter shortcut not working

[Bug Watch Updater]

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

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


On 2011-02-03T22:04:17+00:00 Marcus wrote:

Description of problem:
When in presentation mode typing a number for jumping to that page doesn't work.

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

Steps to Reproduce:
1. Open a document in evince
2. Start presentation mode
3. Type a number to jump to that page
  
Actual results:
nothing happens

Expected results:
Evince should jump to the page number you typed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/780109/comments/0


On 2011-05-02T19:21:45+00:00 Marcus wrote:

This still doesn't work for me in Evince 3.0.0 ...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/780109/comments/1


On 2011-08-16T10:52:14+00:00 Marek wrote:

Hi,

this bug has been fixed in evince-3.0.2. I'm closing this.

Regards

Marek

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/780109/comments/8


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

** Changed in: evince (Fedora)
   Importance: Unknown => Undecided

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

Title:
  [regression] Page#+Enter shortcut not working

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

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

[Bug 1714821] Re: Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-control-center/ubuntu

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

Title:
  Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)

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

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

[Bug 1714821] Re: Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)

[Jeremy Bicha]

** Description changed:

  Please sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)
  
  The version of gnome-user-share currently in Ubuntu has 2 features:
  Bluetooth and WebDav.
  
  Ubuntu has installed gnome-user-share by default for many years so that
  sending and receiving files over Bluetooth works. That feature is now
  rovided by gnome-bluetooth and gnome-control-center. Therefore, the new
  version of gnome-user-share dropped the Bluetooth feature.
  
  Ubuntu has delayed packaging a newer version of gnome-user-share because it
  was using unity-control-center which did not support the new Bluetooth 
feature.
  
  Ubuntu has one long-standing diff from Debian. Ubuntu's gnome-user-share
  package does not actually include the apache dependencies needed for the
  WebDav feature to work (LP: #536766). Since that's now the only feature in
  gnome-user-share, dropping this diff makes sense.
  
  $ reverse-depends gnome-user-share
  Reverse-Recommends
  ==
  * cinnamon-desktop-environment
  * gnome-control-center
  
  Reverse-Depends
  ===
  * gnome-core [amd64 arm64 armhf i386 ppc64el]
  * ubuntu-budgie-desktop [amd64 arm64 armhf i386 ppc64el]
  * ubuntu-gnome-desktop [amd64 arm64 armhf i386 ppc64el]
  
  Step 1
  --
  Ubuntu and Ubuntu Budgie both use gnome-control-center so gnome-user-share is 
unused for Bluetooth.
  
  a. Drop the dependency on gnome-user-share from at least
  gnome-control-center
- ubuntu-budgie-desktop
- 
- But we might need to drop the dependency everywhere until after 18.04
- LTS for 1.c. to work.
  
  b. Demote gnome-user-share to universe.
- 
- c. Have ubuntu-release-upgrader remove gnome-user-share on upgrades.
  
  Step 2
  --
  Sync gnome-user-share from Debian.
- 
- I believe we want to do Step 1 for Ubuntu 17.10 "artful".
  
  The complication for Step 2 is that upgraders will get Apache installed
  unless they upgrade using update-manager/do-release-upgrade
  
  Therefore, I recommend delaying Step 2 until 18.04 development opens.
  
  Explanation of the Ubuntu delta and why it can be dropped:
    * Add git_add_systemd_service.patch:
  - Backport commit from 3.22 to add systemd user service file for
    compatibility with gnome-settings-daemon 3.22
    * debian/control.in:
  - Build-Depend on systemd
    * d/p/0004-revert-remove-help.patch: Bring back the help files
  for users of gnome-file-share-properties (LP: #1570230)
    * debian/patches: 0001-revert-remove-preferences-application.patch
  Fix launching of Prefences from nautilus share bar under unity and
  patch infobar color (LP: #1562515)
    * maintscript: remove old xdg autostart file (lp: #1526894)
    * New Upstream release (LP: #1518813)
    * Merge with Debian, Remaining changes:
  - Suggests the apache2.2-bin and libapache2-mod-dnssd binaries rather than
    depends on those, we want obex push to work out of the box but we don't
    really need webdav and the apache binaries on the default installation.
  - debian/patches:
    + 0001-revert-remove-preferences-application.patch
  0002-revert-data-get-started-by-gsd-sharing.patch
  0003-revert-webdav-fix-launching-server.patch:
   Bring back the preferences app for Unity and modify to allow g-s-d 
sharing
   panel to also work
    + 01_notification.patch: Display an alert box instead of a notification
  for files received.
  - debian/rules:
    + Don't change path to httpd
    + Remove apache 2.2 config
  
  Changelog entries since current artful version 3.14.2-2ubuntu5:
  
  gnome-user-share (3.18.3-2) unstable; urgency=medium
  
    * Fully drop Bluetooth from packaging, obsolete since 3.18.0.
    * Bump Standards-Version to 4.1.0
  
   -- Jeremy Bicha   Sun, 03 Sep 2017 10:28:16 -0400
  
  gnome-user-share (3.18.3-1) unstable; urgency=medium
  
    * New upstream release.
    * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged
  upstream.
    * Bump debhelper compat level to 10.
    * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir.
  
   -- Michael Biebl   Tue, 20 Sep 2016 12:48:27 +0200
  
  gnome-user-share (3.18.2-1) unstable; urgency=medium
  
    * New upstream release.
    * Add Build-Depends on systemd on Linux to get the correct path for the
  systemd user unit directory.
    * Add patch to ensure systemd is not mandatory so we can build on non-Linux
  architectures.
    * Bump Standards-Version to 3.9.8.
    * Drop debian/dirs, no longer needed.
    * Convert from cdbs to dh.
    * Bump debhelper compatibility level to 9.
    * Add patch to properly expand paths in gnome-user-share-webdav.desktop.
  
   -- Michael Biebl   Fri, 02 Sep 2016 18:16:19 +0200
  
  gnome-user-share (3.18.1-1) unstable; urgency=medium
  
    * New upstream release.
    * Bump Standards-Version to 3.9.7
  
   

[Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

[Gunnar Hjalmarsson]

This triggers another change to accountsservice...

** No longer affects: language-selector (Ubuntu Artful)

** Also affects: language-selector (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: accountsservice (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: language-selector (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: language-selector (Ubuntu Artful)
   Status: New => In Progress

** Changed in: language-selector (Ubuntu Artful)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: accountsservice (Ubuntu)
   Status: Fix Released => Fix Committed

** Changed in: accountsservice (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: accountsservice (Ubuntu Artful)
   Status: New => In Progress

** Changed in: accountsservice (Ubuntu Artful)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Description changed:

  [Impact]
  
  When the syntax for the entries in ~/.pam_environment was changed, the
  GUI in language-selector-gnome for maintaining the language priority
  list was broken since language-selector-gnome reads from
  ~/.pam_environment. The language-selector upload to artful makes
  language-selector-gnome handle both the old and the new syntax
  correctly.
  
+ An additional similar change to accountsservice (the update-langlist
+ script) is needed; hence also an accountsservice upload to artful.
+ 
  [Test Case]
  
  * Log in to an "Ubuntu on Xorg" session.
  * Open Language Support and find that it appears as if you can only
-   set one item before the "English" item in the language list.
+   set one item before the "English" item in the language list.
  
  With the new version, it works as expected again.
  
  [Regression Potential]
  
  Low. This is necessary to fix the regression caused by the change in
  accountsservice.
  
  [Original description]
  
  While investigating bug #1662031, I found out that /usr/share/language-
  tools/save-to-pam-env writes to ~/.pam_environment using an incorrect
  syntax: "VARIABLE=value" on each line. The expected syntax is "VARIABLE
  [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

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

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

[Bug 1727967] Re: Wrong keyboard layout for password at login

[Brian Murray]

** Tags added: bot-stop-nagging

** Package changed: ubuntu-release-upgrader (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Wrong keyboard layout for password at login

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

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

[Bug 1727869] Re: DNS resolution does not work after upgrade from 17.04 to 17.10

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd (Ubuntu)

-- 
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/1727869

Title:
  DNS resolution does not work after upgrade from 17.04 to 17.10

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

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

[Bug 1728145] [NEW] gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

[Nicholas Stommel]

Public bug reported:

When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories)
does not fill the screen at all when snapping the window to the right or
left side. There are large gaps on the right and bottom edges of the
terminal window in Wayland. On the same computer, with the same version
of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the
window fills screen space entirely and there is no problem. I am not
using display scaling or hidpi features at all, my display resolution is
set at default 1080p. This needs to be fixed or I'm ditching gnome-
terminal.

Expected behavior: gnome-terminal window should fill right/left of screen when 
snapped to corner in a Wayland session
What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

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

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


** Tags: gnome-terminal wayland

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

** Description changed:

- When using a Wayland gnome-session or ubuntu-session in Ubuntu 17.10,
- gnome-terminal (v3.24.2 is the version in the 17.10 repositories) does
- not fill the screen at all when snapping the window to the right or left
- side.There are large gaps on the right and bottom edges of the terminal
- window in Wayland. On the same computer, with the same version of gnome-
- terminal in an Xorg gnome-session or Xorg ubuntu-session, the window
- fills screen space entirely and there is no problem. I am not using
- display scaling or hidpi features at all, my display resolution is set
- at default 1080p. This needs to be fixed or I'm ditching gnome-terminal.
+ When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
+ 17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories)
+ does not fill the screen at all when snapping the window to the right or
+ left side.There are large gaps on the right and bottom edges of the
+ terminal window in Wayland. On the same computer, with the same version
+ of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the
+ window fills screen space entirely and there is no problem. I am not
+ using display scaling or hidpi features at all, my display resolution is
+ set at default 1080p. This needs to be fixed or I'm ditching gnome-
+ terminal.
  
  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

** Description changed:

  When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
  17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories)
  does not fill the screen at all when snapping the window to the right or
- left side.There are large gaps on the right and bottom edges of the
+ left side. There are large gaps on the right and bottom edges of the
  terminal window in Wayland. On the same computer, with the same version
  of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the
  window fills screen space entirely and there is no problem. I am not
  using display scaling or hidpi features at all, my display resolution is
  set at default 1080p. This needs to be fixed or I'm ditching gnome-
  terminal.
  
  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

** Summary changed:

- gnome-terminal does not fill screen when window snapping on Wayland
+ gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 
17.10

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

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

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

[Bug 1727869] [NEW] DNS resolution does not work after upgrade from 17.04 to 17.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Once 17.10 is installed,DNS resolution does not work after reboot.
May be the bug is in systemd-resolved ?
Work around by using unbound instead

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-release-upgrader-core 1:17.10.7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Thu Oct 26 23:57:46 2017
InstallationDate: Installed on 2016-07-07 (475 days ago)
InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to artful on 2017-10-26 (0 days ago)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug artful dist-upgrade zesty2artful
-- 
DNS resolution does not work after upgrade from 17.04 to 17.10
https://bugs.launchpad.net/bugs/1727869
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to systemd in Ubuntu.

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

[Bug 1727967] [NEW] Wrong keyboard layout for password at login

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading from 16.04 to 17.10 the keyboard layout is incorrect. On
my computer it uses the German layout (z <-> y keys are exchanged,
QWERTZ instead of QWERTY). After login the correct locale is used. My
physical location is in Austria

/etc/defaults/locale:

LANG=en_US.UTF-8
LC_NUMERIC=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
LC_MONETARY=en_GB.UTF-8
LC_PAPER=en_GB.UTF-8
LC_NAME=en_GB.UTF-8
LC_ADDRESS=en_GB.UTF-8
LC_TELEPHONE=en_GB.UTF-8
LC_MEASUREMENT=en_GB.UTF-8
LC_IDENTIFICATION=en_GB.UTF-8

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-release-upgrader-core 1:17.10.8
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
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 10:03:10 2017
InstallationDate: Installed on 2016-06-29 (484 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to artful on 2017-10-23 (3 days ago)

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


** Tags: amd64 apport-bug artful bot-stop-nagging dist-upgrade 
package-from-proposed wayland-session zesty2artful
-- 
Wrong keyboard layout for password at login
https://bugs.launchpad.net/bugs/1727967
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gdm3 in Ubuntu.

-- 
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

[Jeremy Bicha]

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
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 1728143] [NEW] Screen freezes after waking from suspend with Gnome on Wayland

[Nicholas Stommel]

Public bug reported:

It appears that using Xorg instead of Wayland is the only way to fix
this problem on Ubuntu 17.10. For some odd reason, whenever I wake my
computer from suspend (especially after an extended period of time
asleep) using Gnome in a Wayland session (gnome-session and stock
ubuntu-session alike), my screen freezes completely on whatever was last
there before suspending and I can't get any IO response at all. Nothing,
the screen is totally frozen. I am also unable to exit into a recovery
shell or kill GDM or gnome-session/ubuntu-session locally. I also can't
seem to find any traces or indications for the freeze in the syslog, or
maybe I'm just not sure where to look. I believe this is a problem with
GDM on Wayland, not kernel related, as it happens on a totally stock
install and when I use an upgraded/downgraded kernel. It literally
necessitates restarting my computer. This problem is nonexistent when
using Xorg instead of Wayland with GDM. Anyone else have this issue on
Ubuntu 17.10 or figure out a solution better than simply switching to
Xorg? I should clarify that I am not using nvidia drivers, I'm using
Intel integrated graphics on a core-i7 5500U.

Ubuntu 17.10 uses gnome-session v3.26.1.
Expected behavior: When waking computer from suspend, expect GDM lock prompt 
and log back in.
What happened instead: When waking computer from suspend, screen and IO is 
completely frozen, necessitating a force-shutdown.

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

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

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


** Tags: gdm gnome-17.10 gnome-session suspend-resume

** Also affects: gnome-session (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Screen freezes after waking from suspend with Gnome on Wayland

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

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

[Bug 1698553] [gjs/zesty] verification still needed

[Ubuntu Foundations Team Bug Bot]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for zesty for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  Update gjs to 1.48.5

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

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

[Bug 1728137] Re: gnome-calendar assert failure: *** Error in `/usr/bin/gnome-calendar': corrupted size vs. prev_size: 0x00007f806800b390 ***

[Apport retracing service]

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

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 #1708253, 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/1728137/+attachment/4998196/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1708253

** 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-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1728137

Title:
  gnome-calendar assert failure: *** Error in `/usr/bin/gnome-calendar':
  corrupted size vs. prev_size: 0x7f806800b390 ***

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

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

[Bug 1728077] Re: Evince uses wrong encoding when filling out a PDF form

[Thomas Dreibholz]

The upstream bug is at
https://bugs.freedesktop.org/show_bug.cgi?id=103492 .

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

Title:
  Evince uses wrong encoding when filling out a PDF form

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

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

[Bug 364253] Re: Pidgin and Tomboy spell checker underlines every word

[Bug Watch Updater]

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

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-06-27T08:14:52+00:00 Nicolas wrote:

Please make Fedora gtkspell support Enchant/Hunspell

Even though industrial Enchant/Hunspell gtkspell support is only scheduled for
gtkspell3, patches exist for previous versions. Waiting for gtkspell3 has a
major drawback: gtkspell apps use aspell dicts and OO.o/Firefox use hunspell 
dicts

aspell and hunspell dicts are not synchronized to spellchecking behaviour is
different from app to app when both exist

sometimes only hunspell dicts exist

end result is confused users

Moreover the people who could fix the dicts just look at the number of variants
(ispell/aspell/hunspell) they're supposed to maintain and just give up (or
decide to do only hunspell)

The problems of using an early gtkspell3 or a gtkspell2 patched for enchant are
dwarfed by the benefits of killing the aspell/hunspell dict duplication

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtkspell/+bug/364253/comments/0


On 2007-07-16T16:23:30+00:00 Matthew wrote:

Nicolas, can you point me to the patches for gtkspell2 ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtkspell/+bug/364253/comments/1


On 2007-07-16T17:30:41+00:00 Nicolas wrote:

They're on the enchant page gtkspell -> enchant -> hunspell

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtkspell/+bug/364253/comments/2


On 2007-10-03T16:58:07+00:00 Matthias wrote:

I guess at this point, this is no longer an F8 target...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtkspell/+bug/364253/comments/3


On 2007-12-11T10:57:50+00:00 Dwayne wrote:

Here is the link to the patch.  Just for clarity this seems to make gtkspell use
Enchant which in turn can use hunspell (amongst other checkers)

http://www.abisource.com/~dom/gtkspell-2.0.11-enchant.patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtkspell/+bug/364253/comments/4


On 2007-12-20T13:28:00+00:00 Matthew wrote:

Fixed in gtkspell-2.0.11-5.fc9.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtkspell/+bug/364253/comments/5


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

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

Title:
  Pidgin and Tomboy spell checker underlines every word

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

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