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

[GrzesiekC]

Intel HD Graphics 520 - Internal

-- 
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 tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero 

[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze

[Daniel van Vugt]

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

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

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/907
+ 
+ ---
+ 
  I am using 18.04 and sometimes, whatever I type does not work. It is as
  if there is no keyboard connected while I have my laptop keyboard and an
  external keyboard connected to the machine. I even enabled On Screen
  Keyboard and tried to type through it. Same result.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1807056

Title:
  Occasional Keyboard freeze

Status in gnome-shell package in Ubuntu:
  New

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

  ---

  I am using 18.04 and sometimes, whatever I type does not work. It is
  as if there is no keyboard connected while I have my laptop keyboard
  and an external keyboard connected to the machine. I even enabled On
  Screen Keyboard and tried to type through it. Same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Pavlushka]

Is all the affected one's have external graphics card and made any
switch from external to integrated or from external to integrated then
back or any kind of switch between external and integrated Graphics
Cards?

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

[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze

[Dilip]

1. Once did try when I posted this in AskUbuntu. That was the first
suggestion I got. I posted this on Discourse.Ubuntu but the thread got
locked, but still got a like after one month of lock. In the It's Foss
Community where I tried to seek help, there was someone who said it
happens to him/her as well.

I will try without extensions once more. I am more of less sure that is
not the case.

2. Yes, I used mouse to click on the dash search and when I typed, it
worked.

3. Ok, I will see.

4. Done :)

https://gitlab.gnome.org/GNOME/gnome-shell/issues/907

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

Title:
  Occasional Keyboard freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am using 18.04 and sometimes, whatever I type does not work. It is
  as if there is no keyboard connected while I have my laptop keyboard
  and an external keyboard connected to the machine. I even enabled On
  Screen Keyboard and tried to type through it. Same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 981058] Re: Firefox freezes constantly while scrolling or using menus

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox freezes constantly while scrolling or using menus

Status in Mozilla Thunderbird:
  Incomplete
Status in firefox package in Ubuntu:
  Expired

Bug description:
  When I scroll from top to bottom in any page, Firefox using 1 cpu core
  100%. Also it can not scroll smoothly, freezes are happening. This
  freezes are exists everywhere in firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 11.0+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic-pae 3.0.22
  Uname: Linux 3.0.0-17-generic-pae i686
  NonfreeKernelModules: fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  muhammed   1970 F pulseaudio
   /dev/snd/controlC0:  muhammed   1970 F pulseaudio
  BuildID: 20120310010446
  CRDA: Error: [Errno 2] Böyle bir dosya ya da dizin yok
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf880 irq 42'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,17aa400c,0011'
 Controls  : 22
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xcfedc000 irq 43'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: release
  Date: Fri Apr 13 20:41:21 2012
  DefaultProfileIncompatibleExtensions:
   Console² - ID={1280606b-2510-4fe0-97ef-9b5a22eafe80}, Version=0.9, 
minVersion=1.9a7, maxVersion=11.0a1, Location=app-profile, Type=extension, 
Active=Yes
   FlashGot - ID={19503e42-ca3c-4c27-b1e2-9cdb2170ee34}, Version=1.4.1, 
minVersion=1.9a3, maxVersion=1.9.*, Location=app-profile, Type=extension, 
Active=Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  IpRoute:
   default via 10.64.64.64 dev ppp0  proto static 
   10.64.64.64 dev ppp0  proto kernel  scope link  src 176.54.255.205 
   169.254.0.0/16 dev ppp0  scope link  metric 1000 
   172.16.36.0/24 dev vmnet1  proto kernel  scope link  src 172.16.36.1 
   172.16.109.0/24 dev vmnet8  proto kernel  scope link  src 172.16.109.1
  Profiles:
   Profile0 - LastVersion=11.0/20120310010446
   Profile1 (Default) - LastVersion=11.0/20120310010446 (Running)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3FCN19WW
  dmi.board.name: KL3
  dmi.board.vendor: LENOVO
  dmi.board.version: Rev 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr3FCN19WW:bd02/11/2011:svnLENOVO:pnIdeaPadY560p:pvrRev1.0:rvnLENOVO:rnKL3:rvrRev1.0:cvnLENOVO:ct10:cvrRev1.0:
  dmi.product.name: IdeaPad Y560p
  dmi.product.version: Rev 1.0
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 988346] Re: opening multiple tabs at one time blocks everything

[Launchpad Bug Tracker]

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

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

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

Title:
  opening multiple tabs at one time blocks everything

Status in firefox package in Ubuntu:
  Expired

Bug description:
  opening multiple tabs at once blocks firefox for several minutes, afterwards 
everything seem to be o.k.
  very annoying as this happens every time when I try to open several tabs
  other open non firefox windows seems to be affected in the same way but not 
as long in time

  Ubuntu 11.10 (oneiric)
  gnome 2.32.1 in Sysinfo 0.7 resp. gnome 3.2.1 in system monitor 3.2.1
  Kernel 3.0.0-19-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 11.0+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
  Uname: Linux 3.0.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  walter-oswald   1616 F pulseaudio
   /dev/snd/controlC0:  walter-oswald   1616 F pulseaudio
  BuildID: 20120310010316
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe97c000 irq 25'
 Mixer name : 'Nvidia GPU 1c HDMI/DP'
 Components : 'HDA:10de001c,104383a0,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'VT82xx'/'HDA VIA VT82xx at 0xfeafc000 irq 17'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,18491e01,0011'
 Controls  : 33
 Simple ctrls  : 18
  Channel: release
  Date: Wed Apr 25 15:52:50 2012
  ForcedLayersAccel: False
  InstallationMedia: Ubuntu-Studio 11.04 "Natty Narwhal" - Release amd64 
(20110426.1)
  IpRoute:
   default via 192.168.178.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.20  
metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=11.0/20120310010316 (Running)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: 4CoreDual-VSTA
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd12/11/2006:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn4CoreDual-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 952725] Re: Kubuntu 12.04 mime types are missing or not working with Firefox

[Launchpad Bug Tracker]

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

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

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

Title:
  Kubuntu 12.04 mime types are missing or not working with Firefox

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Sorry I don't have any more info, but I feel I need to alert someone
  that mime types are not working in Kubuntu 12.04 beta 1 Firefox.

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

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

[Desktop-packages] [Bug 1033532] Re: Won't load pages. Sits "waiting for example.com"

[Launchpad Bug Tracker]

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

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

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

Title:
  Won't load pages. Sits "waiting for example.com"

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Firefox on the same machine, at the same time, has no problems
  accessing webpages. Chromium has a not-quite-every-time habit of
  hanging, with the twirly indicator going backwards, saying "Waiting
  for example.com". It will sit like that for minutes at a time,
  sometimes you get a page loaded, sometimes not.

  I know that it is not the webpage in question because (A) it can
  happen on any site and (B) some of the sites are mine, so I have
  monitored the server load at the time and not observed a problem.

  However, what is interesting is that I can click a link in Chromium,
  go to my SSH terminal for the server with tail --follow access.log
  running, and see that the request is not actually being received
  (until it is, at which point, Chromium receives + renders the page at
  normal speed).

  So DNS? I've put the test site in my hosts file, to eliminate this
  one. Still the problem exhibits.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  Date: Mon Aug  6 15:35:03 2012
  Desktop-Session:
   DESKTOP_SESSION = gnome-shell
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-shell:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/gnome-shell:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""

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

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

[Desktop-packages] [Bug 955759] Re: firefox fades and response gets delayed

[Launchpad Bug Tracker]

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

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

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

Title:
  firefox fades and  response gets delayed

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox fades and stops responding for some time and starts again.
  Some times the system freezes due to firefox. I was earlier thought it
  is due to UNITY but it is due to firefox. There is not such problem
  with either Chrome or Opera

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 10.0.2+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20
  Uname: Linux 3.0.0-16-generic-pae i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  moorthyvoonna   4596 F pulseaudio
  BuildID: 20120216101208
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7ef4000 irq 42'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0892,10438436,00100302 
HDA:80862804,80860101,0010'
 Controls  : 39
 Simple ctrls  : 21
  Channel: release
  Date: Thu Mar 15 12:32:08 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Profiles: Profile0 (Default) - LastVersion=10.0.2/20120216101208 (Running)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2012-01-23 (51 days ago)
  dmi.bios.date: 01/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1709
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1709:bd01/04/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 981024] Re: colors on video are wrong

[Launchpad Bug Tracker]

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

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

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

Title:
  colors on video are wrong

Status in firefox package in Ubuntu:
  Expired

Bug description:
  when I try to watch a video, the colors are wrong, people are blue

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 11.0+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic-pae 3.0.22
  Uname: Linux 3.0.0-17-generic-pae i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valentina-bilesimo   1564 F pulseaudio
  BuildID: 20120310010446
  CRDA: Error: [Errno 2] File o directory non esistente
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf350 irq 46'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10250121,00100101 
HDA:14f12c06,10250121,0010'
 Controls  : 24
 Simple ctrls  : 14
  Channel: release
  Date: Fri Apr 13 20:08:18 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Novell Moonlight - ID=moonli...@novell.com, 
Version=3.99.0.3, minVersion=1.5, maxVersion=4.0.*, Location=app-profile, 
Type=extension, Active=Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.100  metric 
1 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.102  
metric 2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=11.0/20120310010446 (Running)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3807
  dmi.board.name: Chapala
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3807:bd01/15/2008:svnAcer,inc.:pnAspire5920G:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 5920G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

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

[Desktop-packages] [Bug 985114] Re: many issues in this version - having troble with facebook and google analytics

[Launchpad Bug Tracker]

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

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

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

Title:
  many issues in this version - having troble with facebook and google
  analytics

Status in firefox package in Ubuntu:
  Expired

Bug description:
  i can not scroll more then one page on Facebook and cant see graphs on
  google analytics old version

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 11.0+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic-pae 3.0.22
  Uname: Linux 3.0.0-17-generic-pae i686
  AddonCompatCheckDisabled: True
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sumit  2358 F pulseaudio
  BuildID: 20120310010446
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xb440 irq 42'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0272,10250487,0011 
HDA:80862804,80860101,0010'
 Controls  : 24
 Simple ctrls  : 13
  Channel: release
  Date: Wed Apr 18 23:30:21 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Easiest YouTube Video Downloader - 
ID=manishjain9@hotmail.com_easiestyoutube, Version=2.7, minVersion=3.0, 
maxVersion=9.0a1, Location=app-profile, Type=extension, Active=Yes
   Awesome screenshot: Capture and Annotate - 
ID=jid0-GXjLLfbCoAx0LcltEdFrEkQdQPI@jetpack, Version=2.3.6, minVersion=8.0, 
maxVersion=9.*, Location=app-profile, Type=extension, Active=Yes
   CopyAllUrls - ID={960BE052-4847-422b-9AD6-8631D3D0A607}, Version=0.9.2, 
minVersion=1.5, maxVersion=3.6.*, Location=app-profile, Type=extension, 
Active=Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.102  
metric 2
  Profiles: Profile0 (Default) - LastVersion=11.0/20120310010446 (Running)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2012-04-04 (14 days ago)
  dmi.bios.date: 08/10/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.24
  dmi.modalias: 
