[Desktop-packages] [Bug 1776594] [NEW] getting system error popup

2018-06-12 Thread Prosenjit Mondal
Public bug reported:

Every time when i start my pc i am getting an error popup telling me
there is a system error detected, and for further details i saw its xorg
package crash report in /var/crash directory.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Wed Jun 13 10:56:19 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated 
Graphics Controller [1458:d000]
InstallationDate: Installed on 2017-09-10 (275 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic 
root=UUID=7243e19b-124d-43d0-bae0-a9cba591763b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F10
dmi.board.name: G31M-ES2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd09/29/2009:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G31M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jun 13 10:15:03 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id2176 
 vendor SAM
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-bug third-party-packages 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/1776594

Title:
  getting system error popup

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time when i start my pc i am getting an error popup telling me
  there is a system error detected, and for further details i saw its
  xorg package crash report in /var/crash directory.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Jun 13 10:56:19 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2017-09-10 (275 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release 

[Desktop-packages] [Bug 112238] Re: mga driver no longer will display 1600x1200

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  mga driver no longer will display 1600x1200

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-mga package in Ubuntu:
  Incomplete

Bug description:
  It seems that the newest xorg driver for MGA devices no longer support 
1600x1200 resolution.
  I've only found one place on the net that mentions this issue, they seem to 
believe that it is the latest release of xorg.
  I'm using Feisty on a fairly old machine.

  I've removed all the modeline statement in the xorg.conf file to let
  the VESA preset timing modes in my ViewSonic GS790 monitor control the
  modes.

  My video card is a MGA G400 Max (32M) duel monitor card, but I'm only
  using a single monitor.

  This always worked fine previous installs that were not Ubuntu based.

  The pertinent lines in my xorg.cone are below.
  -
  Section "Monitor"
identifier "GS790"
vendorname "ViewSonic"
modelname "ViewSonic GS790"
HorizSync 30-97
VertRefresh 50-180

#gamma 1.05 1.0 1.03
  EndSection

  Section "Screen"
Identifier "Default Screen"
Device "Matrox Graphics, Inc. MGA G400/G450"
Monitor "GS790"
DefaultDepth 24
SubSection "Display"
  depth 24
  modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
  EndSection

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

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


[Desktop-packages] [Bug 446019] Re: X crash in dixLookupResourceByClass+0xb8 when playing flash

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  X crash in dixLookupResourceByClass+0xb8 when playing flash

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  HW: ThinkPad X200s with gm45 card
  SW: Kubuntu Karmic up-to-date + x-updates PPA

  I started playing a flash video (with beta amd64 flash) in Chromium
  browser and X server crashed with the following stack trace (from
  Xorg.0.log.old):

  0: /usr/bin/X(xorg_backtrace+0x26) [0x4f0136]
  1: /usr/bin/X(xf86SigHandler+0x41) [0x4850f1]
  2: /lib/libc.so.6 [0x7f7597808530]
  3: /usr/bin/X(dixLookupResourceByClass+0xb8) [0x435a68]
  4: /usr/bin/X(dixLookupDrawable+0x4a) [0x452cca]
  5: /usr/bin/X(ProcCreateGC+0x7e) [0x44c93e]
  6: /usr/bin/X(Dispatch+0x384) [0x44e044]
  7: /usr/bin/X(main+0x3b5) [0x433fa5]
  8: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f75977f3abd]
  9: /usr/bin/X [0x433429]
  Saw signal 11.  Server aborting.

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct  8 07:09:46 2009
  DistroRelease: Ubuntu 9.10
  MachineType: LENOVO 74705HG
  Package: xserver-xorg 1:7.4+3ubuntu5
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-12-generic 
root=/dev/mapper/plain-root ro quiet splash
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.40-generic
  RelatedPackageVersions:
   xserver-xorg 1:7.4+3ubuntu5
   libgl1-mesa-glx 7.6.1~git20091002.c01a77d3-0ubuntu1~xup~1
   libdrm2 2.4.13-1ubuntu1
   xserver-xorg-video-intel 2:2.9.0-1ubuntu1~xup~1
   xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1~xup~1
  SourcePackage: xorg
  Uname: Linux 2.6.31-12-generic x86_64
  XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
  XsessionErrors: (chromium-browser:425): Gdk-WARNING **: XID collision, 
trouble ahead
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET38WW (2.02 )
  dmi.board.name: 74705HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET38WW(2.02):bd12/19/2008:svnLENOVO:pn74705HG:pvrThinkPadX200s:rvnLENOVO:rn74705HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 74705HG
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO
  fglrx: Not loaded
  system:
   distro: Ubuntu
   architecture:   x86_64kernel: 2.6.31-12-generic

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

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


[Desktop-packages] [Bug 268853] Re: Screen garbled after KDE comes up since Intrepid Alpha 5

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  Screen garbled after KDE comes up since Intrepid Alpha 5

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Problem:
  The X screen is garbled during startup before the login dialog is displayed; 
doing a vt switch clears the corruption and restores proper functionality.

  Photo:
  http://launchpadlibrarian.net/17530291/cimg1342.jpg

  lspci:
  PCI:*(0@1:0:0) nVidia Corporation G72 [GeForce 7300 SE]
  00:01.0 0604: 8086:29a1 (rev 02)

  Tested:
  Intrepid a4 (-nv 2.1.10-1ubuntu1, xserver 1.4.99.906-1ubuntu2) - Works 
properly
  Intrepid a5 (-nv 2.1.10-1ubuntu1, xserver 1.4.99.906-2ubuntu5) - Shows the 
issue
  Intrepid a6 (-nv 2.1.10-1ubuntu2, xserver 1.5.0-1ubuntu1) - Shows the issue

  
  Original Report:

  Add tag: crash bitesize packaging backport likely-dup needs-testing
  triage-mentoring-available

  This issue is new to Kubuntu Intrepid Alpha 5, i.e., everything still worked 
correctly with Alpha 4. I can reproduce it reliably by booting the Live CD 
(x86_64). While usplash shows up correctly, after X has loaded and while KDE is 
loading the screen becomes garbled - just the mouse pointer shows correctly 
(see attached photo).
  This can be worked around by switching to any text console and switching back 
using Ctrl+Alt+F7.

  Hardware:
  Nvidia GeForce 7300 SE

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

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


[Desktop-packages] [Bug 221297] Re: Wrong resolution for DVI connected Monitor on startup [X3100 GMA]

2018-06-12 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-intel
   Status: Confirmed => Invalid

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

Title:
  Wrong resolution for DVI connected Monitor on startup [X3100 GMA]

Status in xf86-video-intel:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-intel

  I have a Thinkpad T61 with an Intel X3100 GMA. I also have the
  advanced mini dockingstation with a DVI connector. The Problem is that
  the intel graphics driver seems to prioritize the "wrong" way. VGA
  comes first, then LVDS and then TMDS-1. So when I boot up with the
  laptop docked in and the external monitor connected to TMDS-1 I'll get
  only the resolution of the internal monitor (WXGA) instead of SXGA+.

  Everytime this happens I must execute "xrandr --output TMDS-1 --auto
  --output LVDS --off".

  Strange to say VGA comes first so when I connect my Monitor via VGA
  instead of DVI everything applies as expected.

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

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


[Desktop-packages] [Bug 532137] Re: Wacom Intuos2 tablet hotplug only works once after booting

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  Wacom Intuos2 tablet hotplug only works once after booting

Status in X.Org X server:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in xf86-input-wacom package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-input-wacom

  The following two tablets do not work out plug-and-play of the box in
  Lucid:

  056a:0041 Wacom Co., Ltd Intuos2 4x5
  056a:0044 Wacom Co., Ltd Intuos2 12x12

  messages/syslog:
  Mar  4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB 
device using uhci_hcd and address 6
  Mar  4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen 
from 1 choice
  Mar  4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18

  ProblemType: Bug
  Architecture: i386
  Date: Thu Mar  4 14:36:17 2010
  DistroRelease: Ubuntu 10.04
  Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic 
root=/dev/mapper/hostname-root ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
  SourcePackage: nvidia-graphics-drivers
  Uname: Linux 2.6.32-15-generic i686
  dmi.bios.date: 06/05/2006
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG965MQ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD37419-102
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr:
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucidarchitecture:   i686kernel: 
2.6.32-15-generic

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

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


[Desktop-packages] [Bug 575496] Re: ati radeon driver does not autodetect displaysize on Latitude D600

2018-06-12 Thread Bug Watch Updater
** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => Invalid

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

Title:
  ati radeon driver does not autodetect displaysize on Latitude D600

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  (This is a follow-up to bug 80940)
  This bug is still present in Lucid.  xdpyinfo still reports 
dimensions:1400x1050 pixels (370x277 millimeters)
resolution:96x96 dots per inch

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xserver-xorg-video-radeon 1:6.13.0-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Tue May  4 19:36:01 2010
  DkmsStatus: Error: [Errno 2] No such file or directory
  GdmLog:
   Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with 
exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch 
failed: No such file or directory
   QFileSystemWatcher: failed to add paths: /home/gjditchf/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   cat: /var/log/gdm/:0.log: No such file or directory
  GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] 
failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
  GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] 
failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100426.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Computer Corporation Latitude D600
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 product info: "O2Micro", "SmartCardBus Reader", "V1.0", ""
 manfid: 0x, 0x0001
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 5.0V 16-bit PC Card
 Subdevice 0 (function 0) [unbound]
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic 
root=UUID=6b3cd808-d2f4-423d-91b5-0b4583b1156e ro quiet splash
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-ati
  dmi.bios.date: 06/29/2005
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A16
  dmi.board.name: 0G5152
  dmi.board.vendor: Dell Computer Corporation
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA16:bd06/29/2005:svnDellComputerCorporation:pnLatitudeD600:pvr:rvnDellComputerCorporation:rn0G5152:rvr:cvnDellComputerCorporation:ct8:cvr:
  dmi.product.name: Latitude D600
  dmi.sys.vendor: Dell Computer Corporation
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-21-generic

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

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


[Desktop-packages] [Bug 112238]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  mga driver no longer will display 1600x1200

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-mga package in Ubuntu:
  Incomplete

Bug description:
  It seems that the newest xorg driver for MGA devices no longer support 
1600x1200 resolution.
  I've only found one place on the net that mentions this issue, they seem to 
believe that it is the latest release of xorg.
  I'm using Feisty on a fairly old machine.

  I've removed all the modeline statement in the xorg.conf file to let
  the VESA preset timing modes in my ViewSonic GS790 monitor control the
  modes.

  My video card is a MGA G400 Max (32M) duel monitor card, but I'm only
  using a single monitor.

  This always worked fine previous installs that were not Ubuntu based.

  The pertinent lines in my xorg.cone are below.
  -
  Section "Monitor"
identifier "GS790"
vendorname "ViewSonic"
modelname "ViewSonic GS790"
HorizSync 30-97
VertRefresh 50-180

#gamma 1.05 1.0 1.03
  EndSection

  Section "Screen"
Identifier "Default Screen"
Device "Matrox Graphics, Inc. MGA G400/G450"
Monitor "GS790"
DefaultDepth 24
SubSection "Display"
  depth 24
  modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
  EndSection

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

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


[Desktop-packages] [Bug 532137]

2018-06-12 Thread Chris Bagwell
I quickly looked at the Xorg.log files from launchpad below.  Right
after hotplug of tablet, usbParse() goes in infinite loop and prints
message about invalid serial #.  Not positive its infinite loop but at
least the log stops with no messages beyond repeating error message.  If
you wait long enough, perhaps the tablet corrects itself?

Intuos1 and Intuos2 are unique in that they get serial # from hardware
itself and used by xf86-input.wacom.  Serial # is a unique value that
allows tracking multiple tools at once.

You've found a case were tablet streams out packets in a way that serial
# is sent as zero.  Either tablet is saying a zero value or else an if()
statement is getting confused and not allowing to init values correctly.

This is all on kernel side, BTW.

Since I do not own own of these tablets, I do not have much more to
offer.  I can only say it appears mostly a kernel side bug from
information so far.

BTW: the best place to discuss wacom bugs is at project page bug tracker
or mailing list:  http://linuxwacom.sourceforge.net

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

Title:
  Wacom Intuos2 tablet hotplug only works once after booting

Status in X.Org X server:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in xf86-input-wacom package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-input-wacom

  The following two tablets do not work out plug-and-play of the box in
  Lucid:

  056a:0041 Wacom Co., Ltd Intuos2 4x5
  056a:0044 Wacom Co., Ltd Intuos2 12x12

  messages/syslog:
  Mar  4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB 
device using uhci_hcd and address 6
  Mar  4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen 
from 1 choice
  Mar  4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18

  ProblemType: Bug
  Architecture: i386
  Date: Thu Mar  4 14:36:17 2010
  DistroRelease: Ubuntu 10.04
  Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic 
root=/dev/mapper/hostname-root ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
  SourcePackage: nvidia-graphics-drivers
  Uname: Linux 2.6.32-15-generic i686
  dmi.bios.date: 06/05/2006
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG965MQ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD37419-102
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr:
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucidarchitecture:   i686kernel: 
2.6.32-15-generic

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

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


[Desktop-packages] [Bug 268853]

2018-06-12 Thread Ajax-a
The nv driver is long since deprecated. Please file a new bug if you can
still reproduce this with nouveau.

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

Title:
  Screen garbled after KDE comes up since Intrepid Alpha 5

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Problem:
  The X screen is garbled during startup before the login dialog is displayed; 
doing a vt switch clears the corruption and restores proper functionality.

  Photo:
  http://launchpadlibrarian.net/17530291/cimg1342.jpg

  lspci:
  PCI:*(0@1:0:0) nVidia Corporation G72 [GeForce 7300 SE]
  00:01.0 0604: 8086:29a1 (rev 02)

  Tested:
  Intrepid a4 (-nv 2.1.10-1ubuntu1, xserver 1.4.99.906-1ubuntu2) - Works 
properly
  Intrepid a5 (-nv 2.1.10-1ubuntu1, xserver 1.4.99.906-2ubuntu5) - Shows the 
issue
  Intrepid a6 (-nv 2.1.10-1ubuntu2, xserver 1.5.0-1ubuntu1) - Shows the issue

  
  Original Report:

  Add tag: crash bitesize packaging backport likely-dup needs-testing
  triage-mentoring-available

  This issue is new to Kubuntu Intrepid Alpha 5, i.e., everything still worked 
correctly with Alpha 4. I can reproduce it reliably by booting the Live CD 
(x86_64). While usplash shows up correctly, after X has loaded and while KDE is 
loading the screen becomes garbled - just the mouse pointer shows correctly 
(see attached photo).
  This can be worked around by switching to any text console and switching back 
using Ctrl+Alt+F7.

  Hardware:
  Nvidia GeForce 7300 SE

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

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


[Desktop-packages] [Bug 221297]

2018-06-12 Thread Ajax-a
This wants a more nuanced design discussion.

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

Title:
  Wrong resolution for DVI connected Monitor on startup [X3100 GMA]

Status in xf86-video-intel:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-intel

  I have a Thinkpad T61 with an Intel X3100 GMA. I also have the
  advanced mini dockingstation with a DVI connector. The Problem is that
  the intel graphics driver seems to prioritize the "wrong" way. VGA
  comes first, then LVDS and then TMDS-1. So when I boot up with the
  laptop docked in and the external monitor connected to TMDS-1 I'll get
  only the resolution of the internal monitor (WXGA) instead of SXGA+.

  Everytime this happens I must execute "xrandr --output TMDS-1 --auto
  --output LVDS --off".

  Strange to say VGA comes first so when I connect my Monitor via VGA
  instead of DVI everything applies as expected.

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

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


