from:"Casey"

[Desktop-packages] [Bug 1915091] Re: Nautilus shows LXD storage pool in sidebar

2021-02-09 Thread Casey

Gladly.

** Attachment added: "gio-mount"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915091/+attachment/5462077/+files/gio-mount

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

Title:
  Nautilus shows LXD storage pool in sidebar

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs
  storage pool called "default". Now Nautilus shows a "default" device
  in the sidebar despite the loop device not being intended for users to
  directly interact with.

  System: Ubuntu 20.04.2

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

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

[Desktop-packages] [Bug 1915091] [NEW] Nautilus shows LXD storage pool in sidebar

2021-02-08 Thread Casey

Public bug reported:

I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs
storage pool called "default". Now Nautilus shows a "default" device in
the sidebar despite the loop device not being intended for users to
directly interact with.

System: Ubuntu 20.04.2

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

** Description changed:

- I recently set up LXD on Ubuntu 20.04 with a file-backed btrfs storage
- pool called "default". Now Nautilus shows a "default" device in the
- sidebar despite the loop device not being intended for users to directly
- interact with.
+ I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs
+ storage pool called "default". Now Nautilus shows a "default" device in
+ the sidebar despite the loop device not being intended for users to
+ directly interact with.
+ 
+ System: Ubuntu 20.04.2

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

Title:
  Nautilus shows LXD storage pool in sidebar

Status in nautilus package in Ubuntu:
  New

Bug description:
  I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs
  storage pool called "default". Now Nautilus shows a "default" device
  in the sidebar despite the loop device not being intended for users to
  directly interact with.

  System: Ubuntu 20.04.2

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

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

[Desktop-packages] [Bug 1866703] [NEW] gnome-shell crashes on lock screen

2020-03-09 Thread Casey Marshall

Public bug reported:

After latest focal updates, gnome-shell crashes and I lose my entire
session when I lock the screen.

c@slate:~$ dpkg -l | grep gnome-shell
ii  gnome-shell3.35.91-1ubuntu2 
   amd64graphical shell for the GNOME desktop

c@slate:~$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

syslog at the time of crash shows:

Mar  9 15:40:59 slate gnome-shell[14000]: ClutterBoxLayout child 
Gjs_ui_shellEntry_CapsLockWarning natural height: 0.00 < minimum 24.00 
for width 337.00
Mar  9 15:40:59 slate kernel: [ 6402.118795] traps: gnome-shell[14000] trap 
int3 ip:7f7562fb60d5 sp:7fff34854e80 error:0 in 
libglib-2.0.so.0.6400.0[7f7562f7a000+84000]
Mar  9 15:40:59 slate quasselclient[14674]: Error reading events from display: 
Broken pipe
Mar  9 15:40:59 slate gsd-power[14200]: Error reading events from display: 
Broken pipe
Mar  9 15:40:59 slate gsd-media-keys[14199]: Error reading events from display: 
Broken pipe
Mar  9 15:40:59 slate evolution-alarm[14258]: Error reading events from 
display: Broken pipe
Mar  9 15:40:59 slate gsd-wacom[14211]: Error reading events from display: 
Broken pipe
Mar  9 15:40:59 slate update-notifier[15178]: Error reading events from 
display: Broken pipe
Mar  9 15:40:59 slate gsd-color[14190]: Error reading events from display: 
Broken pipe
Mar  9 15:40:59 slate gsd-keyboard[14196]: Error reading events from display: 
Broken pipe
Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Main process exited, 
code=exited, status=1/FAILURE
Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Failed with result 
'exit-code'.
Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Main process exited, 
code=exited, status=1/FAILURE
Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Failed with result 
'exit-code'.
Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Main process 
exited, code=exited, status=1/FAILURE
Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Failed with result 
'exit-code'.
Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Main process exited, 
code=exited, status=1/FAILURE
Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Failed with result 
'exit-code'.
Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Keyboard handling.
Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Media keys handling.
Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Power management 
handling.
Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Wacom handling.
Mar  9 15:40:59 slate systemd[1660]: gnome-shell-wayland.service: Main process 
exited, code=dumped, status=5/TRAP
Mar  9 15:40:59 slate gnome-shell[14035]: (EE) failed to read Wayland events: 
Broken pipe
Mar  9 15:40:59 slate gsd-media-keys[16326]: X connection to :0 broken 
(explicit kill or server shutdown).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  9 15:49:14 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-08-26 (561 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-23 (46 days ago)

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


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

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

Title:
  gnome-shell crashes on lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After latest focal updates, gnome-shell crashes and I lose my entire
  session when I lock the screen.

  c@slate:~$ dpkg -l | grep gnome-shell
  ii  gnome-shell3.35.91-1ubuntu2   
 amd64graphical shell for the GNOME desktop

  c@slate:~$ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  syslog at the time of crash shows:

  Mar  9 15:40:59 slate gnome-shell[14000]: ClutterBoxLayout child 
Gjs_ui_shellEntry_CapsLockWarning natural height: 0.00 < minimum 24.00 
for width 337.00
  Mar  9 15:40:59 slate kernel: [ 6402.118795] traps: gnome-shell[14000] trap 
int3 ip:7f7562fb60d5 sp:7fff34854e80 error:0 in 
libglib-2.0.so.0.6400.0[7f7562f7a000+84000]
  Mar  9 15:40:59 slate quasselclient[14674]: Error reading events from 
display:

[Desktop-packages] [Bug 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04

2019-12-12 Thread Casey Boettcher

>From https://lwn.net/Articles/714710/

"The TIMER_STATS feature, which made some timer statistics available in
/proc/timer_stats, has been removed. It was seen as a security problem,
since it could leak process information across namespaces; the tracing
subsystem should be used to get this information instead."

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

Title:
  GNOME Power Statistics shows nothing on Ubuntu 18.04

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

Bug description:
  GNOME Power Statistics shows nothing on Ubuntu 18.04, just the "cannot
  enable timerstats" error. See the attached screenshot.

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

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

[Desktop-packages] [Bug 387957] Re: Improve Save As Dialog Box (focus issues)

2019-05-06 Thread Casey

I would like to note that this is still/again a problem in 2019 on
Ubuntu 19.04.  (I didn't notice it on 18.10, but maybe I just missed
it.)  I agree with pretty much everything that gdi2k wrote above,
particularly that the following seemingly simple change would remove a
significant annoyance for anyone who occasionally uses the mouse without
at all detracting from keyboard-only functionality:

"Reverting focus to the Name field if a folder is double-clicked using
the mouse (familiar Windows behaviour, which does not impact keyboard-
using advanced users in any way)."

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

Title:
  Improve Save As Dialog Box (focus issues)

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

Bug description:
  The save dialog box has the irritating habit of not focusing on the
  file name area once I have browsed to the location where I would like
  to save my document. This is done better in Windows.

  There are two main scenarios when saving a document where this
  behaviour annoys:

  Scanario 1 - Browsing to save location by double-clicking:  
  1. File -> Save As (to bring up the "Save" dialog box). 
  2. Double click on the folder in which you would like to save the document. 
  3. Notice that the focus is now in the folder list area, not on the file name 
area. 
  4. I now have to click in the file name area to be able to name my document. 

  In Windows, the focus is returned immediately to the file name box
  once a folder is double clicked, so the name can be typed and the
  document saved in one step.

  Scenario 2 - Browsing save location using the keyboard (find as you type):
  1. File -> Save As (to bring up the "Save" dialog box). 
  2. Click on the folder area so that folder names can be typed to find them. 
Hit enter to enter desired folder. 
  3. Within the folder, step 2 can be repeated for subfolders indefinitely. 
  4. Once the desired location has been reached, the user must use the mouse 
click in the file name area to name the file before saving. 

  In Windows, when using find as you type, although focus is retained by
  the folder area when entering a lower folder level (so that you can
  browse to another level using the keyboard if desired), jumping to the
  file name box is simply a matter of pressing tab ONCE. In Ubuntu, I
  have to reverse tab (shift-tab) around 10 times to get back to the
  file name box at the top of the screen, or use the mouse - most
  annoying.

  Solutions (copy the Windows behaviour): 
  1. If a folder is double clicked with the mouse, the focus should jump back 
to the file name box. 
  2. If a folder is entered into by pressing enter (on the keyboard), focus 
should remain in the folder area, but the file name box should only be a single 
tab away. 

  I understand that solution 2 is problematic in that tabbing would
  ordinarily jump to the next element (usually the "file type"
  dropdown), not back to the top of the screen.

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

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-12-09 Thread Casey

So, the error "client-error-not-authorized" is from CUPS. Can someone
shed light on that error?

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

The first two buttons are highlighted and would naturally seem to be
the first options to try, but they didn't actually work. While I was
able to browse the list of printers attached to the print server,
attempting to actually add the printer ended in an uninformative error
message as shown in the second screenshot.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

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

[Desktop-packages] [Bug 1129144] Re: Background can not be clicked in Files (Nautilus) 3.6.3, in listview mode

2018-12-07 Thread Casey

This problem was fixed in Nautilus 3.30. Is there any possibly of
backporting the patches to bionic?

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

Title:
  Background can not be clicked in Files (Nautilus) 3.6.3, in listview
  mode

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  In listview mode, Nautilus does not allow clicking on background, when
  browsing a folder with more files than a single page.

  This must be classified as a bug because:
  1. Background click is necessary to unselect a file;
  2. Background click is available in iconview mode, so it is a doubtful 
behavior;
  3. Users are accustomed to access context menu right clicking background in 
order to create folder, share folder, create file, etc;
  4. Files can't be dragged & dropped into current folder.

  Furthermore, it is a kind of regression, since this error has been
  corrected in a earlier version.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Mon Feb 18 11:04:34 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+296+84'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'173'
  InstallationDate: Installed on 2013-02-17 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130208)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1804954] Re: dconf overrides are not read by flatpaks on wayland sessions