dmi:bvnAcer:bvrV1.24:bd08/10/2011:svnAcer:pnAspire5742:pvrV1.24:rvnAcer:rnAspire5742:rvrV1.24:cvnAcer:ct10:cvrV1.24:
  dmi.product.name: Aspire 5742
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1206463] Re: Non-default themes will not remain selected

[Launchpad Bug Tracker]

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

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

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

Title:
  Non-default themes will not remain selected

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox 23 on Ubuntu 13.10 with gnome-shell & Xfce installed.  I can
  download and select themes other than default.  Firefox restarts
  behaves correctly.  However, on the next restart or on the second
  restart, the default theme is active even though I do not wish it.
  I've noticed that if I leave the Add-ons page open,  after a few
  minutes the appearance page will say that the default theme will be
  selected after restart.  This is with no input from me.  Both gnome-
  shell & Xfce DEs exhibit this behavior, not sure about Unity.
  Firefox 23 exhibits no other misbehaviors I'm aware of.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: firefox 23.0~b4+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daily  1363 F pulseaudio
  BrokenPermissions:
   extensions/silverme...@pardal.de.xpi (0o400)
   extensions/{961408A3-C970-4577-970A-D97C29839A67}.xpi (0o400)
  BuildID: 20130709093527
  Channel: Unavailable
  Date: Tue Jul 30 06:50:05 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-06-07 (52 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130607)
  IpRoute:
   default via 192.168.1.1 dev wlan1  proto static 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.107  
metric 9
  MarkForUpload: True
  PrefSources:
   prefs.js
   [Profile]/extensions/fire...@ghostery.com/defaults/preferences/defaults.js
   
[Profile]/extensions/matus.uhl...@gmail.com/defaults/preferences/ImageTools.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=23.0/20130709093527 (In use)
  RelatedPackageVersions:
   gnome-shell   3.8.3-1ubuntu4
   totem-mozilla 3.8.2-0ubuntu1
   rhythmbox-mozilla 2.99.1-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12a
  dmi.board.name: GA-MA785GM-US2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12a:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785GM-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785GM-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA785GM-US2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1214021] Re: Thunderbird freezes when viewing emails, clicking "Get Mail", and other tasks

[Launchpad Bug Tracker]

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

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

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

Title:
  Thunderbird freezes when viewing emails, clicking "Get Mail", and
  other tasks

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  See above

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: thunderbird 17.0.8+build1-0ubuntu0.12.10.1
  ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16
  Uname: Linux 3.5.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.6.1-0ubuntu12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rajiv  1983 F pulseaudio
  BuildID: 20130803235212
  Channel: Unavailable
  Date: Mon Aug 19 12:18:30 2013
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  ForcedLayersAccel: False
  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 wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.19  metric 
9
  MarkForUpload: True
  PrefSources: prefs.js
  Prefs:
   extensions.lastAppVersion: "17.0.8" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.database.lastMaintenance: 1375673204 (prefs.js)
   places.history.expiration.transient_current_max_pages: 29717 (prefs.js)
   print_printer: "Brother-MFC-7840W" (prefs.js)
  Profiles: Profile0 (Default) - LastVersion=17.0.8/20130803235212 (In use)
  RelatedPackageVersions:
   google-talkplugin 4.4.2.0-1
   rhythmbox-mozilla 2.97-1ubuntu6.1
   totem-mozilla 3.4.3-0ubuntu5
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6EET21WW (1.02 )
  dmi.board.name: 2776L9U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6EET21WW(1.02):bd10/09/2008:svnLENOVO:pn2776L9U:pvrThinkPadX301:rvnLENOVO:rn2776L9U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2776L9U
  dmi.product.version: ThinkPad X301
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1803342] Re: GNOME Shell using older Ubuntu 16.04~18.04 icons on 18.10

[Launchpad Bug Tracker]

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

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

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

Title:
  GNOME Shell using older Ubuntu 16.04~18.04 icons on 18.10

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  After starting my user session, all icons from pre-installed system
  programs, (i.e., System Monitor) are presented using older icons on
  the dock, from 16.04~18.04, instead of showing the new 18.10 icons. On
  programs lists they have the correct 18.10 icons. Even when opening
  new system programs, that are not marked as favorites on the dock,
  they are opened with the correct 18.10 icons. This happens at random,
  I can't find a precise way to get this bug to happen.

  Description:  Ubuntu 18.10
  Release:  18.10

  gnome-shell:
Instalado: 3.30.1-2ubuntu1
Candidato: 3.30.1-2ubuntu1
Tabela de versão:
   *** 3.30.1-2ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 10:27:27 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['cpufreq@konkor', 
'temperature@xtranophilist', 'Internet-Speed-Meter@TH3L0N3C0D3R', 
'ubuntu-appindicat...@ubuntu.com', 'indicator-sens...@alexmurray.github.com', 
'sensory-percept...@harlemsquirrel.github.io', 'vbox-app...@gs.eros2.info', 
'gsconn...@andyholmes.github.io', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-10-30 (14 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1803363] Re: The default shortcut for taking a screenshot kills X

[Launchpad Bug Tracker]

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

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

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

Title:
  The default shortcut for taking a screenshot kills X

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I was looking for the default key for taking a screenshot from
  Unity/GNOME settings and found a list of keyboard shortcuts (as in the
  attached screenshot).

  It turns out that Ctrl+Alt+Print also happens to kill X by default.

  This is not optimal:-)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-11-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1811731] Re: compuer freeze

[Daniel van Vugt]

Your XorgLog seems to show some bugs with the Nouveau driver that may
make the screen appear to freeze:

[ 11270.264] (WW) NOUVEAU(0): nouveau_dri2_flip_event_handler: Pageflip has 
impossible msc 675984 < target_msc 675985
[ 12931.381] (WW) NOUVEAU(0): nouveau_dri2_flip_event_handler: Pageflip has 
impossible msc 775617 < target_msc 775618
[ 13043.502] (WW) NOUVEAU(0): nouveau_dri2_flip_event_handler: Pageflip has 
impossible msc 782342 < target_msc 782343

Can you please try installing the official Nvidia driver:

  sudo apt install nvidia-driver-390

and tell us if that avoids the problem?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  compuer freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  computer system freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jan 14 14:57:48 2019
  DistUpgraded: 2018-09-05 17:29:52,691 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
  InstallationDate: Installed on 2015-01-24 (1451 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 062a: Creative Labs Optical mouse
   Bus 002 Device 002: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
   Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-06 (130 days ago)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68C-GS FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Sep  5 09:58:08 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL DELL USB Keyboard KEYBOARD, id 8
   inputHID 062a:MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

[Daniel van Vugt]

OK, if "realtime-scheduling = no" didn't work then at least we still
know that you have:

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - No   <---  most likely crashed

so next please:

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

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

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

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

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1809712] Re: Not responding to input after switch user to auto-login account

[Daniel van Vugt]

If you're using a Xorg session (the default one named "Ubuntu") then the
mouse pointer is moved by xorg-server independently of gnome-shell. This
means that if the mouse pointer is frozen then it's either Xorg or the
kernel that's freezing.

If you're using Wayland and not using a Xorg session then please try
using the latter.

Can you please reproduce the problem again, recover using the lid trick
and then without rebooting run:

   dmesg > dmesg.txt
   journalctl > cur_boot.txt

If you need to reboot to recover then instead please run this
immediately after rebooting:

   journalctl -b-1 > prev_boot.txt

and send us the resulting text file(s).

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

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

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

** Tags added: radeon

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

Title:
  Not responding to input after switch user to auto-login account

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Step:

  1. There are two users, A and B. A is adminstrator, B is standard user, B is 
automatic login.
  2. Boot into Ubuntu 18.04.1 LTS, it will automatically login to user B.
  3. Switch User to user A without logging out.
  4. Switch User back to user B, either by logging out from user A or not.

  Expected: it will be back to user B normally.

  Actual: it backs to user B but become not responding to keyboard,
  touchpad, or mouse input. Closing the lid is responded normally, which
  is locking the screen, the three-arrows in the lock screen is animated
  normally, clock is updated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 25 14:19:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  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:183a]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-12-23 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=3182b497-aa0e-491d-aad5-e1c8e049dda1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.0E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.01:bd01/18/2012:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn183A:rvr56.0E:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g4 Notebook PC
  dmi.product.version: 07911020561620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze

[Daniel van Vugt]

Sounds like a great workaround. But I have more questions :)

1. Please double-check again that uninstalling your extensions doesn't
help. Because I still find it strange that other people don't report
this bug so most likely it's caused by something that most other people
don't have, like the extensions.

2. Can we assume that you have to use the mouse to get to the dash
search?

3. Can you please try live booting 19.04 (don't install it just boot
from USB) and tell us if the same problem occurs?
http://cdimages.ubuntu.com/daily-live/current/

4. Can you please log the bug upstream with the Gnome Shell developers here:
   https://gitlab.gnome.org/GNOME/gnome-shell/issues
   and then tell us the new bug ID?


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

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

Title:
  Occasional Keyboard freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am using 18.04 and sometimes, whatever I type does not work. It is
  as if there is no keyboard connected while I have my laptop keyboard
  and an external keyboard connected to the machine. I even enabled On
  Screen Keyboard and tried to type through it. Same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 879790] Re: [Lenovo Thinkpad T60] Sound doesn't play properly after upgrade from 11.04->11.10

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  [Lenovo Thinkpad T60] Sound doesn't play properly after upgrade from
  11.04->11.10

