[Desktop-packages] [Bug 513133]

2019-02-16 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance: https://gitlab.freedesktop.org/xdg
/xdg-utils/issues/37.

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

Title:
  When chromium is the only browser installed, i'm still asked to make
  it the default

Status in Xdg-utils:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  I removed firefox* and xulrunner* from my system before installing
  chromium.

  When I launched it using:
  $ x-www-browser

  I still got a dialog asking me to make it the default browser.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Jan 27 02:53:26 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Mythbuntu 10.04 "Lucid Lynx" - Alpha i386 (20100125)
  Package: chromium-browser 4.0.305.0~svn20100123r36929-0ubuntu1
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
  SourcePackage: chromium-browser
  Uname: Linux 2.6.32-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/513133/+subscriptions

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


[Desktop-packages] [Bug 1816237] [NEW] There is no lightdm in ubuntu

2019-02-16 Thread Manar Khaled ALBataineh
Public bug reported:

The LightDM configuration files are empty

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm (not installed)
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 16 15:46:34 2019
InstallationDate: Installed on 2019-02-05 (11 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  There is no lightdm in ubuntu

Status in lightdm package in Ubuntu:
  New

Bug description:
  The LightDM configuration files are empty

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 15:46:34 2019
  InstallationDate: Installed on 2019-02-05 (11 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1247160] Re: Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound at all

2019-02-16 Thread Paul White
Further to comment #25, issue resolved by installing latest Ubuntu
release.

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

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

Title:
  Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out,
  HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  The problem I reported regarding no audio/sound over HDMI in Ubuntu 11
  series as bug #793592, which was fixed in 12.04 and 12.10, has
  unfortunately reappeared in Ubuntu 13.10 following a fresh
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Date: Fri Nov  1 17:49:50 2013
  InstallationDate: Installed on 2013-11-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Symptom_Jack: Black Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 0P096C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: '01'
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd11/09/2009:svnDellInc.:pnStudioHybrid140g:pvr00:rvnDellInc.:rn0P096C:rvrA00:cvnDellInc.:ct3:cvr'01':
  dmi.product.name: Studio Hybrid 140g
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-02-16 Thread Nenad Antic
According to this stackexchange thread

https://unix.stackexchange.com/questions/36450/how-can-i-find-a-memory-leak-of-a-running-process/282944
Here is almost guarantee steps to find who is leaking the memory 

the dumps just posted should have enough information to be able to find
the leaking code sections in Xorg.

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg package in Ubuntu:
  New

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  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
  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 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1816264] Re: software center stuck on Chrome package dialog

2019-02-16 Thread Jann Horn
Simple reproducer in a freshly booted system:

 - open Ubuntu Software Center
 - click on some random package
 - close the window
 - open Ubuntu Software Center
 - attempt to use the back button ("<") in the upper-left corner of the window

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

Title:
  software center stuck on Chrome package dialog

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 18.10 with Wayland in a fresh VM. I configured the
  VM to use Wayland, downloaded Google Chrome from
  https://google.com/chrome, installed Chrome by opening the package
  with Ubuntu Software Center and pressing the install button, and
  closed Ubuntu Software Center. Now, when I open Ubuntu Software Center
  again, I see a dialog with title "google-chrome-stable" (the package
  name) and some information about the package. The dialog has something
  that looks like a "back" button in the top-left corner, but clicking
  it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 22:35:53 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-02-16 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu5
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1816264] Re: software center stuck on Chrome package dialog

2019-02-16 Thread Jann Horn
[Testing on wayland, in case that matters.]

I downloaded a .deb file with Firefox, then opened it with "Ubuntu
Software Center", installed it, and then closed the dialog associated
with Ubuntu Software Center. Now, opening "Ubuntu Software Center" gets
me back to the dialog displaying details about the installed package,
and the "back" button in the upper left doesn't work.

Killing the gnome-software process and then relaunching the software
center gets me back to the software center's main screen. If I now click
on a package, the back button in the upper left works.

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

Title:
  software center stuck on Chrome package dialog

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 18.10 with Wayland in a fresh VM. I configured the
  VM to use Wayland, downloaded Google Chrome from
  https://google.com/chrome, installed Chrome by opening the package
  with Ubuntu Software Center and pressing the install button, and
  closed Ubuntu Software Center. Now, when I open Ubuntu Software Center
  again, I see a dialog with title "google-chrome-stable" (the package
  name) and some information about the package. The dialog has something
  that looks like a "back" button in the top-left corner, but clicking
  it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 22:35:53 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-02-16 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu5
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1816265] [NEW] Disco Dingo Wayland Fractional Scale

2019-02-16 Thread Peter Nunn
Public bug reported:

Installed live session on a Dell XPS 13. Runs really well but after
enabling wayland and turning on the experimental bits

gsettings set org.gnome.mutter experimental-features "['scale-monitor-
framebuffer']"

I still don't get fractional scaling on the single laptop screen (100,
200 etc only).

When an external monitor is plugged in I do then get fractional scaling
and it works well.

This needs to be available on a single monitor as well.

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

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

Title:
  Disco Dingo Wayland Fractional Scale

Status in wayland package in Ubuntu:
  New

Bug description:
  Installed live session on a Dell XPS 13. Runs really well but after
  enabling wayland and turning on the experimental bits

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"

  I still don't get fractional scaling on the single laptop screen (100,
  200 etc only).

  When an external monitor is plugged in I do then get fractional
  scaling and it works well.

  This needs to be available on a single monitor as well.

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

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


[Desktop-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering

2019-02-16 Thread Stuart
Just wondering if there is any update on this?

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

Title:
  DP1.2 daisy-chain flickering

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1816269] [NEW] No image on KVM switch

2019-02-16 Thread Stuart
Public bug reported:

Hi all,

I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
(uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to a
dual DisplayPort adapter, to an Avocent SV340D KVM.

If I have the KVM on the switch for the NUC, everything works great. If
I switch the KVM to another channel, and then switch back to the NUC, I
only get black screens. The only solution is to hard reboot the NUC.

Any help would be appreciated.

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

** Description changed:

  Hi all,
  
  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to a
  dual DisplayPort adapter, to an Avocent SV340D KVM.
  
  If I have the KVM on the switch for the NUC, everything works great. If
  I switch the KVM to another channel, and then switch back to the NUC, I
  only get black screens. The only solution is to hard reboot the NUC.
  
- Any help would be aprpeciated.
+ Any help would be appreciated.

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

Title:
  No image on KVM switch

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to
  a dual DisplayPort adapter, to an Avocent SV340D KVM.

  If I have the KVM on the switch for the NUC, everything works great.
  If I switch the KVM to another channel, and then switch back to the
  NUC, I only get black screens. The only solution is to hard reboot the
  NUC.

  Any help would be appreciated.

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

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


[Desktop-packages] [Bug 1816271] [NEW] no sound

2019-02-16 Thread Kris M
Public bug reported:

19.04,kern 4.19.0-13
just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
kris@kris-ThinkPad-T530:~$ lsb_release -rd
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
kris@kris-ThinkPad-T530:~$ 

kris@kris-ThinkPad-T530:~$ uname -a
Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
kris@kris-ThinkPad-T530:~$ 

kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
kris@kris-ThinkPad-T530:~$ 

I expected sound to recognize soundcard/speakers. It did not until I
unplug/replug headphones.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
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: Sat Feb 16 19:20:26 2019
InstallationDate: Installed on 2019-02-09 (7 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gst-plugins-good1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-good1.0 (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 gst-plugins-good1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1816271

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
  kris@kris-ThinkPad-T530:~$ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ uname -a
  Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kris@kris-ThinkPad-T530:~$ 

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  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: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+subscriptions

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

[Desktop-packages] [Bug 513133] Re: When chromium is the only browser installed, i'm still asked to make it the default

2019-02-16 Thread Bug Watch Updater
** Changed in: xdg-utils
   Status: Confirmed => Unknown

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

Title:
  When chromium is the only browser installed, i'm still asked to make
  it the default

Status in Xdg-utils:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  I removed firefox* and xulrunner* from my system before installing
  chromium.

  When I launched it using:
  $ x-www-browser

  I still got a dialog asking me to make it the default browser.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Jan 27 02:53:26 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Mythbuntu 10.04 "Lucid Lynx" - Alpha i386 (20100125)
  Package: chromium-browser 4.0.305.0~svn20100123r36929-0ubuntu1
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
  SourcePackage: chromium-browser
  Uname: Linux 2.6.32-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/513133/+subscriptions

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


[Desktop-packages] [Bug 1688265] Re: Wifi disconnects when screen is locked

2019-02-16 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Wifi disconnects when screen is locked

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  Ubuntu: 17.04
  Wifi Chipset: Intel 7260 rev bb
  Driver: iwlwifi 4.10.0-19-generic

  If I lock my screen overnight, the following morning my Wifi will be
  disconnected and is slow to reconnect and often requires multiple
  connection attempts. Locking my screen for a short period of time
  (minutes or hours) doesn't trigger the behavior.

  Dmesg:

  
  ```
  [1256404.227085] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256404.229298] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256404.230281] wlp5s0: authenticated
  [1256404.843347] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256409.234035] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256413.045691] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256413.047962] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256413.048999] wlp5s0: authenticated
  [1256413.661996] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256418.051499] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256422.361848] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256422.364062] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256422.365122] wlp5s0: authenticated
  [1256422.978086] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256426.516541] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256426.518958] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.524074] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.544019] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.578930] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256426.581309] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.582424] wlp5s0: authenticated
  [1256426.582716] wlp5s0: associate with 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.583584] wlp5s0: RX AssocResp from 00:25:9c:xx:xx:xx (capab=0x11 
status=0 aid=1)
  [1256426.584763] wlp5s0: associated
  [1256426.584867] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
  [1256426.630815] bridge-wlp5s0: device is wireless, enabling SMAC
  [1256426.630817] bridge-wlp5s0: up
  [1256426.630823] bridge-wlp5s0: attached
  ```

  There are hundreds of lines like this. It looks like it gets into a
  loop where it disconnects every 5 seconds. Once I log in and reconnect
  using the applet in the menu bar, the connection is pretty reliable
  for hours -- I generally work a full day without wifi dropping.

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

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


[Desktop-packages] [Bug 1816271] Re: no sound

2019-02-16 Thread Kris M
** Attachment added: "sound after boot, AFTER I unplug/replug headphones."
   
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+attachment/5239199/+files/Screenshot%20from%202019-02-16%2019-59-54.png

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

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
  kris@kris-ThinkPad-T530:~$ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ uname -a
  Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kris@kris-ThinkPad-T530:~$ 

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  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: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+subscriptions

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


[Desktop-packages] [Bug 1816271] Re: no sound

2019-02-16 Thread Kris M
** Attachment added: "sound after boot"
   
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+attachment/5239198/+files/Screenshot%20from%202019-02-16%2019-59-01.png

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

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
  kris@kris-ThinkPad-T530:~$ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ uname -a
  Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  kris@kris-ThinkPad-T530:~$ 

  kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kris@kris-ThinkPad-T530:~$ 

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  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: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+subscriptions

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


[Desktop-packages] [Bug 1809025] Re: Files Failed to Be Moved to The Desktop

2019-02-16 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Files Failed to Be Moved to The Desktop

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I was trying to move a downloaded file from the "Downloads" folder to
  the actual desktop background and the file(s) wouldn't move from any
  folder to there. Please make a fix for this as its already a
  workaround. [By the way, this happens when you change from the the
  default wallpaper].

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 13:52:46 2018
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2018-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181218)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-generic 
root=UUID=6c7fa075-d8d0-47c2-b828-83d330564545 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1019DD202:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8470p
  dmi.product.sku: D2E04UP#ABA
  dmi.product.version: A1019DD202
  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.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/nautilus/+bug/1809025/+subscriptions

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


[Desktop-packages] [Bug 1816271] Re: no sound

2019-02-16 Thread Jeremy Bicha
** Description changed:

  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
- kris@kris-ThinkPad-T530:~$ lsb_release -rd
- Description:  Ubuntu Disco Dingo (development branch)
- Release:  19.04
- kris@kris-ThinkPad-T530:~$ 
- 
- kris@kris-ThinkPad-T530:~$ uname -a
- Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
- kris@kris-ThinkPad-T530:~$ 
- 
- kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
- N: Unable to locate package pkgname
- kris@kris-ThinkPad-T530:~$ 
  
  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  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: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  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: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  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: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+subscriptions

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


[Desktop-packages] [Bug 1317552] Re: usb modem doesn't recognized by system until wired network connected

2019-02-16 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  usb modem doesn't recognized by system until wired network connected

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I have an usb 3g modem huawei, configured as standalone network
  device. When I connect it, dmesg shows some error messages, but
  nothing happens. After connect and futher disconnect wired network
  (eth0), it succesful recognized by the system as eth1 device and all
  works fine. Problem is that sometimes I have no wired network to start
  usb-3g connection this way.

  Part of dmesg with connect/disconnect manipulations

  [   27.606224] init: libvirt-bin main process (979) terminated with status 127
  [   27.606239] init: libvirt-bin main process ended, respawning
  [   27.915799] r8169 :01:00.0 eth0: link down
  [   27.915869] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   27.916229] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   27.938186] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [   27.941688] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [   28.566084] usb 1-1.1: New USB device found, idVendor=0cf3, idProduct=0036
  [   28.566089] usb 1-1.1: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   28.775155] init: plymouth-upstart-bridge main process ended, respawning
  [   34.989561] FAT-fs (sdb1): Volume was not properly unmounted. Some data 