[Desktop-packages] [Bug 446019]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  X crash in dixLookupResourceByClass+0xb8 when playing flash

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  HW: ThinkPad X200s with gm45 card
  SW: Kubuntu Karmic up-to-date + x-updates PPA

  I started playing a flash video (with beta amd64 flash) in Chromium
  browser and X server crashed with the following stack trace (from
  Xorg.0.log.old):

  0: /usr/bin/X(xorg_backtrace+0x26) [0x4f0136]
  1: /usr/bin/X(xf86SigHandler+0x41) [0x4850f1]
  2: /lib/libc.so.6 [0x7f7597808530]
  3: /usr/bin/X(dixLookupResourceByClass+0xb8) [0x435a68]
  4: /usr/bin/X(dixLookupDrawable+0x4a) [0x452cca]
  5: /usr/bin/X(ProcCreateGC+0x7e) [0x44c93e]
  6: /usr/bin/X(Dispatch+0x384) [0x44e044]
  7: /usr/bin/X(main+0x3b5) [0x433fa5]
  8: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f75977f3abd]
  9: /usr/bin/X [0x433429]
  Saw signal 11.  Server aborting.

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct  8 07:09:46 2009
  DistroRelease: Ubuntu 9.10
  MachineType: LENOVO 74705HG
  Package: xserver-xorg 1:7.4+3ubuntu5
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-12-generic 
root=/dev/mapper/plain-root ro quiet splash
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.40-generic
  RelatedPackageVersions:
   xserver-xorg 1:7.4+3ubuntu5
   libgl1-mesa-glx 7.6.1~git20091002.c01a77d3-0ubuntu1~xup~1
   libdrm2 2.4.13-1ubuntu1
   xserver-xorg-video-intel 2:2.9.0-1ubuntu1~xup~1
   xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1~xup~1
  SourcePackage: xorg
  Uname: Linux 2.6.31-12-generic x86_64
  XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
  XsessionErrors: (chromium-browser:425): Gdk-WARNING **: XID collision, 
trouble ahead
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET38WW (2.02 )
  dmi.board.name: 74705HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET38WW(2.02):bd12/19/2008:svnLENOVO:pn74705HG:pvrThinkPadX200s:rvnLENOVO:rn74705HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 74705HG
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO
  fglrx: Not loaded
  system:
   distro: Ubuntu
   architecture:   x86_64kernel: 2.6.31-12-generic

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

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


[Desktop-packages] [Bug 532137]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  Wacom Intuos2 tablet hotplug only works once after booting

Status in X.Org X server:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in xf86-input-wacom package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-input-wacom

  The following two tablets do not work out plug-and-play of the box in
  Lucid:

  056a:0041 Wacom Co., Ltd Intuos2 4x5
  056a:0044 Wacom Co., Ltd Intuos2 12x12

  messages/syslog:
  Mar  4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB 
device using uhci_hcd and address 6
  Mar  4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen 
from 1 choice
  Mar  4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18

  ProblemType: Bug
  Architecture: i386
  Date: Thu Mar  4 14:36:17 2010
  DistroRelease: Ubuntu 10.04
  Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic 
root=/dev/mapper/hostname-root ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
  SourcePackage: nvidia-graphics-drivers
  Uname: Linux 2.6.32-15-generic i686
  dmi.bios.date: 06/05/2006
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG965MQ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD37419-102
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr:
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucidarchitecture:   i686kernel: 
2.6.32-15-generic

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

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


[Desktop-packages] [Bug 575496]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  ati radeon driver does not autodetect displaysize on Latitude D600

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  (This is a follow-up to bug 80940)
  This bug is still present in Lucid.  xdpyinfo still reports 
dimensions:1400x1050 pixels (370x277 millimeters)
resolution:96x96 dots per inch

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xserver-xorg-video-radeon 1:6.13.0-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Tue May  4 19:36:01 2010
  DkmsStatus: Error: [Errno 2] No such file or directory
  GdmLog:
   Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with 
exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch 
failed: No such file or directory
   QFileSystemWatcher: failed to add paths: /home/gjditchf/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   cat: /var/log/gdm/:0.log: No such file or directory
  GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] 
failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
  GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] 
failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100426.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Computer Corporation Latitude D600
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 product info: "O2Micro", "SmartCardBus Reader", "V1.0", ""
 manfid: 0x, 0x0001
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 5.0V 16-bit PC Card
 Subdevice 0 (function 0) [unbound]
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic 
root=UUID=6b3cd808-d2f4-423d-91b5-0b4583b1156e ro quiet splash
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-ati
  dmi.bios.date: 06/29/2005
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A16
  dmi.board.name: 0G5152
  dmi.board.vendor: Dell Computer Corporation
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA16:bd06/29/2005:svnDellComputerCorporation:pnLatitudeD600:pvr:rvnDellComputerCorporation:rn0G5152:rvr:cvnDellComputerCorporation:ct8:cvr:
  dmi.product.name: Latitude D600
  dmi.sys.vendor: Dell Computer Corporation
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-21-generic

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

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


[Desktop-packages] [Bug 1525526] Re: evince/atril is excruciatingly slow