Status in xserver-xorg-driver-ati:
  Fix Released
Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  After the upgrade from Natty to Oneiric the sound that is played (by
  any program ex. banshee, VLC, Flash) sound very awkward, like if the
  whole sound is slightly gargling.

  My computer: Thinkpad T60

  Already tried to solve the problem: The german ubuntuforum has a wiki-
  page to solve sound problems
  (http://wiki.ubuntuusers.de/Sound_Problembehebung). Unfortunately,
  nothing helped - even a reinstalling of the Alsa-Module didn't solve
  the problem. Hence I think this is a bug.

  Special: In the thread that I opened in the german forum
  (http://forum.ubuntuusers.de/topic/nach-upgrade-11-04-auf-11-10
  -ueberschlaegt-der-ton/) there was another user that has the same
  Problem AND he has the same computer as I do. Therefore, I'm not sure
  if it is a computerspecific problem that may be connected with the
  chipset of the T60...

  Thanks
  Quesst

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/879790/+subscriptions

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

[Desktop-packages] [Bug 1754400] Re: "General input/output error" when attempting to save a document to google drive

[Adolfo Jayme]

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

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

Title:
  "General input/output error" when attempting to save a document to
  google drive

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  (bug initially reported upstream, but apparently only affects ubuntu:
  https://bugs.documentfoundation.org/show_bug.cgi?id=97898)

  Steps to reproduce:

   - start a document in libreoffice writer
   - menu File > Save Remote…
   - use the "Add Service" button to configure an existing google account (not 
one using 2FA, that's not implemented yet)

  Expected result: the document is saved on your google drive

  Current result: an error dialog box that reads: "Error saving the
  document Untitled 1: General input/output error."

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 17:22:50 2018
  InstallationDate: Installed on 2018-02-08 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811731] [NEW] compuer freeze

[Alistair]

Public bug reported:

computer system freeze

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jan 14 14:57:48 2019
DistUpgraded: 2018-09-05 17:29:52,691 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
InstallationDate: Installed on 2015-01-24 (1451 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 062a: Creative Labs Optical mouse
 Bus 002 Device 002: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
 Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-06 (130 days ago)
dmi.bios.date: 10/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: N68C-GS FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Sep  5 09:58:08 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDELL DELL USB Keyboard KEYBOARD, id 8
 inputHID 062a:MOUSE, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: nouveau

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

Title:
  compuer freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  computer system freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jan 14 14:57:48 2019
  DistUpgraded: 2018-09-05 17:29:52,691 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
  InstallationDate: Installed on 2015-01-24 (1451 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 062a: Creative Labs Optical mouse
   Bus 002 Device 002: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
   Bus 002 Device 004: ID 058f:9360 

[Desktop-packages] [Bug 1802208] Re: Reports won't open

[Bug Watch Updater]

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

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-12-05T15:14:05+00:00 Jan-Marek Glogowski wrote:

When OpenJDK tried to enforce stricter class path URL checks without
previous announcement, things started to break left and right. This
included failing LibreOffice JUnitTest checks, since the dependency
classpath in our generated Jars doesn't pass the stricter URL checks and
therefore is ignored.

The check was disabled later in http://hg.openjdk.java.net/jdk-
updates/jdk11u/rev/8513ac27b651, but I still think it's worthwhile to
fix our Jars and then disable
jdk.net.URLClassPath.disableClassPathURLCheck when running the tests.

More info is also in https://gerrit.libreoffice.org/#/c/63118/2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802208/comments/12


On 2018-12-06T10:08:16+00:00 Sbergman wrote:

quoting my 2018-11-12 10:34 comment at
 "Simplify and fix Java UNO
API test makefiles":

"With Java moving away from supporting absolute file URLs in jar
manifest Class-Paths, we need a new solution for what we currently do
with gb_Jar_add_manifest_classpath/gb_Helper_make_url.  We use that in
unotest/Jar_test.mk (which is the subject of this change), but also in
gb_Jar_use_system_jar as used in various places in
RepositoryExternal.mk.  (Note how we already have issues with file URLs
in all of these places with recent Java on Windows, see

'Re: make check fails in [build JCS]'.)

"However, from
 and the details of

'8195874: Improve jar specification adherence', it looks like support
for relative paths starting with '..' in jar manifest Class-Paths is
also going away.  We currently use such at least in
bridges/Jar_java_uno.mk, connectivity/Jar_sdbc_hsqldb.mk, and
javaunohelper/Jar_juh.mk."

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802208/comments/13


On 2018-12-06T10:40:57+00:00 Jan-Marek Glogowski wrote:

>From reading the current URLClassPath.java code, it seem you can set
"jdk.net.URLClassPath.disableClassPathURLCheck" to "debug", and the
loader will print the ignored class path entries, which can help
debugging.

But it doesn't look like there is a way to get the default value, which
could be checked by configure or even our jars to want people of
failures.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802208/comments/14


On 2018-12-11T15:12:38+00:00 Libreoffice-commits wrote:

Jan-Marek Glogowski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/905c107cde4a0a7059b1e11b5f23a0a59188cb0c%5E%21

tdf#121925 test for URLClassPath.ClassPathURLCheck

It will be available in 6.3.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802208/comments/15


On 2018-12-11T21:09:04+00:00 Libreoffice-commits wrote:

Jan-Marek Glogowski committed a patch related to this issue.
It has been pushed to "libreoffice-6-2":

https://git.libreoffice.org/core/+/c9de94c65b8ab8bf6073400eda5ba848ba22af47%5E%21

tdf#121925 test for URLClassPath.ClassPathURLCheck

It will be available in 6.2.0.1.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802208/comments/16


On 2018-12-11T21:12:37+00:00 Jan-Marek Glogowski wrote:

These patches are no fixes, but will detect the failing JDK setup during
configure as an early warning! They should be reverted after 

[Desktop-packages] [Bug 1811724] [NEW] libbd_mdraid.so.2: cannot open shared object file

[themusicgod1]

Public bug reported:

Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
found

Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev 
plugin

Seems to give this warning every time I boot.

udisks2:
  Installed: 2.8.1-3
  Candidate: 2.8.1-3

ubuntu: 19.04 disco

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: udisks2 2.8.1-3
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CustomUdevRuleFiles: 80-net-setup-link.rules
Date: Mon Jan 14 21:31:52 2019
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Red Hat KVM
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
SourcePackage: udisks2
UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Seabios
dmi.bios.version: 0.5.1
dmi.chassis.type: 1
dmi.chassis.vendor: Red Hat
dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
dmi.product.family: Red Hat Enterprise Linux
dmi.product.name: KVM
dmi.product.version: RHEL 6.6.0 PC
dmi.sys.vendor: Red Hat

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

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

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

-- 
Mailing list: https://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 1804744] Re: Restoring from new location does not find backup files

[ethanay]

We are traveling right now so I won't be able to test this for a few weeks.
Better if someone else can get to it sooner...thank you!

On Tue, Jan 15, 2019, 04:45 Brian Murray  Hello ethanay, or anyone else affected,
>
> Accepted deja-dup into cosmic-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/deja-
> dup/38.0-1ubuntu0.1 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-cosmic to verification-done-cosmic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-cosmic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: deja-dup (Ubuntu Cosmic)
>Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed verification-needed-cosmic
>
> ** Changed in: deja-dup (Ubuntu Bionic)
>Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed-bionic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1804744
>
> Title:
>   Restoring from new location does not find backup files
>
> Status in Déjà Dup:
>   Fix Released
> Status in deja-dup package in Ubuntu:
>   Fix Released
> Status in deja-dup source package in Bionic:
>   Fix Committed
> Status in deja-dup source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   When a user tries to restore a backup on a fresh Ubuntu install, deja-
>   dup will not be able to find their backup at first.
>
>   A workaround is to set the current backup location on the fresh
>   install to the old backup location. But that's not at all an obvious
>   path. A user would not normally try that.
>
>   [Test Case]
>
>   1. Back up some files to a temporary dir.
>   2. gsettings reset-recursively org.gnome.DejaDup
>   3. Try to restore from that temporary dir.
>
>   Notice that deja-dup will complain about waiting for Google Drive to
>   be set up (even though your backup drive has nothing to do with
>   Google).
>
>   [Regression Potential]
>
>   The proposed patch mostly affects the restore dialog. Any regressions
>   would likely be in that flow.
>
>   [Original Report]
>
>   1. I back up my computer to my external hard drive
>   2. I reinstall my new distro
>   3. I install deja-dup and duplicity
>   4. I open deja-dup, and select restore
>   5. I select my external hard drive and the restore directory
>   6. Deja-dup fails with "no backup found" message and creates a new
> backup directory on the hard drive
>
>   This indicated to me that deja dup ignored the restore directory I
>   entered, and instead used the default directory, which did not exist,
>   hence restore fails because the backend is told to look in the wrong
>   place for the backup! This seems like more a user interface issue than
>   an issue with the backup.
>
>   Here is the workflow I had to use to restore my backup:
>
>   1. Set storage location to "local folder" and then manually navigate to
> the folder on my external hard drive. If I did not do this specifically,
> then backup would fail. Selecting the external hard drive directly as the
> device and entering the folder in the "folder" field also fails.
>   2. Select restore and again use "local folder" and manually navigate to
> the folder on my external hard drive. If I instead try to use the hard
> drive device listed and enter the backup folder in the "folder" field, the
> restore also fails.
>
>   This issue occurs on both Ubuntu 18.04.1 and ElementaryOS Juno.
>
>   lsb_release -d
>   Description:  elementary OS 5.0 Juno
>
>   dpkg-query -W deja-dup duplicity
>   deja-dup  37.1-2fakesync1
>   duplicity 0.7.17-0ubuntu1
>
>   gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
>   cat /tmp/deja-dup.gsettings
>   org.gnome.DejaDup last-restore '2018-11-23T01:39:44.556645Z'
>   org.gnome.DejaDup periodic true
>   org.gnome.DejaDup periodic-period 1
>   org.gnome.DejaDup full-backup-period 90
>   org.gnome.DejaDup backend 'local'
>   org.gnome.DejaDup last-run '2018-11-23T01:39:44.556645Z'
>   org.gnome.DejaDup nag-check ''
>   org.gnome.DejaDup prompt-check 

[Desktop-packages] [Bug 1802208] Re: Reports won't open

[Olivier Tilloy]

This appears to have been fixed in an OpenJDK update.
Successfully tested on xenial, bionic and disco.

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

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

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

Title:
  Reports won't open

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Invalid
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released

Bug description:
  Reports that were working as of June this year (I haven't opened them
  since then) now are failing with the following error:

  Can not activate the factory for
  org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory

  I tried creating a fresh report to see if its some kind of out of date file 
format but I get the same error:
1. select "Create Report in Design View..."
2. select "Save"
3. Double click report
4. Same error as above

  Of course I'm expecting the report to open without an error.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-report-builder 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:16:08 2018
  InstallationDate: Installed on 2018-02-17 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (190 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1802208/+subscriptions

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

[Desktop-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Nathan Collins]

I just reported this bug upstream here: https://gitlab.gnome.org/GNOME
/network-manager-applet/issues/39.

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1811717] Re: Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop disappear

[Ubuntu QA Website]

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

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

** Tags added: iso-testing

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

Title:
  Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop
  disappear

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I have some icons on desktop (applications folders and files)
  Changing Dock Icon size (Settings-Dock-Icon size) the icons on desktop 
disappear, they reappear creating a file or a folder in the desktop or in 
/Home/Desktop
  sometimes they reappear also changing Icon size again.

  Problem happen both with x11 and wayland session.

  corrado@corrado-p6-dd-1227:~$ inxi -SCGx
  System:
Host: corrado-p6-dd-1227 Kernel: 4.18.0-11-generic x86_64 bits: 64 
compiler: gcc v: 8.2.0 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.2.6 direct render: Yes 
  corrado@corrado-p6-dd-1227:~$ 

  corrado@corrado-p6-dd-1227:~$ apt policy nautilus
  nautilus:
Installed: 1:3.30.4-1ubuntu1
Candidate: 1:3.30.4-1ubuntu1
Version table:
   *** 1:3.30.4-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p6-dd-1227:~$ 

  gnome-shell-extension-desktop-icons:
Installed: 18.11~rc+git20181217-1
Candidate: 18.11~rc+git20181217-1
Version table:
   *** 18.11~rc+git20181217-1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 20:10:16 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1252, 581)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2018-12-27 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181227)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1802208] Re: Reports won't open

[Olivier Tilloy]

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

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

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

Title:
  Reports won't open

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Invalid
Status in libreoffice source package in Xenial:
  Confirmed
Status in libreoffice source package in Bionic:
  Confirmed

Bug description:
  Reports that were working as of June this year (I haven't opened them
  since then) now are failing with the following error:

  Can not activate the factory for
  org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory

  I tried creating a fresh report to see if its some kind of out of date file 
format but I get the same error:
1. select "Create Report in Design View..."
2. select "Save"
3. Double click report
4. Same error as above

  Of course I'm expecting the report to open without an error.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-report-builder 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:16:08 2018
  InstallationDate: Installed on 2018-02-17 (263 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (190 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1802208/+subscriptions

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

[Desktop-packages] [Bug 1811615] Re: custom keyboard shortcut forgotten after restarting gnome

[Sebastien Bacher]

Thanks for pointing that the dock is conflict with that specific
keybinding, reassigning

** Package changed: gnome-settings-daemon (Ubuntu) => gnome-shell-
extension-ubuntu-dock (Ubuntu)

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

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

Title:
  custom keyboard shortcut forgotten after restarting gnome

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

Bug description:
  Ubuntu 18.04.1
  gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  mutter 3.28.3-2~ubuntu18.04.2
  I don't know what else is important

  I installed Ubuntu and changed the shortcut for closing a window (It's called 
"Cerrar la Ventana" in spanish) from Alt+F4 to Super+Q using 
gnome-control-center. It worked well
  Then I restarted gnome (Alt+F2 then "r") and it stopped working.
  It's weird because:
  1) My other custom keyboard shortcuts keep working
  2) gnome-control-center still reports it as being super+q
  3) if I try to "change it" to super+q again directly that doesn't fix it, but 
