[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

[Evan Carroll]

Just found this, still having this bug -- with Reuters.

https://unix.stackexchange.com/q/451413/3285

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.


  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
 array [
object path "/org/gnome/SessionManager/Inhibitor1686"
 ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId 
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason 
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.


  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+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 138141] Re: [upstream] Draw exporting .odg to .svg renders text invisible importing .svg back into Draw

[Christopher M. Penalver]

** Tags added: amd64 bionic i386 natty

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

Title:
  [upstream] Draw exporting .odg to .svg renders text invisible
  importing .svg back into Draw

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-draw
  libreoffice-draw:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy unoconv
  unoconv:
Installed: 0.3-6
Candidate: 0.3-6
Version table:
   *** 0.3-6 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Draw via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/138141/+attachment/2144240/+files/p0p1p2.odg
  && unoconv --listener && unoconv -f svg p0p1p2.odg && lodraw -nologo
  p0p1p2.odg p0p1p2.svg

  the two files should look the same.

  4) What happen instead is the text is gone in the p0p1p2.svg file. The
  problem is that in the svg file the 'fill' attribute of the text is
  set to 'none' while it should have the color of the text.

  WORKAROUND: replace fill:none  with fill:#00 in the xml code of
  the svg file and text will be rendered black. Until bug is solved,
  users can do this with a replace all command in a text editor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/138141/+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 1070210] Re: Libreoffice always uses "letter" paper

[Rolf Leggewie]

FWIW, I do have libpaper-utils and thus paperconf installed.  This
utility was mentioned in the upstrem ticket.

** Bug watch added: Document Foundation Bugzilla #109058
   https://bugs.documentfoundation.org/show_bug.cgi?id=109058

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=109058
   Importance: Unknown
   Status: Unknown

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

Title:
  Libreoffice always uses "letter" paper

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  For new documents, libreoffice chooses always "letter" paper.  It is
  expected, that documents are in A4 paper, because the locale ist set
  to de_DE.UTF-8.

  LibreOffice settings: 
  Tools --> Options --> Language Settings --> Languages --> Locale stting: 
Default - German (Germany)

  The locale settings are: 
  > locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=en_US.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  LibreOffice Version:
  > apt-cache policy libreoffice
  libreoffice:
Installed: 1:3.5.4-0ubuntu1.1
Candidate: 1:3.5.4-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1070210/+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 1070210] Re: Libreoffice always uses "letter" paper

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=109058.

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


On 2017-07-11T07:23:33+00:00 H-m-brand wrote:

LibreOffice completely ignores all deviations from defaults to a $LANG
as the system stored in LC_ALL, LC_PAPER, LC_TIME, etc

For my work I want most of en_US.utf8, but e.g. *NEVER* paper size
Letter of date format M/D/Y, so my (changed) system locales are

$ echo $LANG
en_US.UTF-8
$ echo $LC_ALL
$ env | grep LC_
$ locale -ck LC_PAPER
LC_PAPER
height=297
width=210
paper-codeset="UTF-8"
$ locale -ck LC_NUMERIC
LC_NUMERIC
decimal_point="."
thousands_sep=","
grouping=3;3
numeric-decimal-point-wc=46
numeric-thousands-sep-wc=44
numeric-codeset="UTF-8"
$ locale -ck LC_TIME
LC_TIME
abday="Sun;Mon;Tue;Wed;Thu;Fri;Sat"
day="Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday"
abmon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec"
mon="January;February;March;April;May;June;July;August;September;October;November;December"
am_pm="AM;PM"
d_t_fmt="%a %d %b %Y %R %Z"
d_fmt="%d-%m-%Y"
t_fmt="%R"
t_fmt_ampm="%H:%M:%S"
era=
era_year=""
era_d_fmt=""
alt_digits=
era_d_t_fmt=""
era_t_fmt=""
time-era-num-entries=0
time-era-entries="S"
week-ndays=7
week-1stday=19971130
week-1stweek=7
first_weekday=1
first_workday=2
cal_direction=1
timezone=""
date_fmt="%a %e %b %Y %H:%M:%S"
time-codeset="UTF-8"
$ locale -ck LC_ADDRESS
LC_ADDRESS
postal_fmt="%f%N%a%N%d%N%b%N%s %h %e %r%N%z %T%N%c%N"
country_name=""
country_post=""
country_ab2="NL"
country_ab3="NLD"
country_car="NL"
country_num=528
country_isbn=""
lang_name="Nederlands"
lang_ab="nl"
lang_term="nld"
lang_lib="dut"
address-codeset="UTF-8"
$ locale -ck LC_MEASUREMENT
LC_MEASUREMENT
measurement=1
measurement-codeset="UTF-8"
$ locale -ck LC_MONETARY
LC_MONETARY
int_curr_symbol="EUR "
currency_symbol="€"
mon_decimal_point=","
mon_thousands_sep=" "
mon_grouping=3;3
positive_sign=""
negative_sign="-"
int_frac_digits=2
frac_digits=2
p_cs_precedes=1
p_sep_by_space=1
n_cs_precedes=1
n_sep_by_space=1
p_sign_posn=1
n_sign_posn=2
crncystr="-€"
int_p_cs_precedes=1
int_p_sep_by_space=1
int_n_cs_precedes=1
int_n_sep_by_space=1
int_p_sign_posn=1
int_n_sign_posn=2
duo_int_curr_symbol="EUR "
duo_currency_symbol="€"
duo_int_frac_digits=2
duo_frac_digits=2
duo_p_cs_precedes=1
duo_p_sep_by_space=1
duo_n_cs_precedes=1
duo_n_sep_by_space=1
duo_int_p_cs_precedes=1
duo_int_p_sep_by_space=1
duo_int_n_cs_precedes=1
duo_int_n_sep_by_space=1
duo_p_sign_posn=1
duo_n_sign_posn=2
duo_int_p_sign_posn=1
duo_int_n_sign_posn=2
uno_valid_from=10101
uno_valid_to=1231
duo_valid_from=10101
duo_valid_to=1231
conversion_rate=1;1
monetary-decimal-point-wc=44
monetary-thousands-sep-wc=32
monetary-codeset="UTF-8"

And NONE of those deviations are respected, making my developer life
harder.

This is not new. I reported this back in 2009 to the OpenOffice team,
and no action was taken whatsoever. I just hope filing this ticket might
help.

This is the case in all LibreOffice versions I have access to.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1070210/comments/1


On 2017-07-11T23:35:34+00:00 Vstuart-foote wrote:

@Eike?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1070210/comments/2


On 2017-07-12T11:27:25+00:00 Eike Rathke wrote:

Known, the locale data is taken from a fixed set and can be influenced only 
very little.
The LC_CTYPE locale if present determines the general locale data setting.
The LC_MESSAGES locale if present determines the UI language.

For paper configuration, if the LibreOffice locale under
Tools->Options->LanguageSettings->Languages is set to Default then the
libpaper paperconf utility is probed (which itself takes several sources
into account, see man paperconf), if that is not available or the paper
can't be determined from it then LC_PAPER width and height should be
taken.

However, this nicely fits bug 46448 for which some presets of the
configurable locale data should be taken of LC_* settings if available.
Adding as related.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1070210/comments/3


On 2017-11-22T06:53:52+00:00 Mikeus wrote:

I would also note that LibreOffice ignores not only alterations made with LC_* 
variable assignments but also manually compiled locale definition files with 
category keyword values differing from those LibreOffice considers right for 
that language.
I have slightly tuned ru_RU.utf8 locale definitions to use a point 

[Desktop-packages] [Bug 1070210] Re: Libreoffice always uses "letter" paper

[Rolf Leggewie]

I can verify this even in boinic

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Low

** Tags added: bionic

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

Title:
  Libreoffice always uses "letter" paper

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  For new documents, libreoffice chooses always "letter" paper.  It is
  expected, that documents are in A4 paper, because the locale ist set
  to de_DE.UTF-8.

  LibreOffice settings: 
  Tools --> Options --> Language Settings --> Languages --> Locale stting: 
Default - German (Germany)

  The locale settings are: 
  > locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=en_US.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  LibreOffice Version:
  > apt-cache policy libreoffice
  libreoffice:
Installed: 1:3.5.4-0ubuntu1.1
Candidate: 1:3.5.4-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1070210/+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 1070210] Re: Libreoffice always uses "letter" paper

[Launchpad Bug Tracker]

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

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

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

