[Desktop-packages] [Bug 1730071] Re: Application icons appear stretched when using scaling

2019-01-17 Thread joshua darnell
+1, Ubuntu 18.01

** Attachment added: "Image of problem."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730071/+attachment/5230105/+files/Screenshot%20from%202019-01-17%2021-16-27.png

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

Title:
  Application icons appear stretched when using scaling

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  The appindicator gnome extension shows the "system tray icons" in the
  upper right corner of the screen. However the icons appear vertically
  stretched. The problem appears to be purely visual, as they still work
  as expected.

  > lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  > apt-cache policy gnome-shell-extension-appindicator
  gnome-shell-extension-appindicator:
Installed: 17.10.1
Candidate: 17.10.1
Version table:
   *** 17.10.1 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730071/+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 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent

2019-01-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  The ssh-agent launcher script fails to relaunch ssh-agent

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  There is an issue with the Xsession, in which logging out and logging
  back in again does not clear environment variables, so the ssh-agent
  script thinks that the agent is already running, and thus does not
  bother to start it again.

  I have altered the script, albeit in not the most pretty way, to
  detect if the agent is already running, and if not, force a restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: x11-common 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Aug 28 17:33:34 2018
  Dependencies: lsb-base 9.20170808ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-32-generic, x86_64: installed
   anbox, 1, 4.15.0-33-generic, x86_64: installed
   nvidia, 396.54, 4.15.0-33-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb]
  InstallationDate: Installed on 2018-08-04 (24 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: MSI MS-7751
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-GD65 (MS-7751)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7751
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 
2018-08-28T17:23:14.025376
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
1:18.3~git180816191500.b618d7e~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 
1:18.3~git180816191500.b618d7e~b~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.99+git1808290006.cba8fe4~b~padoka0
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1806121919.3d39506~b~padoka0
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+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 1812247] Re: ssh-agent fails for ssh-add -c: agent refused operation

2019-01-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1789523 ***
https://bugs.launchpad.net/bugs/1789523

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1789523, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1789523
   The ssh-agent launcher script fails to relaunch ssh-agent

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

Title:
  ssh-agent fails for ssh-add -c: agent refused operation

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means
  of `ssh-add -c` indicating that keys "should be subject to
  confirmation before being used for authentication. In Ubuntu 18.10
  this fails with the error

sign_and_send_pubkey: signing failed: agent refused operation

  To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt-
  get upgrade, log out and log back in (these steps are not required but
  we want to use an up-to-date system). Then:

  $ sudo apt-get install ssh-askpass-gnome
  (...)
  $ # verify that ssh-askpass shows a popup, confirm with Enter
  $ ssh-askpass ; echo $?

  0
  $ ssh-keygen
  (...)
  $ ssh-add -D
  All identities removed.
  $ ssh-copy-id $sshuser@$sshserver
  (...)
  Number of key(s) added: 1
  (...)
  $ ssh $sshuser@$sshserver uname -a
  Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 
GNU/Linux
  $ ssh-add -d
  Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu)
  $ ssh-add -c
  Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): 
  Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa)
  The user must confirm each use of the key
  $ ssh $sshuser@$sshserver uname -a
  sign_and_send_pubkey: signing failed: agent refused operation
  sshuser@server's password: [^C'ed]

  $ ssh-add -l
  2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc 