2018-12-01 Thread Casey

Correction -- the issue of window controls is not specific to Wayland
and perhaps belongs in a separate bug.

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

Title:
  dconf overrides are not read by flatpaks on wayland sessions

Status in flatpak package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  "dconf supports distros installing override files into the system,
  then when queried dconf will look at user setting, then fallback to
  distro setting, then fallback to default setting. In a sandbox we can
  ask dconf for the user setting but we don't have disk access to the
  override files"

  So what this means is that on wayland flatpaks can't read the default
  overrides from the session (eg Ubuntu choosing Ambiance and Minimise,
  Maximise, Close etc) as it doesn't have permission to read the system
  files only user ones. (this doesn't affect X11 sessions as gtk reads
  from xsettings instead).

  This will be solved when the settings portal [0] is used in xdg-
  desktop-portal, as that runs on the host outside of the sandbox it is
  able to read the necessary files.

  # Workaround

  Install gnome-tweaks, change your theme to something else and then
  back to Ambiance. Also for the window controls change one of them from
  true to false to true. This will then write user settings to dconf
  which the flatpak's can then read.

  
  0 - https://github.com/flatpak/xdg-desktop-portal/pull/245

  
  === Original Description ===

  System: Ubuntu 18.04.1
  Flatpak version: 1.0.6-flatpak1~bionic (from 
https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak)

  Description: Flatpaks using GTK3 default to the Adwaita theme in a
  Wayland Gnome session. In Xorg sesions they are themed correctly. The
  attached screenshots demonstrate the same version of Gnome Builder
  running in Communitheme-Wayland and Communitheme-Xorg. However,
  flatpaks that use Qt5 (like KeepassXC) seem to be themed correctly
  under Wayland.

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

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

[Desktop-packages] [Bug 1804954] Re: dconf overrides are not read by flatpaks on wayland sessions

2018-12-01 Thread Casey

Thanks, that workaround does mostly work. However, the window controls
still don't look quite right even after disabling and enabling the
minimize and maximize buttons in Gnome Tweaks.

** Attachment added: "Screenshot from 2018-12-01 16-22-17.png"

https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1804954/+attachment/5218035/+files/Screenshot%20from%202018-12-01%2016-22-17.png

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

Title:
dconf overrides are not read by flatpaks on wayland sessions

Status in flatpak package in Ubuntu:
Invalid
Status in xdg-desktop-portal package in Ubuntu:
Confirmed

Bug description:
"dconf supports distros installing override files into the system,
then when queried dconf will look at user setting, then fallback to
distro setting, then fallback to default setting. In a sandbox we can
ask dconf for the user setting but we don't have disk access to the
override files"

So what this means is that on wayland flatpaks can't read the default
overrides from the session (eg Ubuntu choosing Ambiance and Minimise,
Maximise, Close etc) as it doesn't have permission to read the system
files only user ones. (this doesn't affect X11 sessions as gtk reads
from xsettings instead).

This will be solved when the settings portal [0] is used in xdg-
desktop-portal, as that runs on the host outside of the sandbox it is
able to read the necessary files.

# Workaround

Install gnome-tweaks, change your theme to something else and then
back to Ambiance. Also for the window controls change one of them from
true to false to true. This will then write user settings to dconf
which the flatpak's can then read.

0 - https://github.com/flatpak/xdg-desktop-portal/pull/245

=== Original Description ===

System: Ubuntu 18.04.1
Flatpak version: 1.0.6-flatpak1~bionic (from
https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak)

Description: Flatpaks using GTK3 default to the Adwaita theme in a
Wayland Gnome session. In Xorg sesions they are themed correctly. The
attached screenshots demonstrate the same version of Gnome Builder
running in Communitheme-Wayland and Communitheme-Xorg. However,
flatpaks that use Qt5 (like KeepassXC) seem to be themed correctly
under Wayland.

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Casey

Yes.

grep lpadmin /etc/group

lpadmin:x:116:casey

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Casey

Thanks for your followup.

journalctl | grep cups-pk-helper

yields exactly two entries from that day:

Nov 26 11:08:22 localhost.localdomain gnome-control-c[27707]: cups-pk-helper: 
addition of printer 1002 failed: client-error-not-authorized
Nov 26 16:33:53 localhost.localdomain gnome-control-c[7361]: cups-pk-helper: 
addition of printer 1002 failed: client-error-not-authorized

I can consistently reproduce this behavior. If I try to add another
printer the same error results and yields the journalctl entry

Nov 30 07:41:32 localhost.localdomain gnome-control-c[13550]: cups-pk-
helper: addition of printer 958_small failed: client-error-not-
authorized


Is there a way to run cups-pk-helper in a verbose or debugging mode?

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

Title:
  Print settings present two distinct interfaces for adding printers

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

Bug description:
  1. Running stock 18.04.1
  2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

  As shown in the first screenshot below, the print settings panel shows
  an "Add..." in the headerbar as well as "Add a printer..." and
  "Additional printer settings" in the main area.

  The first two buttons are highlighted and would naturally seem to be
  the first options to try, but they didn't actually work. While I was
  able to browse the list of printers attached to the print server,
  attempting to actually add the printer ended in an uninformative error
  message as shown in the second screenshot.

  On the other hand, "Additional printer settings" launches the old
  system-config-printer utility which did succeed in adding my desired
  printer.

  It is not at all obvious without trial and error which option one
  should choose to add a new printer.

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

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-29 Thread Casey