Title:
  Libreoffice always uses "letter" paper

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  For new documents, libreoffice chooses always "letter" paper.  It is
  expected, that documents are in A4 paper, because the locale ist set
  to de_DE.UTF-8.

  LibreOffice settings: 
  Tools --> Options --> Language Settings --> Languages --> Locale stting: 
Default - German (Germany)

  The locale settings are: 
  > locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=en_US.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  LibreOffice Version:
  > apt-cache policy libreoffice
  libreoffice:
Installed: 1:3.5.4-0ubuntu1.1
Candidate: 1:3.5.4-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1070210/+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 913958] Re: nautilus crashed with SIGABRT: nautilus_window_slot_get_current_uri, code should not be reached

[Launchpad Bug Tracker]

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

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

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

Title:
  nautilus crashed with SIGABRT: nautilus_window_slot_get_current_uri,
  code should not be reached

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I was trying to open a new tab. If it's of any relevance, I have
  dropbox running. It's the first time I've seen this crash in the 3 or
  4 days I've been using 12.04 alpha.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.2.1-2ubuntu6 [modified: 
usr/share/applications/nautilus-home.desktop]
  ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
  Uname: Linux 3.2.0-8-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Mon Jan  9 14:20:48 2012
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  ProcCmdline: nautilus -n
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/913958/+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 1766479] Re: Resizing a window's left border to the right can cause it to scoot right

[Launchpad Bug Tracker]

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

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

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

Title:
  Resizing a window's left border to the right can cause it to scoot
  right

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

Bug description:
  Tested with 18.04 beta.

  Created a small window, ffmpeg or ffplay showing a 2x2 pixel video.
  When trying to move it, instead selected left border. Dragging right
  caused the window to scoot away faster than the pointer was moving,
  vanishing in less than a second.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766479/+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 1766479] Re: Resizing a window's left border to the right can cause it to scoot right

[Launchpad Bug Tracker]

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

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

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

Title:
  Resizing a window's left border to the right can cause it to scoot
  right

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

Bug description:
  Tested with 18.04 beta.

  Created a small window, ffmpeg or ffplay showing a 2x2 pixel video.
  When trying to move it, instead selected left border. Dragging right
  caused the window to scoot away faster than the pointer was moving,
  vanishing in less than a second.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766479/+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 1441603] Re: The "CURLY LOGICAL OR/AND" glyphs across all Nanum fonts are swapped over.

[Changwoo Ryu]

Don't expect this issue be fixed.

FYI, only the upstream (Naver Corp) can fix it, because "fixing" it by
others without changing the font name is a clear violation of SIL OFL
license. And Naver doesn't care about this font and is focusing on other
"BarunGothic" font.

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

Title:
  The "CURLY LOGICAL OR/AND" glyphs across all Nanum fonts are swapped
  over.

Status in fonts-nanum package in Ubuntu:
  New

Bug description:
  SYSTEM AND PACKAGE VERSIONS

  Ubuntu Precise 12.04.5 LTS
  Package fonts-nanum.
  Tested with version 3.010-2, but appears still to be present in versions 
20131007-1 (Trusty) and 20140930-1 (Vivid).
  The Firefox referred to below is version 37.0.1+build1-0ubuntu0.12.04.1.

  SANITY CHECK

  Just in case you are also having the same problem that I describe below, the 
following characters should all point in the SAME directions:
   - Pointing DOWN: ⋎ ∨ v (0x22CE, 0x2228, 0x76)
   - Pointing UP: ⋏ ∧ ^ (x022CF, 0x2227, 0x5e)
  Those all display correctly for me in the text box I'm submitting this report 
from (in Firefox), but the first character of each group (the CURLY LOGICAL 
OR/AND character) is upside down for me in the submitted bug report.

  If some characters above point in the wrong direction for you too, you
  should also expect them to be displayed incorrectly in the bug
  description below.

  PROBLEM DESCRIPTION

  The four font files

   - /usr/share/fonts/truetype/nanum/NanumGothic.ttf
   - /usr/share/fonts/truetype/nanum/NanumGothicBold.ttf
   - /usr/share/fonts/truetype/nanum/NanumMyeongjo.ttf
   - /usr/share/fonts/truetype/nanum/NanumMyeongjoBold.ttf

  all have an error in their glyphs for Unicode codepoints 0x22CE and
  0x22CF.

  (I'm using http://www.unicode.org/charts/PDF/U2200.pdf here for
  reference, which other fonts (e.g. DejaVu Sans) also agree with on
  these codepoints.)

  0x22CE (⋎) is the codepoint for the "CURLY LOGICAL OR" symbol (point
  downwards) but the glyph given in the fonts above is the CURLY LOGICAL
  AND  symbol (point upwards).

  Similarly, 0x22CF (⋏) is the codepoint for the "CURLY LOGICAL AND"
  symbol (point upwards) but is rendered by the fonts above with the
  CURLY LOGICAL OR symbol (point downwards).

  The NanumMyeongjo fonts are selected (at least for me and my
  colleagues) by Firefox when it renders those glyphs, and these fonts
  are installed by default in Ubuntu 12.04 Desktop.  The Firefox font
  choice is unchanged even after we installed additional fonts (e.g.
  STIXGeneral) which contain the glyphs in their correct form.  I have
  attached a screen capture demonstrating an example of this "in the
  wild".

  As the glyphs are swapped (rather than simply missing) they still
  *look* correct when viewed in context, and this causes subtle and
  quite serious problems because it can literally change the meaning of
  the mathematical formulae we use in our work.  (For example, these
  symbols are used for rendering formal specifications in the Z
  language, and the meaning of a specification can be fundamentally
  altered by swapping one of those characters for the other.)

  I realise that the primary purpose of this package is to provide Korean 
characters, not mathematical symbols, but since this bug is
   a) potentially quite serious, literally changing the meaning of displayed 
content,
   b) present when viewing content in the default browser on a default Ubuntu 
Desktop install, and
   c) presumably correctable by swapping over the two existing glyphs,
  I hope it can be fixed quickly.

  Many thanks,

  Paul.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-nanum/+bug/1441603/+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 1778369] [NEW] 3D graphics card Bug

[Sergio U. Sanchez Buelna]

Public bug reported:

I was just testing the xorg after a system upgrade from 16.04 to 18.04
and it sent this bug

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jun 23 19:58:11 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:0443]
InstallationDate: Installed on 2017-02-07 (501 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Gigabyte Technology Co., Ltd. GA-880GM-USB3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic 
root=UUID=6722f859-698a-40ff-9e7f-22382ec16837 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FC
dmi.board.name: GA-880GM-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd03/14/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GM-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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 1:2.10.5-1ubuntu1
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
xserver.bootTime: Sat Jun 23 19:23:49 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input USB OPTICAL MOUSE   MOUSE, id 8
 inputSILITEK USB Keyboard KEYBOARD, id 9
 inputSILITEK USB Keyboard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  3D graphics card Bug

Status in xorg package in Ubuntu:
  New

Bug description:
  I was just testing the xorg after a system upgrade from 16.04 to 18.04
  and it sent this bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jun 23 19:58:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:0443]
  InstallationDate: Installed on 2017-02-07 (501 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-880GM-USB3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic 
root=UUID=6722f859-698a-40ff-9e7f-22382ec16837 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FC
  dmi.board.name: GA-880GM-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd03/14/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GM-USB3
  dmi.sys.vendor: Gigabyte Technology Co., 

[Desktop-packages] [Bug 1778368] [NEW] Upgrading said my ubuntu was not installed properly

[John W Sheffield]

Public bug reported:

Slow loading and does not give me fill control of some options I should
have control over is there a program to check my Ubuntu installation?
washerg...@gmail.com

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Jun 23 20:38:19 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. GT218 [GeForce 8400 GS Rev. 3] [3842:1302]
InstallationDate: Installed on 2018-06-23 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
MachineType: HP-Pavilion RK575AA-ABA a1740n
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=06495141-2229-48c0-bf95-d35c2f7236c2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.23
dmi.board.name: LEONITE
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 5.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.23:bd10/30/2007:svnHP-Pavilion:pnRK575AA-ABAa1740n:pvr:rvnASUSTekComputerINC.:rnLEONITE:rvr5.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.family: 103C_53316J
dmi.product.name: RK575AA-ABA a1740n
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Jun 23 20:28:31 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  Upgrading said my ubuntu was not installed properly

Status in xorg package in Ubuntu:
  New

Bug description:
  Slow loading and does not give me fill control of some options I
  should have control over is there a program to check my Ubuntu
  installation? washerg...@gmail.com

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jun 23 20:38:19 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GT218 [GeForce 8400 GS Rev. 3] [3842:1302]
  InstallationDate: Installed on 2018-06-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: HP-Pavilion RK575AA-ABA a1740n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=06495141-2229-48c0-bf95-d35c2f7236c2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.23
  

[Desktop-packages] [Bug 1775999] Re: Cannot set vino preferences in Lubuntu 18.04

[Coeur Noir]

Xubuntu 18.04 :

utilisateur@ordinateur:~$ vino-preferences
vino-preferences : commande introuvable

Without that, how to enable desktop sharing, how to set a vnc password ?

I'm trying x11vnc but its thousands options are not easy to deal with.

And I just discovered Tigervnc is now available in Ubuntu-repository but
am not sure how to make it autostart with session in my quite simple
user-case…

Vino was rather simple and efficient for my little usage.

For reference : https://forum.ubuntu-fr.org/viewtopic.php?id=2027493

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

Title:
  Cannot set vino preferences in Lubuntu 18.04

Status in vino package in Ubuntu:
  Confirmed

Bug description:
  Apparently the functionality of vino-preferences was merged into
  gnome-control-center for 18.04. But since Lubuntu does not include
  gnome-control-center, there is no way to set up vino.,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vino 3.22.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat Jun  9 08:40:31 2018
  InstallationDate: Installed on 2018-03-09 (91 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1)
  SourcePackage: vino
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1775999/+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 1778367] [NEW] package emacs25-common (not installed) failed to install/upgrade: '/usr/share/emacs/25.2/lisp/gnus/gnus-cloud.elc.dpkg-new' をオープンできません: 許可されていない操作です