2018-06-12 Thread Launchpad Bug Tracker
[Expired for poppler (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  evince/atril is excruciatingly slow

Status in poppler package in Ubuntu:
  Expired

Bug description:
  For image-heavy PDF files, both Atril and Evince are extremely slow
  when rendering the page. 'Slow' being in the region of 5-30s (timed),
  depending on the page, and depending on focus.

  Thumbnails take an equally long time to render.

  The same PDF files opened in muPDF render pages instantly.

  Currently version of libpoppler is 0.30.0-0ubuntu1.

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

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


[Desktop-packages] [Bug 1776569] Re: /usr/bin/gnome-software:11:g_list_prepend:add_to_lru_cache:ensure_in_lru_cache:proxy_pixbuf_destroy:gdk_pixbuf_finalize

2018-06-12 Thread Jean-Baptiste Lallement
This is fixed in artful and newer releases of Ubuntu. Please nominate
for Xenial if you want it fixed there.

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

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

Title:
  /usr/bin/gnome-
  
software:11:g_list_prepend:add_to_lru_cache:ensure_in_lru_cache:proxy_pixbuf_destroy:gdk_pixbuf_finalize

Status in gnome-software package in Ubuntu:
  Fix Released

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

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

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


[Desktop-packages] [Bug 41994] Re: closed Laptop Lid to reliably keep Backlight off

2018-06-12 Thread Bug Watch Updater
Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=41853.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2011-10-16T21:19:38+00:00 Ben Shadwick wrote:

I've observed this issue with acpid/acpi-support, gnome-power-manager
and xfce4-power-manager in Ubuntu 11.04 and Xubuntu 11.04 and 11.10, so
I'm thinking that it might be an xorg issue.

After running 'xset dpms force off' with lid closed on a laptop to
disable the backlight, moving the mouse or touching the keyboard will
cause the backlight to turn back on. The backlight should never turn on
under any circumstances when the lid is closed, unless maybe in the case
that the user runs 'xset dpms force on' explicitly.

Corresponding Ubuntu bug report is here:
https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/41994

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/41994/comments/52


On 2011-10-16T23:04:54+00:00 Jeremy Huddleston wrote:

This is not a bug with xset, moving to server component.

Sounds more like an ACPI bug to me, but I'm not very familiar with that side of 
the fence.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/41994/comments/53


On 2018-06-12T18:44:07+00:00 Ajax-a wrote:

Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/41994/comments/64


** Changed in: xorg-server
   Status: Unknown => Invalid

** Changed in: xorg-server
   Importance: Unknown => Medium

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

Title:
  closed Laptop Lid to reliably keep Backlight off

Status in One Hundred Papercuts:
  Invalid
Status in xfce4-power-manager:
  New
Status in X.Org X server:
  Invalid
Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in x11-xserver-utils package in Ubuntu:
  Confirmed

Bug description:
  Currently, on Dapper Beta 1, closing the laptop lid causes the
  backlight to shut off. However, for example when moving the mouse the
  backlight switches back on, even if the lid is still closed.

  The backlight should stay off as long as the lid is closed. There is
  no sense in trying to read a display in a closed lid.

  I am using a Dell Latitude X1.

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

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


[Desktop-packages] [Bug 40330] Re: mouse pointer should flip horizontally when mouse orientation is left-handed

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  mouse pointer should flip horizontally when mouse orientation is left-
  handed

Status in X.Org X server:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I'm running Ubuntu Dapper Drake Flight 6 + updates. When the mouse is
  set to left-handed, the mouse pointer is not affected visually by the
  setting so it continues to point the same direction (slightly to the
  left). I think that the mouse pointer should be reversed so that it
  points slightly to the right when the mouse is set to left-handed.

  The ideal solution whould be to automatically flip the relevant mouse
  pointers horizontally on-the-fly so that regardless of the pointer
  theme they are reversed when the mouse orientation is set to left-
  handed. However, some pointers in a theme would need to remain
  unaffected (like left/right window resize) which complicates the
  implementation of this solution.

  Another solution would be to ship two pointer themes: The default
  theme plus a slightly modified, left-handed variation of the default
  theme in which the affected pointers have been flipped horizontally.
  This is probably the most simple solution to implement for Dapper.

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

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


[Desktop-packages] [Bug 136853] Re: Screen blanks and freezes after a few minutes of idling, possibly due to broken DPMS

2018-06-12 Thread Bug Watch Updater
** Changed in: xf86-video-siliconmotion
   Status: Confirmed => Invalid

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

Title:
  Screen blanks and freezes after a few minutes of idling, possibly due
  to broken DPMS

Status in xf86-video-siliconmotion:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since switching to Gutsy to verify whether the packages I maintain
  still operate as expected, I have noticed that after a  few minutes of
  idle operation, the screen goes blank and cannot be returned to
  normal. The only way to get screen content again is to reboot, which
  is possible either by pressing the ACPI-enabled power button or a
  remote SSH connection. Broken DPMS is suspected, although I have no
  way of confirming this.

  Purposely downgrading xserver-xorg-core and anything that depend on
  it, then pining it to that version, while keeping all the rest of the
  packages to Gutsy versions solves it, which suggests something related
  to X.org upgrade from 1.2 to 1.3 might be at play.

  Note: someone on #ltsp mentions a similar situation using xserver-
  xorg-video-amd, yet the exact same AMD driver doesn't exhibit this
  behavior when compiled and used with earlier X releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xf86-video-siliconmotion/+bug/136853/+subscriptions

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


[Desktop-packages] [Bug 181176] Re: [trident] xserver goes into infinate loop

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  [trident] xserver goes into infinate loop

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-trident package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xserver-xorg-core-dbg

  Added Additional comments about recreating this BUG in Hardy Alpha-3
  in comments below.

  Ubuntu version 7.10 Gutsy xserver-xorg-core

  When launching X at anytime, usally right off the start. Ie right
  after X launches and splash screen occurs.

   /usr/bin/X goes into infinate loop consuming 99% CPU.

  Verified by booting to single user, starting sshd, and letting boot. As soon 
as screen goes blank,
  login via ssh and run top.

  This occurs on a Toshiba Satellite Laptop 1800 exact model PS181C BIOS
  version 1.2 (floppy is dead, cannot upgrade BIOS)

  Other reports of similair problem on FORUM and at following link with Debian 
Kernel:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454304

  The following is the backtrace (first loop):

  #0  x86emuOp_opc80_byte_RM_IMM (op1=128 '\200')
  at ../../../../hw/xfree86/int10/../x86emu/ops.c:5205
  mod = 
  rl = 
  rh = 
  destreg = 
  imm = 
  destval = 
  #1  0xb7bd11b3 in X86EMU_exec ()
  at ../../../../hw/xfree86/int10/../x86emu/decode.c:122
  op1 = 
  #2  0xb7bbd825 in xf86ExecX86int10 (pInt=0x8217870)
  at ../../../../hw/xfree86/int10/xf86x86emu.c:40
  sig = 0
  #3  0xb7bd93f9 in vbeDoEDID (pVbe=0x8217848, pDDCModule=0x0)
  at ../../../../hw/xfree86/vbe/vbe.c:190
  pMonitor = 
  pModule = (pointer) 0x1
  DDC_data = 
  #4  0xb7c0aa20 in TRIDENTSwitchMode ()
 from /usr/lib/xorg/modules/drivers//trident_drv.so
  No symbol table info available.
  #5  0x080a8e54 in InitOutput (pScreenInfo=0x8202a80, argc=10, argv=0xbf9e45f4)
  at ../../../../hw/xfree86/common/xf86Init.c:601
  i = 
  j = -1208328589
  k = 
  scr_index = 
  modulelist = 
  optionlist = (pointer *) 0x82115e0
  layout = 
  screenpix24 = 
  pix24 = 
  pix24From = 
  autoconfig = 
  generation = 1
  #6  0x08076ceb in main (argc=10, argv=0xbf9e45f4, envp=0xbf9e4620)
  at ../../dix/main.c:370
  i = 
  error = 136217184
  xauthfile = 
  alwaysCheckForInput = {0, 1}

  [lspci]
  01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade/i1 
[1023:8620] (rev 5d)
  00:00.0 Host bridge [0600]: ALi Corporation M1632M Northbridge+Trident 
[10b9:1632] (rev 01)
Subsystem: Toshiba America Info Systems Unknown device [1179:0004]
  01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade/i1 
[1023:8620] (rev 5d) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Unknown device [1179:0001]

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

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


[Desktop-packages] [Bug 192508] Re: mouse keys too easy to accidently turn on

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: In Progress => Invalid

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

Title:
  mouse keys too easy to accidently turn on

Status in gnome-control-center:
  New
Status in One Hundred Papercuts:
  Confirmed
Status in vino:
  New
Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am using Hardy Heron and several times now I have tried to use my
  number pad only to discover that they now move the mouse. I don't know
  if there is a short cut key I am hitting on accident, but it is rather
  annoying. Then sometimes when I disable mouse keys, the numlock
  becomes switched so that the system thinks numlock is on when the
  light is off and vice-versa.

  Update: the shortcut is: shift+num-lock

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

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


[Desktop-packages] [Bug 313525] Re: [r200] Strange tremor on the monitor

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => Invalid

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

Title:
  [r200] Strange tremor on the monitor

Status in X.Org X server:
  Invalid
Status in xserver-xorg-driver-ati:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-driver-ati

  Ubuntu Lucid with ATI FireGl 8800 card (r200 chip).

  lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon
  R200 QH [Radeon 8500] (rev 80)

  My monitor model is an HP p1120
  -HorizSync   30-121
  -VertRefresh 48-160

  Since I installed intrepid I have a temblor in my monitor (In the other 
Ubuntu releases it works great). It is especially visible at the edges of the 
windows.
  It is very strange because all seems to be correct (with the default 
xorg.conf configuration):
   - Resultion is on the default 1600x1200
   - The vertical refresh rate is on the default 85Hz
   - The horizontal refresh rate is on 106.3kHz

  I try to configure the HorizSync and VertRefresh manually editing the
  /etc/X11/xorg.conf file but nothing changes

  The tremor is only in 1600x1200 resolution.
  The others resolutions works well

  In Windows with the same settings (1600x1200 - 106.3kHz/85Hz) there is
  no tremor

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

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


[Desktop-packages] [Bug 188792] Re: [9200SE] Incorrect default resolution with CRT over VGA

2018-06-12 Thread Bug Watch Updater
** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => Invalid

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

Title:
  [9200SE] Incorrect default resolution with CRT over VGA

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I have two CRT monitors with a resolution of 1280x1024 at 60fps.  When
  I use the radeon driver for my Radeon 9200SE PCI, the resolution
  defaults to some widescreen res; although i still get graphical
  output, it isn't truly usable with 1/4 the screen chopped off..

  I don't know if the monitors have false hardware identification or
  what, but I need them to be 1280x1024.. and i'm not sure, but it looks
  like radeon is ignoring my mode settings in xorg.conf.

  Monitors: Cybervision C92, Gateway VX900.

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

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


[Desktop-packages] [Bug 554637] Re: [R480] screen display shows "shivering", wrong refresh rate

2018-06-12 Thread Bug Watch Updater
** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => Invalid

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

Title:
  [R480] screen display shows "shivering", wrong refresh rate

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  I the problem with a Radeon X800GTO on a Mitsubishi Diamond Plus
  230SB. xrandr says 1600*1200@85Hz but the OSD says 78.4Hz and the image is
  shaking.
  There is no problem in 75Hz.

  I have this problem since i upgraded to lucid. I have this problem only in 
KMS so i set 
  "options radeon modeset=0" /etc/modprobe.d/radeon-kms.conf to disable it.

  Here are other URLs to the same bug (i think) :
  https://bugs.freedesktop.org/show_bug.cgi?id=23508
  https://bugs.freedesktop.org/show_bug.cgi?id=27278

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+3ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  Architecture: i386
  CheckboxSubmission: 1a456c9fa0d0b19a4a079c28070486e6
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  CurrentDmesg:
   [   51.196034] end_request: I/O error, dev fd0, sector 0
   [   54.736047] end_request: I/O error, dev fd0, sector 0
   [   99.580021] Clocksource tsc unstable (delta = -169534079 ns)
   [  117.812053] __ratelimit: 12 callbacks suppressed
   [  117.812058] gvfsd-metadata[2112]: segfault at 8 ip 0804d35a sp bfc3f9c0 
error 4 in gvfsd-metadata[8048000+c000]
  Date: Sat Apr  3 16:26:19 2010
  DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Lsusb:
   Bus 002 Device 002: ID 046d:c042 Logitech, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T^2 DVB-T 
Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=22e38d43-2b96-411c-88b7-d95f0d2bb122 ro quiet splash
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 08/22/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1008
  dmi.board.name: A8N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 2.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1008:bd08/22/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-19-generic

  [lspci]
  01:00.0 VGA compatible controller [0300]: ATI Technologies Inc R480 [Radeon 
X800 GTO (PCIE)] [1002:5d4f]
Subsystem: PC Partner Limited Device [174b:1600]

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

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


[Desktop-packages] [Bug 136853]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  Screen blanks and freezes after a few minutes of idling, possibly due
  to broken DPMS

Status in xf86-video-siliconmotion:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Since switching to Gutsy to verify whether the packages I maintain
  still operate as expected, I have noticed that after a  few minutes of
  idle operation, the screen goes blank and cannot be returned to
  normal. The only way to get screen content again is to reboot, which
  is possible either by pressing the ACPI-enabled power button or a
  remote SSH connection. Broken DPMS is suspected, although I have no
  way of confirming this.

  Purposely downgrading xserver-xorg-core and anything that depend on
  it, then pining it to that version, while keeping all the rest of the
  packages to Gutsy versions solves it, which suggests something related
  to X.org upgrade from 1.2 to 1.3 might be at play.

  Note: someone on #ltsp mentions a similar situation using xserver-
  xorg-video-amd, yet the exact same AMD driver doesn't exhibit this
  behavior when compiled and used with earlier X releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xf86-video-siliconmotion/+bug/136853/+subscriptions

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


[Desktop-packages] [Bug 40330]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  mouse pointer should flip horizontally when mouse orientation is left-
  handed

Status in X.Org X server:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I'm running Ubuntu Dapper Drake Flight 6 + updates. When the mouse is
  set to left-handed, the mouse pointer is not affected visually by the
  setting so it continues to point the same direction (slightly to the
  left). I think that the mouse pointer should be reversed so that it
  points slightly to the right when the mouse is set to left-handed.

  The ideal solution whould be to automatically flip the relevant mouse
  pointers horizontally on-the-fly so that regardless of the pointer
  theme they are reversed when the mouse orientation is set to left-
  handed. However, some pointers in a theme would need to remain
  unaffected (like left/right window resize) which complicates the
  implementation of this solution.

  Another solution would be to ship two pointer themes: The default
  theme plus a slightly modified, left-handed variation of the default
  theme in which the affected pointers have been flipped horizontally.
  This is probably the most simple solution to implement for Dapper.

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

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


[Desktop-packages] [Bug 224798] Re: [hardy] X crashes when using compiz 0.7.4 + firefox 3.0b5 + java applets ("VNC java viewer")

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  [hardy] X crashes when using compiz 0.7.4 + firefox 3.0b5 + java
  applets ("VNC java viewer")

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  since I'm using ubuntu 8.04, with compiz 0.7.4 activated,
  X crashes and restarts each time when I am using firefox 3.0b5 to connect to 
my vnc server.
  The connection to my vnc server is made by a "java viewer" using http port 
and a webbrowser (here firefox 3.0b5).
  The vnc server and "java viewer" are realvnc 
(http://www.realvnc.com/support/javavncviewer.html#1)
  My graphic card is an Intel 915GM card (using X and intel driver).

  This bug is ALWAYS reproducible.
  I've attached to this bug report all necessary files (I hope).

  Thank you for your help :)

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

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


[Desktop-packages] [Bug 317957] Re: Xorg crashed with SIGFPE in miScreenInit()

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  Xorg crashed with SIGFPE in miScreenInit()

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Crashed near or during resolution changing with external VGA screen
  attached.  Jaunty, 2.6.28-4.10.

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/Xorg
  Package: xserver-xorg-core 2:1.5.99.3-0ubuntu4
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth 
-nolisten tcp vt7
  ProcCwd: /etc/X11
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcVersion: Linux version 2.6.28-4-generic (buildd@vernadsky) (gcc version 
4.3.3 20090111 (prerelease) (Ubuntu 4.3.2-2ubuntu11) ) #10-Ubuntu SMP Mon Jan 
12 19:35:29 UTC 2009
  Signal: 8
  SourcePackage: xorg-server
  StacktraceTop:
   miScreenInit ()
   fbFinishScreenInit () from /usr/lib/xorg/modules//libfb.so
   fbScreenInit () from /usr/lib/xorg/modules//libfb.so
   ?? () from /usr/lib/xorg/modules/drivers//radeon_drv.so
   AddScreen ()
  Title: Xorg crashed with SIGFPE in miScreenInit()
  Uname: Linux 2.6.28-4-generic i686
  UserGroups:

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

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


[Desktop-packages] [Bug 188792]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  [9200SE] Incorrect default resolution with CRT over VGA

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I have two CRT monitors with a resolution of 1280x1024 at 60fps.  When
  I use the radeon driver for my Radeon 9200SE PCI, the resolution
  defaults to some widescreen res; although i still get graphical
  output, it isn't truly usable with 1/4 the screen chopped off..

  I don't know if the monitors have false hardware identification or
  what, but I need them to be 1280x1024.. and i'm not sure, but it looks
  like radeon is ignoring my mode settings in xorg.conf.

  Monitors: Cybervision C92, Gateway VX900.

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

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


[Desktop-packages] [Bug 181176]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  [trident] xserver goes into infinate loop

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-trident package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xserver-xorg-core-dbg

  Added Additional comments about recreating this BUG in Hardy Alpha-3
  in comments below.

  Ubuntu version 7.10 Gutsy xserver-xorg-core

  When launching X at anytime, usally right off the start. Ie right
  after X launches and splash screen occurs.

   /usr/bin/X goes into infinate loop consuming 99% CPU.

  Verified by booting to single user, starting sshd, and letting boot. As soon 
as screen goes blank,
  login via ssh and run top.

  This occurs on a Toshiba Satellite Laptop 1800 exact model PS181C BIOS
  version 1.2 (floppy is dead, cannot upgrade BIOS)

  Other reports of similair problem on FORUM and at following link with Debian 
Kernel:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454304

  The following is the backtrace (first loop):

  #0  x86emuOp_opc80_byte_RM_IMM (op1=128 '\200')
  at ../../../../hw/xfree86/int10/../x86emu/ops.c:5205
  mod = 
  rl = 
  rh = 
  destreg = 
  imm = 
  destval = 
  #1  0xb7bd11b3 in X86EMU_exec ()
  at ../../../../hw/xfree86/int10/../x86emu/decode.c:122
  op1 = 
  #2  0xb7bbd825 in xf86ExecX86int10 (pInt=0x8217870)
  at ../../../../hw/xfree86/int10/xf86x86emu.c:40
  sig = 0
  #3  0xb7bd93f9 in vbeDoEDID (pVbe=0x8217848, pDDCModule=0x0)
  at ../../../../hw/xfree86/vbe/vbe.c:190
  pMonitor = 
  pModule = (pointer) 0x1
  DDC_data = 
  #4  0xb7c0aa20 in TRIDENTSwitchMode ()
 from /usr/lib/xorg/modules/drivers//trident_drv.so
  No symbol table info available.
  #5  0x080a8e54 in InitOutput (pScreenInfo=0x8202a80, argc=10, argv=0xbf9e45f4)
  at ../../../../hw/xfree86/common/xf86Init.c:601
  i = 
  j = -1208328589
  k = 
  scr_index = 
  modulelist = 
  optionlist = (pointer *) 0x82115e0
  layout = 
  screenpix24 = 
  pix24 = 
  pix24From = 
  autoconfig = 
  generation = 1
  #6  0x08076ceb in main (argc=10, argv=0xbf9e45f4, envp=0xbf9e4620)
  at ../../dix/main.c:370
  i = 
  error = 136217184
  xauthfile = 
  alwaysCheckForInput = {0, 1}

  [lspci]
  01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade/i1 
[1023:8620] (rev 5d)
  00:00.0 Host bridge [0600]: ALi Corporation M1632M Northbridge+Trident 
[10b9:1632] (rev 01)
Subsystem: Toshiba America Info Systems Unknown device [1179:0004]
  01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade/i1 
[1023:8620] (rev 5d) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Unknown device [1179:0001]

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

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


[Desktop-packages] [Bug 317957]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  Xorg crashed with SIGFPE in miScreenInit()

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Crashed near or during resolution changing with external VGA screen
  attached.  Jaunty, 2.6.28-4.10.

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/Xorg
  Package: xserver-xorg-core 2:1.5.99.3-0ubuntu4
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth 
-nolisten tcp vt7
  ProcCwd: /etc/X11
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcVersion: Linux version 2.6.28-4-generic (buildd@vernadsky) (gcc version 
4.3.3 20090111 (prerelease) (Ubuntu 4.3.2-2ubuntu11) ) #10-Ubuntu SMP Mon Jan 
12 19:35:29 UTC 2009
  Signal: 8
  SourcePackage: xorg-server
  StacktraceTop:
   miScreenInit ()
   fbFinishScreenInit () from /usr/lib/xorg/modules//libfb.so
   fbScreenInit () from /usr/lib/xorg/modules//libfb.so
   ?? () from /usr/lib/xorg/modules/drivers//radeon_drv.so
   AddScreen ()
  Title: Xorg crashed with SIGFPE in miScreenInit()
  Uname: Linux 2.6.28-4-generic i686
  UserGroups:

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

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


[Desktop-packages] [Bug 192508]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  mouse keys too easy to accidently turn on

Status in gnome-control-center:
  New
Status in One Hundred Papercuts:
  Confirmed
Status in vino:
  New
Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am using Hardy Heron and several times now I have tried to use my
  number pad only to discover that they now move the mouse. I don't know
  if there is a short cut key I am hitting on accident, but it is rather
  annoying. Then sometimes when I disable mouse keys, the numlock
  becomes switched so that the system thinks numlock is on when the
  light is off and vice-versa.

  Update: the shortcut is: shift+num-lock

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

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


[Desktop-packages] [Bug 224798]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  [hardy] X crashes when using compiz 0.7.4 + firefox 3.0b5 + java
  applets ("VNC java viewer")

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  since I'm using ubuntu 8.04, with compiz 0.7.4 activated,
  X crashes and restarts each time when I am using firefox 3.0b5 to connect to 
my vnc server.
  The connection to my vnc server is made by a "java viewer" using http port 
and a webbrowser (here firefox 3.0b5).
  The vnc server and "java viewer" are realvnc 
(http://www.realvnc.com/support/javavncviewer.html#1)
  My graphic card is an Intel 915GM card (using X and intel driver).

  This bug is ALWAYS reproducible.
  I've attached to this bug report all necessary files (I hope).

  Thank you for your help :)

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

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


[Desktop-packages] [Bug 313525]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  [r200] Strange tremor on the monitor

Status in X.Org X server:
  Invalid
Status in xserver-xorg-driver-ati:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-driver-ati

  Ubuntu Lucid with ATI FireGl 8800 card (r200 chip).

  lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon
  R200 QH [Radeon 8500] (rev 80)

  My monitor model is an HP p1120
  -HorizSync   30-121
  -VertRefresh 48-160

  Since I installed intrepid I have a temblor in my monitor (In the other 
Ubuntu releases it works great). It is especially visible at the edges of the 
windows.
  It is very strange because all seems to be correct (with the default 
xorg.conf configuration):
   - Resultion is on the default 1600x1200
   - The vertical refresh rate is on the default 85Hz
   - The horizontal refresh rate is on 106.3kHz

  I try to configure the HorizSync and VertRefresh manually editing the
  /etc/X11/xorg.conf file but nothing changes

  The tremor is only in 1600x1200 resolution.
  The others resolutions works well

  In Windows with the same settings (1600x1200 - 106.3kHz/85Hz) there is
  no tremor

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

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


[Desktop-packages] [Bug 313525]

2018-06-12 Thread Bugzi11-fdo-tormod
The reporter answered these questions in comment 2. The logs in the
downstream bug indicates it broke between xserver 1.4.0.90 and 1.5.2.

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

Title:
  [r200] Strange tremor on the monitor

Status in X.Org X server:
  Invalid
Status in xserver-xorg-driver-ati:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-driver-ati

  Ubuntu Lucid with ATI FireGl 8800 card (r200 chip).

  lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon
  R200 QH [Radeon 8500] (rev 80)

  My monitor model is an HP p1120
  -HorizSync   30-121
  -VertRefresh 48-160

  Since I installed intrepid I have a temblor in my monitor (In the other 
Ubuntu releases it works great). It is especially visible at the edges of the 
windows.
  It is very strange because all seems to be correct (with the default 
xorg.conf configuration):
   - Resultion is on the default 1600x1200
   - The vertical refresh rate is on the default 85Hz
   - The horizontal refresh rate is on 106.3kHz

  I try to configure the HorizSync and VertRefresh manually editing the
  /etc/X11/xorg.conf file but nothing changes

  The tremor is only in 1600x1200 resolution.
  The others resolutions works well

  In Windows with the same settings (1600x1200 - 106.3kHz/85Hz) there is
  no tremor

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

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


[Desktop-packages] [Bug 313525]

2018-06-12 Thread Jeremy Huddleston
Can you provide a server log for a working state and a broken state for 
comparison?  What version change introduces the problem?  A new radeon driver 
or a new server?

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

Title:
  [r200] Strange tremor on the monitor

Status in X.Org X server:
  Invalid
Status in xserver-xorg-driver-ati:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-driver-ati

  Ubuntu Lucid with ATI FireGl 8800 card (r200 chip).

  lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon
  R200 QH [Radeon 8500] (rev 80)

  My monitor model is an HP p1120
  -HorizSync   30-121
  -VertRefresh 48-160

  Since I installed intrepid I have a temblor in my monitor (In the other 
Ubuntu releases it works great). It is especially visible at the edges of the 
windows.
  It is very strange because all seems to be correct (with the default 
xorg.conf configuration):
   - Resultion is on the default 1600x1200
   - The vertical refresh rate is on the default 85Hz
   - The horizontal refresh rate is on 106.3kHz

  I try to configure the HorizSync and VertRefresh manually editing the
  /etc/X11/xorg.conf file but nothing changes

  The tremor is only in 1600x1200 resolution.
  The others resolutions works well

  In Windows with the same settings (1600x1200 - 106.3kHz/85Hz) there is
  no tremor

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

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


[Desktop-packages] [Bug 554637]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  [R480] screen display shows "shivering", wrong refresh rate

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  I the problem with a Radeon X800GTO on a Mitsubishi Diamond Plus
  230SB. xrandr says 1600*1200@85Hz but the OSD says 78.4Hz and the image is
  shaking.
  There is no problem in 75Hz.

  I have this problem since i upgraded to lucid. I have this problem only in 
KMS so i set 
  "options radeon modeset=0" /etc/modprobe.d/radeon-kms.conf to disable it.

  Here are other URLs to the same bug (i think) :
  https://bugs.freedesktop.org/show_bug.cgi?id=23508
  https://bugs.freedesktop.org/show_bug.cgi?id=27278

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+3ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  Architecture: i386
  CheckboxSubmission: 1a456c9fa0d0b19a4a079c28070486e6
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  CurrentDmesg:
   [   51.196034] end_request: I/O error, dev fd0, sector 0
   [   54.736047] end_request: I/O error, dev fd0, sector 0
   [   99.580021] Clocksource tsc unstable (delta = -169534079 ns)
   [  117.812053] __ratelimit: 12 callbacks suppressed
   [  117.812058] gvfsd-metadata[2112]: segfault at 8 ip 0804d35a sp bfc3f9c0 
error 4 in gvfsd-metadata[8048000+c000]
  Date: Sat Apr  3 16:26:19 2010
  DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Lsusb:
   Bus 002 Device 002: ID 046d:c042 Logitech, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T^2 DVB-T 
Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=22e38d43-2b96-411c-88b7-d95f0d2bb122 ro quiet splash
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 08/22/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1008
  dmi.board.name: A8N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 2.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1008:bd08/22/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-19-generic

  [lspci]
  01:00.0 VGA compatible controller [0300]: ATI Technologies Inc R480 [Radeon 
X800 GTO (PCIE)] [1002:5d4f]
Subsystem: PC Partner Limited Device [174b:1600]

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

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


[Desktop-packages] [Bug 1775881] Re: Every time I boot up ubuntu, the login screen looks like a static TV screen. This does not occur with other login manages, only gdm3

2018-06-12 Thread Daniel van Vugt
Assigning to mutter/gnome-shell as that provides the login GUI.

When in a VT, please run 'lspci -k' and send us the output:

  lspci -k > output.txt

or take a photo of the output.

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

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

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

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

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

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

Title:
  Every time I boot up ubuntu, the login screen looks like a static TV
  screen. This does not occur with other login manages, only gdm3

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

Bug description:
  Ubuntu Version 18.04 LTS

  gdm3:
  Installed: 3.28.0-0ubuntu1 500

  Package name: /etc/gdm3

  Whenever I boot Ubuntu following installation from the official
  install ISO, the boot screen appears, but the login manager appears as
  static, scrambled graphics, making me unable to login without opening
  the VT and installing lightdm and switching to that login manager.

  Expected Results:
  Login manager appears with login field, background, and menu while I am able 
to find, click, and enter information into the login text fields.

  Actual Results:
  Scrambled noise appeared on my screen and I am unable to leave without 
force-shutting down my Gateway PC, or opening a VT and installing lightdm, 
rebooting afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Jun  8 11:41:23 2018
  InstallationDate: Installed on 2018-06-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1727356] Re: Wayland sessions (including the login screen itself) don't start up on older Intel GPUs (pre-Sandy Bridge)

2018-06-12 Thread Daniel van Vugt
And:

Intel Core2 Duo E7200

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

Title:
  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs (pre-Sandy Bridge)

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

Bug description:
  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1776582] [NEW] package gnome-initial-setup 3.28.0-2ubuntu6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