may be corrupt. Please run fsck.
  [   55.380263] usb 3-3: new high-speed USB device number 3 using xhci_hcd
  [   55.397190] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01
  [   55.397202] usb 3-3: New USB device strings: Mfr=2, Product=1, 
SerialNumber=0
  [   55.397207] usb 3-3: Product: HUAWEI HiLink
  [   55.397212] usb 3-3: Manufacturer: HUAWEI
  [   55.465739] usb-storage 3-3:1.0: USB Mass Storage device detected
  [   55.465795] scsi7 : usb-storage 3-3:1.0
  [   55.465865] usbcore: registered new interface driver usb-storage
  [   56.464794] scsi 7:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
  [   56.472835] sr1: scsi-1 drive
  [   56.472989] sr 7:0:0:0: Attached scsi CD-ROM sr1
  [   56.473080] sr 7:0:0:0: Attached scsi generic sg3 type 5
  [   56.558838] audit_printk_skb: 156 callbacks suppressed
  [   56.558842] type=1400 audit(1399561168.962:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2017 comm="apparmor_parser"
  [   56.558850] type=1400 audit(1399561168.962:65): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2017 comm="apparmor_parser"
  [   56.559369] type=1400 audit(1399561168.962:66): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2017 comm="apparmor_parser"
  [   56.638660] Buffer I/O error on device sr1, logical block 0
  [   56.638668] Buffer I/O error on device sr1, logical block 0
  [   56.638685] Buffer I/O error on device sr1, logical block 0
  [   56.638693] Buffer I/O error on device sr1, logical block 0
  [   56.638701] Buffer I/O error on device sr1, logical block 1
  [   56.638708] Buffer I/O error on device sr1, logical block 1
  [   56.638716] Buffer I/O error on device sr1, logical block 512
  [   56.640490] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.640501] systemd-udevd[2001]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.651401] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [   56.651427] systemd-udevd[1987]: Failed to apply ACL on /dev/sr1: No such 
file or directory
  [  107.810564] usb 3-3: USB disconnect, device number 3
  [  116.952712] usb 3-3: new high-speed USB device number 4 using xhci_hcd
  [  116.969698] usb 3-3: New USB device found, idVendor=12d1, idProduct=1f01
  [  116.969709] usb 3-3: New USB device strings: Mfr=2, Product=1, 
SerialNumber=0
  [  116.969715] usb 3-3: Product: HUAWEI HiLink
  [  116.969720] usb 3-3: Manufacturer: HUAWEI
  [  116.971391] usb-storage 3-3:1.0: USB Mass Storage device detected
  [  116.971653] scsi8 : usb-storage 3-3:1.0
  [  117.969336] scsi 8:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
  [  117.971006] sr1: scsi-1 drive
  [  117.971389] sr 8:0:0:0: Attached scsi CD-ROM sr1
  [  117.974632] sr 8:0:0:0: Attached scsi generic sg3 type 5
  [  118.063825] quiet_error: 1 callbacks suppressed
  [  118.063836] Buffer I/O error on device sr1, logical block 9
  [  118.063849] Buffer I/O error on device sr1, logical block 9
  [  118.063943] Buffer I/O error on device sr1, logical block 0
  [  118.063951] 

[Desktop-packages] [Bug 1395501] Re: input devices found, but there is no input level

2019-02-16 Thread Paul White
Further to comment #18, closing as "Invalid" due to changes made by
user.

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

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