[Tomoki Uchiyama]

Public bug reported:

Failed to install.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: emacs25-common (not installed)
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jun 24 09:13:41 2018
ErrorMessage: '/usr/share/emacs/25.2/lisp/gnus/gnus-cloud.elc.dpkg-new' 
をオープンできません: 許可されていない操作です
InstallationDate: Installed on 2018-06-02 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64(20180108.1)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: emacs25
Title: package emacs25-common (not installed) failed to install/upgrade: 
'/usr/share/emacs/25.2/lisp/gnus/gnus-cloud.elc.dpkg-new' をオープンできません: 
許可されていない操作です
UpgradeStatus: Upgraded to bionic on 2018-06-02 (21 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package emacs25-common (not installed) failed to install/upgrade:
  '/usr/share/emacs/25.2/lisp/gnus/gnus-cloud.elc.dpkg-new' をオープンできません:
  許可されていない操作です

Status in emacs25 package in Ubuntu:
  New

Bug description:
  Failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: emacs25-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 24 09:13:41 2018
  ErrorMessage: '/usr/share/emacs/25.2/lisp/gnus/gnus-cloud.elc.dpkg-new' 
をオープンできません: 許可されていない操作です
  InstallationDate: Installed on 2018-06-02 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64(20180108.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: emacs25
  Title: package emacs25-common (not installed) failed to install/upgrade: 
'/usr/share/emacs/25.2/lisp/gnus/gnus-cloud.elc.dpkg-new' をオープンできません: 
許可されていない操作です
  UpgradeStatus: Upgraded to bionic on 2018-06-02 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1778367/+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 1778319] Re: Error when trying to open Nautilus from desktop with hotkey

[gf]

I am also using Ubuntu 18.04 with latest updates. 
Files(Nautilus) version 3.26.3. Actions taken: same as described by reporter. 
Expected result is to open Files.  
Actual result is an error window as described. 
Click *ok* on the error window and Files window is open in an empty folder 
called *x-nautilus-desktop:///*(gf)

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

Title:
  Error when trying to open Nautilus from desktop with hotkey

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Click on the desktop, press Ctrl+N (to open new Nautilus window). It results 
in error:
  "This location could not be displayed.
  Sorry, could not display all the contents of "x-nautilus-desktop:///":
  The specified location is not supported"

  Using Ubuntu 18.04 with latest updates, Files version 3.26.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1778319/+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 1778319] Re: Error when trying to open Nautilus from desktop with hotkey

[gf]

I am able to replicate the bug. (gf)

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

Title:
  Error when trying to open Nautilus from desktop with hotkey

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Click on the desktop, press Ctrl+N (to open new Nautilus window). It results 
in error:
  "This location could not be displayed.
  Sorry, could not display all the contents of "x-nautilus-desktop:///":
  The specified location is not supported"

  Using Ubuntu 18.04 with latest updates, Files version 3.26.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1778319/+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 1778319] Re: Error when trying to open Nautilus from desktop with hotkey

[Launchpad Bug Tracker]

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

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

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

Title:
  Error when trying to open Nautilus from desktop with hotkey

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Click on the desktop, press Ctrl+N (to open new Nautilus window). It results 
in error:
  "This location could not be displayed.
  Sorry, could not display all the contents of "x-nautilus-desktop:///":
  The specified location is not supported"

  Using Ubuntu 18.04 with latest updates, Files version 3.26.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1778319/+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 1778365] [NEW] default keyboard layout switches at login on boot

[Joe Liau]

Public bug reported:

Description:Ubuntu 18.04 LTS
Release:18.04

gnome-shell:
  Installed: 3.28.1-0ubuntu2
  Candidate: 3.28.1-0ubuntu2
  Version table:
 *** 3.28.1-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


Expected:
-Arrive at login screen
-Login using preferred keyboard layout en1(Colemak)

What happened:
-Login screen defaults to en2(US) keyboard layout, which is not the default
-Type in the wrong password a few times before noticing and switching to en1

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

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

Title:
  default keyboard layout switches at login on boot

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  gnome-shell:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected:
  -Arrive at login screen
  -Login using preferred keyboard layout en1(Colemak)

  What happened:
  -Login screen defaults to en2(US) keyboard layout, which is not the default
  -Type in the wrong password a few times before noticing and switching to en1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1778365/+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 1778233] Re: Xorg crash when using mouse

[Ville Haapala]

Seems that sometimes pScreen pointer in miPointerSetPosition() is null.

In the attached crash report, the crash is happening here:
current_x = MIPOINTER(pDev)->x - pScreen->x;

#0  0x56353930d2af in miPointerSetPosition (pDev=pDev@entry=0x56353a9d0960, 
mode=mode@entry=0, screenx=screenx@entry=0x7f4a11cd25c0, 
screeny=screeny@entry=0x7f4a11cd25c8, nevents=nevents@entry=0x7f4a11cd25bc, 
events=events@entry=0x7f4a20145050) at ../../../../mi/mipointer.c:629


(gdb) x pScreen
0x56353a660470: 0x


But I have seen it also happening a few lines earlier here:
switch_screen = !point_on_screen(pScreen, x, y);


I don't know how it is possible to get the crash on line 629.
The pScreen pointer is accessed before that, and I would expect the crash 
already there.

And I have absolutely no idea why I'm seeing that null pointer anyway.

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

Title:
  Xorg crash when using mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes when moving mouse Xorg crashes.

  I have a Logitech mouse with free spinning scroll wheel (MX Master).
  100% sure way to reproduce the problem is put the wheel is free spin
  mode and scroll as fast as possible for a few seconds.

  Also the crash happens randomly every couple of days during normal use
  when moving mouse normally.

  I have tried both Nouveau and Nvidia proprietary GPU drivers. Same
  behavior on both.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  xserver-xorg-core:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  Date: Fri Jun 22 16:09:44 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496]
  InstallationDate: Installed on 2018-06-05 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Intel Corporation S2600CW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=09005743-f23a-4610-8ea7-102ba625db6a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.0024.021320181901
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600CW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H12881-251
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0024.021320181901:bd02/13/2018:svnIntelCorporation:pnS2600CW:pvr:rvnIntelCorporation:rnS2600CW:rvrH12881-251:cvn..:ct17:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600CW
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation
  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/xorg/+bug/1778233/+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 1745666] Re: gsd-housekeeping leaks file descriptors

[Vlad K.]

Same here, for Permission Denied, on Bionic. Occurs once every hour.

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

Title:
  gsd-housekeeping leaks file descriptors

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Apparently a process called gsd-housekeeping is periodically invoked
  on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason.
  Looks like it is leaking file descriptors while doing so.

  My syslogs are full of error messages like the following:

  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error 
opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu5 500
  500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+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 1752053] Re: nvidia-390 fails to boot graphical display

[samurailink3]

This is not fixed.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1778361] [NEW] system monitor option "All Processes" does not work