/home/ubuntu/.ssh/id_rsa (RSA)

  So, our key is loaded, ssh-askpass is working (also confirmed with
  `ssh-add -c 
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1812247/+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 1812321] Re: disco

2019-01-17 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => lvm2 (Ubuntu)

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

Title:
  disco

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I took a screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu18
  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
  Date: Thu Jan 17 22:46:00 2019
  DistUpgraded: 2019-01-15 22:12:59,668 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
  MachineType: Dell Inc. Dell System Inspiron N7110
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-01-16 (2 days ago)
  dmi.bios.date: 05/19/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0YH79Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/19/2011:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn0YH79Y:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Inspiron N7110
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Thu Jan 17 16:53:42 2019
  xserver.configfile: default
  xserver.errors:
   client bug: timer event7 debounce: offset negative (-84ms)
   client bug: timer event7 debounce: offset negative (-112ms)
   client bug: timer event7 debounce short: offset negative (-125ms)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.3-1ubuntu1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1812321/+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 1152226] Re: nautilus no longer remembers view per directory

2019-01-17 Thread tellapu
I would still love to see something happen here. 
Why can this crucial feature not be resurrected? :O
It does not need to be set by default but at least having the option to have 
Nautilus remember the view per directory would be great. This is probably the 
only reason I don't use Nautilus and I would like to return but cannot because 
of this annoying bug. 
Thanks for listening and hopefully somebody can have pity on us and work on 
this. Thanks in advance!

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

Title:
  nautilus no longer remembers view per directory

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Nautilus in raring no longer remembers the view per directory as it
  did in previous releases. This is a functionality regression.

  Steps to reproduce:

  1- Open nautilus from launcher
  2- Go to "Downloads" directory
  3- Switch view to "list"
  4- Close nautilus window
  5- Open nautilus again, and go to "Downloads" directory

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  7 10:50:01 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1004x670+148+241'"
  InstallationDate: Installed on 2012-11-13 (113 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-02-13 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1152226/+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 663386] Re: thunderbird is not properly killed when closing the window

2019-01-17 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  thunderbird is not properly killed when closing the window

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Binary package hint: thunderbird

  closing thunderbird by closing the window sometimes leaves a thunderbird-bin 
proces which doesn't allow to open again the program
  killall thunderbird-bin is needed to kill the process

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: thunderbird 3.1.4+build2+nobinonly-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Oct 19 18:54:38 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=it_IT:fr_FR:fr:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/663386/+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 954336] Re: Font rendering incorrect in XFCE

2019-01-17 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Font rendering incorrect in XFCE

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Using Precise.

  I performed a clean install of Precise (Ubuntu, not XUbuntu) then
  installed xfce4. The font rendering of Thunderbird is incorrect in
  XFCE, but fine in Unity. The problem seems to be that the the sub-
  pixel antialiasing has the wrong pixel order, so font edges are off-
  colour.

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

2019-01-17 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  thunderbird crashed with SIGSEGV in g_main_dispatch()

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  apt-cache policy thunderbird
  thunderbird:
Installed: 1:24.0+build1-0ubuntu1
Candidate: 1:24.0+build1-0ubuntu1
Version table:
   *** 1:24.0+build1-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: thunderbird 1:24.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karma  2275 F pulseaudio
  BuildID: 20130917155107
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Channel: Unavailable
  Date: Wed Oct 16 23:45:09 2013
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-09-30 (381 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.101  
metric 9
  MarkForUpload: True
  Plugins:
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
  PrefSources:
   prefs.js
   
[Profile]/extensions/gsea...@standard8.plus.com/defaults/preferences/gsearch.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
  Prefs:
   extensions.lastAppVersion: "24.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.database.lastMaintenance: 1381107874 (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
   plugin.importedState: true (prefs.js)
  ProcCmdline: /usr/lib/thunderbird/thunderbird
  Profiles: Profile0 (Default) - LastVersion=24.0/20130917155107
  RelatedPackageVersions: rhythmbox-mozilla 2.99.1-0ubuntu1
  RunningIncompatibleAddons: False
  Signal: 11
  SourcePackage: thunderbird
  StacktraceTop:
   ?? ()
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/thunderbird/libxul.so
  Title: thunderbird crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (162 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K53SD.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K53SD
  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.:bvrK53SD.205:bd03/06/2012:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53SD
  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/thunderbird/+bug/1240582/+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 992430] Re: ubuntu update to 12.04 LTS wipes ~/.local data

2019-01-17 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ubuntu update to 12.04 LTS wipes  ~/.local data

Status in gedit package in Ubuntu:
  Expired

Bug description:
  The system invited me to update to the new release 12.04 LTS
  After the install, the following directories (used by gedit 3.4.1) were 
missing
  ~/.local/share/gtksourceview-3.0/language-specs
  ~/.local/share/mime/packages
  These directories contain information for the markup of user-defined 
languages and their mime types.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Tue May  1 17:10:44 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: Upgraded to precise on 2012-05-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/992430/+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 1803655] Re: screen flickering and appearing green colour at screen edges

2019-01-17 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  screen flickering and appearing green colour at screen edges

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  recently ihave installed ubuntu 18.10 version from 16.04 lts but it
  has started screen flickering and screen appearing green at edges of
  the screen before logging the system  the screen flickering is
  appearing and with green color after login the screen flickering
  dissapears .I hope you will find the solution and this problem is
  appearing from 5 days is this a software or hardware problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 16 09:45:49 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:365e]
  InstallationDate: Installed on 2018-11-15 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 10104
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=UUID=72505e1c-0f9f-4860-b3d1-59f626acc7e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT29AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD EM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT29AUS:bd12/03/2012:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvrWin8STDEMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  dmi.product.name: 10104
  dmi.product.sku: LENOVO_MT_1010
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803655/+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 1773180] Re: 7, 000 errors a day of ERROR:value_store_frontend.cc(58)] Error while writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to

2019-01-17 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  7,000 errors a day of ERROR:value_store_frontend.cc(58)] Error while
  writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I have a lot of errors in my journal of the following form:

  ERROR:value_store_frontend.cc(58)] Error while writing
  kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to

  often the same id is reported 2 or 3 times. Many of them are the same
  over and over again.

  May 21 15:42:17 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154217.618607:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:42:17 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154217.619171:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:42:34 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154234.396928:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:42:34 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154234.397539:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:42:34 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154234.401254:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:42:35 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154235.535549:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:42:35 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154235.536151:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:43:12 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154312.925656:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:43:12 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154312.926314:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:43:12 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154312.927266:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:43:13 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154313.818263:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:43:13 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154313.818848:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:43:22 sochi org.gnome.Shell.desktop[18271]: 
[4202:9917:0521/154322.585837:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:43:22 sochi org.gnome.Shell.desktop[18271]: 
[4202:9917:0521/154322.586337:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:43:22 sochi org.gnome.Shell.desktop[18271]: 
[4202:9917:0521/154322.587444:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:43:23 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154323.676650:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:43:23 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154323.677423:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154404.243205:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154404.243478:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154404.247541:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
  May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:10226:0521/154404.801699:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
  May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 

[Desktop-packages] [Bug 1803871] Re: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No proper automute when playback is active on headphones plug in

2019-01-17 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker,
  Internal] No proper automute when playback is active on headphones
  plug in

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  When some audio playback is active (e.g. playing music with Audacious)
  and one plugs in headphones, audio will get played on the headphones,
  but the internal speakers don't really mute. Instead they get "stuck"
  at some constant sound.

  To work-around this bug, one has to pause all audio playback before plugging 
in headphones.
  (Or plug out headphones to stop the "stuck" sound)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   elias  1688 F...m pulseaudio
   /dev/snd/controlC0:  elias  1688 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Nov 18 14:37:51 2018
  InstallationDate: Installed on 2018-10-20 (28 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No auto-mute between outputs
  Title: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, 
Internal] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83BB
  dmi.board.vendor: HP
  dmi.board.version: 60.31
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BB:rvr60.31:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-ch0xx
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803871/+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 1803843] Re: Flickerin screen

2019-01-17 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Flickerin screen

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  I've got blinking screen while doing normal things like: watching YT,
  logging into ubuntu, opening browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)
  .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
  Date: Sun Nov 18 01:38:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3978]
 Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978]
  InstallationDate: Installed on 2018-11-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=cd36c326-7f31-46a2-b6dc-7717e22c5174 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: NO DPK
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Nov 17 22:54:50 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803843/+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 1803907] Re: borroso

2019-01-17 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  borroso

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  falla el controlador de video

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CasperVersion: 1.340.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov 18 20:22:31 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:d613]
  LiveMediaBuild: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/hostname/install/boot/vmlinuz 
debian-installer/custom-installation=/hostname/install/custom-installation 
noprompt quiet splash boot=casper ro debian-installer/locale=es_CL.UTF-8 
keyboard-configuration/layoutcode=latam keyboard-configuration/variantcode= -- 
rootflags=sync
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RQG4110H.86A.0012.2009.1106.1345
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG41RQ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE54511-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRQG4110H.86A.0012.2009.1106.1345:bd11/06/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Nov 18 19:38:02 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803907/+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 1803825] Re: Switching HDMI cable while in sleep mode causes display issue

2019-01-17 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Switching HDMI cable while in sleep mode causes display issue

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  1) I am on laptop screen
  2) connect external 4K TV with hdmi
  3) laptop goes to sleep mode
  4) disconnect external TV and connect external monitor with lower resolution 
than 4k
  5) turn on laptop
  6) error in monitor saying can not support that resolution, no image no image 
on laptop either
  After plugging and unplugging few times, started working fine
  please fix

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 07:50:09 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:063e]
  InstallationDate: Installed on 2018-11-01 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5547
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=03b0f076-7978-4e42-856b-f24ddfebdf8f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803825/+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 1799614] Re: Use new media API

2019-01-17 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu2

---
gnome-software (3.30.6-2ubuntu2) disco; urgency=medium

  * debian/patches/0025-snap-Use-new-media-API.patch:
- Use new snapd media API (LP: #1799614)

 -- Robert Ancell   Fri, 18 Jan 2019
15:26:44 +1300

** Changed in: gnome-software (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.

  [Test Case]
  Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.

  [Regression Potential]
  Possibility of new errors being introduced in updated code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1812321] [NEW] disco

2019-01-17 Thread Steve
Public bug reported:

I took a screen shot

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu18
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
Date: Thu Jan 17 22:46:00 2019
DistUpgraded: 2019-01-15 22:12:59,668 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
MachineType: Dell Inc. Dell System Inspiron N7110
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to disco on 2019-01-16 (2 days ago)
dmi.bios.date: 05/19/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0YH79Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/19/2011:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn0YH79Y:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: Dell System Inspiron N7110
dmi.product.sku: System SKUNumber
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Thu Jan 17 16:53:42 2019
xserver.configfile: default
xserver.errors:
 client bug: timer event7 debounce: offset negative (-84ms)
 client bug: timer event7 debounce: offset negative (-112ms)
 client bug: timer event7 debounce short: offset negative (-125ms)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 disco third-party-packages ubuntu

** Attachment added: "Screenshot from 2019-01-17 22-44-34.png"
   
https://bugs.launchpad.net/bugs/1812321/+attachment/5230083/+files/Screenshot%20from%202019-01-17%2022-44-34.png

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

Title:
  disco

Status in xorg package in Ubuntu:
  New

Bug description:
  I took a screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu18
  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
  Date: Thu Jan 17 22:46:00 2019
  DistUpgraded: 2019-01-15 22:12:59,668 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04d8]
  MachineType: Dell Inc. Dell System Inspiron N7110
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-01-16 (2 days ago)
  dmi.bios.date: 05/19/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0YH79Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 

[Desktop-packages] [Bug 1704162] Re: Add on/off switch for network connectivity check

2019-01-17 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Confirmed => Expired

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

Title:
  Add on/off switch for network connectivity check

Status in gnome-control-center:
  Expired
Status in NetworkManager:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  For Ubuntu 17.10, the Desktop Team would like to enable
  NetworkManager's connectivity check (LP: #997200) to detect captive
  portals. This has been supported by other GNOME distros for a couple
  years. Fedora in particular makes it opt out which we plan to do also
  in Ubuntu.

  This bug is a feature request to add an on/off switch for this
  connectivity check to gnome-control-center. I suggest that it be added
  to the Privacy panel although it might also work in the Network panel.

  I think there are two ways the switch could work. It could either
  write directly to a config file or it could use PackageKit to install
  or uninstall the distro-specific package that contains the
  connectivity config file. The advantage of the separate binary package
  is that it's easy to install or uninstall it for people that don't use
  gnome-control-center.

  See the upstream bug for a bit more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1704162/+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 1799614] Re: Use new media API

2019-01-17 Thread Robert Ancell
** Changed in: snapd-glib (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.

  [Test Case]
  Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.

  [Regression Potential]
  Possibility of new errors being introduced in updated code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1799614] Re: Use new media API

2019-01-17 Thread Robert Ancell
** No longer affects: snapd-glib (Ubuntu Xenial)

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.

  [Test Case]
  Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.

  [Regression Potential]
  Possibility of new errors being introduced in updated code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1799614] Re: Use new media API

2019-01-17 Thread Robert Ancell
** Description changed:

- snapd now provides 'media' which replaces the old 'screenshots' data. We
- need to migrate to this as the old screenshot data will be removed in
- the future.
+ [Impact]
+ snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.
+ 
+ [Test Case]
+ Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.
+ 
+ [Regression Potential]
+ Possibility of new errors being introduced in updated code paths.

** Changed in: snapd-glib (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  snapd now provides 'media' which replaces the old 'screenshots' data. We need 
to migrate to this as the old screenshot data will be removed in the future.

  [Test Case]
  Run gnome-software with updated snapd-glib and confirm that screenshots and 
promoted snap banners continue to work.

  [Regression Potential]
  Possibility of new errors being introduced in updated code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1799614] Re: Use new media API

2019-01-17 Thread Robert Ancell
** Also affects: snapd-glib (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: snapd-glib (Ubuntu)
   Status: New => Fix Released

** Changed in: snapd-glib (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: snapd-glib (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: snapd-glib (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: snapd-glib (Ubuntu)
   Importance: Undecided => High

** Changed in: snapd-glib (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: snapd-glib (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: snapd-glib (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in snapd-glib source package in Cosmic:
  In Progress

Bug description:
  snapd now provides 'media' which replaces the old 'screenshots' data.
  We need to migrate to this as the old screenshot data will be removed
  in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1799614] Re: Use new media API

2019-01-17 Thread Robert Ancell
** Changed in: gnome-software (Ubuntu)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  Use new media API

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  snapd now provides 'media' which replaces the old 'screenshots' data.
  We need to migrate to this as the old screenshot data will be removed
  in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 239669] Re: Inkscape saves imported images from openclipart to /tmp

2019-01-17 Thread Bug Watch Updater
** Changed in: inkscape (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Inkscape saves imported images from openclipart to /tmp

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

Bug description:
  Hello to all!!!

  I have created a design and I have imported a clipart from openclipart.
  I have done some work and the next day I have reopened it.

  But in the place of all the openclipart, there's a "Linked image not
  found"

  I have inspectioned more this and the problem is that inkscape save the 
imported images
  by default in /tmp (i'm on ubuntu linux)
  and the path to this images point to /tmp also
  and when the system is restarted, on linux /tmp is cleared.

  And when I click search, for each click is imported and created an
  image in /tmp

  see for example the attached image, i have clicked on horse cuissard, horse 
and man, horse (lego)
  and then restarted with horse cuissard and on the left is my /tmp folder

  I think that import from openclipart should ask where to put all imported 
clipart
  (maybe in ~/.inkscape/clipart/myclipart or better in the same folder as .svg 
file)
  or incorporate the image in the .svg file
  (in this manner if I need to send the file to another person he/she don't 
lost all
  the imported clipart.

  Thanks for your work!!

  Nicola Lunghi

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/239669/+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 1812279] Re: The ubuntu dock (ubuntu-dock-extension) appears when the screen lock is activated, enabling the access to the applications.

2019-01-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1769383, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1769383
   Ubuntu dock/launcher is shown on the lock screen

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

Title:
  The ubuntu dock (ubuntu-dock-extension) appears when the screen lock
  is activated, enabling the access to the applications.

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

Bug description:
  The problem is the same as reported in https://github.com/micheleg
  /dash-to-dock/issues/649.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
  Uname: Linux 4.16.3-041603-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 21:35:02 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-07-25 (906 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to bionic on 2018-07-18 (183 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812279/+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 1811902] Re: Echo cancelation should be enabled by default

2019-01-17 Thread Daniel van Vugt
I have added your suggestion to the sound UI enhancements card for
Ubuntu 19.04:

  https://trello.com/c/aI3BX3ax

but it seems it's already been deferred and isn't going to be considered
for 19.04. Maybe some future release.

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

Title:
  Echo cancelation should be enabled by default

Status in pulseaudio package in Ubuntu:
  Opinion

Bug description:
  Echo cancellation is a basic feature for anything where you are using
  a video or audio conference. According to instructions like these:

  https://bugs.launchpad.net/elementaryos/+bug/1682253
  
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
  
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

  There is now enough support in pulseaudio to do this well, but it's
  just not enabled by default. Users shouldn't need to fish around for
  strange things to add to config files. More complete defaults should
  be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr2684 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 23:45:10 2019
  InstallationDate: Installed on 2018-05-31 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+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 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560

2019-01-17 Thread Rocko
Oops, it was either acpi_osi=! or acpi_osi='Windows 2009' that was
causing the problem. I had copied them in to try and get the nvidia card
working after resume, but it turns out they aren't needed for the nvidia
card to work anyway.

Sorry for the noise.

** Changed in: upower (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Screen backlight control does not work in Disco on Dell XPS 9560

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Invalid

Bug description:
  When I press the screen backlight up/down buttons, gnome-shell pops up
  the backlight control window saying that the backlight is being
  adjusted, but the actual screen brightness does not change.

  The problem is that gnome is adjusting
  /sys/class/backlight/acpi_video0/brightness instead of
  /sys/class/backlight/intel_backlight/brightness. If I manually change
  the latter as root with, say:

  root@xps-9560:~ echo 600 >
  /sys/class/backlight/intel_backlight/brightness

  then the brightness changes.

  The brightness control worked fine in Cosmic on this laptop, so this
  is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 14:47:37 2019
  DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed
   bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed
   bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed
   nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed
   nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-08-16 (518 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 
rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009"
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812161/+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-17 Thread Daniel van Vugt
Thanks for those files. I can see two possible problems (which may not
be problems but should be checked):

1. You are configured to use both the Nvidia driver version 410, and are
asking Xorg to configure the old Intel driver. In theory this should be
possible but OpenGL is really a very simple beast so it might be
confused in the Totem window with both drivers being present. :(

2. The intel Xorg driver doesn't recognise your new Intel GPU:

[19.882] (WW) intel(0): Unknown chipset

So it might be a better idea to stick with the default 'modesetting'
Xorg driver instead of selecting 'intel'. When you use the former you
only need kernel+Mesa support for your new Intel GPU. When you use the
latter you need kernel+Mesa support AND user space support (which
clearly doesn't exist) in the intel Xorg driver. So I think you should
remove this:

# Makes tearing in totem worse.
Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "TearFree" "true"
EndSection

and continue investigating using the 'modesetting' driver only.

P.S. How many monitors are you using?

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

Title:
  Tearing and/or flickering when using Intel graphics

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/totem/+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 1795342] Re: High Power Consumption

2019-01-17 Thread Daniel van Vugt
Cool. What are the approximate power usage numbers you see in watts?

** Summary changed:

- High Power Consumption
+ Higher power consumption when running gnome-shell compared to unity

** Changed in: ubuntu-power-consumption
   Status: Incomplete => New

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

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

Title:
  Higher power consumption when running gnome-shell compared to unity

Status in The Ubuntu Power Consumption Project:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+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 of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2019-01-17 Thread Kevin Knapp
One other bit of info I thought about that could be contributing is my
horizontal monitor is hooked up to a cheap 4 port HDMI switch (not a
true KVM switch, it's HDMI only). This seems to cause the monitor to
flicker back and forth during boot / loading the splash page as it looks
(to my untrained eye) like it can't decide if the HDMI is hooked up to a
monitor or not. Once the login page is displayed though that particular
problem is gone until the next boot.

-- 
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 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:
  Triaged

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

[Desktop-packages] [Bug 1812101] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-17 Thread Hans P Möller
Who is responsible of that checkbox? the filemanager? in kubuntu's case
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:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

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 66566]

2019-01-17 Thread Boobox
Is there another thread where we can upvote a possible feature to change
this via an option?

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

2019-01-17 Thread Anthony Sottile
this change is really unfortunate -- I just phished myself due to
relying on muscle memory that dates back at least 10 years.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

2019-01-17 Thread Rhmzgx56
Actually, it's not the change that is unfortunate, but that it took 15
years for it to happen. Back then, there were far fewer people who had
developed the "wrong" muscle memory around it.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

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

2019-01-17 Thread Msisaac
Here's my situation:  I use a Mac, but I use a Windows keyboard.  I
changed my modifier keys in MacOS system preferences so that Control is
now Cmd and Cmd is now Control.  This means that I can use ctrl + key on
my keyboard for shortcuts, just like I would use in Windows (ctrl + c to
copy, ctrl + v to paste).  If I didn't make that change in system
preferences, I'd have to use the Windows key for those same shortcuts
(win + c to copy, win + v to paste), which is not how the shortcuts work
in Windows.  Before Firefox 64, ctrl + enter on my Windows keyboard
would autocomplete the URL with www. and .com, because I changed my
modifier keys in system preferences.  This behavior is consistent with
how it would work using the same keyboard in Windows.  Because of this
change to Firefox 64, I now have to use win + enter in Firefox, or I
have to change my system preferences modifier keys back to defaults,
which means Firefox would again use ctrl + enter on the keyboard to
autocomplete, but for everything else in the OS, I'd have to use the Win
key.  So Firefox is now the odd program on my Mac.  I have to retrain my
fingers to use win + enter on the Mac, but continue to use ctrl + enter
on Windows.

So while this is really more of a nuisance than a true show-stopper, it
would be nice if you offered a config that would revert the changes on
Macs if the user isn't using a Mac keyboard.

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

Title:
  Inconsistent shortcuts for new tab

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Won't Fix
Status in firefox-3.0 package in Ubuntu:
  Won't Fix
Status in firefox-3.5 package in Ubuntu:
  Won't Fix

Bug description:
  There are currently too many shortcuts when opening a link in a new
  tab:

   - location bar:  + 
   - GO button:  + click
   - search bar:  + 
   - SEARCH button  + click
   - links:  + click
   - menu bar:  + click
   - BACKWARD/FORWARD button:  + click

  This is one of the reasons I'm keeping with Opera. There it is always
  the shift key and I have to remember only one key.

  Thanks for reading!

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/66566/+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 1812279] [NEW] The ubuntu dock (ubuntu-dock-extension) appears when the screen lock is activated, enabling the access to the applications.

2019-01-17 Thread Marco Furlan
Public bug reported:

The problem is the same as reported in https://github.com/micheleg/dash-
to-dock/issues/649.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
Uname: Linux 4.16.3-041603-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 17 21:35:02 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2016-07-25 (906 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to bionic on 2018-07-18 (183 days ago)

** Affects: gnome-shell-extension-ubuntu-dock (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 gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1812279

Title:
  The ubuntu dock (ubuntu-dock-extension) appears when the screen lock
  is activated, enabling the access to the applications.

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

Bug description:
  The problem is the same as reported in https://github.com/micheleg
  /dash-to-dock/issues/649.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
  Uname: Linux 4.16.3-041603-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 21:35:02 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-07-25 (906 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to bionic on 2018-07-18 (183 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812279/+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-17 Thread Josh Holland
** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230058/+files/Xorg.0.log

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

Title:
  Tearing and/or flickering when using Intel graphics

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/totem/+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 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-17 Thread Josh Holland
This Xorg.1.log was last modified in November, so I'm unsure if it's
relevant.

** Attachment added: "Xorg.1.log"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230059/+files/Xorg.1.log

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

Title:
  Tearing and/or flickering when using Intel graphics

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/totem/+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 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-17 Thread Josh Holland
I don't have an /etc/X11/xorg.conf, but I do have (along with the
various distribution-provided files) a
/usr/share/X11/xorg.conf.d/99-custom.conf.

** Attachment added: "99-custom.conf"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230057/+files/99-custom.conf

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

Title:
  Tearing and/or flickering when using Intel graphics

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/totem/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2019-01-17 Thread pen name
I have a USB-connected brother printer/scanner MFC-7420, hooked up to a
desktop running xubuntu 18.04.1  The printer works but the scanner does
not.  I have tried pretty much every heck posted here and elsewhere but
to no avail.  Here's what I have done and the error messages I got.
Heads up:  I wonder what's the significance on the discrepency in (3)
below?

-
0) To install the drivers I following the instruction (+FAQ) on

https://support.brother.com/g/b/downloa ... all=128

including brother-udev-rule-type1-1.0.2-0.all.deb. The printer works, but not 
the scanner.
-
1) Xsane says

Failed to open device `brother2:bus2;dev5'
Invalid argument.

(sudo xsane gives the same error message). When I fire up simple-scan
(sudo or otherwise) it says

Ready to Scan
Brother MFC-7420

but when I click "scan" I got "Unable to connect to scanner".
-
2) scanimage -L
device `brother2:bus2;dev5' is a Brother MFC-7420 USB scanner

scanimage --test
scanimage: open of device brother2:bus2;dev5 failed: Invalid argument
-
3) lsusb
Bus 001 Device 002: ID 04f9:0180 Brother Industries, Ltd MFC-7420

[ Question: How come it says 001:002 when xsane complains about 002:005
?!! ]

ls -l /dev/bus/usb/001/002
crw-rw-r--+ 1 root lp 189, 1 Jan 17 15:36 /dev/bus/usb/001/002

ls -l /dev/bus/usb/001
total 0
crw-rw-r-- 1 root root 189, 0 Jan 17 15:27 001
crw-rw-r--+ 1 root lp 189, 1 Jan 17 15:36 002
crw-rw-r-- 1 root root 189, 2 Jan 17 15:27 003
crw-rw-r-- 1 root root 189, 3 Jan 17 15:27 004
crw-rw-r-- 1 root root 189, 4 Jan 17 15:27 005
crw-rw-r-- 1 root root 189, 5 Jan 17 15:27 006

[Question: According to
https://cromwell-intl.com/open-source/x ... ument.html
the command above should have listed "scanner" but as you can see it's not 
there]
---
4) I have copied files from lib64 to lib, such as
sudo ln -sf /usr/lib64/libbrscandec*.so* /usr/lib
Reboot but to no avail.
---
5) I added myself to the scanner group:
sudo usermod -a -G scanner (me)
Reboot but to no avail. I also tried

more /etc/group | grep -n scanner

and here's the output:
59:scanner:x:120:saned,(me)

6) I edited /lib/udev/rules.d/60-libsane1.rules following the heck in (#12 of)

https://easylinuxtipsproject.blogspot.c ... nters.html

Reboot but to no avail.

7) There is no "brother.conf" in /etc/sane.d

8) I used synaptic to delete all "brother" related files, reinstall the drivers 
in (step 0) above, reboot but to no avail.

9) I added the following two lines at the end of 
/lib/udev/rules.d/40-libsane.rules (Before the line "# The following rule will 
disable ...")

# Brother scanners
ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes"

Reboot but to no avail.

I'm at a lost on what to do. The scanner (again, it's USB-based, not wireless) 
worked until window, but I no longer have access to the window machine and I 
really need the scanner for work. Your help and advice is most welcome. THANKS!

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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-17 Thread Josh Holland
Unfortunately, the BIOS doesn't have an option to disable the Nvidia
GPU.

** Attachment added: "allpackages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230056/+files/allpackages.txt

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

Title:
  Tearing and/or flickering when using Intel graphics

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/totem/+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 1812057] Re: Upgrade Lost Firefox ESR

2019-01-17 Thread Ubuntu User
Olivier, I'm afraid that you appear to be laboring under a
misunderstanding.  Please note that the issue is not what is supported,
but rather the stupidity of upgrade design that wipes out existing
programs.  There is absolutely no reason to not care enough about users
to not leave things alone.

Of course I recognize that I am assuming that software people should
care about others.  Just MHO.


 « Please report bugs with my packages to **me** not to the upstream projects. »

I don't know what this means.  Please explain.

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

Title:
  Upgrade Lost Firefox ESR

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  System was upgraded from Xubuntu 14 to 16 by DVD.  It wiped out many
  things, including the installation of Firefox ESR.

  ESR was manually reinstalled, but there appears to be no integration
  with the former profiles.  While they still exist, both Firefox
  Quantum and Firefox ESR see the exact same profiles.  There appears to
  be no way to remedy the problem.

  No crash is involved.  If -profilemanager is used in Firefox, the same
  choices appear in both versions.  This was not the case prior to the
  upgrade.


  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  firefox-esr:
Installed: 52.9.0esr-1~16.04.york0
Candidate: 52.9.0esr-1~16.04.york0
Version table:
   *** 52.9.0esr-1~16.04.york0 500
  500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
   *** 64.0+build3-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

2019-01-17 Thread PabloAB
Public bug reported:

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

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

-- 
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:
  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 1720624] Re: Ubuntu 17.10 blank CD or audio CD not detected

2019-01-17 Thread corrado venturini
I have again the same/similar problem with Ubuntu 18.04, 18.10 and 19.04.
should i open a new bug?

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

Title:
  Ubuntu 17.10 blank CD or audio CD not detected

Status in lshw package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in udisks2 package in Ubuntu:
  Fix Released
Status in lshw source package in Artful:
  Invalid
Status in nautilus source package in Artful:
  Invalid
Status in udisks2 source package in Artful:
  Fix Released

Bug description:
  Audio CD are not detected while data CD and data DVD are detected.
  When I insert a data CD or DVD I have a notification and I see the CD in 
files. With audio CD nothing happens.
  Also empty CD and DVD are not detected.
  No problem on same PC, different partition with Ubuntu 16.04.
  I have the same problem on 3 different PC running Ubuntu 17.10.

  I opened a question about this problem: 
https://answers.launchpad.net/ubuntu/+question/658807
  and I was invited to open a bug.

  In Ubuntu 16.04 
  when I insert a blank CD I see a box with a message 'You have just inserted a 
blank CD. Choose what application ...'
  when I insert an audio CD I see a box with a message 'You have just inserted 
a Audio CD. Choose what application ...'

  In Ubuntu 17.10 
  when I insert a blank CD or an Audio CD nothing happens so I can't access the 
CD.
  when I insert a data CD od DVD I see a notification at the top of the screen 
and I can see the inserted CD in files.

  In attachment:
  screenshot of messages from Ubuntu 16.04
  messages from 'sudo lshw -c disk' in Ubuntu 16.04
  messages from 'sudo lshw -c disk' in Ubuntu 17.10
   
  corrado@corrado-0926:~$ inxi -Fx
  System:Host: corrado-0926 Kernel: 4.13.0-12-generic x86_64 bits: 64 gcc: 
7.2.0
 Desktop: Gnome 3.26.0 (Gtk 3.22.21-0ubuntu1) Distro: Ubuntu Artful 
Aardvark (development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-HT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 3900 MHz 2: 3900 MHz 3: 3900 MHz 4: 
3900 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.3 ) driver: i915 Resolution: 
1680x1050@59.88hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.2.1 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.13.0-12-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (6.2% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 6.0G (20%) fs: ext4 dev: /dev/sda3
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 37.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 239 Uptime: 3 min Memory: 782.8/7684.1MB Init: systemd 
runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.121) inxi: 2.3.37 
  corrado@corrado-0926:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lshw 02.18-0.1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 12:50:48 2017
  InstallationDate: Installed on 2017-09-29 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: lshw
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1720624/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen

2019-01-17 Thread Miakoda Combies
The proposed work-around, setting dash-to-dock's opacity to fixed, does not 
accomplish anything on my system.
Ubuntu 18.10 - Gnome 3.30.2

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

Title:
  Ubuntu dock/launcher is shown on the lock screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Cosmic:
  In Progress
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Disco:
  Fix Released

Bug description:
  [Impact]
  When entering the lock-screen mode, gnome-shell disables all the extensions. 
It can happen that under certain conditions ubuntu-dock re-enables itself, 
causing the ubuntu-dock to appear in the lock-screen, exposing sensitive 
information. One possible way to reproduce this is to enable dash-to-dock and 
ubuntu-dock at the same time.

  [Test Case]
  1. Make sure ubuntu-dock is enabled
  2. Enable dash-to-dock too
  3. Lock the screen
  4. Make sure the dock does not appear on the lock screen
  5. Make sure there is no warning is the journal

  [Possible Regressions]
  Even if it's something we don't really support please make sure that you can 
use dash-to-dock without uninstalling ubuntu-dock.

  [Original Bug]

  After an update from ubuntu 16.04 to 18.04 the dock is aviable on the 
lockscreen after user login.
  I did not configure this knowingly. Also i can start every application which 
is available on the dock.
  Settings, virtual box, visualstudio code and so on.

  After the update to 18.04 i just configure the screen frequency to
  144Hz and the night mode on. And attach the dock on bottom.

  I later undid these customizations back to configuration before, but
  the dock is stil aviable on lockscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:30:16 2018
  InstallationDate: Installed on 2018-04-08 (27 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=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (27 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1321903] Re: location box dropdown displays on wrong monitor

2019-01-17 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=959682.

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


On 2014-01-14T17:20:18+00:00 csslayer wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 
Firefox/26.0 (Beta/Release)
Build ID: 20131221082715

Steps to reproduce:

I'm using two screen with setup 3200x1800 on the left and 1600x1200 on the 
right under linux. DPI is set to 228 so by default right click menu height 
would only be a little bit smaller than 1200.
When devPixelsPerPx is larger than 1, firefox seems to think the screen size 
also times the factor. Which makes window in the right screen think they are in 
the left screen.


Actual results:

in my screen resolution setup,  if devPixelsPerPx is set to 1.2, after
right clicking on a window in 1600x1200 screen, clicking on the left
part would show menu in the first screen, while the right half click
would show menu in the right screen.

if devPixelsPerPx is set to some larger number (for instance 2), all
popup menu that should be shown in the right screen would be shown in
the left screen.


Expected results:

menu appears in correct screen.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1321903/comments/0


On 2015-03-18T07:01:01+00:00 Xidorn+moz wrote:

Created attachment 8579169
screenshot

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1321903/comments/3


On 2015-03-18T07:10:23+00:00 Xidorn+moz wrote:

It seems this bug has been fixed in Aurora.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1321903/comments/4


On 2015-07-28T17:39:02+00:00 Liam Middlebrook wrote:

Created attachment 8639968
2015-07-28-103032_5520x3840_scrot.png

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


On 2015-07-28T17:46:16+00:00 Liam Middlebrook wrote:

Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101
Firefox/38.0

On the black penciled line (in the image I've attached above) is where
the separation occurs for a `devPixelsPerPx` value of 1.2. I've only
encountered this issue on `devPixelsPerPx` values that are between 1 and
2. It appears that this invisible line of separation changes it's x
position on a linear scale based on the value of `devPixelsPerPx`

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


On 2015-12-30T11:27:33+00:00 6-adv wrote:

Reproduceable on Firefox 43.0 for any values of devPixelsPerPx between 1
and 2 (excluding 1.0 and 2.0).

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


On 2016-01-11T09:16:59+00:00 Cirdeiliviu wrote:

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

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


On 2016-01-15T18:47:30+00:00 Overholt-u wrote:

I see this on Windows, too. It feels like it *started* happening with a
multi-dpi setup but now I'm seeing it without an external monitor
connected, too.

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


On 2016-01-15T18:56:54+00:00 Overholt-u wrote:

William, is this a DOM thing or a Toolkit (?) thing?

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


On 2016-01-15T20:46:01+00:00 R-william wrote:

I don't see anything that indicates this is a DOM thing. My guess is
that we are getting some numbers wrong in
layout/xul/nsMenuPopupFrame.cpp

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


On 2016-02-17T08:06:15+00:00 Xidorn+moz wrote:

jfkthame, as you are recently working on Windows multi-dpi support, I
suppose you have some insight around this issue.

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


On 2016-02-17T09:19:21+00:00 Jfkthame wrote:

It's possible the upcoming patches in bugs like 1240533 

[Desktop-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default

2019-01-17 Thread Pedro Côrte-Real
I don't agree that it's just a Firefox issue. There should be a simple
way to enable this in the normal sound UI, at least as default for
everything and ideally per-app.

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

Title:
  Echo cancelation should be enabled by default

Status in pulseaudio package in Ubuntu:
  Opinion

Bug description:
  Echo cancellation is a basic feature for anything where you are using
  a video or audio conference. According to instructions like these:

  https://bugs.launchpad.net/elementaryos/+bug/1682253
  
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
  
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

  There is now enough support in pulseaudio to do this well, but it's
  just not enabled by default. Users shouldn't need to fish around for
  strange things to add to config files. More complete defaults should
  be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr2684 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 23:45:10 2019
  InstallationDate: Installed on 2018-05-31 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+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 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't display

2019-01-17 Thread David Chapman
Maybe it's an old problem but I did a fresh install of 18.04.1 yesterday
and today I moved the Dock to the bottom and could not get access to
Settings any more.

None of the above helped me at all but the solution is here
https://askubuntu.com/questions/366813/disable-second-non-existent-
screen-from-command-line.

At this link the top command did nothing - but starting from First run:
those two commands did the trick, in my case for the second command I
had to type "VGA-1-2" instead of VGA2.

Have yet to reboot so I will find out if I have to add it to the "run on
start"

Cannot believe this bug has not been fixed.

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't display

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

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1721637/+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 1749864] Re: simple-scan crashes scanning on brother mfc-J985DW scanner

2019-01-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  simple-scan crashes scanning on brother mfc-J985DW scanner

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  [+0.00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 3.26.3, PID=14852
  [+0.02s] CRITICAL: g_action_print_detailed_name: assertion 
'g_action_name_is_valid (action_name)' failed
  [+0.02s] CRITICAL: gtk_application_set_accels_for_action: assertion 
'detailed_action_name != NULL' failed
  [+0.05s] DEBUG: app-window.vala:1714: Loading state from 
/home/bartb1959/.cache/simple-scan/state
  [+0.09s] DEBUG: app-window.vala:1671: Restoring window to 600x400 pixels
  [+0.09s] DEBUG: app-window.vala:1675: Restoring window to maximized
  [+0.09s] DEBUG: autosave-manager.vala:64: Loading autosave information
  [+0.09s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
  [+0.15s] DEBUG: scanner.vala:1454: sane_init () -> SANE_STATUS_GOOD
  [+0.15s] DEBUG: scanner.vala:1460: SANE version 1.0.27
  [+0.15s] DEBUG: scanner.vala:1521: Requesting redetection of scan devices
  [+0.15s] DEBUG: scanner.vala:806: Processing request
  [+0.19s] DEBUG: autosave-manager.vala:281: Autosaving book information
  [+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
  [+0.32s] DEBUG:   Encoding raw
  [+0.32s] DEBUG:   Dimensions: 16 x 16
  [+0.32s] DEBUG:   Rowstride: 64, Length: 1048
  [+0.32s] DEBUG:   Copy pixels == false
  [+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
  [+0.32s] DEBUG:   Encoding raw
  [+0.32s] DEBUG:   Dimensions: 16 x 16
  [+0.32s] DEBUG:   Rowstride: 64, Length: 1048
  [+0.32s] DEBUG:   Copy pixels == false
  [+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
  [+0.32s] DEBUG:   Encoding raw
  [+0.32s] DEBUG:   Dimensions: 16 x 16
  [+0.32s] DEBUG:   Rowstride: 64, Length: 1048
  [+0.32s] DEBUG:   Copy pixels == false
  [+0.41s] DEBUG: app-window.vala:1775: Saving state to 
/home/bartb1959/.cache/simple-scan/state
  [+3.08s] DEBUG: simple-scan.vala:454: Requesting scan at 300 dpi from device 
'(null)'
  [+3.08s] DEBUG: scanner.vala:1569: Scanner.scan ("(null)", dpi=300, 
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=2159, 
paper_height=2794, brightness=0, contrast=0, delay=15ms)
  [+6.98s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+6.98s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0" 
vendor="Brother" model="*mfcj985dwxl" type="MFCJ985DW"
  [+6.98s] DEBUG: scanner.vala:353: Device: name="brother4:bus2;dev7" 
vendor="Brother" model="MFC-J985DW" type="USB scanner"
  [+6.98s] DEBUG: scanner.vala:806: Processing request
  [+8.67s] DEBUG: scanner.vala:867: sane_open ("brother4:net1;dev0") -> 
SANE_STATUS_GOOD
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (0)
  [+8.67s] DEBUG: scanner.vala:738: Option 0: name='(null)' title='Number of 
options' type=bool size=4 cap=soft-detect
  [+8.67s] DEBUG: scanner.vala:741:   Description: Read-only option that 
specifies how many options a specific devices supports.
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (1)
  [+8.67s] DEBUG: scanner.vala:738: Option 1: name='(null)' title='Mode' 
type=group size=4 cap=advanced
  [+8.67s] DEBUG: scanner.vala:741:   Description: 
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (2)
  [+8.67s] DEBUG: scanner.vala:738: Option 2: name='mode' title='Scan mode' 
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True 
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
  [+8.67s] DEBUG: scanner.vala:741:   Description: Select the scan mode
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (3)
  [+8.67s] DEBUG: scanner.vala:738: Option 3: name='resolution' title='Scan 
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600, 
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
  [+8.67s] DEBUG: scanner.vala:741:   Description: Sets the resolution of the 
scanned image.
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (4)
  [+8.67s] DEBUG: scanner.vala:738: Option 4: name='source' title='Scan source' 
type=string size=64 values=["FlatBed", "Automatic Document Feeder(left 
aligned)", "Automatic Document Feeder(left aligned,Duplex)", "Automatic 
Document Feeder(centrally aligned)", "Automatic Document Feeder(centrally 
aligned,Duplex)"] cap=soft-select,soft-detect
  [+8.67s] DEBUG: 


  [+0.00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 3.26.3, PID=14852
  [+0.02s] CRITICAL: g_action_print_detailed_name: assertion 
'g_action_name_is_valid (action_name)' failed
  [+0.02s] CRITICAL: gtk_application_set_accels_for_action: assertion 

[Desktop-packages] [Bug 1749864] Re: simple-scan crashes scanning on brother mfc-J985DW scanner

2019-01-17 Thread Peter Wibberley
For me, the application works but most of the button icons do not
display properly.

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

Title:
  simple-scan crashes scanning on brother mfc-J985DW scanner

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  [+0.00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 3.26.3, PID=14852
  [+0.02s] CRITICAL: g_action_print_detailed_name: assertion 
'g_action_name_is_valid (action_name)' failed
  [+0.02s] CRITICAL: gtk_application_set_accels_for_action: assertion 
'detailed_action_name != NULL' failed
  [+0.05s] DEBUG: app-window.vala:1714: Loading state from 
/home/bartb1959/.cache/simple-scan/state
  [+0.09s] DEBUG: app-window.vala:1671: Restoring window to 600x400 pixels
  [+0.09s] DEBUG: app-window.vala:1675: Restoring window to maximized
  [+0.09s] DEBUG: autosave-manager.vala:64: Loading autosave information
  [+0.09s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
  [+0.15s] DEBUG: scanner.vala:1454: sane_init () -> SANE_STATUS_GOOD
  [+0.15s] DEBUG: scanner.vala:1460: SANE version 1.0.27
  [+0.15s] DEBUG: scanner.vala:1521: Requesting redetection of scan devices
  [+0.15s] DEBUG: scanner.vala:806: Processing request
  [+0.19s] DEBUG: autosave-manager.vala:281: Autosaving book information
  [+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
  [+0.32s] DEBUG:   Encoding raw
  [+0.32s] DEBUG:   Dimensions: 16 x 16
  [+0.32s] DEBUG:   Rowstride: 64, Length: 1048
  [+0.32s] DEBUG:   Copy pixels == false
  [+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
  [+0.32s] DEBUG:   Encoding raw
  [+0.32s] DEBUG:   Dimensions: 16 x 16
  [+0.32s] DEBUG:   Rowstride: 64, Length: 1048
  [+0.32s] DEBUG:   Copy pixels == false
  [+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
  [+0.32s] DEBUG:   Encoding raw
  [+0.32s] DEBUG:   Dimensions: 16 x 16
  [+0.32s] DEBUG:   Rowstride: 64, Length: 1048
  [+0.32s] DEBUG:   Copy pixels == false
  [+0.41s] DEBUG: app-window.vala:1775: Saving state to 
/home/bartb1959/.cache/simple-scan/state
  [+3.08s] DEBUG: simple-scan.vala:454: Requesting scan at 300 dpi from device 
'(null)'
  [+3.08s] DEBUG: scanner.vala:1569: Scanner.scan ("(null)", dpi=300, 
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=2159, 
paper_height=2794, brightness=0, contrast=0, delay=15ms)
  [+6.98s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+6.98s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0" 
vendor="Brother" model="*mfcj985dwxl" type="MFCJ985DW"
  [+6.98s] DEBUG: scanner.vala:353: Device: name="brother4:bus2;dev7" 
vendor="Brother" model="MFC-J985DW" type="USB scanner"
  [+6.98s] DEBUG: scanner.vala:806: Processing request
  [+8.67s] DEBUG: scanner.vala:867: sane_open ("brother4:net1;dev0") -> 
SANE_STATUS_GOOD
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (0)
  [+8.67s] DEBUG: scanner.vala:738: Option 0: name='(null)' title='Number of 
options' type=bool size=4 cap=soft-detect
  [+8.67s] DEBUG: scanner.vala:741:   Description: Read-only option that 
specifies how many options a specific devices supports.
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (1)
  [+8.67s] DEBUG: scanner.vala:738: Option 1: name='(null)' title='Mode' 
type=group size=4 cap=advanced
  [+8.67s] DEBUG: scanner.vala:741:   Description: 
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (2)
  [+8.67s] DEBUG: scanner.vala:738: Option 2: name='mode' title='Scan mode' 
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True 
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
  [+8.67s] DEBUG: scanner.vala:741:   Description: Select the scan mode
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (3)
  [+8.67s] DEBUG: scanner.vala:738: Option 3: name='resolution' title='Scan 
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600, 
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
  [+8.67s] DEBUG: scanner.vala:741:   Description: Sets the resolution of the 
scanned image.
  [+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (4)
  [+8.67s] DEBUG: scanner.vala:738: Option 4: name='source' title='Scan source' 
type=string size=64 values=["FlatBed", "Automatic Document Feeder(left 
aligned)", "Automatic Document Feeder(left aligned,Duplex)", "Automatic 
Document Feeder(centrally aligned)", "Automatic Document Feeder(centrally 
aligned,Duplex)"] cap=soft-select,soft-detect
  [+8.67s] DEBUG: 


  [+0.00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 3.26.3, PID=14852
  [+0.02s] CRITICAL: g_action_print_detailed_name: assertion 
'g_action_name_is_valid (action_name)' failed
  [+0.02s] CRITICAL: gtk_application_set_accels_for_action: assertion 
'detailed_action_name != NULL' failed
  [+0.05s] DEBUG: 

[Desktop-packages] [Bug 1795342] Re: High Power Consumption

2019-01-17 Thread Irfan
I installed a new kernel 4.20 on Gnome-shell and the power consumption was 
almost same/high.
Then, I removed the kernel and switched back to 4.18 that comes with 18.10 base 
and installed unity-session and I noticed a sudden decrease in power 
consumption. I don't know, if the problem is Gnome-shell but this is what seems 
by switching to unity.

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

Title:
  High Power Consumption

Status in The Ubuntu Power Consumption Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+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 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-17 Thread Fusion
ok

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-08-28 (84 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803527/+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] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-17 Thread Hans P Möller
** Attachment added: "LOfilepicker.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812101/+attachment/5230013/+files/LOfilepicker.png

-- 
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:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

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] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-17 Thread Hans P Möller
I don't have the checkbox, see the .png in the above comment

-- 
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:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

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 1812247] [NEW] ssh-agent fails for ssh-add -c: agent refused operation

2019-01-17 Thread schamane
Public bug reported:

Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means
of `ssh-add -c` indicating that keys "should be subject to confirmation
before being used for authentication. In Ubuntu 18.10 this fails with
the error

  sign_and_send_pubkey: signing failed: agent refused operation

To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt-get
upgrade, log out and log back in (these steps are not required but we
want to use an up-to-date system). Then:

$ sudo apt-get install ssh-askpass-gnome
(...)
$ # verify that ssh-askpass shows a popup, confirm with Enter
$ ssh-askpass ; echo $?

0
$ ssh-keygen
(...)
$ ssh-add -D
All identities removed.
$ ssh-copy-id $sshuser@$sshserver
(...)
Number of key(s) added: 1
(...)
$ ssh $sshuser@$sshserver uname -a
Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux
$ ssh-add -d
Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu)
$ ssh-add -c
Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): 
Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa)
The user must confirm each use of the key
$ ssh $sshuser@$sshserver uname -a
sign_and_send_pubkey: signing failed: agent refused operation
sshuser@server's password: [^C'ed]

$ ssh-add -l
2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc 
/home/ubuntu/.ssh/id_rsa (RSA)

So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-
add -c 
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-session (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 gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1812247

Title:
  ssh-agent fails for ssh-add -c: agent refused operation

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means
  of `ssh-add -c` indicating that keys "should be subject to
  confirmation before being used for authentication. In Ubuntu 18.10
  this fails with the error

sign_and_send_pubkey: signing failed: agent refused operation

  To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt-
  get upgrade, log out and log back in (these steps are not required but
  we want to use an up-to-date system). Then:

  $ sudo apt-get install ssh-askpass-gnome
  (...)
  $ # verify that ssh-askpass shows a popup, confirm with Enter
  $ ssh-askpass ; echo $?

  0
  $ ssh-keygen
  (...)
  $ ssh-add -D
  All identities removed.
  $ ssh-copy-id $sshuser@$sshserver
  (...)
  Number of key(s) added: 1
  (...)
  $ ssh $sshuser@$sshserver uname -a
  Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 
GNU/Linux
  $ ssh-add -d
  Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu)
  $ ssh-add -c
  Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): 
  Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa)
  The user must confirm each use of the key
  $ ssh $sshuser@$sshserver uname -a
  sign_and_send_pubkey: signing failed: agent refused operation
  sshuser@server's password: [^C'ed]

  $ ssh-add -l
  2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc 
/home/ubuntu/.ssh/id_rsa (RSA)

  So, our key is loaded, ssh-askpass is working (also confirmed with
  `ssh-add -c 
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2019-01-17 Thread Amr Ibrahim
Yes, it works for Ubuntu ISO but not for everything. It didn't work for
a Windows 10 ISO.