Title:
  input devices found, but there is no input level

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  My input devices is found, but no not working. Get no input level from the 
devices.
  They are not muted!

  pavucontrol > Input Devices > no input level from any of my input devices!
  System settings > Sound > Input > no input level from any of my input devices!

  My computer is a Dell XPS 15 9530.
  Ubuntu 14.04
  Kernel release:3.13.0-39-generic.

  ARECORD
   List of CAPTURE Hardware Devices 
  card 1: G4ME1 [Sennheiser 3D G4ME1], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 2: PCH [HDA Intel PCH], device 0: ALC668 Analog [ALC668 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0

  "wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh" gives:
  http://www.alsa-project.org/db/?f=916914afd5195a1d4ed40f3f38fa0d37285d1039

  Screenshot from alsamixer, pavucontrol and sound control menu.
  https://mrkr.io/pemHMWlKHR

  Teamspeak works fine, if I select recording device in pavucontrol for 
teamspeak.
  https://mrkr.io/5D0ZUSVyLC
  https://mrkr.io/T6nQX77HAD

  Testing in skype, no input is registered!
  https://mrkr.io/xMbrev28bR
  https://mrkr.io/zqu6AFVjld

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

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


[Desktop-packages] [Bug 1814949] Re: gnome-control-center refuses to open if you try to open the Details panels

2019-02-16 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.31.90-1ubuntu3

---
gnome-control-center (1:3.31.90-1ubuntu3) disco; urgency=medium

  * Add new info panel patch to debian/patches/series
  * Increase height in ubuntu-default-height.patch (for new Applications panel)
  * Modify 70_allow_sound_above_100.patch to add a frame around the system
volume box

 -- Jeremy Bicha   Thu, 14 Feb 2019 08:48:46 -0500

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

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

Title:
  gnome-control-center refuses to open if you try to open the Details
  panels

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Workaround
  ==
  Run this command in your terminal:
  gsettings reset org.gnome.ControlCenter last-panel

  and then avoid opening the Details panels

  Issue
  =
  If you try to open the Details panel, gnome-control-center will crash.
  It will then refuse to open.

  Upstream Bug Report
  ===
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285

  See also
  https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/387

  Original Bug Report
  ===
  Segmentation fault while trying to run via cli , the gnome setting doesn't 
working when click on setting menu

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.30.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 14:38:32 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-05-04 (643 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>:  mov
-0x8(%rdi),%rax
   PC (0x7f783f52232d) ok
   source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI___libc_free (mem=0x1) at malloc.c:3085
   g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: Upgraded to disco on 2018-11-06 (92 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1816242] [NEW] Crashes while resizing using annotate-mode from melpa

2019-02-16 Thread mokrates
Public bug reported:

Hi,

I installed annotate-mode from melpa (there is a one in the stable repo
and one in the other, with either version, the bug occurrs), and used
it:

M-x annotate-mode
C-c C-a foobar

This annotates the file.

When the emacs window is too small, I get following *Messages*:
---
Annotations loaded.
Fontifying block...(args-out-of-range foo 0 -6) [2 times]
Error during redisplay: (jit-lock-function 1) signaled (args-out-of-range "foo" 
0 -6)
QuitError during redisplay: (jit-lock-function 1) signaled (args-out-of-range 
"foo" 0 -6)
Mark set
Error during redisplay: (jit-lock-function 1) signaled (args-out-of-range "foo" 
0 -6)
QuitError during redisplay: (jit-lock-function 1) signaled (args-out-of-range 
"foo" 0 -6)
---

While this messages seem to originate outside of 'annotation-mode' on
which page this bug is already filed, this isn't the bug I want to
report, but this seems to be the prerequisite.

If I now wildly resize the emacs-window (trying to figure out what
exactly triggers this and how to fix it), emacs freezes so that only
kill -9 can shut it down. Usually this triggers not only a "killed" but
a "segfault (core dumped)" on the terminal.

Thank you for your software

mo

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: emacs 1:25.2+1-11
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Feb 16 16:38:22 2019
InstallationDate: Installed on 2019-01-14 (32 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
PackageArchitecture: all
SourcePackage: emacs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Crashes while resizing using annotate-mode from melpa

Status in emacs package in Ubuntu:
  New

Bug description:
  Hi,

  I installed annotate-mode from melpa (there is a one in the stable
  repo and one in the other, with either version, the bug occurrs), and
  used it:

  M-x annotate-mode
  C-c C-a foobar

  This annotates the file.

  When the emacs window is too small, I get following *Messages*:
  ---
  Annotations loaded.
  Fontifying block...(args-out-of-range foo 0 -6) [2 times]
  Error during redisplay: (jit-lock-function 1) signaled (args-out-of-range 
"foo" 0 -6)
  QuitError during redisplay: (jit-lock-function 1) signaled (args-out-of-range 
"foo" 0 -6)
  Mark set
  Error during redisplay: (jit-lock-function 1) signaled (args-out-of-range 
"foo" 0 -6)
  QuitError during redisplay: (jit-lock-function 1) signaled (args-out-of-range 
"foo" 0 -6)
  ---

  While this messages seem to originate outside of 'annotation-mode' on
  which page this bug is already filed, this isn't the bug I want to
  report, but this seems to be the prerequisite.

  If I now wildly resize the emacs-window (trying to figure out what
  exactly triggers this and how to fix it), emacs freezes so that only
  kill -9 can shut it down. Usually this triggers not only a "killed"
  but a "segfault (core dumped)" on the terminal.

  Thank you for your software

  mo

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: emacs 1:25.2+1-11
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb 16 16:38:22 2019
  InstallationDate: Installed on 2019-01-14 (32 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: emacs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1816247] Re: The "Show terminal menu bar" is not enabled

2019-02-16 Thread Edson José dos Santos
The terminal menu bar appears only if added manually.
Even though you have started and marked it manually, it will not stay if you 
need to reopen it.


** Attachment added: "Barra de menu só aparece se adicionada manualmente"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816247/+attachment/5239142/+files/Captura%20de%20tela%20de%202019-02-16%2013-52-11.png

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

Title:
  The "Show terminal menu bar" is not enabled

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Hi guys

  The "Show terminal menu bar is not enabled.
  Every time we open the terminal we have to manually inhabit the "Show menu 
bar"

  When we enter the edit option / preferences / shortcuts the "Hide and
  Show menu bar" option is not enabled, much less let us return to the
  default.

  As per attached image, I changed by mistake and can not revert, but
  before having changed the above situation already occurred.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 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: Sat Feb 16 13:48:38 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  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/1816247/+subscriptions

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


[Desktop-packages] [Bug 1816247] Re: The "Show terminal menu bar" is not enabled

2019-02-16 Thread Edson José dos Santos
When we enter the edit option / preferences / shortcuts the "Hide and
Show menu bar" option is not enabled, much less let us return to the
default.

As per attached image, I changed by mistake and can not revert, but
before having changed the above situation already occurred.

** Attachment added: "The terminal menu option is not enabled"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816247/+attachment/5239143/+files/Captura%20de%20tela%20de%202019-02-16%2013-53-05.png

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

Title:
  The "Show terminal menu bar" is not enabled

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Hi guys

  The "Show terminal menu bar is not enabled.
  Every time we open the terminal we have to manually inhabit the "Show menu 
bar"

  When we enter the edit option / preferences / shortcuts the "Hide and
  Show menu bar" option is not enabled, much less let us return to the
  default.

  As per attached image, I changed by mistake and can not revert, but
  before having changed the above situation already occurred.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 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: Sat Feb 16 13:48:38 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  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/1816247/+subscriptions

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


[Desktop-packages] [Bug 1816247] [NEW] The "Show terminal menu bar" is not enabled

2019-02-16 Thread Edson José dos Santos
Public bug reported:

Hi guys

The "Show terminal menu bar is not enabled.
Every time we open the terminal we have to manually inhabit the "Show menu bar"

When we enter the edit option / preferences / shortcuts the "Hide and
Show menu bar" option is not enabled, much less let us return to the
default.

As per attached image, I changed by mistake and can not revert, but
before having changed the above situation already occurred.

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-terminal 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: Sat Feb 16 13:48:38 2019
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2019-02-11 (4 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

** Attachment added: "Opening the Terminal Menu Bar Does Not Appear"
   
https://bugs.launchpad.net/bugs/1816247/+attachment/5239135/+files/Captura%20de%20tela%20de%202019-02-16%2013-51-55.png

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

Title:
  The "Show terminal menu bar" is not enabled

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Hi guys

  The "Show terminal menu bar is not enabled.
  Every time we open the terminal we have to manually inhabit the "Show menu 
bar"

  When we enter the edit option / preferences / shortcuts the "Hide and
  Show menu bar" option is not enabled, much less let us return to the
  default.

  As per attached image, I changed by mistake and can not revert, but
  before having changed the above situation already occurred.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 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: Sat Feb 16 13:48:38 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  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/1816247/+subscriptions

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


[Desktop-packages] [Bug 1816251] Re: HP Spectre x360 15" notebook: Battery drains off during the laptop sleep

2019-02-16 Thread M K
** Description changed:

- HP Spectre x360 15" notebook: Battery drains off during the laptop sleep
- (with or without connected USB-C dock) and not possible to enable deep
- sleep.
+ [HP Spectre x360 - 15-df0008nc]: Battery is drained during the laptop
+ sleep. Additionally it is not possible to enable deep sleep. The
+ symptoms are the same with or without connected USB-C dock.
  
- Enabling deep sleep results into failure: 
- $ sudo echo deep > /sys/power/mem_sleep
- bash: /sys/power/mem_sleep: Permission denied. 
+ Full laptop specification is here:
+ https://support.hp.com/za-en/document/c06200426
  
  
- Additionally also not possible to enable deep sleep by updating grub.
+ Enabling deep sleep results into failure:
+ $ sudo echo deep > /sys/power/mem_sleep
+ bash: /sys/power/mem_sleep: Permission denied.
+ 
+ Additionally also not possible to enable deep sleep by updating grub
+ loader.
  
  # editing /etc/default/grub
  # Adding
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
  sudo update-grub
- # reboot laptop
- # and still gets
+ # reboot laptop and still gets s2idle
  $ cat /sys/power/mem_sleep
  [s2idle]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-power-manager 3.26.0-1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:22:25 2019
  InstallationDate: Installed on 2019-02-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- HP Spectre x360 15" notebook: Battery drains off during the laptop sleep
+ [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep

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

Title:
  [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep
  mode

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

Bug description:
  [HP Spectre x360 - 15-df0008nc] Battery is significantly drained in
  the laptop sleep mode. Over the night the fully charged laptop battery
  will get empty while kept the laptop in sleep mode. The symptoms are
  the same with or without connected USB-C dock.

  As a workaround also it is not possible to enable deep sleep.

  Full laptop specification is here:
  https://support.hp.com/za-en/document/c06200426

  Enabling deep sleep results into failure:
  $ sudo echo deep > /sys/power/mem_sleep
  bash: /sys/power/mem_sleep: Permission denied.

  Additionally also not possible to enable deep sleep by updating grub
  loader.

  # editing /etc/default/grub
  # Adding
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
  sudo update-grub
  # reboot laptop and still gets s2idle
  $ cat /sys/power/mem_sleep
  [s2idle]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-power-manager 3.26.0-1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:22:25 2019
  InstallationDate: Installed on 2019-02-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 475608] Re: no microphone recording on vaio

2019-02-16 Thread Paul White
Bug did not expire due other bug task
No reply to request for information 9 years ago
Marking "Invalid" to close

** Changed in: alsa-driver
   Status: New => Invalid

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

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

Title:
  no microphone recording on vaio

Status in ALSA driver:
  Invalid
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  It's impossibile to record audio using the internal (stereo)
  microphone.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alessandro   2246 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd930 irq 22'
 Mixer name : 'Realtek ALC262'
 Components : 'HDA:10ec0262,104d3200,00100302 
HDA:14f12c06,104d1700,0010'
 Controls  : 18
 Simple ctrls  : 11
  CheckboxCommand: alsa_record_playback
  CheckboxDescription:
   Open the volume control application by right-clicking on the speaker icon in 
the panel and selecting "Sound Preferences".  Select the "Input" tab and choose 
any alternate (non-default) device(s).  Select the "Output" tab and choose any 
alternate (non-default) device(s).  When you are done, click the Test button, 
then speak into the microphone. After a few seconds, your speech will be played 
back to you.
   
   La propria voce è stata riprodotta?
  CheckboxTest: alsa_record_playback_alternates
  Date: Thu Nov  5 18:17:04 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: ksplice_w7k55i5m_vmlinux_new ksplice_w7k55i5m nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=it_IT.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic i686

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

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


[Desktop-packages] [Bug 726982] Re: Internal Microphone not working, Unable to record sound in Acer Aspire one 532H(A0532H)

2019-02-16 Thread Paul White
Bug report did not expire due to assignment
No reply by reporter to comment #2
No comments for around 8 years 
So marking "Invalid" to close

** Changed in: alsa-driver (Ubuntu)
 Assignee: varun kumar (varunkumar-eie) => (unassigned)

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

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

Title:
  Internal Microphone not working,Unable to record sound in Acer Aspire
  one 532H(A0532H)

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  1) problem with Internal Microphone in Acer Aspire One 532H(A0532H)

  Ubuntuforums Suggestion: Ubuntu forums suggested to install
  pavucontrol ,and also said to make right speaker in input devices to
  silence,did it,still my internal mic is not working,it is unable to
  record my voice in sound recroder,can't use gtalk,skype(Very Very
  Frustating). I have gnome alsa mixer,puse audio volume control,pulse
  audio device chooser.

  2) Memory card reader not working(ENE technology card reader not
  working)

  Ubuntu forums suggestion: ubuntu forum said to install some kernel,and
  they suggested to install a file called keucr,a very hard process for
  those who are new to ubuntu,i did all those,Still unable to detect the
  SD Card Reader.

  Please,at this time,solve my internal microphone issue,i am facing a
  sever issue with this.

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

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


[Desktop-packages] [Bug 554992] Re: wrong sound card detected

2019-02-16 Thread Paul White
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011
Bug report did not expire due to assignment
No reply to comment #2 nearly 9 years ago
Marking "Invalid" to close

** Changed in: alsa-driver (Ubuntu)
 Assignee: ajith abraham (ajithabraham-m) => (unassigned)

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

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

Title:
  wrong sound card detected

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  from the sound hardware information i can found only one channel
  facility . on conducting system testing i found that the detected
  sound hardware is wrong one

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajith  1913 F pulseaudio
   /dev/snd/pcmC0D0p:   ajith  1913 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xe312 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,8086d701,00100101'
 Controls  : 27
 Simple ctrls  : 16
  CheckboxCommand: cat /proc/asound/cards
  CheckboxDescription:
   Detecting your sound device(s):
   
   $output
   
   Is this correct?
  CheckboxTest: list_audio_devices
  Date: Sun Apr  4 11:56:51 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic i686

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

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


[Desktop-packages] [Bug 1816240] [NEW] Impossible to boot 18.04.2 from btrfs

2019-02-16 Thread BertN45
Public bug reported:

Try to install Xubuntu 18.04.2 on btrfs, it failed to boot because grub could 
not find the kernel.
The partition did have two directories @ and @home, the @ one contained all the 
root files, while the @home one contained the 'user' directory.

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

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

Title:
  Impossible to boot 18.04.2 from btrfs

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Try to install Xubuntu 18.04.2 on btrfs, it failed to boot because grub could 
not find the kernel.
  The partition did have two directories @ and @home, the @ one contained all 
the root files, while the @home one contained the 'user' directory.

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

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


[Desktop-packages] [Bug 282754] Re: Internal Microphone Not Working On MacBook 1st Gen and Dell Notebook

2019-02-16 Thread Paul White
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010
Bug report did not expire due to another bug task
No reply to request for information almost 9 years ago
Marking "Invalid" to close

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

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

Title:
  Internal Microphone Not Working On MacBook 1st Gen and Dell Notebook

Status in Mactel Support:
  New
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu intrepid (development branch)
  Release:  8.10

   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Internal Microphone does not work. Using Volume Control, if I unmute
  Mux, Mux1, Capture, Capture1, it immediately mutes itself again. I am
  willing to provide any details/help. Please contact me.

  Thanks,

  Anju

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/282754/+subscriptions

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


[Desktop-packages] [Bug 1816202] Re: Mesa version is old

2019-02-16 Thread Timo Aaltonen
that radeon thing should be able to do full 4.5, but the driver is
probably missing something which probably is in mesa 18.3 or 19.0,
neither of which will be pushed to ubuntu 18.10

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

Title:
  Mesa version is old

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  https://mesamatrix.net/ shows that OpenGL version for:
  Intel: 4.5.
  R600: 4.4.
  However, I get 4.2 for Intel and 3.3 for AMD. I think upgrading latest 
available version'd solve the problem.

  CPU: Intel Core i 5.
  GPU: Radeon HD 7670.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglapi-mesa 18.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 01:38:34 2019
  Dependencies:
   gcc-8-base 8.2.0-7ubuntu1
   libc6 2.28-0ubuntu1
   libgcc1 1:8.2.0-7ubuntu1
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:183e]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 7670M [103c:183e]
  InstallationDate: Installed on 2019-02-07 (7 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  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/mesa/+bug/1816202/+subscriptions

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


[Desktop-packages] [Bug 1816202] Re: Mesa version is old

2019-02-16 Thread Timo Aaltonen
your hardware is old, and probably won't ever support any newer opengl
version


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

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

Title:
  Mesa version is old

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  https://mesamatrix.net/ shows that OpenGL version for:
  Intel: 4.5.
  R600: 4.4.
  However, I get 4.2 for Intel and 3.3 for AMD. I think upgrading latest 
available version'd solve the problem.

  CPU: Intel Core i 5.
  GPU: Radeon HD 7670.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglapi-mesa 18.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 01:38:34 2019
  Dependencies:
   gcc-8-base 8.2.0-7ubuntu1
   libc6 2.28-0ubuntu1
   libgcc1 1:8.2.0-7ubuntu1
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:183e]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 7670M [103c:183e]
  InstallationDate: Installed on 2019-02-07 (7 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  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/mesa/+bug/1816202/+subscriptions

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


[Desktop-packages] [Bug 1816251] Re: [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep

2019-02-16 Thread M K
** Description changed:

- [HP Spectre x360 - 15-df0008nc]: Battery is drained during the laptop
- sleep. Additionally it is not possible to enable deep sleep. The
- symptoms are the same with or without connected USB-C dock.
+ [HP Spectre x360 - 15-df0008nc] Battery is significantly drained in the
+ laptop sleep mode. Over the night the fully charged laptop battery will
+ get empty while kept the laptop in sleep mode. The symptoms are the same
+ with or without connected USB-C dock.
+ 
+ As a workaround also it is not possible to enable deep sleep.
  
  Full laptop specification is here:
  https://support.hp.com/za-en/document/c06200426
- 
  
  Enabling deep sleep results into failure:
  $ sudo echo deep > /sys/power/mem_sleep
  bash: /sys/power/mem_sleep: Permission denied.
  
  Additionally also not possible to enable deep sleep by updating grub
  loader.
  
  # editing /etc/default/grub
  # Adding
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
  sudo update-grub
  # reboot laptop and still gets s2idle
  $ cat /sys/power/mem_sleep
  [s2idle]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-power-manager 3.26.0-1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:22:25 2019
  InstallationDate: Installed on 2019-02-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep
+ [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep mode

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

Title:
  [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep
  mode

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

Bug description:
  [HP Spectre x360 - 15-df0008nc] Battery is significantly drained in
  the laptop sleep mode. Over the night the fully charged laptop battery
  will get empty while kept the laptop in sleep mode. The symptoms are
  the same with or without connected USB-C dock.

  As a workaround also it is not possible to enable deep sleep.

  Full laptop specification is here:
  https://support.hp.com/za-en/document/c06200426

  Enabling deep sleep results into failure:
  $ sudo echo deep > /sys/power/mem_sleep
  bash: /sys/power/mem_sleep: Permission denied.

  Additionally also not possible to enable deep sleep by updating grub
  loader.

  # editing /etc/default/grub
  # Adding
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
  sudo update-grub
  # reboot laptop and still gets s2idle
  $ cat /sys/power/mem_sleep
  [s2idle]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-power-manager 3.26.0-1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:22:25 2019
  InstallationDate: Installed on 2019-02-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1816171] Re: Show menubar by default in new terminals has no effect

2019-02-16 Thread Jeremy Bicha
** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  Show menubar by default in new terminals has no effect

Status in gnome-terminal package in Ubuntu:
  Triaged

Bug description:
  I open a terminal window. No menubar is displayed. 
  From the 'amburger' menu I select Preferences and 'Show menubar by default in 
new terminals' nothing happens and next time I open a terminal i have no 
menubar.
  If i right click on the terminal window and select 'Show menubar' i see the 
menubar but this option is not remembered next time i open a terminal.

  corrado@corrado-p6-dd-0215:~$ apt policy gnome-terminal
  gnome-terminal:
Installed: 3.31.90-1ubuntu1
Candidate: 3.31.90-1ubuntu1
Version table:
   *** 3.31.90-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p6-dd-0215:~$ inxi -SCGx
  System:
Host: corrado-p6-dd-0215 Kernel: 4.19.0-13-generic x86_64 bits: 64 
compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco 
Dingo) 
  CPU:
Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 
800 
4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 18.3.2 direct render: Yes 
  corrado@corrado-p6-dd-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 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-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 15 19:39:13 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2019-02-15 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190215)
  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/1816171/+subscriptions

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


[Desktop-packages] [Bug 225926] Re: Microphones on Compaq F750US not Working

2019-02-16 Thread Paul White
Bug report did not expire due to assignment
No reply to request for information
No comments for over 9 years so closing


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

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

Title:
  Microphones on Compaq F750US not Working

Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Expired

Bug description:
  I have Ubuntu 8.04 on a Compaq F750US.
  'lspci | grep -i audio' reports a Nvidia MCP67 REVa1 device.

  The Gnome Sound Recorder 2.22.0 does not record via the internal nor
  external microphones.

  I can provide any information you need, just ask.
  I can try things and restore my partition if it doesn't work or screws things 
up.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu.
  > Ubuntu 8.04
  > 'uname -r'  reports: 2.6.24-16-generic
  > 'lspci | grep -i audio' reports: Nvidia Corporation MCP67 High 
Definition Audio (rev a1)

  2) The version of the package you are using, via 'apt-cache policy 
packagename' or by checking in Synaptic.
  > Assuming "Alsa" here, Synaptic Package Mgr reports:  
 * alsa-base 1.0.16-0ubuntu4
 * alsa-utils  1.0.15-3ubuntu2
 * gstreamer0.10-alsa0.10.18-3

  3) What you expected to happen
  > I was hoping my test sound would be recorded.

  4) What happened instead
  > Nada. No sound played back whatsoever. And, I do have sound playing if 