[peterzay]

Public bug reported:

***
*** Please attribute this bug to the correct package.
***

ubuntu-bug -w failed.

The "All Processes" option only displays the current user's processes.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gedit 3.28.1-1ubuntu1
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
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 23 17:02:00 2018
InstallationDate: Installed on 2018-05-03 (50 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  system monitor option "All Processes" does not work

Status in gedit package in Ubuntu:
  New

Bug description:
  ***
  *** Please attribute this bug to the correct package.
  ***

  ubuntu-bug -w failed.

  The "All Processes" option only displays the current user's processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 23 17:02:00 2018
  InstallationDate: Installed on 2018-05-03 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1778361/+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 1778225] Re: Can't switch UI language for single users, only system-wide

[Gunnar Hjalmarsson]

Unfortunately I can't make sense of the information you have provided so
far. The locale configuration is screwed up somehow, but none of the two
files where such configuration is normally saved seems to be involved.
You reported that "Apply System-Wide" makes a difference, and that
precludes quite a few candidate files.

I don't know how to reproduce the behavior you describe, and so far I
see no confirmed bug in any of the packages which are involved in
language/locale settings. Can you add anything else to shed some light
on it?

Possibly you simply need help with cleaning up the configuration of your
system, and then some support forum such as  is
the place to go.

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1778225/+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 1759942] Re: [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all

[Keith Gaughan]

I believe I'm hitting the same issue, albeit with a Lenovo Miix 310,
which previously to upgrading to Bionic had working audio.

Attached is a log of what I get when I attempt to start pulseaudio with
"pulseaudio -vv", and the list of devices and PCMs given by "aplay -l"
and "aplay -L" respectively.

** Attachment added: "Archive of log files."
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1759942/+attachment/5155943/+files/logs.tzx

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

Title:
  [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a asus laptope model e200h. I install the ubunto desktop. but
  it seems that the audio does not work. I went through the whole
  troubleshooting, but it still dose not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2314/fd/14: Stale file handle
   Cannot stat file /proc/2314/fd/15: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2517 F pulseaudio
  CasperVersion: 1.376.2
  CurrentDesktop: Unity
  Date: Thu Mar 29 20:07:58 2018
  LiveMediaBuild: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio failed
  Symptom_Card: Intel HDMI/DP LPE Audio - Intel HDMI/DP LPE Audio
  Symptom_DevicesInUse:
   Cannot stat file /proc/2314/fd/14: Stale file handle
   Cannot stat file /proc/2314/fd/15: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2517 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HdmiLpeAudio - Intel HDMI/DP LPE Audio, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: E
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1759942/+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 1778011] Re: PRIME Power Saving mode draws too much power

[fargoth]

Can we have an option to switch to the iGPU, but keep the nvidia card
powered and its modules loaded so that it can be used for CUDA
calculations?

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

Title:
  PRIME Power Saving mode draws too much power

Status in nvidia-prime package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Bionic:
  In Progress

Bug description:
  Relying on the nouveau driver and on the vga switcheroo (to get around
  a change in systemd LP: #1777099) caused increased power consumption,
  and slowed down the switching process.

  Solving the problem in systemd (LP: #1777099), and adding code in gpu-
  manager and in nvidia-prime to unload the nvidia modules, and to allow
  the PCI device to sleep, dramatically decreases power consumption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+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 1778319] Re: Error when trying to open Nautilus from desktop with hotkey

[Hans Joachim Desserud]

** Tags added: bionic

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

Title:
  Error when trying to open Nautilus from desktop with hotkey

Status in nautilus package in Ubuntu:
  New

Bug description:
  Click on the desktop, press Ctrl+N (to open new Nautilus window). It results 
in error:
  "This location could not be displayed.
  Sorry, could not display all the contents of "x-nautilus-desktop:///":
  The specified location is not supported"

  Using Ubuntu 18.04 with latest updates, Files version 3.26.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1778319/+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 1762827] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Phil Marsh]

I got this error message while attempting to install Wine from the Ubuntu 18.04 
repository. The Wine install failed.
Thanks,
Phil

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Apr 11 01:29:46 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-BVXsrr/2-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-21 (109 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1762827/+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 1778344] Re: Shotwell exports images with DPI of 1 according to windows

[Bryce Willey]

The original CR2 image from the camera is:

Exif.Image.XResolution   Rational1  72
Exif.Image.YResolution   Rational1  72
Exif.Image.ResolutionUnitShort   1  inch

But I use Darktable to process the raw image, and it's output is:

Error: XMP Toolkit error 203: Duplicate property or field node
Warning: Failed to decode XMP metadata.
Exif.Image.XResolution   SLong   1  300
Exif.Image.YResolution   SLong   1  300
Exif.Image.ResolutionUnitShort   1  inch

So it must be a problem with Darktable. Thanks for the help, I'll close
this.

** Changed in: shotwell (Ubuntu)
   Status: New => Invalid

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

Title:
  Shotwell exports images with DPI of 1 according to windows

Status in shotwell package in Ubuntu:
  Invalid

Bug description:
  When sending images edited with Shotwell to Window's users, the
  properties of the image show a vertical and horizontal resolution of 1
  PPI. I'm assuming that this is a metadata mislabel and that the image
  would have the same problem, but Shotwell does not show the PPI/DPI of
  an image, only the number of pixels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1778344/+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 1778352] Re: [HDA-Intel - HDA Intel, playback] No output device shown; works in Windows

[Ken Edensor]

Please don't let the 'options' addition at the end of /etc/modprobe.d
/alsa-base.conf mislead you - there was no output device shown before I
added it, nor after I commented it out and restarted my PC.

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

Title:
  [HDA-Intel - HDA Intel, playback] No output device shown; works in
  Windows

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04
  No device shown in Settings-> Sound but works fine on this Sony Vaio in 
Windows XP

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ken1556 F pulseaudio
ken   22363 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 23 16:46:08 2018
  InstallationDate: Installed on 2018-05-12 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 980 F pulseaudio
ken1556 F pulseaudio
ken   22363 F alsamixer
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-28 (26 days ago)
  dmi.bios.date: 05/19/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0044J2
  dmi.chassis.asset.tag: Reserved
  dmi.chassis.type: 10
  dmi.chassis.vendor: Reserved
  dmi.chassis.version: Reserved
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0044J2:bd05/19/2006:svnSonyCorporation:pnVGN-FS515E:pvrC3LMFF3M:cvnReserved:ct10:cvrReserved:
  dmi.product.name: VGN-FS515E
  dmi.product.version: C3LMFF3M
  dmi.sys.vendor: Sony Corporation
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-06-13T07:13:49.694143

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1778352/+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 1778352] [NEW] [HDA-Intel - HDA Intel, playback] No output device shown; works in Windows

[Ken Edensor]

Public bug reported:

Ubuntu 18.04
No device shown in Settings-> Sound but works fine on this Sony Vaio in Windows 
XP

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic i686
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ken1556 F pulseaudio
  ken   22363 F alsamixer
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 23 16:46:08 2018
InstallationDate: Installed on 2018-05-12 (42 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 980 F pulseaudio
  ken1556 F pulseaudio
  ken   22363 F alsamixer
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel, playback] No sound at all
UpgradeStatus: Upgraded to bionic on 2018-05-28 (26 days ago)
dmi.bios.date: 05/19/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0044J2
dmi.chassis.asset.tag: Reserved
dmi.chassis.type: 10
dmi.chassis.vendor: Reserved
dmi.chassis.version: Reserved
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0044J2:bd05/19/2006:svnSonyCorporation:pnVGN-FS515E:pvrC3LMFF3M:cvnReserved:ct10:cvrReserved:
dmi.product.name: VGN-FS515E
dmi.product.version: C3LMFF3M
dmi.sys.vendor: Sony Corporation
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-06-13T07:13:49.694143

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386

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

Title:
  [HDA-Intel - HDA Intel, playback] No output device shown; works in
  Windows

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04
  No device shown in Settings-> Sound but works fine on this Sony Vaio in 
Windows XP

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ken1556 F pulseaudio
ken   22363 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 23 16:46:08 2018
  InstallationDate: Installed on 2018-05-12 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 980 F pulseaudio