if I change it to another thing first and then back to super+q it works well.
  4) If I restart gnome again, it stops working again (just that shortcut, not 
the others)

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

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

[Desktop-packages] [Bug 1811717] Re: Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop disappear

[Launchpad Bug Tracker]

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

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

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

Title:
  Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop
  disappear

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I have some icons on desktop (applications folders and files)
  Changing Dock Icon size (Settings-Dock-Icon size) the icons on desktop 
disappear, they reappear creating a file or a folder in the desktop or in 
/Home/Desktop
  sometimes they reappear also changing Icon size again.

  Problem happen both with x11 and wayland session.

  corrado@corrado-p6-dd-1227:~$ inxi -SCGx
  System:
Host: corrado-p6-dd-1227 Kernel: 4.18.0-11-generic x86_64 bits: 64 
compiler: gcc v: 8.2.0 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.2.6 direct render: Yes 
  corrado@corrado-p6-dd-1227:~$ 

  corrado@corrado-p6-dd-1227:~$ apt policy nautilus
  nautilus:
Installed: 1:3.30.4-1ubuntu1
Candidate: 1:3.30.4-1ubuntu1
Version table:
   *** 1:3.30.4-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p6-dd-1227:~$ 

  gnome-shell-extension-desktop-icons:
Installed: 18.11~rc+git20181217-1
Candidate: 18.11~rc+git20181217-1
Version table:
   *** 18.11~rc+git20181217-1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 20:10:16 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1252, 581)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2018-12-27 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181227)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1811615] Re: custom keyboard shortcut forgotten after restarting gnome

[Vicente Reyes Valdivieso]

There it is. I think I found the reason this happens, though. It's the dash to 
dock extension, which overrides the custom commands:
https://askubuntu.com/questions/977876/changing-command-super-q


** Attachment added: "journalctl log uploaded anyway"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1811615/+attachment/5229029/+files/mylog

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

Title:
  custom keyboard shortcut forgotten after restarting gnome

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

Bug description:
  Ubuntu 18.04.1
  gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  mutter 3.28.3-2~ubuntu18.04.2
  I don't know what else is important

  I installed Ubuntu and changed the shortcut for closing a window (It's called 
"Cerrar la Ventana" in spanish) from Alt+F4 to Super+Q using 
gnome-control-center. It worked well
  Then I restarted gnome (Alt+F2 then "r") and it stopped working.
  It's weird because:
  1) My other custom keyboard shortcuts keep working
  2) gnome-control-center still reports it as being super+q
  3) if I try to "change it" to super+q again directly that doesn't fix it, but 
if I change it to another thing first and then back to super+q it works well.
  4) If I restart gnome again, it stops working again (just that shortcut, not 
the others)

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

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

[Desktop-packages] [Bug 1811717] [NEW] Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop disappear

[corrado venturini]

Public bug reported:

I have some icons on desktop (applications folders and files)
Changing Dock Icon size (Settings-Dock-Icon size) the icons on desktop 
disappear, they reappear creating a file or a folder in the desktop or in 
/Home/Desktop
sometimes they reappear also changing Icon size again.

Problem happen both with x11 and wayland session.

corrado@corrado-p6-dd-1227:~$ inxi -SCGx
System:
  Host: corrado-p6-dd-1227 Kernel: 4.18.0-11-generic x86_64 bits: 64 
  compiler: gcc v: 8.2.0 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.2.6 direct render: Yes 
corrado@corrado-p6-dd-1227:~$ 

corrado@corrado-p6-dd-1227:~$ apt policy nautilus
nautilus:
  Installed: 1:3.30.4-1ubuntu1
  Candidate: 1:3.30.4-1ubuntu1
  Version table:
 *** 1:3.30.4-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-p6-dd-1227:~$ 

gnome-shell-extension-desktop-icons:
  Installed: 18.11~rc+git20181217-1
  Candidate: 18.11~rc+git20181217-1
  Version table:
 *** 18.11~rc+git20181217-1 500
500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu disco/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.30.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 14 20:10:16 2019
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1252, 581)'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2018-12-27 (18 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181227)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug disco

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

Title:
  Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop
  disappear

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have some icons on desktop (applications folders and files)
  Changing Dock Icon size (Settings-Dock-Icon size) the icons on desktop 
disappear, they reappear creating a file or a folder in the desktop or in 
/Home/Desktop
  sometimes they reappear also changing Icon size again.

  Problem happen both with x11 and wayland session.

  corrado@corrado-p6-dd-1227:~$ inxi -SCGx
  System:
Host: corrado-p6-dd-1227 Kernel: 4.18.0-11-generic x86_64 bits: 64 
compiler: gcc v: 8.2.0 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.2.6 direct render: Yes 
  corrado@corrado-p6-dd-1227:~$ 

  corrado@corrado-p6-dd-1227:~$ apt policy nautilus
  nautilus:
Installed: 1:3.30.4-1ubuntu1
Candidate: 1:3.30.4-1ubuntu1
Version table:
   *** 1:3.30.4-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p6-dd-1227:~$ 

  gnome-shell-extension-desktop-icons:
Installed: 18.11~rc+git20181217-1
Candidate: 18.11~rc+git20181217-1
Version table:
   *** 18.11~rc+git20181217-1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 

[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze

[Dilip]

I think this is a permanent workaround. It could get rid of keyboard
freeze this time as well by trying to type something on the dash search.

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

Title:
  Occasional Keyboard freeze

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am using 18.04 and sometimes, whatever I type does not work. It is
  as if there is no keyboard connected while I have my laptop keyboard
  and an external keyboard connected to the machine. I even enabled On
  Screen Keyboard and tried to type through it. Same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797141] Re: [nvidia] gnome-shell frequent restart or crash after unlocking screen or resume from sleep

[Karsten W. Rohrbach]

Thanks for pointing out uninstalling the shell extensions. I had the
same problem and switching off all custom shell extensions helped
instantly.

Basically, this also urges an audit of gnome-shell and associated
libraries, as this type of crash _could_ be a security issue triggered
by extensions (potentially untrusted thris party data/code).

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

Title:
  [nvidia] gnome-shell frequent restart or crash after unlocking screen
  or resume from sleep

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  First, let me provide necessary information about system or packages

  System: Ubuntu 18.04.1 LTS
  Package version: gnome-shell 3.28.3-0ubuntu0.18.04.2

  The problem started 3-4 weeks ago (probably after updating several
  packages via `apt update; apt upgrade`

  After *almost all* screen unlock or resume from sleep events, this is what 
happens:
  * I briefly see the desktop screen (which is security or privacy problem I 
guess)
  * then login screen comes up, asking for the password
  * after I put the password there is a wait (5-10 seconds)
  * after that there are two possibilities:
  1. there's brief flash in screen and then screen goes black. i can not 
fire up tty consoles and i have to use SysRq Magic keys to reboot the system
  2. if it does not crash, I login the system, I see the programs/windows 
but they're unresponsive for 10-30 seconds. after unresponsive time, 
gnome-shell restarts and only then system starts to function normally. Then 
apport-bug is started for gnome-shell, I try to send the crash reports.

  I'm not sure this is gnome-shell or gdm3 or Xorg problem. But, apport-
  crash always starts collecting data about gnome-shell, thus I filed
  report against gnome-shell. I also filed bug report against xorg
  (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1797124).

  Let me provide additional info that might help;
  - I have nvidia drivers installed in system
  - gnome-shell produces tons of journal entries (this apport-crash reports are 
huge, nearly 150 MB and I cannot upload them)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 10 17:10:40 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-06-01 (131 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

[Iain Lane]

Fix Released for dnsmasq (because of the revert), but we should still
keep an eye on the upstream thread.

** Changed in: dnsmasq (Ubuntu Disco)
   Status: New => Fix Released

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Disco:
  Fix Released
Status in network-manager source package in Disco:
  Fix Released

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

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

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

[Desktop-packages] [Bug 1804744] Please test proposed package

[Brian Murray]

Hello ethanay, or anyone else affected,

Accepted deja-dup into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/deja-
dup/37.1-2fakesync1ubuntu0.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Restoring from new location does not find backup files

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Bionic:
  Fix Committed
Status in deja-dup source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When a user tries to restore a backup on a fresh Ubuntu install, deja-
  dup will not be able to find their backup at first.

  A workaround is to set the current backup location on the fresh
  install to the old backup location. But that's not at all an obvious
  path. A user would not normally try that.

  [Test Case]

  1. Back up some files to a temporary dir.
  2. gsettings reset-recursively org.gnome.DejaDup
  3. Try to restore from that temporary dir.

  Notice that deja-dup will complain about waiting for Google Drive to
  be set up (even though your backup drive has nothing to do with
  Google).

  [Regression Potential]

  The proposed patch mostly affects the restore dialog. Any regressions
  would likely be in that flow.

  [Original Report]

  1. I back up my computer to my external hard drive
  2. I reinstall my new distro
  3. I install deja-dup and duplicity
  4. I open deja-dup, and select restore
  5. I select my external hard drive and the restore directory
  6. Deja-dup fails with "no backup found" message and creates a new backup 
directory on the hard drive

  This indicated to me that deja dup ignored the restore directory I
  entered, and instead used the default directory, which did not exist,
  hence restore fails because the backend is told to look in the wrong
  place for the backup! This seems like more a user interface issue than
  an issue with the backup.

  Here is the workflow I had to use to restore my backup:

  1. Set storage location to "local folder" and then manually navigate to the 
folder on my external hard drive. If I did not do this specifically, then 
backup would fail. Selecting the external hard drive directly as the device and 
entering the folder in the "folder" field also fails.
  2. Select restore and again use "local folder" and manually navigate to the 
folder on my external hard drive. If I instead try to use the hard drive device 
listed and enter the backup folder in the "folder" field, the restore also 
fails.

  This issue occurs on both Ubuntu 18.04.1 and ElementaryOS Juno.

  lsb_release -d
  Description:  elementary OS 5.0 Juno

  dpkg-query -W deja-dup duplicity
  deja-dup  37.1-2fakesync1
  duplicity 0.7.17-0ubuntu1

  gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
  cat /tmp/deja-dup.gsettings
  org.gnome.DejaDup last-restore '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup last-run '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2018-11-22T12:34:36.095106Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['/home/ethan/.local/share/Trash']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'ethan-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'ethan-laptop'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  

[Desktop-packages] [Bug 1804744] Re: Restoring from new location does not find backup files

[Brian Murray]

Hello ethanay, or anyone else affected,

Accepted deja-dup into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/deja-
dup/38.0-1ubuntu0.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-cosmic

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

** Tags added: verification-needed-bionic

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

Title:
  Restoring from new location does not find backup files

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Bionic:
  Fix Committed
Status in deja-dup source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When a user tries to restore a backup on a fresh Ubuntu install, deja-
  dup will not be able to find their backup at first.

  A workaround is to set the current backup location on the fresh
  install to the old backup location. But that's not at all an obvious
  path. A user would not normally try that.

  [Test Case]

  1. Back up some files to a temporary dir.
  2. gsettings reset-recursively org.gnome.DejaDup
  3. Try to restore from that temporary dir.

  Notice that deja-dup will complain about waiting for Google Drive to
  be set up (even though your backup drive has nothing to do with
  Google).

  [Regression Potential]

  The proposed patch mostly affects the restore dialog. Any regressions
  would likely be in that flow.

  [Original Report]

  1. I back up my computer to my external hard drive
  2. I reinstall my new distro
  3. I install deja-dup and duplicity
  4. I open deja-dup, and select restore
  5. I select my external hard drive and the restore directory
  6. Deja-dup fails with "no backup found" message and creates a new backup 
directory on the hard drive

  This indicated to me that deja dup ignored the restore directory I
  entered, and instead used the default directory, which did not exist,
  hence restore fails because the backend is told to look in the wrong
  place for the backup! This seems like more a user interface issue than
  an issue with the backup.

  Here is the workflow I had to use to restore my backup:

  1. Set storage location to "local folder" and then manually navigate to the 
folder on my external hard drive. If I did not do this specifically, then 
backup would fail. Selecting the external hard drive directly as the device and 
entering the folder in the "folder" field also fails.
  2. Select restore and again use "local folder" and manually navigate to the 
folder on my external hard drive. If I instead try to use the hard drive device 
listed and enter the backup folder in the "folder" field, the restore also 
fails.

  This issue occurs on both Ubuntu 18.04.1 and ElementaryOS Juno.

  lsb_release -d
  Description:  elementary OS 5.0 Juno

  dpkg-query -W deja-dup duplicity
  deja-dup  37.1-2fakesync1
  duplicity 0.7.17-0ubuntu1

  gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
  cat /tmp/deja-dup.gsettings
  org.gnome.DejaDup last-restore '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup last-run '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2018-11-22T12:34:36.095106Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['/home/ethan/.local/share/Trash']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace 

[Desktop-packages] [Bug 1811577] Re: gnome-software or ubuntu software does not load the software

[Olivier Tilloy]

Thanks. It looks like it was a transient problem. I'm going to close the
bug, feel free to re-open it (by changing the status back to New) if the
issue happens again. Thanks!

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

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

Title:
  gnome-software or ubuntu software does not load the software

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  When I open the gnome-software it loads infinitely, and nothing
  appears on the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:08:59 2019
  InstallationDate: Installed on 2019-01-10 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190110)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu1
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811707] Re: gnome-calculator snap does not respect shell theme

