[Desktop-packages] [Bug 63245] Re: Cannot alt + tab out of fullscreen games

[parshall jeffery]

To download free gaming apps you have to visit roblox game
https://apksbrand.com/roblox-unlimited-robux-mod-apk/

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

Title:
  Cannot alt + tab out of fullscreen games

Status in Metacity:
  Confirmed
Status in metacity package in Ubuntu:
  Triaged

Bug description:
  This bug happens on Ubuntu Dapper 64-bit running the GNOME desktop
  environment.  I have not tested it on Edgy or KDE.

  When running some full screen games, the ALT+TAB shortcut will not
  minimize the window and you are forced to exit in order to return to
  the desktop.  Full screen games I have found this to be true in
  include Tremulous (www.tremulous.net), Nexuiz (www.nexuiz.com),
  Wolfenstein Enemy Territory, and Unreal Tournament 2004
  (http://www.unrealtournament.com/ut2004/).

  TO REPRODUCE THIS BUG:

  1.  Open up one of the above listed games.
  2.  Attempt to minimize the game with the ALT + TAB shortcut.

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


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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[C. Jeffery Small]

Xubuntu 22.04.1 after upgrading from 20.04

In order to get multiple Windows 10 systems to "discover" the samba
shares on two different Xubuntu systems, I had to re-enable SMB1
protocol on all the Windows systems.  Microsoft apparently keeps
disabling this on system updates.

As reported above, old Windows mapped drive assignments made to Ubuntu
samba shares have continued to work over time, but new shares cannot be
seen unless SMB1 is enabled.  of course, this should all just work using
newer secure protocols.

For a significant piece of server software, the fact that this hasn't
been addressed long ago is a real mystery.

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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


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

[Desktop-packages] [Bug 1974254] Re: Probles with Clutter

[C. Jeffery Small]

Tim, I followed your advice and yes, that fixed most of the problems I
was having.  Apparently there was a system update that required a
reboot, but there was an error and it just said all updates applied.
This has occurred on the past couple of updates that didn't have too
many changes, but something clearly got screwed up.  I should have done
this reboot myself, but I've become too comfortable believing the
package manager.  I won't make that mistake again.  So that appears to
resolve the issue.  Thanks to you and Erich for your feedback.

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

Title:
  Probles with Clutter

Status in clutter-gtk package in Ubuntu:
  Invalid

Bug description:
  Running Xubuntu 20.04.4

  I've started seeing all sorts of programs failing in the last week
  apparently due to clutter.  This includes Geeqie and Cheese, and
  possibly Zoom, although I haven't tracked down the problem there.  For
  example, when I try to start geeqie, I get:

  Can't initialize clutter-gtk.
  Start geeqie with the option: --disable-clutter

  When I try to run cheese I get:

  (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to
  initialize Clutter: Unable to initialize the Clutter backend: no
  available drivers found.

  ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: 
Unable to initialize libcheese-gtk
  Trace/BPT trap(coredump)

  In researching the problem I ran across this article:

  https://blogs.gnome.org/clutter/

  Now, I have no idea what clutter is/does, but it seems to now be
  retired.  Was the package removal back-ported to earlier releases of
  Ubuntu?  The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and
  gstreamer1.0-clutter-3.0 packages are still installed.

  Any guidelines here?  Thanks.

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


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

[Desktop-packages] [Bug 1974254] Re: Probles with Clutter

[C. Jeffery Small]

I will follow up elsewhere, but I would really like to understand the
disposition of clutter, given the site I reported that says it is now
gone.  What is actually happening here?

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

Title:
  Probles with Clutter

Status in clutter-gtk package in Ubuntu:
  Invalid

Bug description:
  Running Xubuntu 20.04.4

  I've started seeing all sorts of programs failing in the last week
  apparently due to clutter.  This includes Geeqie and Cheese, and
  possibly Zoom, although I haven't tracked down the problem there.  For
  example, when I try to start geeqie, I get:

  Can't initialize clutter-gtk.
  Start geeqie with the option: --disable-clutter

  When I try to run cheese I get:

  (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to
  initialize Clutter: Unable to initialize the Clutter backend: no
  available drivers found.

  ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: 
Unable to initialize libcheese-gtk
  Trace/BPT trap(coredump)

  In researching the problem I ran across this article:

  https://blogs.gnome.org/clutter/

  Now, I have no idea what clutter is/does, but it seems to now be
  retired.  Was the package removal back-ported to earlier releases of
  Ubuntu?  The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and
  gstreamer1.0-clutter-3.0 packages are still installed.

  Any guidelines here?  Thanks.

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


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

[Desktop-packages] [Bug 1974254] Re: Probles with Clutter

[C. Jeffery Small]

???

Can you be more specific.  I am fully patched on 20.04.4 and I still get
the same error reports from geeqie and cheese.  Both worked until very
recently and neither package was updated in quite some time.

The developer of geeqie reported that he saw the same problem.  Then he
didn't!  I am also finding a lot of other stable applications have
stopped working such as openshot and kdenlive video editors, although
these are Qt apps.  Possibly there is a deeper underlying problem.

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

Title:
  Probles with Clutter

Status in clutter-gtk package in Ubuntu:
  Invalid

Bug description:
  Running Xubuntu 20.04.4

  I've started seeing all sorts of programs failing in the last week
  apparently due to clutter.  This includes Geeqie and Cheese, and
  possibly Zoom, although I haven't tracked down the problem there.  For
  example, when I try to start geeqie, I get:

  Can't initialize clutter-gtk.
  Start geeqie with the option: --disable-clutter

  When I try to run cheese I get:

  (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to
  initialize Clutter: Unable to initialize the Clutter backend: no
  available drivers found.

  ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: 
Unable to initialize libcheese-gtk
  Trace/BPT trap(coredump)

  In researching the problem I ran across this article:

  https://blogs.gnome.org/clutter/

  Now, I have no idea what clutter is/does, but it seems to now be
  retired.  Was the package removal back-ported to earlier releases of
  Ubuntu?  The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and
  gstreamer1.0-clutter-3.0 packages are still installed.

  Any guidelines here?  Thanks.

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


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

[Desktop-packages] [Bug 1974254] Re: Probles with Clutter

[C. Jeffery Small]

I wasn't sure of the package so I left field blank.  I went back and
added clutter-gtk.  Hope that helps.

** Also affects: clutter-gtk (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Probles with Clutter

Status in Ubuntu:
  New
Status in clutter-gtk package in Ubuntu:
  New

Bug description:
  Running Xubuntu 20.04.4

  I've started seeing all sorts of programs failing in the last week
  apparently due to clutter.  This includes Geeqie and Cheese, and
  possibly Zoom, although I haven't tracked down the problem there.  For
  example, when I try to start geeqie, I get:

  Can't initialize clutter-gtk.
  Start geeqie with the option: --disable-clutter

  When I try to run cheese I get:

  (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to
  initialize Clutter: Unable to initialize the Clutter backend: no
  available drivers found.

  ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: 
Unable to initialize libcheese-gtk
  Trace/BPT trap(coredump)

  In researching the problem I ran across this article:

  https://blogs.gnome.org/clutter/

  Now, I have no idea what clutter is/does, but it seems to now be
  retired.  Was the package removal back-ported to earlier releases of
  Ubuntu?  The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and
  gstreamer1.0-clutter-3.0 packages are still installed.

  Any guidelines here?  Thanks.

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


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

[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

[C. Jeffery Small]

Just to make sure the note is here, my home directory is not in /home at
all, but located under /u which is a mount point for an external volume
on another disk.  I experienced the same problem trying to run a snap.
Whatever the solution, it should be generalized to any $HOME location.

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

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


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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[C. Jeffery Small]

Regarding my previous comment, disregard the issue about Windows 10
having problems accessing the Samba shares.  This turned out to be a
strange password problem with samba.  Resetting the user's password to
the same value that it already was immediately cleared the issue and all
windows machines could once again see the shares.

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[C. Jeffery Small]

Just to add another voice to the crowd, I'm on Xubuntu 20.04 and I just
ran across this problem myself.

I am using the Nemo file browser, but the same thing occurs with
Nautilus and Thunar.  I didn't notice the problem for a long while
because I had three legacy Windows machines on the network (all running
Windows 10 at this point) and had made file browser bookmarks to the
important shares long ago.  These bookmarks have continued to work to
this day without issue.  I got a new Windows 10 machine a few weeks ago
and was having the problem everyone reports of not being able to connect
("Failed to retrieve share list from server") on the new machine, even
though all the existing bookmarks were still functioning file.  All of
the Windows 10 machines were able to see one another without problem.

Then I ran across this thread and tried Bloodyiron's suggestion of
killing the gvfsd-smb-browse process.  Immediately I was able to connect
to the new machine using Nemo.  I quickly created some needed bookmarks
to the important shares and now I can communicate using the file browser
and expect the new bookmarks to be as reliable as the others.  So I
would suggest this bookmark method to others as a workaround.

This supports Craig W's comment about the difference between discovery
and browsing.  When I run "smbclient -L // -U ", it
reports all of the shares on the target, whether Windows or Linux, with
the closing message: "SMB1 disabled -- no workgroup available" as
expected.

Unfortunately, this is only a one-way solution.  All of the legacy
Windows 10 machines can see and access the Samba shares on the Xubuntu
box, but I haven't yet figured out a way to get the new Windows machine
to access these same shares, with or without gvfsd-smb-browse running.
Every connection attempt is rejected and I haven't found useful messages
in the logs.  If I figure out a solution, I'll post here, and I'm open
to suggestions.

I agree with the general sentiment that for a service as important as
this, there isn't any real excuse for this thing dragging out for two
years as it has.

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1901446] Re: Add gir1.2-tepl-5 package depedency

[Jeffery To]

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

** Also affects: gedit (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973312
   Importance: Unknown
   Status: Unknown

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

Title:
  Add gir1.2-tepl-5 package depedency

Status in gedit package in Ubuntu:
  New
Status in gedit package in Debian:
  Unknown

Bug description:
  (This is most likely a bug/request for Debian, but since I use Ubuntu
  I thought I would report it here first.)

  gedit in groovy depends on libtepl-5-0. It would be great if the
  package also depended on gir1.2-tepl-5 so that gedit plugins written
  in Python can call functions from tepl.

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

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

[Desktop-packages] [Bug 1901446] Re: Add gir1.2-tepl-5 package depedency

[Jeffery To]

I would argue that this is more a bug than a wishlist item.

Functionality is being moved from gedit into tepl (a "Text editor
product line" library). For instance, gedit_utils_str_middle_truncate()
was deprecated in gedit 3.36 and removed in 3.38[1], replaced with
tepl_utils_str_middle_truncate().

For my plugin Control Your Tabs, I had to inline the function[2] because
I couldn't count on users (on Debian and Debian-derived OSes) having
gir1.2-tepl-5 installed so that I could call
tepl_utils_str_middle_truncate(). (Contrast this with the Fedora tepl
rpm, which has the GObject introspection binding included in the same
package[3] and so does not have this problem.)

Should I file an issue upstream (Debian)? Would submitting a patch help?

[1]: 
https://gitlab.gnome.org/GNOME/gedit/-/commit/b21585d0f3ff2081626f6ffb7e1dc1b7a52e
[2]: 
https://github.com/jefferyto/gedit-control-your-tabs/commit/644c2b9d9a61ffd1d8f9aba44866b301ba47bf39
[3]: 
https://src.fedoraproject.org/rpms/tepl/blob/49ace7de0be692b500d7b2be23224197f96ae296/f/tepl.spec#_60

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

Title:
  Add gir1.2-tepl-5 package depedency

Status in gedit package in Ubuntu:
  New

Bug description:
  (This is most likely a bug/request for Debian, but since I use Ubuntu
  I thought I would report it here first.)

  gedit in groovy depends on libtepl-5-0. It would be great if the
  package also depended on gir1.2-tepl-5 so that gedit plugins written
  in Python can call functions from tepl.

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

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

[Desktop-packages] [Bug 1901446] [NEW] Add gir1.2-tepl-5 package depedency

[Jeffery To]

Public bug reported:

(This is most likely a bug/request for Debian, but since I use Ubuntu I
thought I would report it here first.)

gedit in groovy depends on libtepl-5-0. It would be great if the package
also depended on gir1.2-tepl-5 so that gedit plugins written in Python
can call functions from tepl.

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

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

Title:
  Add gir1.2-tepl-5 package depedency

Status in gedit package in Ubuntu:
  New

Bug description:
  (This is most likely a bug/request for Debian, but since I use Ubuntu
  I thought I would report it here first.)

  gedit in groovy depends on libtepl-5-0. It would be great if the
  package also depended on gir1.2-tepl-5 so that gedit plugins written
  in Python can call functions from tepl.

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Jeffery Hancock]

The scaling issue is affecting me as well:

Ubuntu 20.04 LTS
AORUS GeForce RTX™ 2080 Ti XTREME
2X Acer Predator XB281HK 4K Monitor - Displayport Connected
nvidia-driver-440

Installed alongside Windows 10

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1861453] [NEW] The chromium-browser snap package fails to run

[C. Jeffery Small]

Public bug reported:

Xubuntu 19.10
chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
Transitional package - chromium-browser -> chromium snap 

Chromium worked fine before the upgrade to 19.10.  There has been a
transition to snap packaging.

My first attempt to launch the browser results in:

% chromium-browser
2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/x/u/jeff/.Xauthority"
cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: 
Permission denied

% dmesg | grep DENIED  (just showing one typical message)
[827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" 
operation="mount" info="failed flags match" error=-13 
profile="/snap/core/8268/usr/lib/snapd/snap-confine" 
name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" 
srcname="/x/u/" flags="rw, rbind"

The home directory is: /u/jeff

The home directory is actually resides on an external drive mounted on
/x with /u being a symlink to /x/u

% cd /
% ls -l home u
lrwxrwxrwx 1 root root 1 Jan  2  2015 home -> u
lrwxrwxrwx 1 root root 3 Nov 30  2017 u -> x/u

%echo $XAUTHORITY
/u/jeff/.Xauthority

Applications should not care about these sorts of mounts and linkages,
but they now appear to be very sensitive to them.  What needs to be done
to make this work?


BTW, I think this move to SNAP is a disaster and completely the wrong
way to go.  Let's please stick with a single .deb packaging strategy
which has proven itself.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 19.10 chromium snap xubuntu

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

Title:
  The chromium-browser snap package fails to run

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Xubuntu 19.10
  chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
  Transitional package - chromium-browser -> chromium snap 

  Chromium worked fine before the upgrade to 19.10.  There has been a
  transition to snap packaging.

  My first attempt to launch the browser results in:

  % chromium-browser
  2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment 
value is not a clean path: "/x/u/jeff/.Xauthority"
  cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: 
Permission denied

  % dmesg | grep DENIED  (just showing one typical message)
  [827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" 
operation="mount" info="failed flags match" error=-13 
profile="/snap/core/8268/usr/lib/snapd/snap-confine" 
name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" 
srcname="/x/u/" flags="rw, rbind"

  The home directory is: /u/jeff

  The home directory is actually resides on an external drive mounted on
  /x with /u being a symlink to /x/u

  % cd /
  % ls -l home u
  lrwxrwxrwx 1 root root 1 Jan  2  2015 home -> u
  lrwxrwxrwx 1 root root 3 Nov 30  2017 u -> x/u

  %echo $XAUTHORITY
  /u/jeff/.Xauthority

  Applications should not care about these sorts of mounts and linkages,
  but they now appear to be very sensitive to them.  What needs to be
  done to make this work?


  BTW, I think this move to SNAP is a disaster and completely the wrong
  way to go.  Let's please stick with a single .deb packaging strategy
  which has proven itself.

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

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

[Desktop-packages] [Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration

[C. Jeffery Small]

I am VERY interested in continuing work on this.  I'm now running 19.04
and the problem persists.  I cannot change the status so please update
it.

There has been a long running discussion on the Xfce buglist which you
can review here:

https://bugzilla.xfce.org/show_bug.cgi?id=15116

The problem seems to be that the move to gtk3 is the source of the
condition as it has dropped support for multiple monitors.  Olivier
Fourdan is maintaining xfwm4 and he has apparently done something
internally that allows X11-aware applications to be launched on a
separate display (:0.1) in addition to the native display (:0.0), but
none of the other Xfce components such as the panel, desktop, etc have
the ability to run more than one instance on the main display.

In this forum discussion:

https://forum.xfce.org/viewtopic.php?pid=50336#p50336

member gert pointed to this patch in the gtk3 repository that seems to
indicate that multi-screen support has been added back into the toolkit.

https://github.com/xfce-
mirror/xfwm4/commit/b52c2f5b740434803342c471d4dcb5dd62eb99a1

However, this patched version of gtk has not yet made it into a Ubuntu
distribution.

Losing multi-headed independent desktop support has been a terrible step
backwards for Ubuntu.  Please look into this more closely and make sure
that the 19.10 release gets the tools required to get this capability
restored.

I'll provide additional info if necessary.  However, as an end0user in
this arena, I don't have more insights into the interactions of the
display components making up the various desktop environments.


On a couple of other forums, I asked whether there was another flavor of Ubuntu 
that was properly supporting multiple screens.  I received zero replies.  
Multiple independent desktops is critical (as opposed to Xinerama mode) so that 
material can be displayed statically on one display while changing workspaces 
on the other screen.

** Bug watch added: Xfce Bugzilla #15116
   https://bugzilla.xfce.org/show_bug.cgi?id=15116

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

Title:
  Ubuntu 18.10 broke dual-screen dual-desktop configuration

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  I'm running Xubuntu.  I finally reported this problem to the Xfce
  group and received this response:

  "As arandr/xrandr does not detect correctly your 2nd screen, this
  seems that it is not related directly to Xfce, but a bug in Xubuntu
  stack.  Can you please open a bug on Xubuntu project if the issue is
  still present for you?"

  Thus this bug report.

  
  I've been running Xubuntu for years with two monitors, each running an 
independent xfce4 desktop -- i.e., configured without Xinerama. This has worked 
fine for every upgrade through 18.04.  When upgrading to 18.10, something 
significant changed and the the second monitor (display :0.1) was disabled.  
After much reading and work, I have only been able to restore some extremely 
hobbled functionality.  I am unable to get a second xfce4-desktop, panel or 
window manager running on the second screen.  I have assembled detailed 
screenshots and command output at the following link:

  http://smallthoughts.com/xfce/xfce.html

  I'm using an NVIDIA Quadro K-4000 graphics card and no hardware
  changes were made between 18.04 and 18.10.

  The nvidia-settings tool reports both monitors active (as configured
  in /etc/X11/xorg.conf) but the xfce4-display-settings and aarandr
  tools each show only one display (although xrandr can be forced to
  report on the second display.  See full documentation at the above
  link.)

  What changed in the latest release, and what needs to be done to get
  the second monitor running a second desktop once again?  I have been
  struggling with this for many months now and it has severely impacted
  the use of my system.  As a new release of Ubuntu in coming, I would
  appreciate it if this could be prioritized and addressed as quickly as
  possible.

  I will provide additional information upon request.

  P.S.:  There is really no documentation available on running multiple
  desktops on separate screens when Xinerama is not used to tie the
  screens together into a single desktop.  This is a common
  configuration and I would like to request that as part of the solution
  to this problem, the setup steps be documented and this multi-desktop
  configuration be made a standard part of the development and testing
  process for each Ubuntu release.

  13-> lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

[Desktop-packages] [Bug 1825249] Re: fonts garbled in firefox browser -- only on certain pages

[C. Jeffery Small]

No, I haven't done that.

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

Title:
  fonts garbled in firefox browser -- only on certain pages

Status in firefox package in Ubuntu:
  New

Bug description:
  Xubuntu 18.10 and earlier releases
  Firefox browser 66.0.3 and every earlier version of the Quantum releases

  There has been a font display problem on Firefox add-on pages (and a
  very few other random sites) ever since the Quantum browser was
  released.  I reported this to the Firefox team well over a year ago
  here:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1437338

  with periodic follow-up here:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1446688

  You can see a recent example of the problem here:

  http://smallthoughts.com/photos/misc/firefox_66_01.png

  Now, while I'm convinced that this is likely a Firefox problem, I
  cannot get anyone there to reproduce the problem.  So on the chance
  that it's related to some font glitch on the Ubuntu system, I'm
  reporting it here to see if anyone can reproduce the problem.  If you
  could load a recent version of Firefox and visit this (or any add-on)
  page:

  https://addons.mozilla.org/en-US/firefox/addon/autofill-
  quantum/?src=search

  and see if you observe what I'm observing, it would be great in
  helping track down the source of this extremely annoying glitch.  BTW,
  this ONLY happen in Firefox, not in the Chromium or Opera browsers,
  and it does not happen in Firefox running under Windows 10 in a VM on
  the same machine.

  Thanks for any insights as to what might be causing this.

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

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

[Desktop-packages] [Bug 1825249] [NEW] fonts garbled in firefox browser -- only on certain pages

[C. Jeffery Small]

Public bug reported:

Xubuntu 18.10 and earlier releases
Firefox browser 66.0.3 and every earlier version of the Quantum releases

There has been a font display problem on Firefox add-on pages (and a
very few other random sites) ever since the Quantum browser was
released.  I reported this to the Firefox team well over a year ago
here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1437338

with periodic follow-up here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1446688

You can see a recent example of the problem here:

http://smallthoughts.com/photos/misc/firefox_66_01.png

Now, while I'm convinced that this is likely a Firefox problem, I cannot
get anyone there to reproduce the problem.  So on the chance that it's
related to some font glitch on the Ubuntu system, I'm reporting it here
to see if anyone can reproduce the problem.  If you could load a recent
version of Firefox and visit this (or any add-on) page:

https://addons.mozilla.org/en-US/firefox/addon/autofill-
quantum/?src=search

and see if you observe what I'm observing, it would be great in helping
track down the source of this extremely annoying glitch.  BTW, this ONLY
happen in Firefox, not in the Chromium or Opera browsers, and it does
not happen in Firefox running under Windows 10 in a VM on the same
machine.

Thanks for any insights as to what might be causing this.

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

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

Title:
  fonts garbled in firefox browser -- only on certain pages

Status in firefox package in Ubuntu:
  New

Bug description:
  Xubuntu 18.10 and earlier releases
  Firefox browser 66.0.3 and every earlier version of the Quantum releases

  There has been a font display problem on Firefox add-on pages (and a
  very few other random sites) ever since the Quantum browser was
  released.  I reported this to the Firefox team well over a year ago
  here:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1437338

  with periodic follow-up here:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1446688

  You can see a recent example of the problem here:

  http://smallthoughts.com/photos/misc/firefox_66_01.png

  Now, while I'm convinced that this is likely a Firefox problem, I
  cannot get anyone there to reproduce the problem.  So on the chance
  that it's related to some font glitch on the Ubuntu system, I'm
  reporting it here to see if anyone can reproduce the problem.  If you
  could load a recent version of Firefox and visit this (or any add-on)
  page:

  https://addons.mozilla.org/en-US/firefox/addon/autofill-
  quantum/?src=search

  and see if you observe what I'm observing, it would be great in
  helping track down the source of this extremely annoying glitch.  BTW,
  this ONLY happen in Firefox, not in the Chromium or Opera browsers,
  and it does not happen in Firefox running under Windows 10 in a VM on
  the same machine.

  Thanks for any insights as to what might be causing this.

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

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

[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Jeffery Telford]

I had the exact same problem with my Intel NUC5CPYH which uses the
Braswell chipset. After reading a lot of other articles I found this
worked for me and now I can move my mouse anywhere on the desktop and my
whole experience is a lot snappier:

1. Create a new xorg.conf file in your home directory:

sudo X :1 -configure

2. Edit the new xorg.conf.new file and modify/uncomment the following lines in 
the "Device" section:

Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
Option "DRI" "3"

3. Copy the file to the /usr/share/X11/xorg.conf.d directory and name it 
20-intel.conf:

sudo cp xorg.conf.new /usr/share/X11/xorg.conf.d/20-intel.conf

4. Either reboot or restart the gdm service.

If it doesn't work other posters suggested using "uxa" as the
AccelMethod but apparently "sna" is faster.

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1796614] Re: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor

[Jeffery]

Caveat:

Thanks Christopher...

I duplicated your solution by editing the  /etc/gdm3/custom.conf

Everything seems to be working again.

:-)

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

Title:
  [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/432

  ---

  Running startx starts X just fine, but at login I just get a blank
  screen with a blinking cursor. If I hit Alt+F I can get a console
  which allows me to login and run 'startx' at which point Gnome starts
  normally after entering my keychain unlock password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct  7 22:59:13 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Subsystem: Dell Device [1028:0877]
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:0877]
  InstallationDate: Installed on 2018-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b8c Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 187c:0550 Alienware Corporation
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 17 R5
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.5.0
  dmi.board.name: Alienware 17 R5
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 17 R5
  dmi.product.sku: 0877
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1796614] Re: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor

[Jeffery]

I also have this problem.

Differences for me:

I have a RTX 2080 and installed Nvidia's 410.78 driver manually.

Whenever I boot, I too get the black screen with a blinking cursor. I
also have the ctrl+alt+F3, login and run startx

This brings me to the gnome desktop instead of the traditional Ubuntu
desktop.

I am not really sure how to fix this issue.

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

Title:
  [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/432

  ---

  Running startx starts X just fine, but at login I just get a blank
  screen with a blinking cursor. If I hit Alt+F I can get a console
  which allows me to login and run 'startx' at which point Gnome starts
  normally after entering my keychain unlock password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct  7 22:59:13 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Subsystem: Dell Device [1028:0877]
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:0877]
  InstallationDate: Installed on 2018-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b8c Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 187c:0550 Alienware Corporation
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 17 R5
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.5.0
  dmi.board.name: Alienware 17 R5
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 17 R5
  dmi.product.sku: 0877
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1796614] Re: [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor

[Jeffery]

I also have this problem.

Differences for me:

I have a RTX 2080 and installed Nvidia's 410.78 driver manually.

Whenever I boot, I too get the black screen with a blinking cursor. I
also have the ctrl+alt+F3, login and run startx

This brings me to the gnome desktop instead of the traditional Ubuntu
desktop.

I am not really sure how to fix this issue.

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

Title:
  [nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/432

  ---

  Running startx starts X just fine, but at login I just get a blank
  screen with a blinking cursor. If I hit Alt+F I can get a console
  which allows me to login and run 'startx' at which point Gnome starts
  normally after entering my keychain unlock password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct  7 22:59:13 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Subsystem: Dell Device [1028:0877]
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:0877]
  InstallationDate: Installed on 2018-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b8c Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 187c:0550 Alienware Corporation
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 17 R5
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.5.0
  dmi.board.name: Alienware 17 R5
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 17 R5
  dmi.product.sku: 0877
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Jeffery To]

@Adrian Limmi:

1. Open the Add-ons Manager in Thunderbird, and go to the Extensions page/tab 
(if it isn't already open).
2. At the top of the page, click the gear button next to the search box to open 
a menu, then select "Install Add-on From File".
3. From here you can select the .xpi file and it should install without issue.

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

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

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

[Desktop-packages] [Bug 545778] Re: xul-ext-lightning is only available in English

[Jeffery To]

I've extracted all of the language/locale versions of Lightning 6.2.2.1
from the Thunderbird 60.2.1 Linux (binary) release tarballs, they are
available at:

https://www.dropbox.com/sh/w84dtrc73e90j3p/AABC5CeNN-
ZwoNgq9m1hQUs4a/thunderbird-60.2.1?dl=0=_nav_tracking=1

If you are reluctant to install an extension from some random Internet
person (I wouldn't blame you), you can also download the release tarball
for your locale from the Thunderbird homepage
(https://www.thunderbird.net/), then extract the .xpi file from the
thunderbird/distribution/extensions directory (inside the archive).

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Triaged
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

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

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Jeffery To]

Instead of everyone having to download and extract their own .xpi file,
I decided to do it myself and upload all the language/locale versions of
the extension to here:

https://www.dropbox.com/sh/w84dtrc73e90j3p/AABC5CeNN-
ZwoNgq9m1hQUs4a/thunderbird-60.2.1?dl=0=_nav_tracking=1

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

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

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

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Jeffery To]

The bug report for "xul-ext-lightning is only available in English" is
at https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778 .

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

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

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

[Desktop-packages] [Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1

[Jeffery To]

Recent versions of Thunderbird (at least the version packaged /
distributed by Mozilla) has come pre-installed with Lightning; this is
why the extension hasn't been updated on addons.mozilla.org.

The version of Thunderbird installable from the standard Ubuntu
repositories is packaged by Ubuntu. They have chosen to package the
extension as a separate package (xul-ext-lightning), so the most
"correct" solution to this issue is to install that package.

(xul-ext-lightning being English-only appears to be long-standing issue
(#545778); if this affects you I suggest contributing to that bug
report.)

If you would still like to install the .xpi file (perhaps because of the
locale issue):

1. Visit the Thunderbird site (https://www.thunderbird.net/) and download the 
Linux / Linux 64-bit version of Thunderbird, matching your installed version 
(60.2.1 in this case) and locale. It should  be a .tar.bz2 archive.
2. Extract the archive, then inside thunderbird/distribution/extensions there 
should be one .xpi file. That should be the corresponding version of Lightning 
(6.2.2.1).

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

Title:
  Lightning incompatible with Thunderbird 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi

  Today I got the update from Thunderbird 52 to 60.2.1. Unfortunately
  Lightning doesn't work anymore.

  Thunderbird reports that Lightning is incompatible with Thunderbird
  60.2.1.

  Regards,

  Ettore

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

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

[Desktop-packages] [Bug 1798034] Re: Package xul-ext-lightning is in English only

[Jeffery To]

Appears to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778 .

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

Title:
  Package xul-ext-lightning is in English only

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Thunderbird just updated to version 60.2 in Ubuntu 16.04 and I lost
  access to Lightning. I had Lightning 5.4 installed using Thunderbird
  add-ons, but no version compatible with TB 60.2 is available there.

  The package xul-ext-lightning is available and works with TB 60.2, but
  it's in English only.

  Now that Lightning is no longer available otherwise, the package needs
  to come with all the various language versions.

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

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

[Desktop-packages] [Bug 1798102] Re: Lightning no longer in French after upgrading to 60.2.1

[Jeffery To]

Appears to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778 .

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

Title:
  Lightning no longer in French after upgrading to 60.2.1

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is Ubuntu Budgie 18.04

  At first I thought Lightning was broken because I had to uninstall the
  mozilla-addons version of it ( the one found in mozilla addons webpage
  from inside TB ) and then re-install from Ubuntu repository xul-ext-
  lighting to have it upgraded.

  Now Calendar ( lightning ) is no longer displayed in French, but
  English.

  coeur-noir@asgard:~$ dpkg -l | egrep "thunder|xul-ext"
  ii  thunderbird   1:60.2.1+build1-0ubuntu0.18.04.2
amd64Email, RSS and newsgroup client with integrated spam filter
  ii  thunderbird-globalmenu1:60.2.1+build1-0ubuntu0.18.04.2
amd64Email, RSS and newsgroup client (transitional package)
  ii  thunderbird-gnome-support 1:60.2.1+build1-0ubuntu0.18.04.2
amd64Email, RSS and newsgroup client - GNOME support
  ii  thunderbird-locale-en 1:60.2.1+build1-0ubuntu0.18.04.2
amd64English language pack for Thunderbird
  ii  thunderbird-locale-en-us  1:60.2.1+build1-0ubuntu0.18.04.2
all  Transitional English language pack for Thunderbird
  ii  thunderbird-locale-fr 1:60.2.1+build1-0ubuntu0.18.04.2
amd64French language pack for Thunderbird
  ii  xul-ext-calendar-timezones1:60.2.1+build1-0ubuntu0.18.04.2
amd64Calendar Extension for Thunderbird (transitional package)
  ii  xul-ext-gdata-provider1:60.2.1+build1-0ubuntu0.18.04.2
amd64Calendar Extension for Thunderbird (transitional package)
  ii  xul-ext-lightning 1:60.2.1+build1-0ubuntu0.18.04.2
amd64Calendar Extension for Thunderbird
  coeur-noir@asgard:~$

  Same « problem » on Ubuntu Unity 16.04

  [ for reference https://forum.ubuntu-fr.org/viewtopic.php?id=2032006 ]

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

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

[Desktop-packages] [Bug 1777296] [NEW] Synaptic scrollbar does not work properly

[C. Jeffery Small]

Public bug reported:

Xubuntu 18.04
Synaptic 0.84.3

Many years ago this problem was reported and it still has not been
addressed.

The main scrollbar works opposite of almost all other scrollbars
everywhere.  If you B1 click in the scrollbar gutter (i.e., above or
below the movable bar), the contents jumps to the current mouse
position.  If you B2 click in the gutter, the contents scrolls a page at
a time.  This B1 and B2 behavior should be flipped to agree with the
world and make a predictable product.

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

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

Title:
  Synaptic scrollbar does not work properly

Status in xorg package in Ubuntu:
  New

Bug description:
  Xubuntu 18.04
  Synaptic 0.84.3

  Many years ago this problem was reported and it still has not been
  addressed.

  The main scrollbar works opposite of almost all other scrollbars
  everywhere.  If you B1 click in the scrollbar gutter (i.e., above or
  below the movable bar), the contents jumps to the current mouse
  position.  If you B2 click in the gutter, the contents scrolls a page
  at a time.  This B1 and B2 behavior should be flipped to agree with
  the world and make a predictable product.

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

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

[Desktop-packages] [Bug 1716749] Re: Synaptics is not fully aware of display environment

[C. Jeffery Small]

Well, it's 06-16-2018 and we're up to Xubuntu 18.04 and this problem has
not been addressed.

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

Title:
  Synaptics is not fully aware of display environment

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  In a dual monitor environment where separate Xfce4 desktops are
  running on each monitor, you can start Synaptic in either desktop
  environment, but if you start it on display :0.1, it shows the
  Authenticate pop-up window on display :0.0.  Once the password is
  entered, the main window will then appear on display :0.1.  All the
  components of a given program should be display-environment-aware.

  There are a number of system applications that have similar problems.
  I'll report them as I continue to encounter this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Sep 12 11:21:53 2017
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/ksh
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to zesty on 2017-05-27 (108 days ago)

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

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

[Desktop-packages] [Bug 1775766] [NEW] eclipse java runtime error error

[C. Jeffery Small]

Public bug reported:

Eclipse was running properly under 17.10.  After the upgrade to 18.04,
attempts to start it produce the following error:

!SESSION Thu Jun 07 22:26:49 PDT 2018 --
!ENTRY org.eclipse.equinox.launcher 4 0 2018-06-07 22:26:49.702
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)


I have reinstalled all the eclipse and core java packages with no improvement.

eclipse 3.8.1-11
libcj-java 3.13.3-1
java-common 0.63ubuntu1~02
default-jre 2:1.10-63ubuntu1~02
default-jdk 2:1.10-63ubuntu1~02

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

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

Title:
  eclipse java runtime error error

Status in eclipse package in Ubuntu:
  New

Bug description:
  Eclipse was running properly under 17.10.  After the upgrade to 18.04,
  attempts to start it produce the following error:

  !SESSION Thu Jun 07 22:26:49 PDT 2018 
--
  !ENTRY org.eclipse.equinox.launcher 4 0 2018-06-07 22:26:49.702
  !MESSAGE Exception launching the Eclipse Platform:
  !STACK
  java.lang.ClassNotFoundException: 
org.eclipse.core.runtime.adaptor.EclipseStarter
  at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626)
  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
  at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
  at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

  
  I have reinstalled all the eclipse and core java packages with no improvement.

  eclipse 3.8.1-11
  libcj-java 3.13.3-1
  java-common 0.63ubuntu1~02
  default-jre 2:1.10-63ubuntu1~02
  default-jdk 2:1.10-63ubuntu1~02

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

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

[Desktop-packages] [Bug 1775347] Re: Upgrade to 18.04 caused wrong graphics driver to be installed

[C. Jeffery Small]

The update status link in the above comment does not work.  I don't see
an option on this page to update/edit the status.

This seems like an installation issue and not something related to a
package, but if I had to select a package related to this, I would say:

nvidia-driver-390  390.48-0ubuntu3  NVIDIA driver metapackage

I hope that helps and that someone can assign this info to the package
section.

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

Title:
  Upgrade to 18.04 caused wrong graphics driver to be installed

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Upgrading Xubuntu 17.10 to 18.04
  Using Nvidia Quadro K4000 Graphics Card with proprietary driver and dual 
screens

  After the upgrade, which went smoothly, only one screen was recognized
  and the system was almost unusable.  The Xorg process was running
  wild, consuming almost all the CPU.  It was difficult to move the
  cursor and all screen updates were incredibly slow.  I suspected the
  graphics driver and saw that the Nvidia driver had been replaced with
  the X.Org Nouveau open source driver.  I checked the available drivers
  with:

  7-> ubuntu-drivers devices
  == /sys/devices/pci:00/:00:03.0/:04:00.0 ==
  modalias : pci:v10DEd11FAsv10DEsd097Cbc03sc00i00
  vendor   : NVIDIA Corporation
  model: GK106GL [Quadro K4000]
  driver   : nvidia-driver-390 - distro non-free recommended
  driver   : nvidia-340 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  After reinstalling the proprietary driver with the command:

  8-> sudo apt install nvidia-driver-390

  and rebooting the system, everything was back to normal.

  I have had similar driver replacement problems with past upgrades.
  Why doesn't the upgrade register and reinstall the proper graphics
  driver?  And why is the default driver so abysmal with a standard
  Nvidia card?  This should be fixed in future upgrades.

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

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

[Desktop-packages] [Bug 1716749] [NEW] Synaptics is not fully aware of display environment

[C. Jeffery Small]

Public bug reported:

In a dual monitor environment where separate Xfce4 desktops are running
on each monitor, you can start Synaptic in either desktop environment,
but if you start it on display :0.1, it shows the Authenticate pop-up
window on display :0.0.  Once the password is entered, the main window
will then appear on display :0.1.  All the components of a given program
should be display-environment-aware.

There are a number of system applications that have similar problems.
I'll report them as I continue to encounter this problem.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Sep 12 11:21:53 2017
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/ksh
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-05-27 (108 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Synaptics is not fully aware of display environment

Status in xorg package in Ubuntu:
  New

Bug description:
  In a dual monitor environment where separate Xfce4 desktops are
  running on each monitor, you can start Synaptic in either desktop
  environment, but if you start it on display :0.1, it shows the
  Authenticate pop-up window on display :0.0.  Once the password is
  entered, the main window will then appear on display :0.1.  All the
  components of a given program should be display-environment-aware.

  There are a number of system applications that have similar problems.
  I'll report them as I continue to encounter this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Sep 12 11:21:53 2017
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/ksh
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to zesty on 2017-05-27 (108 days ago)

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

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

[Desktop-packages] [Bug 1524755] Re: systemd support

[Jeffery Wilkins]

thanks for digging up a 2 year old problem holy hell

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

Title:
  systemd support

Status in gksu package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  we need support for systemd because both sudo and su are broken
  systemd sets a XDG_RUNTIME_DIR for /run/user/
  when doing su or sudo XDG_RUNTIME_DIR does not get set and /run/user/0 does 
not get created
  please see the github pull request I opened on github
  https://github.com/systemd/systemd/pull/2130

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

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

[Desktop-packages] [Bug 1524755] Re: systemd support

[Jeffery Wilkins]

I setup this bug because it was causing mate-panel to lock up and crash
the whole desktop just because systemd is garbage

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

Title:
  systemd support

Status in gksu package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  we need support for systemd because both sudo and su are broken
  systemd sets a XDG_RUNTIME_DIR for /run/user/
  when doing su or sudo XDG_RUNTIME_DIR does not get set and /run/user/0 does 
not get created
  please see the github pull request I opened on github
  https://github.com/systemd/systemd/pull/2130

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

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

[Desktop-packages] [Bug 1615347] [NEW] Local DNS server not removed when connected to OpenVPN network, when connected by both Ethernet and Wi-Fi

[Jeffery To]

Public bug reported:

I'm using Ubuntu 16.04, connected to the same network by both Ethernet
and Wi-Fi. When I query dnsmasq by running:

dig +short chaos txt servers.bind

I see only one set of DNS servers (one IPv4, one IPv6); not sure if it's
NetworkManager or dnsmasq that is de-duping the servers from both
connections.

When I connect to an OpenVPN connection (configured through NM,
IPv4-only, with no split-tunnelling) and query dnsmasq again, I see that
the VPN DNS server is present, but the local IPv4 DNS server is also
still used (dnsmasq reports two IPv4 servers, one IPv6 server). (I filed
bug #1615343 regarding the local IPv6 DNS server not being removed.)

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Local DNS server not removed when connected to OpenVPN network, when
  connected by both Ethernet and Wi-Fi

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04, connected to the same network by both Ethernet
  and Wi-Fi. When I query dnsmasq by running:

  dig +short chaos txt servers.bind

  I see only one set of DNS servers (one IPv4, one IPv6); not sure if
  it's NetworkManager or dnsmasq that is de-duping the servers from both
  connections.

  When I connect to an OpenVPN connection (configured through NM,
  IPv4-only, with no split-tunnelling) and query dnsmasq again, I see
  that the VPN DNS server is present, but the local IPv4 DNS server is
  also still used (dnsmasq reports two IPv4 servers, one IPv6 server).
  (I filed bug #1615343 regarding the local IPv6 DNS server not being
  removed.)

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

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

[Desktop-packages] [Bug 1615343] [NEW] IPv6 DNS server not removed when connected to IPv4-only OpenVPN VPN

[Jeffery To]

Public bug reported:

I'm using Ubuntu 16.04 on a network where the DNS server is available on
both IPv4 and IPv6 (managed by a router running OpenWrt). As mentioned
in the dnsmasq manpage, I can see dnsmasq has both IPv4 and IPv6 entries
by running:

dig +short chaos txt servers.bind

I also have an IPv4-only OpenVPN connection configured through
NetworkManager (the VPN itself is IPv4-only, the NM connection is set to
Automatic for both IPv4 and IPv6), with no split-tunnelling. When I
connect to the VPN and query dnsmasq again, I see that the IPv4 entry
has been replaced by the VPN IPv4 DNS server, but the (local network)
IPv6 entry is still present.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  IPv6 DNS server not removed when connected to IPv4-only OpenVPN VPN

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04 on a network where the DNS server is available
  on both IPv4 and IPv6 (managed by a router running OpenWrt). As
  mentioned in the dnsmasq manpage, I can see dnsmasq has both IPv4 and
  IPv6 entries by running:

  dig +short chaos txt servers.bind

  I also have an IPv4-only OpenVPN connection configured through
  NetworkManager (the VPN itself is IPv4-only, the NM connection is set
  to Automatic for both IPv4 and IPv6), with no split-tunnelling. When I
  connect to the VPN and query dnsmasq again, I see that the IPv4 entry
  has been replaced by the VPN IPv4 DNS server, but the (local network)
  IPv6 entry is still present.

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

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

[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

found the problem I think.. there is a conflict now GG GG GG
GG

[Terminal #1]
# tail -f /var/log/syslog

[Terminal #2]
# /etc/init.d/network-manager stop

(syslog is quiet)

# /etc/init.d/network-manager start

(syslog is flooded to bat shit crazy)

# /etc/init.d/dnsmasq stop
# /etc/init.d/network-manager stop

(syslog is once again quiet)

# /etc/init.d/network-manager start

(syslog is NOW quiet)
(problem found but not solved!!)

# dpkg -l dnsmasq

ii  dnsmasq 2.75-1 all
Small caching DNS proxy and DHCP/TFTP server

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing 

[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

no clue

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information 

[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

nope post reboot the problem comes back..

damn this bug to all hell

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  

[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

I have stopped the logs from filling up fast by purge resolvconf and
reinstalling it

# service network-manager stop

# dpkg --force-all --purge resolvconf

# apt-get install resolvconf

# service network-manager start

[REBOOT REQUIRED HERE]

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

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 

[Desktop-packages] [Bug 1534501] [NEW] [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

Public bug reported:

snippet of logs.

Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket for 
127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting dnsmasq...
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket for 
127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting dnsmasq...
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket for 
127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting dnsmasq...
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket for 
127.0.1.1: Address already in use
Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS information 
to /sbin/resolvconf
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting dnsmasq...
Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.430292] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 

[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

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

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   

[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

possible duplicate of bug

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost 

[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast

[Jeffery Wilkins]

this bug was filling up syslog at a rate of 1MB per Second this could
fill up a disk really quickly

hence the URGENT label

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

Title:
  [URGENT] dnsmasq errors fills up syslogs extremely fast

Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 

[Desktop-packages] [Bug 1530389] Re: [upstream] some apps can't handle sftp:// URLs

[Jeffery Wilkins]

$ /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
 fusermount: user has no write access to mountpoint /run/user/1000/gvfs
 when I tried with
 $ /usr/lib/gvfs/gvfsd-fuse ~/.gvfs -f -o big_writes
 it worked with no errors

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

Title:
  [upstream] some apps can't handle sftp:// URLs

Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  TESTED AND WORKING ARE

  GEDIT

  NOT WORKING

  MOUSEPAD
  SUBLIME_TEXT

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs 1.26.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Dec 31 10:58:23 2015
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1530389] Re: [upstream] some apps can't handle sftp:// URLs

[Jeffery Wilkins]

this bug was also reported upstream here

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

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

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

Title:
  [upstream] some apps can't handle sftp:// URLs

Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  TESTED AND WORKING ARE

  GEDIT

  NOT WORKING

  MOUSEPAD
  SUBLIME_TEXT

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs 1.26.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Dec 31 10:58:23 2015
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1530389] Re: [upstream] some apps can't handle sftp:// URLs

[Jeffery Wilkins]

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

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

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

Title:
  [upstream] some apps can't handle sftp:// URLs

Status in dbus package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  TESTED AND WORKING ARE

  GEDIT

  NOT WORKING

  MOUSEPAD
  SUBLIME_TEXT

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs 1.26.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Dec 31 10:58:23 2015
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1530389] [NEW] [upstream] some apps can't handle sftp:// URLs

[Jeffery Wilkins]

Public bug reported:

TESTED AND WORKING ARE

GEDIT

NOT WORKING

MOUSEPAD
SUBLIME_TEXT

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gvfs 1.26.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Dec 31 10:58:23 2015
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug xenial

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

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

Title:
  [upstream] some apps can't handle sftp:// URLs

Status in gvfs package in Ubuntu:
  New
Status in mousepad package in Ubuntu:
  New

Bug description:
  TESTED AND WORKING ARE

  GEDIT

  NOT WORKING

  MOUSEPAD
  SUBLIME_TEXT

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs 1.26.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Dec 31 10:58:23 2015
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1530389] Re: [upstream] some apps can't handle sftp:// URLs

[Jeffery Wilkins]

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

** No longer affects: mousepad (Ubuntu)

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

Title:
  [upstream] some apps can't handle sftp:// URLs

Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  TESTED AND WORKING ARE

  GEDIT

  NOT WORKING

  MOUSEPAD
  SUBLIME_TEXT

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs 1.26.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Dec 31 10:58:23 2015
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1529795] [NEW] sudo no longer works

[Jeffery Wilkins]

Public bug reported:

jefferyw@xubuntu:~$ sudo gnome-terminal
[sudo] password for jefferyw: 
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: 
Error calling StartServiceByName for org.gnome.Terminal: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.Terminal exited with status 10

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Dec 29 01:40:34 2015
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  sudo no longer works

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  jefferyw@xubuntu:~$ sudo gnome-terminal
  [sudo] password for jefferyw: 
  Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: 
Error calling StartServiceByName for org.gnome.Terminal: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.Terminal exited with status 10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Dec 29 01:40:34 2015
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1529795] Re: sudo no longer works

[Jeffery Wilkins]

just tried both

sudo xfce-terminal
sudo mate-terminal

and they work its just sudo gnome-terminal is having issues

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

Title:
  sudo no longer works

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  jefferyw@xubuntu:~$ sudo gnome-terminal
  [sudo] password for jefferyw: 
  Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: 
Error calling StartServiceByName for org.gnome.Terminal: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.Terminal exited with status 10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Dec 29 01:40:34 2015
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1524755] Re: systemd support

[Jeffery Wilkins]

** Also affects: gnome-terminal (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  systemd support

Status in gksu package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  we need support for systemd because both sudo and su are broken
  systemd sets a XDG_RUNTIME_DIR for /run/user/
  when doing su or sudo XDG_RUNTIME_DIR does not get set and /run/user/0 does 
not get created
  please see the github pull request I opened on github
  https://github.com/systemd/systemd/pull/2130

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

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

[Desktop-packages] [Bug 1124890] Re: Cannot send backspace using IBus' forward_key_event

[Jeffery Wilkins]

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

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

Title:
  Cannot send backspace using IBus' forward_key_event

Status in Unity:
  Triaged
Status in ibus package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I'm trying to eleminate the use of pre-editing in my input method. In
  order to do so, I have to send fake backspace events to manipulate the
  text buffer. Unity is the only application I've tried where this
  approach doesn't work.

  In my IBus engine, I'd use this call to send a fake backspace:

  self.forward_key_event(IBus.BackSpace, 14, 0)

  Attached is a minimal program to test this bug. It needs `python-gi`,
  `gir1.2-ibus` and `ibus` running to work. How to test:

  1. Open gedit, type something.
  2. Run the script `python ibus_template.py`
  3. Press any key in gedit. With each keypress, a character will be removed 
from gedit's buffer.
  4. Repeat with Unity's Dash

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

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

[Desktop-packages] [Bug 1528285] [NEW] outdated version in the repos

[Jeffery Wilkins]

Public bug reported:

version installed is very far behind the version that is at the
following repo

http://download.mono-project.com/repo/debian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mono-runtime 3.2.8+dfsg-4ubuntu4
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 21 08:34:01 2015
SourcePackage: mono
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  outdated version in the repos

Status in mono package in Ubuntu:
  New

Bug description:
  version installed is very far behind the version that is at the
  following repo

  http://download.mono-project.com/repo/debian

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mono-runtime 3.2.8+dfsg-4ubuntu4
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 21 08:34:01 2015
  SourcePackage: mono
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1528099] [NEW] pulseaudio bluetooth bug

[Jeffery Wilkins]

Public bug reported:

I switched from Xfce using Lightdm to Gnome-Shell using gdm3 I noticed my 
bluetooth headset stopped working
after couple hours of google searching I found out its because there was or is 
2 copies of pulseaudio running
one copy was running as my normal logged in user the other was gdm3
when I took steps to prevent gdm3 from starting a copy of pulseaudio by 
chmod'ing the pulseaudio binary to only allow my normal user my bluetooth 
headset started working again I was able to connect it and become the audio sink

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gdm 3.18.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Dec 20 20:49:05 2015
PackageArchitecture: all
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug xenial

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

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

Title:
  pulseaudio bluetooth bug

Status in gdm3 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I switched from Xfce using Lightdm to Gnome-Shell using gdm3 I noticed my 
bluetooth headset stopped working
  after couple hours of google searching I found out its because there was or 
is 2 copies of pulseaudio running
  one copy was running as my normal logged in user the other was gdm3
  when I took steps to prevent gdm3 from starting a copy of pulseaudio by 
chmod'ing the pulseaudio binary to only allow my normal user my bluetooth 
headset started working again I was able to connect it and become the audio sink

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 20 20:49:05 2015
  PackageArchitecture: all
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1528099] Re: pulseaudio bluetooth bug

[Jeffery Wilkins]

not sure I know how to file bugs upstream anyone else is welcome to

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

Title:
  pulseaudio bluetooth bug

Status in gdm3 package in Ubuntu:
  Triaged
Status in pulseaudio package in Ubuntu:
  New
Status in gdm3 package in Debian:
  New

Bug description:
  I switched from Xfce using Lightdm to Gnome-Shell using gdm3 I noticed my 
bluetooth headset stopped working
  after couple hours of google searching I found out its because there was or 
is 2 copies of pulseaudio running
  one copy was running as my normal logged in user the other was gdm3
  when I took steps to prevent gdm3 from starting a copy of pulseaudio by 
chmod'ing the pulseaudio binary to only allow my normal user my bluetooth 
headset started working again I was able to connect it and become the audio sink

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 20 20:49:05 2015
  PackageArchitecture: all
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1526267] Re: .../softwarecenter/backend/scagent.py : no module named "spawn_helper"

[Jeffery Wilkins]

** Also affects: software-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  .../softwarecenter/backend/scagent.py : no module named "spawn_helper"

Status in apt-xapian-index package in Ubuntu:
  Confirmed
Status in software-center package in Ubuntu:
  New

Bug description:
  xenial install

  get that crash, but apport fails to report it; so i join the crash
  file here to get the details

  
  software-center 13.10-0ubuntu12
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia
  Package: apt-xapian-index 0.47ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.3.0-4.13-generic 4.3.2
  Tags:  xenial
  Uname: Linux 4.3.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1526267] Re: .../softwarecenter/backend/scagent.py : no module named "spawn_helper"

[Jeffery Wilkins]

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

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

Title:
  .../softwarecenter/backend/scagent.py : no module named "spawn_helper"

Status in apt-xapian-index package in Ubuntu:
  Confirmed
Status in software-center package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  New

Bug description:
  xenial install

  get that crash, but apport fails to report it; so i join the crash
  file here to get the details

  
  software-center 13.10-0ubuntu12
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia
  Package: apt-xapian-index 0.47ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.3.0-4.13-generic 4.3.2
  Tags:  xenial
  Uname: Linux 4.3.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1524755] Re: systemd support

[Jeffery Wilkins]

** Information type changed from Private Security to Public

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

Title:
  systemd support

Status in gksu package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  we need support for systemd because both sudo and su are broken
  systemd sets a XDG_RUNTIME_DIR for /run/user/
  when doing su or sudo XDG_RUNTIME_DIR does not get set and /run/user/0 does 
not get created
  please see the github pull request I opened on github
  https://github.com/systemd/systemd/pull/2130

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

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

[Desktop-packages] [Bug 571970] Re: gvfsd-http leaves a lot of sockets in CLOSE_WAIT state

[Jeffery Wilkins]

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

bump for re open this bug is still present in ubuntu trusty

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

Title:
  gvfsd-http leaves a lot of sockets in CLOSE_WAIT state

Status in gvfs package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gvfs-backends

  netstat -tp reveals lots of the old connections made by gvfsd-http,
  and some of them are several days old. this seams like a resource
  leak. not very harmful for typical user, but the intense use of gvfsd
  could even block the user from making any new internet connections
  until the daemon is restarted.

  steps to reproduce:

  1. use dragdrop to copy a picture from a web browser to the gnome desktop 
(this uses gvfs internally).
  interestingly, copying a content from clickable link did not leave a stale 
socket (i don't know if this is a rule. open image in a new tab and dragging 
from there was the most reliable way to reproduce the bug)

  2. invoke netstat -tp in the console
  the socket opened by gvfsd-http wont go away

  workaround:
  kill the daemon (using killall gvfsd-http) or log out

  ProblemType: Bug
  Architecture: i386
  Date: Fri Apr 30 02:22:47 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/lib/gvfs/gvfsd-http
  NonfreeKernelModules: nvidia
  Package: gvfs-backends 1.4.1-0ubuntu1
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANGUAGE=en_US.UTF-8
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: gvfs
  Uname: Linux 2.6.31-20-generic i686

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

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

[Desktop-packages] [Bug 954426] Re: Xorg log flooded with XKB: reuse xkmfile

[Jeffery To]

I'm running Ubuntu 14.10 and I've noticed my Xorg log
(/var/log/Xorg.0.log) filling up with XKB: reuse xkmfile lines. (Not
sure how long this has been happening.) My system has been up for a bit
more than a day and my log file is 7MB.

I've tried clearing the cache files in /var/lib/xkb (as mentioned in
comment #3); the cache files are regenerated on next reboot and XKB:
reuse xkmfile lines continue to appear in the Xorg log.

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

Title:
  Xorg log flooded with XKB: reuse xkmfile

Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  I initially posed this as Question #188982, but now decided to report
  it as it seems to persist and no definitive answers as to the cause
  were found. I was apprehensive about reporting at first mainly because
  this doesn't seem to occur on my other (Precise-running) computers. It
  is however 100% reproducible on this one (i.e. the flood occurs on
  each creation of an Xorg log, though I don't know what triggers
  individual lines).

  My Xorg log is flooded with lines about reusing xkmfile:

  jani@saegusa:~$ grep XKB: reuse xkmfile /var/lib/xkb/server- 
/var/log/Xorg.0.log | tail
  [   391.894] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.901] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.906] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.909] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.914] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.919] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.922] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.926] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.929] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  [   391.933] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5CBD5B10CEC815928ACEFB86BAB14051BA0C83FF.xkm
  jani@saegusa:~$ grep XKB: reuse xkmfile /var/lib/xkb/server- 