ken1556 F pulseaudio
ken   22363 F alsamixer
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-28 (26 days ago)
  dmi.bios.date: 05/19/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0044J2
  dmi.chassis.asset.tag: Reserved
  dmi.chassis.type: 10
  dmi.chassis.vendor: Reserved
  dmi.chassis.version: Reserved
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0044J2:bd05/19/2006:svnSonyCorporation:pnVGN-FS515E:pvrC3LMFF3M:cvnReserved:ct10:cvrReserved:
  dmi.product.name: VGN-FS515E
  dmi.product.version: C3LMFF3M
  dmi.sys.vendor: Sony Corporation
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-06-13T07:13:49.694143

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1778352/+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 1778351] [NEW] Xorg freeze

[Joe Mau]

Public bug reported:

Always after mid-time suspend

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jun 23 17:51:54 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:837f]
   Subsystem: Hewlett-Packard Company Device [103c:8380]
InstallationDate: Installed on 2018-02-13 (129 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: HP HP ProBook 470 G5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.vendor: HP
dmi.bios.version: Q85 Ver. 01.01.07
dmi.board.name: 837F
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.21.00
dmi.chassis.asset.tag: 5CD7497QSD
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 470 G5
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Jun 23 17:51:31 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Always after mid-time suspend

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 23 17:51:54 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (129 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh 

[Desktop-packages] [Bug 1777650] Re: gparted failes to start

[Curtis Gedak]

It appears that the command fixed the issue with lib*g*tkmm.  Next it
hits an issue with lib*a*tkmm, so the next thing to try is to reinstall
that package.  You might need to do this with several packages as the
library of installed packages on your computer appears to be out-of-sync
with the actual packages installed.

Try:

  sudo apt install --reinstall libatkmm-1.6-1v5

and then try to run gparted again.

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

Title:
  gparted failes to start

Status in gtkmm2.4 package in Ubuntu:
  New

Bug description:
  Gparted wanted to start

  termanal input up to failure

  marvin@X1-18:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  /usr/sbin/gpartedbin: error while loading shared libraries: 
libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory
  marvin@X1-18:~$ sudo apt-get install libgtkmm-2.4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'libgtkmm-2.4-1v5' for regex 'libgtkmm-2.4'
  Note, selecting 'libgtkmm-2.4-1c2a' for regex 'libgtkmm-2.4'
  Note, selecting 'libgtkmm-2.4-dev' for regex 'libgtkmm-2.4'
  Note, selecting 'libgtkmm-2.4-doc' for regex 'libgtkmm-2.4'
  libgtkmm-2.4-1v5 is already the newest version (1:2.24.5-2).
  libgtkmm-2.4-dev is already the newest version (1:2.24.5-2).
  ^[[AThe following NEW packages will be installed:
libgtkmm-2.4-doc
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  89 not fully installed or removed.
  Need to get 0 B/8'630 kB of archives.
  After this operation, 123 MB of additional disk space will be used.
  Do you want to continue? [Y/n] ^[[A^C
  marvin@X1-18:~$ sudo apt install gparted
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gparted is already the newest version (0.30.0-3ubuntu1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  89 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up gir1.2-gtk-2.0 (2.24.32-1ubuntu1) ...
  Setting up libltdl-dev:amd64 (2.4.6-2) ...
  Setting up po-debconf (1.0.20) ...
  Setting up libglib2.0-dev-bin (2.56.1-2ubuntu1) ...
  Setting up libcairo-script-interpreter2:amd64 (1.15.10-2) ...
  Setting up libsigsegv2:amd64 (2.12-1) ...
  Setting up libpthread-stubs0-dev:amd64 (0.3-4) ...
  Processing triggers for install-info (6.5.0.dfsg.1-2) ...
  Setting up libpng-tools (1.6.34-1) ...
  Processing triggers for libglib2.0-0:amd64 (2.56.1-2ubuntu1) ...
  Setting up xorg-sgml-doctools (1:1.11-1) ...
  Setting up libicu-le-hb0:amd64 (1.0.3+git161113-4) ...
  Setting up libxml2-utils (2.9.4+dfsg1-6.1ubuntu1) ...
  Setting up libarchive-cpio-perl (0.10-1) ...
  Setting up m4 (1.4.18-1) ...
  Processing triggers for sgml-base (1.29) ...
  Setting up libyaml-tiny-perl (1.70-1) ...
  Setting up x11proto-dev (2018.4-4) ...
  Setting up libsys-hostname-long-perl (1.5-1) ...
  Setting up x11proto-damage-dev (1:2018.4-4) ...
  Setting up pkg-config (0.29.1-0ubuntu2) ...
  Setting up xtrans-dev (1.3.5-1) ...
  Setting up x11proto-xext-dev (2018.4-4) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-3) ...
  Setting up libmail-sendmail-perl (0.80-1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up gir1.2-harfbuzz-0.0:amd64 (1.7.2-1ubuntu1) ...
  Setting up x11proto-xinerama-dev (2018.4-4) ...
  Setting up autotools-dev (20180224.1) ...
  Setting up libice-dev:amd64 (2:1.0.9-2) ...
  Setting up libpixman-1-dev:amd64 (0.34.0-2) ...
  Setting up libuuid-perl (0.27-1build1) ...
  Setting up doc-base (0.10.8) ...
  Registering 41 doc-base files...
  Registering documents with scrollkeeper...
  Setting up x11proto-randr-dev (2018.4-4) ...
  Setting up libiculx60:amd64 (60.2-3ubuntu3) ...
  Setting up libx11-doc (2:1.6.4-3) ...
  Processing triggers for man-db (2.8.3-2) ...
  Setting up libpcrecpp0v5:amd64 (2:8.39-9) ...
  Setting up libpcre32-3:amd64 (2:8.39-9) ...
  Setting up icu-devtools (60.2-3ubuntu3) ...
  Setting up libpcre16-3:amd64 (2:8.39-9) ...
  Setting up libgraphite2-dev:amd64 (1.3.11-2) ...
  Setting up x11proto-input-dev (2018.4-4) ...
  Setting up libharfbuzz-gobject0:amd64 (1.7.2-1ubuntu1) ...
  Setting up x11proto-composite-dev (1:2018.4-4) ...
  Setting up libgtkmm-3.0-doc (3.22.2-2) ...
  Setting up autopoint (0.19.8.1-6) ...
  Setting up zlib1g-dev:amd64 (1:1.2.11.dfsg-0ubuntu2) ...
  Setting up libfile-stripnondeterminism-perl (0.040-1.1~build1) ...
  Setting up libtool (2.4.6-2) ...
  Setting up libsm-dev:amd64 (2:1.2.2-1) ...
  Setting up libpcre3-dev:amd64 (2:8.39-9) ...
  Setting up x11proto-core-dev (2018.4-4) ...
  Setting up libsigc++-2.0-dev:amd64 (2.10.0-2) ...
  Setting up x11proto-fixes-dev (1:2018.4-4) ...
  Setting up libxau-dev:amd64 

[Desktop-packages] [Bug 138141] Re: [upstream] Draw exporting .odg to .svg renders text invisible importing .svg back into Draw

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  [upstream] Draw exporting .odg to .svg renders text invisible
  importing .svg back into Draw

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-draw
  libreoffice-draw:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy unoconv
  unoconv:
Installed: 0.3-6
Candidate: 0.3-6
Version table:
   *** 0.3-6 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Draw via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/138141/+attachment/2144240/+files/p0p1p2.odg
  && unoconv --listener && unoconv -f svg p0p1p2.odg && lodraw -nologo
  p0p1p2.odg p0p1p2.svg

  the two files should look the same.

  4) What happen instead is the text is gone in the p0p1p2.svg file. The
  problem is that in the svg file the 'fill' attribute of the text is
  set to 'none' while it should have the color of the text.

  WORKAROUND: replace fill:none  with fill:#00 in the xml code of
  the svg file and text will be rendered black. Until bug is solved,
  users can do this with a replace all command in a text editor.

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

[Vstuart-foote]

No issue with export to SVG filter, issue with SVG import filter.
Workaround would have been using the svgio filter using Insert -> Image

Resolved with bug 32248.

http://cgit.freedesktop.org/libreoffice/core/commit/?id=dc3eb865bd10e690dbf80f41277b062ac2253572

tdf#32248 SVG: first attempt to support tspan elements

It will be available in 5.2.0.

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

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

Title:
  [upstream] Draw exporting .odg to .svg renders text invisible
  importing .svg back into Draw

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-draw
  libreoffice-draw:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy unoconv
  unoconv:
Installed: 0.3-6
Candidate: 0.3-6
Version table:
   *** 0.3-6 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Draw via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/138141/+attachment/2144240/+files/p0p1p2.odg
  && unoconv --listener && unoconv -f svg p0p1p2.odg && lodraw -nologo
  p0p1p2.odg p0p1p2.svg

  the two files should look the same.

  4) What happen instead is the text is gone in the p0p1p2.svg file. The
  problem is that in the svg file the 'fill' attribute of the text is
  set to 'none' while it should have the color of the text.

  WORKAROUND: replace fill:none  with fill:#00 in the xml code of
  the svg file and text will be rendered black. Until bug is solved,
  users can do this with a replace all command in a text editor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/138141/+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 1778344] [NEW] Shotwell exports images with DPI of 1 according to windows

[Bryce Willey]

Public bug reported:

When sending images edited with Shotwell to Window's users, the
properties of the image show a vertical and horizontal resolution of 1
PPI. I'm assuming that this is a metadata mislabel and that the image
would have the same problem, but Shotwell does not show the PPI/DPI of
an image, only the number of pixels.

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

** Attachment added: "An example image with 1 PPI"
   
https://bugs.launchpad.net/bugs/1778344/+attachment/5155854/+files/Lacy-A1560562.jpg

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

Title:
  Shotwell exports images with DPI of 1 according to windows

Status in shotwell package in Ubuntu:
  New

Bug description:
  When sending images edited with Shotwell to Window's users, the
  properties of the image show a vertical and horizontal resolution of 1
  PPI. I'm assuming that this is a metadata mislabel and that the image
  would have the same problem, but Shotwell does not show the PPI/DPI of
  an image, only the number of pixels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1778344/+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 1778342] [NEW] package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Steven Hoffarth]

Public bug reported:

Upgrading from 16.04 to 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: gconf2 3.2.6-4ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: amd64
Date: Sat Jun 23 08:30:05 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-07-24 (699 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: gconf
Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to artful on 2018-06-23 (0 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Upgrading from 16.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  Date: Sat Jun 23 08:30:05 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-24 (699 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2018-06-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1778342/+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 1725362] Re: Network icon shows question mark after connected to wifi, not wifi radio strength icon

[Raúl Vidal]

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

I am on Ubuntu 18.04 LTS.

This happens to me from time to time. If I reset the router the question mark 
disappears.
Check that the DHCP table has no conflicts. Or that your router is not hung.

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

Title:
  Network icon shows question mark after connected to wifi, not wifi
  radio strength icon

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  BEHAVIOR
  After I successfully connect to a wifi network, the network icon in the 
system tray (at the top-right) shows a question mark over the radio strength 
symbol (even though the Internet connect is working fine). After about 3-5 
minutes, it disappears and the radio symbol shows the signal strength.

  EXPECTED BEHAVIOR
  For the question mark to not be showing if the connection is successful and 
there is valid Internet access, I suppose.

  BUG DISCOVERED USING
  Ubuntu 17.10
  GNOME 3.26.1
  Xorg 1.19.5
  Nvidia 384.90 proprietary driver
  Linux kernel 4.13.0-16-generic
  Panda USB wireless N wifi adapater, connected to a 5.0ghz linksys wireless 
router (E2500)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725362/+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 1778332] [NEW] Apparmor Permission Denied (apparmor="DENIED")

[Clement Yuan]

Public bug reported:

I try to launch the system monitor but nothing show up.

journalctl -f 
Result:
Jun 23 19:04:24 laptop-hostname audit[8109]: AVC apparmor="DENIED" 
operation="capable" profile="snap-update-ns.gnome-system-monitor" pid=8109 
comm="3" capability=6  capname="setgid"
Jun 23 19:04:24 laptop-hostname kernel: audit: type=1400 
audit(1529751864.744:47): apparmor="DENIED" operation="capable" 
profile="snap-update-ns.gnome-system-monitor" pid=8109 comm="3" capability=6  
capname="setgid"
Jun 23 19:04:24 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[8097]: cannot update snap 
namespace: cannot drop supplementary groups: operation not permitted
Jun 23 19:04:24 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[8097]: snap-update-ns failed 
with code 1: File exists
Jun 23 19:04:28 laptop-hostname pkexec[8128]: pam_unix(polkit-1:session): 
session opened for user root by (uid=1000)

/var/log/syslog
Result:
Jun 23 19:03:17 laptop-hostname kernel: [  433.266715] audit: type=1400 
audit(1529751797.796:42): apparmor="DENIED" operation="mount" info="failed 
srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" 
name="/snap/gnome-system-monitor/45/gnome-platform/" pid=7471 comm="3" 
srcname="/snap/gnome-3-26-1604/64/" flags="rw, bind"
Jun 23 19:03:17 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 
19:03:17.799121 main.go:192: cannot change mount namespace of snap 
"gnome-system-monitor" according to change mount (/snap/gnome-3-26-1604/64 
/snap/gnome-system-monitor/45/gnome-platform none bind,ro 0 0): permission 
denied
Jun 23 19:03:17 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 
19:03:17.833637 main.go:192: cannot change mount namespace of snap 
"gnome-system-monitor" according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): permission denied
Jun 23 19:03:17 laptop-hostname kernel: [  433.301209] audit: type=1400 
audit(1529751797.828:43): apparmor="DENIED" operation="mount" info="failed 
srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" 
name="/usr/local/share/fonts/" pid=7471 comm="3" flags="ro, remount, bind"
Jun 23 19:03:17 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 
19:03:17.835300 main.go:192: cannot change mount namespace of snap 
"gnome-system-monitor" according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
permission denied
Jun 23 19:03:17 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 
19:03:17.838094 main.go:192: cannot change mount namespace of snap 
"gnome-system-monitor" according to change mount 
(/var/lib/snapd/hostfs/var/cache/fontconfig /var/cache/fontconfig none bind,ro 
0 0): permission denied
Jun 23 19:03:17 laptop-hostname kernel: [  433.302850] audit: type=1400 
audit(1529751797.832:44): apparmor="DENIED" operation="mount" info="failed 
srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" 
name="/usr/share/fonts/" pid=7471 comm="3" flags="ro, remount, bind"
Jun 23 19:03:17 laptop-hostname kernel: [  433.305652] audit: type=1400 
audit(1529751797.832:45): apparmor="DENIED" operation="mount" info="failed 
srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" 
name="/var/cache/fontconfig/" pid=7471 comm="3" flags="ro, remount, bind"
Jun 23 19:03:17 laptop-hostname kernel: [  433.336540] audit: type=1400 
audit(1529751797.864:46): apparmor="DENIED" operation="capable" 
profile="snap-update-ns.gnome-system-monitor" pid=7478 comm="3" capability=6  
capname="setgid"
Jun 23 19:03:17 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[7456]: cannot update snap 
namespace: cannot drop supplementary groups: operation not permitted
Jun 23 19:03:17 laptop-hostname 
gnome-system-monitor_gnome-system-monitor.desktop[7456]: snap-update-ns failed 
with code 1
Jun 23 19:03:18 laptop-hostname PackageKit: resolve transaction /260_bebcecdc 
from uid 1000 finished with success after 610ms

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

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

Title:
  Apparmor Permission Denied (apparmor="DENIED")

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I try to launch the system monitor but nothing show up.

  journalctl -f 
  Result:
  Jun 23 19:04:24 laptop-hostname audit[8109]: AVC apparmor="DENIED" 
operation="capable" profile="snap-update-ns.gnome-system-monitor" pid=8109 
comm="3" capability=6  capname="setgid"
  Jun 23 19:04:24 laptop-hostname kernel: audit: type=1400 
audit(1529751864.744:47): apparmor="DENIED" operation="capable" 
profile="snap-update-ns.gnome-system-monitor" 

[Desktop-packages] [Bug 1770773] Re: HSP/HFP not working

[Launchpad Bug Tracker]

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

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

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

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

Title:
  HSP/HFP not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Using the 18.04 release, paired bluetooth headsets' do not work in
  HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. Go to sound settings > output tab > try switching mode to HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  Logitech H800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1770773/+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 1778225] Re: Can't switch UI language for single users, only system-wide

[Michael Satke]

Overrides: That is interesting. I ssh-ed frequently until about a year ago 
(from machines inside my WIFI), but not recently.
_

dpkg-query -W gdm3

gdm33.28.2-0ubuntu1.2
_

cat /etc/environment

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

_

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1778225/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

[Owais Lone]

I'm facing the same issue with Ubuntu 18.04 and Kubuntu 18.04. I also
tried a live CD which had the same problem.

I tried Apple Airpods and a Sennheiser headset and had the same issue
with both. For me personally, this is the biggest issue I have with
Ubuntu 18.04 right now as it doesn't let me use a wireless headset for
meetings so it affects my work.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1777218] Re: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: cups-filters (Ubuntu)
   Status: New => Confirmed

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

