date:20190121

thanks

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

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

Title:
  Mobile Broadband panel still shows "Connected" after removing the SIM
  card

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

Bug description:
  [Reproduce Steps]
   1. Boot to Ubuntu 18.04 desktop and insert a SIM card and make sure can 
mobile connection could work successfully.
   2. Removing the SIM card from the slot.

  [Result]
  Expected Result:
  Mobile Broadband panel should reflect the interruption in network connection 
and toggle off the "Connected" status

  Actual Result:
  Mobile Broadband UI still shows "Connected" even without active network 
connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1812357/+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 577669] Re: Firefox window border dissapears after installing kde.

Reporter found work around
Ubuntu and Firefox versions long time EOL
No comments on report for over 6 years
Closing as "Invalid"


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Firefox window border dissapears after installing kde.

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  After restarting my laptop after installing KDE (Whilst i still have
  gnome) Firefox no longer has a window border, and overlaps the gnome
  panel, it is the same in KDE also, but it only does it in Firefox, all
  other windows are ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Sun May  9 04:28:29 2010
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/577669/+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 1273990] Re: firefox crashed with SIGSEGV in mozalloc_abort()

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  firefox crashed with SIGSEGV in mozalloc_abort()

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Just browsing a couple of sites (three tabs open IRC).

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: firefox 25.0+build3-0ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  javier 2362 F pulseaudio
  BuildID: 20131028112446
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Jan 29 09:14:55 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-27 (123 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.2)
  IpRoute:
   default via 192.168.0.4 dev eth0  proto static 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.171  metric 
1
  Plugins:
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   Java(TM) Plug-in 10.51.2 - 
/usr/lib/jvm/java-7-oracle/jre/lib/amd64/libnpjp2.so
  PrefSources: prefs.js
  ProcCmdline: /usr/lib/firefox/firefox
  ProcEnviron:
   LANGUAGE=gl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=gl_ES.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=25.0/20131028112446 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  Signal: 11
  SourcePackage: firefox
  StacktraceTop:
   mozalloc_abort(char const*) () from /usr/lib/firefox/libmozalloc.so
   NS_DebugBreak () from /usr/lib/firefox/libxul.so
   ?? () from /usr/lib/firefox/libxul.so
   _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  Title: firefox crashed with SIGSEGV in mozalloc_abort()
  UpgradeStatus: Upgraded to trusty on 2014-01-27 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  WifiSyslog: Jan 29 09:14:54 javier--15-PC kernel: [ 3076.228858] 
plugin-containe[5345]: segfault at 7f02f1976ff0 ip 7f03112454de sp 
7f02e938aa58 error 4 in libc-2.18.so[7f03110f2000+1bc000]
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18FE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 82.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd10/23/2012:svnHewlett-Packard:pnHPPavilionSleekbook15PC:pvr087E103B590320100:rvnHewlett-Packard:rn18FE:rvr82.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Sleekbook 15 PC
  dmi.product.version: 087E103B590320100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1273990/+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 1719038] Re: X Server crashes during log in VM since 16.04.2

2019-01-21 Thread Gannet

** Attachment added: "Coud not start ksmserver error while login in VM"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1719038/+attachment/5230963/+files/KSM_error.png

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

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  Unknown
Status in qemu package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+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 1719038] Re: X Server crashes during log in VM since 16.04.2

2019-01-21 Thread Gannet

The issue still in 18.10 host and 18.04 VM. Please, look the attachment
above.

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

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  Unknown
Status in qemu package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+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 1809129] Re: Window previews have inconsistent ordering

2019-01-21 Thread Will Cooke

** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic)

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

Title:
  Window previews have inconsistent ordering

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Upstream bug:  https://github.com/micheleg/dash-to-dock/issues/639

  The window previews available in d-2-d change order so that the most
  recently used one is always at the top.  This causes confusion as the
  window which was at the bottom last time you clicked on the icon is
  now at the top.

  This has been fixed upstream to keep the previews in the same order
  that the windows were created.

  [ Impact ]

  Windows previews in ubuntu dock change order so that the top one is
  always the most recently used, causing confusion.

  [ Test case ]

  - Open two window instances of a program (say, nautilus)
  - Click in the ubuntu dock icon to select the window to focus
  - Choose one at the bottom
  - Click again in the dock icon
  - The one that was at the bottom before (and now focused) should still be in 
the
same position

  [ Regression potential ]

  No windows in popup selector could be visible at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1809129/+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 1757068] Re: Night light brakes when screen dims

hum, when you write "nightlight is deactivated" you mean it's on but get
deactivated by the dimming? or is it off? would it be possible to get a
debug log from gnome-settings-daemon (by editing the
org.gnome.SettingsDaemon.Color.desktop Exec entry and adding --debug for
example and then getting the journal log)?

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

Title:
  Night light brakes when screen dims

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

Bug description:
  I'm using the night light function in Budgie which is set to a
  temperature of 4000 and the schedule is set from sunset to sunrise.
  When my display dims after X minutes of inactivity the night light
  function breaks which results in a much blue-er screen. When I move my
  mouse the dimming effect dissapears but and the temperature and
  brightness of my screen go back to the default value as if the night
  light function isn't on. Disabling and enabling the night light
  function fixes the issue until my screen dims again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1757068/+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 621879] Re: Ubuntu Firefox handles DNS failure poorly

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Ubuntu Firefox handles DNS failure poorly

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  When the primary DNS server is set to the wrong address, Ubuntu
  Firefox takes 10 to 15 seconds to look up URLs. The problem does not
  occur with Firefox on Windows XP, and appears to be much less severe
  with Firefox on Fedora 13 or with Google Chrome.  It does not appear
  to be an ipv6 problem.

  
  Steps to reproduce:
  1. Set 192.68.0.1 (incorrect value) as the primary DNS and 208.67.220.220 
(OpenDNS) as the secondary. In my case this I am using a WRT54GL router with 
DHCP, so the DNS was determined by the router, and these settings were in the 
router.

  2. Reboot to make sure you are using OpenDNS. Verify the server used by typing
  nslookup www.google.com .

  3. With Ubuntu Firefox 3.6.8, go to
  http://www.utexas.edu/world/univ/alpha/ and pick an obscure
  university. Open the Web site by  clicking. Do this for several
  universities. (Other Web sites could be used, but these (1) tend to
  load from a single server and (2) are unlikely to be cached locally or
  by remote DNS, thereby simplifying testing.)

  
  Results
  1. The status line displays "Looking up [URL address] ..." for 10 to 15 
seconds. This is reproducible.

  2. If the primary DNS is set correctly and the computer is rebooted,
  the problem is solved and the lookup is almost instantaneous. (Primary
  DNS set to 192.168.0.1 (the modem) instead of 192.68.0.1 in the
  router; primary DNS in the modem was left at 68.94.156.1 [Southwestern
  Bell].)

  
  Other diagnostic information (all tests run with primary server set 
incorrectly)
  1. Nslookup returns the IP address in 0 to 2 seconds. Thus, the system 
appears to be handling the lookup much faster than Firefox.

  2. Even if nslookup is used immediately before Firefox, Firefox is
  still slow. Thus, IP address caching (if it occurred) did not speed up
  Firefox.  Dnsmasq is not installed.

  3. I never observed the problem with Windows XP (I tested on the same
  machine). Name resolution is almost instantaneous.

  4. I have not tested much with other browsers or other OS's, but
  Google Chrome (Ubuntu) and Fedora 13 (Firefox, live CD) are much
  faster. Typically 4 to 5 seconds, as opposed to 10-15 seconds with
  Ubuntu Firefox.  Thus, the bug appears to be specific to Ubuntu
  Firefox, or to a specifically Ubuntu component.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/621879/+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 1743976] Re: gnome-shell is wasting CPU repainting unchanging panels

** Description changed:

  gnome-shell is wasting CPU repainting an unchanging panel and dock.
  Every time an app window changes all visible actors including the panel
  get repainted. But the panels mostly doesn't change, so should be cached
  via offscreen-redirect instead.
+ 
+ [ Impact ]
+ 
+ Ubuntu dock repaints the dock when a window changes
+ 
+ [ Test case ]
+ 
+ - Maximize a window
+ - Change its content, by acting on it
+ - Monitor gnome-shell CPU usage, and it should be lower than using previous 
dock version
+ 
+ [ Possible regression ]
+ 
+ The dock isn't repainted properly or it could produce artifacts in some
+ scenarios

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

Title:
  gnome-shell is wasting CPU repainting unchanging panels

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  gnome-shell is wasting CPU repainting an unchanging panel and dock.
  Every time an app window changes all visible actors including the
  panel get repainted. But the panels mostly doesn't change, so should
  be cached via offscreen-redirect instead.

  [ Impact ]

  Ubuntu dock repaints the dock when a window changes

  [ Test case ]

  - Maximize a window
  - Change its content, by acting on it
  - Monitor gnome-shell CPU usage, and it should be lower than using previous 
dock version

  [ Possible regression ]

  The dock isn't repainted properly or it could produce artifacts in
  some scenarios

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1743976/+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 1809129] Re: Window previews have inconsistent ordering

** Description changed:

  Upstream bug:  https://github.com/micheleg/dash-to-dock/issues/639
  
  The window previews available in d-2-d change order so that the most
  recently used one is always at the top.  This causes confusion as the
  window which was at the bottom last time you clicked on the icon is now
  at the top.
  
  This has been fixed upstream to keep the previews in the same order that
  the windows were created.
+ 
+ [ Impact ]
+ 
+ Windows previews in ubuntu dock change order so that the top one is
+ always the most recently used, causing confusion.
+ 
+ [ Test case ]
+ 
+ - Open two window instances of a program (say, nautilus)
+ - Click in the ubuntu dock icon to select the window to focus
+ - Choose one at the bottom
+ - Click again in the dock icon
+ - The one that was at the bottom before (and now focused) should still be in 
the
+   same position
+ 
+ [ Regression potential ]
+ 
+ No windows in popup selector could be visible at all

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

Title:
  Window previews have inconsistent ordering

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Upstream bug:  https://github.com/micheleg/dash-to-dock/issues/639

  The window previews available in d-2-d change order so that the most
  recently used one is always at the top.  This causes confusion as the
  window which was at the bottom last time you clicked on the icon is
  now at the top.

  This has been fixed upstream to keep the previews in the same order
  that the windows were created.

  [ Impact ]

  Windows previews in ubuntu dock change order so that the top one is
  always the most recently used, causing confusion.

  [ Test case ]

  - Open two window instances of a program (say, nautilus)
  - Click in the ubuntu dock icon to select the window to focus
  - Choose one at the bottom
  - Click again in the dock icon
  - The one that was at the bottom before (and now focused) should still be in 
the
same position

  [ Regression potential ]

  No windows in popup selector could be visible at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1809129/+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 219755] Re: Visiting the Extension Home Page replaces the saved session

Upstream report closed "RESOLVED WORKSFORME" on 2013-06-21
Download/update extensions now handled differently
Visiting extension home page opens a new tab
So closing as issue fixed


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

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

Title:
  Visiting the Extension Home Page replaces the saved session

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

Bug description:
  Summary: Start up Firefox and have it search for updates to
  Extensions. If it finds any updates, apply them. Once you choose the
  button to apply them it will display a dialog stating that the
  extensions were updated successfully. In that dialog box, right click
  one of the extensions that were updated, and choose Visit Home Page.
  If the user chooses this option it will cause the Firefox instance
  that loads to display only the Extension home page and none of the
  other pages that were part of the previous session.

  Firefox 2.0.0.13
  Kubuntu 7.10

  Steps
  1. Set Firefox to load the previously saved session
  2. Open mutiple tabs in Firefox
  3. Restart Firefox at a point when the there are extensions that need to be 
updated
  4. When Firefox restarts, it should prompt the user to update the extensions 
that it found updates for. Click Install Updates at this dialog box.
  5. After clicking Install Updates, the dialog box will state whether each 
extension was updated successfully. Right click one of the entries and click 
Visit Home Page
  6. Observe whether the tabs that were open in Firefox previously will be 
opened

  Expected Results: When the user clicks Visit Home Page it should open
  the Extension's Home Page in a new tab

  Actual Results: The tabs that were previously opened are not reloaded
  when the user clicks Visit Home Page. Instead the user just gets one
  open tab with the Extension's Home Page loaded.

  This scenario has not been tested with Firefox 3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/219755/+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 1809129] Re: Window previews have inconsistent ordering

2019-01-21 Thread Will Cooke

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Window previews have inconsistent ordering

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  New

Bug description:
  Upstream bug:  https://github.com/micheleg/dash-to-dock/issues/639

  The window previews available in d-2-d change order so that the most
  recently used one is always at the top.  This causes confusion as the
  window which was at the bottom last time you clicked on the icon is
  now at the top.

  This has been fixed upstream to keep the previews in the same order
  that the windows were created.

  [ Impact ]

  Windows previews in ubuntu dock change order so that the top one is
  always the most recently used, causing confusion.

  [ Test case ]

  - Open two window instances of a program (say, nautilus)
  - Click in the ubuntu dock icon to select the window to focus
  - Choose one at the bottom
  - Click again in the dock icon
  - The one that was at the bottom before (and now focused) should still be in 