/var/log/Xorg.0.log | wc -l
  1507

  (Interestingly I now notice that the number of those lines seems to be
  constant: the above was copy+paste from terminal just now, and when I
  posed Question #188982 on 2012-02-27, the result was 1507 also.)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: x11-xkb-utils 7.6+4
  Uname: Linux 3.3.0-030300rc4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,resize,compiztoolbox,place,gnomecompat,regex,grid,mousepoll,snap,move,wall,imgpng,vpswitch,session,unitymtgrabhandles,animation,fade,workarounds,expo,scale,ezoom,unityshell]
  CompositorRunning: None
  Date: Tue Mar 13 22:21:23 2012
  DistUpgraded: Log time: 2011-11-20 23:52:49.660633
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.8, 3.2.0-18-generic, x86_64: installed
   virtualbox, 4.1.8, 3.3.0-030300rc4-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RS780 [Radeon HD 3200] [1002:9610] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:82f1]
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-030300rc4-generic 
root=UUID=bf0f4d7e-d08c-4aad-8143-b6e3b16049d6 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: x11-xkb-utils
  UpgradeStatus: Upgraded to precise on 2012-03-13 (0 days ago)
  dmi.bios.date: 08/12/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd08/12/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  

[Desktop-packages] [Bug 1365847] Re: Firefox audio problem with flash plugin