Title:
  package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  not updating it show that 
  package operation failed:
  The installation or removal of a software package failed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-browsed 1.8.3-2ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   wireless-regdb: Install
   cups-browsed: Configure
   wireless-regdb: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Jun 16 13:14:52 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-26 (140 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LF
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic.efi.signed 
root=UUID=1b2054c6-5e33-4b5a-a888-85abd43fc861 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: cups-filters
  Title: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LF.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LF.504:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555LF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1777218/+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 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption

[Vlad Orlov]

** Tags added: bionic xenial

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

Title:
  upowerd/gnome-power-statistics crash; high CPU, memory consumption

Status in gnome-power-manager package in Ubuntu:
  Confirmed

Bug description:
  Not sure if necessary here since same bug is already on:
  https://bugzilla.redhat.com/show_bug.cgi?id=1427621
  https://bugs.freedesktop.org/show_bug.cgi?id=100626
  https://bugzilla.gnome.org/show_bug.cgi?id=781088

  Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic

  Steps to reproduce:
  1. have a system with a recent kernel (4.10.x or later)
  2. start gnome-power-statistics
  3. go to Pprocessor tab
  4. have a look at gnome-system-monitor or htop

  Result:
  - On Processor section, Wakeups tab: "Processor wakeups pers second: 
GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats."
  - High CPU usage of /usr/lib/upower/upowerd
  - Crash gnome-power-statistics

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

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

Re: [Desktop-packages] [Bug 1777650] Re: gparted failes to start

[marvin]

It appears to look in the wrong place

marvin@X1-18:~$ locate libatkmm-1.6.so.1
/snap/gnome-system-monitor/36/usr/lib/x86_64-linux-gnu/libatkmm-1.6.so.1
/snap/gnome-system-monitor/36/usr/lib/x86_64-linux-gnu/libatkmm-1.6.so.1.1.0
/snap/gnome-system-monitor/45/usr/lib/x86_64-linux-gnu/libatkmm-1.6.so.1
/snap/gnome-system-monitor/45/usr/lib/x86_64-linux-gnu/libatkmm-1.6.so.1.1.0


On Sat, Jun 23, 2018 at 10:59 AM Marvin Rueppel  wrote:

>
> Hi
>
> It gives me this...
>
> marvin@X1-18:~$ sudo apt install --reinstall libgtkmm-2.4-1v5
> [sudo] password for marvin:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
> upgraded.
> Need to get 666 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Get:1 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64
> libgtkmm-2.4-1v5 amd64 1:2.24.5-2 [666 kB]
> Fetched 666 kB in 0s (5'689 kB/s)
> (Reading database ... 220072 files and directories currently installed.)
> Preparing to unpack .../libgtkmm-2.4-1v5_1%3a2.24.5-2_amd64.deb ...
> Unpacking libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) over (1:2.24.5-2) ...
> Setting up libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) ...
> Processing triggers for libc-bin (2.27-3ubuntu1) ...
> marvin@X1-18:~$ sudo gedit
> marvin@X1-18:~$ sudo gparted
> Unit -.mount does not exist, proceeding anyway.
> /usr/sbin/gpartedbin: error while loading shared libraries:
> libatkmm-1.6.so.1: cannot open shared object file: No such file or directory
> marvin@X1-18:~$ sudo apt-get install --reinstall libgtkmm-2.4-1v5
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
> upgraded.
> Need to get 666 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Get:1 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64
> libgtkmm-2.4-1v5 amd64 1:2.24.5-2 [666 kB]
> Fetched 666 kB in 0s (9'254 kB/s)
> (Reading database ... 220072 files and directories currently installed.)
> Preparing to unpack .../libgtkmm-2.4-1v5_1%3a2.24.5-2_amd64.deb ...
> Unpacking libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) over (1:2.24.5-2) ...
> Setting up libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) ...
> Processing triggers for libc-bin (2.27-3ubuntu1) ...
> marvin@X1-18:~$ sudo gparted
> Unit -.mount does not exist, proceeding anyway.
> /usr/sbin/gpartedbin: error while loading shared libraries:
> libatkmm-1.6.so.1: cannot open shared object file: No such file or directory
>
>
>
>
> There is a similar issue with telegram (only when installed through apt
> get)
>
> marvin@X1-18:~$ telegram-desktop
> telegram-desktop: error while loading shared libraries:
> libQt5Network.so.5: cannot open shared object file: No such file or
> directory
>
> Could be an issue during ubuntu install?
>
>
>
> On Thu, Jun 21, 2018 at 11:50 PM Curtis Gedak  wrote:
>
>> Or if that doesn't work use:
>>
>>   sudo apt-get install --reinstall libgtkmm-2.4-1v5
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1777650
>>
>> Title:
>>   gparted failes to start
>>
>> Status in gtkmm2.4 package in Ubuntu:
>>   New
>>
>> Bug description:
>>   Gparted wanted to start
>>
>>   termanal input up to failure
>>
>>   marvin@X1-18:~$ gparted
>>   Unit -.mount does not exist, proceeding anyway.
>>   /usr/sbin/gpartedbin: error while loading shared libraries:
>> libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory
>>   marvin@X1-18:~$ sudo apt-get install libgtkmm-2.4
>>   Reading package lists... Done
>>   Building dependency tree
>>   Reading state information... Done
>>   Note, selecting 'libgtkmm-2.4-1v5' for regex 'libgtkmm-2.4'
>>   Note, selecting 'libgtkmm-2.4-1c2a' for regex 'libgtkmm-2.4'
>>   Note, selecting 'libgtkmm-2.4-dev' for regex 'libgtkmm-2.4'
>>   Note, selecting 'libgtkmm-2.4-doc' for regex 'libgtkmm-2.4'
>>   libgtkmm-2.4-1v5 is already the newest version (1:2.24.5-2).
>>   libgtkmm-2.4-dev is already the newest version (1:2.24.5-2).
>>   ^[[AThe following NEW packages will be installed:
>> libgtkmm-2.4-doc
>>   0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
>>   89 not fully installed or removed.
>>   Need to get 0 B/8'630 kB of archives.
>>   After this operation, 123 MB of additional disk space will be used.
>>   Do you want to continue? [Y/n] ^[[A^C
>>   marvin@X1-18:~$ sudo apt install gparted
>>   Reading package lists... Done
>>   Building dependency tree
>>   Reading state information... Done
>>   gparted is already the newest version (0.30.0-3ubuntu1).
>>   0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>   89 not fully installed or removed.
>>   After this operation, 0 B of additional disk space will be used.
>>   Do you want to continue? [Y/n] y
>>   Setting up gir1.2-gtk-2.0 (2.24.32-1ubuntu1) ...
>>   

Re: [Desktop-packages] [Bug 1777650] Re: gparted failes to start

[marvin]

Hi

It gives me this...

marvin@X1-18:~$ sudo apt install --reinstall libgtkmm-2.4-1v5
[sudo] password for marvin:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 666 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64
libgtkmm-2.4-1v5 amd64 1:2.24.5-2 [666 kB]
Fetched 666 kB in 0s (5'689 kB/s)
(Reading database ... 220072 files and directories currently installed.)
Preparing to unpack .../libgtkmm-2.4-1v5_1%3a2.24.5-2_amd64.deb ...
Unpacking libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) over (1:2.24.5-2) ...
Setting up libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
marvin@X1-18:~$ sudo gedit
marvin@X1-18:~$ sudo gparted
Unit -.mount does not exist, proceeding anyway.
/usr/sbin/gpartedbin: error while loading shared libraries:
libatkmm-1.6.so.1: cannot open shared object file: No such file or directory
marvin@X1-18:~$ sudo apt-get install --reinstall libgtkmm-2.4-1v5
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 666 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64
libgtkmm-2.4-1v5 amd64 1:2.24.5-2 [666 kB]
Fetched 666 kB in 0s (9'254 kB/s)
(Reading database ... 220072 files and directories currently installed.)
Preparing to unpack .../libgtkmm-2.4-1v5_1%3a2.24.5-2_amd64.deb ...
Unpacking libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) over (1:2.24.5-2) ...
Setting up libgtkmm-2.4-1v5:amd64 (1:2.24.5-2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
marvin@X1-18:~$ sudo gparted
Unit -.mount does not exist, proceeding anyway.
/usr/sbin/gpartedbin: error while loading shared libraries:
libatkmm-1.6.so.1: cannot open shared object file: No such file or directory



There is a similar issue with telegram (only when installed through apt get)

marvin@X1-18:~$ telegram-desktop
telegram-desktop: error while loading shared libraries: libQt5Network.so.5:
cannot open shared object file: No such file or directory

Could be an issue during ubuntu install?


On Thu, Jun 21, 2018 at 11:50 PM Curtis Gedak  wrote:

> Or if that doesn't work use:
>
>   sudo apt-get install --reinstall libgtkmm-2.4-1v5
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1777650
>
> Title:
>   gparted failes to start
>
> Status in gtkmm2.4 package in Ubuntu:
>   New
>
> Bug description:
>   Gparted wanted to start
>
>   termanal input up to failure
>
>   marvin@X1-18:~$ gparted
>   Unit -.mount does not exist, proceeding anyway.
>   /usr/sbin/gpartedbin: error while loading shared libraries:
> libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory
>   marvin@X1-18:~$ sudo apt-get install libgtkmm-2.4
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   Note, selecting 'libgtkmm-2.4-1v5' for regex 'libgtkmm-2.4'
>   Note, selecting 'libgtkmm-2.4-1c2a' for regex 'libgtkmm-2.4'
>   Note, selecting 'libgtkmm-2.4-dev' for regex 'libgtkmm-2.4'
>   Note, selecting 'libgtkmm-2.4-doc' for regex 'libgtkmm-2.4'
>   libgtkmm-2.4-1v5 is already the newest version (1:2.24.5-2).
>   libgtkmm-2.4-dev is already the newest version (1:2.24.5-2).
>   ^[[AThe following NEW packages will be installed:
> libgtkmm-2.4-doc
>   0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
>   89 not fully installed or removed.
>   Need to get 0 B/8'630 kB of archives.
>   After this operation, 123 MB of additional disk space will be used.
>   Do you want to continue? [Y/n] ^[[A^C
>   marvin@X1-18:~$ sudo apt install gparted
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   gparted is already the newest version (0.30.0-3ubuntu1).
>   0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>   89 not fully installed or removed.
>   After this operation, 0 B of additional disk space will be used.
>   Do you want to continue? [Y/n] y
>   Setting up gir1.2-gtk-2.0 (2.24.32-1ubuntu1) ...
>   Setting up libltdl-dev:amd64 (2.4.6-2) ...
>   Setting up po-debconf (1.0.20) ...
>   Setting up libglib2.0-dev-bin (2.56.1-2ubuntu1) ...
>   Setting up libcairo-script-interpreter2:amd64 (1.15.10-2) ...
>   Setting up libsigsegv2:amd64 (2.12-1) ...
>   Setting up libpthread-stubs0-dev:amd64 (0.3-4) ...
>   Processing triggers for install-info (6.5.0.dfsg.1-2) ...
>   Setting up libpng-tools (1.6.34-1) ...
>   Processing triggers for libglib2.0-0:amd64 (2.56.1-2ubuntu1) ...
>   Setting up xorg-sgml-doctools (1:1.11-1) ...
>   Setting up libicu-le-hb0:amd64 (1.0.3+git161113-4) ...
>   Setting up 

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Ubuntu Foundations Team Bug Bot]

The attachment "gvfs-smb-browse change to NT1 from RedHat Bugzilla"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

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

Bug description:
  On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because
  of that Nautilus displays "Empty Folder" when clicking "Windows
  Network"

  Nautilus should show smbtree nad host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
  smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by 
the processing engine)
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo 
(pid=5708)
  smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo)
  smb-network: send_reply(0x55b19a2e7820), failed=0 ()
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708)
  smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate)
  smb-network: send_reply(0x55b19a2c30c0), failed=0 ()

  Proposed solution:
  Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla
  [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394
  which implements "change to NT1" in gvfs-smb-browse to browse smbtree to 
aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to 
unsafe NT1 which most users are doing to correct this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Sebastian Byczkowski]

A patch for gvfs-smb-browse to switch to NT1

** Patch added: "gvfs-smb-browse change to NT1 from RedHat Bugzilla"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5155768/+files/smbbackendbrowse-switch-to-NT1.patch

** Also affects: nautilus (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/1778322

Title:
  gvfs-smb-browse can't browse samba/smb tree

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

Bug description:
  On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because
  of that Nautilus displays "Empty Folder" when clicking "Windows
  Network"

  Nautilus should show smbtree nad host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
  smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by 
the processing engine)
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo 
(pid=5708)
  smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo)
  smb-network: send_reply(0x55b19a2e7820), failed=0 ()
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708)
  smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate)
  smb-network: send_reply(0x55b19a2c30c0), failed=0 ()

  Proposed solution:
  Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla
  [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394
  which implements "change to NT1" in gvfs-smb-browse to browse smbtree to 
aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to 
unsafe NT1 which most users are doing to correct this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

[Sebastian Byczkowski]

Simpler form of before posted patch.Ehh

** Patch added: "gvfsbackendbrowse.c change to NT1 from RedHat Bugzilla"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1778322/+attachment/5155769/+files/gvfsbackendbrowse-force-smb1.patch

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

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

Bug description:
  On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because
  of that Nautilus displays "Empty Folder" when clicking "Windows
  Network"

  Nautilus should show smbtree nad host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
  smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by 
the processing engine)
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo 
(pid=5708)
  smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo)
  smb-network: send_reply(0x55b19a2e7820), failed=0 ()
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708)
  smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate)
  smb-network: send_reply(0x55b19a2c30c0), failed=0 ()

  Proposed solution:
  Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla
  [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394
  which implements "change to NT1" in gvfs-smb-browse to browse smbtree to 
aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to 
unsafe NT1 which most users are doing to correct this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+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 1778322] [NEW] gvfs-smb-browse can't browse samba/smb tree