The option from gnome-disk-utility works fine, however, the mounted ISO
does not appear on nautilus sidebar, it's hidden in Other Locations. But
that's a different issue.

-- 
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 Committed

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 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2019-01-17 Thread Dimitri John Ledkov
** Also affects: gnome-terminal (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in gnome-terminal source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in gnome-terminal source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1762391/+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 388633] Re: ComboBox has a big blank area above the position of its control

2019-01-17 Thread Stu
Can we get some user testing on this and various alternatives to it ?

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

Title:
  ComboBox has a big blank area above the position of its control

Status in GTK+:
  Invalid
Status in One Hundred Papercuts:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  (when there are a lot of entries or the control is in the bottom of
  the screen - see attached screenshots)

  ComboBox wants to place the current selected option under the cursor,
  but in the presented corner cases it is a wrong choice. See the
  discussion in Gnome bugzilla (where there is also a patch).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/388633/+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 1560286] Re: Evince displays pdf file fine, but prints colors inverted

2019-01-17 Thread felix
I guess its about embedded cmyk images. Can be inspected with

$ pdfimages /tmp/previewZTSTVZ.pdf -list
page   num  type   width height color comp bpc  enc interp  object ID x-ppi 
y-ppi size ratio

   1 0 image 818   750  cmyk4   8  jpeg   no 7  0   155   
