[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-26 Thread bedfojo
I can also confirm that the latest patch fixes the problem. Thank you
very much for your work!

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-06 Thread bedfojo
I should add that I'm using network-manager-openvpn and network-manager-
openvpn-gnome.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-06 Thread bedfojo
Nicholas, thank you very much for your work on this patch.

It works correctly for me: no DNS leak detected by either
https://ipleak.net or https://dnsleaktest.com for me, when both detected
leaks in the unpatched version.

Running Ubuntu-MATE 17.04.

Could we perhaps get this upstreamed into NM?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1610688] Re: Firefox 48 - Search suggestions font size too small

2016-10-11 Thread bedfojo
Fixed in Firefox 49.

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

** Changed in: ubuntu
   Status: Confirmed => Fix Released

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

Title:
  Firefox 48 - Search suggestions font size too small

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

Bug description:
  Upgraded to Firefox 48 from Firefox 47. The font size in the search
  suggestions drop down from the urlbar/awesomebar is now too small. I
  am using Linux (Ubuntu MATE 16.04). Screenshot photo attached. This
  was not the case before. Screenshot attached.

  Ubuntu-MATE 16.04, MATE 1.14.1. Numix theme.

  Reporting here as requested by upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1610688/+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 1605224] Re: at-spi-registryd.desktop not responding on shutdown

2016-07-21 Thread bedfojo
** Bug watch added: GNOME Bug Tracker #769031
   https://bugzilla.gnome.org/show_bug.cgi?id=769031

** Also affects: at-spi via
   https://bugzilla.gnome.org/show_bug.cgi?id=769031
   Importance: Unknown
   Status: Unknown

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

Title:
  at-spi-registryd.desktop not responding on shutdown

Status in at-spi:
  Unknown
Status in ubuntu-mate:
  New
Status in at-spi package in Ubuntu:
  New

Bug description:
  This issue is recurring again on Ubuntu MATE 16.04. It happens
  intermittently on two different machines, both fully updated. The
  assistive technologies are not loaded on startup (diabled in "Startup
  Applications" but it still occurs.

  There was an old bug from 2010 which has now expired as has the related 
upstream bug.
  https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/477978

  There are workarounds but these are hacks:
  
https://ubuntu-mate.community/t/issue-shutting-down-16-04-at-spi-registryd-desktop/5435
  https://ubuntuforums.org/showthread.php?t=2321728
  
https://askubuntu.com/questions/792638/ubuntu-mate-16-04-restart-shut-down-halts-due-to-a-not-responding-program-how-t
 

  A proper fix would be welcome.

  I note that all the recent reports linked to above relate to Ubuntu
  MATE only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1605224/+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 1605224] [NEW] at-spi-registryd.desktop not responding on shutdown

2016-07-21 Thread bedfojo
Public bug reported:

This issue is recurring again on Ubuntu MATE 16.04. It happens
intermittently on two different machines, both fully updated. The
assistive technologies are not loaded on startup (diabled in "Startup
Applications" but it still occurs.

There was an old bug from 2010 which has now expired as has the related 
upstream bug.
https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/477978

There are workarounds but these are hacks:
https://ubuntu-mate.community/t/issue-shutting-down-16-04-at-spi-registryd-desktop/5435
https://ubuntuforums.org/showthread.php?t=2321728
https://askubuntu.com/questions/792638/ubuntu-mate-16-04-restart-shut-down-halts-due-to-a-not-responding-program-how-t
 

A proper fix would be welcome.

I note that all the recent reports linked to above relate to Ubuntu MATE
only.

** Affects: at-spi
 Importance: Unknown
 Status: Unknown

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

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

** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

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

Title:
  at-spi-registryd.desktop not responding on shutdown

Status in at-spi:
  Unknown
Status in ubuntu-mate:
  New
Status in at-spi package in Ubuntu:
  New

Bug description:
  This issue is recurring again on Ubuntu MATE 16.04. It happens
  intermittently on two different machines, both fully updated. The
  assistive technologies are not loaded on startup (diabled in "Startup
  Applications" but it still occurs.

  There was an old bug from 2010 which has now expired as has the related 
upstream bug.
  https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/477978

  There are workarounds but these are hacks:
  
https://ubuntu-mate.community/t/issue-shutting-down-16-04-at-spi-registryd-desktop/5435
  https://ubuntuforums.org/showthread.php?t=2321728
  
https://askubuntu.com/questions/792638/ubuntu-mate-16-04-restart-shut-down-halts-due-to-a-not-responding-program-how-t
 

  A proper fix would be welcome.

  I note that all the recent reports linked to above relate to Ubuntu
  MATE only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1605224/+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 1581979] Re: nm-applet crashed with SIGSEGV in g_hash_table_resize()

2016-07-15 Thread bedfojo
Upstream claims this is fixed. Any chance of backporting the fix to
Ubuntu 16.04?

See: https://bugzilla.gnome.org/show_bug.cgi?id=768655#c1

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

Title:
  nm-applet crashed with SIGSEGV in g_hash_table_resize()

Status in Network Manager Applet:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  nm-applet crashed with SIGSEGV in g_closure_invoke()

  Network Manager applet crashed when Ubuntu MATE started.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.2.0-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 15 15:26:43 2016
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-14 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.43.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.43.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.43.61  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: nm-applet
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SegvAnalysis:
   Segfault happened at: 0x7fd88f2bae38:mov(%r9,%rsi,4),%r8d
   PC (0x7fd88f2bae38) ok
   source "(%r9,%rsi,4)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-applet crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   MAGNETAR 1  2e433d92-0406-4d29-bd58-277142f3019a  802-11-wireless  
1463325983  sun 15.maí 2016, 15:26:23 UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes wlp4s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0 
   Wired connection 1  46e16390-1bf8-4b9a-9269-7a4636905381  802-3-ethernet   
1463325954  sun 15.maí 2016, 15:25:54 UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
MAGNETAR 1  2e433d92-0406-4d29-bd58-277142f3019a  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1581979/+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 1581979] Re: nm-applet crashed with SIGSEGV in g_hash_table_resize()

2016-07-11 Thread bedfojo
** Bug watch added: GNOME Bug Tracker #768655
   https://bugzilla.gnome.org/show_bug.cgi?id=768655

** Also affects: network-manager-applet via
   https://bugzilla.gnome.org/show_bug.cgi?id=768655
   Importance: Unknown
   Status: Unknown

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

Title:
  nm-applet crashed with SIGSEGV in g_hash_table_resize()

Status in Network Manager Applet:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  nm-applet crashed with SIGSEGV in g_closure_invoke()

  Network Manager applet crashed when Ubuntu MATE started.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.2.0-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 15 15:26:43 2016
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-14 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.43.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.43.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.43.61  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: nm-applet
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SegvAnalysis:
   Segfault happened at: 0x7fd88f2bae38:mov(%r9,%rsi,4),%r8d
   PC (0x7fd88f2bae38) ok
   source "(%r9,%rsi,4)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-applet crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   MAGNETAR 1  2e433d92-0406-4d29-bd58-277142f3019a  802-11-wireless  
1463325983  sun 15.maí 2016, 15:26:23 UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes wlp4s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0 
   Wired connection 1  46e16390-1bf8-4b9a-9269-7a4636905381  802-3-ethernet   
1463325954  sun 15.maí 2016, 15:25:54 UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
MAGNETAR 1  2e433d92-0406-4d29-bd58-277142f3019a  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1581979/+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 1591671] Re: nm-applet crash after boot - SIGSEGV in g_hash_table_remove_all()

2016-06-16 Thread bedfojo
Thanks for the interest. However, I can't tell if it is a duplicate. It
is a different error to that in bug #1581979.

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

Title:
  nm-applet crash after boot - SIGSEGV in g_hash_table_remove_all()