[Sebastian Byczkowski]

Public bug reported:

On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of
that Nautilus displays "Empty Folder" when clicking "Windows Network"

Nautilus should show smbtree nad host on the smb network.

When inputing this command:
killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

You can see the error:
smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the 
processing engine)
smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo 
(pid=5708)
smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo)
smb-network: send_reply(0x55b19a2e7820), failed=0 ()
smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708)
smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate)
smb-network: send_reply(0x55b19a2c30c0), failed=0 ()

Proposed solution:
Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla
[link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394
which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod 
adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe 
NT1 which most users are doing to correct this bug.

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

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


** Tags: browse browsing gvfs-smb-browse smbtree

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

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

Bug description:
  On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because
  of that Nautilus displays "Empty Folder" when clicking "Windows
  Network"

  Nautilus should show smbtree nad host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
  smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by 
the processing engine)
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo 
(pid=5708)
  smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo)
  smb-network: send_reply(0x55b19a2e7820), failed=0 ()
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708)
  smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate)
  smb-network: send_reply(0x55b19a2c30c0), failed=0 ()

  Proposed solution:
  Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla
  [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394
  which implements "change to NT1" in gvfs-smb-browse to browse smbtree to 
aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to 
unsafe NT1 which most users are doing to correct this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+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 1778111] Re: Update to pptp-1.10.0