[C. Jeffery Small]

Here is some additional information relating to this issue.

As best as I can tell, the Opera browser (ver. 12.16) is using the same
plugins as Firefox (32).  When I visit the following page:

http://flash.flowplayer.org/plugins/flash/content.html

Opera produces audio output with this video while Firefox does not.
Opera also seems to properly produce audio in flash youtube videos in
flash mode while Firefox cannot -- although if the FF flash plugin is
disabled, youtube videos will fall over to HTML5 mode and then audio is
produced.  Chromium works well in all situations with it's own Flash
11.2.r999 plugin.

The following site:

http://www.radioio.com/channels/jazz/real-jazz/play/?play

is a streaming radio channel that has worked well in the past.  It
currently plays with Firefox 31 on my Solaris system and Firefox 32 on
Windows XP.  It also plays fine using the Ubuntu Chromium browser.
However, it fails to load (i.e. connect) to the stream on both Firefox
and Opera.  I include this in the hope that it offers additional clues
as to what is wrong here.

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

Title:
  Firefox audio problem with flash plugin

Status in “flashplugin-nonfree” package in Ubuntu:
  New

Bug description:
  Xeon E5 64 bit system
  Xubuntu 14.04.1
  Firefox 32.0+build1-0ubuntu0.14.04.1
  flashplugin-installer 11.2.202.400ubuntu0.14.04.1

  Audio plays properly on this system through all media players as well
  as the Chrome and Opera browsers.  However, no sound was issuing from
  the Firefox 31 or 32 browsrs regardless of what video or audio source
  was selected.  After considerable work and a joint investigation with
  a Mozilla developer:

  see:  https://bugzilla.mozilla.org/show_bug.cgi?id=1062556

  it was determined that the proble was with the Shockwave Flash plugin.
  When this plugin was disabled, sources such as youtube would see that
  flash support was unavailable and resort to HTML5 which plays audio
  just fine.  However, disabling the flash plugin means that all flash
  content is unavailable -- both video and audio.

  This plugin interface needs to be investigated and repaired so that
  audio support can be restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1365847/+subscriptions

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