155  183K 7.6%

A "process workaround" is to open the images in libreoffice draw and
print them from there, but obviously the underlying library should be
fixed.

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+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 1770929] Re: backup fails on ubuntu 18.4

2019-01-17 Thread Robert R
This is the error message I receive when trying to use backup:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
  File "/usr/bin/duplicity", line 563, in full_backup
bytes_written = dummy_backup(tarblock_iter)
  File "/usr/bin/duplicity", line 236, in dummy_backup
while tarblock_iter.next():
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 523, in 
next
result = self.process(self.input_iter.next())
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 195, in 
get_delta_iter
for new_path, sig_path in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 286, in 
collate2iters
relem2 = riter2.next()
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 237, in 
sigtar2path_iter
tf = util.make_tarfile("r", sigtarobj)
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 123, in 
make_tarfile
tf = tarfile.TarFile("arbitrary", mode, fp)
  File "/usr/lib/python2.7/tarfile.py", line 1543, in __init__
self.name = os.path.abspath(name) if name else None
  File "/usr/lib/python2.7/posixpath.py", line 364, in abspath
cwd = os.getcwd()
 OSError: [Errno 2] No such file or directory

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

Title:
  backup fails on ubuntu 18.4

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1777392] Re: atril prints cmyk PDF with inverted colors