2018-06-12 Thread Jackson Galloway
Public bug reported:

if i make resolution higher things go off of the screen

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-initial-setup 3.28.0-2ubuntu6.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 12:01:57 2018
DuplicateSignature:
 package:gnome-initial-setup:3.28.0-2ubuntu6.1
 Processing triggers for systemd (237-3ubuntu10) ...
 dpkg: error processing package gnome-initial-setup (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-06-13 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gnome-initial-setup
Title: package gnome-initial-setup 3.28.0-2ubuntu6.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gnome-initial-setup 3.28.0-2ubuntu6.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  if i make resolution higher things go off of the screen

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-initial-setup 3.28.0-2ubuntu6.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jun 13 12:01:57 2018
  DuplicateSignature:
   package:gnome-initial-setup:3.28.0-2ubuntu6.1
   Processing triggers for systemd (237-3ubuntu10) ...
   dpkg: error processing package gnome-initial-setup (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-06-13 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-initial-setup
  Title: package gnome-initial-setup 3.28.0-2ubuntu6.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1753012] Re: Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe() from InitOutput() from dix_main() from __libc_start_main()

2018-06-12 Thread Daniel van Vugt
** Information type changed from Private to Public

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

Title:
  Xorg crashed with SIGABRT in xf86platformProbe() from xf86BusProbe()
  from InitOutput() from dix_main() from __libc_start_main()

Status in xorg-server package in Ubuntu:
  Confirmed

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

  ---

  in xf86BusProbe()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Mar  2 13:54:32 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:3824]
  InstallationDate: Installed on 2015-12-14 (809 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80K6
  ProcCmdline: /usr/lib/xorg/Xorg :1 -configure
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-11-generic 
root=UUID=73fd1edc-d964-40d3-a1dd-b1ca4118cce6 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   xf86BusProbe ()
   InitOutput ()
   ?? ()
   __libc_start_main (main=0x557c28f02b80, argc=3, argv=0x7ffe64d48138, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe64d48128) at ../csu/libc-start.c:310
  Title: Xorg crashed with SIGABRT in xf86BusProbe()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C2CN17WW(V1.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Z51-70
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z51-70
  dmi.modalias: 
dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K6
  dmi.product.version: Lenovo Z51-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180221.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Mar  3 00:27:10 2018
  xserver.configfile: /root/xorg.conf.new
  xserver.devices:

  xserver.errors:
   dbus-core: error connecting to system bus: 
org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket 
/var/run/dbus/system_bus_socket: No such file or directory)
   Server terminated with error (2). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.6-1ubuntu2

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

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


[Desktop-packages] [Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend

2018-06-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012

Bug 1753012 is now public.

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

Title:
  X server crashes with SIGBUS when resuming from suspend

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Every night I suspend my laptop and resume it in the morning. At least
  once a week, the X server crashes with SIGBUS when resuming from
  suspend.

  I scoured systemd journals and all logs under /var/log, and this was
  the only suspicious message I found:

  [ 59358.134] (EE) /dev/dri/card0: failed to set DRM interface version
  1.4: Permission denied

  As my graphics card uses driver i915, I installed xserver-xorg-video-
  intel-dbg but couldn't find any package with debugging symbols for
  xserver-xorg-core, so running 'sudo gdb --core=/core' only yielded
  this:

  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGBUS, Bus error.
  #0  0x5631c45681f1 in ?? ()
  [Current thread is 1 (LWP 1016)]
  (gdb) bt
  #0  0x5631c45681f1 in ?? ()
  #1  0x0001 in ?? ()
  #2  0x5631c5a03350 in ?? ()
  #3  0x0001 in ?? ()
  #4  0x5631c4596ec5 in ?? ()
  #5  0x7f5f0974e2a0 in ?? ()
  #6  0x7f5f093e5977 in ?? ()
  #7  0x in ?? ()

  I'm attaching apport's crash report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Jun  7 08:56:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04b0]
  InstallationDate: Installed on 2018-04-28 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash 
systemd.legacy_systemd_cgroup_controller=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 08FDW5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1768261] Re: Videos are getting stuck randomly at frames

2018-06-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1768610 ***
https://bugs.launchpad.net/bugs/1768610

I'm not sure this is a duplicate of bug 1768610. UnitySupportTest.txt
shows everything is OK.

Sounds more like bug 1767694 to me.

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

Title:
  Videos are getting stuck randomly at frames

Status in xorg package in Ubuntu:
  New

Bug description:
  Updated Ubuntu to 18.04 (from 17.10) and this problem started. Videos,
  on VLC and on Youtube, Twitch etc. on Chrome get stuck on frames. The
  video seek time also gets stuck at that frame, and then suddenly the
  video skips ahead. Audio has no issues. I am assuming it's a problem
  with the video drivers.

  I have dual graphics cards, one integrated and one dedicated(AMD
  Radeon HD 8670M). I guess my problem is similar to
  https://askubuntu.com/questions/1029205/video-playback-performance-
  issue-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May  1 19:40:21 2018
  DistUpgraded: 2018-04-26 21:50:03,842 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea]
  InstallationDate: Installed on 2016-01-21 (830 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron 5537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d287f35b-0011-4adf-a2f4-3626718405ff ro quiet splash radeon.modeset=1 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 04NGGW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron5537:pvrA08:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805010730.6487e7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805010730.6487e7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1768786] Re: Desktop is displayed when resuming from suspend

2018-06-12 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.1

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

Title:
  Desktop is displayed when resuming from suspend

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  Confirmed
Status in budgie-desktop source package in Bionic:
  New
Status in gnome-shell source package in Bionic:
  New
Status in ubuntu-unity-meta source package in Bionic:
  New

Bug description:
  Steps to reproduce and description:

  First test case - where things work correctly:

  1.  Open Settings-> Privacy and make sure that Automatic screen lock is ON.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the lockscreen is shown on resume and that you can't see the 
desktop

  Second test case - where things are broken

  1.  Open Settings -> Privacy and make sure that Automatic screen lock is OFF.
  2.  Suspend your machine
  3.  Resume your machine
  4.  Notice that the desktop is visible for a second, then the screen blanks, 
then the lock screen appears, then the screen blanks again.  You are left at a 
black screen and need to unlock.

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

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


[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2018-06-12 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.1

** Changed in: mutter (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mutter (Ubuntu Bionic)
   Status: Confirmed => In Progress

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  In Progress

Bug description:
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  Steps to reproduce the issue:
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1767694] Re: Video streaming pauses frequently

2018-06-12 Thread Daniel van Vugt
Google Chrome is not part of the Ubuntu archive so the status for
"Ubuntu" tasks is "Invalid".

Please report the bug to the Chrome developers instead at:
https://bugs.chromium.org/p/chromium/issues/list

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

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

Title:
  Video streaming pauses frequently

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When youtube is accessed, video often pauses while audio continues.
  This occurs every 10 or 20 seconds, and the video pauses between 3 and
  7 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 14:50:47 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 80940] Re: ati radeon driver does not autodetect displaysize on Latitude D600, therefore uses wrong resolution

2018-06-12 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

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

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

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

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

Title:
  ati radeon driver does not autodetect displaysize on Latitude D600,
  therefore uses wrong resolution

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xserver-xorg-driver-ati

  Since Hoary up to Feisty Herd2, the xorg ati/radeon driver never detected the 
right physical
  dimension of the display.  So  dpi is set to 75 instead of 125.  This results
  in fonts that almost half as wide and height as it should be.

  Using DisplaySize in Monitor section of xorg.conf  fixes it, but that's not 
autodetection
  (as works perfect with i810 on other laptops)

  $ grep DisplaySize /etc/X11/xorg.conf
  DisplaySize 286 214

  $ xdpyinfo | egrep 'dimens|resolu'
dimensions:1400x1050 pixels (287x215 millimeters)
resolution:124x124 dots per inch

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

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


[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt

2018-06-12 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.1

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

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt (if starting with Shift key). Usually works on the
  second attempt

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

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

  Workaround:
  Hit a lower-case key, then backspace, then enter your password.

  Original description:
  Ubuntu 18.04 login screen rejects a valid password on first attempt. Always 
works on the second attempt..

  This seems to be a new problem, just started today.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2

2018-06-12 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  Unknown
Status in qemu package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1725163] Re: gnome-shell freezes for 25s when logout/shutdown (if USB camera is plugged in)

2018-06-12 Thread Daniel van Vugt
** Summary changed:

- gnome-shell freezes for 25s when logout/shutdown
+ gnome-shell freezes for 25s when logout/shutdown (if USB camera is plugged in)

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

Title:
  gnome-shell freezes for 25s when logout/shutdown (if USB camera is
  plugged in)

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Problem: When I click on logout/shutdown option in gnome-shell topbar
  menu DE freezes for 25sec before providing correct overlay
  (logout/shutdown window)

  Gnome: 3.26
  Ubuntu: 17.10
  gnome-settings-daemon:
Installed: 3.26.1-0ubuntu5
Candidate: 3.26.1-0ubuntu5

  part of log:
  Oct 20 09:35:42 MegaHulk systemd[2225]: Started GNOME Terminal Server.
  Oct 20 09:35:59 MegaHulk at-spi2-registr[11456]: Failed to send session 
response Timeout was reached
  Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor 
proxy: Timeout was reached
  Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor 
proxy: Timeout was reached
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client21' fail
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client21' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client18' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client18' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client17' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client16' fail
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client17' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client15' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client14' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client13' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client12' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client11' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client10' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client24' fail
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client16' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client22' fail
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client9' faile
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client8' faile
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client7' faile
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client6' faile
  Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: 
WARNING: Client '/org/gnome/SessionManager/Client3' faile
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client15' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client14' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client13' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client12' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client11' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client 
'/org/gnome/SessionManager/Client10' failed to reply before tim
  Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: 

[Desktop-packages] [Bug 1697535] Re: [Envy24 ICE1724] Audio doesn't work

2018-06-12 Thread Daniel van Vugt
** Tags added: bionic

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

Title:
  [Envy24 ICE1724] Audio doesn't work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 17.04
  PulseAudio Version: 1:10.0-1ubuntu2
  I expected the audio on my system to work without any additional action on my 