the
same position

  [ Regression potential ]

  No windows in popup selector could be visible at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1809129/+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 1812373] Re: Desktop is not restored correctly after screen saver

2019-01-21 Thread isparnid

I confirm what Reuben says. I use "gnome on Xorg" at boot time. I just
tried "ubuntu" and "gnome": I still have a grey startup screen.

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

Title:
  Desktop is not restored correctly after screen saver

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines,
  the screen saver stopped working properly.

  When the screen is locked manually (by clicking the lock screen icon),
  the screen either freezes with the desktop still showing, or shows the
  same grey background as the login screen; it does not show the normal
  lock screen image.

  When the screen saver is activated automatically, the screen turns off
  as normal, but when I press a key, the grey background as for the
  login screen is shown (in fact, it's the same as the login screen, but
  without the login widget; that is, the normal icons are shown at the
  top of the screen).

  
  Pressing Ctrl+Alt+F1 switches to the login dialog.

  I can then log in successfully, but all GNOME shell extensions are
  disabled.

  (A simple workaround is then to restart gnome-shell with the "r"
  command from the "Enter a command" dialog.)

  I am marking this bug as a security vulnerability because in the case
  that the screen simply freezes, confidential information may be
  displayed by the failure of the screen shield to activate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 18 10:28:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-11-26 (1514 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1057615] Re: Firefox under KDE changes the mouse cursor

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Firefox under KDE changes the mouse cursor

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I run Firefox under KDE with the GTK+ bridge configured to use the same theme 
as KDE (QTCurve).
  Firefox shows the "normal" mouse cursor while hovering on the application 
window.
  As soon as I open the firefox main menu, the mouse cursor changes shape, it 
becomes smaller while still keeping the same theme as before.
  It's impossible to capture such a bug with the screenshot tool.
  I would expect the mouse pointer to keep it's shape/color/size all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 15.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  enzo   2797 F pulseaudio
   /dev/snd/controlC0:  enzo   2797 F pulseaudio
  BuildID: 20120907231657
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf9df8000 irq 79'
 Mixer name : 'Realtek ALC889'
 Components : 'HDA:10ec0889,104383c0,0014'
 Controls  : 44
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfbcfc000 irq 34'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100200'
 Controls  : 24
 Simple ctrls  : 4
  Channel: Unavailable
  Date: Thu Sep 27 18:09:18 2012
  ForcedLayersAccel: False
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424)
  IpRoute:
   default via 192.168.254.254 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.254.0/24 dev eth0  proto kernel  scope link  src 192.168.254.42  
metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Plugins:
   Google Talk Plugin Video Accelerator - 
/opt/google/talkplugin/libnpgtpo3dautoplugin.so (google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   IcedTea-Web Plugin (using IcedTea-Web 1.2 (1.2-2ubuntu1.2)) - 
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-7-plugin)
   Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657
  RelatedPackageVersions:
   google-talkplugin 3.6.1.0-1
   icedtea-7-plugin  1.2-2ubuntu1.2
   adobe-flashplugin 11.2.202.238-0precise1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd05/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1057615/+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 881310] Re: Proxy settings don't work with firefox

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Proxy settings don't work with firefox

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When setting up to use a proxy server in the network settings dialog, firefox 
is unable to connect anymore: Stays in "connecting ..." / spinning loading 
indicator but nothing happens.
  Entering the proxy settings in firefox directly works, while setting it to 
"Use system settings" will cause the mentioned effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 25 10:41:17 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (4 days ago)
  usr_lib_gnome-control-center:
   deja-dup   20.0-0ubuntu3
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/881310/+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 1417470] Re: PDF+Latex export creates multipage pdf, pages missing

2019-01-21 Thread Chris

I still get this bug with Inkscape 0.92.2 (5c3e80d, 2017-08-06)

The attached image produces 7 pages in the PDF and so is not usable in
latex: https://tex.stackexchange.com/questions/243499/sharelatex-pdf-
inclusion-required-page-does-not-exist-5

** Attachment added: "expCross.svg"
   
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1417470/+attachment/5231007/+files/expCross.svg

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

Title:
  PDF+Latex export creates multipage pdf, pages missing

Status in Inkscape:
  Fix Released
Status in inkscape package in Ubuntu:
  Fix Released
Status in inkscape package in Debian:
  Fix Released

Bug description:
  In 0.91 the z-order information in svg is used to create multipage
  PDF+LaTeX documents as per bug 771957. However, for the SVGs I have
  been converting to PDF+LaTeX in this way, the TeX-file instructs to
  load more pages than the PDF has, for example the PDF has only three
  pages and the TeX file also includes page=4. This basically breaks the
  PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf
  package.

  The bug occurs on OpenSuse 13.1 and Windows 8.1.

  Attached a zip file with two svg files and their broken PDF+LaTeX
  counterparts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1417470/+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 1512056] Re: Firefox continuously crashes when scrolling pages with Flash videos on it

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Does anyone still see a problem related to the one that was reported
using currently supported versions of Firefox and Ubuntu? Please let us
know if you do otherwise this report can be left to expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: firefox
   Status: New => Incomplete

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

Title:
  Firefox continuously crashes when scrolling pages with Flash videos on
  it

Status in Adobe Flash Plugin Tools:
  Incomplete
Status in Mozilla Firefox:
  Incomplete
Status in firefox package in Ubuntu:
  Incomplete
Status in flashplugin-nonfree package in Ubuntu:
  Incomplete

Bug description:
  Sir,
  Firefox crashes either in standard or in Safe Mode when I browse FaceBook 
pages.

  This happens since some weeks back updates, and it has not been fixed
  yet.

  I'm running Ubuntu 14.04.3 LTS Trusty 64 bit with GNOME Fallback GUI
  on AMD Athlon 64 X2 Dual Core 5000+ CPU with 4GB Ram.

  Many thanks for your feedback.
  Regards
  Mauro

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 41.0.2+build2-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marenzi1869 F pulseaudio
  BuildID: 20151015172900
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Nov  1 06:44:21 2015
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-17 (562 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.106  metric 
1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MostRecentCrashID: bp-ea0ab317-e8ba-4bf0-8508-140852150824
  PciNetwork:
   
  PrefSources:
   prefs.js
   
[Profile]/extensions/FasterFox_Lite@BigRedBrent/defaults/preferences/fasterfoxlite.js
   
[Profile]/extensions/{EF522540-89F5-46b9-B6FE-1829E2B572C6}/defaults/preferences/prefs.js
  Profiles: Profile0 (Default) - LastVersion=41.0.2/20151015172900 (In use)
  RelatedPackageVersions:
   totem-mozilla 3.10.1-1ubuntu4
   rhythmbox-mozilla 3.0.2-0ubuntu2
   gnome-shell   3.10.4-0ubuntu5.2
   google-talkplugin 5.41.0.0-1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1512056/+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 99230] Re: [feisty] sftp:// and other system registered handlers broken in FF

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
 Assignee: Mozilla Bugs (mozilla-bugs) => (unassigned)

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  [feisty] sftp:// and other system registered handlers broken in FF

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  When you type in protocol which cannot be handled by firefox, but is
  registered to Gnome system, Firefox does nothing. "Loading" text is
  shortly shown in the status bar, after which it turns to "(Untitled)"
  blank page.

  Suggestion (in this preference order):

  1. Open handlers in corresponding application (e.g. nautilus)

  2. Show an error page

  3. Show an error dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/99230/+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 1562385] Re: Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 0[GFX1]: Unknown image format 0 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknow

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image
  format 0[GFX1]: Unknown image format 0 Crash Annotation
  GraphicsCriticalError: |[0][GFX1]: Unknown image format 0|[1][GFX1]:
  Unknown image format 0[GFX1]: Unknown image format 0

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  i have continue this error as loop when i open firefox from terminal
  and this hit the performances

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 45.0.1+build1-0ubuntu1
  Uname: Linux 4.5.0-cyrus-lb ppc64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20-0ubuntu3
  Architecture: powerpc
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amigaone   4535 F pulseaudio
  BuildID: 20160317093517
  Channel: Unavailable
  CurrentDesktop: MATE
  Date: Sat Mar 26 20:51:20 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-03-05 (21 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha powerpc (20160302)
  IpRoute:
   default via 192.168.1.1 dev eth0 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.102
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-2ubuntu1)) - 
/usr/lib/jvm/java-8-openjdk-powerpc/jre/lib/ppc/IcedTeaPlugin.so 
(icedtea-8-plugin)
   Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=45.0.1/20160317093517 (In use)
  RelatedPackageVersions:
   icedtea-8-plugin 1.6.2-2ubuntu1
   gnome-shell  3.18.4-0ubuntu2
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1562385/+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 393853] Re: Cannot create new process for firefox

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Cannot create new process for firefox

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 9.04
  Release:  9.04

  firefox package version: 3.0.11+build2+nobinonly-0ubuntu0.9.04.1

  When I try to open a new firefox instance, for instance if I want to
  switch to another profile:

  $ firefox -p -no-remote

  ... I expect firefox to open in a new instance and to open the profile
  manager.

  What happens instead is that some script or whatever shows a dialog
  window (see attached image file) telling me firefox is already running
  and not responding, which is partly a lie. It is running, but it is
  indeed responsive -- I just want to open up a new instance. My use
  case is misunderstood.

  Removing the -p switch does not change anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/393853/+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 1809692] Re: distorted lines when using chrome/chromium browser

2019-01-21 Thread Mushegh Rafayelyan

I have tested several days the firefox and also snap package of chromium
and they both don't show that problem.

thanks for the advice of snap package of chromium, that fully satisfies
me.

On Thu, 10 Jan 2019 at 03:40, Daniel van Vugt 
wrote:

> ** Changed in: chromium-browser (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1809692
>
> Title:
>   distorted lines when using chrome/chromium browser
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I get dynamically changing distorted lines when using google chrome
>   browser, I suppose it is due to my graphics card.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3.1
>   ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
>   Uname: Linux 4.4.0-140-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: Tue Dec 25 04:18:51 2018
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-xenial-amd64-20160624-2
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA
> controller])
>  Subsystem: Dell Device [1028:07d0]
>   InstallationDate: Installed on 2018-04-12 (256 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
> 20160624-10:47
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 002: ID 8087:0a2b Intel Corp.
>Bus 001 Device 003: ID 0c45:6717 Microdia
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. Latitude 5480
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed
> root=UUID=72a3879f-b71f-40a0-b09b-ceb983af1dbf ro acpi_rev_override quiet
> splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/30/2018
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.8.2
>   dmi.board.name: 0D0XXK
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A02
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0D0XXK:rvrA02:cvnDellInc.:ct10:cvr:
>   dmi.product.name: Latitude 5480
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.91-2~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Mon Dec 24 22:28:33 2018
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1368
>vendor LGD
>   xserver.version: 2:1.18.4-0ubuntu0.8
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1809692/+subscriptions
>

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

Title:
  distorted lines when using chrome/chromium browser

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I get dynamically changing distorted lines when using google chrome
  browser, I suppose it is due to my graphics card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-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'

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2019-01-21 Thread Vadim Nevorotin

18.10, bug is still here! It's a very basic experience - Ubuntu with
Gnome3 can't make even such simple basic things work! What can we say
about other things, if user can't change keyboard layout in  a proper
way?

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in GNOME Settings Daemon:
  Unknown
Status in Ubuntu Flashback:
  New
Status in Ubuntu GNOME:
  Fix Released
Status in Ubuntu GNOME Flashback:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-control-center package in ALT Linux:
  Unknown
Status in gnome-control-center package in Baltix:
  Confirmed
Status in gnome-control-center package in Gentoo Linux:
  Unknown
Status in gnome-control-center package in Mandriva:
  Unknown

Bug description:
  [Impact]

  Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift,
  etc. Shift, Caps Lock keys are just ignored in settings.

  [Test Case]

  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a combination of two modifier keys such as Ctrl+Shift
  -> the UI should reflect the new keys

  - add at least two input sources through gnome-control-center's text entry
    settings
  - press and release Ctrl+Shift
  -> the current input source should change

  [Regression Potential]

  That UI was not working before, it should only be an improvement (some
  key combos are not working as expected, that's another issue and
  shouldn't be mixed with this one)

  The input switching shortcut might capture other non-modifier
  shortcuts, but users will need to consider this when choosing their
  switching shortcut anyways. For users this bug affects, this
  represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE=sharing).

  You can use the tag keyboard-layout-switching-hotkeys to find related bugs.
  
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys

  For using layout switching hotkeys in Unity Greeter, see bug 1245137.
  For using layout switching hotkeys in GNOME lockscreen, see bug 1244548.
  For using layout switching hotkeys in GNOME FlashBack sessions, see bug 
1687466 (at least ).

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+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 1766230] Re: Strange window matching behaviour between Slack and Chrome

2019-01-21 Thread Jack J

I have this too, but with Slack and Nautilus. Steps to reproduce:

1. Have someone send you a file on Slack.
2. Download the file and click on "Open containing folder".
3. The opened Nautilus window is now grouped with the Slack icon on the 
launcher.

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

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+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 1812373] Re: Desktop is not restored correctly after screen saver

2019-01-21 Thread Reuben Thomas

It's always been grey on Ubuntu GNOME as far as I'm aware.

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

Title:
  Desktop is not restored correctly after screen saver

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines,
  the screen saver stopped working properly.

  When the screen is locked manually (by clicking the lock screen icon),
  the screen either freezes with the desktop still showing, or shows the
  same grey background as the login screen; it does not show the normal
  lock screen image.

  When the screen saver is activated automatically, the screen turns off
  as normal, but when I press a key, the grey background as for the
  login screen is shown (in fact, it's the same as the login screen, but
  without the login widget; that is, the normal icons are shown at the
  top of the screen).

  
  Pressing Ctrl+Alt+F1 switches to the login dialog.

  I can then log in successfully, but all GNOME shell extensions are
  disabled.

  (A simple workaround is then to restart gnome-shell with the "r"
  command from the "Enter a command" dialog.)

  I am marking this bug as a security vulnerability because in the case
  that the screen simply freezes, confidential information may be
  displayed by the failure of the screen shield to activate.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 18 10:28:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-11-26 (1514 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1265249] Re: Firefox does NOT close the session correctly

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Firefox does NOT close the session correctly

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Since some days/weeks i have to kill Firefox via "top" and "kill" to
  end the Firefox session - even it is long time before closed!

  Installed Add-ons:
  - Adblock Edge 2.0.9
  - Downloadhelper 4.9.21
  - NoScript 2.6.8.10
  - Ubuntu Firefox Modifications 2.7
  - Witchhammer 2.0

  .

  Xubuntu 12.04.3

  Linux xubuntu 3.8.0-34-generic #49~precise1-Ubuntu SMP Wed Nov 13
  18:05:00 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  Firefox 26.0+build2-0ubuntu0.12.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1265249/+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 76137] Re: firefox crashes [@nsXMLHttpRequest::StreamReaderFunc]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Firefox since that time.

Do you still see a problem related to the one that you reported using
currently supported versions of Firefox and Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
 Assignee: Mozilla Bugs (mozilla-bugs) => (unassigned)

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  firefox crashes [@nsXMLHttpRequest::StreamReaderFunc]

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  ...  when adding information to family trees on ancestry.co.uk

  Binary package hint: firefox

  I am adding information to personal family trees on www.ancestry.co.uk

  It doesn't crash straight away, I can fill in maybe 3 boxes of
  information for an individual and then it crashes

  the problem report for firefox said to attach this...

  var/crash/_usr_lib_firefox_firefox-bin.1001.crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/76137/+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 1801494] Re: dock missing

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

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

Title:
  dock missing

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  1) Description:   Ubuntu 18.04.1 LTS
  Release:  18.04
  2) $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 0.9.1ubuntu18.04.1
Candidate: 0.9.1ubuntu18.04.1
Version table:
   *** 0.9.1ubuntu18.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  4) dock is there
  5) dock is not there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

The warning looks like https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/187 , we should probably include that fix in the
incoming SRU

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
 Card-2: NVIDIA GM108M [GeForce 940M]
 Display Server: x11 (X.Org 1.19.6 )
 drivers: fbdev (unloaded: modesetting,vesa)
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
 System Locale: LANG=en_US.UTF-8
LC_NUMERIC=es_AR.UTF-8
LC_MONETARY=es_AR.UTF-8
LC_PAPER=es_AR.UTF-8
LC_NAME=es_AR.UTF-8
LC_ADDRESS=es_AR.UTF-8
LC_TELEPHONE=es_AR.UTF-8
LC_MEASUREMENT=es_AR.UTF-8
LC_IDENTIFICATION=es_AR.UTF-8
 VC Keymap: n/a
X11 Layout: es
 X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1809813] Re: unable to configure additional keyboard

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  unable to configure additional keyboard

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After adding a second keyboard to my computer i tried to change the keyboard 
layout. i want a "german" layout for my old keyboard and a "us" layout for my 
new keyboard.
  I tried to create a "inputclass" section in /usr/share/X11/xorg.conf.de" wich 
sets "xkb_layout" to "us" by using "matchUSBID" but the settings do not work.
  The gnome keyboard settings doesn't offer a way to change the layout for a 
specific keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 16:57:41 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['cariboubloc...@git.keringar.xyz']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-07-04 (540 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-06-22 (186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809813/+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 1812190] Re: distorted and disappearing icons on the toolbar at the top

Thank you for your bug report, it's still not clear from the video what
your issue is exactly. Is the issue that the keyboard layout indicator
is missing (which is probably https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/187)?

Also you reported that bug against the pdf viewer evince, that seems
wrong. You probably wanted to describe the issue with the top panel
which is from gnome-shell

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

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

Title:
distorted and disappearing icons on the toolbar at the top

Status in gnome-shell package in Ubuntu:
Incomplete

Bug description:
1. I don't see the language switching icon.
2. I expect to see her switching languages.
3. When installed on a new computer, some icons disappear (language,
network), or the display is distorted, for example, the wi-fi icon is displayed
with a delay of about a minute.

---
1. Не вижу иконки переключения языка.
2. Ожидаю увидеть её переключаясь между языками.
3. При установки на новый компьютер пропадают некоторые иконки (языковая,
сетевая), или искажается отображение, например значёк wi-fi отображается с
запазданием около минуты.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evince 3.28.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 17 15:03:16 2019
InstallationDate: Installed on 2018-08-17 (153 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
(20180228)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to bionic on 2018-12-27 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812190/+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 1809813] Re: unable to configure additional keyboard

if the issue was that the new layout was not listed until a session
restart then it's bug #1802680

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

Title:
  unable to configure additional keyboard

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After adding a second keyboard to my computer i tried to change the keyboard 
layout. i want a "german" layout for my old keyboard and a "us" layout for my 
new keyboard.
  I tried to create a "inputclass" section in /usr/share/X11/xorg.conf.de" wich 
sets "xkb_layout" to "us" by using "matchUSBID" but the settings do not work.
  The gnome keyboard settings doesn't offer a way to change the layout for a 
specific keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 16:57:41 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['cariboubloc...@git.keringar.xyz']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-07-04 (540 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-06-22 (186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809813/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-01-21 Thread PabloAB

Seems [this upstream issue](https://gitlab.gnome.org/GNOME/gnome-
shell/issues/913).

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
 Card-2: NVIDIA GM108M [GeForce 940M]
 Display Server: x11 (X.Org 1.19.6 )
 drivers: fbdev (unloaded: modesetting,vesa)
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
 System Locale: LANG=en_US.UTF-8
LC_NUMERIC=es_AR.UTF-8
LC_MONETARY=es_AR.UTF-8
LC_PAPER=es_AR.UTF-8
LC_NAME=es_AR.UTF-8
LC_ADDRESS=es_AR.UTF-8
LC_TELEPHONE=es_AR.UTF-8
LC_MEASUREMENT=es_AR.UTF-8
LC_IDENTIFICATION=es_AR.UTF-8
 VC Keymap: n/a
X11 Layout: es
 X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1797604]

2019-01-21 Thread Ddv2005

Hello

>If you are very impatient, try the live-cd of the next version of Ubuntu 
>(18.10):
>http://releases.ubuntu.com/18.10/

I tried 18.10 but the same problem. I guess that live-cd use modesetting driver 
by default and it works. But modesetting does not have TearFree options and I 
can't use it.
Also intel driver has the same version (2.99.917+git20171229) for 18.04 & 18.10 
and both have the same problems.

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

Title:
  Xserver opengl problems on i5-8259U

Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I have installed 18.04.1 server on Intel NUC NUC8i5BEH with minimal xinit and 
xserver-xorg-video-intel. But it has 2 major issues:
  1. Huge Xorg CPU usage with intel driver...more than 110% on glxgears without 
vsync (with modesetting driver Xorg has zero CPU usage and very good Opengl 
performance)
  2. on DRI3 glxgears it skip most frames and display one frame every 60-70 
frames but reported FPS is doubled than on DRI2

  to reproduce a problem install fresh server image of 18.04 and then
  install minimal xinit+xserver-xorg-video-intel. Put 20-intel.conf to
  enable intel driver. Run X by startx and then run glxgears.

  20-intel.conf:

  Section "Device"
 Identifier "Intel Graphics"
 Driver "intel"
 Option "TearFree" "true"
  # Option "DRI" "3"
  EndSection

  P.S. Before 18.04 I tried 16.04 with HWE kernel...on stock Xserver and
  Intel driver it just crash. On latest HWE xserver and HWE Intel driver
  it works the same as 18.04 because it has the same versions. But with
  old 1.18 xserver and HWE intel driver it works in DRI2 mode...Xorg CPU
  usage just 10% instead of 110% on xserver 1.19...The only problem -
  poor OPENGL performance (glxgears 5400 fps vs 8000 fps on 1.19
  xserver)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Fri Oct 12 17:27:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea5] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2074]
  MachineType: Intel(R) Client Systems NUC8i5BEH
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b5cc483d-ce2c-11e8-9739-94c691a2ff22 ro
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0048.2018.0919.2013
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72692-303
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0048.2018.0919.2013:bd09/19/2018:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-302:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-303:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i5BEH
  dmi.product.version: J72747-302
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1797604/+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 1797604]

2019-01-21 Thread Ddv2005

Finally I have fixed the problem by compiling and installed latest git
xf86-video-intel driver. Now everything works fine. Thanks.

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

Title:
  Xserver opengl problems on i5-8259U

Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I have installed 18.04.1 server on Intel NUC NUC8i5BEH with minimal xinit and 
xserver-xorg-video-intel. But it has 2 major issues:
  1. Huge Xorg CPU usage with intel driver...more than 110% on glxgears without 
vsync (with modesetting driver Xorg has zero CPU usage and very good Opengl 
performance)
  2. on DRI3 glxgears it skip most frames and display one frame every 60-70 
frames but reported FPS is doubled than on DRI2

  to reproduce a problem install fresh server image of 18.04 and then
  install minimal xinit+xserver-xorg-video-intel. Put 20-intel.conf to
  enable intel driver. Run X by startx and then run glxgears.

  20-intel.conf:

  Section "Device"
 Identifier "Intel Graphics"
 Driver "intel"
 Option "TearFree" "true"
  # Option "DRI" "3"
  EndSection

  P.S. Before 18.04 I tried 16.04 with HWE kernel...on stock Xserver and
  Intel driver it just crash. On latest HWE xserver and HWE Intel driver
  it works the same as 18.04 because it has the same versions. But with
  old 1.18 xserver and HWE intel driver it works in DRI2 mode...Xorg CPU
  usage just 10% instead of 110% on xserver 1.19...The only problem -
  poor OPENGL performance (glxgears 5400 fps vs 8000 fps on 1.19
  xserver)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Fri Oct 12 17:27:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea5] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2074]
  MachineType: Intel(R) Client Systems NUC8i5BEH
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b5cc483d-ce2c-11e8-9739-94c691a2ff22 ro
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0048.2018.0919.2013
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72692-303
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0048.2018.0919.2013:bd09/19/2018:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-302:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-303:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i5BEH
  dmi.product.version: J72747-302
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1797604/+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 990754] Re: gnome-terminal cannot start unless launched as root

Reporter and two users found workaround for problem
Ubuntu and GNOME versions very old
No activity on report for over 6 years so closing

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gnome-terminal cannot start unless launched as root

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  I can't start gnome-terminal from dash. I tried to start it as user
  and  was given "floating point exception (core dumped)" But as root,
  it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.4.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Sun Apr 29 05:01:59 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/990754/+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 1812663] [NEW] Background Color And Text Color Both Wite with Dark Theme

2019-01-21 Thread bananenkasper

Public bug reported:

The background color and the text color are both white when using the
dark layout.