2019-01-17 Thread felix
Probably the same issue, but with more information and a sample
document: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286
.

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

Title:
  atril prints cmyk PDF with inverted colors

Status in atril package in Ubuntu:
  New
Status in evince package in Ubuntu:
  New

Bug description:
  Hello,

  Since upgrading to Ubuntu 18.04, I'm having trouble printing PDFs in
  CMYK colorspace from atril.

  The same PDFs printed OK with atril on the same machine when on 17.10,
  they print OK on other machines with 16.04 (with evince though), and
  they also print OK on 18.04 from command line (lpr -P PRINTER_NAME
  file.pdf). I was only able to reproduce the issue with atril.

  The printer is a HP LaserJet Pro 400, also tried on a Lexmark E260dn,
  so it's not a printer or driver issue (different printer
  manufacturers).

  I do not want to post the PDFs in the bug report, but I can send them
  privately. They are 100% CMYK (/DeviceCMYK) as are the included
  images.

  Please contact me if there is any further information needed or
  anything I can try, I'm very interested to resolve this as it
  interferes with my workflow a lot.

  Best regards,
  Borut Mrak

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy atril
  atril:
Installed: 1.20.1-2ubuntu2
Candidate: 1.20.1-2ubuntu2
Version table:
   *** 1.20.1-2ubuntu2 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atril/+bug/1777392/+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 1777392] Re: atril prints cmyk PDF with inverted colors

2019-01-17 Thread felix
Same here, for documentation purposes, you can list the images embedded
in a pdf with

`pdfimages the_document.pdf -list`
.

It affects all pdf processing for me (even if printing the document to
file or opening it in gimp).

