date:20190327

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

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

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

Title:
  Firefox unresponsive for a few seconds if using the globalmenu
  extension

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I'm using firefox with the globalmenu extension. After selecting the
  firefox window, the first attempt to interact with the program (i.e.
  open or close tab, select a tab, scroll down the webpage etc.) makes
  the program unresponsive and the CPU runs at 100% for a few seconds.
  Afterwards, the required action is performed and the program works
  fine until the focus is moved to another window and back to the
  firefox window, then the problem appears again. I've noticed that
  disabling the globalmenu extension solves the problem.

  I'm on Ubuntu 12.10 with

  unity 6.12.0
  firefox 19.0
  firefox-globalmenu 19.0 (in the firefox add-ons page is described as Global 
Menu Bar Integration 3.7.1)

  also affects firefox 20

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

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

[Desktop-packages] [Bug 1610608] Re: Browser slowdown: cause: global menu integration with many bookmarks

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

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

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

Title:
  Browser slowdown: cause: global menu integration with many bookmarks

Status in firefox package in Ubuntu:
  Expired

Bug description:
  OS: Ubuntu Desktop 14.04.5 LTS (fully up to date)
  Firefox: 48.0 build 2 (it's the package supplied by default in Ubuntu)

  The problem:
  I have ~2200 bookmarks in my Firefox profile.  These are being displayed in 
the Unity global menu.  This causes the following problems:
   * Firefox becomes unresponsive for roughly 2 seconds every 15 seconds.
   * The Ubuntu Unity global menu system itself starts to misbehave.

  Regarding the "misbehaving".  One example is this.  My email client
  has a menu bar.  When Firefox is running in the background and my mail
  client is focused, I can press the Alt key to search the menu.  I type
  a few key strokes and I then hit enter on the option I want.  Nothing
  happens.  So the menu searching and displaying is working but you
  can't actually activate an item.  This issue only occurs with Firefox
  running.

  Work-around:
  go to: about:config
  set: ui.use_unity_menubar;false
  observe that Firefox is now once again responsive to use.

  My old work-around:
  Before Firefox 48.0 I was able to work around this issue by simply making 
sure that the vast majority of my bookmarks were not displayed in the 
"Bookmarks Menu".  Now that the latest release of Firefox has forced all 
bookmarks (including "Other Bookmarks") to appear in the menu, this work around 
does not work.  So I now have to disable Unity menu bar integration.

  One possible fix:
  Override the new Firefox behaviour that forces "Other Bookmarks" to display 
in the menu.  This means users have the option of making their bookmarks not be 
loaded into the Unity global menu.  If you did this, it may also be worth 
adding some code to detect vast numbers of bookmarks being displayed in the 
global menu.  When this occurs you could display a message to the user 
informing them that they should move bookmarks out of the "Bookmarks Menu" and 
into "Other Bookmarks" (as visible in the Firefox "Library").

  I expect I'm not the only long-term Firefox user to have built up over
  2000 bookmarks.  I expect many users wont be able to find the cause of
  the Firefox slow downs and global menu misbehaving, so they will be
  stuck with it or will switch to another browser.

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

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

[Desktop-packages] [Bug 1658739] Re: Javascript "Slow script" message blocks Firefox exit

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

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

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

Title:
  Javascript "Slow script" message blocks Firefox exit

Status in firefox package in Ubuntu:
  Expired

Bug description:
  If the computer is running out of memory and one attempts to shut down
  Firefox while there're some scripts that are running continously(*)
  you get the "Do you want to stop the script?" message. And that
  message actually blocks Firefox from exiting despite the fact that the
  exit was initiated before the message appeared.

  (*) In my case the script was the Chat-Window script on VK.com
  (Russian social media site).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 50.1.0+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   volodya2950 F...m pulseaudio
   /dev/snd/controlC0:  volodya2950 F pulseaudio
  BuildID: 20161209095719
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Mon Jan 23 20:13:28 2017
  DefaultProfileIncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Russian (RU) Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePlugins:
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  DefaultProfilePrefSources: prefs.js
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-19 (735 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.5  metric 
600
  MostRecentCrashID: bp-f36c5229-fdc5-4162-8935-6cbb22150802
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=50.1.0/20161209095719
   Profile1 - LastVersion=30.0/20140608211208 (Out of date)
  RelatedPackageVersions:
   google-talkplugin 5.41.3.0-1
   adobe-flashplugin 1:20170110.1-0ubuntu0.16.04.1
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs: bp-f36c5229-fdc5-4162-8935-6cbb22150802
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (178 days ago)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N76VB.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N76VB
  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.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N76VB
  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/firefox/+bug/1658739/+subscriptions

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

[Desktop-packages] [Bug 1718008] Re: Dragging Tab to Toolbar Bookmark Folder doesn't work when most right tab

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

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

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

Title:
  Dragging Tab to Toolbar Bookmark Folder doesn't work when most right
  tab

Status in firefox package in Ubuntu:
  Expired

Bug description:
  State:

   * Some tabs open, one of them babeljs.io
   * Bookmark toolbar is visible.
   * Created a new bookmark folder, which is now the top right.

  Problem:
  Trying to drag open tabs onto the new folder to bookmark the links.

  Some tabs, when dragged over the folder, activate it and the folder
  opens to make drop possible (expected behaviour).

  Dragging the babeljs.io tab over the bookmark toolbar opens each
  bookmark folder but not the new one at most right position.

  Trying to reposition the most right bookmark folder by dragging to
  another position doesn't work either, the folder can't be grabbed.

  Grabbing any other bookmark folder and moving that to the most right
  position repeats this effect for that folder now.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   det1804 F...m pulseaudio
   /dev/snd/controlC1:  det1804 F pulseaudio
   /dev/snd/controlC0:  det1804 F pulseaudio
  BuildID: 20170816210634
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Sep 18 20:50:34 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2012-10-07 (1806 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.104  
metric 600
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816210634 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to xenial on 2016-08-16 (397 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1225B
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 204
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/14/2011:svnASUSTeKComputerInc.:pnR252B:pvr1.0:rvnASUSTeKComputerInc.:rn1225B:rvr204:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: R252B
  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/firefox/+bug/1718008/+subscriptions

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

[Desktop-packages] [Bug 1822023] [NEW] left click "put-in method" icon in indicator, no response

2019-03-27 Thread liumin

Public bug reported:

system:ubuntukylin-19.04-beta-0328

test-steps
1.left click "put-in method" icon in indicator

actual result:no response

expect result:popup menu bar

** Affects: ubuntukylin
 Importance: Undecided
 Assignee: handsome_feng (feng-kylin)
 Status: New

** Affects: indicator-keyboard (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: disco-beta

** Also affects: indicator-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  left click "put-in method" icon in indicator, no response

Status in Ubuntu Kylin:
  New
Status in indicator-keyboard package in Ubuntu:
  New

Bug description:
  system:ubuntukylin-19.04-beta-0328

  test-steps
  1.left click "put-in method" icon in indicator

  actual result:no response

  expect result:popup menu bar

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

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

[Desktop-packages] [Bug 1821960] Re: [wma codec problem, playback] Playback problem

Do you encounter audio stuttering in any other apps?

** Package changed: alsa-driver (Ubuntu) => quodlibet (Ubuntu)

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

** Summary changed:

- [wma codec problem, playback] Playback problem
+ Audio sometimes stutters in Quod Libet in a VM

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

Title:
  Audio sometimes stutters in Quod Libet in a VM

Status in quodlibet package in Ubuntu:
  Incomplete

Bug description:
  The song Waterloo of ABBA plays correct with 
  Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it 
stutters badly with 
  Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
  I use Quod Libet as audio payer.
  The song plays for one second, halts for one second and than plays again for 
a second.
  I have the same problem with all my thousands of other songs with the Windows 
Media Audio 9.2 format.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1987 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1987 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1987 f pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 27 14:36:21 2019
  InstallationDate: Installed on 2018-11-08 (139 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181108)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH 
successful
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [ICH - Intel 82801AA-ICH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

2019-03-27 Thread lathiif aji santhosho

Asus Vivobook A407UF

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

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

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

Title:
  [04f3:0903] Elan Microelectronics Corp fingerprint reader not
  recognised

Status in libfprint:
  New
Status in libfprint package in Ubuntu:
  Incomplete

Bug description:
  Running "fprint-demo" with this hardware installed reports "No devices
  found".

  This is the integrated reader in new ASUS ZenBook UX390UA laptops.

  lsusb -v output here: http://paste.ubuntu.com/23464942/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libfprint0 1:0.6.0-2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 12 15:59:17 2016
  InstallationDate: Installed on 2016-11-08 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: libfprint
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported

If the problem is the kernel version then please try to find the closest
two versions where one works and the other does not, from this list:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions

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

[Desktop-packages] [Bug 1822019] Re: /usr/bin/gnome-shell:11:ShouldMark:DoMarking:JSScript::traceChildren:js::GCMarker::processMarkStackTop:js::GCMarker::drainMarkStack

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

** This bug has been marked a duplicate of private bug 1821954

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

Title:
  /usr/bin/gnome-
  
shell:11:ShouldMark:DoMarking:JSScript::traceChildren:js::GCMarker::processMarkStackTop:js::GCMarker::drainMarkStack

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/583ecffd8129325dec411b34664400a910167abd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported

Derek, are you saying kernel 4.18 (or earlier) does not have the bug?

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions

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

[Desktop-packages] [Bug 1821849] Re: LibreOffice Impress 6.2.2.2 Embedded Video Problem

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

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

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

Title:
  LibreOffice Impress 6.2.2.2 Embedded Video Problem

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The following bugs are for LibreOffice 6.2.2.2 Impress on Kubuntu
  19.04.

  When I start a slide-show with Impress by using either F5 or Shift F5,
  I get a white screen.  When I click on it, the slide is displayed.
  When I exit the presentation with say "Esc", soffice.bin is in the
  taskbar with the odp file used for the presentation.  If I click on
  the odp file and exit, both tasks are removed.

  Now when I advance to an embedded video I get the image shown with
  this report. When the video is started, the previous slide is shown on
  top of the video as it is being played. Not a good view This
  happens when either starting from the first slide or the one preceding
  embedded video.

  I have tried the gtk3 options in https://launchpad.net/bugs/1820062
  and the changes make no difference to this problem.  I have also
  installed gstreamer1.0-plugins-* which solved  previous problem with
  LibreOffice.

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

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

[Desktop-packages] [Bug 1822019] [NEW] /usr/bin/gnome-shell:11:ShouldMark:DoMarking:JSScript::traceChildren:js::GCMarker::processMarkStackTop:js::GCMarker::drainMarkStack

2019-03-27 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/583ecffd8129325dec411b34664400a910167abd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: disco

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

Title:
  /usr/bin/gnome-
  
shell:11:ShouldMark:DoMarking:JSScript::traceChildren:js::GCMarker::processMarkStackTop:js::GCMarker::drainMarkStack

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/583ecffd8129325dec411b34664400a910167abd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1821933] Re: Touch input is misaligned with two screens

Please also run:

  apport-collect 1821933

so it's clear in the bug what package versions are affected.

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

Title:
  Touch input is misaligned with two screens

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using touch input with one screen seems fine.
  However, when connecting a second screen the touch event happens at the wrong 
coordinates.

  Steps to reproduce
  1. Starting with a single screen touch and hold on the background and drag.  
The rubber band selector shows up with the moving corner at your finger.
  2. Connect a second screen
  3. Do the same touch and drag as in step 1 and notice that the moving corner 
is offset to the right and slightly below where the touch is happening.

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

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

[Desktop-packages] [Bug 1821933] Re: Touch input is misaligned with two screens

Will,

Can you detail what scaling factors you are using, as well as running:

  xrandr > xrandr.txt

and attach the file 'xrandr.txt'?

** Tags added: disco

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

Title:
  Touch input is misaligned with two screens

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using touch input with one screen seems fine.
  However, when connecting a second screen the touch event happens at the wrong 
coordinates.

  Steps to reproduce
  1. Starting with a single screen touch and hold on the background and drag.  
The rubber band selector shows up with the moving corner at your finger.
  2. Connect a second screen
  3. Do the same touch and drag as in step 1 and notice that the moving corner 
is offset to the right and slightly below where the touch is happening.

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

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

[Desktop-packages] [Bug 1821904] Re: Gnome Shell always started muted on Disco

Please run these commands:

1. apport-collect 1821904

2. dpkg -l > allpackages.txt

and then attach the file 'allpackages.txt' to this bug.

** Tags added: disco

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

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

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

Title:
  Gnome Shell always started muted on Disco

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On Disco, Gnome Shell always starts muted.

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

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

[Desktop-packages] [Bug 1821895] Re: Gnome Shell crashes after resume on Disco

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Tags added: disco

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

Title:
  Gnome Shell crashes after resume on Disco

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  System - XPS13 9370

  To the best of my knowledge, this was working fine last week.  I
  updated the system via Apt, the system fails to resume after being
  suspended (via lid close).  There is a blank screen for a few seconds,
  followed by the cursor appearing (still blank background) and then
  gnome crashes and comes back to the login screen.

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

Xubuntu daily images are still missing the fix for bug 1819943. So
please wait until a newer image is available which includes that fix
before retesting.

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

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

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

[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus

** Project changed: gnome-shell => mutter

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

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

** Changed in: mutter (Ubuntu)
   Importance: Undecided => High

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

Title:
  apps launched from gnome shell do not get input focus

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

Bug description:
  Observed on upgrading to disco-proposed today...

  When launching an app from the dock or from the applications grid (so
  i believe it's a gnome-shell thing rather than a dock thing), the app
  opens, but does not get the input focus. You have to either click in
  the window, or clicking again on the icon of the running app in the
  dock works, to give it focus. An extra step my muscle memory isn't
  prepared for!

  It seems like the sort of thing that might be an option rather than a
  bug, but if so, changing this behaviour back to its previous default
  is not at all obvious (I haven't found a way). So guessing it is a
  bug. NB: After launching an app this way, *no* window has focus. It is
  lost by the app that had it before, but not given to the newly started
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:53:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (169 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

stranger and stranger .. if you install kernel 5.0.0-8.9 at the first
boot into any new install partition before changing any thing else .. it
does not fix the issue .. once you return sda1 to being grub master ..
neither sda7 nor sda6 will keep lightdm running ..both briefly flash
lightdm login screen and then blank out screen , briefly showing a
cursor .. a long hold down of power button does eventually powerdown
machine .. note: can't even get to consoles .. not a nice fail.

note resetting grub back to the "new install version" works but there
is a stutter in lightdm .. it shows briefly blanks for 2 seconds then
shows again and and you can login..

only other way into partition is through recovery boot option, or via a
chroot.

this is now using xubuntu-am64-desktop.iso -beta version ( two installs
sda6 and sda7 )

I'm beginning to think that using a chroot to reinstall/or update the
kernel might be a "work around only" for the issue .. as a native update
does not work ..

I'm going to test this further .. replace sda6 and sda7 sequentially and
see what happens using chroots for updates more later .. any ideas
what else to look for or check?

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

Title:
lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
New

Bug description:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..

back ground .. PC is lenovo sl 500 with evo860 SSD drive

3 partions contain installs of disco sda1 -- main working system -- I
usually install grub from here as master ..

sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
03-22-2019 repectively

on the test installs as long as the iso is using the grub boot loader
installed from that install the system will boot normally .. the display manger
tends to flicker on and off but does final start and login can proceed.

but if another install re-installs grub as master the display manager
fails to stay active or even come-up for sda6 or sda7 only if their
own grubs are reinstalled will they work normally

sda1 display manager/xorg login works always no matter which "grub-
source" is in control.

if I use rescue boot from any grub as master I can get the displays to work
by running dpkg fix which does nothing .. and then resuming the boot .. then
things work normally..
if the "non-rescue" boots are used the screen/computer locks and only a power
down and reboot gives access. (sometime requiring radical depowering ..
unpluging and removing battery)

now the is a message that appears that RCs??? level is missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 25 11:25:58 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
InstallationDate: Installed on 2019-03-23 (1 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746CTO
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.modalias:
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 2746CTO
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2

[Desktop-packages] [Bug 1818766] Re: Update to 1.47

** Branch linked: lp:~ubuntu-desktop/snapd-glib/ubuntu

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

Title:
  Update to 1.47

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

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Any new release has a risk of introducing bugs, this is mitigated by 
automatic regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

2019-03-27 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821609

** Tags added: iso-testing

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

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

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

[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus

2019-03-27 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => 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/1817924

Title:
  apps launched from gnome shell do not get input focus

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Observed on upgrading to disco-proposed today...

  When launching an app from the dock or from the applications grid (so
  i believe it's a gnome-shell thing rather than a dock thing), the app
  opens, but does not get the input focus. You have to either click in
  the window, or clicking again on the icon of the running app in the
  dock works, to give it focus. An extra step my muscle memory isn't
  prepared for!

  It seems like the sort of thing that might be an option rather than a
  bug, but if so, changing this behaviour back to its previous default
  is not at all obvious (I haven't found a way). So guessing it is a
  bug. NB: After launching an app this way, *no* window has focus. It is
  lost by the app that had it before, but not given to the newly started
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:53:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (169 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

okay still bug present in xubuntu-disco-amd64-desktop-beta.. still uses
kernel 5.0.0-7

updating from proposed with  kernel 5.0.0-8.9  it works properly

i.e. any linux os partion can be used to install grub and another partion with 
linux can be 
selected and boot normally 

e.g. beta install is on sda7 another linux os version is on sda1 which is used 
to install grub to /dev/sda  thus sda1 is master/main linix os used .. the beta 
on sda7 will start lightdm but it flickers on and dies when using kernel 
5.0.0-7 
but when using kernel 5.0.0-8.9 it works properly lightdm stays running and 
does  not even flicker...  the only apparent difference is the kernel selected 
..

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

To manage notifications about this

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

** This bug is no longer a duplicate of bug 1819943
   intel video driver not installed by default in ubuntu 19.04 (Disco) [needed 
for graphics support on Intel Core 2 Duo systems]

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

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

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

[Desktop-packages] [Bug 1821505] Re: [radeon] screen cannot be turned back on after some time of inactivity

2019-03-27 Thread Hark

I believe this is a bug of higher importance as it makes 16.04 LTS in
standard configuration (with enabled screen blanking) unusable on the
ATI Radeon cards.

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

Title:
  [radeon] screen cannot be turned back on after some time of inactivity

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

Bug description:
  When using my AMD Radeon X1300 card, if the screen turns off due to
  inactivity, it cannot be woken up by moving the mouse or by hitting a
  key.

  If you type in a terminal:
  xset -display :0.0 dpms force off
  you can wake the screen normally.

  Typing the following in a terminal turns my screen off, and after typing this 
line, the screen can be woken up by moving the mouse or by hitting a key:
  gnome-screensaver-command -a

  When I restart the display manager via ssh with another computer, the
  screen then comes to life again and I can log back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 24 11:11:17 2019
  DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] 
[1458:215c]
  InstallationDate: Installed on 2010-05-13 (3236 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  MachineType: FUJITSU SIEMENS ESPRIMO E5720
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic 
root=/dev/mapper/orao-root ro rootfstype=ext4 quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago)
  dmi.bios.date: 02/05/2009
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.18.2594.A1
  dmi.board.name: D2594-A1
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D2594-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr:
  dmi.product.name: ESPRIMO E5720
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Mar 24 11:06:06 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Receiver KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1821505] Re: [radeon] screen cannot be turned back on after some time of inactivity

2019-03-27 Thread Hark

Here is the workaround for the problem:

The bug is in the package xserver-xorg-video-radeon 7.7.0, it is fixed in the 
later versions.
Until it is fixed in 16.04 LTS, take the package from the newer releases. 

In this example, we'll pull it from 16.10 (Yakkety Yak):
a) add the line at the end of the /etc/apt/sources.list file:
deb http://old-releases.ubuntu.com/ubuntu yakkety main
b) add file "yakkety.pref" to the /etc/apt/preferences.d
c) sudo apt-get update - this will load new repostiory and refresh the 
preferences
d) sudo apt-get upgrade - this will pull xserver-xorg-video-radeon package 
v7.7.1, with fixed bug.
e) log out from X

That's it. After login, wait for the screen blank and wake it with key
press or mouse action.


** Description changed:

  When using my AMD Radeon X1300 card, if the screen turns off due to
  inactivity, it cannot be woken up by moving the mouse or by hitting a
  key.
  
- WORKAROUND: Type in a terminal:
+ If you type in a terminal:
  xset -display :0.0 dpms force off
+ you can wake the screen normally.
  
- WORKAROUND: Typing the following in a terminal turns my screen off, and after 
typing this line, the screen can be woken up by moving the mouse or by hitting 
a key:
+ Typing the following in a terminal turns my screen off, and after typing this 
line, the screen can be woken up by moving the mouse or by hitting a key:
  gnome-screensaver-command -a
  
- WORKAROUND: When I restart the display manager via ssh with another
- computer, the screen then comes to life again and I can log back in.
+ When I restart the display manager via ssh with another computer, the
+ screen then comes to life again and I can log back in.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 24 11:11:17 2019
  DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] 
[1458:215c]
  InstallationDate: Installed on 2010-05-13 (3236 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  MachineType: FUJITSU SIEMENS ESPRIMO E5720
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic 
root=/dev/mapper/orao-root ro rootfstype=ext4 quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago)
  dmi.bios.date: 02/05/2009
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.18.2594.A1
  dmi.board.name: D2594-A1
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D2594-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr:
  dmi.product.name: ESPRIMO E5720
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Mar 24 11:06:06 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Receiver KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
  xserver.errors:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

** Attachment added: "apt preferences file for Yakkety Yak"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1821505/+attachment/5249927/+files/yakkety.pref

-- 
You received this bug notification

[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus

2019-03-27 Thread bwat47

they moved the issue... again

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #505
   https://gitlab.gnome.org/GNOME/mutter/issues/505

** Changed in: gnome-shell
   Status: New => Unknown

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1116 => 
gitlab.gnome.org/GNOME/mutter/issues #505

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

Title:
  apps launched from gnome shell do not get input focus

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Observed on upgrading to disco-proposed today...

  When launching an app from the dock or from the applications grid (so
  i believe it's a gnome-shell thing rather than a dock thing), the app
  opens, but does not get the input focus. You have to either click in
  the window, or clicking again on the icon of the running app in the
  dock works, to give it focus. An extra step my muscle memory isn't
  prepared for!

  It seems like the sort of thing that might be an option rather than a
  bug, but if so, changing this behaviour back to its previous default
  is not at all obvious (I haven't found a way). So guessing it is a
  bug. NB: After launching an app this way, *no* window has focus. It is
  lost by the app that had it before, but not given to the newly started
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:53:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (169 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1821900] Re: Ubuntu 19.04 Community Wallpapers

** Branch linked: lp:~osomon/ubuntu-wallpapers/disco-community-
wallpapers

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

Title:
  Ubuntu 19.04 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  In Progress

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.04.

  These have been resized to n x 2160 pixels at 72x72 dpi and then
  cropped to 16:9 where needed.

  They are all named Image_Title_by_Author_Name

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

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

[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported

Apologies my first run of apport was mainline 5.0. I immediately
rebooted and use a standard default kernel for 18.04. I deleted both
mainlines since they didn't solve my issue anyway.

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions

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

[Desktop-packages] [Bug 1821900] Re: Ubuntu 19.04 Community Wallpapers

2019-03-27 Thread Olivier Tilloy

** Changed in: ubuntu-wallpapers (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => In Progress

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

Title:
  Ubuntu 19.04 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  In Progress

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.04.

  These have been resized to n x 2160 pixels at 72x72 dpi and then
  cropped to 16:9 where needed.

  They are all named Image_Title_by_Author_Name

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

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

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

2019-03-27 Thread Andreas Hasenack

I just tried with my build from the ppa, but it's not working. When
enabling debugging in gvfsd, I can see it setting the protocol to NT1:

network: Added new job source 0x559ce1b3e070 (GVfsBackendNetwork)
network: Queued new job 0x559ce1b4cab0 (GVfsJobMount)
smb-network: g_vfs_backend_smb_browse_init: default workgroup = 'NULL'
smb-network: Added new job source 0x564f06543070 (GVfsBackendSmbBrowse)
smb-network: Queued new job 0x564f06549ac0 (GVfsJobMount)
smb-network: Error resolving “EXAMPLE”: Name or service not known
smb-network: Forcing NT1 protocol version
smb-network: do_mount - URI = smb://EXAMPLE


That message, "Forcing NT1 protocol version", comes from the gvfs patch and 
confirms that it is using the new smbc_setOptionProtocols() call.

If somebody else wants to try in the meantime, the packages for bionic
are at https://launchpad.net/~ahasenack/+archive/ubuntu/samba-browse-
nt1-1778322/

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

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

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  In Progress
Status in gvfs source package in Bionic:
  Triaged
Status in gvfs source package in Cosmic:
  Triaged

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

  * Test case
  Try to browse a smb share from a bionic client

  * Regression potential
  Check that smb browsing/mounts still work as they should

  ---

  Nautilus should show smbtree nad host on the smb network.

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

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

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

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

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

[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions

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

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

2019-03-27 Thread vvg

Надоело ждать релиза, сегодня накатил обнову по этой инструкции -
https://askubuntu.com/a/1121203/349837

Полёт нормальный языковая панель не исчезает . СПАСИБО 

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

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

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released

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

  [ Impact ]

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

  [ Test case ]

  1. Boot
  2. Suspend or lock the screen
  3. Log again with your user
  4. The keyboard indicator should display current layout

  [ Regression Potential ]

  Really low, we properly pass a null value instead of an undefined one,
  without breaking JS.

  --

  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)

  [ Workarounds ]

  - Switch 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.

  - Restart Gnome Shell (Alt+F2 r):
  https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools

  - 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-shell/+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 1821820] Re: Cannot boot or install - have to use nomodeset

2019-03-27 Thread fossfreedom

** Attachment added: "boot with the drm boot parameter but without nomodeset"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1821820/+attachment/5249898/+files/hang.txt

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

Title:
  Cannot boot or install - have to use nomodeset

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

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

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

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

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

2019-03-27 Thread fossfreedom

** Attachment added: "dmesg with nomodeset"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1821820/+attachment/5249897/+files/nomodeset.txt

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

Title:
  Cannot boot or install - have to use nomodeset

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

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

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

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

[Desktop-packages] [Bug 1821960] [NEW] [wma codec problem, playback] Playback problem

2019-03-27 Thread BertN45

Public bug reported:

The song Waterloo of ABBA plays correct with 
Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it 
stutters badly with 
Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
I use Quod Libet as audio payer.
The song plays for one second, halts for one second and than plays again for a 
second.
I have the same problem with all my thousands of other songs with the Windows 
Media Audio 9.2 format.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bertadmin   1987 F pulseaudio
 /dev/snd/pcmC0D0p:   bertadmin   1987 F...m pulseaudio
 /dev/snd/timer:  bertadmin   1987 f pulseaudio
CurrentDesktop: XFCE
Date: Wed Mar 27 14:36:21 2019
InstallationDate: Installed on 2018-11-08 (139 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181108)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH 
successful
Symptom_AlsaPlaybackTestStderr:
 W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
  x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   e 
r r o r 
  T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
Symptom_Card: Built-in Audio - Intel 82801AA-ICH
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [ICH - Intel 82801AA-ICH, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug disco

** Attachment added: "Screenshot_2019-03-27_14-35-24.png"
   
https://bugs.launchpad.net/bugs/1821960/+attachment/5249890/+files/Screenshot_2019-03-27_14-35-24.png

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

Title:
  [wma codec problem, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The song Waterloo of ABBA plays correct with 
  Windows Media Audio 9.1, VBR Quality 50, 44 kHz, stereo 1-pass VBR, but it 
stutters badly with 
  Windows Media Audio 9.2, VBR Quality 50, 44 kHz, stereo 1-pass VBR
  I use Quod Libet as audio payer.
  The song plays for one second, halts for one second and than plays again for 
a second.
  I have the same problem with all my thousands of other songs with the Windows 
Media Audio 9.2 format.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1987 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1987 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1987 f pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 27 14:36:21 2019
  InstallationDate: Installed on 2018-11-08 (139 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181108)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH 
successful
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [ICH - Intel 82801AA-ICH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias:

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

2019-03-27 Thread Andreas Hasenack

Builds in a ppa look good:
...
Native dependency smbclient found: YES 0.2.3
Checking for function "smbc_setOptionProtocols": YES
...

Checking for real with a bionic desktop now.

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

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

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  In Progress
Status in gvfs source package in Bionic:
  Triaged
Status in gvfs source package in Cosmic:
  Triaged

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

  * Test case
  Try to browse a smb share from a bionic client

  * Regression potential
  Check that smb browsing/mounts still work as they should

  ---

  Nautilus should show smbtree nad host on the smb network.

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

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

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

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

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

[Desktop-packages] [Bug 1821523] Re: Installed snaps miss dependencies and permissions

You don't need to.  snapd will pull in everything that is needed to run the 
snap.  If it doesn't then the problem is with the snap.  Perhaps the 
snapcraft.yaml doesn't specify the interfaces correctly for example.
This is not a bug in GNOME Software.


** Changed in: gnome-software (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  Installed snaps miss dependencies and permissions

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  When testing some text editors I have stumbled over multiple problems,
  after the software is installed.

  The first test was with notepad++. After installing the snap nothing
  worked. The program did not even start, nor provide some information
  what is wrong. After checking the interfaces of the notepad++ snap, I
  assume that there is a dependency to wine. At least the "notepad-plus-
  plus:wine-platform-plug" let me guess it.

  I was a little bit surprised that additional software is needed,
  because the software description in the software center did not
  mention any additional dependencies. Also I am used that the required
  dependencies are installed along with the selected software.

  I did not want to experiment with wine for now, so I have selected
  another editor: notepadqq. After the installation at least the program
  can be started, but no text files can be opened. The bug is also
  described at the project:
  https://github.com/notepadqq/notepadqq/issues/822

  On the Open File dialog a file system is visible that is not the file system 
of my PC. I guess it is the file system of the confined environment. The 
problem is that a text editor that can not access the files of my PC is useless.
  I had to install notepadqq with the classic option, so the file system of my 
PC can be accessed by notepadqq.

  The problem of software center is, that this step is not possible
  within the software center, but only via command line.

  I think it is important that the software center consider the dependencies 
when installing software and give the software all permissions needed to run.
  When permission should not be given without review/check/ the user can be 
asked what access right a software should get. At least an information should 
be given, that permissions are insufficient and how this can be changed.

  Cheers Matthias

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

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

[Desktop-packages] [Bug 1821523] Re: Installed snaps miss dependencies and permissions

2019-03-27 Thread Borim

> Generally speaking snaps do not have dependencies as such, everything is 
> bundled inside the snap.
> Some snaps use platform snaps to provide some core libs, but that's not 
> relevant in this case.

That snaps does not have dependencies is a nice theory, but as you said
that some snaps use platform snaps and without them they do not work. So
what should this relation be?

The problem I see is that the software center does not provide the information, 
which snaps are required to run an installed snap.
In the case of notepad++ I realized the dependency to wine only, because I 
analyzed the problem with the snap command. But software center does not give 
this information, nor does it solve the dependency.
Also when starting notepad++ no information is given, that something is 
missing. It simply does not start.

So the question I have is: How the casual user should recognize what is
missing to run a snap?

** Changed in: gnome-software (Ubuntu)
   Status: Invalid => Opinion

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

Title:
  Installed snaps miss dependencies and permissions

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  When testing some text editors I have stumbled over multiple problems,
  after the software is installed.

  The first test was with notepad++. After installing the snap nothing
  worked. The program did not even start, nor provide some information
  what is wrong. After checking the interfaces of the notepad++ snap, I
  assume that there is a dependency to wine. At least the "notepad-plus-
  plus:wine-platform-plug" let me guess it.

  I was a little bit surprised that additional software is needed,
  because the software description in the software center did not
  mention any additional dependencies. Also I am used that the required
  dependencies are installed along with the selected software.

  I did not want to experiment with wine for now, so I have selected
  another editor: notepadqq. After the installation at least the program
  can be started, but no text files can be opened. The bug is also
  described at the project:
  https://github.com/notepadqq/notepadqq/issues/822

  On the Open File dialog a file system is visible that is not the file system 
of my PC. I guess it is the file system of the confined environment. The 
problem is that a text editor that can not access the files of my PC is useless.
  I had to install notepadqq with the classic option, so the file system of my 
PC can be accessed by notepadqq.

  The problem of software center is, that this step is not possible
  within the software center, but only via command line.

  I think it is important that the software center consider the dependencies 
when installing software and give the software all permissions needed to run.
  When permission should not be given without review/check/ the user can be 
asked what access right a software should get. At least an information should 
be given, that permissions are insufficient and how this can be changed.

  Cheers Matthias

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

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

[Desktop-packages] [Bug 1724572] Re: vino-server crashed with SIGSEGV in _XSend()

2019-03-27 Thread Mark

When will this fix be completed in Ubuntu. I am running 18.04 and,
because of this bug, can't use screen sharing when using Wayland.

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

Title:
  vino-server crashed with SIGSEGV in _XSend()

Status in vino:
  Fix Released
Status in vino package in Ubuntu:
  Incomplete
Status in vino package in Debian:
  Fix Released

Bug description:
  Following upgrade from 17.04 (Gnome) to 17.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: vino 3.8.1-0ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Oct 18 12:59:52 2017
  ExecutablePath: /usr/lib/vino/vino-server
  InstallationDate: Installed on 2017-04-17 (183 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/lib/vino/vino-server
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f2a587b63ce <_XSend+126>:   mov(%rax),%rdx
   PC (0x7f2a587b63ce) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: vino
  StacktraceTop:
   _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
   XTestQueryExtension () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
   ?? ()
  Title: vino-server crashed with SIGSEGV in _XSend()
  UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago)
  UserGroups: sudo

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

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-: nvidia- kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

2019-03-27 Thread Alberto Milone

@Stefan: the first error looks like a bug in the compiler. As for the
second error, the 367.35 driver is not in the Ubuntu archive, therefore
we have no control over it.

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1821953] [NEW] warty-final-ubuntu.png is overwritten in revision 269

2019-03-27 Thread Marko Stanković

Public bug reported:

I've just noticed that warty-final-ubuntu.png is overwritten in
https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
wallpapers/ubuntu/revision/269 by what should be disco-final-ubuntu.png

** Affects: ubuntu-wallpapers (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  warty-final-ubuntu.png is overwritten in revision 269

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  I've just noticed that warty-final-ubuntu.png is overwritten in
  https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  wallpapers/ubuntu/revision/269 by what should be disco-final-
  ubuntu.png

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

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

[Desktop-packages] [Bug 1821952] [NEW] Sound Launcher Stays Minimize Upon Additional Launches

2019-03-27 Thread Lonnie Lee Best

Public bug reported:

I launch "Sound Settings" by going to the speaker icon by the clock and
then I click "Sound Settings".

After doing this, if that window become minimized, and I try to launch
"Sound Settings" again (in the manner described above, the minimized
window should regain focus, but it does not.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20171130-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 27 11:49:44 2019
InstallationDate: Installed on 2019-01-07 (79 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Sound Launcher Stays Minimize Upon Additional Launches

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

Bug description:
  I launch "Sound Settings" by going to the speaker icon by the clock
  and then I click "Sound Settings".

  After doing this, if that window become minimized, and I try to launch
  "Sound Settings" again (in the manner described above, the minimized
  window should regain focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20171130-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 27 11:49:44 2019
  InstallationDate: Installed on 2019-01-07 (79 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1740869] Re: is not responding window is constantly showing when debugging a program

2019-03-27 Thread Treviño

Andrea, if you want to prepare a merge proposal against bionic we can
merge it in the VCS for now and then when I prepare the new SRU for
bionic with other fixes land it... As you wish

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

** Tags added: fixed-3.32 fixed-upstream

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

Title:
   is not responding window is constantly showing when
  debugging a program

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Mentioned window about no responding program is showing and stealing
  focus when I try to debug a Java program in Eclipse. When I click on
  Wait, it disappears for a moment and opens again.

  This renders Ubuntu 17.10 with Gnome 3 nearly useless for program
  debugging.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  2 14:22:56 2018
  InstallationDate: Installed on 2017-12-04 (28 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: mutter
  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/1740869/+subscriptions

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

[Desktop-packages] [Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()

2019-03-27 Thread Treviño

Actually not... I misread the title.

** Tags removed: fixed-3.32.1 fixed-upstream

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

Title:
  gnome-shell crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a() from g_object_ref() from
  st_theme_get_custom_stylesheets()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d

  ---

  Todays update had a kernal and   my gnome shell update. Happened when
  I rebooted.  I now have a black screen and no panel. Icons are all
  that shows up on desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul  3 12:46:31 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: gnome-shell --sm-client-id 
102c52716a25d9b2dd1495780366603150001329
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9bec254d5c 
:  movzbl 0x14(%rax),%edx
   PC (0x7f9bec254d5c) ok
   source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_theme_get_custom_stylesheets () from 
/usr/lib/gnome-shell/libgnome-shell.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1498082] Re: chromium-browser file upload widget needs better memory checking crashes on file upload selector

Thanks for your reply. Closing as being fixed.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  chromium-browser file upload widget needs better memory checking
  crashes on file upload selector

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  
  The file upload browser widget in cromium-browser needs to check for LARGE 
image files
  and not create thumbnails for them. Instead it crashes with running out of 
memory error
  at least on some large tif files.

  I have written a webpage. It has

 
 ...
 
 ...
 

  I have a directory of files called GeoRefTest containing

 olympic park tennis & hockey_mosaic_rgb.tif
 Raw Image 85m.JPG
 Raw Image 45m.JPG
 Raw image 95m.JPG

  When I try to upload one of these files, I get a file browser to select a 
file.
  When I try and select the GeoRefTest directory by double clicking on it, the 
browser dies.
  The window just vanishes.

  In the shell window where I ran cromium-browser I see

  david:server$ chromium-browser &
  [3] 15472
  david:server$ Using PPAPI flash.
  [15472:15504:0921/172218:ERROR:nss_util.cc(856)] After loading Root Certs, 
loaded==false: NSS error code: -8018
  [15472:15472:0921/172233:ERROR:browser_main_loop.cc(207)] Gtk: Attempting to 
read the recently used resources file at 
`/home/david/.local/share/recently-used.xbel', but the parser failed: Error 
reading file '/home/david/.local/share/recently-used.xbel': Is a directory.
  [15472:15472:0921/172238:FATAL:memory_linux.cc(42)] Out of memory, size = 
1652117504

  I have disabled recently-used.xbel which explains that message. But why the 
out of memory? Is it trying to read all the image files
  in the directory to make to make thumbnail images? the olympic park tif file 
is BIG 24632, x 16768 pixels and 314M.

  I suspect that this is the problem, as I am ok if I move the tif file
  elsewhere.

  So the file upload browser needs to catch these memory errors and
  gracefully give up on making thumbnails for huge image files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917
  ProcVersionSignature: Ubuntu 3.13.0-63.104~precise1-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic i686
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: i386
  Date: Mon Sep 21 17:13:39 2015
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1821936] Missing required logs.

2019-03-27 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1821936

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions

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

[Desktop-packages] [Bug 1740869] Re: is not responding window is constantly showing when debugging a program

2019-03-27 Thread Andrea Azzarone

This has already been fixed both in Disco and Cosmic. The commit to be
SRUed in Bionic is this one: https://gitlab.gnome.org/GNOME/gnome-
shell/commit/b3045cb964459d050c280a4a4958131cfa24ebfb

@3v1n0 Do you want to take care of it or should I do that?

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

Title:
   is not responding window is constantly showing when
  debugging a program

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Mentioned window about no responding program is showing and stealing
  focus when I try to debug a Java program in Eclipse. When I click on
  Wait, it disappears for a moment and opens again.

  This renders Ubuntu 17.10 with Gnome 3 nearly useless for program
  debugging.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  2 14:22:56 2018
  InstallationDate: Installed on 2017-12-04 (28 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1498082] Re: chromium-browser file upload widget needs better memory checking crashes on file upload selector

2019-03-27 Thread David McKelvie

I can no longer reproduce this error, in Chromium version 73.0.3683.75

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

Title:
  chromium-browser file upload widget needs better memory checking
  crashes on file upload selector

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  
  The file upload browser widget in cromium-browser needs to check for LARGE 
image files
  and not create thumbnails for them. Instead it crashes with running out of 
memory error
  at least on some large tif files.

  I have written a webpage. It has

 
 ...
 
 ...
 

  I have a directory of files called GeoRefTest containing

 olympic park tennis & hockey_mosaic_rgb.tif
 Raw Image 85m.JPG
 Raw Image 45m.JPG
 Raw image 95m.JPG

  When I try to upload one of these files, I get a file browser to select a 
file.
  When I try and select the GeoRefTest directory by double clicking on it, the 
browser dies.
  The window just vanishes.

  In the shell window where I ran cromium-browser I see

  david:server$ chromium-browser &
  [3] 15472
  david:server$ Using PPAPI flash.
  [15472:15504:0921/172218:ERROR:nss_util.cc(856)] After loading Root Certs, 
loaded==false: NSS error code: -8018
  [15472:15472:0921/172233:ERROR:browser_main_loop.cc(207)] Gtk: Attempting to 
read the recently used resources file at 
`/home/david/.local/share/recently-used.xbel', but the parser failed: Error 
reading file '/home/david/.local/share/recently-used.xbel': Is a directory.
  [15472:15472:0921/172238:FATAL:memory_linux.cc(42)] Out of memory, size = 
1652117504

  I have disabled recently-used.xbel which explains that message. But why the 
out of memory? Is it trying to read all the image files
  in the directory to make to make thumbnail images? the olympic park tif file 
is BIG 24632, x 16768 pixels and 314M.

  I suspect that this is the problem, as I am ok if I move the tif file
  elsewhere.

  So the file upload browser needs to catch these memory errors and
  gracefully give up on making thumbnails for huge image files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917
  ProcVersionSignature: Ubuntu 3.13.0-63.104~precise1-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic i686
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: i386
  Date: Mon Sep 21 17:13:39 2015
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

2019-03-27 Thread dreamcat4

> As luck would have it, one user upstream found a solution for NVIDIA 
> documented here:
> 
> https://gitlab.gnome.org/GNOME/mutter/issues/503#note_463305
> 

Hello. Tried this suggestion today (setting "__GL_MaxFramesAllowed=1" in
/etc/environment, and rebooting). It might have decreased my CPU usage,
I am not certain. However what I am sure of is that it does no fix the
60hz framerate issue with multiple monitors, on NVIDIA.

So have now reported the bug over on NVIDIA's forum. With links back to
here:

https://devtalk.nvidia.com/default/topic/1049107/linux/-linux-xorg-
multiple-monitors-limits-the-framerate-of-faster-120-144hz-monitors-to-
60hz/

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

Title:
  (xorg) multiple monitors: limits the framerate of faster 120/144hz
  monitors to 60hz

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  multiple monitors on xorg
  =

  Was recently discussed over on
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

  Another user + myself have the following issue:

  The slowest connected display limits the FPS. The test case we used is
  over at the top of the other bug report ^^

  This we found today happens with either amd vega graphics, or nvidia
  pascal graphics, the vendor doesn't seem to matter. We have both seen
  the same issue (xorg).

  This is on 18.10, and booting into the 'Gnome (xorg)' login option.
  With the FPS being logged by journalctl -f. With only single monitor
  attached. Then it initially goes as high as the primary monitor can
  show. (And glmark2 running in background, to maintain a continued
  load). Which is 120fps for my case. Then as soon as secondary monitor
  is plugged in, which is a 60hz TV. This is being plugged into the HDMI
  port of the same graphics card in real time. Then the FPS logged by
  'journalctl -f' drops, and becomes capped to 60hz, in the output being
  printed by journalctl -f.

  My setup:
  kernel 5.0.0-05-lowlatency #201903032031
  NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
  ubuntu 18.10

  mutter version:

  mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
  mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all 
[installed]

  To confirm where the '.4' at the very end of the ~ubuntu18.10.4
  version number, it seems to be that we have updated now on our client
  machines the be most recent bugfix updates, kindly provided by Daniel.
  Which closed the other bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
  referred to, as being solved for people's single monitor scenarios.

  Thanks again for the other recent bug fixes in this area, it is a nice
  progress. Very helpful! We hope you can also look into this latest
  problem / issue for the multiple monitor scenario.

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

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

[Desktop-packages] [Bug 1821946] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()

2019-03-27 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1821404, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1821946/+attachment/5249854/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1821946/+attachment/5249856/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1821946/+attachment/5249859/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1821946/+attachment/5249860/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1821946/+attachment/5249861/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1821946/+attachment/5249862/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1821946/+attachment/5249863/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1821404

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gedit crashed with SIGSEGV in gedit_metadata_manager_set()

Status in gedit package in Ubuntu:
  New

Bug description:
  No significant information about the bug

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 27 16:46:53 2019
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2019-02-26 (28 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  ProcCmdline: /usr/bin/gedit --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f41e7e1367a :   
mov(%rax),%esi
   PC (0x7f41e7e1367a) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   gedit_metadata_manager_set () from 
/usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so
   gedit_document_set_metadata () from 
/usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so
   ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_text_view_set_buffer () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1395794] Re: Chrominum Locks Up Ubuntu 14.04

2019-03-27 Thread Lonnie Lee Best

Sorry, just now seeing this. I just want to confirm that I don't have
the issue anymore.

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

Title:
  Chrominum Locks Up Ubuntu 14.04

Status in Pepperflashplugin Nonfree:
  Invalid
Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Twice today, I had to shutdown my Ubuntu 14.04 improperly due to
  system lock-up.

  Each time the lockup happened, these are the exact steps I did:
  1) Launch Chromium browser
  2) Go to https://login.microsoftonline.com
  3) type in an email address
  4) Press tab (attempting to move cursor to password field)

  At this point the entire system locked up.

  The only recent package I recall installing (related to Chromium) was
  the pepperflashplugin-nonfree. So, it may be a bug in that plugin that
  is the culprit. I'm not sure, but I hope my report helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 38.0.2125.111-0ubuntu0.14.04.1.1061
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 24 10:48:49 2014
  InstallationDate: Installed on 2014-11-23 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-11-23T00:10:36.963259

To manage notifications about this bug go to:
https://bugs.launchpad.net/pepperflashplugin-nonfree/+bug/1395794/+subscriptions

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

[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported

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

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions

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

[Desktop-packages] [Bug 1818790] Re: [regression] Desktop zoom is missing the mouse pointer

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/365180

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

Title:
  [regression] Desktop zoom is missing the mouse pointer

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Disco:
  In Progress

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020
  Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454

  ---

  Desktop zoom is missing the mouse pointer.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Wed Mar  6 15:12:04 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-12-04 (92 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 
(20181203)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/1818790/+subscriptions

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

[Desktop-packages] [Bug 1395794] Re: Chrominum Locks Up Ubuntu 14.04

No reply to comment #4 so closing as bug task did not expire

** Changed in: pepperflashplugin-nonfree
   Status: Incomplete => Invalid

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

Title:
  Chrominum Locks Up Ubuntu 14.04

Status in Pepperflashplugin Nonfree:
  Invalid
Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Twice today, I had to shutdown my Ubuntu 14.04 improperly due to
  system lock-up.

  Each time the lockup happened, these are the exact steps I did:
  1) Launch Chromium browser
  2) Go to https://login.microsoftonline.com
  3) type in an email address
  4) Press tab (attempting to move cursor to password field)

  At this point the entire system locked up.

  The only recent package I recall installing (related to Chromium) was
  the pepperflashplugin-nonfree. So, it may be a bug in that plugin that
  is the culprit. I'm not sure, but I hope my report helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 38.0.2125.111-0ubuntu0.14.04.1.1061
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 24 10:48:49 2014
  InstallationDate: Installed on 2014-11-23 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-11-23T00:10:36.963259

To manage notifications about this bug go to:
https://bugs.launchpad.net/pepperflashplugin-nonfree/+bug/1395794/+subscriptions

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

Upstream issue showing fixed 2016-09-05
No comments here for almost two years
No longer an issue here with emacs25 in Ubuntu 18.04 so closing as fixed


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

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Fix Released
Status in emacs24 package in Debian:
  Fix Released

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call

2019-03-27 Thread Treviño

This has been fixed for disco in gnome-shell 3.32.0-1ubuntu1

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

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

Title:
  gnome-shell crashed with SIGSEGV in st_widget_get_theme_node →
  ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-shell source package in Disco:
  Fix Released

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

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.0-3ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1821895] Re: Gnome Shell crashes after resume on Disco

2019-03-27 Thread Joseph Borg

Ah apologies, should have mentioned that from the outset - yes I'm on
Wayland.

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

Title:
  Gnome Shell crashes after resume on Disco

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  System - XPS13 9370

  To the best of my knowledge, this was working fine last week.  I
  updated the system via Apt, the system fails to resume after being
  suspended (via lid close).  There is a blank screen for a few seconds,
  followed by the cursor appearing (still blank background) and then
  gnome crashes and comes back to the login screen.

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

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

[Desktop-packages] [Bug 1821933] [NEW] Touch input is misaligned with two screens

Public bug reported:

Using touch input with one screen seems fine.
However, when connecting a second screen the touch event happens at the wrong 
coordinates.

Steps to reproduce
1. Starting with a single screen touch and hold on the background and drag.  
The rubber band selector shows up with the moving corner at your finger.
2. Connect a second screen
3. Do the same touch and drag as in step 1 and notice that the moving corner is 
offset to the right and slightly below where the touch is happening.

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


** Tags: rls-dd-incoming

** Tags added: rls-dd-incoming

** 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/1821933

Title:
  Touch input is misaligned with two screens

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using touch input with one screen seems fine.
  However, when connecting a second screen the touch event happens at the wrong 
coordinates.

  Steps to reproduce
  1. Starting with a single screen touch and hold on the background and drag.  
The rubber band selector shows up with the moving corner at your finger.
  2. Connect a second screen
  3. Do the same touch and drag as in step 1 and notice that the moving corner 
is offset to the right and slightly below where the touch is happening.

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

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

[Desktop-packages] [Bug 1821895] Re: Gnome Shell crashes after resume on Disco

** Tags added: rls-dd-incoming

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

Title:
  Gnome Shell crashes after resume on Disco

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  System - XPS13 9370

  To the best of my knowledge, this was working fine last week.  I
  updated the system via Apt, the system fails to resume after being
  suspended (via lid close).  There is a blank screen for a few seconds,
  followed by the cursor appearing (still blank background) and then
  gnome crashes and comes back to the login screen.

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

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

[Desktop-packages] [Bug 1821936] [NEW] ALC274 unsupported

Public bug reported:

I find this to be an issue with current LTS 18.04's latest 4.19 kernel.
I tested this on mainline 4.20 and 5.0 kernels as well.

No audio because ALC274 not properly loaded for use, so no audio output.
A related card had a similar bug, which was fixed, and may be of use in
resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485


# cat /proc/asound/card0/codec* | grep Codec
Codec: Realtek ALC274
Codec: Intel Kabylake HDMI

# cat /proc/asound/card0/pcm0c/info
card: 0
device: 0
subdevice: 0
stream: CAPTURE
id: ALC274 Analog
name: ALC274 Analog
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 0

aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

d# hwinfo --sound
21: PCI 1f.3: 0403 Audio device 
  [Created at pci.378]
  Unique ID: nS1_.WnojYJLVCm0
  SysFS ID: /devices/pci:00/:00:1f.3
  SysFS BusID: :00:1f.3
  Hardware Class: sound
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0xa348 
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x31d0 
  Revision: 0x10
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
  Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
  IRQ: 145 (663 events)
  Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
  Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

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


** Tags: alc274 audio driver kernel

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

Title:
  ALC274 unsupported

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I find this to be an issue with current LTS 18.04's latest 4.19
  kernel.  I tested this on mainline 4.20 and 5.0 kernels as well.

  No audio because ALC274 not properly loaded for use, so no audio
  output.  A related card had a similar bug, which was fixed, and may be
  of use in resolving this one:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485

  
  # cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC274
  Codec: Intel Kabylake HDMI

  # cat /proc/asound/card0/pcm0c/info
  card: 0
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC274 Analog
  name: ALC274 Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 0

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  d# hwinfo --sound
  21: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.WnojYJLVCm0
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa348 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x31d0 
Revision: 0x10
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable)
Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable)
IRQ: 145 (663 events)
Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this

[Desktop-packages] [Bug 1821895] Re: Gnome Shell crashes after resume on Disco

Can you confirm you're seeing this in the Wayland session?

I can't (yet) reproduce under the X session.

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

Title:
  Gnome Shell crashes after resume on Disco

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  System - XPS13 9370

  To the best of my knowledge, this was working fine last week.  I
  updated the system via Apt, the system fails to resume after being
  suspended (via lid close).  There is a blank screen for a few seconds,
  followed by the cursor appearing (still blank background) and then
  gnome crashes and comes back to the login screen.

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

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

[Desktop-packages] [Bug 1337660] Re: Cannot input cedilla (ç) on Chromium only, dvorak-br only

2019-03-27 Thread Ekevoo

(it sits between Z and left shift)

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

Title:
  Cannot input cedilla (ç) on Chromium only, dvorak-br only

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  1. Set input source to these options:

  1.a. Portuguese (Brazil, Dvorak)

  1.b. English (Dvorak, international with dead keys)

  1.c. Portuguese (Brazil)

  2. Load any application (say, gnome-terminal)

  3. Type a cedilla using all three input methods. All will work.

  3.a. Right of LShift. http://f.ekevoo.com/2014/cedilla-dvorak-br.png

  3.b. AltGr+Comma. http://f.ekevoo.com/2014/cedilla-dvorak.png

  3.c. Right of L. [3] http://f.ekevoo.com/2014/cedilla-abnt2.png

  4. Load up Chromium (or Chrome).

  5. Type a cedilla using all three input methods.

  6. Method A won't work. The keystroke is ignored. There is absolutely
  no way to create a cedilla.

  7. Methods B and C do work.

  ---

  Expected behavior: the keystroke should not be ignored.

  ---

  The best workaround I have is switching input methods. This is
  phenomenally disruptive (4 awkward keystrokes for a single ordinary
  character). I'm aware I can use diacritics in similar fashion as dead
  keys ("c̩"), but this is not the same as "ç", rendering incorrectly
  for most people I send messages to.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  3 22:32:25 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-30 (64 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command 
= b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = 
b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1337660] Re: Cannot input cedilla (ç) on Chromium only, dvorak-br only

2019-03-27 Thread Ekevoo

Alas, I can't check. I moved away from Brazil and I no longer have
access with a keyboard with the relevant key.

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

Title:
  Cannot input cedilla (ç) on Chromium only, dvorak-br only

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  1. Set input source to these options:

  1.a. Portuguese (Brazil, Dvorak)

  1.b. English (Dvorak, international with dead keys)

  1.c. Portuguese (Brazil)

  2. Load any application (say, gnome-terminal)

  3. Type a cedilla using all three input methods. All will work.

  3.a. Right of LShift. http://f.ekevoo.com/2014/cedilla-dvorak-br.png

  3.b. AltGr+Comma. http://f.ekevoo.com/2014/cedilla-dvorak.png

  3.c. Right of L. [3] http://f.ekevoo.com/2014/cedilla-abnt2.png

  4. Load up Chromium (or Chrome).

  5. Type a cedilla using all three input methods.

  6. Method A won't work. The keystroke is ignored. There is absolutely
  no way to create a cedilla.

  7. Methods B and C do work.

  ---

  Expected behavior: the keystroke should not be ignored.

  ---

  The best workaround I have is switching input methods. This is
  phenomenally disruptive (4 awkward keystrokes for a single ordinary
  character). I'm aware I can use diacritics in similar fashion as dead
  keys ("c̩"), but this is not the same as "ç", rendering incorrectly
  for most people I send messages to.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  3 22:32:25 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-30 (64 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command 
= b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = 
b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1821928] [NEW] package libgjs0g 1.52.1-1ubuntu1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su config

2019-03-27 Thread Claudio Akugna

Public bug reported:

No sé cual es el error...

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgjs0g 1.52.1-1ubuntu1
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
AptOrdering:
 firefox:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Mar 27 10:49:16 2019
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-10-15 (528 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6ubuntu0.1
SourcePackage: gjs
Title: package libgjs0g 1.52.1-1ubuntu1 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
UpgradeStatus: Upgraded to bionic on 2018-09-19 (188 days ago)

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


** Tags: amd64 apport-package bionic third-party-packages

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

Title:
  package libgjs0g 1.52.1-1ubuntu1 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in gjs package in Ubuntu:
  New

Bug description:
  No sé cual es el error...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgjs0g 1.52.1-1ubuntu1
  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
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Mar 27 10:49:16 2019
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-10-15 (528 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6ubuntu0.1
  SourcePackage: gjs
  Title: package libgjs0g 1.52.1-1ubuntu1 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: Upgraded to bionic on 2018-09-19 (188 days ago)

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

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

[Desktop-packages] [Bug 1821019] Re: gnome-terminal does not gain focus upon launch via clicking icon

This seems to be a different bug to the "windows open at the bottom of
the stack one".  Tested by opening a Firefox window and then opening
terminal via the dock.  The terminal window opened on the top, but
without focus.

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

Title:
  gnome-terminal does not gain focus upon launch via clicking icon

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.04, 64 bit machine, nvidia graphics drivers

  Upon first and subsequent launches of gnome-terminal via clicking the
  icon, the window shows but does not immediately gain focus to start
  typing in commands.

  Using Ctrl+alt+T launches the terminal the way I expect, with
  immediate focus to start typing commands.

  I expect it to immediately gain focus to type commands upon launch
  each and every time using both methods.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 10:40:18 2019
  InstallationDate: Installed on 2018-03-02 (382 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821019] Re: gnome-terminal does not gain focus upon launch via clicking icon

** Tags added: rls-dd-incoming

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

Title:
  gnome-terminal does not gain focus upon launch via clicking icon

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.04, 64 bit machine, nvidia graphics drivers

  Upon first and subsequent launches of gnome-terminal via clicking the
  icon, the window shows but does not immediately gain focus to start
  typing in commands.

  Using Ctrl+alt+T launches the terminal the way I expect, with
  immediate focus to start typing commands.

  I expect it to immediately gain focus to type commands upon launch
  each and every time using both methods.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 10:40:18 2019
  InstallationDate: Installed on 2018-03-02 (382 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821019] Re: gnome-terminal does not gain focus upon launch

2019-03-27 Thread Brian Curtis

Updated description and title to add M_M comments as I can confirm them
as well.

** Description changed:

  Ubuntu 19.04, 64 bit machine, nvidia graphics drivers
  
- Upon first and subsequent launches of gnome-terminal the window shows
- but does not immediately gain focus to start typing in commands.
+ Upon first and subsequent launches of gnome-terminal via clicking the
+ icon, the window shows but does not immediately gain focus to start
+ typing in commands.
+ 
+ Using Ctrl+alt+T launches the terminal the way I expect, with immediate
+ focus to start typing commands.
  
  I expect it to immediately gain focus to type commands upon launch each
- and every time.
+ and every time using both methods.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 10:40:18 2019
  InstallationDate: Installed on 2018-03-02 (382 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- gnome-terminal does not gain focus upon launch
+ gnome-terminal does not gain focus upon launch via clicking icon

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

Title:
  gnome-terminal does not gain focus upon launch via clicking icon

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.04, 64 bit machine, nvidia graphics drivers

  Upon first and subsequent launches of gnome-terminal via clicking the
  icon, the window shows but does not immediately gain focus to start
  typing in commands.

  Using Ctrl+alt+T launches the terminal the way I expect, with
  immediate focus to start typing commands.

  I expect it to immediately gain focus to type commands upon launch
  each and every time using both methods.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 10:40:18 2019
  InstallationDate: Installed on 2018-03-02 (382 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-03-27 Thread Seth Forshee

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date:

[Desktop-packages] [Bug 1821921] [NEW] Nautilus upgrade 18.10 to 19.04

2019-03-27 Thread tclovis

Public bug reported:

term1# apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 gnome-shell-extension-desktop-icons : Depends: nautilus (>= 3.30.4) but it is 
not installed
 nautilus-share : Depends: nautilus (>= 2.10) but it is not installed
 ubuntu-desktop : Depends: nautilus but it is not installed
 ubuntu-desktop-minimal : Depends: nautilus but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
term1# apt --fix-broken install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  gir1.2-mutter-3 libdns-export1102 libgmime-3.0-0 libgsoap-2.8.60 
libisc-export169 libkf5dbusaddons-bin libkf5iconthemes-bin libllvm7 libnfs11 
liborcus-0.13-0
  libperl5.26 libprotobuf10 libvoikko1 perl-modules-5.26 python-tdb 
sonnet-plugins
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  nautilus
Suggested packages:
  gnome-sushi nautilus-extension-brasero
The following NEW packages will be installed:
  nautilus
0 upgraded, 1 newly installed, 0 to remove and 657 not upgraded.
78 not fully installed or removed.
Need to get 0 B/599 kB of archives.
After this operation, 2010 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: warning: files list file for package 'nautilus-data' missing; assuming 
package has no files currently installed
dpkg: warning: files list file for package 'nautilus-dropbox' missing; assuming 
package has no files currently installed
dpkg: warning: files list file for package 'nautilus-extension-gnome-terminal' 
missing; assuming package has no files currently installed
(Reading database ... 213687 files and directories currently installed.)
Preparing to unpack .../nautilus_1%3a3.32.0-0ubuntu1_amd64.deb ...
Unpacking nautilus (1:3.32.0-0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/nautilus_1%3a3.32.0-0ubuntu1_amd64.deb (--unpack):
 trying to overwrite 
'/usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libtotem-properties-page.so',
 which is also in package totem 3.26.2-1ubuntu3
Errors were encountered while processing:
 /var/cache/apt/archives/nautilus_1%3a3.32.0-0ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 27 10:02:55 2019
InstallationDate: Installed on 2018-10-19 (159 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug disco

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

Title:
  Nautilus upgrade 18.10 to 19.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  term1# apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   gnome-shell-extension-desktop-icons : Depends: nautilus (>= 3.30.4) but it 
is not installed
   nautilus-share : Depends: nautilus (>= 2.10) but it is not installed
   ubuntu-desktop : Depends: nautilus but it is not installed
   ubuntu-desktop-minimal : Depends: nautilus but it is not installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  term1# apt --fix-broken install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
gir1.2-mutter-3 libdns-export1102 libgmime-3.0-0 libgsoap-2.8.60 
libisc-export169 libkf5dbusaddons-bin libkf5iconthemes-bin libllvm7 libnfs11 
liborcus-0.13-0
libperl5.26 libprotobuf10 libvoikko1 perl-modules-5.26 python-tdb 
sonnet-plugins
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
nautilus
  Suggested packages:
gnome-sushi nautilus-extension-brasero
  The following NEW packages will be installed:
nautilus
  0 upgraded, 1 newly installed, 0 to remove and 657 not upgraded.
  78 not fully installed or removed.
  Need to get 0 B/599 kB of archives.

[Desktop-packages] [Bug 1264739] Re: YouTube black box with audio, needs refreshing to play

No comments here for over 5 years
Presumably fixed a long time ago?

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  YouTube black box with audio, needs refreshing to play

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Frequently and for some time I've had to refresh the page when loading a 
youtube video. 
  What tends to happen is I get a black box, with audio, but no video. 
  I often need to refresh 5-10 times to get the video to actually load and 
play. 
  It always does load eventually, but more often than not it requires many 
refreshes.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 31.0.1650.63-0ubuntu0.13.10.1~20131204.1
  Uname: Linux 3.12.0-031200-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sat Dec 28 20:42:16 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-06-29 (546 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to saucy on 2013-07-12 (169 days ago)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

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

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

[Desktop-packages] [Bug 1261733] Re: YouTube Videos does not work on Chromium BUT same video works on Firefox on the same system and machine

No issues here using Chromium 73 and Ubuntu 18.04
Presumably with no comments here for almost 5 years this report can now be 
closed?

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  YouTube Videos does not work on Chromium BUT same video works on
  Firefox on the same system and machine

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  More details here: http://ubuntuforums.org/showthread.php?t=2194128

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 31.0.1650.63-0ubuntu0.12.04.1~20131204.1
  ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52
  Uname: Linux 3.2.0-57-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Dec 17 16:29:34 2013
  Desktop-Session:
   DESKTOP_SESSION = xubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share
  DetectedPlugins: (no entry found in the Preferences file)
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 1332499] Re: Chromium's window-borders are not showing correctly and the browser is not 100% usable

Upstream bug report was closed "WontFix"in May 2015
Issue not reproducible here using Chromium 73 and Ubuntu 18.04
Presumably with no activity here for nearly 5 years this report can now be 
closed?

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Chromium's window-borders are not showing correctly and the browser is
  not 100% usable

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu GNOME 14.04 LTS 64-bit and I'm running Firefox 30 and Chromium
  version:

  Version 34.0.1847.116 Ubuntu 14.04 aura (260972)

  Chromium is a MESS. I can't use it probably ... I always need two open
  browsers and it is a mess on Facebook and Gmail as well and whenever I
  maximize the window, some of its border specially the upper one just
  disappear.

  On Xubuntu 12.04 LTS, I'm having hard time with Chromium as well -
  https://code.google.com/p/chromium/issues/detail?id=379544

  and: https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1325498

  Not yet sure if these are related.

  As per Ubuntu GNOME Mailing List, I'm not the only one who is affected
  with this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jun 20 15:16:19 2014
  Desktop-Session:
   DESKTOP_SESSION = default
   XDG_CONFIG_DIRS = /etc/xdg/xdg-default:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/default:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda9  
ext4  9.8G  5.0G  4.3G  54% /\nnone   tmpfs 4.0K 0  4.0K   
0% /sys/fs/cgroup\nudev   devtmpfs  3.9G  4.0K  3.9G   1% /dev\ntmpfs   
   tmpfs 793M  1.1M  792M   1% /run\nnone   tmpfs 5.0M 
0  5.0M   0% /run/lock\nnone   tmpfs 3.9G   16M  3.9G   1% 
/run/shm\nnone   tmpfs 100M   28K  100M   1% /run/user\n/dev/sda10  
   ext4   40G  2.4G   35G   7% /home\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda9640K  
255K  386K   40% /\nnone 992K 2  992K1% 
/sys/fs/cgroup\nudev 989K   547  988K1% /dev\ntmpfs
992K   571  991K1% /run\nnone 992K 3  992K1% 
/run/lock\nnone 992K34  992K1% /run/shm\nnone 
992K22  992K1% /run/user\n/dev/sda10   2.6M   13K  2.5M1% 
/home\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-11 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 
(20140410)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1498082] Re: cromium-browser file upload widget needs better memory checkingcrashes on file upload selector

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

Do you still see a problem related to the one that you reported using
currently supported versions of Ubuntu and Chromium? 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: chromium-browser (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- cromium-browser file upload widget needs better memory checkingcrashes on 
file upload selector
+ chromium-browser file upload widget needs better memory checking crashes on 
file upload selector

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

Title:
  chromium-browser file upload widget needs better memory checking
  crashes on file upload selector

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  
  The file upload browser widget in cromium-browser needs to check for LARGE 
image files
  and not create thumbnails for them. Instead it crashes with running out of 
memory error
  at least on some large tif files.

  I have written a webpage. It has

 
 ...
 
 ...
 

  I have a directory of files called GeoRefTest containing

 olympic park tennis & hockey_mosaic_rgb.tif
 Raw Image 85m.JPG
 Raw Image 45m.JPG
 Raw image 95m.JPG

  When I try to upload one of these files, I get a file browser to select a 
file.
  When I try and select the GeoRefTest directory by double clicking on it, the 
browser dies.
  The window just vanishes.

  In the shell window where I ran cromium-browser I see

  david:server$ chromium-browser &
  [3] 15472
  david:server$ Using PPAPI flash.
  [15472:15504:0921/172218:ERROR:nss_util.cc(856)] After loading Root Certs, 
loaded==false: NSS error code: -8018
  [15472:15472:0921/172233:ERROR:browser_main_loop.cc(207)] Gtk: Attempting to 
read the recently used resources file at 
`/home/david/.local/share/recently-used.xbel', but the parser failed: Error 
reading file '/home/david/.local/share/recently-used.xbel': Is a directory.
  [15472:15472:0921/172238:FATAL:memory_linux.cc(42)] Out of memory, size = 
1652117504

  I have disabled recently-used.xbel which explains that message. But why the 
out of memory? Is it trying to read all the image files
  in the directory to make to make thumbnail images? the olympic park tif file 
is BIG 24632, x 16768 pixels and 314M.

  I suspect that this is the problem, as I am ok if I move the tif file
  elsewhere.

  So the file upload browser needs to catch these memory errors and
  gracefully give up on making thumbnails for huge image files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917
  ProcVersionSignature: Ubuntu 3.13.0-63.104~precise1-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic i686
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: i386
  Date: Mon Sep 21 17:13:39 2015
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1337660] Re: Cannot input cedilla (ç) on Chromium only, dvorak-br only

@ekevoo, further to your comment #3, this was fixed in Chromium a long
time ago?

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Cannot input cedilla (ç) on Chromium only, dvorak-br only

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  1. Set input source to these options:

  1.a. Portuguese (Brazil, Dvorak)

  1.b. English (Dvorak, international with dead keys)

  1.c. Portuguese (Brazil)

  2. Load any application (say, gnome-terminal)

  3. Type a cedilla using all three input methods. All will work.

  3.a. Right of LShift. http://f.ekevoo.com/2014/cedilla-dvorak-br.png

  3.b. AltGr+Comma. http://f.ekevoo.com/2014/cedilla-dvorak.png

  3.c. Right of L. [3] http://f.ekevoo.com/2014/cedilla-abnt2.png

  4. Load up Chromium (or Chrome).

  5. Type a cedilla using all three input methods.

  6. Method A won't work. The keystroke is ignored. There is absolutely
  no way to create a cedilla.

  7. Methods B and C do work.

  ---

  Expected behavior: the keystroke should not be ignored.

  ---

  The best workaround I have is switching input methods. This is
  phenomenally disruptive (4 awkward keystrokes for a single ordinary
  character). I'm aware I can use diacritics in similar fashion as dead
  keys ("c̩"), but this is not the same as "ç", rendering incorrectly
  for most people I send messages to.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  3 22:32:25 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-30 (64 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/opt/google/chrome/google-chrome\n'/desktop/gnome/url-handlers/https/command 
= b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = 
b'/opt/google/chrome/google-chrome 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "ERROR Atomic update failure on pipe A"

2019-03-27 Thread Avi Eis

Having same issue, freeze without any changes on screen, on Ubuntu
18.10, Dell Precision 5530.

It only started recently after I encrypted my home directory and swap
but I don't know if that's related.

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

Title:
  Frequent system freezing with i915 error "*ERROR* Atomic update
  failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  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
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  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/linux/+bug/1813423/+subscriptions

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

[Desktop-packages] [Bug 1353940] Re: webgl no longer works

No activity here for nearly 5 years
Example given by reporter works for me using Chromium 73 and Ubuntu 18.04
Examples at https://webglsamples.org/ all work so closing as fixed

Please open a new bug report if an issue is still seen using currently
supported versions of Ubuntu and Chromium.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  webgl no longer works

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Since update to chromium 36, webgl sites no longer work on my ubuntu 12.04 
although it worked well on chromium 35 and older...
  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04
  chromium-browser:
Installé : 36.0.1985.125-0ubuntu1.12.04.0~pkg897
Candidat : 36.0.1985.125-0ubuntu1.12.04.0~pkg897

  
  Visit any webgl site and see it doesn't work, example URL :
  http://www.zygotebody.com/

  Here my chromium about:gpu saying WebGL now unavailable...

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash 3D: Unavailable. Hardware acceleration unavailable
  Flash Stage3D: Unavailable. Hardware acceleration unavailable
  Flash Stage3D Baseline profile: Unavailable. Hardware acceleration unavailable
  Compositing: Software only and threaded. Hardware acceleration unavailable.
  Rasterization: Software only, hardware acceleration unavailable
  Video Decode: Software only, hardware acceleration unavailable
  Video Encode: Software only, hardware acceleration unavailable
  WebGL: Unavailable. Hardware acceleration unavailable
  Driver Bug Workarounds
  clear_uniforms_before_first_program_use
  disable_post_sub_buffers_for_onscreen_surfaces
  init_gl_position_in_vertex_shader
  init_vertex_attributes
  use_current_program_after_successful_link
  Problems Detected
  GPU process was unable to boot: GPU access is disabled in chrome://settings.
  Disabled Features: all
  Accelerated 2d canvas is unstable in Linux at the moment
  Disabled Features: accelerated_2d_canvas
  Stage3D is not supported on Linux: 129848
  Disabled Features: flash_stage3d
  Accelerated video decode is unavailable on Mac and Linux: 137247, 133828
  Disabled Features: accelerated_video_decode
  NVIDIA linux drivers are unstable when using multiple Open GL contexts and 
with low memory: 145600
  Disabled Features: flash_3d, accelerated_video_decode, flash_stage3d
  GPU rasterization is whitelisted on N4, N5, N7 and Moto X: 362779
  Disabled Features: gpu_rasterization
  Always call glUseProgram after a successful link to avoid a driver bug: 349137
  Applied Workarounds: use_current_program_after_successful_link
  Program link fails in NVIDIA Linux if gl_Position is not set: 286468
  Applied Workarounds: init_gl_position_in_vertex_shader
  Clear uniforms before first program use on all platforms: 124764, 349137
  Applied Workarounds: clear_uniforms_before_first_program_use
  Linux NVIDIA drivers don't have the correct defaults for vertex attributes: 
351528
  Applied Workarounds: init_vertex_attributes
  Disable partial swaps on linux drivers: 339493
  Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
  Version Information
  Data exported 7/8/2014 12:19:23
  Chrome versionChrome/36.0.1985.125
  Operating system  Linux 3.5.0-18-generic
  Software rendering list version   8.7
  Driver bug list version   6.1
  ANGLE commit id   invalid-hash
  2D graphics backend   Skia
  Command Line Args --flag-switches-begin --flag-switches-end
  Driver Information
  Initialization time   0
  Sandboxed false
  GPU0  VENDOR = 0x10de, DEVICE= 0x0de1
  Optimus   false
  AMD switchablefalse
  Driver vendor NVIDIA
  Driver version331.38
  Driver date   
  Pixel shader version  
  Vertex shader version 
  Machine model name
  Machine model version 
  GL_VENDOR NVIDIA Corporation
  GL_RENDERER   GeForce GT 430/PCIe/SSE2
  GL_VERSION4.4.0 NVIDIA 331.38
  GL_EXTENSIONS 
  Window system binding vendor  
  Window system binding version 
  Window system binding extensions  
  Direct rendering  Yes
  Reset notification strategy   0x
  Log Messages
  GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.

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

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

[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

2019-03-27 Thread javen

This bug affects me, wait for updating

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

Title:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion
  'G_UDEV_IS_DEVICE (device)' failed

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have no idea about the package to blame: gvfs/udev/kernel ?

  This is now logged:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE 
(device)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb 27 14:21:10 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1314885] Re: Chinese tags are not displayed correctly

Upstream bug report was marked as a duplicate of #272006
which was closed as being fixed in September 2013
No activity here for nearly 5 years so closing as fixed

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Chinese  tags are not displayed correctly

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium display garble characters in the title bar while its able to
  render the correct characters in web pages.

  OS: Ubuntu 14.04

  Workaround is by removing /etc/fonts/conf.d/65-droid-sans-fonts.conf.

  Reference bug report in chromium:

  https://code.google.com/p/chromium/issues/detail?id=316723

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

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

[Desktop-packages] [Bug 1315598] Re: Chromium very slow since upgrade to 14.04 LTS

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

Does anyone still see a problem related to the one that was reported
using currently supported versions of Ubuntu and Chromium? 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: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Chromium very slow since upgrade to 14.04 LTS

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 14.04 LTS Chromium became very slow. Lots of black 
surfaces, etc are shown.
  When run on the command line: "chromium-browser --disable-gpu" the effect 
disappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  3 14:26:00 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-04-20 (12 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

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

addional clarification .. if sda6 (recovery booted or chrooted)
installed grub then sda6 boots with some brief flashing normally. if
sda7 or sda1 (recovery booted or chrooted or a normal boot for sda1)
installed grub then sda6 would boot and lighjtdm would briefly flash
onto screen and the disappear (blank screen) showing just aflashing
underline cursor.

so xorg video drivers appear  NOT to be involved. except maybe as kernel
i915 modules missing I have not checked

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

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

-- 
Mailing list:

[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

2019-03-27 Thread Gianfranco Costamagna

@Brian

Now the disco fix is in both cosmic and bionic queues.
please accept them :)
I checked if wl-asneeded was removed from rules, if the patch was added, and 
also the upgrade path for versioning was correct for bionic->cosmic->disco

please double check! I also fixed the description

** Changed in: libunistring (Ubuntu Cosmic)
 Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco)

** Changed in: libunistring (Ubuntu)
 Assignee: Jeremy Bicha (jbicha) => (unassigned)

** Changed in: libidn (Ubuntu Cosmic)
 Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco)

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  In Progress
Status in libunistring source package in Bionic:
  Fix Committed
Status in libidn source package in Cosmic:
  In Progress
Status in libunistring source package in Cosmic:
  In Progress
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-03-27 Thread fossfreedom

Sorry - I havent had the time yet to see what happens with this patch
(revert_volume_calc) on Disco - but for bionic, this revert patch
resolves the animation issues for bionic

Note - I couldn't get a simple git revert of the commit to apply  - too
many changes in this file I guess with the other cherry-picked commits.

** Patch added: "revert commit 527f6ef8357f614793035a999ec4409ef02470e2"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1811900/+attachment/5249772/+files/revert_volume_calc.patch

-- 
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 gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in mutter source package in Bionic:
  Fix Committed

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/gnome-shell/+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 1821019] Re: gnome-terminal does not gain focus upon launch

2019-03-27 Thread M_M

It also happens to me that the terminal window does not get the focus
when I launch gnome-terminal by clicking on the terminal icon, but if I
use the key combination [Ctrl]+[Alt]+T , then the terminal window takes
focus and the terminal cursor blinks.

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

Title:
  gnome-terminal does not gain focus upon launch

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.04, 64 bit machine, nvidia graphics drivers

  Upon first and subsequent launches of gnome-terminal the window shows
  but does not immediately gain focus to start typing in commands.

  I expect it to immediately gain focus to type commands upon launch
  each and every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 10:40:18 2019
  InstallationDate: Installed on 2018-03-02 (382 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

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

this effected only the more recent installs

you have miss understood the details in the initial report .. the system
would boot normally as long as the grub used (installed) was from the
install partition (sda6 or sda7) .. if another partition was used to
install grub the lightdm would appear briefly and then crash or vanish
to a underline flashing cursor

the video system did work it would flash once on start-up but come back
in about 5 seconds or less is the correct (ie this partition installed
the grub version used)

the main sda1 partition always worked .. only difference was the kernel image 
used .. 
I have not yet checked to see if the sda1 5.0.0.7 image fails currently but it 
worked fine before.

the installation of the newer video drivers did not fix this issue!!! It
remained as long as a 5.0.0.7 kernel was selected to boot sda6 or sda7

sda1 was not effected.

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2

[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

2019-03-27 Thread Gianfranco Costamagna

libunistring backport patch to cosmic from Disco:
diff -Nru libunistring-0.9.10/debian/changelog 
libunistring-0.9.10/debian/changelog
--- libunistring-0.9.10/debian/changelog2018-07-23 16:46:28.0 
+0200
+++ libunistring-0.9.10/debian/changelog2019-03-27 12:21:30.0 
+0100
@@ -1,3 +1,10 @@
+libunistring (0.9.10-1ubuntu1.18.10.1) cosmic; urgency=medium
+
+  * Cherry-pick pthread fix from upstream and disco release.
+(LP: #1813587)
+
+ -- Gianfranco Costamagna   Wed, 27 Mar 2019 
12:21:30 +0100
+
 libunistring (0.9.10-1ubuntu1) cosmic; urgency=medium

   * Do not set as-needed, to work-around a testsuite failure
diff -Nru 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
--- 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
   1970-01-01 01:00:00.0 +0100
+++ 
libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch
   2019-03-27 12:21:14.0 +0100
@@ -0,0 +1,15 @@
+Description: Fix link failure with upstream gnulib patch
+Origin: 
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cca32830b57e91f837c01d15b8732f23ff97fc36
+Last-Update: 2019-03-20
+
+--- libunistring-0.9.10.orig/tests/glthread/thread.h
 libunistring-0.9.10/tests/glthread/thread.h
+@@ -133,8 +133,6 @@ extern int glthread_in_use (void);
+call to foo(...) in the same function.  To avoid this, we test the
+address of a function in libpthread that we don't use.  */
+ 
+-#  pragma weak pthread_create
+-
+ #  ifndef pthread_sigmask /* Do not declare rpl_pthread_sigmask weak.  */
+ #   pragma weak pthread_sigmask
+ #  endif
diff -Nru libunistring-0.9.10/debian/patches/series 
libunistring-0.9.10/debian/patches/series
--- libunistring-0.9.10/debian/patches/series   2018-07-23 16:46:28.0 
+0200
+++ libunistring-0.9.10/debian/patches/series   2019-03-27 12:21:14.0 
+0100
@@ -1,2 +1,3 @@
 0100-float-endian-detection.patch
 0700-multiarch-libc.patch
+cca32830b57e91f837c01d15b8732f23ff97fc36.patch

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  In Progress
Status in libunistring source package in Bionic:
  Fix Committed
Status in libidn source package in Cosmic:
  In Progress
Status in libunistring source package in Cosmic:
  In Progress
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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

[Desktop-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

2019-03-27 Thread Gianfranco Costamagna

Ok Brian, so lets backport the fix from 19.04 and fix also 18.10

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

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

** Changed in: libunistring (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: libidn (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: libidn (Ubuntu Bionic)
   Status: Incomplete => In Progress

** Description changed:

  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.
  
  Test Case
  -
  Does libunistring build successfully?
  
  Regression Potential
  
- We are simply backporting the workaround we applied in Ubuntu 18.10.
+ We are simply backporting the workaround we applied in Ubuntu 19.04.
  
  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
  
  libunistring ftbfs.
  
  FAIL: test-thread_create
  
  
  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  In Progress
Status in libunistring source package in Bionic:
  Fix Committed
Status in libidn source package in Cosmic:
  In Progress
Status in libunistring source package in Cosmic:
  In Progress
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

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

** Summary changed:

- lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.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.16-1

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

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

[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-27 Thread El jinete sin cabeza

@Till

I do not see it crashing:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432#note_475636

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

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

[Desktop-packages] [Bug 1821904] [NEW] Gnome Shell always started muted on Disco

2019-03-27 Thread Joseph Borg

Public bug reported:

On Disco, Gnome Shell always starts muted.

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

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

Title:
  Gnome Shell always started muted on Disco

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On Disco, Gnome Shell always starts muted.

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

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

[Desktop-packages] [Bug 1821900] [NEW] Ubuntu 19.04 Community Wallpapers

Public bug reported:

Attached are the winning entries from the wallpaper competition for
19.04.

These have been resized to n x 2160 pixels at 72x72 dpi and then cropped
to 16:9 where needed.

They are all named Image_Title_by_Author_Name

** Affects: ubuntu-wallpapers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rls-dd-incoming

** Attachment added: "FCS_wallpapers_1904.tar.xz"
   
https://bugs.launchpad.net/bugs/1821900/+attachment/5249731/+files/FCS_wallpapers_1904.tar.xz

** Tags added: rls-dd-incoming

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

Title:
  Ubuntu 19.04 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.04.

  These have been resized to n x 2160 pixels at 72x72 dpi and then
  cropped to 16:9 where needed.

  They are all named Image_Title_by_Author_Name

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

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

[Desktop-packages] [Bug 1821901] [NEW] Location services option should be off by default

Public bug reported:

During first run of g-i-s in Disco the Privacy screen has an option for
enabling/disabling Location Services.  From review with the legal team,
this should be off by default but it is currently on by default.

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


** Tags: rls-dd-incoming

** Tags added: rls-dd-incoming

** Description changed:

- During first run of g-i-s the Privacy screen has an option for
+ During first run of g-i-s in Disco the Privacy screen has an option for
  enabling/disabling Location Services.  From review with the legal team,
  this should be off by default but it is currently on by default.

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

Title:
  Location services option should be off by default

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  During first run of g-i-s in Disco the Privacy screen has an option
  for enabling/disabling Location Services.  From review with the legal
  team, this should be off by default but it is currently on by default.

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

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

[Desktop-packages] [Bug 1821895] [NEW] Gnome Shell crashes after resume on Disco

2019-03-27 Thread Joseph Borg

Public bug reported:

System - XPS13 9370

To the best of my knowledge, this was working fine last week.  I updated
the system via Apt, the system fails to resume after being suspended
(via lid close).  There is a blank screen for a few seconds, followed by
the cursor appearing (still blank background) and then gnome crashes and
comes back to the login screen.

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

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

Title:
  Gnome Shell crashes after resume on Disco

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  System - XPS13 9370

  To the best of my knowledge, this was working fine last week.  I
  updated the system via Apt, the system fails to resume after being
  suspended (via lid close).  There is a blank screen for a few seconds,
  followed by the cursor appearing (still blank background) and then
  gnome crashes and comes back to the login screen.

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

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

[Desktop-packages] [Bug 1821897] [NEW] Unrecoverable failure in required component org.gnome.Shell.desktop

2019-03-27 Thread smay

Public bug reported:

os: ubuntu 18.10
kernel: 4.18.0-16-generic

bug: Thg 3 27 17:06:28 smay-X556UR gnome-session-binary[971]:
Unrecoverable failure in required component org.gnome.Shell.desktop

help me. please!

thanks you.

** 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/1821897

Title:
  Unrecoverable failure in required component org.gnome.Shell.desktop

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

Bug description:
  os: ubuntu 18.10
  kernel: 4.18.0-16-generic

  bug: Thg 3 27 17:06:28 smay-X556UR gnome-session-binary[971]:
  Unrecoverable failure in required component org.gnome.Shell.desktop

  help me. please!

  thanks you.

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

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

[Desktop-packages] [Bug 1821882] [NEW] Screen is very dark and brightness cannot be adjusted

2019-03-27 Thread Pierre Equoy

Public bug reported:

Device: Dell Precision 7530
In the BIOS, the Switchable Graphics option is deactived, which means only the 
nVidia GPU is used.

When booting 19.04 beta live USB, the screen becomes very dark and
brightness cannot be adjusted. (The same issue happens with 18.04.2)

There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
intel_backlight):

$ ll /sys/class/backlight/
total 0
drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

Trying to manually change brightness doesn't do anything:

$ sudo su
root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
root@ubuntu:/sys/class/backlight/nv_backlight# ll
total 0
drwxr-xr-x 3 root root0 Mar 27 09:28 ./
drwxr-xr-x 4 root root0 Mar 27 09:28 ../
-r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
-rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
-rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
-r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
drwxr-xr-x 2 root root0 Mar 27 09:28 power/
lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
-r--r--r-- 1 root root 4096 Mar 27 09:28 type
-rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
50

Although the value is changed, the screen brightness doesn't change.

in dmesg, I can see the following:

[0.241878] ACPI: Added _OSI(Module Device)
[0.241878] ACPI: Added _OSI(Processor Device)
[0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.241878] ACPI: Added _OSI(Processor Aggregator Device)
[0.241878] ACPI: Added _OSI(Linux-Dell-Video)
[0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288620] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288623] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288625] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289376] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.289379] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.289381] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289382] ACPI BIOS Error (bug): Failure creating

[Desktop-packages] [Bug 1821870] Re: gnome-shell segfault libmutter-clutter-2