[Buo-ren, Lin]

** Tags added: snap

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

Title:
  gnome-calculator snap does not respect shell theme

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  I'm running 18.04 with Communitheme / Yaru.  The gnome-calculator snap
  doesn't appear to respect this where other snaps do.

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

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

[Desktop-packages] [Bug 1811707] [NEW] gnome-calculator snap does not respect shell theme

[Joseph Borg]

Public bug reported:

I'm running 18.04 with Communitheme / Yaru.  The gnome-calculator snap
doesn't appear to respect this where other snaps do.

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


** Tags: snap

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

Title:
  gnome-calculator snap does not respect shell theme

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  I'm running 18.04 with Communitheme / Yaru.  The gnome-calculator snap
  doesn't appear to respect this where other snaps do.

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

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

[Desktop-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

[Dan Candeto]

I'm experiencing what may be the same thing in bug #1804280.  I can't
duplicate the issue on wireless networks, only Ethernet (but the issue
is the same whether I use the onboard Ethernet or a USB Ethernet
interface).

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  

[Desktop-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency

[Dan Candeto]

Possibly the same issue as bug #1666432, but I can't confirm that it
occurs on the wireless interface, just Ethernet interfaces.

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

Title:
  intermittent periods of packet loss and high latency

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

Bug description:
  Intermittently and unpredictably, ping response times and packet loss
  will spike to unusable levels.  Normal ping times are about .25 ms for
  other hosts on the local network, with essentially no packet loss.
  During the problematic periods (usually lasting 2-10 minutes), packet
  loss jumps to about 50% and ping response times on the packets that
  aren't dropped jump to between 250 and 750 ms.

  This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu
  18.04.  Changing which host on the network I test this with has no
  effect (and during this, those other hosts are able to use the network
  without any problem).  Replacing the cable changes nothing.  Using a
  different Ethernet interface changes nothing.  Replacing the switch
  changes nothing.  This is almost certainly not a hardware problem.

  There is a chance that using wireless instead of Ethernet would fix
  the issue, but I have been avoiding that since the wired connection is
  much faster when Kubuntu is not malfunctioning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 20 12:48:05 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (711 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via [removed] dev enp0s31f6 proto dhcp metric 100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
   [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH
   enp0s31f6  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b  
/org/freedesktop/NetworkManager/ActiveConnection/5
   [removed]  btdisconnected  /org/freedesktop/NetworkManager/Devices/5 
 --  ----
   wlp3s0 wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 --
   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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2053 F pulseaudio
   /dev/snd/pcmC1D0c:   dan2053 F...m pulseaudio
   /dev/snd/controlC1:  dan2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (712 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 
100
  MachineType: Dell Inc. Precision Tower 3420
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   

[Desktop-packages] [Bug 1799293] Re: Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works.

[Gabriel C.]

@hjwp2, For most folk I do believe Super+L twice is sufficient but it
isn't a full workaround. While it does suspend the machine, it doesn't
prevent the thing folks are fussing about: If someone wakes up your
machine the UI is still bugged, so a random citizen is still able to
interact with the docks (so they can run any script you have in your
dock). That and... maybe you don't want to suspend your machine.  How
big of a deal these are is... relative.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell-extension-dashtodock source package in Bionic:
  Confirmed
Status in gnome-shell source package in Cosmic:
  Confirmed
Status in gnome-shell-extension-dashtodock source package in Cosmic:
  Confirmed
Status in gnome-shell source package in Disco:
  Confirmed
Status in gnome-shell-extension-dashtodock source package in Disco:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

[Alberto Milone]

@Josh: we don't overwrite the xorg.conf any more. We simply create
configuration files in /usr/share/X11/xorg.conf.d/ . This is why we
dropped the feature.

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

Title:
  gpu-manager should also support using custom xorg.conf files for
  Nvidia

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Different GPUs may require different options in the xorg.conf file. Currently 
this is not possible, since the options have been hardcoded in gpu-manager to 
configure the system automatically.

  This new (backported) feature allows users to tell gpu-manager to use
  their own custom xorg.confs for their NVIDIA GPUs.

  [Test Case]
  1) Enable the xenial-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Place your configuration file(s) in the /usr/share/gpu-manager.d
  directory.

  If you are using a non-hybrid system, you can create the /usr/share
  /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
  specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
  /gpu-manager.d/hybrid-power-saving, depending on the power profile you
  intend to apply your settings to.

  4) Restart the system and see if it boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  5) Make sure that the /etc/X11/xorg.conf matches the file you
  specified in 3)

  [Regression Potential]
  Low, the above mentioned changes are already in Artful, and will not affect 
the system's behaviour unless new configuration files are put in the 
/usr/share/gpu-manager.d/ directory.

  __
  This feature has been implemented for Intel (ex. gpumanager_uxa), which is 
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).

  And now Nvidia also need this feature to add Option
  "nvidiaXineramaInfo" "off" to fix some issues.

  Btw, I'm thinking it might be a more flexible to have a config file
  which user could add all options as they want so that we could prevent
  keeping change gpu-manager when some more options are needed in the
  future.

  Needed by LP: #1653592

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+subscriptions

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

[Desktop-packages] [Bug 1811438] Re: getting a printer to work with my laptop

[Brian Murray]

** Package changed: ubuntu => cups (Ubuntu)

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

Title:
  getting a printer to work with my laptop

Status in cups package in Ubuntu:
  New

Bug description:
  when i click on connect for the printer i get up run/cups/cup.sock/
  and cannot get beyond this and just go round in circles. I now have a
  new wireless printer (HP deskjet 2622) and this works with my
  smartphone and my husbands smartphone and his laptop which is
  microsoft?

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

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

[Desktop-packages] [Bug 49498] Re: With Evince I can't copy text out from PDF documents created with cups-pdf

[Bernhard Schülke]

(Ubuntu 18.04)

Evince
Version = 3.28.4-0ubuntu1 
Diodon
Version = 1.8.0-1

Same problem.
When i use atril as pdf-reader, i can copy text to the diodon table. But it 
doesn't work with evince. 

Date today = 2018-01-14.

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

Title:
  With Evince I can't copy text out from PDF documents created with
  cups-pdf

Status in Evince:
  Unknown
Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  When I create PDF documents with the cups-pdf printer, after, I can't select 
text and copy it out from the PDF itself.
  The strange thing is that when I have installed the cups-pdf printer with the 
gnome-cups-manager, I have printed the test page. In this case, and only in 
this case, when I opened the pdf created in Evince I am able to copy the text 
and paste it elsewhere.
  The problem is that when I use the cups-pdf from other tools like gedit, I 
can create PDF documents, but when I open it in Evince, I can't copy text out. 
These documents are like "protected" from copying.

  
  The step to reproduce are:
  1) install cups-pdf
  2) open gnome-cups-manager and install the new printer, then make a test 
pressing the
  "Print a test page" button
  3) open in Evince the just created PDF document and try to copy the text 
> you are able to do
  4) open gedit, write something, and choose to create a PDF with cups-pdf
  5) open in Evince the PDF document just created and try to copy the text 
> you aren't able to do

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

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

[Desktop-packages] [Bug 1811438] [NEW] getting a printer to work with my laptop

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

when i click on connect for the printer i get up run/cups/cup.sock/ and
cannot get beyond this and just go round in circles. I now have a new
wireless printer (HP deskjet 2622) and this works with my smartphone and
my husbands smartphone and his laptop which is microsoft?

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


** Tags: bot-comment
-- 
getting a printer to work with my laptop
https://bugs.launchpad.net/bugs/1811438
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cups 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 1673230] Re: No power indicator for Logitech MX Anywhere 2 wireless mouse