I play a movie or sound file.

  2008-07-24: Is anyone looking into this?

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

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


[Desktop-packages] [Bug 1451170] Re: [ ASUS N550LF , Realtek ALC668, Speaker, Internal] To much sound

2019-02-16 Thread Paul White
Further to comment #56, closing.

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

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

Title:
  [ ASUS N550LF , Realtek ALC668, Speaker, Internal] To much sound

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Hi

  My laptop speaker doesn't want to switch off when my headphones is plugged.
  Description:Ubuntu 15.04
  Release:15.04

  alsa-base:
    Installé : 1.0.25+dfsg-0ubuntu4
    Candidat : 1.0.25+dfsg-0ubuntu4
   Table de version :
   *** 1.0.25+dfsg-0ubuntu4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  Thanks for your support

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   dubis1793 F...m pulseaudio
   /dev/snd/controlC1:  dubis1793 F pulseaudio
   /dev/snd/controlC0:  dubis1793 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun May  3 13:25:39 2015
  InstallationDate: Installed on 2014-10-16 (198 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   dubis1793 F...m pulseaudio
   /dev/snd/controlC1:  dubis1793 F pulseaudio
   /dev/snd/controlC0:  dubis1793 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC668, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-04-26 (6 days ago)
  dmi.bios.date: 01/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550LF.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550LF
  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.:bvrN550LF.212:bd01/13/2014:svnASUSTeKCOMPUTERINC.:pnN550LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N550LF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-05-01T15:39:09.184568

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

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


[Desktop-packages] [Bug 905022] Re: No sounds from headphones on ThinkPad T420

2019-02-16 Thread Paul White
Further to comment #4, closing as "Invalid" as no way of telling if
issue was ever fixed.

** Changed in: alsa-driver (Ubuntu)
 Assignee: Rolf Leggewie (r0lf) => (unassigned)

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

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

Title:
  No sounds from headphones on ThinkPad T420

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Long time reader, first time poster :-)

  I cannot get sound from the analog headphone/microphone port on my
  Lenovo ThinkPad T420. Based on Google searches I have fiddled with the
  snd-hda-intel options in /etc/modprobe.d/alsa-base.conf as follows:

  - Set model=thinkpad resulting in no sound through the headphone jack
  and the loss of the headphone playback connector in alsamixer.
  Unsurprisingly this results in no option to set or configure the
  analog headphone connector in the sound settings applet and/or
  pavucontrol.

  - Set model=generic with the same results as above.

  - Set model=auto which resulted in the appearance of the headphone
  connector (progress!) but I still get no sound from the headphones
  when I select the connector and/or mute the speakers through
  alsamixer.

  I also tried re-configuring the alsa-driver package to include verbose
  debugging support but ran into a whole lot of hassles (some of the
  source references smp_lock.h which is no more in kernel 3+, macro
  conflicts with system includes, etc.) when I tried to build it with
  module-assistant. I also tried to build it from the latest tarball
  from the alsa project with mixed results and ultimately no joy.

  Most problems of this kind I've seen tend to fall into 3 categories:
  (i) fixed by changing snd-hda-intel options, (ii) fixed through some
  sequence of random updates, (iii) sitting in silence. I'm hoping to be
  a bit more proactive.

  The output of alsa-info.sh is attached.

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

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


[Desktop-packages] [Bug 1816264] [NEW] software center stuck on Chrome package dialog

2019-02-16 Thread Jann Horn
Public bug reported:

I am running Ubuntu 18.10 with Wayland in a fresh VM. I configured the
VM to use Wayland, downloaded Google Chrome from
https://google.com/chrome, installed Chrome by opening the package with
Ubuntu Software Center and pressing the install button, and closed
Ubuntu Software Center. Now, when I open Ubuntu Software Center again, I
see a dialog with title "google-chrome-stable" (the package name) and
some information about the package. The dialog has something that looks
like a "back" button in the top-left corner, but clicking it does
nothing.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-software 3.30.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 16 22:35:53 2019
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2019-02-16 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.30.2-0ubuntu5
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  software center stuck on Chrome package dialog

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 18.10 with Wayland in a fresh VM. I configured the
  VM to use Wayland, downloaded Google Chrome from
  https://google.com/chrome, installed Chrome by opening the package
  with Ubuntu Software Center and pressing the install button, and
  closed Ubuntu Software Center. Now, when I open Ubuntu Software Center
  again, I see a dialog with title "google-chrome-stable" (the package
  name) and some information about the package. The dialog has something
  that looks like a "back" button in the top-left corner, but clicking
  it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-software 3.30.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 22:35:53 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-02-16 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu5
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 463589] Re: gnome-volume-control usability loss

2019-02-16 Thread Paul White
Bug report did not expire due to bug watch
No reply to request for information over 9 years ago
Marking "Invalid" to close

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

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

Title:
  gnome-volume-control usability loss

Status in ALSA Libraries:
  New
Status in GNOME media utilities:
  Invalid
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-media

  the new 2.28 gnome-volume-control suppressed the "line-in as output"
  option which is necessary to me. i've been scouring the web for hours
  looking for a workaround, but to no avail.

  lspci -vvv :
  00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition 
Audio Controller (rev 02)
  Subsystem: SigmaTel Device 7680
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Capabilities: [130] Root Complex Link 
  Kernel driver in use: HDA Intel
  Kernel modules: snd-hda-intel

  enclosed, alsa-info.sh output

  is there a way to cleanly get back to gnome 2.26 as the jaunty mixer
  was fully functional ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-lib/+bug/463589/+subscriptions

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


[Desktop-packages] [Bug 932428] Re: [Satellite Pro L40, Analog Devices AD1986A, Other Speaker, Internal] No sound at all

2019-02-16 Thread Paul White
Bug report did not expire due to bug watch
Reporter did not reply to comment #2
Assuming fixed as upstream commit specific to issue

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

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

Title:
  [Satellite Pro L40, Analog Devices AD1986A, Other Speaker, Internal]
  No sound at all

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  1
  Description:  Ubuntu 11.10
  Release:  11.10

  2
  W: Duplicate sources.list entry http://archive.canonical.com/ubuntu/ 
oneiric/partner i386 Packages 
(/var/lib/apt/lists/archive.canonical.com_ubuntu_dists_oneiric_partner_binary-i386_Packages)
  W: You may want to run apt-get update to correct these problems
  N: Unable to locate package pkgname

   apt-get update EXECUTED

  3
  Sound

  4
  No Sound

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1718 F pulseaudio
alan   6507 F audacity
   /dev/snd/pcmC0D0c:   alan   1718 F...m pulseaudio
   /dev/snd/pcmC0D0p:   alan   1718 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xff63c000 irq 43'
 Mixer name : 'Analog Devices AD1986A'
 Components : 'HDA:11d41986,1179ff40,00100500 
HDA:11c11040,11790001,00100200'
 Controls  : 16
 Simple ctrls  : 10
  Date: Tue Feb 14 23:19:03 2012
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_DevicesInUse:
   1718  6507  1718  1718  alan  F pulseaudio
alan  F audacity
   /dev/snd/pcmC0D0c:   alan  F...m pulseaudio
   /dev/snd/pcmC0D0p:   alan  F...m pulseaudio
  Symptom_Jack: Other Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite Pro L40, Analog Devices AD1986A, Other Speaker, Internal] 
No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (123 days ago)
  dmi.bios.date: 02/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.30
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Satellite Pro L40
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.30:bd02/29/2008:svnTOSHIBA:pnSatelliteProL40:pvrPSL43E-00L00NEN:rvnTOSHIBA:rnSatelliteProL40:rvr1.0:cvnTOSHIBA:ct10:cvr:
  dmi.product.name: Satellite Pro L40
  dmi.product.version: PSL43E-00L00NEN
  dmi.sys.vendor: TOSHIBA
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-02-10T22:36:02.832292

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

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


[Desktop-packages] [Bug 680807] Re: Pulseaudio destroys performance

2019-02-16 Thread Paul White
Bug report did not expire due to other bug task
No reply to request for information over 8 years ago
Marking "Invalid" to close

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

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

Title:
  Pulseaudio destroys performance

Status in Linux Mint:
  Triaged
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  After installing Linux Mint 10 32bit and Ubuntu 10.10 32bit I had the
  same problem:

  The desktop felt sluggish, even the terminal was unresponsive. Video
  playback (smplayer, vlc, youtube) stuttered and the system couldn't
  reboot or halt at all.

  After research I removed pulseaudio and everything worked fine
  afterwards.

  I used this info:
  
http://jechem.blogspot.com/2010/10/how-to-remove-pulseaudio-on-ubuntu-1010.html

  Attached is my system's lshw

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

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


[Desktop-packages] [Bug 474016] Re: Asus F5N built-in microphone too low to pick up any sound

2019-02-16 Thread Paul White
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011
Bug report did not expire due to bug watch
No reply to request for information
No comments from anyone affected for around 9 years 
Marking "Invalid" to close

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

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

Title:
  Asus F5N built-in microphone too low to pick up any sound

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  When using the system testing tool I cannot hear anything recorded
  through the built-in microphone.

  When I turn up the sensitivity in the sound preferences to the max it
  does seem to pick up sound, albeit with a lot of amplified static.

  The speakers are turned up and other sounds play normally (e.g. the
  logon sound). The microphone works OK in windows.

  Same thing applies to external microphone when connecting a headset.
  On top of this, the sound goes to headphones only when speakers
  (analog output) is selected in sound preferences. When I select analog
  headphones there is no sound. And I do use analog headset with normal
  microphone and headphone jacks.

  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC660-VD Analog [ALC660-VD Analog]
 Subdevices: 1/1 

  DistroRelease: Ubuntu 9.10
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  Uname: Linux 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 
x86_64 GNU/Linux

  ProblemType: Bug
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  onair242695 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfd778000 irq 20'
 Mixer name : 'Realtek ALC660-VD'
 Components : 'HDA:10ec0660,10431339,0011 
HDA:10573055,10431316,00100700'
 Controls  : 23
 Simple ctrls  : 15
  CheckboxCommand: alsa_record_playback
  CheckboxData: The sound is very low and can barely be heard against solid and 
loud noise.
  CheckboxDescription:
   Open the volume control application by right-clicking on the speaker icon in 
the panel and selecting "Sound Preferences".  Select the "Input" tab and choose 
any alternate (non-default) device(s).  Select the "Output" tab and choose any 
alternate (non-default) device(s).  When you are done, click the Test button, 
then speak into the microphone. After a few seconds, your speech will be played 
back to you.
   
   Вы услышали вашу воспроизведенную речь?
  CheckboxTest: alsa_record_playback_alternates
  Date: Wed Nov  4 13:14:57 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic x86_64

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

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


Re: [Desktop-packages] [Bug 1769126] Re: SIMPLE-SCAN crashes when set to photo scanning

2019-02-16 Thread Chris Rainey
@Forrest Voight:  Awesome write-up. Thanks!

On Sat, Feb 16, 2019 at 3:05 AM Forrest Voight 
wrote:

> I looked into this issue at length and posted a write-up here:
> http://forre.st/brother_printer
>
> The gist of it is that setting up a Brother printer with an invalid
> model name (e.g. "MFCL5900DW" instead of "MFC-L5900DW") can cause
> crashes in some cases (namely simple-scan in photo mode).
>
> Fix:
>
> * (optional) Check "/opt/brother/scanner/brscan4/brsanenetdevice4.cfg" to
> see if the configured device has an invalid model name (by
> cross-referencing with the output of "brsaneconfig4 -q")
> * Delete /opt/brother/scanner/brscan4/brsanenetdevice4.cfg
> * Re-add the scanner with a command similar to "brsaneconfig4 -a
> name=MFC-L5900DW model=MFC-L5900DW nodename=BRN3C2AF4738657"
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1769126
>
> Title:
>   SIMPLE-SCAN crashes when set to photo scanning
>
> Status in simple-scan package in Ubuntu:
>   Confirmed
>
> Bug description:
>   WHAT I EXPECTED TO HAPPEN
>   I expected to scan a photo and get it showing in Simple scan alongside
> the other pages scanned in text mode.
>
>   WHAT HAPPENS INSTEAD
>   Simple scan crashes when set to scan images. When scan button is
> pressed, the app seems to begin the scanning process, scanner takes the
> page (if on the ADF), the app shows as if beginning to scan and then
> suddenly disappears with no message shown.
>
>   However if the app is launched again, the app opens immediately
>   showing all pages scanned up to that moment (in text mode) except for
>   the newly scanned photo, as if the app was always there and had never
>   closed.
>
>   When set to scan text, it is ok, but page size is much larger than
>   actual sheet or flat-bed size (higher, actually, width is ok).
>
>
>   OS: Ubuntu 18.04LTS fresh install and updated
>   Sw centers sais: version 3.28.0-0ubuntu1
>   (no other OS on the computer)
>   Multi-function printer scanner: Brother MFC-J5330DW connected to the
> network (didn't try USB)
>   Computer: HP notebook 15-ay117ns with serial CND70308KK
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1769126/+subscriptions
>

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

Title:
  SIMPLE-SCAN crashes when set to photo scanning

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  WHAT I EXPECTED TO HAPPEN
  I expected to scan a photo and get it showing in Simple scan alongside the 
other pages scanned in text mode.

  WHAT HAPPENS INSTEAD
  Simple scan crashes when set to scan images. When scan button is pressed, the 
app seems to begin the scanning process, scanner takes the page (if on the 
ADF), the app shows as if beginning to scan and then suddenly disappears with 
no message shown.

  However if the app is launched again, the app opens immediately
  showing all pages scanned up to that moment (in text mode) except for
  the newly scanned photo, as if the app was always there and had never
  closed.

  When set to scan text, it is ok, but page size is much larger than
  actual sheet or flat-bed size (higher, actually, width is ok).

  
  OS: Ubuntu 18.04LTS fresh install and updated
  Sw centers sais: version 3.28.0-0ubuntu1
  (no other OS on the computer)
  Multi-function printer scanner: Brother MFC-J5330DW connected to the network 
(didn't try USB)
  Computer: HP notebook 15-ay117ns with serial CND70308KK

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

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


[Desktop-packages] [Bug 410429] Re: sound doesnot work hp6530s

2019-02-16 Thread Paul White
Further to comment #2, issue was fixed.

** Changed in: alsa-driver (Ubuntu)
 Assignee: vikas patel (vikaspatel111087) => (unassigned)

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

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

Title:
  sound doesnot work hp6530s

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
   i could hear sound in headphone  when i try aplay
  /usr/share/sounds/alsa/Noise.wav but  not in laptop speaker and  else
  any other sound doesnot work also in head phone too

  ProblemType: Bug
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dev3612 F mixer_applet2
dev5970 F gnome-volume-co
   /dev/snd/pcmC0D1p:   dev6161 F...m totem
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd890 irq 17'
 Mixer name : 'Analog Devices AD1984A'
 Components : 'HDA:11d4194a,103c30e8,00100400 
HDA:11c11040,103c1378,00100200'
 Controls  : 34
 Simple ctrls  : 20
  DistroRelease: Ubuntu 9.04
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-14-generic i686

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

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


[Desktop-packages] [Bug 1801494] Re: dock missing

2019-02-16 Thread Scott P
I'm now seeing this issue, after messing with my monitor cables.  I only
have a single monitor.  I was trying to get my DVI to work on my AMD
RX550 card - which will not display while logged in (but does at bios).

Both cables are currently plugged into the same monitor (diff ports of
course) in my attempt to switch from HDMI to DVI-D.

My ubuntu session was active in 18.04.1, and I only replugged the DVI
cable and wiggled the HDMI cable.

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

Title:
  dock missing

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

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

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

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


[Desktop-packages] [Bug 1789154] Re: [Aspire E5-574G, Realtek ALC255, Mic, Internal] No sound at all

2019-02-16 Thread tobson
*** This bug is a duplicate of bug 1523100 ***
https://bugs.launchpad.net/bugs/1523100

** This bug has been marked a duplicate of bug 1523100
   Alsa not detecting internal microphone [ALC255] (Realtek)

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

Title:
  [Aspire E5-574G, Realtek ALC255, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The mic is not working. I even tried my headphone mic, thinking it
  might be a hardware problem, but even that didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   anuj   1324 F...m pulseaudio
   /dev/snd/controlC0:  anuj   1324 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 27 10:38:36 2018
  InstallationDate: Installed on 2018-07-31 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   anuj   1324 F...m pulseaudio
   /dev/snd/controlC0:  gdm 929 F pulseaudio
anuj   1324 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [Aspire E5-574G, Realtek ALC255, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Zoro_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd08/28/2015:svnAcer:pnAspireE5-574G:pvrV1.03:rvnAcer:rnZoro_SL:rvrV1.03:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SKL
  dmi.product.name: Aspire E5-574G
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 1816247] Re: The "Show terminal menu bar" is not enabled

2019-02-16 Thread Paul White
*** This bug is a duplicate of bug 1816171 ***
https://bugs.launchpad.net/bugs/1816171

** This bug has been marked a duplicate of bug 1816171
   Show menubar by default in new terminals has no effect

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

Title:
  The "Show terminal menu bar" is not enabled

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Hi guys

  The "Show terminal menu bar is not enabled.
  Every time we open the terminal we have to manually inhabit the "Show menu 
bar"

  When we enter the edit option / preferences / shortcuts the "Hide and
  Show menu bar" option is not enabled, much less let us return to the
  default.

  As per attached image, I changed by mistake and can not revert, but
  before having changed the above situation already occurred.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-terminal 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: Sat Feb 16 13:48:38 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  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/1816247/+subscriptions

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


[Desktop-packages] [Bug 1816255] [NEW] Default sidebar icon screws up size of all icons

2019-02-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Ubuntu 18.04.1, gnome/X11 session.

All the icons in the activities panel (the left side-bar) are shrunk if
an app is run which does not specify an icon. Perhaps the default icon
is too large, or otherwise lacking in a way which causes the entire
side-bar to be re-scaled, shrinking the existing icons.

The example below usses qmlscene (a tool to run Qt-based apps), but I've
seen this with other apps which don't have a proper icon, such as the
citrix receiver.

Please see attached screenshots (before and after running a qmlscene
program)

STEPS TO REPRODUCE:

1. # Install Qt with qmlscene.  
   # I think this is enough:
sudo apt-get install qmlchooser qmlscene
   # But if not, then:
sudo apt-get install qtcreator qtbase5-dev

2. # create a trivial qml program
echo 'import QtQuick 2.9' >t.qml
echo 'import QtQuick.Controls 2.2' >>t.qml
echo 'ApplicationWindow { id: top; visible:true }' >>t.qml

3. qmlscene t.qml

RESULTS: The icons in the left sidebar contract to about half their
previous size.

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

-- 
Default sidebar icon screws up size of all icons
https://bugs.launchpad.net/bugs/1816255
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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


[Desktop-packages] [Bug 1816255] Re: Default sidebar icon screws up size of all icons

2019-02-16 Thread Dmitry Shachnev
** Package changed: gnome-panel (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Default sidebar icon screws up size of all icons

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04.1, gnome/X11 session.

  All the icons in the activities panel (the left side-bar) are shrunk
  if an app is run which does not specify an icon. Perhaps the default
  icon is too large, or otherwise lacking in a way which causes the
  entire side-bar to be re-scaled, shrinking the existing icons.

  The example below usses qmlscene (a tool to run Qt-based apps), but
  I've seen this with other apps which don't have a proper icon, such as
  the citrix receiver.

  Please see attached screenshots (before and after running a qmlscene
  program)

  STEPS TO REPRODUCE:

  1. # Install Qt with qmlscene.  
 # I think this is enough:
  sudo apt-get install qmlchooser qmlscene
 # But if not, then:
  sudo apt-get install qtcreator qtbase5-dev

  2. # create a trivial qml program
  echo 'import QtQuick 2.9' >t.qml
  echo 'import QtQuick.Controls 2.2' >>t.qml
  echo 'ApplicationWindow { id: top; visible:true }' >>t.qml

  3. qmlscene t.qml

  RESULTS: The icons in the left sidebar contract to about half their
  previous size.

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

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


[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-02-16 Thread Dmitrii Shcherbakov
nvidia-xconfig -generated xorg.conf looked like this
https://paste.ubuntu.com/p/4hRVzHmbJV/

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver 
cannot change properties on a disabled device
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:65
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1  - 
Power Button: is 

[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2019-02-16 Thread Dmitrii Shcherbakov
Had this with nvidia graphics drivers after installing and then removing
proprietary drivers downloaded from nvidia website. I could not log in
at all at first boot.

If you see nvidia modules loaded, make sure that you select an xorg
session on the login screen (not wayland) if you this control presented
to you.

lsmod| grep nvidia
nvidia_uvm794624  0
nvidia_drm 40960  13
nvidia_modeset   1040384  1 nvidia_drm
nvidia  17285120  653 nvidia_uvm,nvidia_modeset
ipmi_msghandler   102400  2 ipmi_devintf,nvidia
drm_kms_helper172032  2 nvidia_drm,i915
drm   458752  13 drm_kms_helper,nvidia_drm,i915

Alternatively, just set WaylandEnable to false (and restart gdm).

cat /etc/gdm3/custom.conf
# ...
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
# ...

I also suspect that /etc/X11/xorg.conf generated by nvidia-xconfig
(which I ran during driver installation from the website) was causing
issues.

Steps I performed from a VT session:

1) sudo apt purge 'nvidia*'
2) reboot
3) sudo rm /etc/X11/xorg.conf
4) sudo apt install nvidia-driver- nvidia-dkms- 
nvidia-settings nvidia-prime
5) reboot

I also have 11-nvidia-prime.conf file at /usr/share/X11/xorg.conf.d
which is generated by ubuntu-drivers-common:

cat /usr/share/X11/xorg.conf.d/11-nvidia-prime.conf

# DO NOT EDIT. AUTOMATICALLY GENERATED BY gpu-manager

Section "OutputClass"
Identifier "Nvidia Prime"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
Option "IgnoreDisplayDevices" "CRT"
Option "PrimaryGPU" "Yes"
ModulePath "/x86_64-linux-gnu/nvidia/xorg"
EndSection

dpkg -l | grep ubuntu-drivers-common
ii  ubuntu-drivers-common 1:0.5.2.2  

https://github.com/tseliot/ubuntu-drivers-
common/blob/bionic/share/hybrid/gpu-manager.c#L1359-L1375

** Attachment added: 
"nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5239177/+files/nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  

[Desktop-packages] [Bug 1815874] Re: [snap] Libreoffice contextual groups NotebookBar text cropping

2019-02-16 Thread Adolfo Jayme
** Summary changed:

- [snap] Libreoffice contextual groups menu text cropping
+ [snap] Libreoffice contextual groups NotebookBar text cropping

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

Title:
  [snap] Libreoffice contextual groups NotebookBar text cropping

Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice 6.0.2 shows truncated/cropped text on some options in the
  contextual grouped menu (notebook bar). See attached. Notice words
  like Italic, Underlined, Left, etc.

  This with 96dpi on 1920x1080p resolution, Enabled anti-aliasing with
  rgba/slight hinting in Plasma on Kubuntu 18.04 with the Breeze theme,
  and Sifr icon theme in LibreOffice.

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

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


[Desktop-packages] [Bug 1808880] Re: Got unknown content type text/html from reviews.ubuntu.com

2019-02-16 Thread corrado venturini
You're right: in Bionic I do not see the 'Write a Review' button for
snap packages.

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

Title:
  Got unknown content type text/html from reviews.ubuntu.com

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  see screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 18 01:25:58 2018
  InstallationDate: Installed on 2018-12-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1517956] Re: xdg-settings (used to) assume desktop files have exactly one Exec line

2019-02-16 Thread Bug Watch Updater
** Changed in: xdg-utils
   Status: Confirmed => Unknown

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

Title:
  xdg-settings (used to) assume desktop files have exactly one Exec line

Status in Xdg-utils:
  Unknown
Status in xdg-utils package in Ubuntu:
  Fix Committed

Bug description:
  In searching the desktop file for suitability, it scans for all lines
  that begin "Exec", and takes the result and packs it into a variable.

  If there is exactly one Exec line, this takes out a command name to
  test for existence, but when more than one matches, the program name
  is captured as "firstexecprog\nsecondexecprog\nthirdexecprog", and
  "which" doesn't know how to look up a program like that and the
  subsequent tests fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1517956/+subscriptions

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


[Desktop-packages] [Bug 480010] Re: Playback 10% too fast after resume

2019-02-16 Thread Paul White
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011
Bug report did not expire due to another bug task and bug watch
No reply to request for information almost 9 years ago
Marking "Invalid" to close

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

** Changed in: linux
   Status: New => Invalid

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

Title:
  Playback 10% too fast after resume

Status in Linux:
  Invalid
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  If the laptop hibernates or suspends and then resumes, there is an odd
  effect when starting (at least) mplayer video and rhythmbox (probably
  totem and VLC too).  Video and audio playback is noticeably too fast:
  a 5 min song will play in 4min 35sec of real-time, and about a major
  second out of tune.  I'm guessing the sound card clock is set wrongly
  on resume.  Running mpg321 (with default or -o oss or -o alsa09) will
  reset it so that playback is correct (mpg321 -o esd does not);
  restarting pulseaudio (not sure the best way to do this) doesn't seem
  to have any effect, but sudo alsa force-reload also restores to
  correct pitch/timing.

  Ubuntu 9.10 2.6.31-14-generic on Viglen Dossier laptop, soundcard:
  Intel 82801CA-ICH3 with AD1886

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel 
82801CA-ICH3]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer', '/dev/sequencer2'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'I82801CAICH3'/'Intel 82801CA-ICH3 with AD1886 at irq 5'
 Mixer name : 'Analog Devices AD1886'
 Components : 'AC97a:41445361'
 Controls  : 38
 Simple ctrls  : 24
  Date: Tue Nov 10 13:47:08 2009
  DistroRelease: Ubuntu 9.10
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Uname: Linux 2.6.31-14-generic i686

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

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


[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-02-16 Thread Nenad Antic
** Attachment added: "cat /procs/{pid}/smaps right after running for 2.5 hours"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+attachment/5239133/+files/xorg_smaps_%402hours.zip

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg package in Ubuntu:
  New

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  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
  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 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1816251] [NEW] HP Spectre x360 15" notebook: Battery drains off during the laptop sleep