[Desktop-packages] [Bug 1365847] Re: Firefox audio problem with flash plugin

[C. Jeffery Small]

I hope someone will review this and treat it as a serious bug!

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

Title:
  Firefox audio problem with flash plugin

Status in “flashplugin-nonfree” package in Ubuntu:
  New

Bug description:
  Xeon E5 64 bit system
  Xubuntu 14.04.1
  Firefox 32.0+build1-0ubuntu0.14.04.1
  flashplugin-installer 11.2.202.400ubuntu0.14.04.1

  Audio plays properly on this system through all media players as well
  as the Chrome and Opera browsers.  However, no sound was issuing from
  the Firefox 31 or 32 browsrs regardless of what video or audio source
  was selected.  After considerable work and a joint investigation with
  a Mozilla developer:

  see:  https://bugzilla.mozilla.org/show_bug.cgi?id=1062556

  it was determined that the proble was with the Shockwave Flash plugin.
  When this plugin was disabled, sources such as youtube would see that
  flash support was unavailable and resort to HTML5 which plays audio
  just fine.  However, disabling the flash plugin means that all flash
  content is unavailable -- both video and audio.

  This plugin interface needs to be investigated and repaired so that
  audio support can be restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1365847/+subscriptions

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

[Desktop-packages] [Bug 1365847] Re: Firefox audio problem with flash plugin