$ cat .config/gtk-3.0/settings.ini 
[Settings]
gtk-application-prefer-dark-theme=1

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gedit 3.30.2-0ubuntu0.18.10.2
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 13:01:50 2019
InstallationDate: Installed on 2017-12-15 (402 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gedit
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (88 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Background Color And Text Color Both Wite with Dark Theme

Status in gedit package in Ubuntu:
  New

Bug description:
  The background color and the text color are both white when using the
  dark layout.

  $ cat .config/gtk-3.0/settings.ini 
  [Settings]
  gtk-application-prefer-dark-theme=1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gedit 3.30.2-0ubuntu0.18.10.2
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 13:01:50 2019
  InstallationDate: Installed on 2017-12-15 (402 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to cosmic on 2018-10-24 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1812663/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

Thank you for your bug report.
- What desktop session do you use?
- What keyboard layouts do you have configued in GNOME?
- Could you add your journalctl log after getting the issue?

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
 Card-2: NVIDIA GM108M [GeForce 940M]
 Display Server: x11 (X.Org 1.19.6 )
 drivers: fbdev (unloaded: modesetting,vesa)
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
 System Locale: LANG=en_US.UTF-8
LC_NUMERIC=es_AR.UTF-8
LC_MONETARY=es_AR.UTF-8
LC_PAPER=es_AR.UTF-8
LC_NAME=es_AR.UTF-8
LC_ADDRESS=es_AR.UTF-8
LC_TELEPHONE=es_AR.UTF-8
LC_MEASUREMENT=es_AR.UTF-8
LC_IDENTIFICATION=es_AR.UTF-8
 VC Keymap: n/a
X11 Layout: es
 X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1812668] [NEW] package libreoffice-common (not installed) failed to install/upgrade: попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете openoffice-debian-men

2019-01-21 Thread Артём

Public bug reported:

Provide details about the issue.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libreoffice-common (not installed)
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Jan 18 16:00:01 2019
ErrorMessage: попытка перезаписать «/usr/bin/soffice», который уже имеется в 
пакете openoffice-debian-menus 4.1.6-9790
InstallationDate: Installed on 2018-10-30 (83 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: libreoffice
Title: package libreoffice-common (not installed) failed to install/upgrade: 
попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете 
openoffice-debian-menus 4.1.6-9790
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-hook-error apport-package 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/1812668

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете
  openoffice-debian-menus 4.1.6-9790

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Provide details about the issue.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Jan 18 16:00:01 2019
  ErrorMessage: попытка перезаписать «/usr/bin/soffice», который уже имеется в 
пакете openoffice-debian-menus 4.1.6-9790
  InstallationDate: Installed on 2018-10-30 (83 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете 
openoffice-debian-menus 4.1.6-9790
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812668/+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 1369237] Re: nautilus doesn't hide dragged filename

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. You reported this bug some
time ago and there have been many changes in Ubuntu since that time.
Your problem may have been fixed with some of the updates.

It would help us a lot if you could test on a currently supported Ubuntu
version. When you test it and it is still an issue, kindly upload the
updated logs by running only once in a terminal:

apport-collect 

and then change the status of the bug back to "New".

Please add any additional information that you think might be relevant.
Alternatively, please confirm that this is no longer a problem and that
we can close the bug report. If we do not hear from you this bug report
will expire in approximately 60 days time.

Thank you again
Paul White
[Ubuntu Bug Squad]

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

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

Title:
  nautilus doesn't hide dragged filename

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Very very rare it happens that after dragging filename (when renaming)
  its gray image stays after cancelling the operation. I don't see a way
  of removing it but killing nautilus' process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1369237/+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 1374808] Re: Copying speed is decreased

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. You reported this bug some
time ago and there have been many changes in Ubuntu since that time.
Your problem may have been fixed with some of the updates.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

It would help us a lot if you could test on a currently supported Ubuntu
version. When you test it and it is still an issue, kindly upload the
updated logs by running only once in a terminal:

apport-collect 1374808

and then change the status of the bug back to "New".

Please add any additional information that you think might be relevant
to enable us to possibly reproduce the issue. Alternatively, please
confirm that this is no longer a problem and that we can close the bug
report. If we do not hear from you this bug report will expire in
approximately 60 days time.

Thank you again
Paul White
[Ubuntu Bug Squad]


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

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

Title:
  Copying speed is decreased

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When I copy something on my usb disk drive the speed keeps getting
  slower and slower.From 25 mb/sec to 3 mb/sec...I am using Ubuntu
  13.10...What is happening?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1374808/+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 1812583] [NEW] libpaper1:amd64 package post-installation scriptreturned error status 1 during upgrade from Xenial 16.04 LTS to Bionic 18.04 LTS

You have been subscribed to a public bug:

Bug already reported as Bug #1770878.
My experience and output is the same.

Is there any workaround at this point?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.29
ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 20 11:27:49 2019
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to bionic on 2019-01-20 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages xenial2bionic
-- 
libpaper1:amd64 package post-installation scriptreturned error status 1 during 
upgrade from Xenial 16.04 LTS to Bionic 18.04 LTS
https://bugs.launchpad.net/bugs/1812583
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to texlive-base in Ubuntu.

-- 
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 645896] Re: When click on Home, VLC starts

Reporter given work-around to fix issue
GNOME 2 package is obsolete
No activity here for over 8 years so closing


** Changed in: nautilus (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  When click on Home, VLC starts

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: software-center

  When launching Dossier personnel(Home) Documents etc VLC is launched! I can 
access Home Documents etc only through Poste de travail(My computer)!...If I 
remove VLC it's ok? But..I need VLC to read videos movies that cannot be read 
with the gnu linux native video reader.
  I am on 10.10

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: software-center 2.1.22.4
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Thu Sep 23 10:54:46 2010
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.10
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  Package: nautilus 1:2.32.0-0ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Tags: maverick
  Uname: Linux 2.6.35-22-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/645896/+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 1812683] [NEW] rhythmbox crashes when trying to play music

2019-01-21 Thread Götz Waschk

Public bug reported:

Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault.
0x77183384 in gtk_tree_view_get_column ()
   from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
(gdb) bt
#0  0x77183384 in gtk_tree_view_get_column () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#1  0x76ecd5fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#2  0x76ece792 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x76ecf445 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x7718d1fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#5  0x710bedae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#6  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#7  0x76be3ced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7700f7fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x7700c78e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#17 0x7700dcdb in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#18 0x7701099e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#19 0x76fde1e1 in gtk_event_controller_handle_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x7719d85b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#21 0x77b46642 in  () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
#22 0x7705815b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#23 0x76be310d in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x76bf605e in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x76bfe0af in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x7719fb04 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#28 0x770551ce in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#29 0x770572a8 in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#30 0x75323765 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#31 0x75353f82 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#32 0x76909387 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x769095c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x7690964c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x737e7e3d in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#36 0x77aa0b09 in rb_application_run () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
#37 0x4d57 in main ()

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 16:14:12 2019
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (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 gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1812683

Title:
  rhythmbox crashes when trying to play music

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault.
  0x77183384 in gtk_tree_view_get_column ()
 from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb) bt
  #0  0x77183384 in gtk_tree_view_get_column () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #1  0x76ecd5fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x76ece792 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #3  0x76ecf445 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #4  0x7718d1fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #5  0x710bedae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #6  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #7

[Desktop-packages] [Bug 1434830] Re: Clicking on Files bookmark doesn't open the requested folder but gives error message

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do and
in which version of Ubuntu otherwise this report can be left to expire
in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  Clicking on Files  bookmark doesn't open the requested folder but
  gives error message

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  Ubuntu and Windows 7 installed on the same PC for dual-boot; on disk there is 
at least one NTFS partition for Windows, and Ubuntu is installed in a different 
partition.

  Steps to reproduce:
  - Open "Files", and navigate to any folder in the NTFS partition;
  - Bookmark that folder (e.g. with Ctrl+D);
  - Reboot the PC and log in with Ubuntu;
  - Open "Files", and click on the previously created bookmark (under 
"Bookmarks" on the bar to the left);
  - An error message pops-up "Unable to find the requested file. Please check 
the spelling and try again"; it should open to the bookmarked folder instead.

  The issue is systematic.

  Workaround:
  - After logging in, and opening "Files", first click on the NTFS partition in 
the bar to the left (under "Devices"), and then click on the bookmark.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 21 15:36:41 2015
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified', 'permissions', 'owner', 'group']"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'permissions', 'owner', 'group', 
'mime_type', 'where']"
  InstallationDate: Installed on 2014-11-25 (115 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1434830/+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 1812668] Re: package libreoffice-common (not installed) failed to install/upgrade: попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете openoffice-debian-menus

2019-01-21 Thread Olivier Tilloy

Please uninstall all upstream debian packages before attempting to
upgrade libreoffice. See https://wiki.ubuntu.com/LibreOfficeBugWrangling
#package_libreoffice-
common_.28not_installed.29_failed_to_install.2Fupgrade:_trying_to_overwrite_.27.2Fusr.2Fbin.2Fsoffice.27
.2C_which_is_also_in_package_openoffice-debian-menus for reference.

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

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете
  openoffice-debian-menus 4.1.6-9790

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Provide details about the issue.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Jan 18 16:00:01 2019
  ErrorMessage: попытка перезаписать «/usr/bin/soffice», который уже имеется в 
пакете openoffice-debian-menus 4.1.6-9790
  InstallationDate: Installed on 2018-10-30 (83 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
попытка перезаписать «/usr/bin/soffice», который уже имеется в пакете 
openoffice-debian-menus 4.1.6-9790
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812668/+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 1810739] Update Released

2019-01-21 Thread Łukasz Zemczak