Status in ubuntu-mate:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Fairly regularly I get this crash on boot in nm-applet.

  The wifi connects OK, so it is only a problem in nm-applet.
  Relaunching nm-applet works OK.

  Apport crash report attached.

  Ubuntu MATE 16.04 fully updated.

  network-manager-gnome is 1.2.0-ubuntu0.16.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1591671/+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 1591671] Re: nm-applet crash after boot - SIGSEGV in g_hash_table_remove_all()

2016-06-12 Thread bedfojo
** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nm-applet crash after boot - SIGSEGV in g_hash_table_remove_all()

Status in ubuntu-mate:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Fairly regularly I get this crash on boot in nm-applet.

  The wifi connects OK, so it is only a problem in nm-applet.
  Relaunching nm-applet works OK.

  Apport crash report attached.

  Ubuntu MATE 16.04 fully updated.

  network-manager-gnome is 1.2.0-ubuntu0.16.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1591671/+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 1001902] Re: xdg-open is not mate compatible

2014-10-11 Thread bedfojo
** Package changed: ubuntu = xdg-utils (Ubuntu)

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

** Also affects: xdg-utils via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754219
   Importance: Unknown
   Status: Unknown

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

Title:
  xdg-open is not mate compatible

Status in The Linux Mint Distribution:
  New
Status in Ubuntu MATE:
  Confirmed
Status in Xdg-utils:
  Unknown
Status in “xdg-utils” package in Ubuntu:
  Confirmed

Bug description:
  I had to modify /usr/bin/xdg-open to duplicate the gnome parts and
  replace /gnome/mate/. Some applications like chrome/chromium open
  their file using xdg-open.

  Linux Mint 13 RC mate edition

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1001902/+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 1001902] Re: xdg-open is not mate compatible

2014-10-01 Thread bedfojo
** Package changed: xdg-utils (Ubuntu) = ubuntu-mate

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

Title:
  xdg-open is not mate compatible

Status in The Linux Mint Distribution:
  New
Status in Ubuntu MATE:
  Confirmed
Status in Ubuntu:
  Confirmed

Bug description:
  I had to modify /usr/bin/xdg-open to duplicate the gnome parts and
  replace /gnome/mate/. Some applications like chrome/chromium open
  their file using xdg-open.

  Linux Mint 13 RC mate edition

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1001902/+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 1001902] Re: xdg-open is not mate compatible

2014-09-30 Thread bedfojo
** Project changed: ubuntu-mate = xdg-utils (Ubuntu)

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

Title:
  xdg-open is not mate compatible

Status in The Linux Mint Distribution:
  New
Status in Ubuntu:
  Confirmed
Status in “xdg-utils” package in Ubuntu:
  New

Bug description:
  I had to modify /usr/bin/xdg-open to duplicate the gnome parts and
  replace /gnome/mate/. Some applications like chrome/chromium open
  their file using xdg-open.

  Linux Mint 13 RC mate edition

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1001902/+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 1001902] Re: xdg-open is not mate compatible

2014-09-30 Thread bedfojo
See upstream : https://bugs.freedesktop.org/show_bug.cgi?id=74125

It may be that xdg-utils v1.1.0-rc2 is patched.

Any chance of Ubuntu updating xdg-utils to v1.1.0-rc2 or simply carrying
the patch if not?

** Bug watch added: freedesktop.org Bugzilla #74125
   https://bugs.freedesktop.org/show_bug.cgi?id=74125

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

Title:
  xdg-open is not mate compatible

Status in The Linux Mint Distribution:
  New
Status in Ubuntu:
  Confirmed
Status in “xdg-utils” package in Ubuntu:
  New

Bug description:
  I had to modify /usr/bin/xdg-open to duplicate the gnome parts and
  replace /gnome/mate/. Some applications like chrome/chromium open
  their file using xdg-open.

  Linux Mint 13 RC mate edition

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1001902/+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