groups:
casey adm cdrom sudo dip plugdev lpadmin sambashare lxd

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-29 Thread Casey

apt policy cups-pk-helper reveals

Installed: 0.2.6-1ubuntu1.2

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-29 Thread Casey

Sure.

** Attachment added: "g-c-c.log"

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805438/+attachment/5217393/+files/g-c-c.log

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

[Desktop-packages] [Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-27 Thread Casey

** Attachment added: "Error"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805438/+attachment/5216781/+files/Screenshot%20from%202018-11-26%2016-33-59.png

** Tags added: ui

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

Title:
  Print settings present two distinct interfaces for adding printers

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

Bug description:
  1. Running stock 18.04.1
  2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

  As shown in the first screenshot below, the print settings panel shows
  an "Add..." in the headerbar as well as "Add a printer..." and
  "Additional printer settings" in the main area.

  The first two buttons are highlighted and would naturally seem to be
  the first options to try, but they didn't actually work. While I was
  able to browse the list of printers attached to the print server,
  attempting to actually add the printer ended in an uninformative error
  message as shown in the second screenshot.

  On the other hand, "Additional printer settings" launches the old
  system-config-printer utility which did succeed in adding my desired
  printer.

  It is not at all obvious without trial and error which option one
  should choose to add a new printer.

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

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

[Desktop-packages] [Bug 1805438] [NEW] Print settings present two distinct interfaces for adding printers

2018-11-27 Thread Casey

Public bug reported:

1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

The first two buttons are highlighted and would naturally seem to be the
first options to try, but they didn't actually work. While I was able to
browse the list of printers attached to the print server, attempting to
actually add the printer ended in an uninformative error message as
shown in the second screenshot.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one should
choose to add a new printer.

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

** Tags: ui

** Attachment added: "Screenshot from 2018-11-26 16-33-41.png"

https://bugs.launchpad.net/bugs/1805438/+attachment/5216780/+files/Screenshot%20from%202018-11-26%2016-33-41.png

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

Title:
Print settings present two distinct interfaces for adding printers

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

Bug description:
1. Running stock 18.04.1
2. gnome-control-center 3.28.2-0ubuntu0.18.04.2

As shown in the first screenshot below, the print settings panel shows
an "Add..." in the headerbar as well as "Add a printer..." and
"Additional printer settings" in the main area.

On the other hand, "Additional printer settings" launches the old
system-config-printer utility which did succeed in adding my desired
printer.

It is not at all obvious without trial and error which option one
should choose to add a new printer.

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

[Desktop-packages] [Bug 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()

2018-04-28 Thread Casey Matson-deKay

I am getting the same issue, same error. Crashes once I reach the
progress screen of 18.04 installation.

Syslog report:

..


Apr 28 20:26:54 ubuntu localechooser: info: Set debian-installer/locale = 
'en_CA.UTF-8'
Apr 28 20:26:54 ubuntu localechooser: info: System locale 
(debian-installer/locale) = 'en_CA.UTF-8'
Apr 28 20:26:54 ubuntu ubiquity: /usr/lib/ubiquity/localechooser/localechooser: 
910: [: C.UTF-8: unexpected operator
Apr 28 20:26:54 ubuntu ubiquity[3103]: debconffilter_done: ubi-timezone 
(current: ubi-timezone)
Apr 28 20:26:54 ubuntu ubiquity[3103]: Step_before = stepLocation
Apr 28 20:26:54 ubuntu partman: mke2fs 1.44.1 (24-Mar-2018)
Apr 28 20:26:54 ubuntu ubiquity[3103]: switched to page usersetup
Apr 28 20:26:54 ubuntu clear_partitions: Considering /home,/dev/nvme0n1p6.
Apr 28 20:26:54 ubuntu kernel: [  100.161039] EXT4-fs (nvme0n1p6): mounted 
filesystem with ordered data mode. Opts: (null)
Apr 28 20:26:54 ubuntu kernel: [  100.278116] EXT4-fs (nvme0n1p7): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
Apr 28 20:26:54 ubuntu kernel: [  100.296127] EXT4-fs (nvme0n1p6): mounted 
filesystem with ordered data mode. Opts: (null)
Apr 28 20:26:55 ubuntu ubiquity: File descriptor 3 (pipe:[67210]) leaked on pvs 
invocation. Parent PID 18458: /bin/sh
Apr 28 20:26:55 ubuntu ubiquity[3103]: debconffilter_done: 
ubiquity.components.partman_commit (current: ubi-usersetup)
Apr 28 20:26:55 ubuntu /install.py: keeping packages due to preseeding: 
icedtea6-plugin openoffice.org
Apr 28 20:26:55 ubuntu /install.py: keeping language packs for: en_US.UTF-8
Apr 28 20:26:56 ubuntu ubiquity: W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Could not resolve 
'archive.ubuntu.com'
Apr 28 20:26:56 ubuntu ubiquity: W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Could not 
resolve 'security.ubuntu.com'
Apr 28 20:26:56 ubuntu ubiquity: W: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Could not 
resolve 'archive.ubuntu.com'
Apr 28 20:26:56 ubuntu ubiquity: W: Some index files failed to download. They 
have been ignored, or old ones used instead.
Apr 28 20:26:56 ubuntu ubiquity: W: --force-yes is deprecated, use one of the 
options starting with --allow instead.
Apr 28 20:27:13 ubuntu ubiquity[3103]: debconffilter_done: ubi-usersetup 
(current: ubi-usersetup)
Apr 28 20:27:13 ubuntu ubiquity[3103]: Step_before = stepUserInfo
Apr 28 20:27:14 ubuntu kernel: [  119.884166] do_trap: 26 callbacks suppressed
Apr 28 20:27:14 ubuntu kernel: [  119.884168] traps: ubiquity[3103] trap int3 
ip:7ff0a1502c41 sp:7ffe0681d810 error:0 in 
libglib-2.0.so.0.5600.1[7ff0a14b1000+113000]
Apr 28 20:27:25 ubuntu /install.py: Exception during installation:
Apr 28 20:27:25 ubuntu /install.py: Traceback (most recent call last):
Apr 28 20:27:25 ubuntu /install.py:   File "/usr/share/ubiquity/install.py", 
line 765, in 
Apr 28 20:27:25 ubuntu /install.py: install.run()
Apr 28 20:27:25 ubuntu /install.py:   File "/usr/share/ubiquity/install.py", 
line 135, in run
Apr 28 20:27:25 ubuntu /install.py: self.copy_all()
Apr 28 20:27:25 ubuntu /install.py:   File "/usr/share/ubiquity/install.py", 
line 513, in copy_all
Apr 28 20:27:25 ubuntu /install.py: self.db.progress('SET', 10 + 
copy_progress)
Apr 28 20:27:25 ubuntu /install.py:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
Apr 28 20:27:25 ubuntu /install.py: lambda *args, **kw: 
self.command(command, *args, **kw))
Apr 28 20:27:25 ubuntu /install.py:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Apr 28 20:27:25 ubuntu /install.py: status = int(status)
Apr 28 20:27:25 ubuntu /install.py: ValueError: invalid literal for int() with 
base 10: ''
Apr 28 20:27:25 ubuntu /install.py: 
Apr 28 20:27:25 ubuntu nautilus-autostart.desktop[2103]: Trace/breakpoint trap 
(core dumped)
Apr 28 20:27:31 ubuntu dbus-daemon[1666]: [session uid=999 pid=1666] Activating 
via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.81' (uid=999 pid=18835 
comm="/usr/bin/gnome-terminal.real " label="unconfined")
Apr 28 20:27:31 ubuntu systemd[1622]: Starting GNOME Terminal Server...
Apr 28 20:27:31 ubuntu dbus-daemon[1666]: [session uid=999 pid=1666] 
Successfully activated service 'org.gnome.Terminal'
Apr 28 20:27:31 ubuntu systemd[1622]: Started GNOME Terminal Server.

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

Title:
  ubiquity crashed with signal 5 in _XEventsQueued()

Status in glib2.0 package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Triaged
Status in glib2.0 source package in Bionic:
  Incomplete
Status in ubiquity source package in Bionic:
  Triaged

Bug description:
  Crashed in a VM in the middle of installation. The host is Bionic up

[Desktop-packages] [Bug 1710059] Re: Theming issue when searching in Thunderbird

2018-03-05 Thread Casey

This bug happens also with the default Ambiance theme on Ubuntu 17.10.
See attached screenshot.

** Attachment added: "thunderbird_low_contrast.png"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1710059/+attachment/5070119/+files/thunderbird_low_contrast.png

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

Title:
  Theming issue when searching in Thunderbird

Status in ubuntu-mate:
  Invalid
Status in thunderbird package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid

Bug description:
  Affecting the dropdown list of the search input field in the top right
  of Thunderbird.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1710059/+subscriptions

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

[Desktop-packages] [Bug 1704765] Re: can't drag file from desktop to folder window on Artful

2018-02-11 Thread Casey

Confirming that I'm seeing this as well. Switched to running Xorg to
avoid it. Xorg drag and drop across screens results in a copy instead of
a move but at least doesn't freeze.

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

Title:
  can't drag file from desktop to folder window on Artful

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

Bug description:
  I'm running Ubuntu 17.10 (Artful).  If I create a text file on my
  desktop and then attempt to drag it into a Nautilus folder window, it
  fails: when I release the mouse cursor over the folder window nothing
  happens and the file is not moved.

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

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

[Desktop-packages] [Bug 1722256] Re: Wifi connection status icon shows a "?" when connected

2018-02-01 Thread Casey

Confirming that adding dns=default to
/etc/NetworkManager/NetworkManager.conf solved the problem for me as
well - thank you Scorpius!

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

Title:
  Wifi connection status icon shows a "?" when connected

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

Bug description:
  Wifi connection status icon on the top bar shows a "?" even when connected to 
a wifi network.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-28 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.26.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-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/gnome-shell/+bug/1722256/+subscriptions

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

[Desktop-packages] [Bug 1712571] Re: xwayland does not support wacom tablets

2017-09-12 Thread Casey

The implementation looks promising but still seems incomplete. For
instance, Xournal still works much better in a real X11 session than
under XWayland. In the latter setting, the cursor does not display as
the stylus hovers over the tablet so it's not possible to see where one
is drawing until one actually applies pressure and and starts inking.

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

Title:
  xwayland does not support wacom tablets

Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  When running a session under Wayland, my Wacom tablet does not work
  properly in applications using xwayland (the cursor moves, but
  clicking does not work).

  This is a known issue that apparently has been fixed in xorg-server
  1.20 branch - see the upstream bug at
  https://bugs.freedesktop.org/show_bug.cgi?id=99411 and also
  https://bugzilla.redhat.com/show_bug.cgi?id=1397898.

  Is xorg-server 1.20 likely to be released in time for Artful or can
  the wacom patches be backported for xwayland?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.3-1ubuntu3
  Uname: Linux 4.13.0-041300rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 20:59:41 2017
  DistUpgraded: 2017-08-17 08:53:31,141 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.12.0-11-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-041300rc6-generic, x86_64: installed
   nvidia-384, 384.59, 4.12.0-11-generic, x86_64: installed
   nvidia-384, 384.59, 4.13.0-041300rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-08-16 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-041300rc6-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=7
  Renderer: Software
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-08-17 (6 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Aug 17 08:57:12 2017
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1682436] [NEW] Location Options button gets stuck

2017-04-13 Thread Casey

Public bug reported:

Running Ubuntu 16.04 with GNOME shell and Nautilus 3.14.3. I was able to
reproduce this bug in a fresh 16.04 VM.

After clicking the Location Options toggle (the hamburger menu) once,
the button does not deactivate on subsequent clicks. See the attached
image.

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

** Attachment added: "Screenshot from 2017-04-13 06-22-53.png"

https://bugs.launchpad.net/bugs/1682436/+attachment/4861275/+files/Screenshot%20from%202017-04-13%2006-22-53.png

** Description changed:

- Running Ubuntu 16.04 with Nautilus 3.14.3. I was able to reproduce this
- bug in a fresh 16.04 VM.
+ Running Ubuntu 16.04 with GNOME shell and Nautilus 3.14.3. I was able to
+ reproduce this bug in a fresh 16.04 VM.

After clicking the Location Options toggle (the hamburger menu) once,
the button does not deactivate on subsequent clicks. See the attached
image.

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

Title:
Location Options button gets stuck

Status in nautilus package in Ubuntu:
New

Bug description:
Running Ubuntu 16.04 with GNOME shell and Nautilus 3.14.3. I was able
to reproduce this bug in a fresh 16.04 VM.

After clicking the Location Options toggle (the hamburger menu) once,
the button does not deactivate on subsequent clicks. See the attached
image.

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

[Desktop-packages] [Bug 1630884] [NEW] Xorg freeze; mouse moves, but no mouse click or keyboard response

2016-10-06 Thread Casey R Hickerson

Public bug reported:

I've encountered this issue on several fresh installations of Ubuntu
16.04.1 on different machines. Typically, the machine becomes
unresponsive to the keyboard presses or to mouse clicks; however, it
does respond to mouse movement. I am unable to open a text console to
manipulate processes, and I am forced to hard restart the machine.
During the most recent instance, I noticed that the mouse cursor would
change in response to its location on the screen while

The issue most often occurs about 3-5 minutes after Chromium has been
opened, but it has also occurred without Chromium being installed.
Moreover, it as occurred while using Xfce and GNOME 3 and while using
open source and proprietary video drivers.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Oct  6 00:04:47 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Dell GF119M [NVS 4200M] [1028:0493]
InstallationDate: Installed on 2016-10-06 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
MachineType: Dell Inc. Latitude E6420
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=3c7f4e14-5817-44b1-adbb-1666f8c29348 ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A23
dmi.board.asset.tag: TSI3251
dmi.board.name: 032T9K
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.asset.tag: TSI3251
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd01/04/2016:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6420
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: amd64 apport-bug freeze ubuntu xenial

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

Title:
  Xorg freeze; mouse moves, but no mouse click or keyboard response

Status in xorg package in Ubuntu:
  New

Bug description:
  I've encountered this issue on several fresh installations of Ubuntu
  16.04.1 on different machines. Typically, the machine becomes
  unresponsive to the keyboard presses or to mouse clicks; however, it
  does respond to mouse movement. I am unable to open a text console to
  manipulate processes, and I am forced to hard restart the machine.
  During the most recent instance, I noticed that the mouse cursor would
  change in response to its location on the screen while

  The issue most often occurs about 3-5 minutes after Chromium has been
  opened, but it has also occurred without Chromium being installed.
  Moreover, it as occurred while using Xfce and GNOME 3 and while using
  open source and proprietary video drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Oct  6 00:04:47 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu

[Desktop-packages] [Bug 1572679] Re: screen flickering and tearing kwin nouveau kubuntu 16.04

2016-06-23 Thread Casey

I am dealing with the same flickering issue as described above, and am
using the same hardware. If there is any information I can provide,
please let me know.

Casey

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

Title:
  screen flickering and tearing kwin nouveau kubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  The bug I see on my Dell D830 (8GB RAM, Nvidia G86M [Quadro NVS 140M]
  (rev a1)) with nouveau driver using Kubuntu 16.04.

  After login everything seems to work fine for roughly 2 minutes. After
  that flickering and tearing starts (when moving windows around with
  the mouse) and gets more intense until the screen is full of "color-
  blobs" (which means: one cannot see anything anymore).  Starting a
  flash movie in Firefox provokes immediate tearing and flickering.

  Restarting the kwin compositor helps - for another 2 minutes, then the
  whole problem starts to catch on momentum again. I tried everything
  mentioned here:

  http://askubuntu.com/questions/672007/flickering-in-kde-plasma-5-4

  the only thing that helps for a longer period of time is turning off
  compositing completely.

  I am unsure where to further look for the problem: Is it kwin? xorg?
  nouveau? All of them? Whatever? The logs I checked (xorg, syslog,
  dmesg etc.) contain nothing that I can make sense of.

  I'd appreciate any hint to where (and: what) to look (for) and which
  more specific information to collect ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 20 19:22:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-22 (28 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160320)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-24-generic, x86_64: installed
   vboxhost, 5.0.22, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.22, 4.4.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation G86M [Quadro NVS 140M] [10de:0429] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G86M [Quadro NVS 140M] [1028:01fe]
  InstallationDate: Installed on 2016-05-02 (46 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude D830
  NonfreeKernelModules: wl
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5f4a29b4-76d7-473a-948b-6e916e79e20f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Tags:  xenial kubuntu
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/21/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0UY141
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd07/21/2008:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D830
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-19 Thread Casey Marshall

I can work around this with my custom build of pcscd with udev disabled,
but it seems that this issue will still affect Debian and Ubuntu users
who install the package.

Can we mark this bug as Confirmed, since my symptoms are so similar to
the descriptions in the Debian bug[1] you've linked above?

Anything else I can do to help?

Thanks,
Casey

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-06 Thread Casey Marshall

Recompiling with --disable-libudev gets rid of the 100% CPU problem and
I can still use my smartcard.

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-04 Thread Casey Marshall

** Attachment added: "pcscd binary and core dump"
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588521/+files/pcscd-core-bin.tar.bz2

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-04 Thread Casey Marshall

Here's a core dump with the corresponding pcscd binary I built from
source, which was taken in the above-mentioned gdb session.

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-04 Thread Casey Marshall

Ran it with gdb, reproduced, and then interrupted when it started
consuming 100% CPU:

Thread 1 "pcscd" received signal SIGINT, Interrupt.
0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00411cfd in ProcessEventsServer 
(pdwClientID=pdwClientID@entry=0x7fffe49c) at winscard_msg_srv.c:223
#2  0x004037f9 in SVCServiceRunLoop () at pcscdaemon.c:128
#3  main (argc=, argv=) at pcscdaemon.c:685
(gdb) info threads
  Id   Target Id Frame 
* 1Thread 0x77fb9740 (LWP 18298) "pcscd" 0x774e2853 in select 
() from /lib/x86_64-linux-gnu/libc.so.6
  2Thread 0x76fb0700 (LWP 18302) "pcscd" 0x774e09ed in poll () 
from /lib/x86_64-linux-gnu/libc.so.6
  3Thread 0x767af700 (LWP 18303) "pcscd" 0x774e09ed in poll () 
from /lib/x86_64-linux-gnu/libc.so.6
  4Thread 0x75fae700 (LWP 18304) "pcscd" 0x774e09ed in poll () 
from /lib/x86_64-linux-gnu/libc.so.6
  5Thread 0x757ad700 (LWP 18305) "pcscd" 0x774e09ed in poll () 
from /lib/x86_64-linux-gnu/libc.so.6
(gdb) thread 2
[Switching to thread 2 (Thread 0x76fb0700 (LWP 18302))]
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x76fc064c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x777b666a in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#3  0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) thread 3
[Switching to thread 3 (Thread 0x767af700 (LWP 18303))]
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x76fc064c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x777b666a in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#3  0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) thread 4
[Switching to thread 4 (Thread 0x75fae700 (LWP 18304))]
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x76fb9bc5 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x76fbab53 in libusb_handle_events_timeout_completed () from 
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#3  0x76fbac3f in libusb_handle_events () from 
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#4  0x771d64bc in ?? () from 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
#5  0x771d0b83 in ?? () from 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
#6  0x004064db in EHStatusHandlerThread (rContext=0x61f010) at 
eventhandler.c:464
#7  0x777b666a in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) thread 5
[Switching to thread 5 (Thread 0x757ad700 (LWP 18305))]
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x0040eeaa in poll (__timeout=-1, __nfds=1, __fds=0x757aced0) 
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  HPEstablishUSBNotifications (arg=0x649910) at hotplug_libudev.c:624
#3  0x777b666a in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-04 Thread Casey Marshall

Oh, here's /var/log/syslog from unplugging and replugging in my camera.
I Ctrl-C killed pcscd after it went to 100% each time.

pcscd segfaulted.

Mar  4 12:04:11 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug 
level=debug
Mar  4 12:04:13 mawhrin-skel kernel: [14604.513268] usb 3-1: USB disconnect, 
device number 6
Mar  4 12:04:13 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools.
Mar  4 12:04:13 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools.
Mar  4 12:04:13 mawhrin-skel laptop-mode: Laptop mode
Mar  4 12:04:13 mawhrin-skel laptop_mode[17937]: Laptop mode
Mar  4 12:04:13 mawhrin-skel laptop-mode: enabled, not active [unchanged]
Mar  4 12:04:13 mawhrin-skel laptop_mode[17937]: enabled, not active [unchanged]
Mar  4 12:04:53 mawhrin-skel systemd[1]: Starting Laptop Mode Tools - Battery 
Polling Service...
Mar  4 12:04:53 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools.
Mar  4 12:04:53 mawhrin-skel systemd[1]: Started Laptop Mode Tools - Battery 
Polling Service.
Mar  4 12:04:53 mawhrin-skel laptop-mode: Laptop mode
Mar  4 12:04:53 mawhrin-skel laptop_mode[17997]: Laptop mode
Mar  4 12:04:53 mawhrin-skel laptop-mode: enabled, not active [unchanged]
Mar  4 12:04:53 mawhrin-skel laptop_mode[17997]: enabled, not active [unchanged]
Mar  4 12:04:53 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools.
Mar  4 12:05:01 mawhrin-skel CRON[18049]: (root) CMD ([ -x /usr/sbin/dma ] && 
/usr/sbin/dma -q1)
Mar  4 12:05:17 mawhrin-skel kernel: [14668.018203] pcscd[17921]: segfault at 
7f447696064c ip 7f447696064c sp 7f447694fed0 error 14 in 
libc-2.21.so[7f4476d85000+1c]
Mar  4 12:05:20 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug 
level=debug
Mar  4 12:05:30 mawhrin-skel kernel: [14681.443071] usb 3-1: new high-speed USB 
device number 7 using xhci_hcd
Mar  4 12:05:31 mawhrin-skel kernel: [14681.844167] usb 3-1: New USB device 
found, idVendor=046d, idProduct=0825
Mar  4 12:05:31 mawhrin-skel kernel: [14681.844175] usb 3-1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=2
Mar  4 12:05:31 mawhrin-skel kernel: [14681.844179] usb 3-1: SerialNumber: 
DD923C60
Mar  4 12:05:31 mawhrin-skel kernel: [14681.845342] uvcvideo: Found UVC 1.00 
device  (046d:0825)
Mar  4 12:05:31 mawhrin-skel kernel: [14681.937806] input: UVC Camera 
(046d:0825) as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/input/input19
Mar  4 12:05:32 mawhrin-skel kernel: [14683.279489] usb 3-1: set resolution 
quirk: cval->res = 384
Mar  4 12:05:32 mawhrin-skel mtp-probe: checking bus 3, device 7: 
"/sys/devices/pci:00/:00:14.0/usb3/3-1"
Mar  4 12:05:32 mawhrin-skel mtp-probe: bus: 3, device: 7 was not an MTP device
Mar  4 12:05:32 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools.
Mar  4 12:05:32 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools.
Mar  4 12:05:32 mawhrin-skel systemd[1]: message repeated 3 times: [ Reloaded 
Laptop Mode Tools.]
Mar  4 12:05:32 mawhrin-skel systemd-udevd[18064]: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa restore 1' failed with exit code 99.
Mar  4 12:05:32 mawhrin-skel laptop-mode: Laptop mode
Mar  4 12:05:32 mawhrin-skel laptop_mode[18067]: Laptop mode
Mar  4 12:05:32 mawhrin-skel laptop-mode: enabled, not active [unchanged]
Mar  4 12:05:32 mawhrin-skel laptop_mode[18067]: enabled, not active [unchanged]
Mar  4 12:05:32 mawhrin-skel pulseaudio[6720]: [pulseaudio] source.c: Default 
and alternate sample rates are the same.
Mar  4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Supervising 3 threads of 1 
processes of 1 users.
Mar  4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Successfully made thread 18136 
of process 6720 (n/a) owned by '1000' RT at priority 5.
Mar  4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Supervising 4 threads of 1 
processes of 1 users.
Mar  4 12:07:09 mawhrin-skel kernel: [14780.487379] pcscd[18060]: segfault at 
7f74fedfa64c ip 7f74fedfa64c sp 7f74fede9ed0 error 14 in 
libc-2.21.so[7f74ff21f000+1c]
Mar  4 12:07:43 mawhrin-skel systemd[1]: Starting Laptop Mode Tools - Battery 
Polling Service...
Mar  4 12:07:43 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools.
Mar  4 12:07:43 mawhrin-skel systemd[1]: Started Laptop Mode Tools - Battery 
Polling Service.
Mar  4 12:07:43 mawhrin-skel laptop-mode: Laptop mode
Mar  4 12:07:43 mawhrin-skel laptop_mode[18161]: Laptop mode
Mar  4 12:07:43 mawhrin-skel laptop-mode: enabled, not active [unchanged]
Mar  4 12:07:43 mawhrin-skel laptop_mode[18161]: enabled, not active [unchanged]
Mar  4 12:07:43 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools.

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-04 Thread Casey Marshall

It starts consuming 100% CPU after this:

02341452 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0217 hotplug_libudev.c:619:HPEstablishUSBNotifications()
0068 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0149 hotplug_libudev.c:619:HPEstablishUSBNotifications()
2713 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0152 hotplug_libudev.c:619:HPEstablishUSBNotifications()
00020583 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0143 hotplug_libudev.c:619:HPEstablishUSBNotifications()
02634822 ifdhandler.c:1143:IFDHPowerICC() action: PowerDown, 
usb:1050/0115:libudev:1:/dev/bus/usb/003/002 (lun: 0)
0091 eventhandler.c:479:EHStatusHandlerThread() powerState: 
POWER_STATE_UNPOWERED

or this:

05000574 ifdhandler.c:1143:IFDHPowerICC() action: PowerDown, 
usb:1050/0115:libudev:1:/dev/bus/usb/003/002 (lun: 0)
0261 eventhandler.c:479:EHStatusHandlerThread() powerState: 
POWER_STATE_UNPOWERED
06904552 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add
0242 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 
0x046D, PID: 0x0825, path: /dev/bus/usb/003/007
0015 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a 
supported smart card reader
0017 hotplug_libudev.c:619:HPEstablishUSBNotifications()
00022668 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add
0214 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 
0x046D, PID: 0x0825, path: /dev/bus/usb/003/007
0013 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a 
supported smart card reader
0017 hotplug_libudev.c:619:HPEstablishUSBNotifications()
6048 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add
0207 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 
0x046D, PID: 0x0825, path: /dev/bus/usb/003/007
0014 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a 
supported smart card reader
0015 hotplug_libudev.c:619:HPEstablishUSBNotifications()
00014614 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add
0200 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 
0x046D, PID: 0x0825, path: /dev/bus/usb/003/007
0016 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a 
supported smart card reader
0014 hotplug_libudev.c:619:HPEstablishUSBNotifications()

Basically, if I plug or unplug a USB device, pcscd immediately starting
using 100% CPU.

Let me know if there is anything else I can send you to help you debug.

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-02 Thread Casey Marshall

I ran pcscd as you suggested, capturing output. Made sure the smart card
was working by using my SSH key. I was then able to reproduce the 100%
cpu condition by plugging in my Logitech USB webcam.

Attached the output, but I redacted the hex dumps before posting here
because I'm not sure if they contain sensitive information. Let me know
if you need the original.

** Attachment added: "pcscd debug output (redacted)"

https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4587143/+files/pcscd.log.redacted

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

Title:
Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
New

Bug description:
In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND

27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03
/usr/sbin/pcscd --foreground --auto-exit

I get this about once a day since installing xenial. I can't quite
connect it to any specific event on the system, it just seems to
happen sporadically -- fan turns on, I run top, and there it is again.

Never had this issue on same hardware incl. smartcard with trusty.

I wonder if it might be this? https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=718473

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

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-01 Thread Casey Marshall

This is what I've got installed ^^

c@mawhrin-skel:~/omnibus-layers$ dpkg -l | grep pcscd
ii  pcscd   1.8.14-1ubuntu1 
  amd64Middleware to access a smart card using PC/SC 
(daemon side)

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1551897] [NEW] Excessive CPU utilization

2016-03-01 Thread Casey Marshall

Public bug reported:

In xenial, pcscd CPU utilization occasionally goes haywire:

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 

  
27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

I get this about once a day since installing xenial. I can't quite
connect it to any specific event on the system, it just seems to happen
sporadically -- fan turns on, I run top, and there it is again.

Never had this issue on same hardware incl. smartcard with trusty.

I wonder if it might be this? https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=718473

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Desktop-packages] [Bug 1516340] [NEW] make keyboard shortcut to quit more discoverable