[Sebastien Bacher]

Thanks for the reply, it's probably one of the issues fixed with newer
kernel/upower versions, if it's working in the current LTS then let's
close the bug, we don't plan to SRU those improvements to xenial at this
point

** Package changed: gnome-power-manager (Ubuntu) => upower (Ubuntu)

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

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

Title:
  No power indicator for Logitech MX Anywhere 2 wireless mouse

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-power-manager:
Installiert:   3.18.0-1ubuntu1
Installationskandidat: 3.18.0-1ubuntu1
Versionstabelle:
   *** 3.18.0-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I would expect to have a battery symbol in the top right corner for the mouse 
as well as battery statistics as for internal laptop battery or previous 
Logitech MX Anywhere mouse.

  4) What happened instead
  No battery shown and statistics window only showing internal laptop battery.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-power-manager 3.18.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 15 19:44:21 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2016-05-15 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/upower/+bug/1673230/+subscriptions

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

[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS

[Sebastien Bacher]

Could those having this issue add their journalctl log from a session
where they try to connect the other monitor? And also give details of
the video cards/drivers you use and what screen are connected and using
what ports/adaptors/etc?

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

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

** Package changed: libxrandr (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Secondary monitor not connecting in 18.04 LTS

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
  (nvidia driver v390) and a Benq W1070 projector.

  I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects
  for a split second and then gets disconnected. In Ubuntu 16.04
  projector was working fine as a mirror display and extended desktop.
  Here's what I already tried:

  - enable the nouveau driver instead of the nvidia driver -> no result
  - enable the on-board intel board with sudo prime-select intel -> no result
  - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> 
no result
  - disable nouveau driver, disable nvidia driver from the repository and 
install nvidia driver from nvidia website (both 390 and 396) -> no result
  - installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
  - played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
  - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
  - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
  - under settings -> devices -> displays I don't see a secondary display (just 
the main one)

  I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
  day)

  Here is the output of xrandr the very second when I connect the
  projector (then HDMI-1-2 goes disconnected and no modes are
  displayed):

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x 
axis y axis) 345mm x 194mm
     1920x1080 60.02*+  60.0159.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 disconnected (normal left inverted right x axis y axis)
    1920x1080 (0x258) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
    1920x1080 (0x259) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
    1920x1080 (0x25a) 148.352MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 

[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS

[Máté Vojts]

Same here: Asus Zenbook UX410UA, i7-8550U, Intel UHD 620, Ubuntu
18.04.1.

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

Title:
  Secondary monitor not connecting in 18.04 LTS

Status in libxrandr package in Ubuntu:
  Confirmed

Bug description:
  I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
  (nvidia driver v390) and a Benq W1070 projector.

  I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects
  for a split second and then gets disconnected. In Ubuntu 16.04
  projector was working fine as a mirror display and extended desktop.
  Here's what I already tried:

  - enable the nouveau driver instead of the nvidia driver -> no result
  - enable the on-board intel board with sudo prime-select intel -> no result
  - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> 
no result
  - disable nouveau driver, disable nvidia driver from the repository and 
install nvidia driver from nvidia website (both 390 and 396) -> no result
  - installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
  - played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
  - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
  - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
  - under settings -> devices -> displays I don't see a secondary display (just 
the main one)

  I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
  day)

  Here is the output of xrandr the very second when I connect the
  projector (then HDMI-1-2 goes disconnected and no modes are
  displayed):

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x 
axis y axis) 345mm x 194mm
     1920x1080 60.02*+  60.0159.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 disconnected (normal left inverted right x axis y axis)
    1920x1080 (0x258) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
    1920x1080 (0x259) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
    1920x1080 (0x25a) 148.352MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
59.94Hz
    1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
33.75KHz
  v: height 1080 start 1084 end 1094 total 1125   clock  
60.00Hz
    1920x1080i 

[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mesa (Ubuntu Cosmic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Alberto Milone]

@Fink: I would like to see powertop when you don't use bbswitch (and the
Nvidia GPU is on). More specifically, I would like to know if you can
disable the Nvidia GPU using the "Tunables" tab from powertop.

-- 
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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Alberto Milone]

Pe4enko: Here is your problem:

NVRM: API mismatch: the client has the version 410.66, but
NVRM: this kernel module has the version 390.87. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.

It looks like you installed the 410.66 driver (maybe using the installer
from Nvidia's website), and then tried to install the 390 driver from
the Ubuntu archive. This is not going to work. Please uninstall the
nvidia packages (sudo apt-get remove --purge '*nvidia*') and then use
the Nvidia installer to uninstall the other driver.

-- 
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 1811225] Re: Mesa 18.2.8 stable release

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Mesa 18.2.8 stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point 
release of the series. This will also be backported to 18.04 as part of the HWE 
stack update.

  Upstream changes:

  18.2.3
  - Different patches for the DirectX9 and DRI state trackers.
  - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza 
and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky.
  - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, 
anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in
  Radeonsi.
  - State Trackers also get different fixes and corrections.
  - Finally, fixes for GLSL and NIR are also in this queue.

  18.2.4
  - Different fixes for different drivers: freedreno, radeonsi, swr, anv and 
radv.
  - Also there are fixes for ac, gallium, spirv and blorp.

  18.2.5
  - A patch for nine state tracker that fixes several crashes using nine's
  thread_submit feature. There are other patches to other state trackers.
  - A couple of patches for Meson build system, as well as for autotools.
  - In the drivers side, there are a couple of fixes for RADV, one regarding
  subgroups and another regarding conditional rendering. There are also fixes 
for virgl, r600, and i965.
  - Finally, the queue contains a couple of fixes for NIR, Wayland, and other
  components.

  18.2.6
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.7
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.8
  - Several fixes in Meson build system.
  - Also several fixes for st/nine subcomponent.
  - Patch for RADV driver that fixes a hang in Yakuza using DXVK.
  - There are also fixes for Virgl driver.
  - Added PCI IDs for VegaM, Vega20 and Vega10.

  
  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems, this is the last of the 
series so should be safe to update to.

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

[Dan Streetman]

The libreoffice and openjdk tests appear to have been failing either
consistently or intermittently for months or even over a year in some
cases.  It appears they should be ignored or marked flaky.

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

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Bionic:
  Fix Committed
Status in cups source package in Cosmic:
  Fix Committed
Status in cups source package in Disco:
  Fix Released
Status in cups package in Debian:
  Fix Released

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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