[C. Jeffery Small]

Somehow this got tagged for the mdadm package although I know that I set
it properly.  I'm updating the target package to the flash plugin.

** Package changed: mdadm (Ubuntu) = flashplugin-nonfree (Ubuntu)

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

Title:
  Firefox audio problem with flash plugin

Status in “flashplugin-nonfree” package in Ubuntu:
  New

Bug description:
  Xeon E5 64 bit system
  Xubuntu 14.04.1
  Firefox 32.0+build1-0ubuntu0.14.04.1
  flashplugin-installer 11.2.202.400ubuntu0.14.04.1

  Audio plays properly on this system through all media players as well
  as the Chrome and Opera browsers.  However, no sound was issuing from
  the Firefox 31 or 32 browsrs regardless of what video or audio source
  was selected.  After considerable work and a joint investigation with
  a Mozilla developer:

  see:  https://bugzilla.mozilla.org/show_bug.cgi?id=1062556

  it was determined that the proble was with the Shockwave Flash plugin.
  When this plugin was disabled, sources such as youtube would see that
  flash support was unavailable and resort to HTML5 which plays audio
  just fine.  However, disabling the flash plugin means that all flash
  content is unavailable -- both video and audio.

  This plugin interface needs to be investigated and repaired so that
  audio support can be restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1365847/+subscriptions

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