2015-11-14 Thread Casey

Public bug reported:

Currently, ctrl-w closes the current settings module while ctrl-q quits
gnome control center altogether. However, the user has no way of
discovering this except for trial and error. At the very least, the
"quit" option in the menu should be labeled with ctrl-q.

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


** Tags: needs-design

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

Title:
  make keyboard shortcut to quit more discoverable

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

Bug description:
  Currently, ctrl-w closes the current settings module while ctrl-q
  quits gnome control center altogether. However, the user has no way of
  discovering this except for trial and error. At the very least, the
  "quit" option in the menu should be labeled with ctrl-q.

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

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

[Desktop-packages] [Bug 1504792] [NEW] nm applet displays inaccurate notification when user disconnects from VPN

2015-10-10 Thread Casey

Public bug reported:

When the user voluntarily disconnects from a vpn connection, network
manager displays the error message  "VPN Connection Failed." See the
attached screenshot. However, since a disconnection in this case is a
success, not a failure, something more neutral like "Successfully
disconnected" would be more appropriate.

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: needs-design

** Attachment added: "screenshot3.png"
   
https://bugs.launchpad.net/bugs/1504792/+attachment/4490835/+files/screenshot3.png

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

Title:
  nm applet displays inaccurate notification when user disconnects from
  VPN

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