[Desktop-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency

[Dan Candeto]

Persists with 4.15.0-43-generic.

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

Title:
  intermittent periods of packet loss and high latency

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

Bug description:
  Intermittently and unpredictably, ping response times and packet loss
  will spike to unusable levels.  Normal ping times are about .25 ms for
  other hosts on the local network, with essentially no packet loss.
  During the problematic periods (usually lasting 2-10 minutes), packet
  loss jumps to about 50% and ping response times on the packets that
  aren't dropped jump to between 250 and 750 ms.

  This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu
  18.04.  Changing which host on the network I test this with has no
  effect (and during this, those other hosts are able to use the network
  without any problem).  Replacing the cable changes nothing.  Using a
  different Ethernet interface changes nothing.  Replacing the switch
  changes nothing.  This is almost certainly not a hardware problem.

  There is a chance that using wireless instead of Ethernet would fix
  the issue, but I have been avoiding that since the wired connection is
  much faster when Kubuntu is not malfunctioning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 20 12:48:05 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (711 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via [removed] dev enp0s31f6 proto dhcp metric 100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
   [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH
   enp0s31f6  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b  
/org/freedesktop/NetworkManager/ActiveConnection/5
   [removed]  btdisconnected  /org/freedesktop/NetworkManager/Devices/5 
 --  ----
   wlp3s0 wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 --
   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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2053 F pulseaudio
   /dev/snd/pcmC1D0c:   dan2053 F...m pulseaudio
   /dev/snd/controlC1:  dan2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (712 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 
100
  MachineType: Dell Inc. Precision Tower 3420
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64

[Desktop-packages] [Bug 1811674] [NEW] Even withg WaylandEnable=false gdm3 only loads sometimes

[dusf]

Public bug reported:

gdm3:
  Installed: 3.28.3-0ubuntu18.04.3

Description:Ubuntu 18.04.1 LTS
Release:18.04

I expect the greeter to load every boot.

Instead, gdm3 is not stable on my system, it will work for either one or
several boots after I take corrective action, but inevitably this
results in the greeter not loading. The graphics card on my Intel Core
i5 system is an Nvidia GTX 970, and I manually installed nvidia-
driver-415 when I could not load a greeter as soon as I had installed.

Searching here and elsewhere, I have tried many things to resolve this,
which I will outline below. If you know something else I can try - to
get make gdm3 stable - please let me know.

Even with WaylandEnable=false uncommented in /etc/gdm3/custom.conf, I
usually cannot login, instead of the greeter I would see either a black
screen or graphic distortion like a black screen with some pink lines
across the top, and I am only able to login setting nomodeset.

With gd3 not working, I tried lightdm, and on encountering similar
issues switched back to gdm3 again:

sudo apt-get install gdm3
sudo dpkg-reconfigure gdm3

This seemed to work - kind of, for the first few days I could boot most
of the time. I have quiet splash permanently removed from my boot
options, and boot was sometimes hanging on Started NVIDIA Persistence
Daemon as in the attached images.

Another time with gdm3 I saw the following output instead of the
greeter, also attached.

How can I begin to resolve this issue please?

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

** Attachment added: "gdm3 sample distrotion"
   
https://bugs.launchpad.net/bugs/1811674/+attachment/5229001/+files/IMG_20190114_072805528%20%281%29.jpg

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

Title:
  Even withg WaylandEnable=false gdm3 only loads sometimes

Status in gdm3 package in Ubuntu:
  New

Bug description:
  gdm3:
    Installed: 3.28.3-0ubuntu18.04.3

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  I expect the greeter to load every boot.

  Instead, gdm3 is not stable on my system, it will work for either one
  or several boots after I take corrective action, but inevitably this
  results in the greeter not loading. The graphics card on my Intel Core
  i5 system is an Nvidia GTX 970, and I manually installed nvidia-
  driver-415 when I could not load a greeter as soon as I had installed.

  Searching here and elsewhere, I have tried many things to resolve
  this, which I will outline below. If you know something else I can try
  - to get make gdm3 stable - please let me know.

  Even with WaylandEnable=false uncommented in /etc/gdm3/custom.conf, I
  usually cannot login, instead of the greeter I would see either a
  black screen or graphic distortion like a black screen with some pink
  lines across the top, and I am only able to login setting nomodeset.

  With gd3 not working, I tried lightdm, and on encountering similar
  issues switched back to gdm3 again:

  sudo apt-get install gdm3
  sudo dpkg-reconfigure gdm3

  This seemed to work - kind of, for the first few days I could boot
  most of the time. I have quiet splash permanently removed from my boot
  options, and boot was sometimes hanging on Started NVIDIA Persistence
  Daemon as in the attached images.

  Another time with gdm3 I saw the following output instead of the
  greeter, also attached.

  How can I begin to resolve this issue please?

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

[Till Kamppeter]

The epson-inkjet-printer-escpr seems to be some problem of the test script 
design that the test sometimes fails on slow processors due to being to 
time-consuming, because it works on most architectures and repeating it can 
make it pass. So I simply re-triggered it on Xenial i386 and Bionic i386 to see 
whether it passes now. Note that I did not look into the actual test script of 
this package. At least the output of the test script looks like some standard 
script also used by CUPS and other printer drivers. This script for sure does 
not set MaxJobTime=0 in CUPS and so results should not change by this fix.
I do not know about LibreOffice and OpenJDK tests.

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

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Bionic:
  Fix Committed
Status in cups source package in Cosmic:
  Fix Committed
Status in cups source package in Disco:
  Fix Released
Status in cups package in Debian:
  Fix Released

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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

[Desktop-packages] [Bug 879790] Re: [Lenovo Thinkpad T60] Sound doesn't play properly after upgrade from 11.04->11.10

[Bug Watch Updater]

** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => 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/879790

Title:
  [Lenovo Thinkpad T60] Sound doesn't play properly after upgrade from
  11.04->11.10

Status in xserver-xorg-driver-ati:
  Fix Released
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade from Natty to Oneiric the sound that is played (by
  any program ex. banshee, VLC, Flash) sound very awkward, like if the
  whole sound is slightly gargling.

  My computer: Thinkpad T60

  Already tried to solve the problem: The german ubuntuforum has a wiki-
  page to solve sound problems
  (http://wiki.ubuntuusers.de/Sound_Problembehebung). Unfortunately,
  nothing helped - even a reinstalling of the Alsa-Module didn't solve
  the problem. Hence I think this is a bug.

  Special: In the thread that I opened in the german forum
  (http://forum.ubuntuusers.de/topic/nach-upgrade-11-04-auf-11-10
  -ueberschlaegt-der-ton/) there was another user that has the same
  Problem AND he has the same computer as I do. Therefore, I'm not sure
  if it is a computerspecific problem that may be connected with the
  chipset of the T60...

  Thanks
  Quesst

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/879790/+subscriptions

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

[Desktop-packages] [Bug 879790]

[Michel Dänzer]

(In reply to mirh from comment #79)
> Is this still a thing?

Let's assume not, thanks for the follow-up.

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

Title:
  [Lenovo Thinkpad T60] Sound doesn't play properly after upgrade from
  11.04->11.10

Status in xserver-xorg-driver-ati:
  Fix Released
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade from Natty to Oneiric the sound that is played (by
  any program ex. banshee, VLC, Flash) sound very awkward, like if the
  whole sound is slightly gargling.

  My computer: Thinkpad T60

  Already tried to solve the problem: The german ubuntuforum has a wiki-
  page to solve sound problems
  (http://wiki.ubuntuusers.de/Sound_Problembehebung). Unfortunately,
  nothing helped - even a reinstalling of the Alsa-Module didn't solve
  the problem. Hence I think this is a bug.

  Special: In the thread that I opened in the german forum
  (http://forum.ubuntuusers.de/topic/nach-upgrade-11-04-auf-11-10
  -ueberschlaegt-der-ton/) there was another user that has the same
  Problem AND he has the same computer as I do. Therefore, I'm not sure
  if it is a computerspecific problem that may be connected with the
  chipset of the T60...

  Thanks
  Quesst

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/879790/+subscriptions

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

[Desktop-packages] [Bug 1673230] Re: No power indicator for Logitech MX Anywhere 2 wireless mouse

[rjb]

Hi Sebastien

Meanwhile I use 18.04 LTS where the problem is solved.
Therefore I have no possibility to provide you with this information.
However, I see that somebody else is affected by the same bug - possibly that 
person can provide the required information.

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

Title:
  No power indicator for Logitech MX Anywhere 2 wireless mouse

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

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-power-manager:
Installiert:   3.18.0-1ubuntu1
Installationskandidat: 3.18.0-1ubuntu1
Versionstabelle:
   *** 3.18.0-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I would expect to have a battery symbol in the top right corner for the mouse 
as well as battery statistics as for internal laptop battery or previous 
Logitech MX Anywhere mouse.

  4) What happened instead
  No battery shown and statistics window only showing internal laptop battery.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-power-manager 3.18.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 15 19:44:21 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2016-05-15 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1673230/+subscriptions

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

[Desktop-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Jalon Funk]

This bug is fixed upstream. Can we get backport to bionic?

https://gitlab.gnome.org/GNOME/glib/issues/1271#note_352412
https://gitlab.gnome.org/GNOME/glib/merge_requests/365
https://gitlab.gnome.org/GNOME/glib/merge_requests/366

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

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

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

[Desktop-packages] [Bug 1811577] Re: gnome-software or ubuntu software does not load the software

[Phelps Scofield]

I have upgraded the system since the problem was detected, and it looks
like the gnome-software is working fine.I will try to install some
software to check if it is working well.

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

Title:
  gnome-software or ubuntu software does not load the software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When I open the gnome-software it loads infinitely, and nothing
  appears on the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:08:59 2019
  InstallationDate: Installed on 2019-01-10 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190110)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu1
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Olivier Tilloy]

Thanks for the report!

Can you try the upstream deb packages
(https://www.libreoffice.org/download/download/) and tell us whether
they suffer from the same problem.

If you don't mind trying the snap package too (sudo snap install
libreoffice && snap run libreoffice), I'd be interested in knowing
whether it's affected.

Also, please run "apport-collect 1811530" to attach system information
to this bug. Thanks!

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

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

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

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

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

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

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

  It seems to be connected wit hardware acceleration, that is greyed
  out. The newest appimage of LibreOffice is working as expected

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

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

[Desktop-packages] [Bug 1025839] Re: Printing multiple copies submits multiple separate jobs (should submit one job)

[Olivier Tilloy]

Randall, that's a very old bug that was marked fixed almost 4 years ago.
I'd suggest filing a new bug with a detailed description of the problem.

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

Title:
  Printing multiple copies submits multiple separate jobs (should submit
  one job)

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  In the print dialog, if "Number of Copies" is set to 50 then 50
  separate, independent print jobs are spooled.  It should submit a
  single print job, specifying 50 copies.   This will allow the printer
  to do the replication if it can (all Postscript printers can).

  This is important because:
   
1) Submitting a separate jobs for each copy causes the page(s) to be 
rendered again and again,
with a drastic reduction in through-put.   

   This is CRUCIAL if the pages contain complex graphics or images which 
take a long time to render
   or transmit to the printer:   A one-minute delay for the first of 50 
copies is okay, but 1 minute for 
   *each* of 50 copies is intolerable.

2) If the print job was a mistake, it is virtually impossible to stop the 
printer.  Pressing the cancel
button on the printer cancels just one copy, but after a little while 
the next one starts printing...

3) It is very inconvenient to cancel the job in CUPS, with 50 separate 
jobs, without affecting other
unrelated jobs in the queue (you can cancel all jobs in the queue at 
once, or one at a time).

  Note that CUPS has always supported a "number of copies" option at the 
command-line level.
  For example
 lpr '-#50'  file.pdf
  prints 50 copies of the file, rendering it once only.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33
  Uname: Linux 3.0.0-22-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Jul 17 11:49:58 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1025839/+subscriptions

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

[Desktop-packages] [Bug 1811511] Re: package libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1 failed to install/upgrade: new libreoffice-sdbc-firebird package pre-installation script subproces

[Olivier Tilloy]

Try removing and re-installing libreoffice-sdbc-firebird:

sudo apt remove --purge libreoffice-sdbc-firebird
sudo apt install libreoffice-sdbc-firebird

Does that resolve the issue?

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

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

Title:
  package libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1
  failed to install/upgrade: new libreoffice-sdbc-firebird package pre-
  installation script subprocess returned error exit status 1

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  after upgrading to the system version 18.04.1, this error is issued.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Tue Jan  8 01:36:58 2019
  Dependencies:
   
  ErrorMessage: new libreoffice-sdbc-firebird package pre-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-08-30 (1230 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice
  Title: package libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1 
failed to install/upgrade: new libreoffice-sdbc-firebird package 
pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-01-08 (4 days ago)

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

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

[Desktop-packages] [Bug 1811555] Re: package libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.

[Olivier Tilloy]

Can you check that this is not a "disk full" situation?

Otherwise, I'd suggest using the command line to remove libreoffice-
common and reinstalling it.

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

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

Title:
  package libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 failed to
  install/upgrade: unable to open
  '/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png
  .dpkg-new': Operation not permitted

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Libreoffice will not update, leading to seeral applications reporting
  errors when being installed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libreoffice-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jan 12 12:24:13 2019
  DpkgTerminalLog:
   Preparing to unpack 
.../libreoffice-common_1%3a6.0.7-0ubuntu0.18.04.2_all.deb ...
   Unpacking libreoffice-common (1:6.0.7-0ubuntu0.18.04.2) over 
(1:6.0.6-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_1%3a6.0.7-0ubuntu0.18.04.2_all.deb 
(--unpack):
unable to open 
'/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-10-07 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 failed to 
install/upgrade: unable to open 
'/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811577] Re: gnome-software or ubuntu software does not load the software

[Olivier Tilloy]

After reverting to the snapshot with which I was initially able to
observe the problem, gnome-software now loads correctly (the loading
screen is displayed for 4-5 seconds and then the home screen with the
lists of categories and software).

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => New

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

Title:
  gnome-software or ubuntu software does not load the software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When I open the gnome-software it loads infinitely, and nothing
  appears on the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:08:59 2019
  InstallationDate: Installed on 2019-01-10 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190110)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu1
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811577] Re: gnome-software or ubuntu software does not load the software

[Olivier Tilloy]

I have observed that in a fully up-to-date disco VM. gnome-software
would display a loading screen forever. After rebooting the VM, however,
it loaded instantly. Here is the relevant bits from journalctl from
today:

ene 14 07:27:50 discovm gnome-software[3787]: plugin appstream took 1,6 seconds 
to do setup
ene 14 07:27:51 discovm gnome-software[3787]: enabled plugins: 
desktop-categories, fwupd, os-release, packagekit, packagekit-local, 
packagekit-offline, packagekit-proxy, packagekit-refine-repos, 
packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, 
shell-extensions, ubuntuone, appstream, desktop-menu-path, hardcoded-blacklist, 
hardcoded-featured, hardcoded-popular, modalias, odrs, packagekit-refine, 
rewrite-resource, steam, packagekit-history, provenance, snap, systemd-updates, 
generic-updates, provenance-license, icons, key-colors, key-colors-metadata
ene 14 07:27:51 discovm gnome-software[3787]: disabled plugins: dpkg, dummy, 
repos, epiphany
ene 14 07:27:51 discovm dbus-daemon[555]: [system] Activating via systemd: 
service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.697' 
(uid=1000 pid=3787 comm="/usr/bin/gnome-software --gapplication-service " 
label="unconfined")
ene 14 07:27:59 discovm gnome-software[3787]: failed to rescan: No valid root 
node specified
ene 14 07:27:59 discovm gnome-software[3787]: failed to rescan: No valid root 
node specified
ene 14 07:28:13 discovm gnome-software[3787]: ignoring non-installed app GsApp: 
[0x7fa7240d8ea0]
ene 14 07:28:13 discovm gnome-software[3787]: ignoring non-installed app GsApp: 
[0x7fa72410a950]
ene 14 07:28:13 discovm gnome-software[3787]: ignoring non-installed app GsApp: 
[0x7fa7241142b0]
ene 14 07:29:45 discovm dbus-daemon[526]: [system] Activating via systemd: 
service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.338' 
(uid=1000 pid=1779 comm="gnome-software " label="unconfined")
ene 14 11:05:23 discovm gnome-software-service.desktop[2154]: Unable to acquire 
bus name 'org.gnome.Software'
ene 14 11:05:38 discovm dbus-daemon[526]: [system] Activating via systemd: 
service name='org.freedesktop.PackageKit' unit='packagekit.service' requested 
by ':1.338' (uid=1000 pid=1779 comm="gnome-software " label="unconfined")
ene 14 11:09:35 discovm dbus-daemon[555]: [system] Activating via systemd: 
service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.141' 
(uid=1000 pid=1536 comm="gnome-software " label="unconfined")
ene 14 11:10:04 discovm gnome-software-service.desktop[1934]: Unable to acquire 
bus name 'org.gnome.Software'

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

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

Title:
  gnome-software or ubuntu software does not load the software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When I open the gnome-software it loads infinitely, and nothing
  appears on the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:08:59 2019
  InstallationDate: Installed on 2019-01-10 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190110)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu1
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1800284] Re: digit transformed into exponent if moving between typing of two *

