Re: [Desktop-packages] [Bug 1530142] Re: [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all

[John Moulding]

Hi Raymond,

you'll have to forgive my ignorance (I'm a Linux newbie), but does that
mean that I actually have to raise the ticket myself?

I've no problem with that, but I don't want to dive in and make a twerp of
myself.

Best regards,

John Moulding

On 3 February 2016 at 09:09, Raymond <1530...@bugs.launchpad.net> wrote:

> 0.728657] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
> (scratch(0x850C)=0xCAFEDEAD)
> [ 18.728660] [drm:si_resume] *ERROR* si startup failed on resume
> [ 19.878088] [drm:si_dpm_set_power_state] *ERROR* si_upload_sw_state failed
>
>
>
> [ 8192.226320] playback write error (DMA or IRQ trouble?)
>  [ 8202.234132] playback write error (DMA or IRQ trouble?)
>
>
> You have to open upstream bug report at bugzilla.kernel.org. driver
> sound/ Alsa
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Summary changed:
>
> - [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all
> + [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all
> playback write error (DMA or IRQ trouble?)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1530142
>
> Title:
>   [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all
>   playback write error (DMA or IRQ trouble?)
>
> Status in alsa-driver package in Ubuntu:
>   Incomplete
>
> Bug description:
>   No sound, either on headphones or internal speakers.  Have been all
>   over forums, tried every fix I can find.  The installation is new, and
>   it's on a new Dell 5559.
>
>   Sound is not muted, and I believe the settings are correct, but it's
>   hard to be sure, as each answer I find seems to have slightly
>   differing advice, albeit a lot in common.
>
>   Would be really helpful if your best and most complete FAQ answers
>   were locked in one place, sorted by Ubuntu release:  otherwise there's
>   no way to tell which helpful suggestions/solutions are really correct.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu4
>   ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
>   Uname: Linux 3.13.0-74-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.19
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  john   2107 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Wed Dec 30 14:25:38 2015
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2015-12-24 (6 days ago)
>   InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140417)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
>   Symptom_AlsaPlaybackTestStderr:
>W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r
> x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p
> u t   e r r o r
> T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Symptom_DevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  john   2107 F pulseaudio
>   Symptom_Jack: Speaker, Internal
>   Symptom_Type: No sound at all
>   Title: [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 09/16/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.0.6
>   dmi.board.name: 0664DJ
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5559
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1530142/+subscriptions
>

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

Title:
  [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all
  playback write error (DMA or IRQ trouble?)

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  No sound, either on headphones or internal speakers.  Have been all
  over forums, tried every fix I can find.  The installation is new, and
  it's on a new Dell 5559.

  Sound is not muted, and I believe the settings are correct, but it's
  hard to be sure, as each answer I find seems to have slightly
  differing advice, albeit a lot in common.

  Would be really helpful if your best and most complete FAQ answers
  were locked in one place, sorted by Ubuntu release:  otherwise there's
  no way to tell which helpful suggestions/solutions are really correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 

[Desktop-packages] [Bug 1479715] Re: Crash due to fd leak when playing sounds in pidgin

[Cysioland]

I see it nominated for wily, but it occurs in wily.

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

Title:
  Crash due to fd leak when playing sounds in pidgin

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding pidgin.  This problem was most recently seen with version
  1:2.10.11-0ubuntu4, the problem page at
  https://errors.ubuntu.com/problem/7470d12c4e88f72501f718f2e8fd6469b2cb650f
  contains more details.

  Upstream bug: https://developer.pidgin.im/ticket/16752

  Partial backtrace:

  #0  0x7f0e72819b24 in g_source_attach (source=source@entry=0x0, 
context=0x0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:1163
  #1  0x7f0e74b848b8 in gst_bus_add_watch_full_unlocked (bus=, priority=, func=0x56004c7ceeb0 , 
user_data=0x56004e00aa40, notify=0x0) at gstbus.c:885
  #2  0x7f0e74b849e0 in gst_bus_add_watch_full (bus=0x7f0e14009260 
[GstBus], priority=0, func=0x56004c7ceeb0 , user_data=0x56004e00aa40, 
notify=0x0) at gstbus.c:936
  #3  0x56004c7cfb3a in pidgin_sound_play_file (filename=)
  at /build/pidgin-hiYwOJ/pidgin-2.10.11/./pidgin/gtksound.c:543
  #4  0x56004c7cf927 in pidgin_sound_play_event (event=PURPLE_SOUND_SEND)
  at /build/pidgin-hiYwOJ/pidgin-2.10.11/./pidgin/gtksound.c:616

  
  [Impact]

  * Each sound played will leak a file descriptor.

  * Crash (null pointer dereference) after playing sounds roughly 1000
  times (depending on fd limit)

  * Depending on the amount of activity, this can mean every few hours
  for some users (it's once for each received or sent message)

  
  [Test Case]

  1. Set the file descriptor limit low enough to be able to login, plus a few 
extra. "ulimit -Sn 20" works for me
  2. Start pidgin
  3. Tools menu -> preferences -> sounds tab
  4. Click "preview" 10 times or so
  5. Acquire crash

  [Regression Potential]

  * The fix consists in adding two lines, returning FALSE when a sound
  finishes playing or when an error happens, which tells gstreamer to
  free those file descriptors, so it's highly unlikely that this could
  make things worse.

  * A user who reported this bug yesterday was given a .deb file with
  the fix, who also distributed that fixed .deb to other 50 users who
  also had the issue in ubuntu wily. Everyone is happy now.

  [Other Info]

  * This fix will be included in pidgin 2.10.12, set to release very
  soon.

  * The bug originally happened because of the backported gstreamer 1.0
  patch that was also introduced in post-2.10.11 development versions.

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

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

[Desktop-packages] [Bug 1543745] [NEW] Xorg crash prevents login

[Fabio]

Public bug reported:

After a recent update, it's no more possible to log in to Ubuntu 16.04
trough lightdm with Unity.

I'm attaching .xsession-errors hoping it can be useful.

I'm reporting this from another partition with Trusty, because I did'n
know how to report without any GUI. I'm willing to add details if anyone
helps me on how to send them from the CLI.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.4-0ubuntu2
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: Tue Feb  9 20:11:26 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.3.0-5-generic, x86_64: installed
 bbswitch, 0.8, 4.3.0-7-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-2-generic, x86_64: installed
 psmouse-focaltech, 0.1, 3.19.0-18-generic, x86_64: installed
 psmouse-focaltech, 0.1, 3.19.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics 
Controller [1043:178d]
InstallationDate: Installed on 2015-03-21 (325 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X550JK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic.efi.signed 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash acpi_osi=
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550JK.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550JK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X550JK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Tue Feb  9 19:54:16 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 926 does not belong 
to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1117 
 vendor LGD
xserver.version: 2:1.17.3-2ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 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/1543745

Title:
  Xorg crash prevents login

Status in xorg package in Ubuntu:
  New

Bug description:
  After a recent update, it's no more possible to log in to Ubuntu 16.04
  trough lightdm with Unity.

  I'm attaching .xsession-errors hoping it can be useful.

  I'm reporting this from another partition with Trusty, because I did'n
  know how to report without any GUI. I'm willing to add details if
  anyone helps me on how to send them from the CLI.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  

[Desktop-packages] [Bug 1511476] Re: Unstable unity session

[Roger Tri]

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

This occurs mainly using libreoffice, but lately also using chrome, I
attach a crash file...

** Attachment added: "_opt_google_chrome_chrome.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511476/+attachment/4567587/+files/_opt_google_chrome_chrome.1000.crash

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

Title:
  Unstable unity session

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  My unity session crash randomly, when I am working on my computer, or
  when nothing is done in my computer.

  This occurs repeatedly since I have installed ubuntu 15.10.

  This does not happen on my laptop. The main difference I noticed
  between my computer and my laptop is that my laptop has an NVidia
  Graphic card and my computer has an intel Core™ i5-2320 as CPU/GPU. So
  it has no Graphic Card.

  Here you will find my syslog file content, during the crash :

  Oct 29 18:23:10 choupchoup org.a11y.atspi.Registry[1438]: XIO:  fatal IO 
error 11 (Resource temporarily unavailable) on X server ":0"
  Oct 29 18:23:10 choupchoup org.a11y.atspi.Registry[1438]: after 5183 requests 
(5183 known processed) with 0 events remaining.
  Oct 29 18:23:10 choupchoup org.freedesktop.Notifications[1349]: 
(notify-osd:2595): Gdk-WARNING **: notify-osd: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: 
(polkit-gnome-authentication-agent-1:1747): Gdk-WARNING **: 
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (nm-applet:1754): Gdk-WARNING 
**: nm-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X 
server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (update-notifier:2058): 
Gdk-WARNING **: update-notifier: Fatal IO error 11 (Ressource temporairement 
non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (telepathy-indicator:1933): 
Gdk-WARNING **: telepathy-indicator: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: 
(unity-fallback-mount-helper:1751): Gdk-WARNING **: 
unity-fallback-mount-helper: Fatal IO error 11 (Ressource temporairement non 
disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (nautilus:1748): Gdk-WARNING 
**: nautilus: Fatal IO error 11 (Ressource temporairement non disponible) on X 
server :0.
  Oct 29 18:23:10 choupchoup org.ayatana.bamf[1349]: (bamfdaemon:1407): 
Gdk-WARNING **: bamfdaemon: Fatal IO error 11 (Ressource temporairement non 
disponible) on X server :0.
  Oct 29 18:23:10 choupchoup acpid: client 815[0:0] has disconnected
  Oct 29 18:23:10 choupchoup acpid: client connected from 3456[0:0]
  Oct 29 18:23:10 choupchoup acpid: 1 client rule loaded
  Oct 29 18:23:10 choupchoup org.freedesktop.Notifications[1349]: loading icon 
'notification-nm-no-connection' caused error: 'L'icône « 
notification-nm-no-connection » n'est pas présente dans le thème 
ubuntu-mono-dark'loading icon 'notification-nm-device-wired' caused error: 
'L'icône « notification-nm-device-wired » n'est pas présente dans le thème 
ubuntu-mono-dark'
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.UDisks2VolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.GPhoto2VolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.MTPVolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.AfcVolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: gnome-session[1565]: 
GLib-GIO-WARNING: Error releasing name org.gnome.SessionManager: The connection 
is closed
  Oct 29 18:23:10 choupchoup gnome-session[1565]: GLib-GIO-WARNING: Error 
releasing name org.gnome.SessionManager: The connection is closed
  Oct 29 18:23:10 choupchoup org.gnome.zeitgeist.Engine[1349]: 
(zeitgeist-daemon:1902): GLib-GIO-WARNING **: Error releasing name 
org.gnome.zeitgeist.Engine: The connection is closed
  Oct 29 18:23:10 choupchoup org.gnome.zeitgeist.Engine[1349]: 
#033[31m[17:23:10.094000 

[Desktop-packages] [Bug 883319] Re: xrandr --scale restricts area in which mouse moves

[Mr.Gosh]

This Bug still affects acutal distributions of Ubuntu:

lsb_release -rd
Description:Ubuntu 15.10
Release:15.10

uname -a
Linux 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

xrandr --version
xrandr program version   1.4.3
Server reports RandR version 1.4

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Precise:
  Fix Released
Status in xorg-server source package in Quantal:
  Fix Released
Status in xorg-server source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

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

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

[Desktop-packages] [Bug 1543457] [NEW] Chromium is Crashed & won't open in Ubuntu 16.04

[Udara Madubhashana]

Public bug reported:

When i open chromium, It's crashed and won't open in Ubuntu 16.04
(Xenial Xerus)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 48.0.2564.82-0ubuntu1.1222
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Feb  9 09:06:02 2016
InstallationDate: Installed on 2016-02-06 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160205)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''
modified.conffile..etc.default.chromium.browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Chromium is Crashed & won't open in Ubuntu 16.04

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When i open chromium, It's crashed and won't open in Ubuntu 16.04
  (Xenial Xerus)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 48.0.2564.82-0ubuntu1.1222
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb  9 09:06:02 2016
  InstallationDate: Installed on 2016-02-06 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160205)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot

[Alexander A. Kompaniets]

Hi, Cedric!
The latest version' changelog (0.9.8.8-0ubuntu7.3 from Canonical repos) doesn't 
contains any relevant bugfixes,
so I think the bug is still there.

Could you please update your PPA? Thanks in advance!

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

Title:
  bridge_ignore_without_connections.patch breaks NM created bridge at
  boot

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I've created a bridge with network-manager-gnome, the bridge slave
  physical device is eth0. After a reboot the bridge is brought up, but
  eth0 isn't attached.

  First test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical 
device is eth0 and remove all other connections. After a reboot the bridge is 
brought up, but eth0 isn't attached. When I open 
/etc/NetworkManager/NetworkManager.conf and save it without any modification, 
eth0 is instantly added to my bridge. Strange!

  Second test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical 
device is eth0. Disable the "autoconnect" of the default wired network. After a 
reboot the bridge is brought up, but eth0 isn't  attached. Instead eth0 is 
brought up and full configured.

  After compiling and testing different upstream versions, i could track
  the problem down to bridge_ignore_without_connections.patch.  A
  network-manager package without this specific patch, brings my bridge
  up at boot and adds eth0 to the bridge in both test-cases.

  I've checked the behaviour on my ubuntu 13.10 box with network-manager
  (0.9.8.0-0ubuntu22)  and the trusty version network-manager
  (0.9.8.8-0ubuntu1) .

  Till now i couldn't  encounter any sideeffects of removing this patch
  with the bridge created by libvirt.

  Regards
  Mathias Kresin

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

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

[Desktop-packages] [Bug 1311257] Re: Wifi cannot connect or unstable after suspend 14.04

[Zisu Andrei]

Hello everyone.

I had a similar issue on elementary OS freya when coming out of suspend
with Intel Wireless-N 7260.

I could patch it with "nmcli nm sleep false" , however, it seems like
uninstalling laptop-mode-tools fixed it definitively.

Also, this fixed another issue: after I issues a suspend command, it
took 10-20 seconds until the laptop actually turned off. Now it turns
off instantly.

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

Title:
  Wifi cannot connect or unstable after suspend 14.04

Status in gnome-nettool package in Ubuntu:
  Confirmed

Bug description:
  I've tried every solution, such as
  1. editing /etc/pm/config.d to add
   SUSPEND_MODULES="iwlwifi"
  2. editing /etc/modprobe/d/wilwifi.conf to add:
  options iwlwifi bt_coex_active=0
  options iwlwifi 11n_disable=1
  3. running: sudo rmmod iwlwifi && sudo modprobe iwlwifi
  4. stopping, starting, or restarting Network Manager

  Nothing seems to work.  When I had 13.10, my wifi worked without a
  problem, but once I erased it and installed 14.04, wifi will not
  connect after suspend.  Ethernet works fine.  The only way I've found
  to resolve this is to restart my computer.  I have a Lenovo T420.  If
  I try to connect after suspend, it shows the Wifi Networks, tries to
  connect, and  says "Disconnected..." every time.

  ~$ sudo apt-get update; sudo apt-get install hwinfo grep rfkill; sudo lshw -C 
network; rfkill list; sudo iwlist scan | egrep -i 'chan|ssid'; cat 
/etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | grep -iA2 net; 
lsusb; nmcli nm status; sudo lshw -short; uname -a; dmesg | egrep 
'02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|rt2|rt3|rt5|rt6|rt7|usb|witch|wl';sudo
 dmidecode|egrep 'anufact|roduct|erial|elease'; iwconfig; cat /etc/modprobe.d/* 
| egrep 
'80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl';
 cat /var/lib/NetworkManager/NetworkManager.state; sudo hwinfo --netcard ; ps 
-aux|egrep 'wpa|icd|etwork'; netstat -rn ; cat /etc/resolv.conf; ls -lia /boot; 
sudo lsmod
  Ign http://dl.google.com stable InRelease
  Hit http://dl.google.com stable Release.gpg
  Hit http://dl.google.com stable Release
  Hit http://repository.spotify.com stable InRelease
  Ign http://us.archive.ubuntu.com trusty InRelease
  Hit http://dl.google.com stable/main amd64 Packages
  Hit http://dl.google.com stable/main i386 Packages
  Ign http://extras.ubuntu.com trusty InRelease
  Hit http://repository.spotify.com stable/non-free amd64 Packages
  Ign http://security.ubuntu.com trusty-security InRelease
  Ign http://us.archive.ubuntu.com trusty-updates InRelease
  Hit http://repository.spotify.com stable/non-free i386 Packages
  Hit http://extras.ubuntu.com trusty Release.gpg
  Hit http://security.ubuntu.com trusty-security Release.gpg
  Ign http://us.archive.ubuntu.com trusty-backports InRelease
  Hit http://extras.ubuntu.com trusty Release
  Ign http://us.archive.ubuntu.com trusty-proposed InRelease
  Hit http://security.ubuntu.com trusty-security Release
  Hit http://extras.ubuntu.com trusty/main Sources
  Ign http://dl.google.com stable/main Translation-en_US
  Hit http://us.archive.ubuntu.com trusty Release.gpg
  Ign http://dl.google.com stable/main Translation-en
  Hit http://security.ubuntu.com trusty-security/main Sources
  Hit http://extras.ubuntu.com trusty/main amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-updates Release.gpg
  Hit http://security.ubuntu.com trusty-security/restricted Sources
  Hit http://extras.ubuntu.com trusty/main i386 Packages
  Hit http://us.archive.ubuntu.com trusty-backports Release.gpg
  Hit http://security.ubuntu.com trusty-security/universe Sources
  Hit http://us.archive.ubuntu.com trusty-proposed Release.gpg
  Hit http://security.ubuntu.com trusty-security/multiverse Sources
  Hit http://us.archive.ubuntu.com trusty Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/main amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-updates Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/restricted amd64 Packages
  Ign http://repository.spotify.com stable/non-free Translation-en_US
  Hit http://us.archive.ubuntu.com trusty-backports Release
  Ign http://ppa.launchpad.net trusty InRelease
  Ign http://repository.spotify.com stable/non-free Translation-en
  Hit http://security.ubuntu.com trusty-security/universe amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-proposed Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/multiverse amd64 Packages
  Hit http://us.archive.ubuntu.com trusty/main Sources
  Ign 

[Desktop-packages] [Bug 1543617] [NEW] InputSources should have an explicit default

[Jonas G. Drange]

Public bug reported:

The AccountsService package rolls the org.freedesktop.Accounts.User.xml
schema, which comes with a default, empty InputSources. Mir defaults to
“en”.

Maybe we should set this value to “en” so that there's a canonical way
of figuring out what InputSource to use. Additionally, if a vendor wants
“no” to be the default, it could make sense to just override this schema
default value.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  InputSources should have an explicit default

Status in Canonical System Image:
  New
Status in accountsservice package in Ubuntu:
  New

Bug description:
  The AccountsService package rolls the
  org.freedesktop.Accounts.User.xml schema, which comes with a default,
  empty InputSources. Mir defaults to “en”.

  Maybe we should set this value to “en” so that there's a canonical way
  of figuring out what InputSource to use. Additionally, if a vendor
  wants “no” to be the default, it could make sense to just override
  this schema default value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543617/+subscriptions

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

[Desktop-packages] [Bug 1543546] [NEW] Monitor DPI settings are ignored after upgrade to Xenial

[Michael Marley]

Public bug reported:

I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24"
4K) from Wily to Xenial.  Before I did this, applications using all the
toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value
automatically detected from the monitor, causing them to automatically
scale to a usable size.  However, after upgrading to Xenial, GTK3
applications no longer have this behavior.  Instead, they appear at the
normal 96DPI size, causing them to be nearly unreadable due to the small
size of their widgets.

I am currently using GTK3 3.18.7-1ubuntu2,  but the issue has been
occurring since I upgraded to Xenial months ago.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Monitor DPI settings are ignored after upgrade to Xenial

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24"
  4K) from Wily to Xenial.  Before I did this, applications using all
  the toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value
  automatically detected from the monitor, causing them to automatically
  scale to a usable size.  However, after upgrading to Xenial, GTK3
  applications no longer have this behavior.  Instead, they appear at
  the normal 96DPI size, causing them to be nearly unreadable due to the
  small size of their widgets.

  I am currently using GTK3 3.18.7-1ubuntu2,  but the issue has been
  occurring since I upgraded to Xenial months ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1543546/+subscriptions

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

[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

[xavi]

Same issue here. I've been also able to trigger it while doing alt+tab.
I also lose my entire session when this happens. It doesn't happen
always but after some hours of work. I don't detect anything special
when system crashes... sorry =(

Running Metacity under Ubuntu 15.10

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

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  This bug seemed to occur already since earlier versions of Ubuntu, and
  usually would just end up leaving me with undecorated windows, from
  which recovery was as easy as restarting metacity by hand, but in this
  release of Ubuntu (15.04), it seems gnome-session tries to restart it
  too many times in a too short span, and then decides arbitrarily that
  it failed so bad it has to kill the whole session.

  So, while the metacity bug is really a thing, my real problem actually might 
be a gnome-session-bin bug.
  I expect metacity crashing would not bring down the whole session, as is the 
case currently.

  At any rate, this is extremely annoying, I am hitting this bug about
  every two days, and because of it and the regression in crash
  handling, I end up losing all my windows and running programs. (In all
  fairness, I am suspecting a hardware issue, but the problem remains
  that a sub process dying should not cause the parent process to die
  like this)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: metacity 1:3.14.3-1ubuntu7
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Oct 20 05:19:37 2015
  ExecutablePath: /usr/bin/metacity
  InstallationDate: Installed on 2010-01-30 (2088 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcCmdline: metacity
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: metacity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3
  Title: metacity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago)
  UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse 
pulse-access sambashare vboxusers video

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

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

[Desktop-packages] [Bug 1542549] Re: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

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

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

Title:
  package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  desplay

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1
  Uname: Linux 4.4.0-3-generic i686
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: i386
  Date: Sat Feb  6 00:30:33 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-04 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160127)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: lightdm
  Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1478112] Re: Impossible to save settings for Tunneled TLS connection

[Marco Sbodio]

** Tags added: trusty

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

Title:
  Impossible to save settings for Tunneled TLS connection

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I was attempting to connect to a Wifi router (WPA & WPA2 Enterprise,
  Tunneled TLS) using network-manager 0.9.10.0-4ubuntu15.1  in Ubuntu
  15.04. I entered my username and password, however, the save button is
  gray and will not respond.

  The only way I can save the settings is if I use an authentication
  method which is neither Tunneled TLS nor PEAP. Every other
  authentication methods lets me save the settings, but is the wrong
  setting for the router.

  I tried connecting on Ubuntu 14.04, which worked flawlessly. I
  attempted to copy the profile in /etc/NetworkManager/system-
  connections/ over to my Ubuntu install in 15.04, however, this did not
  solve the problem. This leads me to believe that it is a new problem
  in 15.10 and might have something to do with being unable to save the
  username and password to the keyring.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 24 19:44:00 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-07 (411 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (91 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
User27  25e56186-6cdd-4704-85c1-01fb7f53392b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with Chromium

[Bug Watch Updater]

** Changed in: debian
   Status: Unknown => New

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

Title:
  Unable to use the widevine plugin with Chromium

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in Debian:
  New

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  Solution :

  With the help from several people (hogliux for patch and saiarcot895
  for PPA) , a PPA is available with this feature :

  - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  - You need the binary widevine plugin plugin (2 files) :

  https://bugs.launchpad.net/ubuntu/+source/chromium-
  
browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz

  To be copied in /usr/lib/chromium

  - Launch netflix.com and see if it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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

[Desktop-packages] [Bug 1541892] Re: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Alberto Salvia Novella]

This report needs to:

1. Be translated into English
2. Set its status back to "confirmed".

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

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

Title:
  package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Clear 64 bit system Ubuntu Mate 16.04 , can't update in first time.
  apt-get install -f :
  dpkg: зависимости пакетов не позволяют настроить пакет ubuntu-mate-core:
   ubuntu-mate-core зависит от lightdm, однако:
Пакет lightdm пока не настроен.

  dpkg: ошибка при обработке пакета ubuntu-mate-core (--configure):
   проблемы зависимостей — оставляем не настроенным
  Отчёты apport не записаны, так как сообщение об ошибке указывает на повторную 
ошибку от предыдущего отказа.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lightdm:
Установлен: 1.17.5-0ubuntu2
Кандидат:   1.17.5-0ubuntu2
Таблица версий:
   *** 1.17.5-0ubuntu2 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb  4 18:10:40 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-02-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: lightdm
  Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 883319] Re: xrandr --scale restricts area in which mouse moves

[Marc Deslauriers]

This particular bug has been closed for a long time. If you are still
seeing an issue similar to this one, please file a new bug. Thanks.

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Precise:
  Fix Released
Status in xorg-server source package in Quantal:
  Fix Released
Status in xorg-server source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

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

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

[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi

[Timo Jyrinki]

If there is a Qt side to this bug, the silo 32 has a certain probability
of fixing it.

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  Mobile data doesn't automatically connect after leaving wifi

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  The mobile data doesn't automatically connect when leaving wifi.

  Expected Behavior:
  - Leave wifi
  - Mobile data connects automatically

  Observed Behavior:
  - Leave wifi
  - Mobile data is available but user interaction is required to connect. The 
device requires a reboot or airplane mode to be cycled before a connection is 
made.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions

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

[Desktop-packages] [Bug 1540953] Re: Xorg crashed when undocking Lenovo T450s from docking station

[Alberto Salvia Novella]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Xorg crashed when undocking Lenovo T450s from docking station

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

Bug description:
  I have a Lenovo T450s. When undocking the notebook from the docking
  station (Lenovo UltraDock, two monitors are connected), Xorg
  frequently crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+12ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.4-0ubuntu2
  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: Tue Feb  2 15:43:35 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5036]
  InstallationDate: Installed on 2016-02-02 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20BWS00V00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=eb42241b-c617-430d-84eb-b21a749fc2ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS00V00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS00V00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Tue Feb  2 15:33:03 2016
  xserver.configfile: default
  xserver.errors:
   systemd-logind: failed to get session: PID 3028 does not belong to any known 
session
   intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 1, disabling 
CRTC:25
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4925
   vendor AUO
  xserver.version: 2:1.17.3-2ubuntu2

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

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

[Desktop-packages] [Bug 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

[Alberto Milone]

Verification didn't fail in LP: #1539865

It seems to me that the error came from 2:15.200-0ubuntu0.5 but was
reported as coming from 2:15.200-0ubuntu0.6, since it was (probably) all
part of the same upgrade:

2016-01-30 18:25:56 configure fglrx-updates:amd64 2:15.200-0ubuntu0.5 
2016-01-30 18:25:56 status half-configured fglrx-updates:amd64 
2:15.200-0ubuntu0.5
...
2016-01-30 18:35:24 upgrade fglrx-updates-core:amd64 2:15.200-0ubuntu0.5 
2:15.200-0ubuntu0.6

Now, if we finally approved the update, we would stop having all these
duplicates and false positives.

** Tags removed: verification-failed

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

Title:
  Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Trusty:
  Fix Committed
Status in fglrx-installer-updates source package in Trusty:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  Upgrading from the upstream fglrx driver packages to the packages in
  the Ubuntu repository fails because the /etc/ati directory is a real
  directory instead of being a link (which was common in the Ubuntu
  packages).

  [Test Case]
  1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages 
from the AMD installer 
  2. Upgrade the package to the current ubuntu release.
  3. Check the apt-get output 

  Expected results: the fglrx module should be updated correctly.

  Actual results:
  The update fails as described below.

  [Regression Potential]
  Low. The change only affects a migration from a specific release.

  
  __
  Note that the fglrx 14.502 package name is 
fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from 
Ubuntu repository.

  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for install-info (5.2.0.dfsg.1-2) ...
  Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ...

  (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for doc-base (0.10.5) ...
  Processing 1 changed doc-base file...
  Errors were encountered while processing:
   /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb
  Log ended: 2015-10-22 05:31:11

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

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

[Desktop-packages] [Bug 1458220] Re: system keyboard layout not honored

[Flames_in_Paradise]

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

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

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

Title:
  system keyboard layout not honored

Status in sddm package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in sddm package in Mandriva:
  Unknown

Bug description:
  I'm on a fresh install of Kubuntu:
  Description:Ubuntu 15.04
  Release:15.04

  I chose German as installation language, de with nodeadkeys as
  keyboard and locale is set to de_DE.UTF-8.

  The console uses the correct keyboard, however when logging into sddm,
  the keyboard layout is set to US.

  SDDM doesn't seem to honour the keyboard configured during
  installation.

  SDDM installed is:
  ddm:
Installiert:   0.11.0-0ubuntu10
Installationskandidat: 0.11.0-0ubuntu10
Versionstabelle:
   *** 0.11.0-0ubuntu10 0
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  I believe it's a bug since the keyboard layout at login window after
  installing as described above should be the default system one, german
  in the above case.

  I have tried all sorts of ways (including some ugly hacks) to get this
  resolved on a previous installation but didn't find a way. Considering
  the many moving parts to get the login manager up and running, I'm
  aware this might be filed against the wrong package. It might even be
  an installer bug.

  
  Thanks!

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

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

[Desktop-packages] [Bug 883319] Re: xrandr --scale restricts area in which mouse moves

[Marc Deslauriers]

This particular bug was indeed fixed in Ubuntu 12.04:

xorg-server (2:1.11.4-0ubuntu10.12) precise-proposed; urgency=low

  * debian/patches/238-xrandr-fix-panning.patch: disable CRTC cursor
confinement when panning is enabled. (LP: #883319)

 -- Marc Deslauriers  Tue, 12 Feb 2013
16:45:02 -0500

If you are seeing similar symptoms in a more recent release, it's likely to be 
a different bug altogether.
Please file a new bug so the issue actually gets fixed instead of commenting in 
a bug that has been long closed and doesn't show up on any bug lists anymore.

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Precise:
  Fix Released
Status in xorg-server source package in Quantal:
  Fix Released
Status in xorg-server source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

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

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

[Desktop-packages] [Bug 1543782] Re: Complete system freeze some time after screensaver starts.

[Richard Eames]

** Attachment added: "output of journalctrl"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1543782/+attachment/4568112/+files/journal.log

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

Title:
  Complete system freeze some time after screensaver starts.

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Ever since updating to 15.10 my computer has been freezing every day.
  Usually this happens after I've left work, and since I leave my
  computer on, I manually start the screensaver (ctrl+alt+L), and when I
  come back the next morning, the computer is completely unresponsive,
  even to sysrq. Gnome screensaver itself doesn't appear to be the
  culprit since I can turn it on, then log back into my system any time
  within perhaps 5 minutes. Looking at my root journalctrl output,
  yesterday, it appears to have crashed 30 minutes after I logged out (I
  was zeroing a drive with dd, and was issuing a kill -USR1 to track the
  progress every 30 seconds).

  At first I thought it might be a botched upgrade from 15.04, so I
  tried a clean reinstall last week, but it still freezes. There is also
  nothing in the logs that would indicate an error/crash.

  The only potentially related piece of information is that I use gnome-
  shell, installed via ubuntu-gnome-desktop.

  I'm not sure what package to file this under since I don't know how to
  reproduce, or how to diagnose the issue. Any debugging advice will be
  appreciated since this issue is really starting to annoy me.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screensaver 3.6.1-7ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb  9 13:20:44 2016
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'gnome'
   org.gnome.desktop.session idle-delay uint32 600
  InstallationDate: Installed on 2016-02-04 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1542615] Re: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Robert Ancell]

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

** This bug is no longer a duplicate of bug 1542582
   package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1540568
   package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has 
to be enabled to start service udev

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

Title:
  package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb  5 23:10:00 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-28 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=family
   autologin-user-timeout=0
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: lightdm
  Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1541892] Re: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Robert Ancell]

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

** This bug has been marked a duplicate of bug 1540568
   package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has 
to be enabled to start service udev

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

Title:
  package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Clear 64 bit system Ubuntu Mate 16.04 , can't update in first time.
  apt-get install -f :
  dpkg: зависимости пакетов не позволяют настроить пакет ubuntu-mate-core:
   ubuntu-mate-core зависит от lightdm, однако:
Пакет lightdm пока не настроен.

  dpkg: ошибка при обработке пакета ubuntu-mate-core (--configure):
   проблемы зависимостей — оставляем не настроенным
  Отчёты apport не записаны, так как сообщение об ошибке указывает на повторную 
ошибку от предыдущего отказа.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lightdm:
Установлен: 1.17.5-0ubuntu2
Кандидат:   1.17.5-0ubuntu2
Таблица версий:
   *** 1.17.5-0ubuntu2 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb  4 18:10:40 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-02-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: lightdm
  Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 971209] Re: gvfsd-network SIGSEGV in g_vfs_monitor_emit_event()

[Andrew]

I have this error with the condition:

UnreportableReason:
 You have some obsolete package versions installed. Please upgrade the 
following packages and check if the problem still occurs:
 
 libgd3, libimobiledevice6, liblocale-gettext-perl, libtext-charwidth-perl, 
libtext-iconv-perl, perl-base

I have run sudo apt-get update && sudo apt-get upgrade before this
occurred and then rebooted.

I think plugging in an Android device around this time, that may have
triggered the crash. The only other application in use at the time was
Mozilla Firefox. I will attach syslog snippet and crash log.

ProblemType: Crash
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Feb 10 08:29:42 2016
DistroRelease: Ubuntu 16.04
ExecutablePath: /usr/lib/gvfs/gvfsd-network
ExecutableTimestamp: 1453833027
ProcCmdline: /usr/lib/gvfs/gvfsd-network --spawner :1.7 
/org/gtk/gvfs/exec_spaw/3
ProcCwd: /
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8

** Attachment added: "syslog-snippet.log"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/971209/+attachment/4568134/+files/syslog-snippet.log

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

Title:
  gvfsd-network SIGSEGV in g_vfs_monitor_emit_event()

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  i added a wireless network to the system.  That worked.  I am not sure
  that triggered the issue.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 20:47:07 2012
  ExecutablePath: /usr/lib/gvfs/gvfsd-network
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120401)
  ProcCmdline: /usr/lib/gvfs/gvfsd-network --spawner :1.12 
/org/gtk/gvfs/exec_spaw/4
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gvfs
  Title: gvfsd-network crashed with SIGSEGV in g_vfs_monitor_emit_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1432949] Re: r300 Mesa driver not loading with KMS enabled

[royden]

** Bug watch added: freedesktop.org Bugzilla #71789
   https://bugs.freedesktop.org/show_bug.cgi?id=71789

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=71789
   Importance: Unknown
   Status: Unknown

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

Title:
  r300 Mesa driver not loading with KMS enabled

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I cannot get 3D acceleration to work. I was expecting to see the gears
  via the command 'glxgears' I have KMS enable on my iBook G4 by using
  the following parameter

  Linux radeon.modeset=1 video=offb:off video=1024x768-32
  video=radeonfb:off radeon.agpmode=-1

  Here are my Mesa and Xorg output

  rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e 
dri2 -e drm -e KMS
  [32.774] Kernel command line: 
root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off 
video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off 
video=1024x768-32 video=radeonfb:off radeon.agpmode=-1
  [33.203] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.011] (II) LoadModule: "radeon"
  [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
  [35.337] (II) Module radeon: vendor="X.Org Foundation"
  [35.604] (II) [KMS] Kernel modesetting enabled.
  [35.697] (II) Loading sub module "dri2"
  [35.697] (II) LoadModule: "dri2"
  [35.697] (II) Module "dri2" already built-in
  [35.870] (II) RADEON(0): KMS Color Tiling: enabled
  [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled
  [35.870] (II) RADEON(0): KMS Pageflipping: enabled
  rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render
  libGL: screen 0 does not appear to be DRI3 capable
  libGL: pci id for fd 4: 1002:4e56, driver r300
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: r300
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Error: couldn't find RGB GLX visual or fbconfig
  rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  libgl1-mesa-dr 10.5.0~rc1-0 powerpc  free implementation of the OpenGL
  rican-linux@ibookG4-UbuntuMATE:~$ 

  rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri
  libgl1-mesa-dri:
Installed: 10.5.0~rc1-0ubuntu1
Candidate: 10.5.0-0ubuntu1
Version table:
   10.5.0-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages
   *** 10.5.0~rc1-0ubuntu1 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5
  Uname: Linux 3.18.0-13-powerpc-smp ppc
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: powerpc
  CurrentDesktop: MATE
  Date: Tue Mar 17 00:58:43 2015
  InstallationDate: Installed on 2015-03-17 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1325931]

[Cno]

(In reply to elicoten from comment #0)

> However, when I came to try to print it, it would not print correctly. The
> print dialog box showed the dimensions of A6 (140mm x 105mm) and I couldn't
> find any way to change this. I tried to print it anyway, but it came out
> wrong.

Is this related to "Use only paper size from printer preferences"
checkbox on the File > Print .. Options tab. ??

See bug 61186
and https://wiki.documentfoundation.org/ReleaseNotes/4.1#Other

(Then we could close as duplicate of bug 67576
and note that bug 94343 is about improving the position)

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

Title:
  Can't select non-standard paper sizes for Printing

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Problem description: 
  I was trying to print a small compliments slip on a card that was 140mm x 
100mm.

  I set the page size under Format -> Page -> Size to user defined, and
  then entered the width of 14.00cm and height of 10.00cm correctly.

  However, when I came to try to print it, it would not print correctly.
  The print dialog box showed the dimensions of A6 (140mm x 105mm) and I
  couldn't find any way to change this. I tried to print it anyway, but
  it came out wrong.

  To prove that the problem is in LibreOffice and probably not related
  to the driver, I exported the file to a PDF, and was able to print it
  by setting up a Custom Paper size in the printer settings dialog - an
  option which LibreOffice doesn't seem to have.

  Steps to reproduce:
  1. Create a new Document
  2. From the menu, do Format -> Page
  3. From the Format dropdown, select User
  4. Enter a size that is not a standard paper size
  5. Click OK
  6. Attempt to print the document

  Current behavior:
  No matter what combinations of options I tried, I was unable to change the 
Printer paper size to the correct size.
  If I go ahead and click Print, the output is wrong (output not aligned 
correctly on the page).

  Expected behavior:
  Paper size could be set by the selected Page size, or provide some way to 
change the printer paper size.
  Operating System: Ubuntu
  Version: 4.2.3.3 release

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun  3 12:04:40 2014
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-05-07 (26 days ago)

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

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

[Desktop-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

[sjp333]

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

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

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

Status in xorg package in Ubuntu:
  New

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubuntu Display configuration dialog detects both displays correctly
  and their positions 

[Desktop-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

[Samuel]

After 40 hours of trying, I bought a DVD reader and reinstalled Ubuntu. 
I encourage to implement: when we accept proposed updates, a warning appears 
explaining the risks.
Reason: many of us can not understand what is suggested here or elsewhere in 
Internet related with Terminal -no further than copy even if we have an 
extra computer to read online the suggestions -Network Manager was broken- and 
try to solve this problem for days, we still can not repair this bugs. 
PS: move/copy this suggestion if you think of a better place for implementation.

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Fix Committed

Bug description:
  [Triage Notes]

  This regression is caused by a libnl proposed update tracked in bug
  1511735. It has not been released as an update, only proposed as an
  update for early testing. If you volunteered to test proposed updates,
  then thank you. Your care and attention will stop this regression from
  hitting ordinary users, and we appreciate your contribution to Ubuntu.

  If you are not aware that you volunteered to test proposed updates,
  then please be aware that your system is configured to do so. In this
  case, you probably should turn this off. I'd appreciate if someone
  could explain how to do this in the comments.

  [Impact]

   * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
     libnl-route-3-200) and when libnl is updated to proposed
     3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
     validation packets.

     This affects the 0.98 release of NetworkManager and has already
     been fixed in newer releases.

   * Backporting fixes from upstream release is required to prevent
     NetworkManager from faulting which breaks networking on most
     Desktop releases.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

   * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
     libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

  [Test Case]

   * Reproduce crash test:
  1. Download 14.04.03 Desktop iso, amd64
  2. Launched in a VM, run from iso
  3. In terminal, enable proposed
  4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
  5. sudo restart network-manager
  #  note the nm-applet disappears as NM has now crashed, no network
     conn.
  6. dmesg to confirm network-manager crash
  7. sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
  8. sudo start network-manager
  #  nm-applet reappears, network connectivity restored

   * Successful upgrade test:
     1. Download 14.04.03 Desktop iso, amd64
     2. Launched in a VM, run from iso
     3. In a terminal, sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
     4. sudo restart network-manager  # NM still runs, no crash, net up
     5. enable trusty-proposed in /etc/apt/sources.list
     6. sudo apt-get update
     7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
     8. sudo restart network-manager  # NM still runs, no crash, net up.

  [Regression Potential]

   * NetworkManager is a highly visible package, so testing NetworkManager
     functionality is critical.  The patch does address the crash specificly
     introduced by the updated libnl SRU.

   * We need to ensure that users have installed this NetworkManager
     update before installing libnl3 update (special phasing needed).

  [Original Description]
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1543872] Re: Desktop streched across both screens

[Christopher M. Penalver]

sjp333, thank you for reporting this and helping make Ubuntu better.

As per
http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5428369=8=4192
an update to your computer's buggy and outdated BIOS is available
(1.34). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status New. If it's not reproducible, please mark 
this as Invalid.

Thank you for your understanding.

** Tags added: bios-outdated-1.34

** Description changed:

- I have a intel laptop with a nvidia k2100m quadro GPU. Intel HD graphics 
controls the internal display and the nvidia card handles the display port out. 
When trying to utilize a dual monitor setup the output of the desktop looks 
like its been stretched across both displays. It appears like the resolution is 
very low and the mouse pointer is incorrectly calibrated with its location on 
the screen. The dual monitor setup is completely useless with this bug. I 
believe this https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462 is the 
same issue filed way back in 2014. However, it was never resolved. This is a 
pretty big issue. Anyone have any ideas on how to fix it?
- Description:  Ubuntu 15.10
- Release:  15.10
- 
- xorg:
-   Installed: 1:7.7+7ubuntu4
-   Candidate: 1:7.7+7ubuntu4
-   Version table:
-  *** 1:7.7+7ubuntu4 0
- 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Intel HD graphics controls the internal display and the nvidia card
+ handles the display port out. When trying to utilize a dual monitor
+ setup the output of the desktop looks like its been stretched across
+ both displays. It appears like the resolution is very low and the mouse
+ pointer is incorrectly calibrated with its location on the screen.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 
PST 2016
-  GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 
PST 2016
+  GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
-  
+ 
  CurrentDesktop: Unity
  Date: Tue Feb  9 19:50:31 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.7, 4.2.0-17-generic, x86_64: installed
-  bbswitch, 0.7, 4.2.0-25-generic, x86_64: installed
-  bbswitch, 0.7, 4.2.0-27-generic, x86_64: installed
-  nvidia-352, 352.79, 4.2.0-25-generic, x86_64: installed
-  nvidia-352, 352.79, 4.2.0-27-generic, x86_64: installed
+  bbswitch, 0.7, 4.2.0-17-generic, x86_64: installed
+  bbswitch, 0.7, 4.2.0-25-generic, x86_64: installed
+  bbswitch, 0.7, 4.2.0-27-generic, x86_64: installed
+  nvidia-352, 352.79, 4.2.0-25-generic, x86_64: installed
+  nvidia-352, 352.79, 4.2.0-27-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
-  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:1909]
-  NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:1909]
+  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:1909]
+  NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:1909]
  InstallationDate: Installed on 2015-07-29 (195 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150727)
  MachineType: Hewlett-Packard HP ZBook 15
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic 
root=UUID=d0125fd5-5a86-4280-94b5-e38def1ab992 ro quiet nosplash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: 

[Desktop-packages] [Bug 971776] Re: software-center crashed with GError in constructor(): Format der Bilddatei unbekannt

[crystal allen]

** Package changed: software-center (Ubuntu) => lubuntu-software-center
(Ubuntu)

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

Title:
  software-center crashed with GError in constructor(): Format der
  Bilddatei unbekannt

Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-software-center source package in Precise:
  Fix Released

Bug description:
  I am on Ubuntu12.04 64bit updated to 2.3.2012.

  The Software center crashed on the search term"python".

  [TEST CASE]
  This crash occurs only intermittently under certain conditions when an image 
download fails. As such, this error can't be reliably reproduced. However, to 
test, you can fully exercise this code by clearing the downloaded icon cache 
and then reloading them per the following steps:
  1. Install the version of software-center in precise-proposed.
  2. With Software Center not running, execute the following in a terminal:

  $ cd ~/.cache/software-center/icons
  $ rm *

  3. Launch Software Center and navigate to "All Software" -> "For Purchase"
  4. Verify that as you scroll the list the application icons are loaded in the 
view.

  [REGRESSION POTENTIAL]
  Very low. If a regression were to occur, it would manifest as "generic" icons 
appearing in the list views or the details view.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: software-center 5.1.14
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Apr  2 20:19:36 2012
  ExecutablePath: /usr/share/software-center/software-center
  ExecutableTimestamp: 1333128425
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac 
(20120328)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  ProcCwd: /home/user
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-center']
  SourcePackage: software-center
  Title: software-center crashed with GError in constructor(): Format der 
Bilddatei unbekannt
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

[sjp333]

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1543872. I ran it
after the bug occured and I was able to stablize the system.

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

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubuntu 

[Desktop-packages] [Bug 1542028] Re: xapp window should reflect app name rather than "Xmir root window"

[Daniel van Vugt]

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  xapp window should reflect app name rather than "Xmir root window"

Status in Canonical System Image:
  New
Status in Canonical Pocket Desktop:
  New
Status in puritine package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Launching xapp on ubuntu-pd in windowed mode, results in a window title of 
"root xmir"
  It should reflect the app name in the container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542028/+subscriptions

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

[Desktop-packages] [Bug 1398595] Re: Working printer device communication error (5012)

[Launchpad Bug Tracker]

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

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

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

Title:
  Working printer device communication error (5012)

Status in cups package in Ubuntu:
  Expired

Bug description:
  My Deskjet 1000 series printer doesn't print now. It used to, but HPLIP 
confirms  a device communication error (5012). I'm using Ubuntu 14.4 LTS 
(upgrade) with AMD 64bit archetecture. It worked well up until about 2 weeks 
ago. I printed one page perfectly, but the second page failed. I then bought 
the newest model of same printer (HP 1010) thinking that the device was the 
problem. Same error.
  Any help would surely be appreciated here. 

  Thanks in advance,
  David Sprung

  P.S. I've tried deleting HPLIP and trying it without: failed.
  Installed newest HPLIP: failed. Help! I'm beginning to think it's a
  software issue, as my Dad's printer (HP) failed on his machine about
  the same time

  
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CupsErrorLog:
   E [03/Dec/2014:17:50:54 -0500] Unknown directive BrowseAddress on line 8 of 
/etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive JobPrivateAccess on line 85 
of /etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive JobPrivateValues on line 86 
of /etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive SubscriptionPrivateAccess 
on line 87 of /etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive SubscriptionPrivateValues 
on line 88 of /etc/cups/cupsd.conf.
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-09-20 (439 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  Lpstat: device for Deskjet_1000_J110: 
hp:/usb/Deskjet_1000_J110_series?serial=CN0BP22MYZ05D2
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: cups 1.7.2-0ubuntu1.2
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Deskjet_1000_J110: HP Deskjet 1000 j110 Series, hpcups 3.14.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=d3e197fa-9ef8-4603-8f5e-88976258e568 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=d3e197fa-9ef8-4603-8f5e-88976258e568 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags:  trusty apparmor apparmor apparmor apparmor apparmor apparmor apparmor 
apparmor apparmor apparmor
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-09-01 (93 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/09/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: u'/etc/cups/cupsd.conf']

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

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

[Desktop-packages] [Bug 1525274] Re: [HP Compaq nw8440 (EY694AA#ABA), Analog Devices AD1981, Other, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [HP Compaq nw8440 (EY694AA#ABA), Analog Devices AD1981, Other,
  Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Nothing shows in device output or input and no sound at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  f801263 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Dec 11 09:49:08 2015
  InstallationDate: Installed on 2015-12-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D6c:   Slmodemd   5139 F...m slmodemd
   /dev/snd/pcmC0D6p:   Slmodemd   5139 F...m slmodemd
   /dev/snd/controlC0:  f801263 F pulseaudio
Slmodemd   5139 F slmodemd
  Symptom_Jack: Other, Internal
  Symptom_Type: No sound at all
  Title: [HP Compaq nw8440 (EY694AA#ABA), Analog Devices AD1981, Other, 
Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YVD Ver. F.0A
  dmi.board.name: 30A3
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.16
  dmi.chassis.asset.tag: CNU6332KMN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YVDVer.F.0A:bd06/14/2006:svnHewlett-Packard:pnHPCompaqnw8440(EY694AA#ABA):pvrF.0A:rvnHewlett-Packard:rn30A3:rvrKBCVersion40.16:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nw8440 (EY694AA#ABA)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1543872] Re: Desktop streched across both screens

[sjp333]

L70 Ver. 01.34
10/28/2015
The bug was reproducible and there was no improvement.

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

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

Title:
  Desktop streched across both screens

Status in xorg package in Ubuntu:
  New

Bug description:
  Intel HD graphics controls the internal display and the nvidia card
  handles the display port out. When trying to utilize a dual monitor
  setup the output of the desktop looks like its been stretched across
  both displays. It appears like the resolution is very low and the
  mouse pointer is incorrectly calibrated with its location on the
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 
PST 2016
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:

  CurrentDesktop: Unity
  Date: Tue Feb  9 19:50:31 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-17-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-25-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-27-generic, x86_64: installed
   nvidia-352, 352.79, 4.2.0-25-generic, x86_64: installed
   nvidia-352, 352.79, 4.2.0-27-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1909]
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1909]
  InstallationDate: Installed on 2015-07-29 (195 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150727)
  MachineType: Hewlett-Packard HP ZBook 15
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic 
root=UUID=d0125fd5-5a86-4280-94b5-e38def1ab992 ro quiet nosplash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L70 Ver. 01.08
  dmi.board.name: 1909
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.51
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL70Ver.01.08:bd04/10/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10303:rvnHewlett-Packard:rn1909:rvrKBCVersion94.51:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~wily
  version.libgl1-mesa-dri: libgl1-mesa-dri 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~wily
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~wily
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151202.da9ad388-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20150926.1ff13a92-0ubuntu0sarvatt
  xserver.bootTime: Tue Feb  9 19:31:46 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

Re: [Desktop-packages] [Bug 883319] Re: xrandr --scale restricts area in which mouse moves

[jd]

No it wasn't. I saw this issue in 13.10, 14.04, 14.10, 15.04, and now
15.10. So if it was fixed in 12.04, then it was only fixed in that version.
Funny that I have a new bug altogether and yet the symptoms are identical
in every way. More liked Occam's Razor states that either the issue was
never fixed, or more complex description of it being fixed, then a magical
being appeared from the sky and made a completely different issue that is
identical in every way, but is apparently not the same thing.

You tell me if that sounds like a completely different bug or if it's a
lazy person who didn't fix it at all or correctly.


On Tue, Feb 9, 2016 at 8:56 AM, Marc Deslauriers <
marc.deslauri...@canonical.com> wrote:

> This particular bug was indeed fixed in Ubuntu 12.04:
>
> xorg-server (2:1.11.4-0ubuntu10.12) precise-proposed; urgency=low
>
>   * debian/patches/238-xrandr-fix-panning.patch: disable CRTC cursor
> confinement when panning is enabled. (LP: #883319)
>
>  -- Marc Deslauriers  Tue, 12 Feb 2013
> 16:45:02 -0500
>
> If you are seeing similar symptoms in a more recent release, it's likely
> to be a different bug altogether.
> Please file a new bug so the issue actually gets fixed instead of
> commenting in a bug that has been long closed and doesn't show up on any
> bug lists anymore.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/883319
>
> Title:
>   xrandr --scale restricts area in which mouse moves
>
> Status in X.Org X server:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Fix Released
> Status in xorg-server source package in Precise:
>   Fix Released
> Status in xorg-server source package in Quantal:
>   Fix Released
> Status in xorg-server source package in Raring:
>   Fix Released
>
> Bug description:
>   SRU Request:
>
>   [IMPACT]
>   A bug in the version of xorg-server in precise prevents users from
> scaling screen resolution. When attempting to do so, as was possible in
> Natty and earlier, and which is possible in Quantal+, the mouse pointer
> remains locked inside the old resolution. This prevents users of small
> screens such as netbooks from scaling to a greater screen resolution.
>
>   [Test Case]
>   - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale
> the display by using the following command:
>
>   xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25
>
>   See if the mouse moves correctly to all screen extremities, and is not
>   confined by a transparent border at 1024x600
>
>   [Regression Potential]
>   This is fixed with a patch backported from the xorg-server version in
> Quantal. In theory it should just affect screen which are scaled and
> panned, which is uncommon. If so, the patch can be backed out.
>
>
>
>   Original Bug Description:
>   in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so
>
>   xrandr --output LVDS1 --scale 1.2x1.2
>
>   this worked fine: the desktop scaled to larger size correctly .
>After upgrading to 11.10, in kde the desktop still resizes
>   correctly, but the movement of the mouse is restricted to an area equal
> to
>   the screen size *before* issuing the scaling command. .. Ie let's say
>   the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
>   screen size changes to 1640x922 but the mouse moves in an area the size
> of
>   1366x768 in the top left of the screen and then 'hits a wall' preventing
>   it to move. I also tried ubuntu 11.10 with gnome: here the screen also
>   resizes, but I have the same issue with the mouse, and the extended area
>   of the desktop is black...
>
>   Some time ago there was a similar issue, which was resolved later. Now
> it seems
>   to be back...
>
>   jos@samsungsucks:~$ lsb_release -rd
>   Description:Ubuntu 11.10
>   Release:11.10
>
>   jos@samsungsucks:~$ xrandr --version
>   xrandr program version   1.3.5
>   Server reports RandR version 1.3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions
>


-- 
J.D. Abbey III
jdabbey...@gmail.com
Mobile (858) 349-3357
Office (714) 584-4011

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Precise:
  Fix Released
Status in xorg-server source package in Quantal:
  Fix Released
Status in xorg-server source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the 

[Desktop-packages] [Bug 1543458] Re: Xorg crash prevents login

[Fabio]

The "Xlib: extension "GLX" missing on display ":0"" message suggests
it's indeed a problem with the GPU. I found that it could be caused by
bugs with nvidia drivers. This could be the case, as mine it's an
optimus laptop with NVIDIA GTX 850m.

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

Title:
  Xorg crash prevents login

Status in nvidia-graphics-drivers-352 package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  After a recent update, it's no more possible to log in to Ubuntu 16.04
  trough lightdm with Unity.

  I'm attaching .xsession-errors hoping it can be useful.

  I'm reporting this from another partition with Trusty, because I did'n
  know how to report without any GUI. I'm willing to add details if
  anyone helps me on how to send them from the CLI.

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

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