Bug description:
  When the user voluntarily disconnects from a vpn connection, network
  manager displays the error message  "VPN Connection Failed." See the
  attached screenshot. However, since a disconnection in this case is a
  success, not a failure, something more neutral like "Successfully
  disconnected" would be more appropriate.

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

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

[Desktop-packages] [Bug 1502889] [NEW] VPN icon is conjoined to wired network icon

2015-10-05 Thread Casey

Public bug reported:

When I am connected to a VPN through a wired network, the lock icon
partly overlaps with the down arrow as shown in the attachment. Since
both icons are white, the result is an unsightly conjoined blob. There
should be some space between the two icons.

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Conjoined icons"
   
https://bugs.launchpad.net/bugs/1502889/+attachment/4484663/+files/screenshot.png

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

Title:
  VPN icon is conjoined to wired network icon

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

Bug description:
  When I am connected to a VPN through a wired network, the lock icon
  partly overlaps with the down arrow as shown in the attachment. Since
  both icons are white, the result is an unsightly conjoined blob. There
  should be some space between the two icons.

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

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

[Desktop-packages] [Bug 1460838] [NEW] headphones won't work unless pavucontrol is installed and the internal microphone is unmuted from there

2015-06-01 Thread Casey Hofford

Public bug reported:

The issue is as described in the summary. My device is now working fine,
however this fix is clearly some sort of bug, so I figured it would be
helpful to report. If someone feels like working on it and wants any log
files just let me know! Not sure what would actually be helpful.I had
this issue in both 14.10 and 15.04 with the most recent releases of
pulseaudio and alsamixer.

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