[Desktop-packages] [Bug 1160569]

[C. Jeffery Small]

Xubuntu 14.04.1

Every time I attempt to run the apport-bug bug reporting command, it
tries to load data into an instance of firefox [30, 31, 32] which
repeatedly fails with Firefox reporting:

--
File not found
Firefox cannot find the file at current working dir 
path/https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/long_id_string
--

In the terminal window where the command is launched, I get the
following:

--
% apport-bug package

** (apport-gtk:13523): WARNING **: Couldn't connect to accessibility
bus: Failed to connect to socket /tmp/dbus-t4rIGS23K1: Connection
refused

(process:13996): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
--

The first warning is a ubuntu bug.  The second is apparently issued by
Firefox and is likely responsible for the command failing.

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

Title:
  [regression] GLib-CRITICAL **: g_slice_set_config: assertion
  `sys_page_size == 0' failed

Status in The Mozilla Firefox Browser:
  Confirmed
Status in “apport” package in Ubuntu:
  Confirmed
Status in “firefox” package in Ubuntu:
  Triaged
Status in “thunderbird” package in Ubuntu:
  Triaged

Bug description:
  Have a look at the screen-shot for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 19.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20130308124351
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: Unavailable
  Date: Tue Mar 26 21:48:57 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-26 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130326)
  IpRoute:
   default via 10.0.1.1 dev eth0  proto static
   10.0.1.0/24 dev eth0  proto kernel  scope link  src 10.0.1.16  metric 1
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Videos) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   VLC Multimedia Plugin (compatible Videos 3.6.3) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=19.0.2/20130308124351
  RelatedPackageVersions:
   totem-mozilla 3.6.3-0ubuntu4
   rhythmbox-mozilla 2.98-0ubuntu3
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 887674] Re: Desktop wallpaper doesn't rotate images

[Jeffery von Ronne]

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

** This bug has been marked a duplicate of bug 549627
   Image containing EXIF orientation does not display properly as wallpaper

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

Title:
  Desktop wallpaper doesn't rotate images

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

Bug description:
  The images I take on my digital camera are tagged in the EXIF data with 
orientation, so whether I took it in portrait or landscape, the picture shows 
up correctly.
  Nautilus, Gthumb, Shotwell, etc. work with this just fine. Using them as 
desktop wallpaper used to work fine, too.
  In Oneiric, they are no longer rotated. They show up to the wallpaper chooser 
sideways.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Nov  8 11:23:37 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 549627] Re: Image containing EXIF orientation does not display properly as wallpaper

[Jeffery von Ronne]

This is still a problem using Unity in Trusty Tahr.

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

Title:
  Image containing EXIF orientation does not display properly as
  wallpaper

Status in Nautilus:
  Incomplete
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-control-center

  An image that contains EXIF orientation data displays correctly as a
  thumbnail in gnome-appearance-properties i.e gnome-appearance-
  properties reads the EXIF and rotates the image.  However, when the
  thumbnail is selected and applied as wallpaper the orientation is not
  read and the wallpaper image is displayed with the wrong orientation.

  When bug #278332 (https://bugs.launchpad.net/ubuntu/+source/gnome-
  control-center/+bug/278332) was fixed to show the previews correctly
  is it possible the preview was actually correct as that was what you
  would see if applied ?

  Using Karmic Beta1 upgraded from 9.10.
  gnome-control-center 1:2.29.92-0ubuntu3

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

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

[Desktop-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*

[C. Jeffery Small]

I would like to also confir this bug in a 14.04.1 system.  I would live
to report this using apport-bug but it is that very command that is
failing!  Here is the terminal output seen when attempting to run this
commad:


3- apport-bug smbclient

** (apport-gtk:7235): WARNING **: Couldn't connect to accessibility bus: Failed 
to connect to socket /tmp/dbus-J9CVMJHXEs: Connection refused
4- 
(process:7727): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::sm-connect after class was initialised

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::show-crash-dialog after class was initialised

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::display after class was initialised

(firefox:7727): GLib-GObject-WARNING **: Attempt to add property 
GnomeProgram::default-icon after class was initialised


After answering various question and getting to the place where it is
supposed to write the html file, the browser reports that the file is
unavailable (i.e., doesn't exist).

I have used apport-bug a couple of times in the past.  This just started
today.  I rebotted the machine and the problem persisted.

Any known workaround would be appreciated.

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

Title:
   Couldn't connect to accessibility bus: Failed to connect to socket
  /tmp/dbus-*

Status in Assistive Technology Service Provider Interface:
  New
Status in “at-spi2-core” package in Ubuntu:
  Confirmed
Status in “at-spi2-core” package in Debian:
  Confirmed

Bug description:
  Since a few days, xsession-errors is fullfilled by that kind of
  errors:

  ** (nautilus:22621): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection
  refused

  ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused

  Similar errors are reported all over the net, but Debian have tried to fix it 
already:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517

  But some other devs seems to blame an atk-bridge:
  https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA

  And some others suggest a dbus/gdbus race; the good thing is that
  seems not disturbing that much the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  Date: Fri Jun 21 08:35:40 2013
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions

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

[Desktop-packages] [Bug 1362963] [NEW] findsmb command is missing from smbclient package

[C. Jeffery Small]

Public bug reported:

[Note: I cannot report this using apport-bug as that command is
currently failing on this system.]

The findsmb command is missing from the package:  smbclient 2.4.1.6
+dfsg-1ubuntu2.14.04.3

Note that the manual page is included, but the command itself is
missing.

There is also some confusing regarding the documentation.  Here is the
manpage for the trusty distribution:

http://manpages.ubuntu.com/manpages/trusty/man1/findsmb.1.html

Notice that it indicates that this command is included in  
smbclient_4.1.3+dfsg-2ubuntu5_i386
Is this correct notation?  Are the 64-bit packages not documented, or is this 
another bug?

The findsmb command is supposed to be a perl script so it should really be 
package independent.
Can the file be downloaded from some location?

** Affects: at-spi2-core (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  findsmb command is missing from smbclient package

Status in “at-spi2-core” package in Ubuntu:
  New

Bug description:
  [Note: I cannot report this using apport-bug as that command is
  currently failing on this system.]

  The findsmb command is missing from the package:  smbclient 2.4.1.6
  +dfsg-1ubuntu2.14.04.3

  Note that the manual page is included, but the command itself is
  missing.

  There is also some confusing regarding the documentation.  Here is the
  manpage for the trusty distribution:

  http://manpages.ubuntu.com/manpages/trusty/man1/findsmb.1.html

  Notice that it indicates that this command is included in  
smbclient_4.1.3+dfsg-2ubuntu5_i386
  Is this correct notation?  Are the 64-bit packages not documented, or is this 
another bug?

  The findsmb command is supposed to be a perl script so it should really be 
package independent.
  Can the file be downloaded from some location?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1362963/+subscriptions

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

[Desktop-packages] [Bug 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.

[C. Jeffery Small]

I also have this problem.  I recently installed 14.04.1 on a new Xeon
system and did not see this for a few days.  However, as I have done
system configuration, I now find that every time I log in, I get a pop-
up window with a title Document Not Found and the above message at the
content.  The yelp package is installed, but I didn't do this manually.
I assume it was part of the initial installation or else was installed
as a dependency by some other package that I installed.

When I select help from the pull-down menu, it accesses the following
url without problem:

file:///usr/share/xubuntu-docs/about/xubuntu-index.html

When I search the filesystem for ubuntu-help/index, the only hits are:

/usr/share/help-langpack/en_AU/ubuntu-help/index.page
/usr/share/help-langpack/en_CA/ubuntu-help/index.page
/usr/share/help-langpack/en_GB/ubuntu-help/index.page


Solving the problem would be great.  As a workaround, stopping the pop-up at 
login would be nice.

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

Title:
  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

Status in “yelp” package in Ubuntu:
  New

Bug description:
  after upgrading to 14.10 alpha 2 when i try to launch yelp from
  command or from menu it shows

  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

  even when i try to search it shows the same

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: yelp 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Aug 24 11:53:45 2014
  InstallationDate: Installed on 2012-03-24 (882 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324)
  SourcePackage: yelp
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-08-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1259422] Re: Google authentication error in empathy

[Jeffery von Ronne]

The same thing happens for me with an up-to-date 14.04 system.  I do not
believe I have had any other machines using my google account when it
happened.

** Changed in: empathy (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  Google authentication error in empathy

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Basically empathy can authenticate google account. But after couple of
  days when i start empathy, it can't authenticate google account. Other
  application which use google account are working fine. Off/On google
  account doesn't solve this problem. What i need to do is remove the
  account and add it again. And same things will happen after couple of
  days. It's embarrassing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: empathy 3.8.4-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-15.22-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Dec 10 11:55:37 2013
  MarkForUpload: True
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1245963] Re: gvfsd-afc crashes when attempting to copy a file from an iPhone using Nautilus

[Jeffery To]

I retried this today (for no particular reason) and found that I can now
copy files from my iPhone with Nautilus. I'm not sure why it works, nor
did I notice anything relevant in the packages that I upgraded recently.

:-) that it works now but :-( for not knowing why or what happened.

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

Title:
  gvfsd-afc crashes when attempting to copy a file from an iPhone using
  Nautilus

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded to Ubuntu 13.10 (Saucy) and am now unable to copy
  files from my iPhone (with iOS 6) using Nautilus.

  Steps to reproduce:

  1.  Open a Nautilus window.
  2.  Attach an iPhone. Two new entries appear under Devices in the left side 
panel: iPhone name and Documents on iPhone name
  3.  Middle-click on the iPhone name entry (or right-click and select Open 
in New Tab) to mount the iPhone file system and open a new tab.
  4.  Copy a file from the iPhone tab, and paste into the original tab.

  At this point Nautilus shows an alert box:
  Error while copying filename.
  There was an error copying the into directory.
  Show more details (when expanded:)
  Operation not supported by backend

  I don't remember if Apport prompts me to report this crash immediately
  or after a certain amount of time, but I have a crash report in
  /var/crash for gvfsd-afc. I'd be happy to attach it here if necessary,
  though I've already reported this crash a few times; I'm sure the
  developers can also find it on errors.ubuntu.com under the title
  gvfsd-afc crashed with SIGABRT in g_assertion_message().

  In Nautilus, I can still copy files to the iPhone and delete files
  from the iPhone; only copying files from the iPhone is not working. I
  can also view pictures from my iPhone directly, and copy files from it
  using Terminal (by going to the mount point in /run/user directly), so
  it appears only Nautilus is affected.

  Thanks!

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

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

[Desktop-packages] [Bug 1247873] Re: on startup upper panel is black(lower is ok)only on ubuntu 13.10

[Jeffery Eman]

Hi.. anybody working on this bug?

it is kind of annoying bug.. i've been using a workaround..
Ctrl+Alt+F1.. login to my ID.. and run 'DISPLAY=:0 gnome-panel'  - if
start the gnome-panel from first terminal it is working fine.

to automate the above step: i tried to put a shell script on startup to
call gnome-panel.  But it still show the blank upper pannel.

looks like the gnome-panel can only be called from first terminal.

this happens after i upgraded from 13.04 to 13.10...

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

Title:
  on startup upper panel is black(lower is ok)only on ubuntu 13.10

Status in “gnome-panel” package in Ubuntu:
  Confirmed

Bug description:
  on startup upper pannel is ok but lower is ok. in console i got
  (gnome-panel:16206): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: 
assertion 'accelerator != NULL' failed

  ** (gnome-panel:16206): WARNING **: Unable to parse mouse modifier
  '(null)'

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  this affects 13.10 ubuntu only

  gnome-panel:
Installed: 1:3.6.2-0ubuntu15
Candidate: 1:3.6.2-0ubuntu15
Version table:
   *** 1:3.6.2-0ubuntu15 0
  500 http://ua.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1245963] [NEW] gvfsd-afc crashes when attempting to copy a file from an iPhone using Nautilus

[Jeffery To]

Public bug reported:

I recently upgraded to Ubuntu 13.10 (Saucy) and am now unable to copy
files from my iPhone (with iOS 6) using Nautilus.

Steps to reproduce:

1.  Open a Nautilus window.
2.  Attach an iPhone. Two new entries appear under Devices in the left side 
panel: iPhone name and Documents on iPhone name
3.  Middle-click on the iPhone name entry (or right-click and select Open in 
New Tab) to mount the iPhone file system and open a new tab.
4.  Copy a file from the iPhone tab, and paste into the original tab.

At this point Nautilus shows an alert box:
Error while copying filename.
There was an error copying the into directory.
Show more details (when expanded:)
Operation not supported by backend

I don't remember if Apport prompts me to report this crash immediately
or after a certain amount of time, but I have a crash report in
/var/crash for gvfsd-afc. I'd be happy to attach it here if necessary,
though I've already reported this crash a few times; I'm sure the
developers can also find it on errors.ubuntu.com under the title gvfsd-
afc crashed with SIGABRT in g_assertion_message().

In Nautilus, I can still copy files to the iPhone and delete files from
the iPhone; only copying files from the iPhone is not working. I can
also view pictures from my iPhone directly, and copy files from it using
Terminal (by going to the mount point in /run/user directly), so it
appears only Nautilus is affected.

Thanks!

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

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

Title:
  gvfsd-afc crashes when attempting to copy a file from an iPhone using
  Nautilus

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  I recently upgraded to Ubuntu 13.10 (Saucy) and am now unable to copy
  files from my iPhone (with iOS 6) using Nautilus.

  Steps to reproduce:

  1.  Open a Nautilus window.
  2.  Attach an iPhone. Two new entries appear under Devices in the left side 
panel: iPhone name and Documents on iPhone name
  3.  Middle-click on the iPhone name entry (or right-click and select Open 
in New Tab) to mount the iPhone file system and open a new tab.
  4.  Copy a file from the iPhone tab, and paste into the original tab.

  At this point Nautilus shows an alert box:
  Error while copying filename.
  There was an error copying the into directory.
  Show more details (when expanded:)
  Operation not supported by backend

  I don't remember if Apport prompts me to report this crash immediately
  or after a certain amount of time, but I have a crash report in
  /var/crash for gvfsd-afc. I'd be happy to attach it here if necessary,
  though I've already reported this crash a few times; I'm sure the
  developers can also find it on errors.ubuntu.com under the title
  gvfsd-afc crashed with SIGABRT in g_assertion_message().

  In Nautilus, I can still copy files to the iPhone and delete files
  from the iPhone; only copying files from the iPhone is not working. I
  can also view pictures from my iPhone directly, and copy files from it
  using Terminal (by going to the mount point in /run/user directly), so
  it appears only Nautilus is affected.

  Thanks!

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

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

[Desktop-packages] [Bug 1205647] Re: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

[Jeffery To]

I've filed this issue with upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=710986

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

** Changed in: gvfs
   Importance: Undecided = Unknown

** Changed in: gvfs
   Status: New = Unknown

** Changed in: gvfs
 Remote watch: None = GNOME Bug Tracker #710986

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

Title:
  gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

Status in GVFS:
  Unknown
Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  Unmounting share from nautilus

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 27 15:58:03 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb
  InstallationDate: Installed on 2013-07-20 (6 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANGUAGE=fr_FR
   LANG=fr_FR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fad3ebbfff1:cmpb   $0x0,(%rax)
   PC (0x7fad3ebbfff1) ok
   source $0x0 ok
   destination (%rax) (0x0170) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
  UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1205647] Re: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

[Jeffery To]

I can reproduce this issue with the following steps:

1.  Open a Nautilus window. (It defaults to my home directory.)
2.  Open a new tab or window. (This also opens to my home directory.)
3.  In the new tab/window, navigate to a Samba share. (I have one bookmarked so 
I click on the bookmark in the left side panel.) A new entry for the share 
appears under Network in the left side panel.
4.  Close the new tab/window.
5.  In the left side panel, under Network, click the unmount icon next to Samba 
share entry.

At this point, gvfsd-smb crashes. I also get two alert boxes (I believe
from Nautilus):

1.  Oops! Something went wrong.
Unhandled error message: The connection is closed

2.  Unable to unmount share name
The connection is closed

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

Title:
  gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()

Status in GVFS:
  New
Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  Unmounting share from nautilus

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 27 15:58:03 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb
  InstallationDate: Installed on 2013-07-20 (6 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANGUAGE=fr_FR
   LANG=fr_FR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fad3ebbfff1:cmpb   $0x0,(%rax)
   PC (0x7fad3ebbfff1) ok
   source $0x0 ok
   destination (%rax) (0x0170) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
   ?? ()
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run()
  UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1215098] Re: iPhone with iOS 7 does not work on Ubuntu

[Jeffery von Ronne]

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

** This bug has been marked a duplicate of bug 1207812
   Iphone with iOS 7 does not work on Ubuntu

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

Title:
  iPhone with iOS 7 does not work on Ubuntu

Status in “libimobiledevice” package in Ubuntu:
  Confirmed

Bug description:
  Devices running iOS 7 now have a USB Pair Trust prompt that appears
  when the device is plugged into a machine. This prompt reads Trust
  This Computer? Your settings and data will be accessible from this
  computer when connected via USB or Wi-Fi. [Trust] [Don't Trust]

  Repro:
  1) Plug powered-on Apple device with iOS 7 into Ubuntu USB port

  Expected results: 
  The device should pair with the Ubuntu machine when Trust is tapped.

  Actual results: 
  When plugged into an Ubuntu machine, when the Trust button on the prompt is 
clicked, the iPhone buzzes twice, then repeats the prompt. This will repeat 
endlessly. 

  On the Ubuntu machine, a dialog reading The device [name of device]
  is locked. Enter the passcode on the device and click Try again.
  [Cancel] [Try again] is displayed. However, no opportunity to enter
  the passcode on the device is ever displayed. Clicking Try again
  only re-displays this dialog, endlessly.

  
  System and package information:
  Description:  Ubuntu 13.04
  Release:  13.04

  libimobiledevice-utils:
Installed: 1.1.4-1ubuntu6.2
Candidate: 1.1.4-1ubuntu6.2
Version table:
   *** 1.1.4-1ubuntu6.2 0
  500 http://us.archive.ubuntu.com/ubuntu/ raring-updates/universe i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ raring-security/universe i386 
Packages
  100 /var/lib/dpkg/status
   1.1.4-1ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
  pcfqa@Lenovo-Ubuntu:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libimobiledevice-utils 1.1.4-1ubuntu6.2
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Wed Aug 21 12:16:57 2013
  InstallationDate: Installed on 2012-04-27 (481 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libimobiledevice
  UpgradeStatus: Upgraded to raring on 2013-04-25 (117 days ago)

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

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

[Desktop-packages] [Bug 1196793] [NEW] misleading incorrect password error when lacking permissions to unlock luks

[Jeffery von Ronne]

Public bug reported:

When logged into a Ubuntu 12.04.2 server through x2go, I attempted to
use the gnome-disk-utility (palimpsest from gnome-disk-utility
3.0.2-2ubuntu7) to unlock a luks encrypted filesystem on a removable
device.  I got the error Incorrect Passphrase. Try again even though I
was using the correct passphrase (which I could use with cryptsetup
luksOpen as root).

I believe the real reason I couldn't unlock the device with gnome-
diskutility was that the default policykit org.freedesktop.udisks.policy
only allows luks-unlock for active users.  The policy is reasonable,
but gnome-disk-utility should distinguish unlock failures because of
insufficient permissions from incorrect password.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-disk-utility 3.0.2-2ubuntu7
ProcVersionSignature: Ubuntu 3.8.0-25.37~precise1-generic 3.8.13
Uname: Linux 3.8.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
Date: Mon Jul  1 23:02:56 2013
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug policykit precise

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

Title:
  misleading incorrect password error when lacking permissions to
  unlock luks

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  When logged into a Ubuntu 12.04.2 server through x2go, I attempted to
  use the gnome-disk-utility (palimpsest from gnome-disk-utility
  3.0.2-2ubuntu7) to unlock a luks encrypted filesystem on a removable
  device.  I got the error Incorrect Passphrase. Try again even though
  I was using the correct passphrase (which I could use with cryptsetup
  luksOpen as root).

  I believe the real reason I couldn't unlock the device with gnome-
  diskutility was that the default policykit
  org.freedesktop.udisks.policy only allows luks-unlock for active
  users.  The policy is reasonable, but gnome-disk-utility should
  distinguish unlock failures because of insufficient permissions from
  incorrect password.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-disk-utility 3.0.2-2ubuntu7
  ProcVersionSignature: Ubuntu 3.8.0-25.37~precise1-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Mon Jul  1 23:02:56 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1045430] [NEW] gnome-control-center appearance crash

[Jeffery Medina]

Public bug reported:

When opening gnome-control-center and clicking on Appearnace this error 
displays in a terminal (gnome-control-center:14576): GLib-GIO-CRITICAL **: 
g_simple_async_result_take_error: assertion `error != NULL' failed
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.2-0ubuntu0.4
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Mon Sep  3 09:52:48 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime  0.3.94-0ubuntu2

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