2019-02-16 Thread M K
Public bug reported:

HP Spectre x360 15" notebook: Battery drains off during the laptop sleep
(with or without connected USB-C dock) and not possible to enable deep
sleep.

Enabling deep sleep results into failure: 
$ sudo echo deep > /sys/power/mem_sleep
bash: /sys/power/mem_sleep: Permission denied. 


Additionally also not possible to enable deep sleep by updating grub.

# editing /etc/default/grub
# Adding
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
sudo update-grub
# reboot laptop
# and still gets
$ cat /sys/power/mem_sleep
[s2idle]

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-power-manager 3.26.0-1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 16 18:22:25 2019
InstallationDate: Installed on 2019-02-13 (3 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  HP Spectre x360 15" notebook: Battery drains off during the laptop
  sleep

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

Bug description:
  HP Spectre x360 15" notebook: Battery drains off during the laptop
  sleep (with or without connected USB-C dock) and not possible to
  enable deep sleep.

  Enabling deep sleep results into failure: 
  $ sudo echo deep > /sys/power/mem_sleep
  bash: /sys/power/mem_sleep: Permission denied. 

  
  Additionally also not possible to enable deep sleep by updating grub.

  # editing /etc/default/grub
  # Adding
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
  sudo update-grub
  # reboot laptop
  # and still gets
  $ cat /sys/power/mem_sleep
  [s2idle]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-power-manager 3.26.0-1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:22:25 2019
  InstallationDate: Installed on 2019-02-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 525131] Re: cannot hear any sound

2019-02-16 Thread Paul White
Further to comment #3, issue was resolved.

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

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

Title:
  cannot hear any sound

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  i upgraded to Karmic Koala(Ubuntu 9.10) this morning and i am unable to hear 
any sound from my computer.
  i tried re-installing and upgrading ALSA Drivers. still nothing.
  not even system sounds are audible.
  tried varying all sound volume related controls.
  i am a newbie to Linux, hence point me in the right direction to rectify this.

  Thanks,
  Vikram

  ProblemType: Bug
  Architecture: amd64
  CheckboxSubmission: 151658acb686cf1cec6f622cbc364c9c
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sun Feb 21 08:32:59 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/totem
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: alsa-driver
  Uname: Linux 2.6.31-19-generic x86_64
  XsessionErrors:
   (gnome-settings-daemon:1789): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:1789): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:1846): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:1835): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

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

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


[Desktop-packages] [Bug 1036301] Re: lsmod indicates no sound modules

2019-02-16 Thread Paul White
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017
Bug report did not expire due to assignment
No reply to request for information over 6 years ago
Marking "Invalid" to close

** Changed in: alsa-driver (Ubuntu)
 Assignee: Denis REICHERT (denis-reichert) => (unassigned)

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

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

Title:
  lsmod indicates no sound modules

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  aplay -l says no sound card

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 août  13 18:23 seq
   crw-rw---T 1 root audio 116, 33 août  13 18:23 timer
  AplayDevices: aplay: device_list:252: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices: arecord: device_list:252: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Aug 13 18:26:01 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-V EVO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1702:bd12/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Desktop-packages] [Bug 1517956]

2019-02-16 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance: https://gitlab.freedesktop.org/xdg
/xdg-utils/issues/83.

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

Title:
  xdg-settings (used to) assume desktop files have exactly one Exec line

Status in Xdg-utils:
  Unknown
Status in xdg-utils package in Ubuntu:
  Fix Committed

Bug description:
  In searching the desktop file for suitability, it scans for all lines
  that begin "Exec", and takes the result and packs it into a variable.

  If there is exactly one Exec line, this takes out a command name to
  test for existence, but when more than one matches, the program name
  is captured as "firstexecprog\nsecondexecprog\nthirdexecprog", and
  "which" doesn't know how to look up a program like that and the
  subsequent tests fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1517956/+subscriptions

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


[Desktop-packages] [Bug 491425] Re: feedback coming from Macbook Pro speakers

2019-02-16 Thread Paul White
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011
Bug report did not expire due to another bug task
No reply to request for information nearly 9 years ago
Marking "Invalid" to close

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

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

Title:
  feedback coming from Macbook Pro speakers

Status in Mactel Support:
  New
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Hear a humming sound coming from laptop internal speakers.  When I
  change preferences on audio, the sound goes away for about 30 seconds,
  then returns.  Rather annoying.  Just installed ubuntu  9.10 on the
  bootcamp partitionm, macbook pro 2.2.

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ekuenzli   1794 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd840 irq 22'
 Mixer name : 'SigmaTel STAC9221 A1'
 Components : 'HDA:83847680,106b1e00,00103401'
 Controls  : 20
 Simple ctrls  : 12
  CheckboxCommand: alsa_record_playback
  CheckboxDescription:
   Open the volume control application by right-clicking on the speaker icon in 
the panel and selecting "Sound Preferences".  Select the "Input" tab and choose 
any alternate (non-default) device(s).  Select the "Output" tab and choose any 
alternate (non-default) device(s).  When you are done, click the Test button, 
then speak into the microphone. After a few seconds, your speech will be played 
back to you.
   
   Did you hear your speech played back?
  CheckboxTest: alsa_record_playback_alternates
  Date: Wed Dec  2 10:24:40 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic-pae
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-15-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/491425/+subscriptions

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


[Desktop-packages] [Bug 484576] Re: [9.10] macbook 2.1 sound jack outputs one channel only

2019-02-16 Thread Paul White
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011
Bug report did not expire due to another bug task
No reply to request for information in comment #28
No comments from anyone else affected for nearly 9 years
Marking "Invalid" to close

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

** Changed in: mactel-support
   Status: New => Invalid

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

Title:
  [9.10] macbook 2.1 sound jack outputs one channel only

Status in Mactel Support:
  Invalid
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 9.10
  After having fixed the problem everyone's having about not having any sound 
output jack at all (using alsamixer),
  now I have sound from the left channel only.
  If I do speaker-test it'll try Front Left only, unless I add -c2 to it, in 
which case it'll try Front right too but it will output no sound.

  Please let me know what kind of reports I should be sending to you,
  but this is just the ubuntu live cd (in a usb stick) pretty much out
  of the box on a macbook 2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/484576/+subscriptions

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


[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-02-16 Thread Nenad Antic
** Attachment added: "cat /procs/{pid}/smaps right after reboot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+attachment/5239130/+files/xorg_smaps_%40reboot.zip

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg package in Ubuntu:
  New

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  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
  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 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-02-16 Thread Nenad Antic
** Attachment added: "The corresponding Xorg process core dump (Note: 3.2 GB 
when expanded)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+attachment/5239134/+files/xorg.dump.7z

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

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg package in Ubuntu:
  New

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  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
  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 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-02-16 Thread Nenad Antic
-- 
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/1815693

Title:
  Kubuntu 18.10 Xorg severe memory leak

Status in xorg package in Ubuntu:
  New

Bug description:
  Suddenly sometimes during the past two weeks my kubuntu installation
  has started to freeze up. I can't remember what apt upgrade that
  caused it, and I have done several the last few days hoping for it to
  be resolved.

  I didn't know what was causing it as I hadn't made any other changes
  expect for the odd apt upgrade. Before that I had just finished a
  several weeks long session of intense work around the clock without
  having to reboot even once. Suddenly it is now freezing up within
  hours. Even without doing anything, just leaving the computer alone.
  However, yesterday I accidentally discovered that my RAM was filled
  up. More than filled up, even all swap was full. And before I could
  close anything down it froze up again.

  So TLDR; I have today logged the memory consumption while I was
  handling some bills and linked is a log of constantly increasing Xorg
  memory usage. So it goes until it chokes the machine and only a hard
  reboot is possible.

  My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see 
how the Xorg usage creeps up.
  https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0

  I should add that this bug seems specific to Kubuntu, and (I guess)
  associated with running under Virtualbox. I have another Ubuntu 18.04
  (i.e. not _K_ubuntu) running on bare metal and it is not having any
  problems.

  Please advise what additional information I should post to have this
  resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Feb 13 01:00:13 2019
  DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2015-10-22 (1209 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago)
  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
  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 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Desktop-packages] [Bug 1801494] Re: dock missing

2019-02-16 Thread Scott P
Also,  I have no customizations to the OS generally.  I am using the OS
video driver for amd.

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

Title:
  dock missing

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

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

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

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


[Desktop-packages] [Bug 1767817] Re: Full text search does not work

2019-02-16 Thread Mordi
Thatoo, see my previous comment #8 why this bug occurs.

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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


[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

2019-02-16 Thread Mark smith
Two network & volume indicators also on XFCE panel.
No change even after resetting the panel (xfce4-panel -r).
I guess two is better than none. ;-)

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

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

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

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  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 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+subscriptions

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


[Desktop-packages] [Bug 584529]

2019-02-16 Thread gds
Wayne, I don't see this problem doing these steps:

1. Make sure ff and tb both working OK, network wise
2. Switch off wifi and verify ff does not access anything.
3. Shutdown tb (all windows)
4. Start tb with wifi off
5. Switch wifi on
6. Verify ff working again, can access a page
7. In tb click "Get Mail". Tb check mails, no waiting, no messages, see 
immediate connections occur in wireshark.

Tried this on 2 systems with same result using 60.*.

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

Title:
  Thunderbird complains there is no connection on resume from suspend,
  when there is a connection

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  When I resume from suspend, network manager quickly re-establishes a
  WiFi internet connection.  With an active connection, I try to check
  my mail with Thunderbird, but it complains that it can't connect to
  the IMAP server.  This seems to happen after longer suspend periods
  because if I try to replicate the behaviour by quickly suspending and
  resuming (suspend of a few seconds), I get no warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.4+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  Architecture: amd64
  Date: Sun May 23 12:26:28 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100412)
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

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

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


[Desktop-packages] [Bug 1553637] Re: Cannot hide the toolbar

2019-02-16 Thread Paul White
Toolbar was removed in gedit 3.18 so the request is no longer valid.

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

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

Title:
  Cannot hide the toolbar

Status in gedit package in Ubuntu:
  Invalid

Bug description:
  The Gedit version included in Ubuntu Wily Werewolf allowed me to hide
  the toolbar, the version included in Xenial Xerus does not offer this.

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

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


[Desktop-packages] [Bug 1815752] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build

2019-02-16 Thread Jarno Suni
I do not see how signing itself would be the cause. That could be
tested, if there was linux-image-unsigned-4.4.0-143-generic available in
xenial-proposed. However, there are other changes in 4.4.0-143-generic
that might be the cause for incompatibility between the kernel and the
nvidia driver.

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

Title:
  nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed
  to build

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