The only "process workaround" so far is to open the document in
libreoffice draw and print it from there :( .

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

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

Title:
  atril prints cmyk PDF with inverted colors

Status in atril package in Ubuntu:
  New
Status in evince package in Ubuntu:
  New

Bug description:
  Hello,

  Since upgrading to Ubuntu 18.04, I'm having trouble printing PDFs in
  CMYK colorspace from atril.

  The same PDFs printed OK with atril on the same machine when on 17.10,
  they print OK on other machines with 16.04 (with evince though), and
  they also print OK on 18.04 from command line (lpr -P PRINTER_NAME
  file.pdf). I was only able to reproduce the issue with atril.

  The printer is a HP LaserJet Pro 400, also tried on a Lexmark E260dn,
  so it's not a printer or driver issue (different printer
  manufacturers).

  I do not want to post the PDFs in the bug report, but I can send them
  privately. They are 100% CMYK (/DeviceCMYK) as are the included
  images.

  Please contact me if there is any further information needed or
  anything I can try, I'm very interested to resolve this as it
  interferes with my workflow a lot.

  Best regards,
  Borut Mrak

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy atril
  atril:
Installed: 1.20.1-2ubuntu2
Candidate: 1.20.1-2ubuntu2
Version table:
   *** 1.20.1-2ubuntu2 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atril/+bug/1777392/+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 1811530] Re: Impress embeded video files show flickering white stripes

2019-01-17 Thread Olivier Tilloy
Ah, thanks.

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

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

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

Title:
  Impress embeded video files show flickering white stripes

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

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1811530/+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] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-17 Thread Olivier Tilloy
Just tested on a kubuntu desktop, and there's a checkbox option in the
save dialog that reads "Automatically select filename extension
(.docx)". See attached screenshot.

Predictably, if I check this option, the extension is automatically
added to the filename, and if I uncheck it, it's not.

Were you expecting a different behaviour? Or are you not seeing that
checkbox?

** Attachment added: "Capture d’écran du 2019-01-17 17-14-44.png"
   
https://bugs.launchpad.net/df-libreoffice/+bug/1812101/+attachment/5230005/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202019-01-17%2017-14-44.png

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

-- 
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:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

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 1811530] Re: Impress embeded video files show flickering white stripes

2019-01-17 Thread klinge
well the bug exists already:
https://bugs.documentfoundation.org/show_bug.cgi?id=118631 they sent me
here, because the bug doesn't appear in the appimages.

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

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

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1811530/+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] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-17 Thread Bug Watch Updater
Launchpad has imported 4 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=122752.

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


On 2019-01-16T09:50:35+00:00 Hans P Möller wrote:

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


Reproducible: Always


User Profile Reset: No


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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812101/comments/0


On 2019-01-16T17:44:10+00:00 Italo Vignoli wrote:

On my Linux PC, LibreOffice vanilla works properly with all flavours of
Ubuntu 18.10. IMHO, bug has to be filed at KDE or Canonical as the
software is tweaked/recompiled by them.

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


On 2019-01-16T18:56:48+00:00 Xiscofauli wrote:

Thank you for reporting the bug.
KDE5 support has been hugely improved in LibreOffice 6.2.
Could you please try to reproduce it with LibreOffice 6.2 from 
https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.

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


On 2019-01-16T20:09:27+00:00 Hans P Möller wrote:

I installed 6.2RC2 but I don't get the "kde look" in the file picker/dialog 
that the libreoffice-kde5 package gave me.
In help->about appears VCL:kde4 and not gtk3_kde5 which i was getting before.

I don't know who is responsible of libreoffice-kde5 package, but there
is the problem. vanila LO works ok in 6.1.4.2 and 6.2. Should I file KDE
or Ubuntu? Who is responsible for libreoffice-kde5
https://packages.ubuntu.com/disco/libreoffice-kde5 ?

Version: 6.2.0.2
Build ID: 2ce5217b30a543f7666022df50f0562f82be0cff
CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: kde4; 
Locale: es-CL (es_CL.UTF-8); UI-Language: en-US
Calc: threaded

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


** Changed in: df-libreoffice
   Status: Unknown => Incomplete

** Changed in: df-libreoffice
   Importance: Unknown => Low

-- 
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:
  Incomplete
Status in libreoffice package in Ubuntu:
  New

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] Re: libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-17 Thread Olivier Tilloy
** Bug watch added: Document Foundation Bugzilla #122752
   https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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

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

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

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 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2019-01-17 Thread Kevin Knapp
I just got hit with this bug as well. Fresh Ubuntu 18.10 install on a
Desktop (Ryzen 2995x, 32GB RAM, Vega 64, 250GB NVMe /, and 1TB Evo 860
SSD /home) with two monitors (1 vertical using DP, and one horizontal
using HDMI), only thing I did post install was install a few flatpaks
from flathub (Discord, Telegram, VSCode, Slack), and a snap (CLion) as
well as a Rust toolchain (https://rustup.rs). Went to bed, went to work
the next morning, and when I came up the computer appeared to be frozen
as it wouldn't wake from sleep. After a hard reset and login, I noticed
I couldn't do an update do to "disk full". Checked `df` and saw `/` was
full. Quick checking of dirs lead to `/var/log/syslog` being 230GB from
a single night/day of no use!

My plan is to do a re-install (with Kubuntu which is what it was prior
to this install), however if there is something else I can provide that
would help track down this bug I will (assuming I see a message prior to
the nuke/pave).

-- 
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 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:
  Triaged

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 

[Desktop-packages] [Bug 1811530] Re: Impress embeded video files show flickering white stripes

2019-01-17 Thread Olivier Tilloy
Thanks for the additional feedback. It looks like this might be an
upstream bug, rather than something specific to Ubuntu. Would you mind
filing a bug at
https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice=guided,
and sharing the link to it here? Thanks!

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

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1811530/+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 1812057] Re: Upgrade Lost Firefox ESR

2019-01-17 Thread Olivier Tilloy
Firefox ESR is not an official Ubuntu package. As seen on
https://launchpad.net/~jonathonf:

  « Please report bugs with my packages to **me** not to the upstream
projects. »

** Changed in: firefox (Ubuntu)
   Status: New => 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/1812057

Title:
  Upgrade Lost Firefox ESR

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  System was upgraded from Xubuntu 14 to 16 by DVD.  It wiped out many
  things, including the installation of Firefox ESR.

  ESR was manually reinstalled, but there appears to be no integration
  with the former profiles.  While they still exist, both Firefox
  Quantum and Firefox ESR see the exact same profiles.  There appears to
  be no way to remedy the problem.

  No crash is involved.  If -profilemanager is used in Firefox, the same
  choices appear in both versions.  This was not the case prior to the
  upgrade.


  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  firefox-esr:
Installed: 52.9.0esr-1~16.04.york0
Candidate: 52.9.0esr-1~16.04.york0
Version table:
   *** 52.9.0esr-1~16.04.york0 500
  500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
   *** 64.0+build3-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1812057/+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 1721735] Re: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed

2019-01-17 Thread Andrea Azzarone
** No longer affects: snapd (Ubuntu Artful)

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

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

** Changed in: snapd (Ubuntu)
   Status: In Progress => Fix Released

** No longer affects: gnome-software (Ubuntu Artful)

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

Title:
  UbuntuOne auth dialog is displayed when polkit auth dialog is
  dismissed

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  With snapd 16-2.28.1 from the candidate channel

  Test Case
  1. With gnome-software, install a snap
  2. When the polkit auth dialog is displayed, click "Cancel"

  Actual result 
  The Ubuntu One authentication dialog is displayed

  Expected result
  The polkit authentication dialog is dismissed and the user returns to the 
main screen of gnome-software. The U1 dialog is not displayed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:05:54 2017
  InstallationDate: Installed on 2013-09-03 (1493 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1721735/+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 1798360] Re: Invalid read in the snap plugin

2019-01-17 Thread Andrea Azzarone
Fix released in https://launchpad.net/ubuntu/+source/snapd-glib/1.45-1

** Changed in: snapd-glib (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: snapd-glib (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Invalid read in the snap plugin

Status in gnome-software package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  Fix Released

Bug description:
  On cosmic, open gnome-software, type some text to search, it easily
  leads to snapd related warnings on stdout and those corresponding
  valgrind invalid read errors

  ==31017== Invalid read of size 8
  ==31017==at 0x4913AC5: g_type_check_instance_is_fundamentally_a 
(gtype.c:4023)
  ==31017==by 0x48F4AF4: g_object_unref (gobject.c:3243)
  ==31017==by 0x497D4E2: g_source_callback_unref (gmain.c:1551)
  ==31017==by 0x497DF1D: g_source_destroy_internal (gmain.c:1236)
  ==31017==by 0x4980B77: g_main_dispatch (gmain.c:3206)
  ==31017==by 0x4980B77: g_main_context_dispatch (gmain.c:3847)
  ==31017==by 0x4980ED7: g_main_context_iterate.isra.26 (gmain.c:3920)
  ==31017==by 0x49811D1: g_main_loop_run (gmain.c:4116)
  ==31017==by 0x12C6EB5E: end_sync (snapd-client-sync.c:33)
  ==31017==by 0x12C6EB5E: snapd_client_find_section_sync 
(snapd-client-sync.c:646)
  ==31017==by 0x12C2F571: find_snaps (gs-plugin-snap.c:294)
  ==31017==by 0x12C30320: gs_plugin_add_search (gs-plugin-snap.c:635)
  ==31017==by 0x186660: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:695)
  ==31017==by 0x1869E1: gs_plugin_loader_run_results 
(gs-plugin-loader.c:1147)
  ==31017==by 0x187BC4: gs_plugin_loader_process_thread_cb 
(gs-plugin-loader.c:3140)
  ==31017==by 0x4ADFC02: g_task_thread_pool_thread (gtask.c:1331)
  ==31017==by 0x49A9AD2: g_thread_pool_thread_proxy (gthreadpool.c:307)
  ==31017==by 0x49A9134: g_thread_proxy (gthread.c:784)
  ==31017==by 0x5CFC163: start_thread (pthread_create.c:486)
  ==31017==by 0x5E2FDEE: clone (clone.S:95)
  ==31017==  Address 0xdccd330 is 96 bytes inside a block of size 184 free'd
  ==31017==at 0x483897B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==31017==by 0x49128C3: g_type_free_instance (gtype.c:1936)
  ==31017==by 0x12C67046: request_data_unref (snapd-client.c:178)
  ==31017==by 0x497D4E2: g_source_callback_unref (gmain.c:1551)
  ==31017==by 0x497DF1D: g_source_destroy_internal (gmain.c:1236)
  ==31017==by 0x4980B77: g_main_dispatch (gmain.c:3206)
  ==31017==by 0x4980B77: g_main_context_dispatch (gmain.c:3847)
  ==31017==by 0x4980ED7: g_main_context_iterate.isra.26 (gmain.c:3920)
  ==31017==by 0x49811D1: g_main_loop_run (gmain.c:4116)
  ==31017==by 0x12C6EB5E: end_sync (snapd-client-sync.c:33)
  ==31017==by 0x12C6EB5E: snapd_client_find_section_sync 
(snapd-client-sync.c:646)
  ==31017==by 0x12C2F571: find_snaps (gs-plugin-snap.c:294)
  ==31017==by 0x12C30320: gs_plugin_add_search (gs-plugin-snap.c:635)
  ==31017==by 0x186660: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:695)
  ==31017==by 0x1869E1: gs_plugin_loader_run_results 
(gs-plugin-loader.c:1147)
  ==31017==by 0x187BC4: gs_plugin_loader_process_thread_cb 