The verification of the Stable Release Update for libreoffice has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] libreoffice 6.1.4 for cosmic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.1.4 is the fourth bugfix release of the fresh 6.1 line. 
Version 6.1.3 is currently in cosmic.
 For a list of fixed bugs compared to 6.1.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.4/RC2#List_of_fixed_bugs
 (that's a total of 126 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 126 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1810739/+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 1810739] Re: [SRU] libreoffice 6.1.4 for cosmic

This bug was fixed in the package libreoffice-l10n -
1:6.1.4-0ubuntu0.18.10.1

---
libreoffice-l10n (1:6.1.4-0ubuntu0.18.10.1) cosmic; urgency=medium

  * New upstream release (LP: #1810739)
  * debian/patches/apparmor-mesa.diff: removed, as this requires apparmor 2.13

 -- Olivier Tilloy   Wed, 09 Jan 2019
14:04:28 +0100

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 6.1.4 for cosmic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.1.4 is the fourth bugfix release of the fresh 6.1 line. 
Version 6.1.3 is currently in cosmic.
 For a list of fixed bugs compared to 6.1.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.4/RC2#List_of_fixed_bugs
 (that's a total of 126 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 126 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1810739/+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 1810739] Re: [SRU] libreoffice 6.1.4 for cosmic

This bug was fixed in the package libreoffice - 1:6.1.4-0ubuntu0.18.10.1

---
libreoffice (1:6.1.4-0ubuntu0.18.10.1) cosmic; urgency=medium

  * New upstream release (LP: #1810739)
  * debian/patches/apparmor-mesa.diff: removed, as this requires apparmor 2.13

 -- Olivier Tilloy   Wed, 09 Jan 2019
14:04:28 +0100

** Changed in: libreoffice (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 6.1.4 for cosmic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.1.4 is the fourth bugfix release of the fresh 6.1 line. 
Version 6.1.3 is currently in cosmic.
 For a list of fixed bugs compared to 6.1.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.4/RC2#List_of_fixed_bugs
 (that's a total of 126 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 126 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1810739/+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 1812583] Re: libpaper1:amd64 package post-installation scriptreturned error status 1 during upgrade from Xenial 16.04 LTS to Bionic 18.04 LTS

2019-01-21 Thread Till Kamppeter

/usr/bin/tl-paper is part of texlive-base. Moving ...

** Package changed: libpaper (Ubuntu) => texlive-base (Ubuntu)

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

Title:
  libpaper1:amd64 package post-installation scriptreturned error status
  1 during upgrade from Xenial 16.04 LTS to Bionic 18.04 LTS

Status in texlive-base package in Ubuntu:
  New

Bug description:
  Bug already reported as Bug #1770878.
  My experience and output is the same.

  Is there any workaround at this point?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 11:27:49 2019
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2019-01-20 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1812583/+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 844860] Re: cheese crashed with SIGSEGV in g_closure_invoke()

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do and
in which version of Ubuntu otherwise this report can be left to expire
in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: cheese (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  cheese crashed with SIGSEGV in g_closure_invoke()

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  Cheese crashed for no apparent reason

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: cheese 3.0.1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Thu Sep  8 17:29:04 2011
  ExecutablePath: /usr/bin/cheese
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  MachineType: Dell Inc. Studio 1557
  ProcCmdline: cheese
  RelatedPackageVersions:
   cheese3.0.1-2ubuntu2
   cheese-common 3.0.1-2ubuntu2
  SegvAnalysis:
   Segfault happened at: 0x4156a5:  cmp0x30(%rdx),%rax
   PC (0x004156a5) ok
   source "0x30(%rdx)" (0x10030) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cheese
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: cheese crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/23/2010:svnDellInc.:pnStudio1557:pvrA08:rvnDellInc.:rn0KM426:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Studio 1557
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 003: ID 0c45:6417 Microdia Integrated Webcam

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/844860/+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 942843] Re: cheese crashed with SIGSEGV in cogl_object_unref()

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do and
in which version of Ubuntu otherwise this report can be left to expire
in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: cheese (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  cheese crashed with SIGSEGV in cogl_object_unref()

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  Happened during launch of cheese, before the application's main window
  even displays.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: cheese 3.3.90-0ubuntu1
  Uname: Linux 2.6.31.14.27-efikamx armv7l
  ApportVersion: 1.93-0ubuntu2
  Architecture: armhf
  Date: Tue Feb 28 13:33:51 2012
  ExecutablePath: /usr/bin/cheese
  ProcCmdline: cheese
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  RelatedPackageVersions:
   cheese3.3.90-0ubuntu1
   cheese-common 3.3.90-0ubuntu1
  Signal: 11
  SourcePackage: cheese
  StacktraceTop:
   ?? () from /usr/lib/arm-linux-gnueabihf/libcogl.so.5
   cogl_object_unref () from /usr/lib/arm-linux-gnueabihf/libcogl.so.5
   ?? ()
   ?? ()
  Title: cheese crashed with SIGSEGV in cogl_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  lspci:
   Error: command ['lspci', '-vvnn'] failed with exit code 1: pcilib: Cannot 
open /proc/bus/pci
   lspci: Cannot find any working access method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/942843/+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 883484] Re: cheese crashes with baddrawable error message

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do and
in which version of Ubuntu otherwise this report can be left to expire
in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: cheese (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  cheese crashes with baddrawable error message

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  Error message when running from terminal:

  (cheese:24091): Gdk-WARNING **: The program 'cheese' received an X Window 
System error.
  This probably reflects a bug in the program.
  The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 1373 error_code 9 request_code 137 minor_code 9)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the --sync command line
 option to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: cheese 3.2.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Sat Oct 29 08:13:12 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  MachineType: LENOVO INVALID
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.2.0-0ubuntu2
   cheese-common 3.2.0-0ubuntu2
  SourcePackage: cheese
  UpgradeStatus: Upgraded to oneiric on 2011-10-13 (16 days ago)
  dmi.bios.date: 06/24/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 06CN32WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: SPEEDY
  dmi.board.vendor: LENOVO
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr06CN32WW:bd06/24/2008:svnLENOVO:pnINVALID:pvrLenovoIdeaPadY510:rvnLENOVO:rnSPEEDY:rvr1.0:cvnLENOVO:ct10:cvr1.0:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo IdeaPad Y510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/883484/+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 543758] Re: cheese crashed with SIGSEGV when webcam is already in use

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu? Please let us know if you do and
in which version of Ubuntu otherwise this report can be left to expire
in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: cheese (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  cheese crashed with SIGSEGV when webcam is already in use

Status in Cheese:
  Expired
Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cheese

  Not much to say. I have recently (yesterday) upgraded from 9.10 to
  10.4 Beta 1. I just installed Cheese and it crashed after about 5
  seconds. The problem was that mplayer was open and the same time and
  "reading" the webcam ie I had run the command "mplayer /dev/v4l/by-id
  /usb-0402_USB2.0_Camera-video-index0" and that was still running while
  I tried opening cheese. Shutting down Mplayer fixed the problem and
  Cheese is working now.

  So the problems seems to be that Cheese throws a segfault when
  accessing a camera that is already in use.

  ProblemType: Crash
  Architecture: i386
  Date: Sun Mar 21 23:04:18 2010
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/cheese
  NonfreeKernelModules: nvidia
  Package: cheese 2.29.92-0ubuntu1
  ProcCmdline: cheese
  ProcEnviron:
   LANG=da_DK.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: cheese
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/gstreamer-0.10/libgstvideo4linux2.so
   ?? () from /usr/lib/libgstbase-0.10.so.0
   ?? () from /usr/lib/libgstbase-0.10.so.0
   ?? () from /usr/lib/libgstbase-0.10.so.0
  Title: cheese crashed with SIGSEGV
  Uname: Linux 2.6.32-16-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/cheese/+bug/543758/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2019-01-21 Thread Lucia Di Fino

I encounter the exact same problems of Thales Loiola Raveli on an ASUS
14 UX433FN with Linux Mint 19.1 Cinnamon.

When will the patch be added to a Linux Mint-supported kernel version?
Please please please, it's hard to have a brand-new but mute 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/1784485

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/1784485/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

** Attachment added: "hwinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+attachment/5231145/+files/hwinfo.txt

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

Title:
  [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speaker - No sound
  Headset - OK
  Bluetooth earbuds - OK

  Everything is OK on Windows 10.

  
  lsb_release -rd
  Description:KDE neon User Edition 5.14
  Release:18.04

  ALSA version
  alsa-base 1.0.25+dfsg-0ubuntu5

  
  /proc/version_signature
  Ubuntu 4.15.0-43.46-generic 4.15.18

  uname -r
  4.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

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

Title:
  [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speaker - No sound
  Headset - OK
  Bluetooth earbuds - OK

  Everything is OK on Windows 10.

  
  lsb_release -rd
  Description:KDE neon User Edition 5.14
  Release:18.04

  ALSA version
  alsa-base 1.0.25+dfsg-0ubuntu5

  
  /proc/version_signature
  Ubuntu 4.15.0-43.46-generic 4.15.18

  uname -r
  4.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

** Attachment added: "pacmd.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+attachment/5231146/+files/pacmd.txt

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

Title:
  [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speaker - No sound
  Headset - OK
  Bluetooth earbuds - OK

  Everything is OK on Windows 10.

  
  lsb_release -rd
  Description:KDE neon User Edition 5.14
  Release:18.04

  ALSA version
  alsa-base 1.0.25+dfsg-0ubuntu5

  
  /proc/version_signature
  Ubuntu 4.15.0-43.46-generic 4.15.18

  uname -r
  4.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+attachment/5231143/+files/dmesg.txt

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

Title:
  [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speaker - No sound
  Headset - OK
  Bluetooth earbuds - OK

  Everything is OK on Windows 10.

  
  lsb_release -rd
  Description:KDE neon User Edition 5.14
  Release:18.04

  ALSA version
  alsa-base 1.0.25+dfsg-0ubuntu5

  
  /proc/version_signature
  Ubuntu 4.15.0-43.46-generic 4.15.18

  uname -r
  4.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812735] [NEW] Andyrock has to update this placeholder bug :)

Public bug reported:

Something in OSK doesn't work, he knows about it!

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Released

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Released

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => High

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

Title:
  Andyrock has to update this placeholder bug :)

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Something in OSK doesn't work, he knows about it!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812735/+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 1711534] Re: Application list cluttered on a fresh Artful installation

2019-01-21 Thread Jeremy Bicha

The Sundry app folder is being removed.

Please file new separate bugs for any remaining issues.

** Changed in: gnome-menus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Application list cluttered on a fresh Artful installation

Status in gnome-menus package in Ubuntu:
  Invalid

Bug description:
  GNOME Shell application list contains many rarely-used and sometimes
  redundant app icons like:

  * 3 different icons for fcitx
  * 2 icons for OnBoard (OnBoard settings are accessible from OnBoard itself)
  * ImageMagick (Most probably rarely used, especially when there's also EOG)
  * Language Support, Input Method (There's a language panel in 
gnome-control-center, so this looks like a unity-control-center leftover)

  Because of that, the application list is 3 pages long, making other
  apps unnecessarily hard to find.

  One way to solve that would be to pack rarely-used, but still useful
  stuff into GNOME's Sundry app folder. Completely redundant icons can
  probably be just removed.

  Original suggestion: https://didrocks.fr/2017/08/03/ubuntu--
  guadec-2017-and-plans-for-gnome-shell-migration/#comment-3455664382

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1711534/+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 1711534] Re: Application list cluttered on a fresh Artful installation

2019-01-21 Thread Jeremy Bicha

The Sundry app folder is being removed from Ubuntu 19.04.

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

Title:
  Application list cluttered on a fresh Artful installation

Status in gnome-menus package in Ubuntu:
  Invalid

Bug description:
  GNOME Shell application list contains many rarely-used and sometimes
  redundant app icons like:

  * 3 different icons for fcitx
  * 2 icons for OnBoard (OnBoard settings are accessible from OnBoard itself)
  * ImageMagick (Most probably rarely used, especially when there's also EOG)
  * Language Support, Input Method (There's a language panel in 
gnome-control-center, so this looks like a unity-control-center leftover)

  Because of that, the application list is 3 pages long, making other
  apps unnecessarily hard to find.

  One way to solve that would be to pack rarely-used, but still useful
  stuff into GNOME's Sundry app folder. Completely redundant icons can
  probably be just removed.

  Original suggestion: https://didrocks.fr/2017/08/03/ubuntu--
  guadec-2017-and-plans-for-gnome-shell-migration/#comment-3455664382

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1711534/+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 1812699] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.

2019-01-21 Thread James

Public bug reported:

Error/crash occurred while installing.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Mon Jan 21 10:51:27 2019
DuplicateSignature:
 package:nvidia-340:(not installed)
 Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-HmQWyL/094-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-390 390.77-0ubuntu0.18.04.1
InstallationDate: Installed on 2019-01-20 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package
  nvidia-utils-390 390.77-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  Error/crash occurred while installing.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Jan 21 10:51:27 2019
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-HmQWyL/094-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in 
package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2019-01-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1812699/+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 1812014] Re: keyboard not responding after suspend after some time

2019-01-21 Thread Krzysztof

Hi,
I mentioned the performance problem because as I believe it is connected with 
not responding keyboard. If I notice a performance problem for instance during 
watching yt video I know that keyboard stopped working.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1812699] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-390 390.77

2019-01-21 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package
  nvidia-utils-390 390.77-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  Error/crash occurred while installing.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Jan 21 10:51:27 2019
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-HmQWyL/094-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in 
package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-390 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2019-01-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-390 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1812699/+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 1018677] Re: scanner doesn't work on bootup

2019-01-21 Thread Thomas Zahreddin

I updated libusb-0.1.so.4 to libusb-dev in ubuntu 18.04 LTS and the
error was gone.

BTW: i am astonished how such an error can remain so long in the
operating system :-(

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

Title:
  scanner doesn't work on bootup

Status in libusb package in Ubuntu:
  Confirmed

Bug description:
  When the computer boots up (12.04) with the scanner attached lsusb
  lists the scanner

  
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 03f0:1705 Hewlett-Packard ScanJet 5590
  Bus 002 Device 003: ID 0424:2502 Standard Microsystems Corp. 
  Bus 002 Device 004: ID 0424:2602 Standard Microsystems Corp. USB 2.0 Hub
  Bus 002 Device 005: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card 
Reader
  Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)

  On Bus 002 Device 002

  crw-rw-r--+ 1 root root 189, 129 Jun 27 21:51 /dev/bus/usb/002/002

  But when I run scanimage -L

  
  >scanimage -L

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  doesn't work as root either

  scanimage -L
  [sudo] password for manojav: 

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  
  the only way to get the scanner working again is to power it off (unplug) and 
plug it again. this time its recognized by scanimage -L or xsane running as 
non-root as well root.

  looks like something has got a hold of the device and not letting it
  go! its similar to when a scanning app crashes and leaves things is a
  bad state. only way to clear that is power off the scanner and plug it
  back-in

  this has been happening since 11.10, and now also w/ 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xsane 0.998-3ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Wed Jun 27 22:00:50 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xsane
  UpgradeStatus: Upgraded to precise on 2012-06-26 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/1018677/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-01-21 Thread Petruhin Alexandr

this bug came from this bugfix:

https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt

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

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

Title:
  gnome-shell assert failure: double free or corruption (fasttop) in
  g_free() from g_error_free() from cogl_error_free() from
  cogl_texture_new_with_size() from
  clutter_offscreen_effect_real_create_texture()

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Problem is occurring if dual monitor is used. Second monitor is
  repeatingly blank and activated again. At the bottom it probably
  contains the upper part of the first monitor. I had the same problem
  at 18.04 when using gdm3 without wayland during logon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic i686
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: i386
  AssertionMessage: double free or corruption (fasttop)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  3 21:02:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_signal_restore_set (set=0xbfcd5e9c) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
   __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
   __GI_abort () at abort.c:79
   __libc_message (action=do_abort, fmt=) at 
../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption 
(fasttop)") at malloc.c:5350
  Title: gnome-shell assert failure: double free or corruption (fasttop)
  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/gnome-shell/+bug/1790525/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-01-21 Thread Prashant Gupta

- What desktop session do you use - Gnome 3.28.3
- What keyboard layouts do you have configured in GNOME- De (German) and En (Us 
English)
- Could you add your journalctl log after getting the issue? I have attached 
file below

** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+attachment/5231141/+files/journalctl.txt

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
 Card-2: NVIDIA GM108M [GeForce 940M]
 Display Server: x11 (X.Org 1.19.6 )
 drivers: fbdev (unloaded: modesetting,vesa)
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
 System Locale: LANG=en_US.UTF-8
LC_NUMERIC=es_AR.UTF-8
LC_MONETARY=es_AR.UTF-8
LC_PAPER=es_AR.UTF-8
LC_NAME=es_AR.UTF-8
LC_ADDRESS=es_AR.UTF-8
LC_TELEPHONE=es_AR.UTF-8
LC_MEASUREMENT=es_AR.UTF-8
LC_IDENTIFICATION=es_AR.UTF-8
 VC Keymap: n/a
X11 Layout: es
 X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-01-21 Thread Prashant Gupta

@PabloAB or @Sebastian Becher could you please tell how long one has to
wait before the new update to gnome-shell fixes the issue? I wanted to
avoid the method from Petruhin Alexandr of rolling back to earlier
version of gnome-shell. I can wait for the new update if it doesn't take
much time as you have mentioned above in the link above somebody already
fixed the issue.

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
 Card-2: NVIDIA GM108M [GeForce 940M]
 Display Server: x11 (X.Org 1.19.6 )
 drivers: fbdev (unloaded: modesetting,vesa)
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
 System Locale: LANG=en_US.UTF-8
LC_NUMERIC=es_AR.UTF-8
LC_MONETARY=es_AR.UTF-8
LC_PAPER=es_AR.UTF-8
LC_NAME=es_AR.UTF-8
LC_ADDRESS=es_AR.UTF-8
LC_TELEPHONE=es_AR.UTF-8
LC_MEASUREMENT=es_AR.UTF-8
LC_IDENTIFICATION=es_AR.UTF-8
 VC Keymap: n/a
X11 Layout: es
 X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1103567] Re: "Backup location is too small" should mention how much space is required

This bug was fixed in the package deja-dup - 38.3-1

---
deja-dup (38.3-1) unstable; urgency=medium

  * New upstream release:
- If some files couldn't be backed up, don't override that message
  with successful verification message. (lp: #1371613)
- Tell user how much free space is needed when backup location is tiny
  (lp: #1103567)

 -- Sebastien Bacher   Thu, 17 Jan 2019 11:24:31
+0100

** Changed in: deja-dup (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  "Backup location is too small" should mention how much space is
  required

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  My backup fails with this error:

  Backup location is too small.  Try using one with more space.

  I've since tried to make more space, but I still get this error.

  This error would be much more useful if it told me how much free space
  was required.

  $ lsb_release -d
  Description:  Ubuntu 12.10
  $ dpkg-query -W deja-dup duplicity
  deja-dup  24.0-0ubuntu1
  duplicity 0.6.19-0ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1103567/+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 1371613] Re: Backup result message nonsense when some folders failed AND a verification test was done

This bug was fixed in the package deja-dup - 38.3-1

---
deja-dup (38.3-1) unstable; urgency=medium

  * New upstream release:
- If some files couldn't be backed up, don't override that message
  with successful verification message. (lp: #1371613)
- Tell user how much free space is needed when backup location is tiny
  (lp: #1103567)

 -- Sebastien Bacher   Thu, 17 Jan 2019 11:24:31
+0100

** Changed in: deja-dup (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Backup result message nonsense when some folders failed AND a
  verification test was done

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  There are two bugs here; I'm describing the second, layered on the
  first:

  The first is that even though I have explicitly listed ~/.cache in the
  folders to ignore, I get a complaint that it failed to back up
  something in .cache.

  the second bug is that when it does a password/restore verification
  test (which it does every two months), I end up with a completion
  message that makes no sense: it tells me that the test succeeded, but
  then lists a couple of files, suggesting maybe that they were the only
  ones which were backed up? Or the only ones for which the restore test
  was successful?

  See attached graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 19 09:45:48 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1371613/+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 543758] Re: cheese crashed with SIGSEGV when webcam is already in use

2019-01-21 Thread Thiago Figueiro

Unfortunately I’m no longer in a position to reproduce this bug. Feel
free to close it.

Sent on the run; please excuse my brevity.

> On 22 Jan 2019, at 03:11, Paul White <543...@bugs.launchpad.net> wrote:
> 
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
> 
> Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
> 
> Do you still see a problem related to the one that you reported in a
> currently supported version of Ubuntu? Please let us know if you do and
> in which version of Ubuntu otherwise this report can be left to expire
> in approximately 60 days time.
> 
> Thank you for helping make Ubuntu better.
> 
> Paul White
> [Ubuntu Bug Squad]
> 
> ** Changed in: cheese (Ubuntu)
>   Status: Triaged => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (604196).
> https://bugs.launchpad.net/bugs/543758
> 
> Title:
>  cheese crashed with SIGSEGV when webcam is already in use
> 
> Status in Cheese:
>  Expired
> Status in cheese package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Binary package hint: cheese
> 
>  Not much to say. I have recently (yesterday) upgraded from 9.10 to
>  10.4 Beta 1. I just installed Cheese and it crashed after about 5
>  seconds. The problem was that mplayer was open and the same time and
>  "reading" the webcam ie I had run the command "mplayer /dev/v4l/by-id
>  /usb-0402_USB2.0_Camera-video-index0" and that was still running while
>  I tried opening cheese. Shutting down Mplayer fixed the problem and
>  Cheese is working now.
> 
>  So the problems seems to be that Cheese throws a segfault when
>  accessing a camera that is already in use.
> 
>  ProblemType: Crash
>  Architecture: i386
>  Date: Sun Mar 21 23:04:18 2010
>  Disassembly: => 0x0:Cannot access memory at address 0x0
>  DistroRelease: Ubuntu 10.04
>  ExecutablePath: /usr/bin/cheese
>  NonfreeKernelModules: nvidia
>  Package: cheese 2.29.92-0ubuntu1
>  ProcCmdline: cheese
>  ProcEnviron:
>   LANG=da_DK.utf8
>   SHELL=/bin/bash
>  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
>  SegvAnalysis:
>   Segfault happened at: 0x0:Cannot access memory at address 0x0
>   PC (0x) not located in a known VMA region (needed executable 
> region)!
>  SegvReason: executing NULL VMA
>  Signal: 11
>  SourcePackage: cheese
>  StacktraceTop:
>   ?? ()
>   ?? () from /usr/lib/gstreamer-0.10/libgstvideo4linux2.so
>   ?? () from /usr/lib/libgstbase-0.10.so.0
>   ?? () from /usr/lib/libgstbase-0.10.so.0
>   ?? () from /usr/lib/libgstbase-0.10.so.0
>  Title: cheese crashed with SIGSEGV
>  Uname: Linux 2.6.32-16-generic i686
>  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cheese/+bug/543758/+subscriptions

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

Title:
  cheese crashed with SIGSEGV when webcam is already in use

Status in Cheese:
  Expired
Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cheese

  Not much to say. I have recently (yesterday) upgraded from 9.10 to
  10.4 Beta 1. I just installed Cheese and it crashed after about 5
  seconds. The problem was that mplayer was open and the same time and
  "reading" the webcam ie I had run the command "mplayer /dev/v4l/by-id
  /usb-0402_USB2.0_Camera-video-index0" and that was still running while
  I tried opening cheese. Shutting down Mplayer fixed the problem and
  Cheese is working now.

  So the problems seems to be that Cheese throws a segfault when
  accessing a camera that is already in use.

  ProblemType: Crash
  Architecture: i386
  Date: Sun Mar 21 23:04:18 2010
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/cheese
  NonfreeKernelModules: nvidia
  Package: cheese 2.29.92-0ubuntu1
  ProcCmdline: cheese
  ProcEnviron:
   LANG=da_DK.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: cheese
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/gstreamer-0.10/libgstvideo4linux2.so
   ?? () from /usr/lib/libgstbase-0.10.so.0
   ?? () from /usr/lib/libgstbase-0.10.so.0
   ?? () from /usr/lib/libgstbase-0.10.so.0
  Title: cheese crashed with SIGSEGV
  Uname: Linux 2.6.32-16-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list:

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

** Description changed:

+ Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913
+ 
+ --
+ 
  Steps to reproduce the bug:
  
  1. After normal boot, suspend or lock.
  2. Login again.
  
  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)
  
  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.
  
  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173
  
  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
-Distro: Ubuntu 18.04.1 LTS
+    Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
-Card-2: NVIDIA GM108M [GeForce 940M]
-Display Server: x11 (X.Org 1.19.6 )
-drivers: fbdev (unloaded: modesetting,vesa)
-Resolution: 1920x1080@60.00hz
-OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
-version: 4.5 Mesa 18.0.5
+    Card-2: NVIDIA GM108M [GeForce 940M]
+    Display Server: x11 (X.Org 1.19.6 )
+    drivers: fbdev (unloaded: modesetting,vesa)
+    Resolution: 1920x1080@60.00hz
+    OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
+    version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE
  
  # Consult the keyboard(5) manual page.
  
  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"
  
  BACKSPACE="guess"
-System Locale: LANG=en_US.UTF-8
-   LC_NUMERIC=es_AR.UTF-8
-   LC_MONETARY=es_AR.UTF-8
-   LC_PAPER=es_AR.UTF-8
-   LC_NAME=es_AR.UTF-8
-   LC_ADDRESS=es_AR.UTF-8
-   LC_TELEPHONE=es_AR.UTF-8
-   LC_MEASUREMENT=es_AR.UTF-8
-   LC_IDENTIFICATION=es_AR.UTF-8
-VC Keymap: n/a
-   X11 Layout: es
-X11 Model: pc105
-  X11 Variant: en
-  X11 Options: terminate:ctrl_alt_bksp
+    System Locale: LANG=en_US.UTF-8
+   LC_NUMERIC=es_AR.UTF-8
+   LC_MONETARY=es_AR.UTF-8
+   LC_PAPER=es_AR.UTF-8
+   LC_NAME=es_AR.UTF-8
+   LC_ADDRESS=es_AR.UTF-8
+   LC_TELEPHONE=es_AR.UTF-8
+   LC_MEASUREMENT=es_AR.UTF-8
+   LC_IDENTIFICATION=es_AR.UTF-8
+    VC Keymap: n/a
+   X11 Layout: es
+    X11 Model: pc105
+  X11 Variant: en
+  X11 Options: terminate:ctrl_alt_bksp

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8

[Desktop-packages] [Bug 1812693] [NEW] [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

Public bug reported:

Internal speaker - No sound
Headset - OK
Bluetooth earbuds - OK

Everything is OK on Windows 10.


lsb_release -rd
Description:KDE neon User Edition 5.14
Release:18.04

ALSA version
alsa-base 1.0.25+dfsg-0ubuntu5


/proc/version_signature
Ubuntu 4.15.0-43.46-generic 4.15.18

uname -r
4.15.0-43-generic

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


** Tags: alc1220 amd64 bionic realtek

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1812693/+attachment/5231140/+files/alsa-info.txt

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

Title:
  [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speaker - No sound
  Headset - OK
  Bluetooth earbuds - OK

  Everything is OK on Windows 10.

  
  lsb_release -rd
  Description:KDE neon User Edition 5.14
  Release:18.04

  ALSA version
  alsa-base 1.0.25+dfsg-0ubuntu5

  
  /proc/version_signature
  Ubuntu 4.15.0-43.46-generic 4.15.18

  uname -r
  4.15.0-43-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

PabloAB,

I don't think that the fix mentioned in such issue is the fix for it
though.

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1812697] [NEW] nm-connection-editor: re-enable desktop launcher visibility in GNOME and KDE in Bionic

2019-01-21 Thread Amr Ibrahim

Public bug reported:

Upstream fix:
https://gitlab.gnome.org/GNOME/network-manager-applet/commit/24c5f40e729b0efc7c53f4b33ead006ab7e769a6

This bug is about re-enabling the desktop launcher visibility of nm-
connection-editor. A typical use case of nm-connection-editor is sharing
internet connection with other computers over Ethernet. I cannot do that
in the network panel of gnome-control-center on Bionic.

Gnome and KDE do not allow starting nm-connection-editor from the GUI,
nor provide a graphical way to manage more specialized connections, like
Bridge, Team and Bond ones.

Upstream also changed the displayed name (to Advanced Network
Configuration) to hint users that the tool should be used for
specialized networking configurations.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager-gnome 1.8.10-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 17:04:54 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-11-29 (52 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 default via 192.168.0.1 dev wlp6s0 proto dhcp metric 20600 
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
 192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.5 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
 running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

** Affects: network-manager-applet (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 network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1812697

Title:
  nm-connection-editor: re-enable desktop launcher visibility in GNOME
  and KDE in Bionic

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

Bug description:
  Upstream fix:
  
https://gitlab.gnome.org/GNOME/network-manager-applet/commit/24c5f40e729b0efc7c53f4b33ead006ab7e769a6

  This bug is about re-enabling the desktop launcher visibility of nm-
  connection-editor. A typical use case of nm-connection-editor is
  sharing internet connection with other computers over Ethernet. I
  cannot do that in the network panel of gnome-control-center on Bionic.

  Gnome and KDE do not allow starting nm-connection-editor from the GUI,
  nor provide a graphical way to manage more specialized connections,
  like Bridge, Team and Bond ones.

  Upstream also changed the displayed name (to Advanced Network
  Configuration) to hint users that the tool should be used for
  specialized networking configurations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 17:04:54 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-29 (52 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto dhcp metric 20600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.5 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1812697/+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 1808684] Re: Remove 'Archive Mounter' from options to mount ISO files

This bug was fixed in the package nautilus - 1:3.30.5-1ubuntu1

---
nautilus (1:3.30.5-1ubuntu1) disco; urgency=medium

  * Update to the current stable version
  * debian/mount-archive.desktop, debian/nautilus.install,
debian/patches/03_translations_list_update.patch:
- remove the custom 'mount archive' handler which was added years back,
  nowadays gnome-disk-utility provide a similar feature
  (lp: #1808684)

nautilus (3.30.5-1) unstable; urgency=medium

  * New upstream release
  * Don't have nautilus-data recommend nautilus
  * Restore -Wl,-O1 to our LDFLAGS
  * debian/copyright: nautilus is GPL-3+ instead of GPL-2+

 -- Sebastien Bacher   Thu, 17 Jan 2019 15:46:31
+0100

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

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

Title:
  Remove 'Archive Mounter' from options to mount ISO files

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Steps:

  1. Open nautilus
  2. Right-click on an ISO image file (like a Windows 10 setup ISO file)
  3. Choose 'Open With Other Application'
  4. Choose 'Archive Mounter'
  5. The mounted fie is empty

  I believe that option is legacy, useless and a duplicate of 'Disk
  Image Mounter', which is the right option to choose to mount ISO
  files. When I mount with 'Archive Mounter', I get an empty mounted
  file with nothing in it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 16 12:53:53 2018
  InstallationDate: Installed on 2018-12-06 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1808684/+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 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_ou

2019-01-21 Thread Gert van de Kraats

I created bug #1795760, which describes a Xwayland-abort and got the
status duplicate of 1745799.

Below is a part of the symbolic trace of the abort.

 #7 0x004b6296 in xwl_log_handler (format=0xb7dc71ea "%s@%u: error %d: %s\n", 
args=0xbf9c7994 "\027uܷ\255\001") at ../../../../../hw/xwayland/xwayland.c:1137
 msg = "wl_surface@429: error 2: Failed to create a texture for surface 
429: Failed to create texture 2d due to size/format constraints\n", '\000' 

 #8 0xb7dc5fef in wl_log (fmt=0xb7dc71ea "%s@%u: error %d: %s\n") at 
../src/wayland-util.c:404

Problem can be solved by using slicing at shm_buffer_attach() at
src/wayland/meta-wayland-buffer.c, if size of texture is too large for
graphics card.

I attach a bug-fix to this bug, which is tested during a long time.


** Attachment added: "error9_patch.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+attachment/5231177/+files/error9_patch.txt

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2:
  error 0: invalid global wl_output (20)\n"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashes when plugging in Dell WD15

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  Uname: Linux 4.15.0-rc8+ x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 22:12:41 2018
  DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:077a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9365
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ 
root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash 
wmi.debug_dump_wdg=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.21
  dmi.board.name: 0DVT6M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9365
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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-server/+bug/1745799/+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 1812101]

2019-01-21 Thread Jan-Marek Glogowski

FYI KDE4 used to have its own auto-extension checkbox in the file open
dialog, so the LO KDE4 integration used that KDE setting and skipped
LOs' own handling. Probably that setting doesn't exist anymore, as file
dialogs are now Qt5 based and now LO has to handle the file auto-
extension on its own.

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

2019-01-21 Thread Michael Weghorn

Created attachment 148457
Screenshot of save dialog in KDE 5

For me, with a current daily build of the "master" branch, the file
extension is automatically added when using the "kde5" VCL plugin and
taking these steps:

1) open a new Writer document
2) "File" -> "Save as"
3) type "test" as file name (without ".docx" at the end)
4) select filter "Word 2007-2019 (.docx)"
5) make sure the checkbox "Automatically select filename extension" is checked
6) click "OK"

The attached screenshots shows the dialog at the point in time I click
"OK".

The file is the saved as "test.docx".

Is this the scenario that this bug report is covering or did I
misunderstand anything?

Version: 6.3.0.0.alpha0+
Build ID: 87bf8b7900fe4757bd8494f7a72966915f653eb6
CPU threads: 2; OS: Linux 4.19; UI render: default; VCL: kde5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-19_19:05:11
Locale: en-US (en_DK.UTF-8); UI-Language: en-US
Calc: threaded

With an older build of master (~1 month old, as of commit
6ba8d6533081dab96c00695dd7a908e0f7bcf164; currently don't have a newer
one with gtk3_kde5 available), I can confirm that this works as
described above with kde5, but not with gtk3_kde5. So this looks like it
might be a gtk3_kde5 problem only, but I might be missing something...

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

2019-01-21 Thread Hans P Möller

Created attachment 148473
lubuntu LXQt file saver

Hi Michael,
the problem is in Lubuntu 18.10 which uses LXQt, the checkbox doesn't exist 
there (see attachment). In KDE it exists, as you pointed.

Who creates the checkbox? Libreoffice or the filemanager (in kubuntu
dolphin)?

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

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

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1812101/+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 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_ou

2019-01-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "error9_patch.txt" 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1745799

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2:
  error 0: invalid global wl_output (20)\n"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crashes when plugging in Dell WD15

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  Uname: Linux 4.15.0-rc8+ x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 22:12:41 2018
  DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:077a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9365
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ 
root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash 
wmi.debug_dump_wdg=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.21
  dmi.board.name: 0DVT6M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9365
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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-server/+bug/1745799/+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 1812683] Re: rhythmbox crashes when trying to play music