[Hans Joachim Desserud]

** Tags added: upgrade-software-version

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

Title:
  Update to pptp-1.10.0

Status in pptp-linux package in Ubuntu:
  New

Bug description:
  On 2018-01-18 the pptp team released a new version 1.10.0
  https://sourceforge.net/projects/pptpclient/files/pptp/

  It would be great if you can update ubuntu or debian package too because I 
have a problem which looks fixed in 1.10.0 .
  Thank you in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pptp-linux/+bug/1778111/+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 1778319] [NEW] Error when trying to open Nautilus from desktop with hotkey

[joshas]

Public bug reported:

Click on the desktop, press Ctrl+N (to open new Nautilus window). It results in 
error:
"This location could not be displayed.
Sorry, could not display all the contents of "x-nautilus-desktop:///":
The specified location is not supported"

Using Ubuntu 18.04 with latest updates, Files version 3.26.3

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

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

Title:
  Error when trying to open Nautilus from desktop with hotkey

Status in nautilus package in Ubuntu:
  New

Bug description:
  Click on the desktop, press Ctrl+N (to open new Nautilus window). It results 
in error:
  "This location could not be displayed.
  Sorry, could not display all the contents of "x-nautilus-desktop:///":
  The specified location is not supported"

  Using Ubuntu 18.04 with latest updates, Files version 3.26.3

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