** Tags: amd64 apport-bug precise third-party-packages

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

Title:
  gnome-control-center appearance crash

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  When opening gnome-control-center and clicking on Appearnace this error 
displays in a terminal (gnome-control-center:14576): GLib-GIO-CRITICAL **: 
g_simple_async_result_take_error: assertion `error != NULL' failed
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Mon Sep  3 09:52:48 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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

[Desktop-packages] [Bug 1045430] Re: gnome-control-center appearance crash

[Jeffery Medina]

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

Title:
  gnome-control-center appearance crash

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  When opening gnome-control-center and clicking on Appearnace this error 
displays in a terminal (gnome-control-center:14576): GLib-GIO-CRITICAL **: 
g_simple_async_result_take_error: assertion `error != NULL' failed
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.4
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Mon Sep  3 09:52:48 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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

[Desktop-packages] [Bug 921339] [NEW] Unable to Open/Save Password Protected LibreOffice Calc (.ods)

[Jeffery]

Public bug reported:

After a recent Ubuntu 11.10 update, password protected LibreOffice Calc
(.ods) files are no longer able to be opened.  After the correct
password is entered, LibreOffice 3.4.5 responds with a message that
says, The password is incorrect.  The file cannot be opened.  The same
file can be opened in OpenOffice on Windows Vista.  It is also noted
that a new LibreOffice Calc file cannot be saved with a password.  When
trying to save a new file with a passord, LibreOffice 3.4.5 responsds
with a message that says, Error Saving the document...General Error.
General input/output error.