(gs-plugin-loader.c:3140)
  ==31017==by 0x4ADFC02: g_task_thread_pool_thread (gtask.c:1331)
  ==31017==by 0x49A9AD2: g_thread_pool_thread_proxy (gthreadpool.c:307)
  ==31017==by 0x49A9134: g_thread_proxy (gthread.c:784)
  ==31017==by 0x5CFC163: start_thread (pthread_create.c:486)
  ==31017==by 0x5E2FDEE: clone (clone.S:95)
  ==31017==  Block was alloc'd at
  ==31017==at 0x483774F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==31017==by 0x4986650: g_malloc (gmem.c:99)
  ==31017==by 0x499E5B2: g_slice_alloc (gslice.c:1024)
  ==31017==by 0x499EBE8: g_slice_alloc0 (gslice.c:1050)
  ==31017==by 0x49124F9: g_type_create_instance (gtype.c:1836)
  ==31017==by 0x48F5397: g_object_new_internal (gobject.c:1805)
  ==31017==by 0x48F7223: g_object_new_valist (gobject.c:2128)
  ==31017==by 0x48F7558: g_object_new (gobject.c:1648)
  ==31017==by 0x12C5C70A: _snapd_get_find_new (snapd-get-find.c:34)
  ==31017==by 0x12C6A967: snapd_client_find_section_async 
(snapd-client.c:2119)
  ==31017==by 0x12C6EB4D: snapd_client_find_section_sync 
(snapd-client-sync.c:645)
  ==31017==by 0x12C2F571: find_snaps (gs-plugin-snap.c:294)
  ==31017==by 0x12C30320: gs_plugin_add_search (gs-plugin-snap.c:635)
  ==31017==by 0x186660: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:695)
  ==31017==by 0x1869E1: gs_plugin_loader_run_results 
(gs-plugin-loader.c:1147)
  ==31017==by 0x187BC4: gs_plugin_loader_process_thread_cb 
(gs-plugin-loader.c:3140)
  ==31017==by 0x4ADFC02: 

[Desktop-packages] [Bug 1724808] Re: osd progress looks odd using Ambiance or Radiance

2019-01-17 Thread Andrea Azzarone
** Changed in: ubuntu-themes
   Status: In Progress => Fix Released

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

Title:
  osd progress looks odd using Ambiance or Radiance

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Released

Bug description:
  == Impact ==
  osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.

  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.

  == Potential Regressions ==
  Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.

  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1724808/+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 1799293] Re: Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works.

2019-01-17 Thread Andrea Azzarone
Fix released in disco: https://launchpad.net/ubuntu/+source/gnome-shell-
extension-ubuntu-dock/64ubuntu2

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

** Changed in: gnome-shell-extension-dashtodock (Ubuntu Cosmic)
   Status: Triaged => In Progress

** Changed in: gnome-shell-extension-dashtodock (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  Locking the screen once leaves screen contents visible but not
  interactive. Locking the screen a second time works.

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in gnome-shell-extension-dashtodock source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell-extension-dashtodock source package in Cosmic:
  In Progress
Status in gnome-shell source package in Disco:
  Invalid
Status in gnome-shell-extension-dashtodock source package in Disco:
  Fix Released

Bug description:
  1) Ubuntu 18.10 (new install)
  2) gdm3 3.30.1-1ubuntu5

  Preconditions
  The session's user has auto-login enabled (i.e. the system starts and the 
user is not prompted for a password but directly presented with the desktop)

  3) What should happen:
  Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top 
right corner menu) and the lock screen is engaged (that is, lock screen clock 
shade drops down and screen fades to dark). Pressing ENTER brings back the lock 
screen and the password is prompted.

  4) What happens:
  First Win + L lets the system in a half locked state in which the contents of 
the desktop are seen although no interaction is possible. A second Win + L 
correctly invokes the lock screen.

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

2019-01-17 Thread Jeremy Bicha
Amr, we have tried that, but it doesn't look like upstream will commit
to releasing 3.28.4 in time for Ubuntu 18.04.2 LTS. Nor is upstream
willing to let the Ubuntu developers handle the 3.28.4 release.

https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule

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

Title:
  SRU 3.28 latest git to bionic

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1811900/+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 1811530] Re: Impress embeded video files show flickering white stripes

2019-01-17 Thread klinge
after experimenting with different slideshows: it does change somehow,
there are some videos that work fine now, others show green patches
instead and some still show the same error than with the old packages.

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

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1811530/+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 1811530] Re: Impress embeded video files show flickering white stripes

2019-01-17 Thread klinge
There is no change with the newest upstream packages. The behavior stays
the same. As addition I give some apport informations from a second pc
that shows the same behavior.

** Tags added: third-party-packages

** Description changed:

  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.
  
  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.
  
  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.
  
  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.
  
  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-04-11 (280 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
+ Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
+ Tags: third-party-packages bionic
+ Uname: Linux 4.15.0-43-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
+ _MarkForUpload: True

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

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

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

2019-01-17 Thread klinge
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1811530/+attachment/5229991/+files/Dependencies.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/1811530

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

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

2019-01-17 Thread klinge
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1811530/+attachment/5229993/+files/ProcEnviron.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/1811530

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

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

2019-01-17 Thread Sebastien Bacher
Thank you for your bug report. The item works fine here (tested on an
Ubuntu iso, the mount gets added in the nautilus sidebar and can be
browsed), gnome-disk-utility does provide a similar option though so
there is no need to keep that custom one

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

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

-- 
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 Committed

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 1811530] ProcCpuinfoMinimal.txt

2019-01-17 Thread klinge
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1811530/+attachment/5229992/+files/ProcCpuinfoMinimal.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/1811530

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1811530/+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 870632] Re: cheese captures automatically and blanks the screen until logout

2019-01-17 Thread Paul White
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.04 (natty) reached end-of-life on October 28, 2012 and
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 using a
currently supported version of 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: 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/870632

Title:
  cheese captures automatically and blanks the screen until logout

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  I start cheese, and cheese photo capture automatically and  blanks the
  screen until logout. The photo it's in /home/usr/Webcam_Pictures, but
  logout user and applications...

  I have Creative Live! Cam Vista IM VF0260 working without problems in
  camorama

  
  Ubuntu 11.04
  cheese:
Instalados: 2.32.0-0ubuntu2
Candidato:  2.32.0-0ubuntu2
Tabla de versión:
   *** 2.32.0-0ubuntu2 0
  500 http://es.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  100 /var/lib/dpkg/status

  What you expected to happen?
  1. Not photo automatically
  2. Not logout in photo capture

  What happened instead?
  1. Photo automatically
  2. Logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/870632/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-01-17 Thread Rocko
@Daniel: I still see this bug occasionally in 18.10 and 19.04. When it
happens, the ubuntu dock and the status bar still work, but none of the
applications will accept any input, including gnome-terminal. You can
switch applications using the dock, but alt-tab doesn't do anything, and
ALT-F2 doesn't work.

At this point all I have figured out to try is to go to another tty
console and try "DISPLAY=:0 gnome-shell --replace". When I switch
back to the gnome-shell tty (usually tty2), it restarts and all is fine
for a some time (just now it was fine for around 20 seconds) and then
gnome-shell completely and I'm back at the login screen on tty1.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1801496] Re: Printing job in 16.04 is slower than in 14.04

2019-01-17 Thread Till Kamppeter
Sorry for the late reply, I had some other more urgent tasks to do.

I have looked into your log.

foomatic-rip was running for 5 seconds (09:09:52 - 09:09:57) and it ran
this time due to the Ghostscript process it called and which by itself
ran at least 4 seconds. This does not look for a very long time and if
you think this is for the document which you had sent, it is a problem
of Ghostscript. As foomatic-rip calls the pdftops filter of cups-filters
and then pdftops calls Ghostscript for actually converting the incoming
PDF to PostScript, you can let pdftops use Poppler instead of
Ghostscript for this task to see whether Poppler processes the job more
quickly.

To switch pdftops to Poppler, use the "pdftops-renderer=pdftops" option
(see README of cups-filters, /usr/share/doc/cups-filters/README.gz).

If with Poppler your jobs go more quickly, report a bug on
www.ghostscript.com, supplying a sample input file and the Ghostscript
command line (you find it in CUPS' error_log). Before doing this please
also try to run the Ghostscript command line directly on the input file
from a terminal window, to check whether Ghostscript was really that
slow. Also printing very many and/or big jobs in a row and observing the
output of the "top" command could help.

If the problem is not the slowness of Ghostscript but the "Removing
document files." task afterwards taking a full minute (does this make
the next job wait that minute?) report a bug on www.cups.org. Note that
this delay is not caused by Ghostscript or foomatic-rip as these
processes had already ended before.

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

Title:
  Printing job in 16.04 is slower than in 14.04

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04LTS
  OS Version:   16.04.5
  CUPS Version: 2.1.3
  Ghostscript Version:  9.25 (2018-09-13)

  Printing job in 16.04 is slower than in 14.04

  We(RICOH printer driver developer) are report a problem from our printer 
users:
  I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds).

  But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I
  print the same file with the same driver is slow(326 Seconds).

  I figure out that all the print jobs is much slower on Ubuntu 16.04.

  I view the "CUPS Error Log",   it shows that there are three points
  which maybe the reasons that makes the print job slowly.

  
  FIRST:
  
  By counting the time from "Starting renderer" to "renderer exited with status 
0", we figure out that 16.04 spend more time than 14.04 on "renderer" process.
  So we assuming that:"renderer" is one of the key process that makes the print 
job slowly.

  "Starting renderer with command: \"printf \'\\033%%-12345X@PJL 
JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\  @PJL 
EOJ\\012\\033%%-12345X\'\""
  .
  renderer exited with status 0"
  


  SECOND:
  
  On 16.04, a print job outputs lots of logs as below:
  "[Job xxx] Removing document files."

  This step(“Removing document files”)does not exsit on 14.04.
  

  
  The phenomenon that print jobs slower in 16.04 is more obvious when printing 
many jobs in the same time.

  THIRD
  We tried drivers form other company(HP,Brother…), the printings also slow 
down in Ubuntu 16.04 than 14.04.

  Our question is:
  1. Do you have any plan to improve the performance of printing on Ubuntu 
16.04?
  2. Do you have any workaround before this problems fixed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+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 1795703] Re: Ubuntu Dock gets replaced with a standard GNOME one after a while

2019-01-17 Thread Launchpad Bug Tracker
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 in Ubuntu.
https://bugs.launchpad.net/bugs/1795703

Title:
  Ubuntu Dock gets replaced with a standard GNOME one after a while

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

Bug description:
  I don't reboot my desktop and don't hibernate it, it just works for
  multiple days in a row without a reboot. I only turn off the monitor
  when I go out.

  Sometimes, after a while, when I turn on the monitor, Ubuntu's Dock is
  no longer there and what I get is the GNOME Dock which is hidden and
  can be seen by pressing "Super" (which shows all windows as well).
  This is annoying.

  Not sure if related, but here's what I've found in the journalctl
  logs: https://gist.github.com/k-bx/3a11b3ae34531a0dd2eb9cdaac97cf6c

  > JS ERROR: TypeError: this._workspaceIsolation is undefined

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  2 19:32:07 2018
  InstallationDate: Installed on 2018-08-30 (32 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795703/+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 1800477] Re: Extensions are disabled after unlocking the screen

2019-01-17 Thread Launchpad Bug Tracker
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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1800477

Title:
  Extensions are disabled after unlocking the screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Quite often all the extension (excepted the dock) are disabled after
  unlocking the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 29 15:00:52 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1567 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (218 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+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 1800477] Re: Extensions are disabled after unlocking the screen

2019-01-17 Thread Ernst Sjöstrand
I think I have this problem too.
I also have this in my session log:

oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: == Stack trace for context 
0x55f6851611c0 ==
oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #0   7ffc4b206740 b   
resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7fd1489cc040 @ 25)
oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #1   55f697d100f0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fd116ba3dc0 @ 20)
oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #2   7ffc4b2076e0 b   
self-hosted:261 (7fd1489c1dc0 @ 223)
oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #3   55f697d10038 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fd116ba3d30 @ 172)
oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #4   7ffc4b2087f0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fd1489b0b80 @ 71)
oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #5   55f697d0ff58 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:235 
(7fd116ba39d0 @ 102)
oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #6   7ffc4b209760 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fd1489b0b80 @ 71)
..

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