Could you install the dbgsym
(https://wiki.ubuntu.com/Debug%20Symbol%20Packages) for glib, gtk and
rhythmbox and get a debug backtrace?

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  rhythmbox crashes when trying to play music

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault.
  0x77183384 in gtk_tree_view_get_column ()
 from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  (gdb) bt
  #0  0x77183384 in gtk_tree_view_get_column () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #1  0x76ecd5fa in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #2  0x76ece792 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #3  0x76ecf445 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #4  0x7718d1fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #5  0x710bedae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
  #6  0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  #7  0x76be3ced in g_cclosure_marshal_generic_va () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7700f7fc in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x76be3346 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #14 0x76bfe9ff in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #15 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #16 0x7700c78e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #17 0x7700dcdb in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0x7701099e in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #19 0x76fde1e1 in gtk_event_controller_handle_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #20 0x7719d85b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #21 0x77b46642 in  () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #22 0x7705815b in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #23 0x76be310d in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #24 0x76bf605e in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #25 0x76bfe0af in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #26 0x76bff12f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #27 0x7719fb04 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #28 0x770551ce in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #29 0x770572a8 in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #30 0x75323765 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #31 0x75353f82 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #32 0x76909387 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #33 0x769095c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #34 0x7690964c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #35 0x737e7e3d in g_application_run () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #36 0x77aa0b09 in rb_application_run () at 
/usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  #37 0x4d57 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 16:14:12 2019
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1812683/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell filling up syslog with thousands/millions of entries with
  stack traces ending in osdWindow.js (lines 206/207 in bionic, lines
  223/224 in cosmic)

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/602

  ---

  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

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

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu

[Desktop-packages] [Bug 1812745] [NEW] Rubbish Bin icon on desktop doesn't work, then suddenly starts working

2019-01-21 Thread Jonathan Kamens

Public bug reported:

Immediately after upgrading from cosmic to disco, double-clicking the
"Rubbish Bin" icon on my desktop does nothing.

I try many times, does nothing.

I open a Nautilus window by clicking on the Nautilus icon in the
sidebar, and select "Rubbish Bin" in that window, and I am able to view
it just fine.

Then I double-click the Rubbish Bin icon on the desktop again, and a
window flashes quickly and then disappears.

Then I click it again, and now it is magically working properly, i.e.,
double-clicking opens a Nautilus window displaying the Rubbish Bin.

A couple minutes later I try again, and it's not working again.

Etc.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.30.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 15:48:31 2019
InstallationDate: Installed on 2019-01-02 (19 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages

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

Title:
  Rubbish Bin icon on desktop doesn't work, then suddenly starts working

Status in nautilus package in Ubuntu:
  New

Bug description:
  Immediately after upgrading from cosmic to disco, double-clicking the
  "Rubbish Bin" icon on my desktop does nothing.

  I try many times, does nothing.

  I open a Nautilus window by clicking on the Nautilus icon in the
  sidebar, and select "Rubbish Bin" in that window, and I am able to
  view it just fine.

  Then I double-click the Rubbish Bin icon on the desktop again, and a
  window flashes quickly and then disappears.

  Then I click it again, and now it is magically working properly, i.e.,
  double-clicking opens a Nautilus window displaying the Rubbish Bin.

  A couple minutes later I try again, and it's not working again.

  Etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 15:48:31 2019
  InstallationDate: Installed on 2019-01-02 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1812745/+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 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-21 Thread Josh Holland

> Does using a Wayland session avoid the bug?

Yes, I see no tearing in Totem (or Chrome) when using Wayland. (Note:
after uninstalling the Nvidia drivers (`apt purge nvidia-driver-410 &&
apt autoremove --purge`), I have to boot with `nouveau.modeset=0`,
otherwise boot hangs at Plymouth after entering my disk encryption
password.)

In Wayland, xrandr prints the following:

$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
340mm x 190mm
   1920x1080 59.96*+

> Also, what shell are you using?

If you mean shell-as-in-graphical, and I understand correctly what that
means, then I'm using i3wm. If you mean shell-as-in-CLI, then bash.

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

Title:
  Tearing and/or flickering when using Intel graphics

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811808/+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 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-01-21 Thread Doug McMahon

Maybe I'm missing the point of this bug, if so sorry about that.
The bug seems to be basically about being able to log into a wayland session 
while using nvidia drivers. Though the description has changed a time or two.

So question could be simply rephrased  - Does the fix released imply
that nvidia should be working on 19.04 on all nvidia devices?

It's stated above that - 
"mutter 3.30.2 in 18.10 & 19.04:
  * EGLDevice compiled and working
  * EGLStreams' new build deps are missing so not configured, but compiled in 
anyway by accident because the new build deps were weak, and it's working**"

 "** EGLStreams working means Wayland clients get full Nvidia
acceleration but I thought it was broken for a while because that also
includes 100% CPU use by [kworker/u16:3+events_unbound]. Possible driver
bug? "

What I mentioned is that no m series nvidia i've tested gets nvidia support in 
a wayland session.
(- when logging into wayland one is automatically switched to Intel

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland sessions don't work with the Nvidia driver in 18.04, even
  after enabling them via the kernel command line 'nvidia-
  drm.modeset=1'.

  [Original description]
  Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due 
to following missing changes in mutter 3.28.3-2~ubuntu18.04.2

  commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84
  Author: Miguel A. Vico 
  Date:   Thu Jun 7 16:29:44 2018 -0700

  renderer/native: Choose first EGL config for non-GBM backends

  Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only
  choose EGL configs that match the GBM_FORMAT_XRGB pixel format.
  However, there won't be any EGL config satisfying such criteria for
  non-GBM backends, such as EGLDevice.

  This change will let us choose the first EGL config for the EGLDevice
  backend, while still forcing GBM_FORMAT_XRGB configs for the GBM
  one.

  Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2

  commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b
  Author: Jonas Ådahl 
  Date:   Tue Nov 14 16:08:52 2017 +0800

  renderer/native: Also wrap flip closures for EGLStreams

  When using the EGLStream backend, the MetaRendererNative passed a
  GClosure to KMS when using EGLStreams, but KMS flip callback event
  handler in meta-gpu-kms.c expected a closure wrapped in a closure
  container, meaning it'd instead crash when using EGLStreams. Make the
  flip handler get what it expects also when using EGLStreams by wrapping
  the flip closure in the container before handing it over to EGL.

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

  apt-cache policy mutter
  mutter:
  Installed: 3.28.3-2~ubuntu18.04.2
  Candidate: 3.28.3-2~ubuntu18.04.2
  Version table:
  *** 3.28.3-2~ubuntu18.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages
  100 /var/lib/dpkg/status
  3.28.1-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+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 1812754] [NEW] Libreoffice writer adds blank pages on multiple inputs

2019-01-21 Thread Kevin O'Gorman

Public bug reported:

When I have multiple .txt files on the command line and start
libreoffice writer, it adds (many) blank pages to the documents.  These
blanks contain nothing at all and I have not figured out how to remove
them.  But they are included when I print them.

I'm attaching a file on which this happens.  It contains an anonymized
fragment of the original, repeates a number of times.  I suggest you
create two copies, called perhaps junk1.txt and junk2.txt.

I use the command "soffice junk*" to load them into the writer, and I
get the extra blank pages.

If, however, I just do soffice junk1.txt, I get a document of the
correct size.

I can do that of course, but it is still an annoying and inconvenient
error for my workflow.

---

One hint to debugging: if I do this:

for i in junk1.txt junk2.txt
do
  soffice $i &
done

I see the problem.  If, however, I introduce a delay the problem does
not appear.  Like so:

for i in junk1.txt junk2.txt
do
  sleep 2
  soffice $i &
done

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Jan 21 13:58:01 2019
InstallationDate: Installed on 2018-10-18 (95 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "file that exibits the problem"
   https://bugs.launchpad.net/bugs/1812754/+attachment/5231229/+files/junk1.txt

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

Title:
  Libreoffice writer adds blank pages on multiple inputs

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When I have multiple .txt files on the command line and start
  libreoffice writer, it adds (many) blank pages to the documents.
  These blanks contain nothing at all and I have not figured out how to
  remove them.  But they are included when I print them.

  I'm attaching a file on which this happens.  It contains an anonymized
  fragment of the original, repeates a number of times.  I suggest you
  create two copies, called perhaps junk1.txt and junk2.txt.

  I use the command "soffice junk*" to load them into the writer, and I
  get the extra blank pages.

  If, however, I just do soffice junk1.txt, I get a document of the
  correct size.

  I can do that of course, but it is still an annoying and inconvenient
  error for my workflow.

  ---

  One hint to debugging: if I do this:

  for i in junk1.txt junk2.txt
  do
soffice $i &
  done

  I see the problem.  If, however, I introduce a delay the problem does
  not appear.  Like so:

  for i in junk1.txt junk2.txt
  do
sleep 2
soffice $i &
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jan 21 13:58:01 2019
  InstallationDate: Installed on 2018-10-18 (95 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812754/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

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

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

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

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

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  A temporal workaround is to switching with keyboard (Super+space) or
  mouse. BUT if you then logout on the login screen *when you press the
  first character* of the password the shown selected keyboard layout
  resets.

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812266/+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 1812744] Re: resolved uses only per-link dns servers

2019-01-21 Thread Dimitri John Ledkov

turns of DNS automatic => turn off automatic DNS

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

Title:
  resolved uses only per-link dns servers

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I configured multiple DNS servers in the DNS= option. The manual page
  says:

  "DNS requests are sent to one of the listed DNS servers in parallel to
  suitable per-link DNS servers"

  What I see however, is that each DNS request is sent twice to the same
  server, e.g.:

  
  connect(15, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
  connect(16, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0

  If a per-link server is pushed by network-manager, it's always that
  one. Since my per-link server can lag a lot, that is annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812746] [NEW] desktop icon created by VirtualBox no longer working in disco

2019-01-21 Thread Jonathan Kamens

Public bug reported:

I told VirtualBox to create a desktop icon for one of my virtual
machines. It worked just fine in cosmic.

After upgrading to disco, however, instead of showing up as an icon, it
shows up as a ".desktop" text file, and double-clicking it just opens
the text file in gedit.

I tried deleting and recreating the icon in VirtualBox, and that didn't
help.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.30.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 21 15:52:33 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (19 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages

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

Title:
  desktop icon created by VirtualBox no longer working in disco

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I told VirtualBox to create a desktop icon for one of my virtual
  machines. It worked just fine in cosmic.

  After upgrading to disco, however, instead of showing up as an icon,
  it shows up as a ".desktop" text file, and double-clicking it just
  opens the text file in gedit.

  I tried deleting and recreating the icon in VirtualBox, and that
  didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 15:52:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-02 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812746/+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 1325525] Re: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d

2019-01-21 Thread Nikolai Bozhenov

I can confirm that the issue is still present in 18.04:
- 53-monospace-lcd-filter.conf is not linked into conf.d (not sure if it is a 
bug by itself)
- when the file is linked into conf.d, the warning about broken config appears 
(this is definitely a bug)

** Changed in: fontconfig (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu-trusty, and noticed that in Thunderbird the
  fonts are rendered incorrectly. It seemed that the problem is with
  sub-pixel rendering.

  After much googling and finding nothing I've started to compare the 
/etc/fonts/conf.d dir on my Precise machin with the trusty one. I noticed that 
on trusty the 53-monospace-lcd-filter.conf file is missing from the conf.d dir, 
but is available in the conf.avail.
  After I created the symlink and rebooted, my thunderbird font rendering 
became normal again.

  But now if I start from something from the terminal it says:
  "Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 
10: Having multiple values in  isn't supported and may not work as 
expected"

  So the 1st question, why did you leave out the monospace-lcd-
  filter.conf from the fontconfig conf.d, and the second is why didn't
  you update it so it won't complaing about the multiple test tags.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  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: Mon Jun  2 12:43:15 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:308c]
  MachineType: LENOVO 3492C4G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=a1bd4186-b465-4605-845f-12c9de2dc180 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: F1KT44AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrF1KT44AUS:bd12/21/2012:svnLENOVO:pn3492C4G:pvrThinkCentreEdge72:rvnLENOVO:rn:rvrNODPK:cvnLENOVO:ct3:cvr:
  dmi.product.name: 3492C4G
  dmi.product.version: ThinkCentre Edge72
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jun  2 12:37:17 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9
   inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16498 
   vendor DEL
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325525/+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 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1

2019-01-21 Thread Feris-juan

Hi, I've got the same problem, I've got:
error: Python gobject/dbus may be not installed
error: Plug-in install failed.
 then the script stops and a widow with: lug-In install failed appears.

My Python 2.7.15rc1


My hp-check log:

-desktop:~$ hp-check log
Saving output in log file: /home/juan/hp-check.log

HP Linux Imaging and Printing System (ver. 3.18.12)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball   
has the proper dependencies installed to successfully run.  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both compile- and run-time dependencies).   

Check types:
a. EXTERNALDEP - External Dependencies  
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies   
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: 22-19.1 version is not supported. Using 22-19 versions
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 GNU/Linux
 Host: juan-desktop
 Proc: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 GNU/Linux
 Distribution: 22 19.1
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.18.12
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for 22 distro  
19.1 version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.18.12

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/HP
ppdbase=/usr/share/ppd
doc=/usr/share/doc/hplip-3.18.12
html=/usr/share/doc/hplip-3.18.12
icon=/usr/share/applications
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv/hp
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=no
foomatic-drv-install=no
foomatic-ppd-install=no
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.18.12
restricted-build=no
ui-toolkit=qt4
qt3=no
qt4=yes
qt5=no
policy-kit=no
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=yes
class-driver=no


Current contents of '/var/lib/hp/hplip.state' file:
[plugin]
installed = 1
eula = 1
version = 3.18.12


Current contents of '~/.hplip/hplip.conf' file:
[upgrade]
notify_upgrade = true
last_upgraded_time = 1547657460
pending_upgrade_time = 0
latest_available_version = 3.17.10

[installation]
date_time = 01/21/19 16:39:24
version = 3.18.12


 


--
| COMPILEDEP |
--

 gcc  gcc - GNU Project C and C++ Compiler  
   REQUIRED-   7.3.0   OK -
 make make - GNU make utility to maintain groups of programs
   REQUIRED3.0 4.1 OK -
 libtool  libtool - Library building support services   
   REQUIRED-   2.4.6   OK -


| General Dependencies |


 libcryptolibcrypto - OpenSSL cryptographic library 
   REQUIRED-   1.1.0   OK -
 python-xml   Python XML libraries  
   REQUIRED-   2.2.5   OK -
 libnetsnmp-devel libnetsnmp-devel - SNMP networking library development 
files REQUIRED5.0.9   5.7.3   OK -
 sane-devel   SANE -

[Desktop-packages] [Bug 1812744] Re: resolved uses only per-link dns servers

2019-01-21 Thread Dimitri John Ledkov

** Attachment added: "Screenshot from 2019-01-21 23-11-46.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+attachment/5231234/+files/Screenshot%20from%202019-01-21%2023-11-46.png

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

Title:
  resolved uses only per-link dns servers

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I configured multiple DNS servers in the DNS= option. The manual page
  says:

  "DNS requests are sent to one of the listed DNS servers in parallel to
  suitable per-link DNS servers"

  What I see however, is that each DNS request is sent twice to the same
  server, e.g.:

  
  connect(15, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
  connect(16, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0

  If a per-link server is pushed by network-manager, it's always that
  one. Since my per-link server can lag a lot, that is annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812744] Re: resolved uses only per-link dns servers

2019-01-21 Thread Dimitri John Ledkov

That is intentionally done by NM to prevent leaking DNS queries. Which
is privacy sensitive (ie. do _not_ use "public" dns, to query VPN
encrypted hostnames).

If you do not want to use router configured DNS servers, you can specify
per-connection DNS server overrides in network-manager, which is imho
what you should be doing.

Ie. wipe the resolved.conf settings of DNS=, go into system settings
into each of your connections (ie. the wlan & ethernet one) and in
ipv4/ipv6 tabs, turns of DNS automatic, and specify manual DNS servers
there. Then NM will push those to resolved (note you will need to
reconnect).

It's best to use per-connection DNS servers, and specifically per
connection DNS overrides and configure that all in NM. Do not override /
provide fallbacks in resolved.conf. It is poor taste.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

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

Title:
  resolved uses only per-link dns servers

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I configured multiple DNS servers in the DNS= option. The manual page
  says:

  "DNS requests are sent to one of the listed DNS servers in parallel to
  suitable per-link DNS servers"

  What I see however, is that each DNS request is sent twice to the same
  server, e.g.:

  
  connect(15, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0
  connect(16, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("192.168.0.1")}, 16) = 0

  If a per-link server is pushed by network-manager, it's always that
  one. Since my per-link server can lag a lot, that is annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1

2019-01-21 Thread Till Kamppeter

** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  Unable to install hplip 3.18.12 on linux mint 19.1

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  RESTART OR RE-PLUG IS REQUIRED
  --
  If you are installing a USB connected printer, and the printer was plugged in 
when you started this installer, you
  will need to either restart your PC or unplug and re-plug in your printer 
(USB cable only). If you choose to restart, 
  run this command after restarting: hp-setup (Note: If you are using a 
parallel connection, you will have to restart   
  your PC. If you are using network/wireless, you can ignore and continue). 


  Restart or re-plug in your printer (r=restart, p=re-plug in*,
  i=ignore/continue, q=quit) : i

  
  PRINTER SETUP
  -
  Please make sure your printer is connected and powered on at this time.
  Do you want to setup printer in GUI mode? (u=GUI mode*, i=Interactive mode) : 
u

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Printer/Fax Setup Utility ver. 9.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Searching... (bus=net, timeout=5, ttl=4, search=(None) desc=0, method=slp)
  Segmentation fault
  error:  The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins.  Please run 
'hp-plugin' as normal user to install plug-ins.   Visit  
http://hplipopensource.com  for more infomation. 


  
  Segmentation fault
  error:  The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins.  Please run 
'hp-plugin' as normal user to install plug-ins.   Visit  
http://hplipopensource.com  for more infomation. 

  Done.

  
  RE-STARTING HP_SYSTRAY
  --

  HP Linux Imaging and Printing System (ver. 3.18.12)
  System Tray Status Service ver. 2.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: 
PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)

  :~/Downloads$ hp-plugin

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  
  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir //.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.18.12 Plugin Self Extracting 
Archive.

  HP Linux Imaging and Printing System (ver. 3.18.12)
  Plugin Installer ver. 3.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Plug-in version: 3.18.12
  Installed HPLIP version: 3.18.12
  Number of files to install: 55

  Plugin installation failed
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.

  From kernel log

  
  hplip/plugin.py" name="/etc/xdg/Trolltech.conf" pid=4238 comm="python" 
requested_mask="k" denied_mask="k" fsuid=1000 ouid=0
  [ 9015.754212] audit: type=1400 audit(1548011993.816:100): apparmor="DENIED" 
operation="file_lock" profile="/usr/share/hplip/plugin.py" 
name="/run/sudo/ts/" pid=4240 comm="sudo" requested_mask="k" 
denied_mask="k" fsuid=0 ouid=0
  [ 9015.862631] audit: type=1400 audit(1548011993.924:101): apparmor="DENIED" 
operation="file_lock" profile="/usr/share/hplip/plugin.py" name="/run/utmp" 
pid=4240 comm="sudo" requested_mask="k" denied_mask="k" fsuid=0

[Desktop-packages] [Bug 1796661] Re: Firefox can't download files to an fscrypt protected, unlocked folder

2019-01-21 Thread Troels Liebe Bentsen

The issue is because firefox does a rename from the /tmp folder to the
encrypted home folder, right now fscrypt returns EPERM instead of EXDEV
that would be normal when the operation can not complete because of
crossing a mount point or in this case unencrypted to an encrypted
folder.

The upstream firefox bug is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1521041

But one could argue that the kernel interface is broken and it should
return EXDEV as tools like mv also breaks, there are some patches in the
works but I don't know how far they are, maybe ubuntu could carry them
until they go upstream:

https://patchwork.kernel.org/patch/9943001/

** Bug watch added: Mozilla Bugzilla #1521041
   https://bugzilla.mozilla.org/show_bug.cgi?id=1521041

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

Title:
  Firefox can't download files to an fscrypt protected, unlocked folder

Status in firefox package in Ubuntu:
  New

Bug description:
  My Downloads folder is encrypted by fscrypt. I can save and read files
  in there.  However, for Firefox - all downloads fail and it says only
  "download failed" and offers a button to retry which fails again.
  After a failed attempt, a file is created with a proper file name but
  no content (0 bytes).

  When I changed the download dir to a different non-fscrypted folder,
  everything works properly and files do get properly saved.

  I switched to Chromium and Chromium has no problems downloading files
  into any dirs, regardless encrypted or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: firefox 62.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pkolaczk   3692 F pulseaudio
   /dev/snd/pcmC0D0c:   pkolaczk   3692 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pkolaczk   3692 F...m pulseaudio
  BuildID: 20181002091723
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 12:10:57 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-04-12 (543 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.0.1 dev enxd481d7358c11 proto dhcp metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev enxd481d7358c11 proto kernel scope link src 192.168.0.2 
metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=62.0.3/20181002091723
  RelatedPackageVersions: adobe-flashplugin 1:20180911.1-0ubuntu0.18.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd07/24/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1796661/+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 1811900] Re: SRU 3.28 latest git to bionic