Bug description:
  I installed new kernel from xenial-proposed and this happened.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.104-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog: root: clean, 318706/1281120 files, 2426738/512 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 4.4.0-143-generic
  Date: Wed Feb 13 12:18:21 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv-linux.h:2161:9:
 error: too many arguments to function ‘get_user_pages’
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (1179 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (970) killed by TERM signal
  PackageVersion: 340.104-0ubuntu0.16.04.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 13 12:57:38 2019
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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


[Desktop-packages] [Bug 770048] Re: Tab bar isn't needed when view/editing one file

2019-02-16 Thread Paul White
In recent versions of gedit the tab bar appears when a second file is
opened and is removed if all files except one are closed. Closing as
fixed.


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

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

Title:
  Tab bar isn't needed when view/editing one file

Status in gedit:
  Won't Fix
Status in gedit package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gedit

  When viewing or editing just one file, the tab created is simply a
  waste of space, as the same pertinent information is provided in the
  title bar.

  Gedit should have a behavior/toggle similar to the "Always show the tab bar" 
toggle in Mozilla's Firefox:
  "Always show the tab bar: If you're only viewing one web page in a Firefox 
window, the tab bar is not normally shown. Check this preference to always show 
the tab bar, including when only the Firefox window contains only one page."

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

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


[Desktop-packages] [Bug 1129842] Re: Usability. Need option "reset and clear" in context menu

2019-02-16 Thread Paul White
Upstream report https://bugzilla.gnome.org/show_bug.cgi?id=310915
requested this feature but was closed "RESOLVED WONTFIX" on 2014-01-20

** Bug watch added: GNOME Bug Tracker #310915
   https://bugzilla.gnome.org/show_bug.cgi?id=310915

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

Title:
  Usability. Need option "reset and clear" in context menu

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  All time I open context menu, look for clear and then go to window
  menu. Very frestrating.

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

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


Re: [Desktop-packages] [Bug 1715121] Re: cheese error message

2019-02-16 Thread emilram
thank you-I am using camorama instead .

On Fri, Feb 15, 2019 at 4:51 PM Sebastien Bacher 
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because your
> description didn't include enough information. You may find it helpful
> to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem.
>
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures.
>
> At a minimum, we need:
> 1. The specific steps or actions you took that caused you to encounter the
> problem.
> 2. The behavior you expected.
> 3. The behavior you actually encountered (in as much detail as possible).
> Thanks!
>
> ** Changed in: cheese (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: cheese (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1715121
>
> Title:
>   cheese error message
>
> Status in cheese package in Ubuntu:
>   Incomplete
>
> Bug description:
>   "there was an error playing video from webcam"
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: xorg 1:7.7+1ubuntu8.1
>   ProcVersionSignature: Ubuntu 4.4.0-94.117~14.04.1-generic 4.4.83
>   Uname: Linux 4.4.0-94-generic i686
>   ApportVersion: 2.14.1-0ubuntu3.25
>   Architecture: i386
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Tue Sep  5 13:26:57 2017
>   DistUpgraded: Fresh install
>   DistroCodename: trusty
>   DistroVariant: ubuntu
>   GraphicsCard:
>Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772]
> (rev 02) (prog-if 00 [VGA controller])
>  Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
>   InstallationDate: Installed on 2017-06-27 (69 days ago)
>   InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386
> (20150218.1)
>   MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic
> root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro splash quiet
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/24/2007
>   dmi.bios.vendor: Award Software International, Inc.
>   dmi.bios.version: F4
>   dmi.board.name: 945GCMX-S2
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.modalias:
> dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
>   dmi.product.name: 945GCMX-S2
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
>   version.libgl1-mesa-dri: libgl1-mesa-dri N/A
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core N/A
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>   xserver.bootTime: Tue Sep  5 13:24:20 2017
>   xserver.configfile: default
>   xserver.devices:
>inputPower Button KEYBOARD, id 6
>inputPower Button KEYBOARD, id 7
>inputSEMICCHIP Usb Mouse  MOUSE, id 8
>inputWebcam C170  KEYBOARD, id 9
>inputAT Translated Set 2 keyboard KEYBOARD, id 10
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id   12309
>vendor DEL
>   xserver.version: 2:1.18.3-1ubuntu2.3~trusty2
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1715121/+subscriptions
>

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

Title:
  cheese error message

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  "there was an error playing video from webcam"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-94.117~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-94-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Sep  

[Desktop-packages] [Bug 1504079] Re: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

2019-02-16 Thread Craig
Looks like this bug should be reported on Gitlab rather than Gnome
Bugzilla.  There are several tracker subprojects on Gitlab.  I'm
guessing this bug should be reported on one of:

https://gitlab.gnome.org/GNOME/tracker-miners
or,
https://gitlab.gnome.org/GNOME/tracker

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

Title:
  tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  i need

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: tracker-extract 1.4.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic i686
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Oct  8 16:04:40 2015
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-09-13 (25 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xad14eb08 :mov
(%eax),%eax
   PC (0xad14eb08) ok
   source "(%eax)" (0x007c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   gst_video_info_to_caps () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   avcodec_decode_video2 () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
  Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
  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/tracker/+bug/1504079/+subscriptions

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


[Desktop-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync

2019-02-16 Thread Florian Schwarz
As you proposed:
https://gitlab.gnome.org/GNOME/glib/issues/1688

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

Title:
  cifs - poor upload speed with nautilus compared to rsync

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with
  cifs. Copying an 8 GB file...

  Upload (local -> mounted)
  - Nautilus/Nemo -> 6 MB/s
  - rsync -> 50-60 MB/s

  Download performance is also strange, but not my biggest concern.
  Download (mounted -> local)
  - Nautilus/Nemo -> 90 MB/s
  - rsync -> 50-60 MB/s

  rsync command (upload):
  rsync --progress /home/me/file.iso /mnt/cifs_media/

  fstab entry:
  //nas/media /mnt/cifs_media cifs 
vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700
 0 0

  Any idea, why Nautilus is uploading up to 10 times more slowly than
  rsync, although both using the same cifs, os, hardware, network etc.?

  PS: Further info for bug report
  1) The release of Ubuntu: Ubuntu 18.04 LTS
  2) The version of the package: Nautilus 3.26.3
  3) What you expected to happen: At least same speed as with using rsync
  4) What happened instead: See above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1782535/+subscriptions

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


Re: [Desktop-packages] [Bug 1814949] Re: gnome-control-center refuses to open if you try to open the Details panels

2019-02-16 Thread Khairul Aizat Kamarudzzaman
Tested the fix in disco-proposed ...

so far so good not crashing when go to info in setting ... thanks !!
On Feb 16 2019, at 1:34 am, Sebastien Bacher  wrote:
> The fix is in disco-proposed, https://launchpad.net/ubuntu/+source
> /gnome-control-center/1:3.31.90-1ubuntu3
>
> ** Changed in: gnome-control-center (Ubuntu)
> Status: Triaged => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1814949
>
> Title:
> gnome-control-center refuses to open if you try to open the Details
> panels
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1814949/+subscriptions
>

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

Title:
  gnome-control-center refuses to open if you try to open the Details
  panels

Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Workaround
  ==
  Run this command in your terminal:
  gsettings reset org.gnome.ControlCenter last-panel

  and then avoid opening the Details panels

  Issue
  =
  If you try to open the Details panel, gnome-control-center will crash.
  It will then refuse to open.

  Upstream Bug Report
  ===
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285

  See also
  https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/387

  Original Bug Report
  ===
  Segmentation fault while trying to run via cli , the gnome setting doesn't 
working when click on setting menu

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.30.2-4ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 14:38:32 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-05-04 (643 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>:  mov
-0x8(%rdi),%rax
   PC (0x7f783f52232d) ok
   source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI___libc_free (mem=0x1) at malloc.c:3085
   g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: Upgraded to disco on 2018-11-06 (92 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-02-16 Thread Michael Weimann
I observed the same behaviour as Adrian S..

Selecting Intel keeps the Nvidia card powered and the fan spinning.
Installing and using bbswitch manually works. I can't make it working powering 
off the card at boot time :( Therefore I have to do it manually every time I 
boot my notebook.

MX150, Ubuntu 18.04.2

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

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

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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


[Desktop-packages] [Bug 1794033]

2019-02-16 Thread Mark-a-janes
Mesa CI reproduce these test failures immediately:

https://mesa-
ci.01.org/mesa_master/builds/15252/group/63a9f0ea7bb98050796b649e85481845

Builds have fairly recent kernels:

Linux otc-gfxtest-sklgt2-01 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1
(2018-12-22) x86_64 GNU/Linux

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Confirmed

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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


[Desktop-packages] [Bug 1799686] Re: Enable v4l2 hardware accelerated video decode for ARM devices

2019-02-16 Thread Adam Smith
** Summary changed:

- Enable v4l2 hardware accelerated video decode
+ Enable v4l2 hardware accelerated video decode for ARM devices

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

Title:
  Enable v4l2 hardware accelerated video decode for ARM devices

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium browser is capable of decoding video via v4l2 codecs.
  ChromeOS uses this on arm devices to achieve good performance.

  Patches to enable this in Linux can be found here
  
https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0
  and here
  
https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada

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

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


[Desktop-packages] [Bug 1760086] Re: simple-scan crashed with SIGSEGV in make_cache_block()

2019-02-16 Thread Forrest Voight
*** This bug is a duplicate of bug 1769126 ***
https://bugs.launchpad.net/bugs/1769126

(Reposted here because some people aren't subscribed to #1769126. Sorry
if you get a duplicate notification.)

I looked into this issue at length and posted a write-up here:
http://forre.st/brother_printer

The gist of it is that setting up a Brother printer with an invalid
model name (e.g. "MFCL5900DW" instead of "MFC-L5900DW") can cause
crashes in some cases (namely simple-scan in photo mode).

Fix:

* (optional) Check "/opt/brother/scanner/brscan4/brsanenetdevice4.cfg" to see 
if the configured device has an invalid model name (by cross-referencing with 
the output of "brsaneconfig4 -q")
* Delete /opt/brother/scanner/brscan4/brsanenetdevice4.cfg
* Re-add the scanner with a command similar to "brsaneconfig4 -a 
name=MFC-L5900DW model=MFC-L5900DW nodename=BRN3C2AF4738657"

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

Title:
  simple-scan crashed with SIGSEGV in make_cache_block()

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Segfaults when trying to scan a document in Photo mode. Text mode
  works.

  Scanner is a all-in-one Brother J4625DW.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Mar 30 13:58:18 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/simple-scan
  MachineType: LENOVO 2353CTO
  ProcCmdline: simple-scan
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x7ffb702a214c : movzbl 
0x3ec(%rax),%eax
   PC (0x7ffb702a214c) ok
   source "0x3ec(%rax)" (0x03ec) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: simple-scan
  StacktraceTop:
   make_cache_block () from /usr/lib/x86_64-linux-gnu/sane/libsane-brother4.so.1
   read_scanned_data () from 
/usr/lib/x86_64-linux-gnu/sane/libsane-brother4.so.1
   PageScan () from /usr/lib/x86_64-linux-gnu/sane/libsane-brother4.so.1
   sane_brother4_read () from 
/usr/lib/x86_64-linux-gnu/sane/libsane-brother4.so.1
   ?? ()
  Title: simple-scan crashed with SIGSEGV in make_cache_block()
  UpgradeStatus: Upgraded to bionic on 2018-01-22 (67 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2353CTO
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1799686] Re: Enable v4l2 hardware accelerated video decode for ARM devices

2019-02-16 Thread Adam Smith
I asked on the pi forum if they could help with the upstream bug report
https://www.raspberrypi.org/forums/viewtopic.php?f=66=233552 .  I like
the pi, but the people that make it are obnoxious.  They are not going
to help.

I posted some more patches from endless os in that thread.

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

Title:
  Enable v4l2 hardware accelerated video decode for ARM devices

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium browser is capable of decoding video via v4l2 codecs.
  ChromeOS uses this on arm devices to achieve good performance.

  Patches to enable this in Linux can be found here
  
https://github.com/Igalia/chromium/commit/58cca7607828bbadc4e154dde36e9c96469ba2d0
  and here
  
https://github.com/Igalia/chromium/commit/c607620917eee5ff646b2daf304f6f133fb24ada

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

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


[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

2019-02-16 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-intel (Fedora)
   Status: Incomplete => Confirmed

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Confirmed

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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


[Desktop-packages] [Bug 1690006] Re: Firefox fails acid3.acidtests.org

2019-02-16 Thread Bug Watch Updater
Launchpad has imported 35 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1311329.

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


On 2016-10-19T12:40:02+00:00 Bill Gianopoulos wrote:

Under both Aurora and nightly ACID3 test 35 is failing with this error:

Test 35 failed: expected '0' but got '1' - root element, with no parent
node, claims to be a :first-child

Current relase and Beta are NOT affected.

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


On 2016-10-19T13:02:07+00:00 Bill Gianopoulos wrote:

This fails under WIndows as well.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/1


On 2016-10-19T14:41:19+00:00 Mats-l wrote:

Is this an intentional change from bug 1300374?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/2


On 2016-10-19T14:46:30+00:00 Bill Gianopoulos wrote:

(In reply to Mats Palmgren (:mats) from comment #2)
> Is this an intentional change from bug 1300374?

If this is an intentional change, and the reasons for the change are
legitimate, then we should ask to have the test changed.  That said,
Google Chrome still gets 100% on this test.  I will try backing out that
change to see how it impacts the test results.

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


On 2016-10-19T15:14:15+00:00 Bill Gianopoulos wrote:

I have verified that restoring this code:

if (!parent) {
return false;
}

from edgeChildMatches

which was removed by the patch for bug 1300374 does restore the 100%
result in the Acid3 test.

I also wonder why this was not known , if it was not, because I thought
we included the Acid3 test in the our test suite.

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


On 2016-10-19T15:20:58+00:00 B-emilio wrote:

Yes, this is intentional, since the spec changed. If it breaks stuff we
can of course restore the old behavior (though I won't say Acid3 is
representative of actual content, and this is the first report related
to that bug AFAIK).

I think we should get the test changed, but I don't know how feasible is
it.

Also, no, I don't think we include Acid3 in our test suite (otherwise
that patch would've never landed).

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


On 2016-10-19T15:51:11+00:00 Ms2ger wrote:

Fixing Acid3 has historically not been an issue. I asked Hixie
.

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


On 2016-10-21T02:29:02+00:00 Bmo-7 wrote:

(In reply to Emilio Cobos Álvarez [:emilio] from comment #5)
> I think we should get the test changed, but I don't know how feasible is it.
Will this change cause any webcompat issue here between Blink and us ? 
Following the spec is correct but still concerned about breakage of any 
websites due to compatibility issues.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/7


On 2016-10-21T08:52:43+00:00 B-emilio wrote:

Hi Astley,

As I said before, I don't think Acid3 is representative of actual
content, so I don't think sites rely on this.

That being said, yes, it's a difference, but this is the first report
related to that change in two months, and it's in a fairly artificial
test.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/8


On 2016-10-24T13:35:11+00:00 Bmo-7 wrote:

So could we change to Tech Evangelism team to help the fix on ACID3 test
cases?

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


On 2016-10-24T16:10:48+00:00 Ms2ger wrote:

No need. I'll try to poke again this week.

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


On 2016-10-24T16:18:05+00:00 Bill Gianopoulos wrote:

Problem 

[Desktop-packages] [Bug 1769126] Re: SIMPLE-SCAN crashes when set to photo scanning

2019-02-16 Thread Forrest Voight
I looked into this issue at length and posted a write-up here:
http://forre.st/brother_printer

The gist of it is that setting up a Brother printer with an invalid
model name (e.g. "MFCL5900DW" instead of "MFC-L5900DW") can cause
crashes in some cases (namely simple-scan in photo mode).

Fix:

* (optional) Check "/opt/brother/scanner/brscan4/brsanenetdevice4.cfg" to see 
if the configured device has an invalid model name (by cross-referencing with 
the output of "brsaneconfig4 -q")
* Delete /opt/brother/scanner/brscan4/brsanenetdevice4.cfg
* Re-add the scanner with a command similar to "brsaneconfig4 -a 
name=MFC-L5900DW model=MFC-L5900DW nodename=BRN3C2AF4738657"

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

Title:
  SIMPLE-SCAN crashes when set to photo scanning

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  WHAT I EXPECTED TO HAPPEN
  I expected to scan a photo and get it showing in Simple scan alongside the 
other pages scanned in text mode.

  WHAT HAPPENS INSTEAD
  Simple scan crashes when set to scan images. When scan button is pressed, the 
app seems to begin the scanning process, scanner takes the page (if on the 
ADF), the app shows as if beginning to scan and then suddenly disappears with 
no message shown.

  However if the app is launched again, the app opens immediately
  showing all pages scanned up to that moment (in text mode) except for
  the newly scanned photo, as if the app was always there and had never
  closed.

  When set to scan text, it is ok, but page size is much larger than
  actual sheet or flat-bed size (higher, actually, width is ok).

  
  OS: Ubuntu 18.04LTS fresh install and updated
  Sw centers sais: version 3.28.0-0ubuntu1
  (no other OS on the computer)
  Multi-function printer scanner: Brother MFC-J5330DW connected to the network 
(didn't try USB)
  Computer: HP notebook 15-ay117ns with serial CND70308KK

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

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


[Desktop-packages] [Bug 1751479] Re: Firefox always show download "Failed" even if it downloads successfully

2019-02-16 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1440679.

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


On 2018-02-23T14:55:26+00:00 Justin Yang wrote:

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux aarch64; rv:58.0) Gecko/20100101 
Firefox/58.0
Build ID: 20180208174849

Steps to reproduce:

Platform: 
Linux

Architecture: 
Arm64 (aarch64)

Distro: 
Ubuntu xenial and ArchLinuxArm

Desktop Environment: 
Xfce 4.12 and Mate 1.20

Hardware: 
Chromebook plus with crouton (a Ubuntu Xenial chroot) installed, and I also 
have ArchlinuxArm installed on my USB disk, which can be booted in this 
Chromebook.

What I did:
I want to download files in Firefox. Just open any website, click "Download" 
link.


Actual results:

I can not see my downloading items on browser panel, it just says "No
downloads for this session". What's more, if I click  "Show all
downloads", I can see my downloading items whose status is "Failed".
However, I can confirm it's downloading background successfully, and the
downloaded file appears on my computer. I tried to remove my profile,
say, the ".mozilla" folder, and downloaded again, but nothing improved.


Expected results:

It should download successfully. I just downgrade my Firefox to 57.x,
everything is fine, and this downloading issue is gone.

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


On 2018-02-23T16:30:27+00:00 Gingerbread-man-2 wrote:

(In reply to Justin Yang from comment #0)
> I just downgrade my Firefox to 57.x, everything is fine, and this downloading 
> issue is gone.

It would help if you could find the regression range.
mozregression --good 57 --bad 58
https://mozilla.github.io/mozregression/documentation/usage.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1751479/comments/1


On 2018-02-24T15:39:40+00:00 Justin Yang wrote:

(In reply to Gingerbread Man from comment #1)
> (In reply to Justin Yang from comment #0)
> > I just downgrade my Firefox to 57.x, everything is fine, and this 
> > downloading issue is gone.
> 
> It would help if you could find the regression range.
> mozregression --good 57 --bad 58
> https://mozilla.github.io/mozregression/documentation/usage.html

Well, I tried, but it seems that mozregression only support x86
platform, while my laptop is an Arm64 machine:(

See my mozregression output here:
https://imgur.com/13pqToLl.png

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1751479/comments/2


On 2018-02-25T18:07:02+00:00 Justin Yang wrote:

Well, I just find that my downloading item will appear on the browser
panel if it's in Private window, but not in normal window.

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


On 2018-03-05T16:55:16+00:00 Paolo-mozmail-q wrote:

We don't need to track this as a regression because, as far as I know,
this isn't a supported environment.

Comment 3 reminds me of a similar symptom that was caused by a compiler
issue in the interface between JS and C++. To understand what caused the
problem this time, even if mozregression doesn't work, you can still
bisect manually by building different Firefox source revisions locally,
remembering that the issue may also be in the compiler rather than the
code being built. Hope this helps!

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


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

** Changed in: firefox
   Importance: Unknown => Medium

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

Title:
   Firefox always show download "Failed" even if it downloads
  successfully

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  
  Firefox version: 
Installed: 58.0.2+build1-0ubuntu0.16.04.1
Candidate: 58.0.2+build1-0ubuntu0.16.04.1
Version table:
   *** 58.0.2+build1-0ubuntu0.16.04.1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-updates/main arm64 Packages
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports 
xenial-security/main arm64 Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial/main 
arm64 Packages

  
  Architecture: 
  Arm64 

[Desktop-packages] [Bug 1297697] Re: Allow regexp in Search/Replace

2019-02-16 Thread Paul White
Regular expressions can be enabled in the "Find & Replace" dialog
Checked in Ubuntu 18.04 but probably has existed for some time

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

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

Title:
  Allow regexp in Search/Replace

Status in gedit package in Ubuntu:
  Fix Released

Bug description:
  Hi all!
  To allow easy tab, spaces, EOL etc. search/replaces in gedit, it would be 
quite useful to add the ability to wok with regular expressions (minimal set: 
\r \n \d \D \s \t \w \W).
  Thank you!
  --
  A.Angelo

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

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


[Desktop-packages] [Bug 683725] Re: When I format an usb key, after remount it opens the empty device twice.

2019-02-16 Thread Paul White
Further to comment #10, closing Papercut task.

** Changed in: hundredpapercuts
   Status: Confirmed => Invalid

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

Title:
  When I format an usb key, after remount it opens the empty device
  twice.

Status in One Hundred Papercuts:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in parted package in Ubuntu:
  Invalid

Bug description:
  When I plug an usb device and I format it through right click format, after 
the task is done, it remounts the device and open the empty device in nautilus 
twice. 
  It should open only once.
  It could not open at all because if we want to use the usb key to run "create 
a startup disk" it is no use and if we need to put files in it, we only have to 
double click the icon on the desktop to open the device.

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

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


[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

2019-02-16 Thread Michael Weimann
This still happens after the 18.04.2 update.
My card is a MX150.

I have to power off the card by bbswitch every time I boot my laptop.

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

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

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


[Desktop-packages] [Bug 1816231] [NEW] There is a constant screen flickereing.

2019-02-16 Thread Azhar Majeed
Public bug reported:

I have installed the 18.04.2 lts version. I have a basic intel graphics card
It says unable to locate package pkgname when I type apt-cache policy pkgname. 
I think it's a problem with the xorg file. not sure.
When the mouse tracker is moving there does'nt seem to be a problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 16 18:06:57 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad]
InstallationDate: Installed on 2019-02-16 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: ASUSTeK COMPUTER INC. X555LAB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef09309f-b8f6-4d98-9c90-7b08ac5e2392 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555LAB.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555LAB
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.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555LAB
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  There is a constant screen flickereing.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed the 18.04.2 lts version. I have a basic intel graphics card
  It says unable to locate package pkgname when I type apt-cache policy 
pkgname. I think it's a problem with the xorg file. not sure.
  When the mouse tracker is moving there does'nt seem to be a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 18:06:57 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad]
  InstallationDate: Installed on 2019-02-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef09309f-b8f6-4d98-9c90-7b08ac5e2392 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  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.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  

[Desktop-packages] [Bug 1213354] Re: Add bookmark to Ubuntu Forums in Firefox default

2019-02-16 Thread Paul White
*** This bug is a duplicate of bug 602265 ***
https://bugs.launchpad.net/bugs/602265

** This bug has been marked a duplicate of bug 602265
   The defaut firefox bookmarks could do with updating.

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

Title:
  Add bookmark to Ubuntu Forums in Firefox default

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  When a new Firefox profile is created in Saucy, it includes a list of "Ubuntu 
and Free Software links" by default.  That
  list includes a link to Launchpad but not to the Ubuntu Forums.  Launchpad is 
for bugs not for getting help and there is nothing directly where users can get 
help, beginner or otherwise.  Adding a link to the Forums would help the very 
new users find online help.  

  The default bookmarks list of  "Ubuntu and Free Software links" should
  include a link to Ubuntu Forums (http://www.ubuntuforums.org/)
  labelled as "Community Support"

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: firefox 23.0~b10+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lars   1392 F pulseaudio
  BuildID: 20130801095339
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Channel: Unavailable
  CurrentDmesg:
   [   24.924859] Adding 246572k swap on /dev/zram1.  Priority:5 extents:1 
across:246572k SSFS
   [   27.488922] sky2 :01:00.0 eth0: Link is up at 100 Mbps, full duplex, 
flow control rx
   [   27.488962] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   55.452676] init: mysql post-start process (1002) terminated with status 1
  Date: Sat Aug 17 14:33:46 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-09 (7 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64+mac 
(20130808)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static 
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.36  metric 1
  MarkForUpload: True
  Plugins:
   DivX Browser Plug-In - /usr/lib/mozilla/plugins/gecko-mediaplayer-dvx.so 
(gecko-mediaplayer)
   RealPlayer 9 - /usr/lib/mozilla/plugins/gecko-mediaplayer-rm.so 
(gecko-mediaplayer)
   Windows Media Player Plug-in - 
/usr/lib/mozilla/plugins/gecko-mediaplayer-wmp.so (gecko-mediaplayer)
   QuickTime Plug-in 7.6.9 - /usr/lib/mozilla/plugins/gecko-mediaplayer-qt.so 
(gecko-mediaplayer)
   mplayerplug-in is now gecko-mediaplayer 1.0.8 - 
/usr/lib/mozilla/plugins/gecko-mediaplayer.so (gecko-mediaplayer)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=23.0/20130801095339 (In use)
  RelatedPackageVersions: gecko-mediaplayer 1.0.8-1ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 06/28/07
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM21.88Z.009A.B00.0706281359
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4208EAA
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 4
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4208EAA
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM21.88Z.009A.B00.0706281359:bd06/28/07:svnAppleInc.:pnMacmini2,1:pvr1.0:rvnAppleInc.:rnMac-F4208EAA:rvrPVT:cvnAppleInc.:ct4:cvrMac-F4208EAA:
  dmi.product.name: Macmini2,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Desktop-packages] [Bug 1791307] Re: [snap] GTK theme doesn't match the host system

2019-02-16 Thread bwat47
The chromium snap is core18 now, and if anything the theming is even
worse now. It seems to only partially respect the system theme, and has
bugs like white text on white background, instead of properly respecting
yaru's theming. I attached a screenshot


** Attachment added: "core-18-themeing.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1791307/+attachment/5239088/+files/core-18-themeing.png

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

Title:
  [snap] GTK theme doesn't match the host system

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  The GTK theme of the chrome and file open/save dialogs doesn't match
  the theme on the host system.

  See attached screenshots.

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

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


[Desktop-packages] [Bug 1816043] Re: libreoffice snap package not displaying all unicode emojis

2019-02-16 Thread Adolfo Jayme
Have you installed an emoji font to ~/.fonts? In that case, LO won’t
read it until bug 1703638 is fixed.

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

Title:
  libreoffice snap package not displaying all unicode emojis

Status in libreoffice package in Ubuntu:
  New

Bug description:
  libreoffice 6.2 snap package is not displaying all unicode emojis,
  while the *.deb download from libreoffice.org is displaying them all.
  tested in calc & writer.

  Talking about these particular emojis:

     ⏳ ⚠

  See attachment for comparison between current snap and deb package.

  Using Ubuntu 18.04.

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

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


[Desktop-packages] [Bug 408060] Re: Problem on playing any 3gp file

2019-02-16 Thread Paul White
Bug report did not expire due to assignment
No reply to request for information
No comments for around 9 years 
Marking "Invalid" to close

** Changed in: alsa-driver (Ubuntu)
 Assignee: Sanu (sanucholayil) => (unassigned)

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

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

Title:
  Problem on playing any 3gp file

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  While playing any 3gp file on TOTEM player the player searches for AMR 
Decoder which in unable to find. It says in a dialogue box thatn "no suitable 
plugin is found".
  what will I do now?

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

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


[Desktop-packages] [Bug 381428] Re: jaunty jackalope audio driver for HDA NVidia, ALC1200 Analog, is not working as it should

2019-02-16 Thread Paul White
Bug report did not expire due to assignment
No reply to request for information
No comments for around 9 years 
Marking "Invalid" to close

** Changed in: alsa-driver (Ubuntu)
 Assignee: Pettan (pettannilsson) => (unassigned)

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

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

Title:
  jaunty jackalope audio driver for HDA NVidia, ALC1200 Analog, is not
  working as it should

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  my speaker hum while playing a video file

  ProblemType: Bug
  .etc.asound.conf:
   
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manzur 3745 F mixer_applet2
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 21'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,103c2a6d,00100101'
 Controls  : 34
 Simple ctrls  : 20
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.18.dfsg-1ubuntu8
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Uname: Linux 2.6.28-11-generic x86_64

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

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