Description:Ubuntu 11.10, Release:  11.10

libreoffice:
  Installed: (none)
  Candidate: 1:3.4.5-0ubuntu1
  Version table:
 1:3.4.5-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric-proposed/main amd64 
Packages
 1:3.4.4-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 
Packages
 1:3.4.3-3ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Jan 24 18:10:57 2012
InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to oneiric on 2011-12-23 (32 days ago)

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


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  Unable to Open/Save Password Protected LibreOffice Calc (.ods)

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  After a recent Ubuntu 11.10 update, password protected LibreOffice
  Calc (.ods) files are no longer able to be opened.  After the correct
  password is entered, LibreOffice 3.4.5 responds with a message that
  says, The password is incorrect.  The file cannot be opened.  The
  same file can be opened in OpenOffice on Windows Vista.  It is also
  noted that a new LibreOffice Calc file cannot be saved with a
  password.  When trying to save a new file with a passord, LibreOffice
  3.4.5 responsds with a message that says, Error Saving the
  document...General Error.  General input/output error.

  Description:Ubuntu 11.10, Release:  11.10

  libreoffice:
Installed: (none)
Candidate: 1:3.4.5-0ubuntu1
Version table:
   1:3.4.5-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric-proposed/main amd64 
Packages
   1:3.4.4-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 
Packages
   1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Jan 24 18:10:57 2012
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-12-23 (32 days ago)

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

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