[Sebastien Bacher]

Thanks!

** Changed in: gnome-calculator (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  digit transformed into exponent if moving between typing of two *

Status in gnome-calculator package in Ubuntu:
  Triaged

Bug description:
  Open gnome-calculator

  Write (or compute) a number, let's type 9×9×9×9×9×9×9×9×9×9×9×9, enter.
  Or type directly 282429536481.

  What is observed :

  Now, We'll (try) to compute the product of all the digits.
  So move the caret after the first digit, type *
  Result (OK) : 2x|82429536481
  Move right :  2x8|2429536481
  Type another *, and observe, rather than adding a multiply sign, the digit is 
transformed into an exponent sign :
 2x^|2429536481

  What should be observed :
 2x8x|2429536481

  If you type anything else (like pressing space and deleting it), the
  bug doesn't occur.

  The bug is probably due to a bad test for converting ** into ^ :
  - first, it should detect that another key (arrow, shortcut, and even simple 
modifier should be counted as other keys) has been pressed. Or it should be 
based on the character preceding the caret, not the one previously pressed.
  - in any case, it should never replace anything than a *

  $ apt show gnome-calculator
  Package: gnome-calculator
  Version: 3.22.3-1
  Priority: optional
  Section: math
  Maintainer: Debian GNOME Maintainers 

  Installed-Size: 5 691 kB

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

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

[Desktop-packages] [Bug 1786492] Re: Update to nautilus 3.28 or newer

[Sebastien Bacher]

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

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

Title:
  Update to nautilus 3.28 or newer

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  This update is blocked on implementing a replacement for the desktop
  icons feature.

  See https://didrocks.fr/2018/01/23/welcome-to-the-ubuntu-bionic-age-
  nautilus-a-lts-and-desktop-icons/

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

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

[Desktop-packages] [Bug 1673230] Re: No power indicator for Logitech MX Anywhere 2 wireless mouse

[Sebastien Bacher]

Thank you for your bug report. Could you add the output of the 'upower
--dump' command with your mouse connected?

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

** Changed in: gnome-power-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  No power indicator for Logitech MX Anywhere 2 wireless mouse

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

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-power-manager:
Installiert:   3.18.0-1ubuntu1
Installationskandidat: 3.18.0-1ubuntu1
Versionstabelle:
   *** 3.18.0-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I would expect to have a battery symbol in the top right corner for the mouse 
as well as battery statistics as for internal laptop battery or previous 
Logitech MX Anywhere mouse.

  4) What happened instead
  No battery shown and statistics window only showing internal laptop battery.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-power-manager 3.18.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 15 19:44:21 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2016-05-15 (303 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1673230/+subscriptions

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

[Desktop-packages] [Bug 1811577] Re: gnome-software or ubuntu software does not load the software

[Sebastien Bacher]

Thank you for your bug report. Could you include your journalctl log
from the boot/session having the issue? Do you get any error if you try
to start it from a command line?

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

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

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

Title:
  gnome-software or ubuntu software does not load the software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  When I open the gnome-software it loads infinitely, and nothing
  appears on the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 10:08:59 2019
  InstallationDate: Installed on 2019-01-10 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190110)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu1
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811469] Re: package libgnome-desktop-3-17:amd64 3.28.2-0ubuntu1.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Sebastien Bacher]

thanks but the issue seems some sort of corruption rather than a bug in
the component

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Invalid

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

Title:
  package libgnome-desktop-3-17:amd64 3.28.2-0ubuntu1.2 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in gnome-desktop3 package in Ubuntu:
  Invalid

Bug description:
  not installed the atualization

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgnome-desktop-3-17:amd64 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Jan 11 19:22:08 2019
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2018-11-14 (57 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: gnome-desktop3
  Title: package libgnome-desktop-3-17:amd64 3.28.2-0ubuntu1.2 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811540] Re: gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure()

[Sebastien Bacher]

** Changed in: gvfs (Ubuntu)
   Importance: Medium => Low

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

Title:
  gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure()

Status in gvfs package in Ubuntu:
  New

Bug description:
  I started a live session using daily ISO 20190112 within KVM. I opened
  the Settings application, changed the Ubuntu dock icon size and when I
  closed Settings I saw a crash notification which led to the reporting
  of this bug report.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gvfs-daemons 1.38.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CasperVersion: 1.401
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 12 21:34:16 2019
  Disassembly: => 0x50: Cannot access memory at address 0x50
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190112)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.27 
/org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x50:  Cannot access memory at address 0x50
   PC (0x0050) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gvfsd-trash crashed with SIGSEGV in g_closure_invoke()
  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/gvfs/+bug/1811540/+subscriptions

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

[Desktop-packages] [Bug 1764724] Re: logn(x) parsed as log(n)(x)

[Sebastien Bacher]

Thanks!

** Changed in: gnome-calculator (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  logn(x) parsed as log(n)(x)

Status in gnome-calculator package in Ubuntu:
  Triaged

Bug description:
  "logn" is common notation for log base n, e.g. log2(x) is log base 2
  of x.

  gnome-calculator appears to always parse this notation as log(n)(x).
  So, log10(2) is log(10)(2) = 2, rather than log10(2) ~= 0.301.

  Arbitrary bases are already supported if the base is input as a
  subscript.  But, typing the base without subscript is common enough
  that it should be accounted for.  gnome-calculator should at least
  show an error like "function 'log10' is not defined," to avoid
  silently reporting incorrect results.

  
  Ubuntu 17.10, gnome-calculator 3.25.92.

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

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

[Desktop-packages] [Bug 1811615] Re: custom keyboard shortcut forgotten after restarting gnome

[Sebastien Bacher]

Thank you for your bug report. Could you add your journalctl log from a
session having the issue?

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

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

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

Title:
  custom keyboard shortcut forgotten after restarting gnome

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

Bug description:
  Ubuntu 18.04.1
  gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  mutter 3.28.3-2~ubuntu18.04.2
  I don't know what else is important

  I installed Ubuntu and changed the shortcut for closing a window (It's called 
"Cerrar la Ventana" in spanish) from Alt+F4 to Super+Q using 
gnome-control-center. It worked well
  Then I restarted gnome (Alt+F2 then "r") and it stopped working.
  It's weird because:
  1) My other custom keyboard shortcuts keep working
  2) gnome-control-center still reports it as being super+q
  3) if I try to "change it" to super+q again directly that doesn't fix it, but 
if I change it to another thing first and then back to super+q it works well.
  4) If I restart gnome again, it stops working again (just that shortcut, not 
the others)

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

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

[Desktop-packages] [Bug 1167442] Re: 13.04: cannot remove google account from ubuntu task bar (Email)

[Olivia Watson]

I am also getting Gmail error 007 with my Gmail account, I have searched
on the internet to find out the solution from
https://gmailtechnicalsupportnumbers.com/blog/tag/gmail-error-007/ and
got the reason but need a solution, yet not find the appropriate
solution regarding this error. Has anyone faced this issue or have an
idea regarding this kind of error? Kindly let me know.

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

Title:
  13.04: cannot remove google account from ubuntu task bar (Email)

Status in webapps-applications package in Ubuntu:
  Confirmed

Bug description:
  At the top of my screen is an envelope icon. When I click on it, it
  shows lots of information about my gmail account, and it becomes blue
  when there's new mail.

  If I visit "online-accounts" under system settings, I find no accounts
  listed at all.

  There is no apparent way to revoke Ubuntu's permission to access my
  gmail account.

  The obviously-enabled access is not properly reflected in the online-
  accounts dialogue.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubuntu-settings 12.10.7
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 10 12:37:23 2013
  InstallationDate: Installed on 2013-03-18 (22 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811588] Re: Seahorse doesn't show passwords anymore

[Daniele Besana (WP-OK)]

Hi Olivier,

Yes, that was it :)

Under "View" I see two categories (Personal / Trusted), but no way to assign 
the saved passwords to them.
Is it a bug?


Thanks

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

Title:
  Seahorse doesn't show passwords anymore

Status in seahorse package in Ubuntu:
  New

Bug description:
  After upgrade to Ubuntu 18.10, Seahorse doesn't show passwords
  anymore.

  Here the behavior:
  1. I open seahorse and I see Certificates, GPG keys, secure shell.
  2. After ~10 seconds, the Passwords section appears
  3. It contains two folders: Login and Default.
  4. Both folders are empty and saved passwords are not visible.

  I already removed "dbus-user-session" as suggested here:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825

  But it didn't solve.

  
  Thanks

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

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

[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported

[Łukasz Zemczak]

Ok, then indeed this doesn't likely seem to be any regression.
Releasing. Thanks!

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

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

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

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

[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.12.4-1ubuntu1.2

---
network-manager (1.12.4-1ubuntu1.2) cosmic; urgency=medium

  [ Alfonso Sanchez-Beato ]
  * Import some WoWLAN patches from the newer stable serie
(LP: #1781597)

 -- Sebastien Bacher   Mon, 10 Dec 2018 22:19:07
+0100

** Changed in: network-manager (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

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

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

[Desktop-packages] [Bug 1781597] Update Released

[Łukasz Zemczak]

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

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

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

[Łukasz Zemczak]

The SRUs have a few autopkgtest regressions reported against them in
various series. The libreoffice ones seem generally flaky, not sure
about openjdk-8 ones but what I'm worried about the  epson-inkjet-
printer-escpr ones. I re-ran the cosmic one against release and saw it
passing, so I'd like someone to take a look and make sure there's no
real regression here.

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

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Bionic:
  Fix Committed
Status in cups source package in Cosmic:
  Fix Committed
Status in cups source package in Disco:
  Fix Released
Status in cups package in Debian:
  Fix Released

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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