** Description changed:

  The issue is as described in the summary. My device is now working fine,
  however this fix is clearly some sort of bug, so I figured it would be
  helpful to report. If someone feels like working on it and wants any log
- files just let me know! Not sure what would actually be helpful.
+ files just let me know! Not sure what would actually be helpful.I had
+ this issue in both 14.10 and 15.04 with the most recent releases of
+ pulseaudio and alsamixer.

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

Title:
  headphones won't work unless pavucontrol is installed and the internal
  microphone is unmuted from there

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The issue is as described in the summary. My device is now working
  fine, however this fix is clearly some sort of bug, so I figured it
  would be helpful to report. If someone feels like working on it and
  wants any log files just let me know! Not sure what would actually be
  helpful.I had this issue in both 14.10 and 15.04 with the most recent
  releases of pulseaudio and alsamixer.

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

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

[Desktop-packages] [Bug 1368303] [NEW] Enhanced Zoom Desktop only works if mouse pointer is over the active window

2014-09-11 Thread Casey Burkhardt

Public bug reported:

I have my Enhanced Zoom Desktop enabled and setup as follows:

Zoom In Button: ControlSuperButton4
Zoom Out Button: ControlSuperButton5
Enable focus tracking: Disabled

I've noticed that since upgrading to 14.04, I can only use the zoom
functionality if my mouse cursor sits above the currently focused
window.  If, for example, I move my cursor to another monitor without
clicking to activate the window in that area, I cannot use my defined
shortcut to increase or decrease the magnification level.  The same is
true if I move my cursor outside the bounds of the currently focused
window within the same display.