part. Instead, the audio does not work despite working on Windows.

  A few years ago, my onboard sound broke so I bought a pci sound card
  (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724
  chipset. This sound card works on Windows but not Ubuntu or Debian.
  I've attempted to troubleshoot this myself over the past year or so
  and had no luck figuring out the problem (though ubuntu-bug seems to
  think there is a problem with pulseaudio).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 12 14:00:25 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-12-10 (184 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5QL-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Desktop-packages] [Bug 80940] Re: ati radeon driver does not autodetect displaysize on Latitude D600, therefore uses wrong resolution

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  ati radeon driver does not autodetect displaysize on Latitude D600,
  therefore uses wrong resolution

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-driver-ati

  Since Hoary up to Feisty Herd2, the xorg ati/radeon driver never detected the 
right physical
  dimension of the display.  So  dpi is set to 75 instead of 125.  This results
  in fonts that almost half as wide and height as it should be.

  Using DisplaySize in Monitor section of xorg.conf  fixes it, but that's not 
autodetection
  (as works perfect with i810 on other laptops)

  $ grep DisplaySize /etc/X11/xorg.conf
  DisplaySize 286 214

  $ xdpyinfo | egrep 'dimens|resolu'
dimensions:1400x1050 pixels (287x215 millimeters)
resolution:124x124 dots per inch

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

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


[Desktop-packages] [Bug 211897] Re: Xorg crashed with SIGSEGV in xf86RandR12SetRotations()

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  Xorg crashed with SIGSEGV in xf86RandR12SetRotations()

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  I noticed that just enabling xinerama causes a segmentation fault. As
  mentioned in the wiki, I enabled NoTrapSignals. xorg.conf and
  associated log is attached, the very same configuration without
  xinerama works fine. The crash is very easily reproducable on my
  laptop, if you need any more information, just ask.

  $ lsb_release -rd
  Description:Ubuntu hardy (development branch)
  Release:8.04
  $ apt-cache policy xorg
  xorg:
Installed: 1:7.3+10ubuntu7
Candidate: 1:7.3+10ubuntu7
Version table:
   *** 1:7.3+10ubuntu7 0
  700 http://de.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status
   1:7.2-5 0
  650 http://ftp.de.debian.org testing/main Packages
  $ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.2.1-1ubuntu6
Candidate: 2:2.2.1-1ubuntu6
Version table:
   *** 2:2.2.1-1ubuntu6 0
  700 http://de.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status
   2:2.1.0-2 0
  650 http://ftp.de.debian.org testing/main Packages
  $ apt-cache policy xserver-xorg-video-i810
  xserver-xorg-video-i810:
Installed: 2:1.7.4-0ubuntu7
Candidate: 2:1.7.4-0ubuntu7
Version table:
   2:2.1.0-2 0
  650 http://ftp.de.debian.org testing/main Packages
   *** 2:1.7.4-0ubuntu7 0
  700 http://de.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  Architecture: amd64
  Date: Fri Apr  4 19:44:29 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/Xorg
  Package: xserver-xorg-core 2:1.4.1~git20080131-1ubuntu6 [modified: 
usr/bin/Xorg usr/bin/cvt usr/bin/gtf]
  PackageArchitecture: amd64
  ProcCmdline: X :1 -config xinerama.xorg.conf
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   xf86RandR12SetRotations (
   xf86CrtcScreenInit (screen=0xa20730)
   ?? ()
   AddScreen (pfnInit=0x7f9a08aa79f0, argc=4, 
   InitOutput (pScreenInfo=0x7f1d20, argc=4,
  Title: Xorg crashed with SIGSEGV in xf86RandR12SetRotations()
  Uname: Linux 2.6.24-14-generic x86_64
  UserGroups:

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

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


[Desktop-packages] [Bug 148117] Re: [r128] Rage 128: Unsuitable videomode autoselected

2018-06-12 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-r128
   Status: Confirmed => Invalid

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

Title:
  [r128] Rage 128: Unsuitable videomode autoselected

Status in X.org xf86-video-r128:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  I tested Ubunti 7.10-beta-desktop-i386 on my PCs.

  At one PC the X-Server was not able to start, and i saw only the
  commandline.

  This PC has a  ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to 
a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline 
an got errormessages, the X-Server didn't start:
  
  auth:  creating new authority file /home/ubuntu/.serverauth.20130
  xauth:  creating new authority file /home/ubuntu/.Xauthority
  xauth:  creating new authority file /home/ubuntu/.Xauthority

  X Window System Version 1.3.0
  Release Date: 19 April 2007
  X Protocol Version 11, Revision 0, Release 1.3
  Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6)
  Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 
18:11:30 GMT 2007 i686
  Build Date: 21 September 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Module Loader present
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

  (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  1 21:58:06 2007
  (==) Using config file: "/etc/X11/xorg.conf"
  (II) Module already built-in
  (II) Module already built-in
  (II) Module already built-in
  (EE) R128(0): No DFP detected
  (II) Module already built-in
  (EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

  Fatal server error:
  AddScreen/ScreenInit failed for driver 0

  XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

  
***
  The /etc/X11/xorg.conf:
  
***
  # xorg.conf (xorg X Window System server configuration file)
  #
  # This file was generated by dexconf, the Debian X Configuration tool, using
  # values from the debconf database.
  #
  # Edit this file with caution, and see the xorg.conf manual page.
  # (Type "man xorg.conf" at the shell prompt.)
  #
  # This file is automatically updated on xserver-xorg package upgrades *only*
  # if it has not been modified since the last upgrade of the xserver-xorg
  # package.
  #
  # If you have edited this file but would like it to be automatically updated
  # again, run the following command:
  #   sudo dpkg-reconfigure -phigh xserver-xorg

  Section "Files"
  EndSection

  Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "de"
  EndSection

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons"   "true"
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "stylus"
Option  "Device""/dev/input/wacom"
Option  "Type"  "stylus"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "eraser"
Option  "Device""/dev/input/wacom"
Option  "Type"  "eraser"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "cursor"
Option  "Device""/dev/input/wacom"
Option  "Type"  "cursor"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "Device"
Identifier  "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
Driver  "ati"
BusID   "PCI:1:0:0"
  EndSection

  Section "Monitor"
Identifier  "108080"
Option  "DPMS"
  EndSection

  

[Desktop-packages] [Bug 520671] Re: No icons on Geode thin client

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  No icons on Geode thin client

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-geode package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-geode package in Debian:
  Fix Released

Bug description:
  Binary package hint: xorg

  Lucid 10.04 Alpha daily cd image

  Linux 200608-21 2.6.32-13-generic #18-Ubuntu SMP Wed Feb 10 21:24:20
  UTC 2010 i586 GNU/Linux

  In the attached screenshots we can see that there are no icons in the
  menus or in nautilus and some gnome applets won't show properly
  (network, volume, email notifications...). It's a fresh install, no
  updates.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Feb 11 15:30:40 2010
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100211.1)
  Lsusb:
   Bus 002 Device 003: ID 0566:3002 Monterey International Corp. 
   Bus 002 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 004: ID 13fe:1d00 Kingston Technology Company Inc. 
DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: xorg 1:7.5+1ubuntu2
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic 
root=UUID=d43f10f2-3a3e-444a-bb09-ba3c70705955 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
  RelatedPackageVersions:
   xserver-xorg 1:7.5+1ubuntu2
   libgl1-mesa-glx 7.7-0ubuntu8
   libdrm2 2.4.17-0ubuntu2
   xserver-xorg-video-intel 2:2.9.1-1ubuntu4
  SourcePackage: xorg
  Uname: Linux 2.6.32-13-generic i586
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   architecture:   i586kernel: 2.6.32-13-generic
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
  Lsusb:
   Bus 002 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard
   Bus 002 Device 002: ID 413c:3200 Dell Computer Corp. Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 004: ID 13fe:1d00 Kingston Technology Company Inc. 
DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: xserver-xorg-video-geode 2.11.7-1
  PackageArchitecture: i386
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=20b94a47-9f3b-40a0-a94a-188b712150d9 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Tags: lucid lucid
  Uname: Linux 2.6.32-19-generic i586
  UnreportableReason: This is not a genuine Ubuntu package
  UserGroups:
   
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i586
   kernel: 2.6.32-19-generic

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

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


[Desktop-packages] [Bug 520925] Re: [i810e] Can only get 1024x768, native 1152x864 mode deleted

2018-06-12 Thread Bug Watch Updater
Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=26561.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-02-14T00:23:34+00:00 Geir Ove Myhr wrote:

Created attachment 33285
Xorg.0.log

Originally reported at:
  https://bugs.launchpad.net/bugs/520925

[Problem] 
Monitor supports 1152x864, but this resolution is not available through xrandr. 
Not sure if this is due to bad EDID (so it would need an EDID quirk) or if the 
driver is interpreting it wrong.

[Original report]

My monitor samtron 56v supports 1152*864
but I cant set that resolution

In display preferences ... ( system -> preferences -? Display preference )
It shows as unknown monitor
I can get 1024*768 resolution
In windows XP I can have 1152*864

i have intel 810 motherboard and intel 82810E display

Ubuntu 9.10 (now I have updated to pre release of 10.04)

Xorg.0.log shows:
(II) intel(0): Not using driver mode "1152x864" (mode clock too high)


---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: xserver-xorg-video-intel 2:2.10.0+git20100120.93cd943d-0ubuntu0sarvatt
PackageArchitecture: i386
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu1
 libgl1-mesa-glx 7.8.0~git20100121.4736e1cb-0ubuntu0sarvatt
 libdrm2 2.4.17+git20100120.9de34e2d-0ubuntu0sarvatt2
 xserver-xorg-video-intel 2:2.10.0+git20100120.93cd943d-0ubuntu0sarvatt
 xserver-xorg-video-ati 1:6.12.99+git20100120.30a19b75-0ubuntu0sarvatt
Tags: lucid
Uname: Linux 2.6.33-020633rc5-generic i686
UnreportableReason: This is not a genuine Ubuntu package
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
system:
 distro: Ubuntu
 architecture:   i686kernel: 2.6.33-020633rc5-generic

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/13


On 2010-02-14T00:24:04+00:00 Geir Ove Myhr wrote:

Created attachment 33286
dmesg output

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/14


On 2010-02-14T00:24:34+00:00 Geir Ove Myhr wrote:

Created attachment 33287
xrandr --verbose

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/15


On 2010-02-14T00:25:08+00:00 Geir Ove Myhr wrote:

Created attachment 33288
lspci -vvnn

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/16


On 2010-04-06T11:33:58+00:00 Jesse Barnes wrote:

Can you manually create a working modeline using xrandr for the 1152x864
mode?

Yakui, can you take a look?  Maybe we just need another hsync quirk or
something for this mode.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/25


On 2010-08-09T07:52:30+00:00 Ajax-a wrote:

(In reply to comment #4)
> Can you manually create a working modeline using xrandr for the 1152x864 mode?
> 
> Yakui, can you take a look?  Maybe we just need another hsync quirk or
> something for this mode.

This is actually an xserver bug.  KMS rounds up the pixel clock limit
based on all modes found in EDID; X only does so for detailed timings.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/29


On 2011-10-09T03:31:21+00:00 Jeremy Huddleston wrote:

Is this still an issue?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/30


On 2018-06-12T18:43:00+00:00 Ajax-a wrote:

Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/520925/comments/32


** Changed in: xserver-xorg-video-intel
   Status: Confirmed => Invalid

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

Title:
  [i810e] Can only get 1024x768,  native 1152x864 mode deleted

Status in xf86-video-intel:
  

[Desktop-packages] [Bug 80940]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  ati radeon driver does not autodetect displaysize on Latitude D600,
  therefore uses wrong resolution

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-driver-ati

  Since Hoary up to Feisty Herd2, the xorg ati/radeon driver never detected the 
right physical
  dimension of the display.  So  dpi is set to 75 instead of 125.  This results
  in fonts that almost half as wide and height as it should be.

  Using DisplaySize in Monitor section of xorg.conf  fixes it, but that's not 
autodetection
  (as works perfect with i810 on other laptops)

  $ grep DisplaySize /etc/X11/xorg.conf
  DisplaySize 286 214

  $ xdpyinfo | egrep 'dimens|resolu'
dimensions:1400x1050 pixels (287x215 millimeters)
resolution:124x124 dots per inch

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

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


[Desktop-packages] [Bug 401045]

2018-06-12 Thread Ajax-a
*** Bug 25840 has been marked as a duplicate of this bug. ***

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

Title:
  X crashes in FindGlyphByHash

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

Bug description:
  In karmic X session exits, kills all applications that are running and 
returns to the login prompt.
  Description:  Ubuntu karmic (development branch)
  Release:  9.10

  Xorg.0.log.old gives:

  Backtrace:
  0: /usr/bin/X(xorg_backtrace+0x3b) [0x81353db]
  1: /usr/bin/X(xf86SigHandler+0x55) [0x80c3185]
  2: [0x718400]
  3: /usr/bin/X(FindGlyphByHash+0x3c) [0x816f9dc]
  4: /usr/bin/X [0x817c30c]
  5: /usr/bin/X [0x8175455]
  6: /usr/bin/X(Dispatch+0x33f) [0x808d67f]
  7: /usr/bin/X(main+0x3bd) [0x80723dd]
  8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb2c7a5]
  9: /usr/bin/X [0x8071891]
  Saw signal 11.  Server aborting.

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

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


[Desktop-packages] [Bug 148117]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  [r128] Rage 128: Unsuitable videomode autoselected

Status in X.org xf86-video-r128:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  I tested Ubunti 7.10-beta-desktop-i386 on my PCs.

  At one PC the X-Server was not able to start, and i saw only the
  commandline.

  This PC has a  ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to 
a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline 
an got errormessages, the X-Server didn't start:
  
  auth:  creating new authority file /home/ubuntu/.serverauth.20130
  xauth:  creating new authority file /home/ubuntu/.Xauthority
  xauth:  creating new authority file /home/ubuntu/.Xauthority

  X Window System Version 1.3.0
  Release Date: 19 April 2007
  X Protocol Version 11, Revision 0, Release 1.3
  Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6)
  Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 
18:11:30 GMT 2007 i686
  Build Date: 21 September 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Module Loader present
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

  (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  1 21:58:06 2007
  (==) Using config file: "/etc/X11/xorg.conf"
  (II) Module already built-in
  (II) Module already built-in
  (II) Module already built-in
  (EE) R128(0): No DFP detected
  (II) Module already built-in
  (EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

  Fatal server error:
  AddScreen/ScreenInit failed for driver 0

  XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

  
***
  The /etc/X11/xorg.conf:
  
***
  # xorg.conf (xorg X Window System server configuration file)
  #
  # This file was generated by dexconf, the Debian X Configuration tool, using
  # values from the debconf database.
  #
  # Edit this file with caution, and see the xorg.conf manual page.
  # (Type "man xorg.conf" at the shell prompt.)
  #
  # This file is automatically updated on xserver-xorg package upgrades *only*
  # if it has not been modified since the last upgrade of the xserver-xorg
  # package.
  #
  # If you have edited this file but would like it to be automatically updated
  # again, run the following command:
  #   sudo dpkg-reconfigure -phigh xserver-xorg

  Section "Files"
  EndSection

  Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "de"
  EndSection

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons"   "true"
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "stylus"
Option  "Device""/dev/input/wacom"
Option  "Type"  "stylus"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "eraser"
Option  "Device""/dev/input/wacom"
Option  "Type"  "eraser"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "cursor"
Option  "Device""/dev/input/wacom"
Option  "Type"  "cursor"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "Device"
Identifier  "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
Driver  "ati"
BusID   

[Desktop-packages] [Bug 148117]

2018-06-12 Thread Bugzi11-fdo-tormod
Yes, this is still the same on Ubuntu 10.10 which has xserver 1.9.0.

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

Title:
  [r128] Rage 128: Unsuitable videomode autoselected

Status in X.org xf86-video-r128:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  I tested Ubunti 7.10-beta-desktop-i386 on my PCs.

  At one PC the X-Server was not able to start, and i saw only the
  commandline.

  This PC has a  ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to 
a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline 
an got errormessages, the X-Server didn't start:
  
  auth:  creating new authority file /home/ubuntu/.serverauth.20130
  xauth:  creating new authority file /home/ubuntu/.Xauthority
  xauth:  creating new authority file /home/ubuntu/.Xauthority

  X Window System Version 1.3.0
  Release Date: 19 April 2007
  X Protocol Version 11, Revision 0, Release 1.3
  Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6)
  Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 
18:11:30 GMT 2007 i686
  Build Date: 21 September 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Module Loader present
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

  (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  1 21:58:06 2007
  (==) Using config file: "/etc/X11/xorg.conf"
  (II) Module already built-in
  (II) Module already built-in
  (II) Module already built-in
  (EE) R128(0): No DFP detected
  (II) Module already built-in
  (EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

  Fatal server error:
  AddScreen/ScreenInit failed for driver 0

  XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

  
***
  The /etc/X11/xorg.conf:
  
***
  # xorg.conf (xorg X Window System server configuration file)
  #
  # This file was generated by dexconf, the Debian X Configuration tool, using
  # values from the debconf database.
  #
  # Edit this file with caution, and see the xorg.conf manual page.
  # (Type "man xorg.conf" at the shell prompt.)
  #
  # This file is automatically updated on xserver-xorg package upgrades *only*
  # if it has not been modified since the last upgrade of the xserver-xorg
  # package.
  #
  # If you have edited this file but would like it to be automatically updated
  # again, run the following command:
  #   sudo dpkg-reconfigure -phigh xserver-xorg

  Section "Files"
  EndSection

  Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "de"
  EndSection

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons"   "true"
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "stylus"
Option  "Device""/dev/input/wacom"
Option  "Type"  "stylus"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "eraser"
Option  "Device""/dev/input/wacom"
Option  "Type"  "eraser"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "cursor"
Option  "Device""/dev/input/wacom"
Option  "Type"  "cursor"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "Device"
Identifier  "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
Driver  "ati"
BusID   "PCI:1:0:0"
  EndSection

  Section "Monitor"
Identifier  "108080"
Option  "DPMS"
  EndSection

  Section 

[Desktop-packages] [Bug 148117]

2018-06-12 Thread Jeremy Huddleston
This is coming from R128InitDDARegisters during init in r128_driver.c:

Roff  = XclksPerTransferPrecise * (DisplayFifoDepth - 4);

Ron   = (4 * info->ram->MB
 + 3 * MAX(info->ram->Trcd - 2, 0)
 + 2 * info->ram->Trp
 + info->ram->Twr
 + info->ram->CL
 + info->ram->Tr2w
 + XclksPerTransfer) << (11 - UseablePrecision);

Not that it helps me much, but maybe someone can work with that...

That being said, this driver isn't really maintained anymore since it's not 
used my modern devices... so I'm not sure this will ever be fixed.

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

Title:
  [r128] Rage 128: Unsuitable videomode autoselected

Status in X.org xf86-video-r128:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  I tested Ubunti 7.10-beta-desktop-i386 on my PCs.

  At one PC the X-Server was not able to start, and i saw only the
  commandline.

  This PC has a  ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to 
a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline 
an got errormessages, the X-Server didn't start:
  
  auth:  creating new authority file /home/ubuntu/.serverauth.20130
  xauth:  creating new authority file /home/ubuntu/.Xauthority
  xauth:  creating new authority file /home/ubuntu/.Xauthority

  X Window System Version 1.3.0
  Release Date: 19 April 2007
  X Protocol Version 11, Revision 0, Release 1.3
  Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6)
  Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 
18:11:30 GMT 2007 i686
  Build Date: 21 September 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Module Loader present
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

  (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  1 21:58:06 2007
  (==) Using config file: "/etc/X11/xorg.conf"
  (II) Module already built-in
  (II) Module already built-in
  (II) Module already built-in
  (EE) R128(0): No DFP detected
  (II) Module already built-in
  (EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

  Fatal server error:
  AddScreen/ScreenInit failed for driver 0

  XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

  
***
  The /etc/X11/xorg.conf:
  
***
  # xorg.conf (xorg X Window System server configuration file)
  #
  # This file was generated by dexconf, the Debian X Configuration tool, using
  # values from the debconf database.
  #
  # Edit this file with caution, and see the xorg.conf manual page.
  # (Type "man xorg.conf" at the shell prompt.)
  #
  # This file is automatically updated on xserver-xorg package upgrades *only*
  # if it has not been modified since the last upgrade of the xserver-xorg
  # package.
  #
  # If you have edited this file but would like it to be automatically updated
  # again, run the following command:
  #   sudo dpkg-reconfigure -phigh xserver-xorg

  Section "Files"
  EndSection

  Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "de"
  EndSection

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons"   "true"
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "stylus"
Option  "Device""/dev/input/wacom"
Option  "Type"  "stylus"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "eraser"
Option  "Device""/dev/input/wacom"
Option  "Type"  "eraser"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
 

[Desktop-packages] [Bug 148117]

2018-06-12 Thread Mattst88
Is this still a problem?

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

Title:
  [r128] Rage 128: Unsuitable videomode autoselected

Status in X.org xf86-video-r128:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  I tested Ubunti 7.10-beta-desktop-i386 on my PCs.

  At one PC the X-Server was not able to start, and i saw only the
  commandline.

  This PC has a  ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to 
a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline 
an got errormessages, the X-Server didn't start:
  
  auth:  creating new authority file /home/ubuntu/.serverauth.20130
  xauth:  creating new authority file /home/ubuntu/.Xauthority
  xauth:  creating new authority file /home/ubuntu/.Xauthority

  X Window System Version 1.3.0
  Release Date: 19 April 2007
  X Protocol Version 11, Revision 0, Release 1.3
  Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6)
  Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 
18:11:30 GMT 2007 i686
  Build Date: 21 September 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Module Loader present
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

  (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct  1 21:58:06 2007
  (==) Using config file: "/etc/X11/xorg.conf"
  (II) Module already built-in
  (II) Module already built-in
  (II) Module already built-in
  (EE) R128(0): No DFP detected
  (II) Module already built-in
  (EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

  Fatal server error:
  AddScreen/ScreenInit failed for driver 0

  XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

  
***
  The /etc/X11/xorg.conf:
  
***
  # xorg.conf (xorg X Window System server configuration file)
  #
  # This file was generated by dexconf, the Debian X Configuration tool, using
  # values from the debconf database.
  #
  # Edit this file with caution, and see the xorg.conf manual page.
  # (Type "man xorg.conf" at the shell prompt.)
  #
  # This file is automatically updated on xserver-xorg package upgrades *only*
  # if it has not been modified since the last upgrade of the xserver-xorg
  # package.
  #
  # If you have edited this file but would like it to be automatically updated
  # again, run the following command:
  #   sudo dpkg-reconfigure -phigh xserver-xorg

  Section "Files"
  EndSection

  Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "de"
  EndSection

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons"   "true"
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "stylus"
Option  "Device""/dev/input/wacom"
Option  "Type"  "stylus"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "eraser"
Option  "Device""/dev/input/wacom"
Option  "Type"  "eraser"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "InputDevice"
Driver  "wacom"
Identifier  "cursor"
Option  "Device""/dev/input/wacom"
Option  "Type"  "cursor"
Option  "ForceDevice"   "ISDV4" # Tablet PC ONLY
  EndSection

  Section "Device"
Identifier  "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
Driver  "ati"
BusID   "PCI:1:0:0"
  EndSection

  Section "Monitor"
Identifier  "108080"
Option  "DPMS"
  EndSection

  Section "Screen"
Identifier  "Default 

[Desktop-packages] [Bug 211897]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  Xorg crashed with SIGSEGV in xf86RandR12SetRotations()

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  I noticed that just enabling xinerama causes a segmentation fault. As
  mentioned in the wiki, I enabled NoTrapSignals. xorg.conf and
  associated log is attached, the very same configuration without
  xinerama works fine. The crash is very easily reproducable on my
  laptop, if you need any more information, just ask.

  $ lsb_release -rd
  Description:Ubuntu hardy (development branch)
  Release:8.04
  $ apt-cache policy xorg
  xorg:
Installed: 1:7.3+10ubuntu7
Candidate: 1:7.3+10ubuntu7
Version table:
   *** 1:7.3+10ubuntu7 0
  700 http://de.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status
   1:7.2-5 0
  650 http://ftp.de.debian.org testing/main Packages
  $ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.2.1-1ubuntu6
Candidate: 2:2.2.1-1ubuntu6
Version table:
   *** 2:2.2.1-1ubuntu6 0
  700 http://de.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status
   2:2.1.0-2 0
  650 http://ftp.de.debian.org testing/main Packages
  $ apt-cache policy xserver-xorg-video-i810
  xserver-xorg-video-i810:
Installed: 2:1.7.4-0ubuntu7
Candidate: 2:1.7.4-0ubuntu7
Version table:
   2:2.1.0-2 0
  650 http://ftp.de.debian.org testing/main Packages
   *** 2:1.7.4-0ubuntu7 0
  700 http://de.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  Architecture: amd64
  Date: Fri Apr  4 19:44:29 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/Xorg
  Package: xserver-xorg-core 2:1.4.1~git20080131-1ubuntu6 [modified: 
usr/bin/Xorg usr/bin/cvt usr/bin/gtf]
  PackageArchitecture: amd64
  ProcCmdline: X :1 -config xinerama.xorg.conf
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   xf86RandR12SetRotations (
   xf86CrtcScreenInit (screen=0xa20730)
   ?? ()
   AddScreen (pfnInit=0x7f9a08aa79f0, argc=4, 
   InitOutput (pScreenInfo=0x7f1d20, argc=4,
  Title: Xorg crashed with SIGSEGV in xf86RandR12SetRotations()
  Uname: Linux 2.6.24-14-generic x86_64
  UserGroups:

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

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


[Desktop-packages] [Bug 520671]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and
is not obviously still valid. Please file a new report if you continue
to experience issues with a current server.

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

Title:
  No icons on Geode thin client

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-geode package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-geode package in Debian:
  Fix Released

Bug description:
  Binary package hint: xorg

  Lucid 10.04 Alpha daily cd image

  Linux 200608-21 2.6.32-13-generic #18-Ubuntu SMP Wed Feb 10 21:24:20
  UTC 2010 i586 GNU/Linux

  In the attached screenshots we can see that there are no icons in the
  menus or in nautilus and some gnome applets won't show properly
  (network, volume, email notifications...). It's a fresh install, no
  updates.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Feb 11 15:30:40 2010
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100211.1)
  Lsusb:
   Bus 002 Device 003: ID 0566:3002 Monterey International Corp. 
   Bus 002 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 004: ID 13fe:1d00 Kingston Technology Company Inc. 
DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: xorg 1:7.5+1ubuntu2
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic 
root=UUID=d43f10f2-3a3e-444a-bb09-ba3c70705955 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
  RelatedPackageVersions:
   xserver-xorg 1:7.5+1ubuntu2
   libgl1-mesa-glx 7.7-0ubuntu8
   libdrm2 2.4.17-0ubuntu2
   xserver-xorg-video-intel 2:2.9.1-1ubuntu4
  SourcePackage: xorg
  Uname: Linux 2.6.32-13-generic i586
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   architecture:   i586kernel: 2.6.32-13-generic
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
  Lsusb:
   Bus 002 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard
   Bus 002 Device 002: ID 413c:3200 Dell Computer Corp. Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 004: ID 13fe:1d00 Kingston Technology Company Inc. 
DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: xserver-xorg-video-geode 2.11.7-1
  PackageArchitecture: i386
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=20b94a47-9f3b-40a0-a94a-188b712150d9 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Tags: lucid lucid
  Uname: Linux 2.6.32-19-generic i586
  UnreportableReason: This is not a genuine Ubuntu package
  UserGroups:
   
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i586
   kernel: 2.6.32-19-generic

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

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


[Desktop-packages] [Bug 1762801] Re: Xwayland crashed with signal 7 in XkbDeviceApplyKeymap()

2018-06-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1774723 ***
https://bugs.launchpad.net/bugs/1774723

Although the binary is different, the stack is identical. Let's call
this bug 1774723.

Both Xorg and Xwayland share the same source so it makes sense to group
them.

** This bug has been marked a duplicate of bug 1774723
   Xorg crashed with signal 7 in XkbCopyKeymap() from XkbCopyKeymap() from 
XkbDeviceApplyKeymap() from CopyKeyClass() from DeepCopyKeyboardClasses()

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

Title:
  Xwayland crashed with signal 7 in XkbDeviceApplyKeymap()

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Apr  7 17:18:23 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13ed]
  InstallationDate: Installed on 2018-03-01 (40 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: ASUSTeK COMPUTER INC. S301LA
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcEnviron:
   LANGUAGE=es_BO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_BO.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=47cb83ff-b68f-4365-9a97-07b0b4723c16 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   XkbDeviceApplyKeymap ()
   ?? ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with signal 7 in XkbDeviceApplyKeymap()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S301LA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: S301LA
  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.:bvrS301LA.205:bd08/19/2013:svnASUSTeKCOMPUTERINC.:pnS301LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS301LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: S
  dmi.product.name: S301LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1774723] Re: Xorg/Xwayland crashed with signal 7 in XkbCopyKeymap() from XkbCopyKeymap() from XkbDeviceApplyKeymap() from CopyKeyClass() from DeepCopyKeyboardClasses()

2018-06-12 Thread Daniel van Vugt
** Summary changed:

- Xorg crashed with signal 7 in XkbCopyKeymap() from XkbCopyKeymap() from 
XkbDeviceApplyKeymap() from CopyKeyClass() from DeepCopyKeyboardClasses()
+ Xorg/Xwayland crashed with signal 7 in XkbCopyKeymap() from XkbCopyKeymap() 
from XkbDeviceApplyKeymap() from CopyKeyClass() from DeepCopyKeyboardClasses()

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

Title:
  Xorg/Xwayland crashed with signal 7 in XkbCopyKeymap() from
  XkbCopyKeymap() from XkbDeviceApplyKeymap() from CopyKeyClass() from
  DeepCopyKeyboardClasses()

Status in xorg-server package in Ubuntu:
  Confirmed

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

  ---

  Many times over the last few weeks, when I open my laptop after a
  sleep, I'm eventually greeted not by the desktop, but by a login
  screen, because Xorg has crashed.

  I'm running bionic on a Lenovo ThinkPad X230, often with two external 
monitors.
  Nothing else unusual offhand.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 10:16:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1523633505
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2018-05-01 (30 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 343522U
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcCwd: /home/neal
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   XkbDeviceApplyKeymap ()
   ?? ()
   ?? ()
   ?? ()
  Title: Xorg crashed with signal 7 in XkbDeviceApplyKeymap()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1749150] Re: Spontaneous single window freezing

2018-06-12 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  Spontaneous single window freezing

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  

[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2018-06-12 Thread Daniel van Vugt
Probably, but not definitely. I've nominated xenial for a fix in case we
can.

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  When the connection drops temporarily, using A2DP, a noticeable latency is 
introduced, and the audio goes out of sync.

  [Test Case]
  1) Enable the -proposed repository, and install the new pulseaudio

  2) Restart your computer, connect it to a bluetooth device (e.g. a
  headset or a speaker), play one or more videos either locally or
  online, and see if you can still reproduce the problem.

  [Regression Potential]
  Low, as the changes are upstream, and, if anything, it should also fix a 
memory leak.

  Furthermore, the changes only affect the bluez5-device module, in
  pulseaudio, and they make the buffer updating logic more conscious of
  how things can change when the connection drops. This is unlikely to
  affect anything else in pulseaudio.

  
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working 
properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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


[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2018-06-12 Thread Yale Huang
@egor-tensin Thanks. Your walk-around works.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

2018-06-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: update-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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


[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

2018-06-12 Thread Jiwon Kim
** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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


[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2018-06-12 Thread Egor Tensin
> Comment here only if you think the duplicate status is wrong.

Or I won't.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2018-06-12 Thread Egor Tensin
I had a lot of trouble with NetworkManager+OpenVPN on Ubuntu and
discovered a couple of workarounds.

If you're having trouble resolving internal domain names (like
*.internal.company.com), you might want to try adding something like
this to the [ipv4] section in /etc/NetworkManager/system-
connections/YOUR_VPN_CONNECTION:

dns-search=internal.company.com;

If you want to direct all DNS lookups through your VPN, try adding

dns-priority=-1

to the same section. But this will disable all DNS servers except for
the VPN, so if you have a local DNS server, local domain names will stop
resolving.

I'm using Ubuntu 18.04 & network-manager 1.10.6-2ubuntu1.

I'll duplicate this message in #1671606.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 175243]

2018-06-12 Thread Alexdeucher
Is this still an issue with kms or newer versions of the driver?

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

Title:
  [Mobility 9000] screen flickers only if text tty entered (radeon)

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I "upgraded" to Gutsy by doing a clean install a couple of days ago and now 
have noticed a strange screen flickering bug.
  I have a radeon mobility 9000 on a Dell Inspiron 600m, and did not have this 
problem previously with Feisty Fawn.

  The bug is screen flickering in text consoles _and_ X. Interestingly, though, 
this bug does not occur if I boot into splash and then
  it goes straight to X. I am able to log on and use desktop effects and such 
without any flicker. However, the moment it has to
  switch to a text tty/vt, whether through a Ctrl-Alt-Fn or after I log out 
when X restarts, it starts flickering and the flicker makes
  everything pretty much unusable (well quite annoying at least). I tried 
booting with vga=normal but that doesn't change anything. No splash on boot 
doesn't help.

  I believe this has something to do with the new text tty changes in Gutsy vs 
Feisty, but am not sure exactly what these are, so if someone has some advice 
maybe on something I can do to try to mess with these that would be great (I'm 
pretty sure it's not
  an X issue per se b/c it does not seem to happen the first time X starts and 
I log on after splash; oh yeah also it does _not_ happen when BIOS is starting 
and in the initial splash; however after we go to tty I can't get the flicker 
to stop).

  Thanks a lot
  Misha

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

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


[Desktop-packages] [Bug 175243] Re: [Mobility 9000] screen flickers only if text tty entered (radeon)

2018-06-12 Thread Bug Watch Updater
** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => Invalid

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

Title:
  [Mobility 9000] screen flickers only if text tty entered (radeon)

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I "upgraded" to Gutsy by doing a clean install a couple of days ago and now 
have noticed a strange screen flickering bug.
  I have a radeon mobility 9000 on a Dell Inspiron 600m, and did not have this 
problem previously with Feisty Fawn.

  The bug is screen flickering in text consoles _and_ X. Interestingly, though, 
this bug does not occur if I boot into splash and then
  it goes straight to X. I am able to log on and use desktop effects and such 
without any flicker. However, the moment it has to
  switch to a text tty/vt, whether through a Ctrl-Alt-Fn or after I log out 
when X restarts, it starts flickering and the flicker makes
  everything pretty much unusable (well quite annoying at least). I tried 
booting with vga=normal but that doesn't change anything. No splash on boot 
doesn't help.

  I believe this has something to do with the new text tty changes in Gutsy vs 
Feisty, but am not sure exactly what these are, so if someone has some advice 
maybe on something I can do to try to mess with these that would be great (I'm 
pretty sure it's not
  an X issue per se b/c it does not seem to happen the first time X starts and 
I log on after splash; oh yeah also it does _not_ happen when BIOS is starting 
and in the initial splash; however after we go to tty I can't get the flicker 
to stop).

  Thanks a lot
  Misha

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

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


[Desktop-packages] [Bug 175243]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  [Mobility 9000] screen flickers only if text tty entered (radeon)

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I "upgraded" to Gutsy by doing a clean install a couple of days ago and now 
have noticed a strange screen flickering bug.
  I have a radeon mobility 9000 on a Dell Inspiron 600m, and did not have this 
problem previously with Feisty Fawn.

  The bug is screen flickering in text consoles _and_ X. Interestingly, though, 
this bug does not occur if I boot into splash and then
  it goes straight to X. I am able to log on and use desktop effects and such 
without any flicker. However, the moment it has to
  switch to a text tty/vt, whether through a Ctrl-Alt-Fn or after I log out 
when X restarts, it starts flickering and the flicker makes
  everything pretty much unusable (well quite annoying at least). I tried 
booting with vga=normal but that doesn't change anything. No splash on boot 
doesn't help.

  I believe this has something to do with the new text tty changes in Gutsy vs 
Feisty, but am not sure exactly what these are, so if someone has some advice 
maybe on something I can do to try to mess with these that would be great (I'm 
pretty sure it's not
  an X issue per se b/c it does not seem to happen the first time X starts and 
I log on after splash; oh yeah also it does _not_ happen when BIOS is starting 
and in the initial splash; however after we go to tty I can't get the flicker 
to stop).

  Thanks a lot
  Misha

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

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


[Desktop-packages] [Bug 175243]

2018-06-12 Thread Luigi Toscano
(In reply to comment #8)
> Is this still an issue with kms or newer versions of the driver?

Yes, it is (sorry for my lack of updates), but with KMS is different. I'm 
currently using Debian Squeeze:
xserver-xorg-video-radeon 1:6.13.1-2
xserver-xorg  1:7.5+7
xserver-xorg-core 2:1.7.7-8
libdrm2   2.4.21-1~squeeze3
linux-image-2.6.32-5-686  2.6.32-26 (it contains drm from 2.6.34)

When KMS is turned on (default behaviour), the flickering stars when (I think) 
the kernel module is loaded (I don't know if radeon or drm) and when Xorg 
starts, the flickering is fixed (just like Xorg change some values) and virtual 
consoles work again.
How can I help to debug this issue?

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

Title:
  [Mobility 9000] screen flickers only if text tty entered (radeon)

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I "upgraded" to Gutsy by doing a clean install a couple of days ago and now 
have noticed a strange screen flickering bug.
  I have a radeon mobility 9000 on a Dell Inspiron 600m, and did not have this 
problem previously with Feisty Fawn.

  The bug is screen flickering in text consoles _and_ X. Interestingly, though, 
this bug does not occur if I boot into splash and then
  it goes straight to X. I am able to log on and use desktop effects and such 
without any flicker. However, the moment it has to
  switch to a text tty/vt, whether through a Ctrl-Alt-Fn or after I log out 
when X restarts, it starts flickering and the flicker makes
  everything pretty much unusable (well quite annoying at least). I tried 
booting with vga=normal but that doesn't change anything. No splash on boot 
doesn't help.

  I believe this has something to do with the new text tty changes in Gutsy vs 
Feisty, but am not sure exactly what these are, so if someone has some advice 
maybe on something I can do to try to mess with these that would be great (I'm 
pretty sure it's not
  an X issue per se b/c it does not seem to happen the first time X starts and 
I log on after splash; oh yeah also it does _not_ happen when BIOS is starting 
and in the initial splash; however after we go to tty I can't get the flicker 
to stop).

  Thanks a lot
  Misha

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

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


[Desktop-packages] [Bug 175243]

2018-06-12 Thread Julien Cristau
> --- Comment #9 from Luigi Toscano  2010-10-28 
> 13:57:05 PDT ---
> linux-image-2.6.32-5-686  2.6.32-26 (it contains drm from 2.6.34)
> 
from .33 (plus various fixes) actually.

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

Title:
  [Mobility 9000] screen flickers only if text tty entered (radeon)

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  I "upgraded" to Gutsy by doing a clean install a couple of days ago and now 
have noticed a strange screen flickering bug.
  I have a radeon mobility 9000 on a Dell Inspiron 600m, and did not have this 
problem previously with Feisty Fawn.

  The bug is screen flickering in text consoles _and_ X. Interestingly, though, 
this bug does not occur if I boot into splash and then
  it goes straight to X. I am able to log on and use desktop effects and such 
without any flicker. However, the moment it has to
  switch to a text tty/vt, whether through a Ctrl-Alt-Fn or after I log out 
when X restarts, it starts flickering and the flicker makes
  everything pretty much unusable (well quite annoying at least). I tried 
booting with vga=normal but that doesn't change anything. No splash on boot 
doesn't help.

  I believe this has something to do with the new text tty changes in Gutsy vs 
Feisty, but am not sure exactly what these are, so if someone has some advice 
maybe on something I can do to try to mess with these that would be great (I'm 
pretty sure it's not
  an X issue per se b/c it does not seem to happen the first time X starts and 
I log on after splash; oh yeah also it does _not_ happen when BIOS is starting 
and in the initial splash; however after we go to tty I can't get the flicker 
to stop).

  Thanks a lot
  Misha

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

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


[Desktop-packages] [Bug 255826] Re: scrolling in Firefox causes Xorg-process to lag (S3 Savage driver)

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  scrolling in Firefox causes Xorg-process to lag (S3 Savage driver)

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-savage package in Ubuntu:
  Invalid

Bug description:
  In a new installation of Xubuntu hardy from alternate CD on an old
  Toshiba Satellite Pro 4300 Series everything seems to work but when
  using the scroll bar in Firefox the system becames unstable and must
  be rebooted to recover.

  The only change necessary for it to work was adding acpi=force at
  Kernel boot up.

  When this happen:
  - The display is not correctly updated / refreshed
  - The Xorg process consumes more CPU than normal (~30/40%)
  - Everything related to graphical windows slows down, but terminals (opened 
before) work correctly.

  Here is some information about the system and configuration:

  jordi@canigo:~$ lspci 
  00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (rev 03)
  00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge 
(rev 03)
  00:05.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
  00:05.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  00:05.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
  00:05.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
  00:07.0 Communication controller: Agere Systems 56k WinModem (rev 01)
  00:09.0 IRDA controller: Toshiba America Info Systems FIR Port Type-DO
  00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
Bridge with ZV Support (rev 20)
  00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
Bridge with ZV Support (rev 20)
  00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio 
Controller] (rev 02)
  01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11)
  06:00.0 Network controller: RaLink RT2561/RT61 rev B 802.11g

  jordi@canigo:~$ sudo lshw -C video
  [sudo] password for jordi: 
*-display UNCLAIMED 
 description: VGA compatible controller
 product: 86C270-294 Savage/IX-MV
 vendor: S3 Inc.
 physical id: 0
 bus info: pci@:01:00.0
 version: 11
 width: 32 bits
 clock: 66MHz
 capabilities: pm agp agp-1.0 vga_controller bus_master cap_list
 configuration: latency=248 maxlatency=255 mingnt=4

  The xorg.conf file only has "Configured video device" and "Configured
  Monitor", which I think is normal in Ubuntu 8.04

  I think it detects correctly the card and loads the correct driver:

  jordi@canigo:~$ lsmod | grep savage
  savage 33920  2 
  drm82452  3 savage


  If you need more information, I'll provide it.

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

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


[Desktop-packages] [Bug 194521]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  [mach64] ATI Mobility M1 -- the mouse cursor garbles some underlying
  pixels

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-mach64 package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  Using
   xserver-xorg-video-ati - 1:6.7.197+git20080217.d055b9e8-0ubuntu0tormod~gutsy

  on Sony with ATI Mobility M1

  I observe a line of garbled pixels under the mouse cursor, for example
  on the initial login screen, and then they stay there no matter what
  is redrawn, like that they are "burned in". Moving mouse cursor keep
  these pixels on the initial location, and doesn't produce new, until
  something happens, when the "burned in" pixels appear somewhere else,
  but again under the current place of the cursor.

  The effect never happens in Vesa mode. Here's conf, I don't know what
  else I should try:

  Section "Device"
Identifier  "Generic Video Card"
Boardname   "ATI Rage Mobility"
Busid   "PCI:1:0:0"
Driver  "ati"
Screen  0
Vendorname  "ATI"
Option  "MergedFB"  "off"
  EndSection

  Thanks in advance for any suggestions.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Feb 22 22:46:40 2008
  DistroRelease: Ubuntu 7.10
  Package: xserver-xorg-video-ati 
1:6.7.197+git20080217.d055b9e8-0ubuntu0tormod~gutsy
  PackageArchitecture: i386
  SourcePackage: xserver-xorg-video-ati
  Uname: Linux lino 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 
GNU/Linux
  UnreportableReason: This is not a genuine Ubuntu package

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

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


[Desktop-packages] [Bug 255826]

2018-06-12 Thread Ajax-a
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you 
continue to experience issues with current releases.

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

Title:
  scrolling in Firefox causes Xorg-process to lag (S3 Savage driver)

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-savage package in Ubuntu:
  Invalid

Bug description:
  In a new installation of Xubuntu hardy from alternate CD on an old
  Toshiba Satellite Pro 4300 Series everything seems to work but when
  using the scroll bar in Firefox the system becames unstable and must
  be rebooted to recover.

  The only change necessary for it to work was adding acpi=force at
  Kernel boot up.

  When this happen:
  - The display is not correctly updated / refreshed
  - The Xorg process consumes more CPU than normal (~30/40%)
  - Everything related to graphical windows slows down, but terminals (opened 
before) work correctly.

  Here is some information about the system and configuration:

  jordi@canigo:~$ lspci 
  00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (rev 03)
  00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge 
(rev 03)
  00:05.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
  00:05.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  00:05.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
  00:05.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
  00:07.0 Communication controller: Agere Systems 56k WinModem (rev 01)
  00:09.0 IRDA controller: Toshiba America Info Systems FIR Port Type-DO
  00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
Bridge with ZV Support (rev 20)
  00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
Bridge with ZV Support (rev 20)
  00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio 
Controller] (rev 02)
  01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11)
  06:00.0 Network controller: RaLink RT2561/RT61 rev B 802.11g

  jordi@canigo:~$ sudo lshw -C video
  [sudo] password for jordi: 
*-display UNCLAIMED 
 description: VGA compatible controller
 product: 86C270-294 Savage/IX-MV
 vendor: S3 Inc.
 physical id: 0
 bus info: pci@:01:00.0
 version: 11
 width: 32 bits
 clock: 66MHz
 capabilities: pm agp agp-1.0 vga_controller bus_master cap_list
 configuration: latency=248 maxlatency=255 mingnt=4

  The xorg.conf file only has "Configured video device" and "Configured
  Monitor", which I think is normal in Ubuntu 8.04

  I think it detects correctly the card and loads the correct driver:

  jordi@canigo:~$ lsmod | grep savage
  savage 33920  2 
  drm82452  3 savage


  If you need more information, I'll provide it.

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

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


[Desktop-packages] [Bug 255826]

2018-06-12 Thread Jeremy Huddleston
Is this still an issue?

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

Title:
  scrolling in Firefox causes Xorg-process to lag (S3 Savage driver)

Status in X.Org X server:
  Invalid
Status in xserver-xorg-video-savage package in Ubuntu:
  Invalid

Bug description:
  In a new installation of Xubuntu hardy from alternate CD on an old
  Toshiba Satellite Pro 4300 Series everything seems to work but when
  using the scroll bar in Firefox the system becames unstable and must
  be rebooted to recover.

  The only change necessary for it to work was adding acpi=force at
  Kernel boot up.

  When this happen:
  - The display is not correctly updated / refreshed
  - The Xorg process consumes more CPU than normal (~30/40%)
  - Everything related to graphical windows slows down, but terminals (opened 
before) work correctly.

  Here is some information about the system and configuration:

  jordi@canigo:~$ lspci 
  00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (rev 03)
  00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge 
(rev 03)
  00:05.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
  00:05.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  00:05.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
  00:05.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
  00:07.0 Communication controller: Agere Systems 56k WinModem (rev 01)
  00:09.0 IRDA controller: Toshiba America Info Systems FIR Port Type-DO
  00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
Bridge with ZV Support (rev 20)
  00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus 
Bridge with ZV Support (rev 20)
  00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio 
Controller] (rev 02)
  01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11)
  06:00.0 Network controller: RaLink RT2561/RT61 rev B 802.11g

  jordi@canigo:~$ sudo lshw -C video
  [sudo] password for jordi: 
*-display UNCLAIMED 
 description: VGA compatible controller
 product: 86C270-294 Savage/IX-MV
 vendor: S3 Inc.
 physical id: 0
 bus info: pci@:01:00.0
 version: 11
 width: 32 bits
 clock: 66MHz
 capabilities: pm agp agp-1.0 vga_controller bus_master cap_list
 configuration: latency=248 maxlatency=255 mingnt=4

  The xorg.conf file only has "Configured video device" and "Configured
  Monitor", which I think is normal in Ubuntu 8.04

  I think it detects correctly the card and loads the correct driver:

  jordi@canigo:~$ lsmod | grep savage
  savage 33920  2 
  drm82452  3 savage


  If you need more information, I'll provide it.

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

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


[Desktop-packages] [Bug 194521] Re: [mach64] ATI Mobility M1 -- the mouse cursor garbles some underlying pixels

2018-06-12 Thread Bug Watch Updater
** Changed in: xserver-xorg-driver-ati
   Status: Confirmed => Invalid

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

Title:
  [mach64] ATI Mobility M1 -- the mouse cursor garbles some underlying
  pixels

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-mach64 package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  Using
   xserver-xorg-video-ati - 1:6.7.197+git20080217.d055b9e8-0ubuntu0tormod~gutsy

  on Sony with ATI Mobility M1

  I observe a line of garbled pixels under the mouse cursor, for example
  on the initial login screen, and then they stay there no matter what
  is redrawn, like that they are "burned in". Moving mouse cursor keep
  these pixels on the initial location, and doesn't produce new, until
  something happens, when the "burned in" pixels appear somewhere else,
  but again under the current place of the cursor.

  The effect never happens in Vesa mode. Here's conf, I don't know what
  else I should try:

  Section "Device"
Identifier  "Generic Video Card"
Boardname   "ATI Rage Mobility"
Busid   "PCI:1:0:0"
Driver  "ati"
Screen  0
Vendorname  "ATI"
Option  "MergedFB"  "off"
  EndSection

  Thanks in advance for any suggestions.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Feb 22 22:46:40 2008
  DistroRelease: Ubuntu 7.10
  Package: xserver-xorg-video-ati 
1:6.7.197+git20080217.d055b9e8-0ubuntu0tormod~gutsy
  PackageArchitecture: i386
  SourcePackage: xserver-xorg-video-ati
  Uname: Linux lino 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 
GNU/Linux
  UnreportableReason: This is not a genuine Ubuntu package

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

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


[Desktop-packages] [Bug 194521]

2018-06-12 Thread Mattst88
Is this still a problem?

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

Title:
  [mach64] ATI Mobility M1 -- the mouse cursor garbles some underlying
  pixels

Status in xserver-xorg-driver-ati:
  Invalid
Status in xserver-xorg-video-mach64 package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-ati

  Using
   xserver-xorg-video-ati - 1:6.7.197+git20080217.d055b9e8-0ubuntu0tormod~gutsy

  on Sony with ATI Mobility M1

  I observe a line of garbled pixels under the mouse cursor, for example
  on the initial login screen, and then they stay there no matter what
  is redrawn, like that they are "burned in". Moving mouse cursor keep
  these pixels on the initial location, and doesn't produce new, until
  something happens, when the "burned in" pixels appear somewhere else,
  but again under the current place of the cursor.

  The effect never happens in Vesa mode. Here's conf, I don't know what
  else I should try:

  Section "Device"
Identifier  "Generic Video Card"
Boardname   "ATI Rage Mobility"
Busid   "PCI:1:0:0"
Driver  "ati"
Screen  0
Vendorname  "ATI"
Option  "MergedFB"  "off"
  EndSection

  Thanks in advance for any suggestions.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Feb 22 22:46:40 2008
  DistroRelease: Ubuntu 7.10
  Package: xserver-xorg-video-ati 
1:6.7.197+git20080217.d055b9e8-0ubuntu0tormod~gutsy
  PackageArchitecture: i386
  SourcePackage: xserver-xorg-video-ati
  Uname: Linux lino 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 
GNU/Linux
  UnreportableReason: This is not a genuine Ubuntu package

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

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


[Desktop-packages] [Bug 1776569] [NEW] /usr/bin/gnome-software:11:g_list_prepend:add_to_lru_cache:ensure_in_lru_cache:proxy_pixbuf_destroy:gdk_pixbuf_finalize

2018-06-12 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
software:11:g_list_prepend:add_to_lru_cache:ensure_in_lru_cache:proxy_pixbuf_destroy:gdk_pixbuf_finalize

Status in gnome-software package in Ubuntu:
  New

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

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

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


[Desktop-packages] [Bug 1773597] Re: USB flash drive won't mount

2018-06-12 Thread Roy Kimbrell
dmesg output after plugging in encrypted flash drive:

[  919.639686] usb 2-1.3: new high-speed USB device number 26 using ehci-pci
[  919.757260] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=a838
[  919.757264] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  919.757266] usb 2-1.3: Product: USB Flash Drive
[  919.757268] usb 2-1.3: Manufacturer: Lexar
[  919.757269] usb 2-1.3: SerialNumber: AAAE359Y7BWXS1P7
[  919.758328] usb-storage 2-1.3:1.0: USB Mass Storage device detected
[  919.758543] scsi host6: usb-storage 2-1.3:1.0
[  920.936918] scsi 6:0:0:0: Direct-Access LexarUSB Flash Drive  1100 
PQ: 0 ANSI: 6
[  920.937343] sd 6:0:0:0: Attached scsi generic sg2 type 0
[  920.938391] sd 6:0:0:0: [sdb] 62517248 512-byte logical blocks: (32.0 
GB/29.8 GiB)
[  920.939511] sd 6:0:0:0: [sdb] Write Protect is off
[  920.939514] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  920.940674] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[  920.948341]  sdb: sdb1
[  920.952267] sd 6:0:0:0: [sdb] Attached SCSI removable disk

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

Title:
  USB flash drive won't mount

Status in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=870f1d77-345c-44b2-99e6-79adea07159c ro quiet splash vt.handoff=1

  Ubuntu version: Ubuntu 18.04 LTS, software is up to date

  Steps to create problem:

  1. Reboot
  2. Insert USB flash drive

  USB flash drive does not appear on desktop or in Nautilus file window

  dmesg | tail

  [ 1435.463032] usb 2-1.3: new high-speed USB device number 8 using ehci-pci
  [ 1435.685760] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=c75c
  [ 1435.685763] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 1435.685765] usb 2-1.3: Product: USB Flash Drive
  [ 1435.685766] usb 2-1.3: Manufacturer: Lexar
  [ 1435.685767] usb 2-1.3: SerialNumber: D2036779FCE9EDC016EF

  lsusb

  Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth 
Mini-card
  Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / 
Trackstick
  Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
  Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 002 Device 008: ID 05dc:c75c Lexar Media, Inc. 
  Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 0c45:640f Microdia 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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


[Desktop-packages] [Bug 1773597] Re: USB flash drive won't mount

2018-06-12 Thread Roy Kimbrell
The latest Ubuntu update included Linux version 4.15.0-23-generic. This
appears, after a single test after a reboot, to have allowed a FAT-
formatted USB memory stick to be recognized and mounted. I opened the
device and copied a file to it then unmounted it with no problem.

However, the encrypted device still does not work. When inserted, a
dialog box appears that allows no input except in it. I entered the pass
phrase, but nothing happened except the pass phrase (dots only) were
spread out beyond their input area. The machine was effectively locked
out. Previously, I had power cycled the machine to get out of this
condition, but this time I had an appointment and just left it. When I
returned several hours later, the dialog box had disappeared. Yet I was
not able to access the device: a box with an error message appeared
instead. Nor could it be ejected: "Writing data to Lexar USB Flash Drive
Device should not be unplugged."

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

Title:
  USB flash drive won't mount

Status in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=870f1d77-345c-44b2-99e6-79adea07159c ro quiet splash vt.handoff=1

  Ubuntu version: Ubuntu 18.04 LTS, software is up to date

  Steps to create problem:

  1. Reboot
  2. Insert USB flash drive

  USB flash drive does not appear on desktop or in Nautilus file window

  dmesg | tail

  [ 1435.463032] usb 2-1.3: new high-speed USB device number 8 using ehci-pci
  [ 1435.685760] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=c75c
  [ 1435.685763] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 1435.685765] usb 2-1.3: Product: USB Flash Drive
  [ 1435.685766] usb 2-1.3: Manufacturer: Lexar
  [ 1435.685767] usb 2-1.3: SerialNumber: D2036779FCE9EDC016EF

  lsusb

  Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth 
Mini-card
  Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / 
Trackstick
  Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
  Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 002 Device 008: ID 05dc:c75c Lexar Media, Inc. 
  Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 0c45:640f Microdia 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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


[Desktop-packages] [Bug 1770965] Re: After upgrade and reboot, the lightdm display manager does not start

2018-06-12 Thread Brian Murray
The fix for bug 1775660 may end up fixing the ubuntu-release-upgrader
task in this bug report.

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

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

Title:
  After upgrade and reboot, the lightdm display manager does not start

Status in lightdm package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  Upon the upgrade, lightdm-kde-greeter was removed as it has become
  obsolete. That leaves the user with a system that hangs.

  I rebooted using system-recovery, and installed lightdm-gtk-greeter
  using aptitude. However, this greeter was not enabled in lightdm.conf.
  Also, the greeter was not configured with the background image for
  this release. I had to do these actions manually. Only then did
  lightdm start properly and with a nice background.

  For most users this problem will leave the system unusable forever,
  and should therefore be avoided. The obsolete greeter should be
  replaced with a suitable greeter.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Sun May 13 16:30:51 2018
  InstallationDate: Installed on 2013-02-05 (1922 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2018-05-13 12:28:57.668250
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

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

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


[Desktop-packages] [Bug 1768261] Re: Videos are getting stuck randomly at frames

2018-06-12 Thread Brian Murray
*** This bug is a duplicate of bug 1768610 ***
https://bugs.launchpad.net/bugs/1768610

** This bug is no longer a duplicate of bug 1752938
   Upgrading Ubuntu 18.04 disables GPU hardware acceleration
** This bug has been marked a duplicate of bug 1768610
   leftover conffile forces GNOME is software rendering

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

Title:
  Videos are getting stuck randomly at frames

Status in xorg package in Ubuntu:
  New

Bug description:
  Updated Ubuntu to 18.04 (from 17.10) and this problem started. Videos,
  on VLC and on Youtube, Twitch etc. on Chrome get stuck on frames. The
  video seek time also gets stuck at that frame, and then suddenly the
  video skips ahead. Audio has no issues. I am assuming it's a problem
  with the video drivers.

  I have dual graphics cards, one integrated and one dedicated(AMD
  Radeon HD 8670M). I guess my problem is similar to
  https://askubuntu.com/questions/1029205/video-playback-performance-
  issue-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May  1 19:40:21 2018
  DistUpgraded: 2018-04-26 21:50:03,842 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea]
  InstallationDate: Installed on 2016-01-21 (830 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron 5537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d287f35b-0011-4adf-a2f4-3626718405ff ro quiet splash radeon.modeset=1 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 04NGGW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron5537:pvrA08:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805010730.6487e7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805010730.6487e7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

2018-06-12 Thread Brian Murray
*** This bug is a duplicate of bug 1768610 ***
https://bugs.launchpad.net/bugs/1768610

** This bug has been marked a duplicate of bug 1768610
   leftover conffile forces GNOME is software rendering

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1694142] Re: package language-selector-gnome 0.165.4 failed to install/upgrade: підпроцес встановлено pre-removal сценарій повернув статус помилку 127

2018-06-12 Thread Brian Murray
*** This bug is a duplicate of bug 1768379 ***
https://bugs.launchpad.net/bugs/1768379

** This bug has been marked a duplicate of bug 1768379
   python3-minimal should depend on versioned version of python3-minimal

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

Title:
  package language-selector-gnome 0.165.4 failed to install/upgrade:
  підпроцес встановлено pre-removal сценарій повернув статус помилку 127

Status in language-selector package in Ubuntu:
  New

Bug description:
  after reinstall gnome-terminal and new updates, restar pc. System
  wrote about fail

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: language-selector-gnome 0.165.4
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun May 28 20:13:33 2017
  ErrorMessage: підпроцес встановлено pre-removal сценарій повернув статус 
помилку 127
  InstallationDate: Installed on 2016-11-05 (203 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: language-selector
  Title: package language-selector-gnome 0.165.4 failed to install/upgrade: 
підпроцес встановлено pre-removal сценарій повернув статус помилку 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2018-06-12 Thread Timo Aaltonen
18.0.x series is done, this would need to be added as a distro patch

** Also affects: mesa (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-06-12 Thread calvin
On Ubuntu 18.04 the problem is solved if you installed the available package by 
clicking the link below
https://bugzilla.mozilla.org/attachment.cgi?id=8974077
Here is the origin of the .deb
https://bugzilla.mozilla.org/show_bug.cgi?id=1405634

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 60180] Re: X can't handle two dual-head nvidia cards

2018-06-12 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  X can't handle two dual-head nvidia cards

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xserver-xorg

  I have two PCI Express nVidia cards, a 7900GT with one LCD, and a
  6800GT with two CRTs. There's a bug in X config parser that prevents
  it from using the second CRT. I'm using Edgy, but this has been broken
  since XFree86.

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

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


[Desktop-packages] [Bug 60180]

2018-06-12 Thread Ajax-a
MatchPciInstances is still not great, but the code _has_ changed
significantly since 2006, so this probably isn't a useful report of that
fact.

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

Title:
  X can't handle two dual-head nvidia cards

Status in X.Org X server:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xserver-xorg

  I have two PCI Express nVidia cards, a 7900GT with one LCD, and a
  6800GT with two CRTs. There's a bug in X config parser that prevents
  it from using the second CRT. I'm using Edgy, but this has been broken
  since XFree86.

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

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


[Desktop-packages] [Bug 1768078] Re: gnome-control-center network panel missing DNS search

2018-06-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-control-center network panel missing DNS search

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

Bug description:
  The Unity network panel offered a means to set DNS search data on
  fixed IP connections maintained via NetworkManager in
  /etc/NetworkManager/system-coonections/ dns-search variable.

  This feature is absent in 18.04 Gnome's gnome-control-center network
  panel.

  Lack of the feature means the dns-search variable is unset which also
  causes /etc/resolv.conf to leave the search to be unset. This is
  unacceptable in a assigned IP address Enterprise environment.

  One workaround is to manually edit the NetworkManager system-
  connections file after its creation to set the variable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon Apr 30 12:36:30 2018
  InstallationDate: Installed on 2018-04-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1776534] Re: Input devices stop working after logout or switch-user

2018-06-12 Thread Ananth P
** Package changed: ubuntu => gdm3 (Ubuntu)

** Description changed:

  laptop: HP G42
  Ubuntu: 18.04 LTS
  
  After clicking logout or switch user, once the system reaches the
  greeter/login screen, input devices -- keyboard, mouse, touchpad -- stop
  working, making it impossible to login back or shutdown.
  
  Initially I thought the system is frozen, but log shows that it still
- respnds to lid open/close, usb plug/unplug events, scheduled background
+ responds to lid open/close, usb plug/unplug events, scheduled background
  tasks etc. Only the input devices, both onboard and external, are not
  usable. There's an external monitor attached to the laptop, and it shows
  the greeter and changes when lid is open or closed.
  
  What works:
  
  * logging in during fresh boot. Keyboard and mouse work at the greeter.
  * suspend/resume, lock/unlock screen. I'm able to enter password and get back 
to my session.
  * shutdown/restart while logged in.
  
  What doesn't work:
  
  * logout
  * switch user
  
  17.10 and other previous versions of ubuntu didn't have this issue on
  the same machine.
+ 
+ Workaround: restart gdm3 from a remote client.

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

Title:
  Input devices stop working after logout or switch-user

Status in gdm3 package in Ubuntu:
  New

Bug description:
  laptop: HP G42
  Ubuntu: 18.04 LTS

  After clicking logout or switch user, once the system reaches the
  greeter/login screen, input devices -- keyboard, mouse, touchpad --
  stop working, making it impossible to login back or shutdown.

  Initially I thought the system is frozen, but log shows that it still
  responds to lid open/close, usb plug/unplug events, scheduled
  background tasks etc. Only the input devices, both onboard and
  external, are not usable. There's an external monitor attached to the
  laptop, and it shows the greeter and changes when lid is open or
  closed.

  What works:

  * logging in during fresh boot. Keyboard and mouse work at the greeter.
  * suspend/resume, lock/unlock screen. I'm able to enter password and get back 
to my session.
  * shutdown/restart while logged in.

  What doesn't work:

  * logout
  * switch user

  17.10 and other previous versions of ubuntu didn't have this issue on
  the same machine.

  Workaround: restart gdm3 from a remote client.

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

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


[Desktop-packages] [Bug 1776534] [NEW] Input devices stop working after logout or switch-user

2018-06-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

laptop: HP G42
Ubuntu: 18.04 LTS

After clicking logout or switch user, once the system reaches the
greeter/login screen, input devices -- keyboard, mouse, touchpad -- stop
working, making it impossible to login back or shutdown.

Initially I thought the system is frozen, but log shows that it still
respnds to lid open/close, usb plug/unplug events, scheduled background
tasks etc. Only the input devices, both onboard and external, are not
usable. There's an external monitor attached to the laptop, and it shows
the greeter and changes when lid is open or closed.

What works:

* logging in during fresh boot. Keyboard and mouse work at the greeter.
* suspend/resume, lock/unlock screen. I'm able to enter password and get back 
to my session.
* shutdown/restart while logged in.

What doesn't work:

* logout
* switch user

17.10 and other previous versions of ubuntu didn't have this issue on
the same machine.

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


** Tags: 18.04
-- 
Input devices stop working after logout or switch-user
https://bugs.launchpad.net/bugs/1776534
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 in Ubuntu.

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


[Desktop-packages] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2

2018-06-12 Thread Andreas Hasenack
Upstream bug https://gitlab.freedesktop.org/spice/spice-gtk/issues/66
was closed, but if I understood it correctly, only for 18.04. Is this
still an issue for 16.04, and does the patch from comment #5 help there?

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

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  Unknown
Status in qemu package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1776515] [NEW] /usr/lib/gvfs/gvfsd-smb-browse:6:talloc_abort:talloc_abort_unknown_value:talloc_chunk_from_ptr:_talloc_free:internal_resolve_name

2018-06-12 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: artful bionic kylin-14.10 kylin-15.04 trusty utopic vivid wily xenial 
yakkety zesty

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

Title:
  /usr/lib/gvfs/gvfsd-smb-
  
browse:6:talloc_abort:talloc_abort_unknown_value:talloc_chunk_from_ptr:_talloc_free:internal_resolve_name

Status in gvfs package in Ubuntu:
  New

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

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

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


  1   2   >