Title:
  Extensions are disabled after unlocking the screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Quite often all the extension (excepted the dock) are disabled after
  unlocking the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 29 15:00:52 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1567 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (218 days ago)

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

2019-01-17 Thread Sebastien Bacher
Testing on 18.10 the "progressive dimming before blanking" doesn't reset
the color profile here. Could you trigger the bug and add the systemctl
log from around the time the bug manifest itself?

-- 
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 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-17 Thread Douglas Kosovic
Sorry ignore comment #16 as the following line in /etc/ppp/ip-
up.d/usepeerdns will exit because of the '#!/bin/sh -e' shebang
line:

cp -Lp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"


So my original suggestion of replacing the following line:

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

to:

cp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
chmod 644 "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

was correct and won't prematurely exit.

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  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/+bug/1778946/+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 467303] Re: gnome-terminal corrupted character display at the VIM cursor ?25I

2019-01-17 Thread Paul White
Bug did not expire due to assignment
No comments for nearly 8 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/467303

Title:
  gnome-terminal corrupted character display at the VIM cursor ?25I

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  Ubuntu 9.04  gnome-terminal

  Repro:
  ssh into an HPUX box and run vim

  When you enter Insert mode the some characters will be displayed on top of 
the cursor: '[?25I ' and these characters _appear_ highlighted.  The second 
character '[' appears to overlap the the previous character a little and is 
cutoff by the next character.
  When you hit Esc to return to command mode and move the cursor, the same 
characters are displayed but they will not be highlighted.

  This also occurs when scrolling, and typing in insert mode.

  Details:
  These characters are not in the vim buffer, and will usually disappear if you 
resize the window.

  Highlighting the characters that appear highlighted inverts the colors (on my 
grey on black screen they become white on black)
  Highlighting the non-highlighted characters appears normal.

  Changing the 'text' color in profiles affects all characters, and no
  other palette changes affect any characters.

  Testing:
   HPUX PA-Risc 11.00, vim 7.2
   HPUX IA64 11.31, vim 7.1

  Ubuntu 9.04 fully patched
  gnome-terminal:
Installed: 2.26.0-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/467303/+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 1170164] Re: can't switch input method at all

2019-01-17 Thread Paul White
is this still an issue or can this report be closed now?

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

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

Title:
  can't switch input method at all

Status in ibus:
  Incomplete
Status in gnome-terminal package in Ubuntu:
  Incomplete

Bug description:
  Normally gnome-terminal allows the user to switch the input method by
  pressing a special key combination.

  Sometimes gnome-terminal gets into a state where it seems to ignore
  the special key combination for switching the input method in ibus -
  it is permanently locked in the default input method for English.
  There is no clear pattern of usage or trigger for when it happens.

  1. The problem is not solved by resetting the terminal using the menu 
Terminal -> Reset, or Terminal -> Reset and Clear
  2. The problem is also not solved even by starting a new gnome-terminal from 
the menu, File -> Open Terminal -> Default
  3. However, using the command-line to start a new terminal with the factory 
disabled does make input method switching work again:  gnome-terminal 
--disable-factory   but doing this obviously loses all the session information 
in the previous gnome-terminal.
  4. Also, when the problem occurs, opening a new tab re-enables the input mode 
to be switched in the new tab as well as in the original tab. However, the 
problem usually re-occurs soon in the original tab.

  This has been happening in all versions of Ubuntu since 10.04 until
  12.04.02 precise, with gnome-terminal up to and including version
  3.4.1.1-0ubuntu1 and ibus version 1.4.1-3ubuntu1

  This is a really annoying bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1170164/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-17 Thread Douglas Kosovic
I can confirm the issue is the following line in /etc/ppp/ip-
up.d/usepeerdns as previously mentioned :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

The variable expansion of that line is :
cp -a /run/systemd/resolve/stub-resolv.conf 
/run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0

I had to modify the shebang line of that script from :
  #!/bin/sh -e
to :
  #!/bin/sh
to get past that line and output debugging output I inserted, which included :

ls -l /run/systemd/resolve/stub-resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 720 Jan 17 21:47 
/run/systemd/resolve/stub-resolv.conf

ls -l /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0
-rw--- 1 root root 720 Jan 17 21:47 
/run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0

So 'cp -a' isn't copying the permissions. Oddly, $? is 0 after running
that 'cp -a' line, therefor seems correct, also umask is 0022, so I'm
not sure what is going wrong.


Anyway a fix seems to be to change the following line in 
/etc/ppp/ip-up.d/usepeerdns from :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

to:

cp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
chmod 644 "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"


For Ubuntu 18.04 setups that have the pppconfig package installed, the
following lines in /etc/ppp/ip-up.d/0dns-up probably should be changed
from :

/bin/cp -Lp "$RESOLVCONF" "$RESOLVBAK" || exit 1
/bin/cp -Lp "$TEMPRESOLV" "$RESOLVCONF" || exit 1
chmod 644 "$RESOLVCONF" || exit 1

to:

/bin/cp -Lp "$RESOLVCONF" "$RESOLVBAK" || exit 1
chmod 644 "$RESOLVBAK" || exit 1
/bin/cp -Lp "$TEMPRESOLV" "$RESOLVCONF" || exit 1
chmod 644 "$RESOLVCONF" || exit 1

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  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/+bug/1778946/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

2019-01-17 Thread Douglas Kosovic
Correction the following line in /etc/ppp/ip-up.d/usepeerdns
probably should be changed from :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

to:

cp -Lp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
chmod 644 "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  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/+bug/1778946/+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 403015] Re: hindi language font not working on terminal.

2019-01-17 Thread Paul White
Bug did not expire due to assignment
No comments for over 9 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid

manish,

Please create a new bug report if you see a similar issue in a currently
supported version of Ubuntu.

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/403015

Title:
  hindi language font not working on terminal.

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  after installing language fonts (whichever i could find) hindi font
  doesn't seem to work. Hindi words are not appearing properly.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gnome-terminal
  Package: gnome-terminal 2.26.0-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  Uname: Linux 2.6.28-11-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/403015/+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 505401] Re: cursor jumps to the beginning after typing 20 characters or more

2019-01-17 Thread Paul White
Bug did not expire due to assignment
No comments for nearly 6 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/505401

Title:
  cursor jumps to the beginning after typing 20 characters or more

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  after update kernel to 2.6.31.17 cursor jumps to the beginning after
  typing 20 characters or more

  ProblemType: Bug
  Architecture: i386
  Date: Sun Jan 10 05:50:23 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: fglrx
  Package: gnome-terminal 2.28.1-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: gnome-terminal
  Uname: Linux 2.6.31-17-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/505401/+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 361283] Re: shift-ctrl-t fails to open tab on MID

2019-01-17 Thread Paul White
Bug did not expire due to assignment
No comments for over 6 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/361283

Title:
  shift-ctrl-t fails to open tab on MID

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  In jaunty daily build of MID edition from today, I am trying to work in a 
gnome-terminal session and noticed that shift-ctrl-t does not open a tab, but 
instead returns the error:
  Couldn't execute command: uxterm -fa Monospace -fs 12
  Verify that this command exists.

  I also tried opening a tab from the menu, and that works, but doing it with 
the hotkey does not.
  I attempted to try it again after installing the xterm package, and it does 
behave differently, but still not correctly.  After installing xterm, pressing 
shift-ctrl-t results in another terminal screen being opened, but it is just a 
large xterm screen rather than a gnome terminal session, and it is NOT opened 
in a tab, but rather as a full screened window.

  gnome-terminal version is 2.26.0-0ubuntu2
  xterm version is 241-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/361283/+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 487591] Re: Control-backslash gets transformed to

2019-01-17 Thread Paul White
Bug did not expire due to assignment
No comments for over 9 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid


** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/487591

Title:
  Control-backslash gets transformed to <

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  I use Control-backslash as a shortcut in midnight commander and some people 
use it to send a signal.
  After upgrade do Karmic this stopped working on my computer because now 
ctrl+\ becomes <.
  Since the < character is available on most keyboards, there is usually no 
need for extra way of entering it.
  Control+backslash is what is needed.
  I believe that this is a bug, because the keyboard layout that I use do not 
translate ctrl+\ to <. In other words, the need for this translation would be 
expressed as part of keyboard layout, not gnome-terminal-specific behavior.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Nov 24 13:17:15 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  Package: gnome-terminal 2.28.1-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: gnome-terminal
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/487591/+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 328155] Re: "xclip -selection clipboard" does not paste to terminal

2019-01-17 Thread Paul White
Bug did not expire due to assignment
No comments for over 8 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid


** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/328155

Title:
  "xclip -selection clipboard" does not paste to terminal

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  I have a script which copies some things to clipboard via xclip.  I
  use the "-selection clipboard" option to allow me to paste the results
  into apps with Ctrl-V keyboard shortcut.  This works fine in GUI apps
  such as gedit for example, but I can not paste the clipboard directly
  into gnome-terminal.

  Steps to reproduce:
  In gnome-terminal run the following command:
  echo testing123 | xclip -selection clipboard
  attempt to paste clipboard back to terminal with Ctrl-Shift-V

  Actual Results:
  nothing is pasted

  Expected results:
  "testing123" is pasted onto the terminal command line

  Reproducible: Always

  The only way I can now paste my clipboard to gnome-terminal is to open
  a GUI app, paste with Ctrl-V, select the text again, and copy to
  clipboard again with Ctrl-C.  After doing this, I can paste into
  gnome-terminal with Ctrl-Shift-V.

  I'm not exactly sure if this is an xclip or gnome-terminal issue, but
  I've filed it under gnome-terminal for now.

  Ubuntu 8.10
  xclip 0.08-8
  gnome-terminal 2.24.1.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/328155/+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 562339] Re: strange behaviour when switching tabs in "Full Screen" mode

2019-01-17 Thread Paul White
Bug did not expire due to bug watch
No comments for over 8 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid


** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/562339

Title:
  strange behaviour when switching tabs in "Full Screen" mode

Status in GNOME Terminal:
  Expired
Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  I have a dual monitor setup.

  1) start gnome terminal
  2) Press F11 to go to fullscreen mode
  3) create a new tab
  4) switch between the tabs (to the new one and back)

  i've seen the following behaviour:
  when switching twice the first time the window changes the monitors (from 
left to right)
  next switching the window moves to the next virtual workspace
  it eventually reappears on the first workspace where it all started.

  another time the tabs was detached and two gnome termnial windows
  where visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-terminal 2.29.6-0ubuntu5 [modified: usr/bin/gnome-terminal]
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  Architecture: amd64
  Date: Tue Apr 13 16:47:41 2010
  ExecutablePath: /usr/bin/gnome-terminal
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/562339/+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 403493] Re: switching tabs, tab gets lose

2019-01-17 Thread Paul White
Bug did not expire due to assignment
No comments for over 9 years
Bug refers to GNOME 2 version of terminal
Closing as the report is now invalid

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => 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/403493

Title:
  switching tabs, tab gets lose

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  When I click on a tab, often not always the tab get lose conected and
  get its own window. I'm not sure why. I tried to reproduce it by

  I guess this is a function that does not work correctly. When you drag
  your tab down it should not open in a new window. Only when you
  explicitly move the tab out of the screen, or hold the tab for a while
  when you drag it.

  Now it happens on split seconds and is not predictable.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gnome-terminal
  Package: gnome-terminal 2.26.0-0ubuntu2
  ProcEnviron:
   PATH=(custom, user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  Uname: Linux 2.6.28-13-generic x86_64

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


  1   2   >