I would expect that I should be able to increase or decrease the
magnification level of the display regardless of the mouse position
within it.  This appeared to be the case at least on 12.04.

$ lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04

$ apt-cache policy compiz
compiz:
  Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1
  Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1

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

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

Title:
  Enhanced Zoom Desktop only works if mouse pointer is over the active
  window

Status in “compiz” package in Ubuntu:
  New

Bug description:
  I have my Enhanced Zoom Desktop enabled and setup as follows:

  Zoom In Button: ControlSuperButton4
  Zoom Out Button: ControlSuperButton5
  Enable focus tracking: Disabled

  I've noticed that since upgrading to 14.04, I can only use the zoom
  functionality if my mouse cursor sits above the currently focused
  window.  If, for example, I move my cursor to another monitor without
  clicking to activate the window in that area, I cannot use my defined
  shortcut to increase or decrease the magnification level.  The same is
  true if I move my cursor outside the bounds of the currently focused
  window within the same display.

  I would expect that I should be able to increase or decrease the
  magnification level of the display regardless of the mouse position
  within it.  This appeared to be the case at least on 12.04.

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  $ apt-cache policy compiz
  compiz:
Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1
Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1

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

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

[Desktop-packages] [Bug 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep

2014-05-06 Thread Casey Earnshaw

Hello again

I did a dist-upgrade last night and it seems to have fixed the issue,
although I've only had time to check it twice today before I had to rush
off to work!

Thank you very much!

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

Title:
  Ubuntu 14.04 blank screen after wakeup from sleep

Status in “linux-lts-trusty” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-ati” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Samsung Serie 5 AMD notebook (find in attachment the hardware 
profile).
  OS: Ubuntu 14.04 (updated today).

  After wakeup the notebook from the sleep mode, the screen goes blank while 
the OS and the hardware is awake.
  (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system).

  This problem is not happening with the AMD property drivers (but they
  have another bug, i can't set up the brighness of the monitor).

  The problem in my opinion is related to this package:  xserver-xorg-
  video-ati.

  Changing quiet splash with nomodeset into /etc/default/grub makes
  the wakeup working, but the pc is really slow (can't be used), also
  after the normal start up.

  
  Best regards and have a good work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep

2014-05-06 Thread Casey Earnshaw

Yes, that's true, sorry false alarm from me,  but it really truly did
work this morning, but as soon as I got home same issue, I wish I knew
what I did right. I'm afraid I'm still very much a novice when it comes
to Linux, only did the switch a few months ago I don't know how to do an
information copy paste like others in this, but if I can get it to work
and it will help then I am more than happy to do so if it helps, I'll
need to know the commands though.

Thanks guys, and very best of luck with the fix! x

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

Title:
  Ubuntu 14.04 blank screen after wakeup from sleep

Status in “linux-lts-trusty” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-ati” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Samsung Serie 5 AMD notebook (find in attachment the hardware 
profile).
  OS: Ubuntu 14.04 (updated today).

  After wakeup the notebook from the sleep mode, the screen goes blank while 
the OS and the hardware is awake.
  (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system).

  This problem is not happening with the AMD property drivers (but they
  have another bug, i can't set up the brighness of the monitor).

  The problem in my opinion is related to this package:  xserver-xorg-
  video-ati.

  Changing quiet splash with nomodeset into /etc/default/grub makes
  the wakeup working, but the pc is really slow (can't be used), also
  after the normal start up.

  
  Best regards and have a good work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about

[Desktop-packages] [Bug 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep

2014-04-25 Thread Casey Earnshaw

I just wanted to confirm that I am getting this problem too running an
Asus Apire One D257.

On awake it lets me type in my password but it loads a completely blank
screen that doesn't go away, I can however drop into a command line with
ctrl alt and f1-f6

Hope this helps!

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

Title:
  Ubuntu 14.04 blank screen after wakeup from sleep

Status in “xserver-xorg-video-ati” package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Samsung Serie 5 AMD notebook (find in attachment the hardware 
profile).
  OS: Ubuntu 14.04 (updated today).

  After wakeup the notebook from the sleep mode, the screen goes blank while 
the OS and the hardware is awake.
  (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system).

  This problem is not happening with the AMD property drivers (but they
  have another bug, i can't set up the brighness of the monitor).

  The problem in my opinion is related to this package:  xserver-xorg-
  video-ati.

  Changing quiet splash with nomodeset into /etc/default/grub makes
  the wakeup working, but the pc is really slow (can't be used), also
  after the normal start up.

  
  Best regards and have a good work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 870717] Re: ubuntu-bug thunar

2013-02-24 Thread Casey Carson

Still exists in xubuntu 12.04.  Any plans to rectify?

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

Title:
  ubuntu-bug thunar

Status in “xdg-user-dirs” package in Ubuntu:
  Confirmed

Bug description:
  I am using Xubuntu 11.04 (amd64) and I have seen in thunar file
  manager (1.2.1) the following:

  In my personal account /home/user, the personal folder Downloads,
  that's the exact name, in thunar shortcuts it shows the name Download
  instead of Downloads.

  If I remove the shortcut and put Downloads again, it appears correctly.
  I just wondered why this by default?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/870717/+subscriptions

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

[Desktop-packages] [Bug 819310] Re: gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()

2012-09-09 Thread Casey Greene

12.10 with galaxy nexus here.

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

Title:
  gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  This happened after unmounting the camera from within nautilus. The
  camera was connected using the pictbridge mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gvfs-backends 1.9.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Aug  1 15:36:00 2011
  ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.3 
/org/gtk/gvfs/exec_spaw/3
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en
   LANG=en_DK.utf8
  SegvAnalysis:
   Segfault happened at: 0x7f335148548f:mov0x20(%rax),%rax
   PC (0x7f335148548f) ok
   source 0x20(%rax) (0xaaca) not located in a known VMA region 
(needed readable region)!
   destination %rax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_value_unset () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: Upgraded to oneiric on 2011-07-27 (5 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 990228] Re: sidebar minimum width too large

2012-08-25 Thread Casey Jao

While the minimum width still leaves a significant marging to the right
of the thumbnails, Kim's patch is a definite improvement.

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

Title:
  sidebar minimum width too large

Status in Evince document viewer:
  New
Status in “evince” package in Ubuntu:
  Triaged

Bug description:
  The minimum width of the thumbnail sidebar in evince 3.4 (running
  12.04 release) leaves large margins on both sides of the thumbnail. On
  a 1366x768 laptop screen, this whitespace takes away about an inch of
  horizontal screen width which could be more usefully allocated to the
  main preview window. The attached image shows a maximised evince
  window in Ubuntu 12.04, and exhibits the large amount of whitespace on
  each side of the thumbnails. By contrast, evince 2.30 on Debian 6.0
  lets me shrink the sidebar to fit the thumbnails snugly.

  
  Ubuntu version: 12.04
  Package version: Evince 3.4.0-0ubuntu1

  What you expected to happen:
  Evince should let me shrink the sidebars to the width of the thumbnails.

  What happened instead:
  The minimum width of the sidebar leaves a half inch of whitespace on each 
side of the thumbnail, which robs space from the actual preview window.

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

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

[Desktop-packages] [Bug 990228] [NEW] sidebar minimum width too large

2012-04-27 Thread Casey Jao

Public bug reported:

The minimum width of the thumbnail sidebar in evince 3.4 (running 12.04
release) leaves large margins on both sides of the thumbnail. On a
1366x768 laptop screen, this whitespace takes away about an inch of
horizontal screen width which could be more usefully allocated to the
main preview window. The attached image shows a maximised evince window
in Ubuntu 12.04, and exhibits the large amount of whitespace on each
side of the thumbnails. By contrast, evince 2.30 on Debian 6.0 lets me
shrink the sidebar to fit the thumbnails snugly.


Ubuntu version: 12.04
Package version: Evince 3.4.0-0ubuntu1

What you expected to happen:
Evince should let me shrink the sidebars to the width of the thumbnails.

What happened instead:
The minimum width of the sidebar leaves a half inch of whitespace on each side 
of the thumbnail, which robs space from the actual preview window.

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

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

Title:
  sidebar minimum width too large

Status in “evince” package in Ubuntu:
  New

Bug description:
  The minimum width of the thumbnail sidebar in evince 3.4 (running
  12.04 release) leaves large margins on both sides of the thumbnail. On
  a 1366x768 laptop screen, this whitespace takes away about an inch of
  horizontal screen width which could be more usefully allocated to the
  main preview window. The attached image shows a maximised evince
  window in Ubuntu 12.04, and exhibits the large amount of whitespace on
  each side of the thumbnails. By contrast, evince 2.30 on Debian 6.0
  lets me shrink the sidebar to fit the thumbnails snugly.

  
  Ubuntu version: 12.04
  Package version: Evince 3.4.0-0ubuntu1

  What you expected to happen:
  Evince should let me shrink the sidebars to the width of the thumbnails.

  What happened instead:
  The minimum width of the sidebar leaves a half inch of whitespace on each 
side of the thumbnail, which robs space from the actual preview window.

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

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

[Desktop-packages] [Bug 990228] Re: sidebar minimum width too large

2012-04-27 Thread Casey Jao

** Attachment added: evince_bad_304.png
   
https://bugs.launchpad.net/bugs/990228/+attachment/3110898/+files/evince_bad_304.png

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

Title:
  sidebar minimum width too large

Status in “evince” package in Ubuntu:
  New

Bug description:
  The minimum width of the thumbnail sidebar in evince 3.4 (running
  12.04 release) leaves large margins on both sides of the thumbnail. On
  a 1366x768 laptop screen, this whitespace takes away about an inch of
  horizontal screen width which could be more usefully allocated to the
  main preview window. The attached image shows a maximised evince
  window in Ubuntu 12.04, and exhibits the large amount of whitespace on
  each side of the thumbnails. By contrast, evince 2.30 on Debian 6.0
  lets me shrink the sidebar to fit the thumbnails snugly.

  
  Ubuntu version: 12.04
  Package version: Evince 3.4.0-0ubuntu1

  What you expected to happen:
  Evince should let me shrink the sidebars to the width of the thumbnails.

  What happened instead:
  The minimum width of the sidebar leaves a half inch of whitespace on each 
side of the thumbnail, which robs space from the actual preview window.

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

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

[Desktop-packages] [Bug 990228] Re: sidebar minimum width too large

2012-04-27 Thread Casey Jao

** Attachment added: evince_230.png
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/990228/+attachment/3110899/+files/evince_230.png

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

Title:
  sidebar minimum width too large

Status in “evince” package in Ubuntu:
  New

Bug description:
  The minimum width of the thumbnail sidebar in evince 3.4 (running
  12.04 release) leaves large margins on both sides of the thumbnail. On
  a 1366x768 laptop screen, this whitespace takes away about an inch of
  horizontal screen width which could be more usefully allocated to the
  main preview window. The attached image shows a maximised evince
  window in Ubuntu 12.04, and exhibits the large amount of whitespace on
  each side of the thumbnails. By contrast, evince 2.30 on Debian 6.0
  lets me shrink the sidebar to fit the thumbnails snugly.

  
  Ubuntu version: 12.04
  Package version: Evince 3.4.0-0ubuntu1

  What you expected to happen:
  Evince should let me shrink the sidebars to the width of the thumbnails.

  What happened instead:
  The minimum width of the sidebar leaves a half inch of whitespace on each 
side of the thumbnail, which robs space from the actual preview window.

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

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

48 matches

Mail list logo