[Desktop-packages] [Bug 2061245] Re: Ubuntu 24.04 - GNOME on Xorg session crashes on launch

[Rich McAllister]

I'm having the same xorg crash problem on Xubuntu 24.04 beta, see
#2061246 (dup'ed to here.)  I can reproduce the problem with a Ubuntu
24.04 beta install, but there xorg always crashes, unlike the
Xubuntu/xfce4 flavor where the first login after booting fails but
trying again immediately will succeed.

There's some crash info left in Xorg.0.log, I'll attach it.


** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061245/+attachment/5764900/+files/Xorg.0.log

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

Title:
  Ubuntu 24.04 - GNOME on Xorg session crashes on launch

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded an existing 23.10 installation to 24.04 LTS development 
branch/beta.
  Whereas GNOME on Xorg worked fine on 23.10, upon completed upgrade/reboot my 
system defaulted to GNOME on Wayland*.
  Attempting to login under Xorg caused the system to freeze and subsequently 
prompted me to login again. I cannot launch GNOME on 24.04 using Xorg, only 
Wayland.
  Upon deleting "20-nvidia.conf", located at "/etc/X11/xorg.conf.d/", 
attempting to launch an Xorg/X11 session greeted me with a black screen, and I 
was subsequently returned to login a few seconds later.

  (*The Wayland session, while functional, contained a lot of tearing,
  stuttering, and a lack of animations.)

  Ubuntu 24.04 LTS Dev.
  DE: GNOME
  Graphics driver: Nvidia 535

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 14:58:57 2024
  DistUpgraded: 2024-04-13 14:14:00,343 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1ec7] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:13aa]
  InstallationDate: Installed on 2023-12-15 (121 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B17
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=d1172f3e-66ff-4508-a818-d3f88ec03bdb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/26/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING EDGE AC (MS-7B17)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd03/26/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B17:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGEDGEAC(MS-7B17):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7B17
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2039722] Re: "Large Text" accessibility option cannot be turned off. Text is too large

[Rich McAllister]

I can reproduce this with Ubuntu 23.10.1.  It is necessary to select
large text while running the installer (I did use the new installer.)
The key difference is on a host installed without selecting large text
in the installer, "gsettings get org.gnome.desktop.interface text-
scaling-factor" will reset the factor to 1.0.  On a host installed
*with* selecting large text in the installer, it will reset the factor
to 1.25. Presumably the installer is somehow setting the default value
in the installed image, but I don't know how to check that. Also
presumably, the Accessablity menu implements "turn on large text" to
mean "set text-scaling-factor 1.25" and "turn off large text" to mean
"reset text-scaling-factor".  So once the default value is set to 1.25,
turning  off is effectively a no-op.  I do not know whether the bug here
is in the installer -- that it shouldn't push the install value into the
defaults of the image -- or in the accessibility dialog, which maybe
should implement "turn off large text" as "set text-scaling-factor 1.0".

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

Title:
  "Large Text" accessibility option cannot be turned off. Text is too
  large

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

Bug description:
  SUMMARY

  There is a little "accessibility" menu in the top right of my screen.
  If I click it, there is a switch saying "Large Text". It is enabled.
  If I click it to turn it off, it switches off, but nothing changes. If
  I then log out and back in, then click the accessibility menu, I find
  "Large Text" has been switched back on.

  If in the "accessibility" menu I click "Accessibility Settings", it
  brings up a pane in the Settings app ("org.gnome.Settings.desktop"?).
  If I then click "Seeing", I see several settings, one of which is
  "Large Text". If I turn off "Large Text" here, it switches off, but
  nothing changes. If I then close Settings and choose "Accessibility
  Settings" then "Seeing" again, I find "Large Text" has been switched
  back on.

  Additionally, all the text on my screen is too large. It is making it
  hard to use the computer.

  NOTE: I would appreciate a rapid response in terms of "what
  information do you need me to gather to ensure the bug can be
  diagnosed properly". I have not fully debugged yet (I have not messed
  with gsettings, etc) because I don't want to destroy the bug state
  before gathering the appropriate diagnostics.

  CONTEXT / DETAILED EXPLANATION

  I have a hunch the Ubuntu installer is partially to blame, so I'm
  going to describe the events leading up to the problem.

  Yesterday I got a new ThinkPad. This ThinkPad is "1.5x retina". That
  means it is 1080p (1920x1200 to be exact) in a laptop form factor and
  in order for things to look "normal size" it must display at 150%. The
  copy of Windows on the laptop was configured for 150% display scale
  for example. I took the ThinkPad out of the box and immediately wiped
  the Windows partition and installed 22.04 LTS from a USB stick. This
  worked but I had difficulty because the installer was running at 1x
  and so all the text was very small. My eyesight is not very good and I
  can read regular computer text but anything smaller than regular I
  have trouble. Once I got into the OS though I could set the display
  scale to 150% using Displays->Fractional Scale + Scale. Then
  everything looked good. I was happy. I did notice the Login screen had
  very small text though.

  My 22.04 LTS worked well but a friend told me it's better to use
  regular updates rather than LTS, so I wiped my 22.04 LTS partition and
  installed 23.10.1 from a USB stick. This time I noticed something in
  the installer. The installer had an accessibility menu (little T pose
  man icon) and one of the options was "Large Text". Perfect! I clicked
  "Large Text" and my complaint about the text being too small to read
  in the installer was fixed. I installed 23.10 and booted. When I got
  to the login screen on first boot I noticed the accessibility menu
  again so I selected "Large Text" so the text on the login screen would
  not be so small. Then I logged in. I immediately set my display scale
  to 150% as before.

  Inside 23.10, I quickly noticed that all the text was larger than I
  expected. Web pages that fit on my screen before did not anymore. A
  specific thing I noticed was the Mouse & Keyboard screen, the titlebar
  tabs were crowded where they had not been in 22.04 (see screenshot).
  It was then I noticed the anamolous, forced-on "Large Text" in the
  accessibility menu.

  Remembering that I had set "Large Text" in the login screen, I tried
  logging out, turning off login screen "Large Text" and logging back
  in. The login screen "Large Text" is remembered correctly and on re-
  entering login large text remains off. But it did

Re: [Desktop-packages] [Bug 514973] Re: [Rhythmbox] Don't play Audiobooks in shuffle mode

[Rich Jones]

The answer is ID3 tags though.

On Mon, Feb 6, 2023, 16:26 Paul White <514...@bugs.launchpad.net> wrote:

> Upstream issue was closed 2020/11/15 as no-one was able to
> provide an answer to "How would any application be able to
> "identify" audiobook files programmatically?
>
> I'm closing this bug report as "Invalid" as this is a GNOME
> issue for which they have provided an explanation as to why
> this issue will not be fixed.
>
> ** Changed in: hundredpapercuts
>Status: New => Invalid
>
> ** Changed in: rhythmbox (Ubuntu)
>Status: Triaged => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/514973
>
> Title:
>   [Rhythmbox] Don't play Audiobooks in shuffle mode
>
> Status in One Hundred Papercuts:
>   Invalid
> Status in Rhythmbox:
>   Expired
> Status in rhythmbox package in Ubuntu:
>   Invalid
>
> Bug description:
>   This happens all the time, I'm away from the computer listening to music
> in
>   shuffle mode, and a chapter of an audiobook starts playing. I have stop
> what
>   I'm doing and change it.
>
>   Why would anybody ever want to randomly listen to a random chapter of
>   a book?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hundredpapercuts/+bug/514973/+subscriptions
>
>

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

Title:
  [Rhythmbox] Don't play Audiobooks in shuffle mode

Status in One Hundred Papercuts:
  Invalid
Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  This happens all the time, I'm away from the computer listening to music in
  shuffle mode, and a chapter of an audiobook starts playing. I have stop what
  I'm doing and change it.

  Why would anybody ever want to randomly listen to a random chapter of
  a book?

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


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

[Desktop-packages] [Bug 1767431] Re: restore type-ahead find, again

[Rich Smith]

This is really annoying, counter-intuitive behaviour. At the very least
the old behaviour should be restorable by a setting.

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

Title:
  restore type-ahead find, again

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The dropping of the type-ahead find patch in 17.10 might deeply affect
  non-technical users, as pointed out, this is possibly a bad HCI
  design. As there is a patch exists from the Arch community[1], and the
  at least some people managed to patch it in 17.10[2], might it be
  possible to add such patch back before 18.04.1 so that it won't affect
  people upgraded from 16.04?

  [1]: https://aur.archlinux.org/nautilus-typeahead.git
  [2]: https://askubuntu.com/a/1002521

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

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

[Desktop-packages] [Bug 1869632] Re: AppArmor profile denied access to /etc/mdns.allow

[Rich McAllister]

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

** This bug has been marked a duplicate of bug 1869629
   please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Many messages in syslog

  audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
  operation="open" profile="/usr/sbin/cups-browsed"
  name="/etc/mdns.allow" pid=1323 comm="cups-browsed" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  This is caused by configuring libnss-mdns to resolve local names, with
  /etc/nsswitch.conf containing

  hosts:  files mdns [NOTFOUND=return] dns myhostname

  libnss-mnds reads /etc/mdns.allow to find which domains to resolve,
  but /etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.11-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Sun Mar 29 15:48:11 2020
  InstallationDate: Installed on 2019-10-24 (157 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1869632] Re: AppArmor profile denied access to /etc/mdns.allow

[Rich McAllister]

Bug also exists in package version 1.27.3-1 (current version in focal)

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Many messages in syslog

  audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
  operation="open" profile="/usr/sbin/cups-browsed"
  name="/etc/mdns.allow" pid=1323 comm="cups-browsed" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  This is caused by configuring libnss-mdns to resolve local names, with
  /etc/nsswitch.conf containing

  hosts:  files mdns [NOTFOUND=return] dns myhostname

  libnss-mnds reads /etc/mdns.allow to find which domains to resolve,
  but /etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.11-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Sun Mar 29 15:48:11 2020
  InstallationDate: Installed on 2019-10-24 (157 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1869632] [NEW] AppArmor profile denied access to /etc/mdns.allow

[Rich McAllister]

Public bug reported:

Many messages in syslog

audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
operation="open" profile="/usr/sbin/cups-browsed" name="/etc/mdns.allow"
pid=1323 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0
ouid=0

This is caused by configuring libnss-mdns to resolve local names, with
/etc/nsswitch.conf containing

hosts:  files mdns [NOTFOUND=return] dns myhostname

libnss-mnds reads /etc/mdns.allow to find which domains to resolve, but
/etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups-browsed 1.25.11-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CupsErrorLog:
 
CurrentDesktop: XFCE
Date: Sun Mar 29 15:48:11 2020
InstallationDate: Installed on 2019-10-24 (157 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
SourcePackage: cups-filters
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug eoan

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

Title:
  AppArmor profile denied access to /etc/mdns.allow

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Many messages in syslog

  audit: type=1400 audit(1585521672.468:40): apparmor="DENIED"
  operation="open" profile="/usr/sbin/cups-browsed"
  name="/etc/mdns.allow" pid=1323 comm="cups-browsed" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  This is caused by configuring libnss-mdns to resolve local names, with
  /etc/nsswitch.conf containing

  hosts:  files mdns [NOTFOUND=return] dns myhostname

  libnss-mnds reads /etc/mdns.allow to find which domains to resolve,
  but /etc/apparmor.d/usr.sbin.cups-browsed does not allow access.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.11-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Sun Mar 29 15:48:11 2020
  InstallationDate: Installed on 2019-10-24 (157 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic 
root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1867971] [NEW] gsettings dependency is problematic

[Rich Morin]

Public bug reported:

A current discussion on orca-list indicates that some blind users are
finding Orca's use of gsettings to be problematic:

The most accessible Linux version to use with Orca?
https://mail.gnome.org/archives/orca-list/2020-March/msg00233.html

Here are some relevant snippets:

> ubuntu certainly fails here, the developers locked down orca
configuration attaching it to gsettings and making it impossible to
configure inside orca.

> You can't modify orca configuration settings in ubuntu-mate and save
those modifications.  You have to use gsettings to get at orca
configuration and change them so they're saved.  Garden variety ubuntu
in 19.10 does the same thing.  In earlier versions of ubuntu this was
not the case, you could make your changes inside orca and save those
changes.

> You never heard of gsettings before since using it is about as complex
as editing a windows registry.  The gsettings along with dconf-editor
controls the configuration on graphical user interface systems other
configuration files you might find in certain directories does not.  In
the case of ubuntu 19.10 orca got strait jacketed into gsettings.  This
was not the case in earlier ubuntu versions though.

> I tried installing ubuntu 19.10 a few minutes ago the desktop version
since I couldn't get a download url for ubuntu-mate.org and couldn't
even bring up orca and this was after I verified the download.  That
cured me of ubuntu I'm pretty sure permanently.  running alt-super-s
didn't work and alt-f2 orca also failed and even alt-f2 screen-reader
failed as well.  I waited until all disk action had stopped to run those
commands too.

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

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

Title:
  gsettings dependency is problematic

Status in orca package in Ubuntu:
  New

Bug description:
  A current discussion on orca-list indicates that some blind users are
  finding Orca's use of gsettings to be problematic:

  The most accessible Linux version to use with Orca?
  https://mail.gnome.org/archives/orca-list/2020-March/msg00233.html

  Here are some relevant snippets:

  > ubuntu certainly fails here, the developers locked down orca
  configuration attaching it to gsettings and making it impossible to
  configure inside orca.

  > You can't modify orca configuration settings in ubuntu-mate and save
  those modifications.  You have to use gsettings to get at orca
  configuration and change them so they're saved.  Garden variety ubuntu
  in 19.10 does the same thing.  In earlier versions of ubuntu this was
  not the case, you could make your changes inside orca and save those
  changes.

  > You never heard of gsettings before since using it is about as complex
  as editing a windows registry.  The gsettings along with dconf-editor
  controls the configuration on graphical user interface systems other
  configuration files you might find in certain directories does not.  In
  the case of ubuntu 19.10 orca got strait jacketed into gsettings.  This
  was not the case in earlier ubuntu versions though.

  > I tried installing ubuntu 19.10 a few minutes ago the desktop version
  since I couldn't get a download url for ubuntu-mate.org and couldn't
  even bring up orca and this was after I verified the download.  That
  cured me of ubuntu I'm pretty sure permanently.  running alt-super-s
  didn't work and alt-f2 orca also failed and even alt-f2 screen-reader
  failed as well.  I waited until all disk action had stopped to run those
  commands too.

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

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

Re: [Desktop-packages] [Bug 1855477] Re: gnome-control-center will not let me paste in a password from my password manger

[Rich Hart]

I'm using Xorg.  And the password manager is xkeepass ( and keepass2 )

On 12/9/19 11:49 AM, Jamie Strandboge wrote:
> Thank you for using Ubuntu and reporting a bug.
>
> Are you using wayland or Xorg for your desktop session? What password
> manager are you using?
>
> ** Information type changed from Private Security to Public Security
>

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

Title:
  gnome-control-center will not let me paste in a password from my
  password manger

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

Bug description:
  Gnome-control-center online-accounts will not let me paste my google
  password in.Since I use long secure complex passwords, typing in
  passwords is not a viable option.   Please fix this bug.

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

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

[Desktop-packages] [Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on

[Rich Wales]

I don't think Compiz is relevant here.  My computer isn't running Compiz
— its display manager is GDM3 as best I can tell.  (ri...@richw.org, the
original reporter of this bug)

** Package changed: compiz (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Windows move to different monitor when multiple monitors turned off
  and back on

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10, gdm3 3.34.1-1ubuntu1, cinnamon 4.0.10-2, cinnamon-
  screensaver 4.0.3-1, nvidia-driver 435.21-0ubuntu2.

  I have a TV set connected to my computer as a second monitor (for
  displaying YouTube videos, etc.).

  When I turn off both my main monitor and the TV for the night, and
  turn them back on in the morning, I often find that the windows I had
  left open on the main monitor (email, browser, xterm, etc.) have moved
  from the main monitor to the TV and need to be moved back individually
  to the main monitor (via the "move to the other monitor" function on
  the taskbar icons).

  This doesn't always happen -- sometimes the windows show up on the
  main monitor where I left them the night before, and sometimes not.
  Maybe 50-50, one way or the other.

  The main monitor is configured (in the Display settings) as the
  primary monitor, and the taskbar panel remains on the main monitor --
  and when I wake up the screen saver to unlock it, the password
  dialogue always shows up on the main monitor -- but the windows may
  end up on either device after I've unlocked.

  It doesn't appear to make any difference what order I turn the monitor
  and the TV off/on.  In particular, I've conscientiously turned off the
  TV before locking the screen and turning off the monitor, and then
  turned on the monitor and unlocked the screen before turning the TV
  back on, but the windows frequently still end up on the TV instead of
  the main monitor.

  I would like to somehow flag the windows so that they will stay put on
  my main monitor when I turn things off at night and turn them back on
  in the morning -- or, even better, I would like the windows to remain
  associated with the same device and not move around on their own.

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

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

[Desktop-packages] [Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

As I wrote earlier, the EDID file I used came from edid-generator github
and it is called 1920x1080.bin . You want me to google that for you?

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

Title:
  drm fails to accept edid version 2.4

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: x

[Desktop-packages] [Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

I'm not sure this is a Linux problem. It may be that the panel is
reporting bad EDID data. I haven't investigated enough to say for sure.
In any case none of the more recent Linux releases fixed the problem in
my tests. Also no other open source OSs were able to deal with the
onboard LCD panel either. (That may have changed since I tested.)

If you were interested, you might be able to patch the firmware on the
onboard panel to provide different EDID information. I looked into doing
this and there are some tutorials out there. However, it's possible you
could do something wrong and end up worse than you were before. If you
learn something new, please post it here. In particular if you find some
open source OS that can configure this display properly at full
resolution without resorting to forcing EDID information please say so
here.

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

Title:
  drm fails to accept edid version 2.4

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0

[Desktop-packages] [Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

I was able to display on an external monitor, or the internal monitor,
but not both simultaneously. I didn't spend too much time trying to
solve the problem and now the laptop is with a family member at another
location. If you work on this issue and find a solution please post it
here.

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

Title:
  drm fails to accept edid version 2.4

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-m

[Desktop-packages] [Bug 1821533] Re: drm fails to accept edid version 2.4

[Rich Drewes]

** Summary changed:

- failure to detect and use Intel 620 graphics pci id 3ea0
+ drm fails to accept edid version 2.4

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

Title:
  drm fails to accept edid version 2.4

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I was able to get the onboard LCD panel working, finally, as follows:

First I extracted the edid file from the LCD panel using get-edid and
putting that in /lib/firmware/edid/ncp.bin, and then forcing the kernel
to take that using the kernel boot option
drm.edid_firmware=edid/ncp.bin. This failed, and dmesg said that the
ncp.bin file had a "bad block 0". Possibly that means that nothing
within Linux can accept edid version 2.4?

Then I grabbed a generic 1920x1080.bin edid file from edid-generator
github and put that one in /lib/firmware/edid/ and used that one with
drm.edid_firmware and the display worked for the first time!

I am still unsure why Linux couldn't accept the version 2.4 edid data
from the LCD panel.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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 COMPUT

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Below is the EDID information from the onboard panel. Why can't drm/i915
deal with it?


guest@guest-ZenBook-UX431FA:~$ sudo get-edid | parse-edid 
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
1 potential busses found: 5
128-byte EDID successfully retrieved from i2c bus 5
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
Identifier ""
ModelName ""
VendorName "NCP"
# Monitor Manufactured week 1 of 2018
# EDID version 2.4
# Digital Display
DisplaySize 310 170
Gamma 2.20
Option "DPMS" "false"
Modeline"Mode 0" 138.50 1920 1968 2000 2080 1080 1083 1088  
+hsync -vsync 
EndSection

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.boar

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I think the problem is that the laptop's onboard LCD panel is reporting
EDID data with version 2 and the i915 driver can only deal with version
1 at the moment. How can this be fixed?

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-m

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Correction: last message should read "Why is the driver/module expecting
EDID major version *1* and getting *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/1821533

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xo

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Progress! Based on information in dmesg, pasted in at the end of this
message, I thought maybe the graphics device was found OK but the laptop
was trying to drive an external monitor instead of the onboard display.
Sure enough, when I boot without nomodeset option and with an external
HDMI monitor attached the system does display to the external monitor
with proper 1920x1080 resolution.

What does the "EDID is invalid:" message mean? Why is the driver/module
expecting EDID major version 2 and getting 1? Does this have to do with
the version of kbl_dmc firmware loaded to the graphics device?


guest@guest-ZenBook-UX431FA:~$ dmesg | egrep  "drm|i915"
[3.196687] fb: switching to inteldrmfb from EFI VGA
[3.196881] [drm] Replacing VGA console driver
[3.210304] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.210306] [drm] Driver supports precise vblank timestamp query.
[3.212814] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[3.214857] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
[3.228865] [drm] EDID has major version 2, instead of 1
[3.236620] [drm] EDID has major version 2, instead of 1
[3.240878] [drm] EDID has major version 2, instead of 1
[3.244590] [drm] EDID has major version 2, instead of 1
[3.244595] i915 :00:02.0: eDP-1: EDID is invalid:
[3.244597] [drm] EDID has major version 2, instead of 1
[3.290049] [drm] Initialized i915 1.6.0 20180514 for :00:02.0 on minor 0
[3.326674] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[3.356268] fbcon: inteldrmfb (fb0) is primary device
[4.724973] i915 :00:02.0: fb0: inteldrmfb frame buffer device

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection se

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Is it known whether any machines with Intel Graphics 620 with pci id
0x3ea0 have functioning graphics with any version of Ubuntu?

This is relatively new hardware, but it seems unlikely that I am the
only one in the world who has tried this combination, and if other
people with different machines with the same 0x3ea0 pci id do have
working graphics then that would suggest that the problem is some quirk
of my particular ASUS UX431FA (perhaps some initialization timing quirk
or hardware/design bug that is worked-around for the Windows 10
installation that came with the system).

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBook

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I tried booting 4.18.0-16-generic (which i believe is the hwe kernel)
with kernel option drm.debug=0xff. When the system came up of course it
had no video but I could ssh in and grab the dmesg output, which is
attached to this message. dmesg had many drm-related debugging messages
and i915-related messages, but none of it was particularly helpful to me
yet.

** Attachment added: "dmesg-drm.debug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821533/+attachment/5249204/+files/dmesg-drm.debug.txt

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASU

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Just in case my addition of i915 to initramfs was causing a problem with
drm-intel-next, I removed i915 from initramfs and repeated the test. The
result was the same, no video after a certain point in the boot process
with nomodeset using the drm-intel-next kernel as in #8.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.l

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

I installed kernel and modules and headers from
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
and rebooted without nomodeset option. Same behavior: after the "loading
initramfs" message the screen blanks and never comes back.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-m

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Based on a lead from an Arch Linux blog post, I tried adding the i915
module to the initramfs. This could possibly lead to earlier
initialization of the graphics device and it also seems consistent with
the DragonFlyBSD "probe early" patch I linked to in my initial bug
report which may have fixed the graphics problem in DragonFlyBSD (I
cannot tell for certain if the graphics problem was fixed there due to
another, unrelated problem, but the fix definitely allowed the boot to
proceed further and the text did seem to switch to full screen
resolution).

The update-initramfs operation failed on the v5.1-rc2 kernel because of
two missing firmware files.

The update-initramfs operation succeeded on the 4.x kernels I had
installed, one of which is the hwe kernel (I believe). I verified the
presence of the i915 module in the initramfs for those kernels using
lsinitramfs. Unfortunately, booting with i915 in the initramfs on the
4.x kernels and without nomodeset did not solve the problem.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Also: booting without nomodeset kernel option for v5.1-rc2 kernel leads
to black screen, just as before. At that point the system cannot even be
switched to text console with ctrl-alt-Fn.

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libg

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Thanks for your help.

Unfortunately, no change after installing v5.1-rc2: Still stuck in
800x600 after booting with nomodeset kernel option.

Added kernel-bug-exists-upstream and marked confirmed.

dmesg output attached.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821533/+attachment/5249132/+files/dmesg

** Tags added: kernel-bug-exists-upstream

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

** Changed in: linux-hwe (Ubuntu)
   Status: New => Confirmed

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

Title:
  failure to detect and use Intel 620 graphics pci id 3ea0

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

Bug description:
  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware
  enablement packages does not solve problem: the system will still only
  boot with nomodeset kernel option, and X is limited to using fbdev
  module at 800x600 resolution.

  The "modesetting" driver appears to be loaded and then unloaded during
  X startup. Trying to force intel module from xserver-xorg-video-intel
  by setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does
  not help.

  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.

  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
  DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
  verified that the patch referenced in that bug report does make
  DragonFlyBSD boot past the video problem which I think is the same
  problem I experience with every Linux OS I have tried including
  Ubuntu.

  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver

  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:

[Desktop-packages] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

** Description changed:

  Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
  install (also 18.10, also 19.04 daily) leads to black screen. Adding
  "nomodeset" to kernel boot parameter gives 800x600 video only and
  permits installing OS to disk. Applying updates and hardware enablement
  packages does not solve problem: the system will still only boot with
  nomodeset kernel option, and X is limited to using fbdev module at
  800x600 resolution.
  
  The "modesetting" driver appears to be loaded and then unloaded during X
  startup. Trying to force intel module from xserver-xorg-video-intel by
  setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not
  help.
  
  The PCI id for the graphics device appears to be 3ea0 and the place
  where that might be relevant is the i915 module.
  
  This problem occurs with every other Linux release I have tried
  including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
  The one open source OS that I have found where it might be fixed is
- DragonFlyBSD (see bug report 3167 here
- https://bugs.dragonflybsd.org/issues/3167). I have verified that the
- patch referenced in that bug report does make DragonFlyBSD boot past the
- video problem which I think is the same problem I experience with every
- Linux OS I have tried including Ubuntu.
+ DragonFlyBSD (see https://bugs.dragonflybsd.org/issues/3167). I have
+ verified that the patch referenced in that bug report does make
+ DragonFlyBSD boot past the video problem which I think is the same
+ problem I experience with every Linux OS I have tried including Ubuntu.
  
  guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  
  guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
  ii  linux-generic-hwe-18.044.18.0.16.66   
  amd64Complete Generic Linux kernel and headers
  ii  linux-headers-generic-hwe-18.044.18.0.16.66   
  amd64Generic Linux kernel headers
  ii  linux-image-generic-hwe-18.04  4.18.0.16.66   
  amd64Generic Linux kernel image
  ii  linux-signed-generic-hwe-18.04 4.18.0.16.66   
  amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
  ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1   
  amd64X.Org X server -- fbdev display driver
  
  Expected result: Video at 1920x1080
  Actual result: Video limited to 800x600
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 10:36:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
+  Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
  InstallationDate: Installed on 2019-03-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX431FA.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX431FA
  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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX431FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  vers

[Desktop-packages] [Bug 1821533] [NEW] failure to detect and use Intel 620 graphics pci id 3ea0

[Rich Drewes]

Public bug reported:

Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware enablement
packages does not solve problem: the system will still only boot with
nomodeset kernel option, and X is limited to using fbdev module at
800x600 resolution.

The "modesetting" driver appears to be loaded and then unloaded during X
startup. Trying to force intel module from xserver-xorg-video-intel by
setting up 20-intel.conf file in /usr/share/X11/xorg.conf.d/ does not
help.

The PCI id for the graphics device appears to be 3ea0 and the place
where that might be relevant is the i915 module.

This problem occurs with every other Linux release I have tried
including Fedora 29, Elementary OS latest, Mint 19.1, Manjaro latest.
The one open source OS that I have found where it might be fixed is
DragonFlyBSD (see bug report 3167 here
https://bugs.dragonflybsd.org/issues/3167). I have verified that the
patch referenced in that bug report does make DragonFlyBSD boot past the
video problem which I think is the same problem I experience with every
Linux OS I have tried including Ubuntu.

guest@guest-ZenBook-UX431FA:~$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

guest@guest-ZenBook-UX431FA:~$ dpkg -l | grep hwe | egrep "linux|fbdev"
ii  linux-generic-hwe-18.044.18.0.16.66 
amd64Complete Generic Linux kernel and headers
ii  linux-headers-generic-hwe-18.044.18.0.16.66 
amd64Generic Linux kernel headers
ii  linux-image-generic-hwe-18.04  4.18.0.16.66 
amd64Generic Linux kernel image
ii  linux-signed-generic-hwe-18.04 4.18.0.16.66 
amd64Complete Signed Generic Linux kernel and headers 
(dummy transitional package)
ii  xserver-xorg-video-fbdev-hwe-18.04 1:0.5.0-1ubuntu1~18.04.1 
amd64X.Org X server -- fbdev display driver

Expected result: Video at 1920x1080
Actual result: Video limited to 800x600

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 24 10:36:51 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:17d1]
InstallationDate: Installed on 2019-03-24 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX431FA
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=e6ae272a-49f0-491b-99b6-2a3785a7679e ro nomodeset vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX431FA.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX431FA
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.:bvrUX431FA.205:bd12/14/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX431FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic resolution ubuntu

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

Title:
  failure to detect and use Inte

[Desktop-packages] [Bug 1817308] Re: GhostScript Update causes Blue Background

[Rich]

Update Manager came through with the update a couple of hours ago -
Fixed the blue background on HP Photosmart B210. Thanks for quick work
Guys

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

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

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

[Desktop-packages] [Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

I filed a bug report with GNOME:

https://bugzilla.gnome.org/show_bug.cgi?id=792832

I added the link to:

Also affects project.

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

** Also affects: gedit via
   https://bugzilla.gnome.org/show_bug.cgi?id=792832
   Importance: Unknown
   Status: Unknown

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit:
  Unknown
Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing until the behaviour is "interrupted" by
  a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editors under multiple Linux variants - but
  Gedit is my favourite text editor and Ubuntu is my favourite Linux so
  I thought I would start here.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ apt-cache policy gedit
  gedit:
    Installed: 3.18.3-0ubuntu4
    Candidate: 3.18.3-0ubuntu4
    Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
    Installed: 1.2.0-2
    Candidate: 1.2.0-2
    Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

** Description changed:

  If I paste a special character - say from the Character Map - into Gedit
  or medit in Ubuntu 16.04 into the middle of a line, then the space
  characters directly after the special character display with a
- "compressed" character spacing/display until the behaviour is
- "interrupted" by a standard text character.
+ "compressed" character spacing until the behaviour is "interrupted" by a
+ standard text character.
  
  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines with
  the special character problem.
  
  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .
  
  https://askubuntu.com/questions/986258/why-do-special-characters-change-
  spacing-following-space-character-in-gedit-or-m
  
  Please see that post for full details, worked example, and screenshots.
  
  Additional comments:
  
  * As stated above:
  - running Ubuntu 16.04
  
  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0
  
  I am aware that it is thus not strictly a gedit issue, and probably
- affects multiple Gnome editor under multiple Linux variants but Gedit is
- my favourite text editor and Ubuntu is my favourite Linux so I thought I
- would start here.
+ affects multiple Gnome editors under multiple Linux variants - but Gedit
+ is my favourite text editor and Ubuntu is my favourite Linux so I
+ thought I would start here.
  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  
  $ apt-cache policy gedit
  gedit:
-   Installed: 3.18.3-0ubuntu4
-   Candidate: 3.18.3-0ubuntu4
-   Version table:
-  *** 3.18.3-0ubuntu4 500
- 500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.18.3-0ubuntu4
+   Candidate: 3.18.3-0ubuntu4
+   Version table:
+  *** 3.18.3-0ubuntu4 500
+ 500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  $ apt-cache policy medit
  medit:
-   Installed: 1.2.0-2
-   Candidate: 1.2.0-2
-   Version table:
-  *** 1.2.0-2 500
- 500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.2.0-2
+   Candidate: 1.2.0-2
+   Version table:
+  *** 1.2.0-2 500
+ 500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing until the behaviour is "interrupted" by
  a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editors under multiple Linux variants - but
  Gedit is my favourite text editor and Ubuntu is my favourite Linux so
  I thought I would start here.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ apt-cache policy gedit
  gedit:
    Installed: 3.18.3-0ubuntu4
    Candidate: 3.18.3-0ubuntu4
    Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
    Installed: 1.2.0-2
    Candidate: 1.2.0-2
    Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

** Tags added: ui

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing until the behaviour is "interrupted" by
  a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editors under multiple Linux variants - but
  Gedit is my favourite text editor and Ubuntu is my favourite Linux so
  I thought I would start here.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ apt-cache policy gedit
  gedit:
    Installed: 3.18.3-0ubuntu4
    Candidate: 3.18.3-0ubuntu4
    Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
    Installed: 1.2.0-2
    Candidate: 1.2.0-2
    Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1744946] [NEW] Special characters change the width of trailing/leading space character in Gedit (and medit)

[Tao Rich]

Public bug reported:

If I paste a special character - say from the Character Map - into Gedit
or medit in Ubuntu 16.04 into the middle of a line, then the space
characters directly after the special character display with a
"compressed" character spacing/display until the behaviour is
"interrupted" by a standard text character.

So the basic problem result is that the uniform monospacing of
characters gets out of alignment on lines above and below the lines with
the special character problem.

I posted a detailed question on AskUbuntu and the prevailing opinion was that I 
should log a bug report.
Another user with different versions was easily able to reproduce the same 
issue .

https://askubuntu.com/questions/986258/why-do-special-characters-change-
spacing-following-space-character-in-gedit-or-m

Please see that post for full details, worked example, and screenshots.

Additional comments:

* As stated above:
- running Ubuntu 16.04

* This affects:
- Gedit 3.18.3
- medit 1.2.0

I am aware that it is thus not strictly a gedit issue, and probably
affects multiple Gnome editor under multiple Linux variants but Gedit is
my favourite text editor and Ubuntu is my favourite Linux so I thought I
would start here.

$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

$ apt-cache policy gedit
gedit:
  Installed: 3.18.3-0ubuntu4
  Candidate: 3.18.3-0ubuntu4
  Version table:
 *** 3.18.3-0ubuntu4 500
500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy medit
medit:
  Installed: 1.2.0-2
  Candidate: 1.2.0-2
  Version table:
 *** 1.2.0-2 500
500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing/display until the behaviour is
  "interrupted" by a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editor under multiple Linux variants but Gedit
  is my favourite text editor and Ubuntu is my favourite Linux so I
  thought I would start here.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ apt-cache policy gedit
  gedit:
Installed: 3.18.3-0ubuntu4
Candidate: 3.18.3-0ubuntu4
Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
Installed: 1.2.0-2
Candidate: 1.2.0-2
Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1739878] [NEW] package network-manager-config-connectivity-hostname 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit

[Rich Perry]

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

Public bug reported:

I am using a Hyper-V virtual machine on Windows 10 Pro (1709 build
16299.125), and have received the error in the summary following the
first update after install.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Dec 23 21:40:50 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-12-23 (0 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
IpRoute:
 default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.163 metric 100 
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.163 
 192.168.1.1 dev eth0 proto dhcp scope link src 192.168.1.163 metric 100
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
PackageArchitecture: all
PciNetwork:
 
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
RfKill:
 
SourcePackage: network-manager
Title: package network-manager-config-connectivity-hostname 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 eth0ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-hostname 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am using a Hyper-V virtual machine on Windows 10 Pro (1709 build
  16299.125), and have received the error in the summary following the
  first update after install.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Dec 23 21:40:50 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-12-23 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.163 metric 100 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.163 
   192.168.1.1 dev eth0 proto dhcp scope link src 192.168.1.163 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  PackageArchitecture: all
  PciNetwork:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-hostname 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIOR

Re: [Desktop-packages] [Bug 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages

[Rich Jones]

:-O!

It only took eight years, but we did it folks!

Hooray!
R

On Tue, Dec 5, 2017 at 10:23 AM, Jeremy Bicha  wrote:

> This is finally "fixed" in Ubuntu 18.04 Alpha by having gnome-user-share
> depend on the packages it needs. The depends are not a fully functional
> Apache install but just an Apache binary and a WebDav server.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (645391).
> https://bugs.launchpad.net/bugs/536766
>
> Title:
>   Personal file sharing preferences dialog does not offer to install
>   needed packages
>
> Status in Ayatana Design:
>   Fix Committed
> Status in gnome-user-share package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Binary package hint: nautilus
>
>   What happens -> I open the Personal file sharing preferences dialog via
> system-preferences or via nautilus, and Im told that the network sharing
> feature can not be enabled because the required packages are not on your pc.
>   I, as a tech user, went to synaptic, found the package, looked for its
> recommends and got the functionality.
>   A normal user wont be able to do so, and so a button to install those
> packages is needed for usabilty's sake.
>
>   --
>
>   Desired resolution:
>
>   - Change the "Sharing Options" text in them Nautilus right click folder
> menu to "Local network share"
>   - Change the 'Share' tab title text in the Nautilus 'Properties' window
> to "Local network share"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions
>

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

Title:
  Personal file sharing preferences dialog does not offer to install
  needed packages

Status in Ayatana Design:
  Fix Committed
Status in gnome-user-share package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  What happens -> I open the Personal file sharing preferences dialog via 
system-preferences or via nautilus, and Im told that the network sharing 
feature can not be enabled because the required packages are not on your pc.
  I, as a tech user, went to synaptic, found the package, looked for its 
recommends and got the functionality.
  A normal user wont be able to do so, and so a button to install those 
packages is needed for usabilty's sake.

  --

  Desired resolution:

  - Change the "Sharing Options" text in them Nautilus right click folder menu 
to "Local network share"
  - Change the 'Share' tab title text in the Nautilus 'Properties' window to 
"Local network share"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions

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

[Desktop-packages] [Bug 1622880] Re: nautilus crashes on Ubuntu 16.10

[Mark Rich]

Using the command in step 5 resolved it for me too.

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

Title:
  nautilus crashes on Ubuntu 16.10

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus crashes on Ubuntu 16.10

  nautilus

  (nautilus:16009): Gtk-WARNING **: Theme parsing error: :1:0: 
Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' 
does not exist
  Nautilus-Share-Message: Called "net usershare info" but it failed: Failed to 
execute child process "net" (No such file or directory)
  **
  ERROR:nautilus-canvas-container.c:6021:finish_adding_new_icons: assertion 
failed: (!container->details->auto_layout)
  Aborted (core dumped)

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

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

[Desktop-packages] [Bug 1622467] [NEW] Segmentation fault (core dumped) while try create folder from select files

[rich]

Public bug reported:

ERROR:nautilus-view.c:1834:rename_newly_added_folder: code should not be
reached

gdb nautilus:
...
[New Thread 0x9e67cb40 (LWP 14410)]
**
ERROR:nautilus-view.c:1834:rename_newly_added_folder: code should not be reached

Thread 1 "nautilus" received signal SIGABRT, Aborted.
0xb7fdac31 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fdac31 in __kernel_vsyscall ()
#1  0xb6a99e89 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#2  0xb6a9b3e7 in __GI_abort () at abort.c:89
#3  0xb6d4b325 in g_assertion_message () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6d4b3ac in g_assertion_message_expr () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x080a5336 in ?? ()
#6  0xb60fde3a in ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
#7  0xb60fdaac in ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
#8  0xb6e1538d in g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#9  0xb6e14b6b in g_closure_invoke () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#10 0xb6e272b9 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#11 0xb6e2fc96 in g_signal_emit_valist () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#12 0xb6e2ffc5 in g_signal_emit () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#13 0x080a4a9e in ?? ()
#14 0xb6d25981 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#15 0xb6d24d8b in g_main_context_dispatch () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#16 0xb6d25179 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#17 0xb6d25244 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#18 0xb6f0df2b in g_application_run () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
#19 0x08068338 in ?? ()
#20 0xb6a86637 in __libc_start_main (main=0x8068260, argc=1, argv=0xb024, 
init=0x8131920, fini=0x8131980, rtld_fini=0xb7fea780 <_dl_fini>, 
stack_end=0xb01c)
at ../csu/libc-start.c:291
#21 0x080683a2 in ?? ()

also on the amd64 platform

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon Sep 12 10:11:15 2016
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'345'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1530x846+1779+212'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.desktop' b'font' b"'Ubuntu 11'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'where', 'owner', 'octal_permissions', 'group', 
'date_accessed', 'selinux_context', 'permissions', 'mime_type']"
InstallationDate: Installed on 2010-08-27 (2207 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
SourcePackage: nautilus
UpgradeStatus: Upgraded to xenial on 2016-04-15 (149 days ago)

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


** Tags: apport-bug i386 xenial

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

Title:
  Segmentation fault (core dumped) while try create folder from select
  files

Status in nautilus package in Ubuntu:
  New

Bug description:
  ERROR:nautilus-view.c:1834:rename_newly_added_folder: code should not
  be reached

  gdb nautilus:
  ...
  [New Thread 0x9e67cb40 (LWP 14410)]
  **
  ERROR:nautilus-view.c:1834:rename_newly_added_folder: code should not be 
reached

  Thread 1 "nautilus" received signal SIGABRT, Aborted.
  0xb7fdac31 in __kernel_vsyscall ()
  (gdb) bt
  #0  0xb7fdac31 in __kernel_vsyscall ()
  #1  0xb6a99e89 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54
  #2  0xb6a9b3e7 in __GI_abort () at abort.c:89
  #3  0xb6d4b325 in g_assertion_message () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #4  0xb6d4b3ac in g_assertion_message_expr () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0x080a5336 in ?? ()
  #6  0xb60fde3a in ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
  #7  0xb60fdaac in ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
  #8  0xb6e1538d in g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #9  0xb6e14b6b in g_closure_invoke () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #10 0xb6e272b9 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #11 0xb6e2fc96 in g_signal_emit_valist () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #12 0xb6e2ffc5 in g_signal_emit () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  #13 0x080a4a9e in ?? ()
  #14 0xb6d25981 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #15 0xb6d24d8b in g_main_context_dispatch () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #16 0xb6d25179 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #17 0xb6d25244 in g_main_c

[Desktop-packages] [Bug 1584884] Re: totem crush with Segmentation fault.

[rich]

Graphics: Gallium 0.4 on ATI RS480

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

Title:
  totem crush with Segmentation fault.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Run:
  >totem
  Segmentation fault (core dumped)
  >totem
  Segmentation fault (core dumped)

  run with gdb:

  >gdb totem
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from totem...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /usr/bin/totem 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffdb903700 (LWP 21787)]
  [New Thread 0x7fffdacbd700 (LWP 21788)]
  [New Thread 0x7fffda3b0700 (LWP 21790)]
  [New Thread 0x7fffd9baf700 (LWP 21791)]
  [New Thread 0x7fffcacfc700 (LWP 21808)]
  [New Thread 0x7fffca08a700 (LWP 21810)]
  [New Thread 0x7fffc295f700 (LWP 21826)]
  [New Thread 0x7fffc215e700 (LWP 21827)]
  [New Thread 0x7fffc0881700 (LWP 21828)]
  [New Thread 0x7fffb3b88700 (LWP 21829)]
  [New Thread 0x7fff9b6b7700 (LWP 21844)]
  [New Thread 0x7fff9aeb6700 (LWP 21845)]
  [New Thread 0x7fff997c0700 (LWP 21848)]
  [New Thread 0x7fff8bfff700 (LWP 21850)]

  Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
  0x7fffdc55c083 in LLVMBuildLoad () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
  (gdb) q

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May 23 19:59:00 2016
  InstallationDate: Installed on 2009-11-30 (2366 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to xenial on 2015-11-05 (200 days ago)

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

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

[Desktop-packages] [Bug 1584884] Re: totem crush with Segmentation fault.

[rich]

You need this or something more?

** Attachment added: "msg"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1584884/+attachment/4670828/+files/msg

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

Title:
  totem crush with Segmentation fault.

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Run:
  >totem
  Segmentation fault (core dumped)
  >totem
  Segmentation fault (core dumped)

  run with gdb:

  >gdb totem
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from totem...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /usr/bin/totem 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffdb903700 (LWP 21787)]
  [New Thread 0x7fffdacbd700 (LWP 21788)]
  [New Thread 0x7fffda3b0700 (LWP 21790)]
  [New Thread 0x7fffd9baf700 (LWP 21791)]
  [New Thread 0x7fffcacfc700 (LWP 21808)]
  [New Thread 0x7fffca08a700 (LWP 21810)]
  [New Thread 0x7fffc295f700 (LWP 21826)]
  [New Thread 0x7fffc215e700 (LWP 21827)]
  [New Thread 0x7fffc0881700 (LWP 21828)]
  [New Thread 0x7fffb3b88700 (LWP 21829)]
  [New Thread 0x7fff9b6b7700 (LWP 21844)]
  [New Thread 0x7fff9aeb6700 (LWP 21845)]
  [New Thread 0x7fff997c0700 (LWP 21848)]
  [New Thread 0x7fff8bfff700 (LWP 21850)]

  Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
  0x7fffdc55c083 in LLVMBuildLoad () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
  (gdb) q

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May 23 19:59:00 2016
  InstallationDate: Installed on 2009-11-30 (2366 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to xenial on 2015-11-05 (200 days ago)

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

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

[Desktop-packages] [Bug 1584884] [NEW] totem crush with Segmentation fault.

[rich]

Public bug reported:

Run:
>totem
Segmentation fault (core dumped)
>totem
Segmentation fault (core dumped)

run with gdb:

>gdb totem
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from totem...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/totem 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdb903700 (LWP 21787)]
[New Thread 0x7fffdacbd700 (LWP 21788)]
[New Thread 0x7fffda3b0700 (LWP 21790)]
[New Thread 0x7fffd9baf700 (LWP 21791)]
[New Thread 0x7fffcacfc700 (LWP 21808)]
[New Thread 0x7fffca08a700 (LWP 21810)]
[New Thread 0x7fffc295f700 (LWP 21826)]
[New Thread 0x7fffc215e700 (LWP 21827)]
[New Thread 0x7fffc0881700 (LWP 21828)]
[New Thread 0x7fffb3b88700 (LWP 21829)]
[New Thread 0x7fff9b6b7700 (LWP 21844)]
[New Thread 0x7fff9aeb6700 (LWP 21845)]
[New Thread 0x7fff997c0700 (LWP 21848)]
[New Thread 0x7fff8bfff700 (LWP 21850)]

Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
0x7fffdc55c083 in LLVMBuildLoad () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
(gdb) q

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: totem 3.18.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon May 23 19:59:00 2016
InstallationDate: Installed on 2009-11-30 (2366 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
SourcePackage: totem
UpgradeStatus: Upgraded to xenial on 2015-11-05 (200 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  totem crush with Segmentation fault.

Status in totem package in Ubuntu:
  New

Bug description:
  Run:
  >totem
  Segmentation fault (core dumped)
  >totem
  Segmentation fault (core dumped)

  run with gdb:

  >gdb totem
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from totem...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /usr/bin/totem 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffdb903700 (LWP 21787)]
  [New Thread 0x7fffdacbd700 (LWP 21788)]
  [New Thread 0x7fffda3b0700 (LWP 21790)]
  [New Thread 0x7fffd9baf700 (LWP 21791)]
  [New Thread 0x7fffcacfc700 (LWP 21808)]
  [New Thread 0x7fffca08a700 (LWP 21810)]
  [New Thread 0x7fffc295f700 (LWP 21826)]
  [New Thread 0x7fffc215e700 (LWP 21827)]
  [New Thread 0x7fffc0881700 (LWP 21828)]
  [New Thread 0x7fffb3b88700 (LWP 21829)]
  [New Thread 0x7fff9b6b7700 (LWP 21844)]
  [New Thread 0x7fff9aeb6700 (LWP 21845)]
  [New Thread 0x7fff997c0700 (LWP 21848)]
  [New Thread 0x7fff8bfff700 (LWP 21850)]

  Thread 1 "totem" received signal SIGSEGV, Segmentation fault.
  0x7fffdc55c083 in LLVMBuildLoad () from 
/usr/lib/x86_64-linux-gnu/libLLVM-3.8.so.1
  (gdb) q

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May 23 19:59:00 2016
  InstallationDate: Installed on 2009-11-30 (2366 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to xenial 

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Rich Fiekowsky]

Seems to be the same problem for me. 
Running 14.04, up-to-date as of Mar 4 2016.  
It started happening when I upgraded from iPhone4 running iOS 7 to iPhone5c 
with  iOS 9.2 . 
Noticed another change :  iPhone4 used to mount at two different mount points - 
one had the applications as folders - I think it was named "Documents" - that 
one no longer appears in Nautilus. The "Username's iPhone" mount point still 
appears, and works well.
TIA!

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Rich Daley]

Thanks! I think where it got confusing is that those of us who reported
this against VLC got added to this defect when someone decided they were
the same thing. I will follow that other case.

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

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Fix Released
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Invalid
Status in totem source package in Vivid:
  In Progress
Status in vlc source package in Vivid:
  Invalid

Bug description:
  [ Description ]

  Under Unity, the menu items "Language" and "Subtitles" do not show
  available languages and subtitles that can be selected.

  [ Fix ]

  Port to GMenu, which can correctly show the menu items.

  NOTE that this removes the menu from full screen under Unity.

  [ QA ]

  Test under both Unity and GNOME shell (and optionally other DEs) that
  you can load a video (e.g.
  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
  [large - 819M]) with subtitles and languages and select between them.

  [ Development fix ]

  Identical & already uploaded.

  [ Regression potential ]

  Due to the nature of this change, you won't get the app menu when full
  screened under Unity any more - langs and subtitles can only be
  selected from the regular menu which is visible when not in full
  screen.

  No other regressions are expected, so if you find any please report in
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Desktop-packages] [Bug 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Rich Daley]

+1 to pwuertz's comment. This is a wider issue than totem so marking it
as resolved when there's a workaround only for totem doesn't help those
of us with issues in VLC.

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

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Fix Released
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Invalid
Status in totem source package in Vivid:
  In Progress
Status in vlc source package in Vivid:
  Invalid

Bug description:
  [ Description ]

  Under Unity, the menu items "Language" and "Subtitles" do not show
  available languages and subtitles that can be selected.

  [ Fix ]

  Port to GMenu, which can correctly show the menu items.

  NOTE that this removes the menu from full screen under Unity.

  [ QA ]

  Test under both Unity and GNOME shell (and optionally other DEs) that
  you can load a video (e.g.
  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv
  [large - 819M]) with subtitles and languages and select between them.

  [ Development fix ]

  Identical & already uploaded.

  [ Regression potential ]

  Due to the nature of this change, you won't get the app menu when full
  screened under Unity any more - langs and subtitles can only be
  selected from the regular menu which is visible when not in full
  screen.

  No other regressions are expected, so if you find any please report in
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+subscriptions

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

[Desktop-packages] [Bug 1296275] Re: PTP Cameras not working on 14.04, works flawlessly on 12.04

[rich painter]

I would like to join in by reporting that my Canon PowerShot SX20IS will
also not function on the USB for my Lenovo T530 running Ubuntu 14.04 LTS
64bit updated. It works fine in my windows vista and xp machines.

lsusb shows
Bus 003 Device 006: ID 04a9:31e4 Canon, Inc. 

gtkam reports the proper model is detected but reports "cannot
initialize it"

gnome3 automounts it on the desktop which when double clicked the
contents are empty.

ls -l /run/user// in part shows:
d? ? ?   ? ?? gvfs/

regards
rich painter

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

Title:
  PTP Cameras not working on 14.04, works flawlessly on 12.04

Status in GVFS:
  Unknown
Status in libgphoto:
  New
Status in Rapid Photo Downloader:
  Invalid
Status in gvfs package in Ubuntu:
  Triaged
Status in libgphoto2 package in Ubuntu:
  Fix Released
Status in gvfs source package in Trusty:
  Won't Fix
Status in libgphoto2 source package in Trusty:
  Fix Released
Status in gvfs source package in Utopic:
  Triaged
Status in libgphoto2 source package in Utopic:
  Fix Released

Bug description:
  I have a Canon Powershot A3200 camera. It works perfectly on 12.04,
  pops right up when I plug it in. However on 14.04 nothing happens.

  lsusb outputs shows that the camera is detected, with the right model.

  SRU INFORMATION:
  
  IMPACT: All PtP cameras which don't have an explicit vendor/model match in 
/lib/udev/hwdb.d/20-libgphoto2-6.hwdb stop working in gvfs/shotwell/etc. This 
is a regression since Saucy.

  FIX: Bring back the udev rule to tag generic PtP devices that we had had for 
many releases. This will tag the udev_device with the ID_GPHOTO2 property which 
is where gvfs and friends are looking (not on the usb_interface child).
  Patch: 
http://launchpadlibrarian.net/177343655/libgphoto2_2.5.4-1ubuntu1_2.5.4-1ubuntu2.diff.gz

  REGRESSION POTENTIAL: Very low. Adding tags to the wrong device might
  confuse gvfs/shotwell and friends, but this rule had been in
  production for many years. Broken udev rules are harmless except for
  error spew in syslog, and this doesn't interfere with the hwdb
  database as it only matches on usb_devices, not on usb_interfaces.

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

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

[Desktop-packages] [Bug 1450935] [NEW] Rhythmbox crashed when I added to a large Play Queue

[Rich Fiekowsky]

Public bug reported:

Rhythmbox just crashed on my Ubuntu 14.04 system on a Dell GX620. The Dell 
mimitower has the  integrated sound and 4 GB RAM.
The action that apparently provoked the crash was: I dragged and dropped three 
files from the Music list (in the main pane) onto the Play Queue icon (in the 
left pane). It was playing (not paused) at the time. Earlier in the day, I had 
pointed rhythmbox to my audio directory (in Preferences). RB had finished 
adding the tracks to the Music list. But afterward, I had made a few changes in 
some of the subdirectories of my audio directory.  

At the time, Chromium was using a great deal of RAM, and tabs were open
which had played video with sound.

After the music stopped, apport displayed that there was not enough free
memory to analyze and report the crash. System Monitor showed over 2 GB
free.

I realize my usage is a little extreme:

 - System monitor showed the rhythmbox process was using 255 MB of memory 
before apport killed it. 
  
 - My audio directory contains over 50,000 tracks 
   
 - There were 125 tracks in the Play Queue at the time. I had dragged and 
dropped them there, one at a time or a few at a time, from the Music list.

lsb -rd   sez:
Description:Ubuntu 14.04.2 LTS
Release:14.04

apt-cache policy rhythmbox  sez:
rhythmbox:
  Installed: 3.0.2-0ubuntu2
  Candidate: 3.0.2-0ubuntu2
  Version table:
 *** 3.0.2-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
100 /var/lib/dpkg/status
 3.0.2-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

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

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

Title:
  Rhythmbox crashed when I added to a large Play Queue

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox just crashed on my Ubuntu 14.04 system on a Dell GX620. The Dell 
mimitower has the  integrated sound and 4 GB RAM.
  The action that apparently provoked the crash was: I dragged and dropped 
three files from the Music list (in the main pane) onto the Play Queue icon (in 
the left pane). It was playing (not paused) at the time. Earlier in the day, I 
had pointed rhythmbox to my audio directory (in Preferences). RB had finished 
adding the tracks to the Music list. But afterward, I had made a few changes in 
some of the subdirectories of my audio directory.  

  At the time, Chromium was using a great deal of RAM, and tabs were
  open which had played video with sound.

  After the music stopped, apport displayed that there was not enough
  free memory to analyze and report the crash. System Monitor showed
  over 2 GB free.

  I realize my usage is a little extreme:

   - System monitor showed the rhythmbox process was using 255 MB of memory 
before apport killed it. 

   - My audio directory contains over 50,000 tracks 
 
   - There were 125 tracks in the Play Queue at the time. I had dragged and 
dropped them there, one at a time or a few at a time, from the Music list.

  lsb -rd   sez:
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  apt-cache policy rhythmbox  sez:
  rhythmbox:
Installed: 3.0.2-0ubuntu2
Candidate: 3.0.2-0ubuntu2
Version table:
   *** 3.0.2-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   3.0.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

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

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

[Desktop-packages] [Bug 1448634] [NEW] VLC menu items don't enable during playback

[Rich Daley]

Public bug reported:

Since upgrading to 15.04 (and hence Unity 7.3.2) I'm having trouble with
the menus in VLC.

Several items on the "Video" menu are disabled when playback is stopped
and are meant to become enabled during playback.

I initially reported this as a bug in VLC, but they reckon it's a Unity
issue as the right-click context menu works fine:
https://forum.videolan.org/viewtopic.php?f=13&t=125719&p=422755#p422755

I have confirmed this happens with both Statusbar menus and Locally
Integrated menus. And I can also confirm that on the last day of 14.10
before I upgraded it was working fine in that version of Unity.

I've also confirmed that changing to different VLC packages (such as
those from PPAs) does not resolve the issue.

Thanks for your help!

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.2+15.04.20150420-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Sun Apr 26 10:51:54 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-30 (85 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: unity
UpgradeStatus: Upgraded to vivid on 2015-04-23 (2 days ago)

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


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  VLC menu items don't enable during playback

Status in unity package in Ubuntu:
  New

Bug description:
  Since upgrading to 15.04 (and hence Unity 7.3.2) I'm having trouble
  with the menus in VLC.

  Several items on the "Video" menu are disabled when playback is
  stopped and are meant to become enabled during playback.

  I initially reported this as a bug in VLC, but they reckon it's a
  Unity issue as the right-click context menu works fine:
  https://forum.videolan.org/viewtopic.php?f=13&t=125719&p=422755#p422755

  I have confirmed this happens with both Statusbar menus and Locally
  Integrated menus. And I can also confirm that on the last day of 14.10
  before I upgraded it was working fine in that version of Unity.

  I've also confirmed that changing to different VLC packages (such as
  those from PPAs) does not resolve the issue.

  Thanks for your help!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr 26 10:51:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-30 (85 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (2 days ago)

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

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

[Desktop-packages] [Bug 1425526] [NEW] nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build

[Rich Gore]

Public bug reported:

The bug report popped up after installing the latest upadate I think it
was the Ubuntu base?

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
DKMSKernelVersion: 3.13.0-46-generic
Date: Wed Feb 25 08:30:18 2015
InstallationDate: Installed on 2015-02-10 (15 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1425526

Title:
  nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  The bug report popped up after installing the latest upadate I think
  it was the Ubuntu base?

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-46-generic
  Date: Wed Feb 25 08:30:18 2015
  InstallationDate: Installed on 2015-02-10 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1409397] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build

[rich]

Public bug reported:

Problem occurred when installing nvidia drivers after installing 14.04
LTS  and running update manager the firsttime. Instead of installing
the program reported an errror

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-44-generic
Date: Sun Jan 11 01:37:52 2015
InstallationDate: Installed on 2015-01-10 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm 
kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1409397

Title:
  nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm
  kernel module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  Problem occurred when installing nvidia drivers after installing 14.04
  LTS  and running update manager the firsttime. Instead of installing
  the program reported an errror

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Sun Jan 11 01:37:52 2015
  InstallationDate: Installed on 2015-01-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm 
kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1327295] Re: Can't resize "S.M.A.R.T. data" window

[rich painter]

I am running Ubuntu 14.04.1 LTS with Gnome3 64 bit on a Lenovo T530.

I have the same problem with the English (US) presentation. I want to
amplify the bug report...

1. The SMART data popup is not moveable and must be.
2. the popup is not resizable and must be.
3. the individual fields are nearly all truncated.

All of these problems prevent even seeing any of the useful SMART data.

image is attached.

regards
oldunixguy


** Attachment added: "Screenshot from 2014-12-08 10:47:37.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1327295/+attachment/4276393/+files/Screenshot%20from%202014-12-08%2010%3A47%3A37.png

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

Title:
  Can't resize "S.M.A.R.T. data" window

Status in GNOME Disks:
  New
Status in Ubuntu Translations:
  New
Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Can't resize "S.M.A.R.T. data" window to see full-lenght attribute
  names when using some translation (Ukrainian in my case). It makes
  this window very difficult to understand.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun  6 19:40:46 2014
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2014-04-18 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1387098] [NEW] GUI will not start with Ubuntu drivers and Nvidia drivers - nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

[Mark Rich]

Public bug reported:

Have tried various combinations of drivers but the GUI starts only
occasionally and the startup times are very long when it does.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-uvm 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.16.0-24-generic
Date: Wed Oct 29 09:21:05 2014
InstallationDate: Installed on 2014-04-20 (191 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

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

Title:
  GUI will not start with Ubuntu drivers and Nvidia drivers -
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Have tried various combinations of drivers but the GUI starts only
  occasionally and the startup times are very long when it does.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-24-generic
  Date: Wed Oct 29 09:21:05 2014
  InstallationDate: Installed on 2014-04-20 (191 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping

[Rich Wales]

NOT working for me (Ubuntu 14.04, iPhone 4S running iOS 7.1.2).

I'm not getting the trust loop problem, but I am getting "Unhandled
Lockdown error (-20)" and cannot mount the iPhone in order to upload
photos into Shotwell.

I've tried the suggestion to make the /var/lib/lockdown directory
publicly read/writable, but this did not help.

Is there a separate bug for this lockdown problem?

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

Title:
  [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt
  Looping

Status in The Linux Mint Distribution:
  Fix Committed
Status in “libimobiledevice” package in Ubuntu:
  Fix Released
Status in “libimobiledevice” package in Debian:
  Fix Released

Bug description:
  The latest libimobiledevice release 1.1.5 is a year old and does not
  support iOS7 devices. Most iOS devices have been updated to iOS7 by
  now, so currently the library is broken in functionality for most
  users. The git snapshot has been tested to work, but there seems to be
  no new upstream release being prepared for the time being.

  The new git snapshot includes several fixes, including the security
  fix that was previously patched on top of 1.1.5 in Ubuntu.

  Packaging branch merge request attached to this bug report.

  --- Original report ---

  The iPhone reporting "Trust the currently connected computer?" Trust/Don't 
Trust.
  This then happens in a continous loop when clicking Trust.

  ---
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nrawlins   2068 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb
  InstallationDate: Installed on 2013-08-15 (3 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Sony Corporation VGN-SR29XN_S
  MarkForUpload: True
  Package: linux 3.8.0.27.45
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1130Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR29XN_S
  dmi.product.version: C6017UKK
  dmi.sys.vendor: Sony Corporation

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

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

[Desktop-packages] [Bug 1172960] Re: No grid displayed

[Rich Hart]

Went from 1204 which worked fine, to 1404, which is broken.  No grid
lines!

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

Title:
  No grid displayed

Status in “gnome-mines” package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to 13.04 frpm 12.10

  Started Gnome Mines, choose standard game 16x16, game started, but no
  grid displayed. When a square is clicked its grid apperas, as do clean
  neighbouring squares.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-mines 1:3.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri Apr 26 00:09:59 2013
  ExecutablePath: /usr/games/gnome-mines
  InstallationDate: Installed on 2011-10-08 (565 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-mines
  UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:2114): GLib-CRITICAL **: 
g_variant_new_string: assertion `string != NULL' failed
   (polkit-gnome-authentication-agent-1:2114): polkit-gnome-1-WARNING **: 
Failed to register client: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
   (xfsettingsd:2190): xfsettingsd-WARNING **: Failed to get the 
_NET_NUMBER_OF_DESKTOPS property.
   (xfdesktop:2037): GLib-GIO-CRITICAL **: g_file_get_path: assertion 
`G_IS_FILE (file)' failed

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

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

[Desktop-packages] [Bug 1294899] Re: Import saved VPN connection has been Recently Broken

[Mark Rich]

So how does one import the .ovpn and certificate files manually as suggested in 
#26?
I have copied the files to /etc/openvpn and what next?

Some helpful advice beyond the comment to do this may be useful for
those of us who do not know how please.

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

Title:
  Import saved VPN connection has been Recently Broken

Status in The OpenVPN Virtual Private Network:
  Invalid
Status in “network-manager-applet” package in Ubuntu:
  New
Status in “network-manager-openvpn” package in Ubuntu:
  Confirmed
Status in “network-manager-openvpn” package in Debian:
  New

Bug description:
  I believe recent changes have broken network-manager-openvpn feature
  that allows you to "Import saved VPN connection".

  I've tested this feature with bundles that I've definitely imported
  successfully in the past.

  Now, not only does it not import, but it gives absolutely no feedback
  at all; the window just disappears as though I didn't just ask it to
  import a VPN.conf file. The folder (I'm importing the .conf file from)
  includes all the necessary supporting files. I'm very sure this is not
  a user error on my part. I've done this several times in the past and
  I'm certain that the files (that are currently being ignored without
  dialog feedback) are exactly the same as they were when I was able to
  import successfully a few weeks ago.

  I've tested this on multiple machines that have Ubuntu 14.04 installed
  and fully updated.

  And, even if the files were indeed corrupted (which I'm certain they
  are not), the fact that the UI just disappears, instead of showing an
  error, is a bug within itself.

  Also, I'd like to point out, that I was able to set up this VPN bundle
  manually. The point of this bug is to report that the ability to
  import via .conf files (so that you don't have to set things manually)
  has recently became nonfunctional.

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

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

[Desktop-packages] [Bug 1182007] Re: Failed to SUID root

[Mark Rich]

Receiving these messages periodically in /var/log/syslog

Apr 23 18:54:26 markys-home-pc signond[12687]:
../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root.
Secure storage will not be available.

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

Title:
  Failed to SUID root

Status in “signon” package in Ubuntu:
  Confirmed

Bug description:
  signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init
  Failed to SUID root. Secure storage will not be available.

  This report appears in syslog each time Empathy tries and fails to
  connect to Google Talk using the google-talkplugin interface.

  It is not clear whether this SUID report is related to the Empathy
  failure.

  See bug #1168582 "Google talk "Requires Authorization" after
  suspend/resume"

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

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

[Desktop-packages] [Bug 1237118] Re: [CA0106 - CA0106, playback] No sound at all Rocketfish card

[Rich Marganski]

So is there no way to get sound from this card?

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

Title:
  [CA0106 - CA0106, playback] No sound at all Rocketfish card

Status in “alsa-driver” package in Ubuntu:
  New
Status in “gnome-alsamixer” package in Ubuntu:
  New

Bug description:
  I am totally unable to get sound from this sound card and get the
  following errors when using gnome-alsamixer

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Analog Source"!

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Digital Source"!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-31-generic.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard1703 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'CA0106'/'AudigyLS [Unknown] at 0xcf00 irq 21'
 Mixer name : 'CA0106'
 Components : ''
 Controls  : 29
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 19'
 Mixer name : 'Nvidia ID 15'
 Components : 'HDA:10de0015,10de0101,00100100'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Oct  8 18:25:10 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.2)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed
  Symptom_Card: HDA-Intel - HDA NVidia
  Symptom_DevicesInUse:
   1703  richard   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Type: No sound at all
  Title: [CA0106 - CA0106, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.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:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-10-08T18:15:34.000181

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

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

[Desktop-packages] [Bug 1237118] Re: [CA0106 - CA0106, playback] No sound at all Rocketfish card

[Rich Marganski]

I'm sorry, I'm not very familiar with making these config changes. Can
you describe where to do the following? Should I be adding text to a
file or something?

"
1) add Analog Front, Analog Rear, Analog Center/LFE and Analog Side similar to 
Front, Rear, Center, LFE and Side in
2) add Analog Source and elements Phone , Mic, Line In and Aux similar to Input 
Source and Element in
"

Thanks for all the help, just having trouble understanding what you are
asking me to do exaclty

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

Title:
  [CA0106 - CA0106, playback] No sound at all Rocketfish card

Status in “alsa-driver” package in Ubuntu:
  New
Status in “gnome-alsamixer” package in Ubuntu:
  New

Bug description:
  I am totally unable to get sound from this sound card and get the
  following errors when using gnome-alsamixer

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Analog Source"!

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Digital Source"!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-31-generic.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard1703 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'CA0106'/'AudigyLS [Unknown] at 0xcf00 irq 21'
 Mixer name : 'CA0106'
 Components : ''
 Controls  : 29
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 19'
 Mixer name : 'Nvidia ID 15'
 Components : 'HDA:10de0015,10de0101,00100100'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Oct  8 18:25:10 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.2)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed
  Symptom_Card: HDA-Intel - HDA NVidia
  Symptom_DevicesInUse:
   1703  richard   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Type: No sound at all
  Title: [CA0106 - CA0106, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.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:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-10-08T18:15:34.000181

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

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

[Desktop-packages] [Bug 1237118] Re: [CA0106 - CA0106, playback] No sound at all Rocketfish card

[Rich Marganski]

** Attachment added: "alsa-info.txt.dLLZ8XR3GO"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/1237118/+attachment/3870112/+files/alsa-info.txt.dLLZ8XR3GO

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

Title:
  [CA0106 - CA0106, playback] No sound at all Rocketfish card

Status in “alsa-driver” package in Ubuntu:
  New
Status in “gnome-alsamixer” package in Ubuntu:
  New

Bug description:
  I am totally unable to get sound from this sound card and get the
  following errors when using gnome-alsamixer

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Analog Source"!

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Digital Source"!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-31-generic.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard1703 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'CA0106'/'AudigyLS [Unknown] at 0xcf00 irq 21'
 Mixer name : 'CA0106'
 Components : ''
 Controls  : 29
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 19'
 Mixer name : 'Nvidia ID 15'
 Components : 'HDA:10de0015,10de0101,00100100'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Oct  8 18:25:10 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.2)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed
  Symptom_Card: HDA-Intel - HDA NVidia
  Symptom_DevicesInUse:
   1703  richard   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Type: No sound at all
  Title: [CA0106 - CA0106, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.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:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-10-08T18:15:34.000181

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

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

[Desktop-packages] [Bug 1237118] Re: [CA0106 - CA0106, playback] No sound at all Rocketfish card

[Rich Marganski]

** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/1237118/+attachment/3870111/+files/pulseverbose.log

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

Title:
  [CA0106 - CA0106, playback] No sound at all Rocketfish card

Status in “alsa-driver” package in Ubuntu:
  New
Status in “gnome-alsamixer” package in Ubuntu:
  New

Bug description:
  I am totally unable to get sound from this sound card and get the
  following errors when using gnome-alsamixer

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Analog Source"!

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Digital Source"!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-31-generic.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard1703 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'CA0106'/'AudigyLS [Unknown] at 0xcf00 irq 21'
 Mixer name : 'CA0106'
 Components : ''
 Controls  : 29
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 19'
 Mixer name : 'Nvidia ID 15'
 Components : 'HDA:10de0015,10de0101,00100100'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Oct  8 18:25:10 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.2)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed
  Symptom_Card: HDA-Intel - HDA NVidia
  Symptom_DevicesInUse:
   1703  richard   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Type: No sound at all
  Title: [CA0106 - CA0106, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.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:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-10-08T18:15:34.000181

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

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

[Desktop-packages] [Bug 1237118] [NEW] [CA0106 - CA0106, playback] No sound at all Rocketfish card

[Rich Marganski]

Public bug reported:

I am totally unable to get sound from this sound card and get the
following errors when using gnome-alsamixer

** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No idea
what to do for mixer element "Analog Source"!

** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No idea
what to do for mixer element "Digital Source"!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-31-generic.
ApportVersion: 2.0.1-0ubuntu17.5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  richard1703 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'CA0106'/'AudigyLS [Unknown] at 0xcf00 irq 21'
   Mixer name   : 'CA0106'
   Components   : ''
   Controls  : 29
   Simple ctrls  : 13
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 19'
   Mixer name   : 'Nvidia ID 15'
   Components   : 'HDA:10de0015,10de0101,00100100'
   Controls  : 0
   Simple ctrls  : 0
Card1.Amixer.values:
 
Date: Tue Oct  8 18:25:10 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.2)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed
Symptom_Card: HDA-Intel - HDA NVidia
Symptom_DevicesInUse:
 1703  richard   F pulseaudio
 PID ACCESS COMMAND
Symptom_Type: No sound at all
Title: [CA0106 - CA0106, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.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:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-10-08T18:15:34.000181

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


** Tags: apport-bug i386 precise running-unity

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

Title:
  [CA0106 - CA0106, playback] No sound at all Rocketfish card

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  I am totally unable to get sound from this sound card and get the
  following errors when using gnome-alsamixer

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Analog Source"!

  ** (gnome-alsamixer:2614): WARNING **: gam_toggle_get_state (). No
  idea what to do for mixer element "Digital Source"!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-31-generic.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard1703 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'CA0106'/'AudigyLS [Unknown] at 0xcf00 irq 21'
 Mixer name : 'CA0106'
 Components : ''
 Controls  : 29
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 19'
 Mixer name : 'Nvidia ID 15'
 Components : 'HDA:10de0015,10de0101,00100100'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Oct  8 18:25:10 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.2)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed
  Symptom_Card: HDA-Intel - HDA NVidia
  Symptom_DevicesInUse:
   1703  richard   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Type: No sound at all
  Title: [CA0106 - CA0106, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh inst

[Desktop-packages] [Bug 1195025] [NEW] banshee crashed (using dlna playback plugin)

[Rich]

Public bug reported:

using the dlna playback plugin it just crashed.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic i686
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rel1987 F pulseaudio
Date: Wed Jun 26 16:55:00 2013
InstallationDate: Installed on 2011-11-24 (580 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Black SPDIF Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [Ratel Ultra, Realtek ALC889, Black SPDIF Out, Rear] Playback problem
UpgradeStatus: Upgraded to raring on 2013-05-13 (44 days ago)
dmi.bios.date: 03/09/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: JGIBX10J.86A.0396.2010.0309.2234
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DH57JG
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE70930-302
dmi.chassis.type: 2
dmi.modalias: 
dmi:bvnIntelCorp.:bvrJGIBX10J.86A.0396.2010.0309.2234:bd03/09/2010:svnSystem76,Inc:pnRatelUltra:pvrratu1:rvnIntelCorporation:rnDH57JG:rvrAAE70930-302:cvn:ct2:cvr:
dmi.product.name: Ratel Ultra
dmi.product.version: ratu1
dmi.sys.vendor: System76, Inc

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


** Tags: apport-bug gnome3-ppa i386 raring third-party-packages

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

Title:
  banshee crashed (using dlna playback plugin)

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  using the dlna playback plugin it just crashed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rel1987 F pulseaudio
  Date: Wed Jun 26 16:55:00 2013
  InstallationDate: Installed on 2011-11-24 (580 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Ratel Ultra, Realtek ALC889, Black SPDIF Out, Rear] Playback problem
  UpgradeStatus: Upgraded to raring on 2013-05-13 (44 days ago)
  dmi.bios.date: 03/09/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: JGIBX10J.86A.0396.2010.0309.2234
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DH57JG
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70930-302
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrJGIBX10J.86A.0396.2010.0309.2234:bd03/09/2010:svnSystem76,Inc:pnRatelUltra:pvrratu1:rvnIntelCorporation:rnDH57JG:rvrAAE70930-302:cvn:ct2:cvr:
  dmi.product.name: Ratel Ultra
  dmi.product.version: ratu1
  dmi.sys.vendor: System76, Inc

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

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

[Desktop-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while

[Rich Moffat]

unfortunely for me it's just a temporary fix. I'm lucky if I go for 5
minutes with sound. And that's just if the pc is cold. It does also seem
to be affected by the type of sound (I know that sounds crazy). I was
watching one video of someone etching a circuit board. When he was
showing running it under the tap to rinse it off it will cut out within
5 seconds. I tried it repeatedly (20 times at least) with the same
results. All other sections I can get 1-5 minutes of sound before it
cuts out. Something about that frequency seems to make things work. Go
figure

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

Title:
  [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Restart will fix the issue, but sound always quits from internal
  speaker. Headphones work always.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1838 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 44'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f15069,1179fc50,00100302 
HDA:80862805,1179fc50,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Sat Aug 18 11:18:34 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd07/13/2011:svnTOSHIBA:pnSatelliteL755:pvrPSK1WU-05N004:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L755
  dmi.product.version: PSK1WU-05N004
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while

[Rich Moffat]

Another clue (for someone. I don't understand it)

If I "suspend" my system my sound is back on return. (sudo pm-suspend)

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

Title:
  [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Restart will fix the issue, but sound always quits from internal
  speaker. Headphones work always.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1838 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 44'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f15069,1179fc50,00100302 
HDA:80862805,1179fc50,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Sat Aug 18 11:18:34 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd07/13/2011:svnTOSHIBA:pnSatelliteL755:pvrPSK1WU-05N004:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L755
  dmi.product.version: PSK1WU-05N004
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while

[Rich Moffat]

Here is the output from alsa-info.sh (I'm assuming that's what you
meant). 3 files in attached tar file:

alsa-output-before.txt
alsa-output-after.txt
alsa-output-diff.txt

** Attachment added: "alsa-output results"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1038479/+attachment/3467160/+files/alsa-output.tar

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

Title:
  [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Restart will fix the issue, but sound always quits from internal
  speaker. Headphones work always.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1838 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 44'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f15069,1179fc50,00100302 
HDA:80862805,1179fc50,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Sat Aug 18 11:18:34 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd07/13/2011:svnTOSHIBA:pnSatelliteL755:pvrPSK1WU-05N004:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L755
  dmi.product.version: PSK1WU-05N004
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while

[Rich Moffat]

Same issue with my L755. Been chasing solutions for two weekends now.
Tried solutions for similar solutions to no avail.

Any additional info I can give to move this along can be provided.

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

Title:
  [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Restart will fix the issue, but sound always quits from internal
  speaker. Headphones work always.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1838 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 44'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f15069,1179fc50,00100302 
HDA:80862805,1179fc50,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Sat Aug 18 11:18:34 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd07/13/2011:svnTOSHIBA:pnSatelliteL755:pvrPSK1WU-05N004:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L755
  dmi.product.version: PSK1WU-05N004
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1078755] [NEW] package colord 0.1.16-2ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[rich]

Public bug reported:

This occured automatically ... wdo came up saying "System problem
problem detected" asked for report to be submitted, then sent be here in
the brouser ... The "problem problem" is an interesting msg

I have no clue what is wrong with my system that has been reported

Description:Ubuntu 12.04.1 LTS

rich@rich-office:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
rich@rich-office:~$ apt-cache policy apport-package
N: Unable to locate package apport-package
rich@rich-office:~$ 

rich@rich-office:~$ apt-cache policy colord
colord:
  Installed: 0.1.16-2ubuntu0.1
  Candidate: 0.1.16-2ubuntu0.1
  Version table:
 *** 0.1.16-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.1.16-2 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
rich@rich-office:~$

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: colord 0.1.16-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
Uname: Linux 3.2.0-32-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu15
Architecture: i386
Date: Tue Nov 13 18:58:43 2012
ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MarkForUpload: True
SourcePackage: colord
Title: package colord 0.1.16-2ubuntu0.1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
UpgradeStatus: Upgraded to precise on 2012-11-14 (0 days ago)

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


** Tags: apport-package i386 precise

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

Title:
  package colord 0.1.16-2ubuntu0.1 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 1

Status in “colord” package in Ubuntu:
  New

Bug description:
  This occured automatically ... wdo came up saying "System problem
  problem detected" asked for report to be submitted, then sent be here
  in the brouser ... The "problem problem" is an interesting msg

  I have no clue what is wrong with my system that has been reported

  Description:Ubuntu 12.04.1 LTS

  rich@rich-office:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  rich@rich-office:~$ apt-cache policy apport-package
  N: Unable to locate package apport-package
  rich@rich-office:~$ 

  rich@rich-office:~$ apt-cache policy colord
  colord:
Installed: 0.1.16-2ubuntu0.1
Candidate: 0.1.16-2ubuntu0.1
Version table:
   *** 0.1.16-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.1.16-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  rich@rich-office:~$

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: colord 0.1.16-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Uname: Linux 3.2.0-32-generic-pae i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  Date: Tue Nov 13 18:58:43 2012
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
  MarkForUpload: True
  SourcePackage: colord
  Title: package colord 0.1.16-2ubuntu0.1 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to precise on 2012-11-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1061073] Re: Desktop effects are slow and desktop corruption using mesa 9

[Rich Sezov]

@sarvatt: Does this mean there's an update now in Quantal? Because I
(temporarily) went back to Precise to avoid this issue.

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

Title:
  Desktop effects are slow and desktop corruption using mesa 9

Status in KDE Base Workspace:
  New
Status in Mesa:
  Won't Fix
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I have Kubuntu 12.10 set up on a ThinkPad T430.

  I'm experiencing both desktop corruption and slow performance of
  desktop effects. I've tried to downgrade mesa to 8.0.4 and that fixed
  the problem.

  Attached is a video comparing the two. The video does not show the
  desktop corruption I mention (vertical lines appearing) but I will
  attach a screenshot of that.

  I originally thought this was related to bug 1042211 but they told me
  to file another report since it seems to be different artifacts that
  I'm seeing.

  Of course I can't say for sure whether the slow performance and the
  artifacts are due to the same problem but the artifacts seem to appear
  when the desktop effects are activated. As you can see in the video,
  mesa 9.0 displays much "jerkier" effects and it seems that when the
  artifacts come this jerking becomes really bad just before the
  artifacts appear. Just now I did notice that the artifacts appeared at
  the mouse pointer when I clicked in a window. The artifacts followed
  the mouse pointer as I moved it but after clicking a few times they
  disappeared.

  WORKAROUND:
  As described in bug 1042211 I downloaded the 8.0.4 version of mesa from 
https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1. This fixed the 
problem for me.

  Since it took a little while for me to figure out how to get the .deb 
packages from that page, here is how for anyone who wants to try:
  1) Go to the above page.
  2) Under "Builds" select your architecture
  3) This will bring you to a page with all the .deb files for your 
architecture. I only installed the libgl1-mesa-dri, libgl1-mesa-glx, 
libglapi-mesa and libglu1-mesa packages.

  Please let me know if you need more information.

  p.s. I had some problems choosing the package for this bug. It
  wouldn't let me put it on libgl1-mesa so I put it on libgl1-mesa-dri.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 15:40:20 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroRelease: Ubuntu 12.10
  DistroVariant: kubuntu
  DkmsStatus: virtualbox, 4.1.18, 3.5.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f3]
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  MachineType: LENOVO 2347W2U
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=c8916e6c-a99f-43f1-9d8c-c1daf21fedac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Tags:  quantal kubuntu
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET41WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347W2U
  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:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2347W2U:pvrThinkPadT430:rvnLENOVO:rn2347W2U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347W2U
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3
  ver

[Desktop-packages] [Bug 1061073] Re: Desktop effects are slow and desktop corruption using mesa 9

[Rich Sezov]

Okay, I got my machine working properly, but I had to go back to a
12.04-based distro (I used Netrunner). Here's how to get things working,
without the trial and error that I went through.

1. Install the OS. 
2. Disable Desktop effects, and install all patches. 
3. Add the Bumblebee and x-swat PPAs. You have to do this because the latest 
NVidia drivers aren't in the 12.04 repos. 
4. apt-get install bumblebee bumblebee-nvidia. This adds the latest NVidia 
driver to your machine. Unfortunately, it also installs the problematic Mesa 9 
libraries. We will fix this in the next step. It's also important that you have 
desktop effects turned off. If they're still on when you reboot, you'll get 
really bad system locks. Once this is installed, reboot. 
5. Video is configured correctly, but will have all kinds of problems if you 
enable desktop effects. To get everything working properly, you need to 
downgrade to Mesa 8.0.4. The following command will do that: 

sudo apt-get install libglapi-mesa=8.0.4-0ubuntu0.1 libgl1-mesa-
glx=8.0.4-0ubuntu0.1 ia32-libs=20090808ubuntu35 ia32-libs-
multiarch:i386=20090808ubuntu35 libgl1-mesa-glx:i386=8.0.4-0ubuntu0.1
libglapi-mesa:i386=8.0.4-0ubuntu0.1 libglu1-mesa:i386=8.0.4-0ubuntu0.1
libgl1-mesa-dri=8.0.4-0ubuntu0.1

6. Reboot. When you log back in, hit Alt-Shift-F12 and test that desktop
effects are working properly. If they are, you can enable them by
default.

7. To prevent constant update notifications, I used ppa-purge to remove
the x-swat PPA.

8. Add the kubuntu-backports PPA and install KDE 4.9.2, which is the
same version of KDE that 12.10 has.

You now have a working system! No package mess, and you're running
basically the same software. Since this seems to be a KDE bug, I'm not
all that hopeful for a fix here; I'm betting it'll take another KDE
release. So for the time being, I'm staying on this set up until either
this bug is marked as fixed or the one from KDE is marked as fixed and
there's a new release available.

I hope this helps somebody!

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

Title:
  Desktop effects are slow and desktop corruption using mesa 9

Status in KDE Base Workspace:
  New
Status in Mesa:
  Confirmed
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I have Kubuntu 12.10 set up on a ThinkPad T430.

  I'm experiencing both desktop corruption and slow performance of
  desktop effects. I've tried to downgrade mesa to 8.0.4 and that fixed
  the problem.

  Attached is a video comparing the two. The video does not show the
  desktop corruption I mention (vertical lines appearing) but I will
  attach a screenshot of that.

  I originally thought this was related to bug 1042211 but they told me
  to file another report since it seems to be different artifacts that
  I'm seeing.

  Of course I can't say for sure whether the slow performance and the
  artifacts are due to the same problem but the artifacts seem to appear
  when the desktop effects are activated. As you can see in the video,
  mesa 9.0 displays much "jerkier" effects and it seems that when the
  artifacts come this jerking becomes really bad just before the
  artifacts appear. Just now I did notice that the artifacts appeared at
  the mouse pointer when I clicked in a window. The artifacts followed
  the mouse pointer as I moved it but after clicking a few times they
  disappeared.

  WORKAROUND:
  As described in bug 1042211 I downloaded the 8.0.4 version of mesa from 
https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1. This fixed the 
problem for me.

  Since it took a little while for me to figure out how to get the .deb 
packages from that page, here is how for anyone who wants to try:
  1) Go to the above page.
  2) Under "Builds" select your architecture
  3) This will bring you to a page with all the .deb files for your 
architecture. I only installed the libgl1-mesa-dri, libgl1-mesa-glx, 
libglapi-mesa and libglu1-mesa packages.

  Please let me know if you need more information.

  p.s. I had some problems choosing the package for this bug. It
  wouldn't let me put it on libgl1-mesa so I put it on libgl1-mesa-dri.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 15:40:20 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/s

[Desktop-packages] [Bug 1061073] Re: Desktop effects are slow and desktop corruption using mesa 9

[Rich Sezov]

Possible newbie question: how did you downgrade to Mesa 8.0.4? I've been
looking for a PPA, but haven't found one. Should I grab the ones from
the Precise repository?

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

Title:
  Desktop effects are slow and desktop corruption using mesa 9

Status in KDE Base Workspace:
  New
Status in Mesa:
  Unknown
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I have Kubuntu 12.10 set up on a ThinkPad T430.

  I'm experiencing both desktop corruption and slow performance of
  desktop effects. I've tried to downgrade mesa to 8.0.4 and that fixed
  the problem.

  Attached is a video comparing the two. The video does not show the
  desktop corruption I mention (vertical lines appearing) but I will
  attach a screenshot of that.

  I originally thought this was related to bug 1042211 but they told me
  to file another report since it seems to be different artifacts that
  I'm seeing.

  Of course I can't say for sure whether the slow performance and the
  artifacts are due to the same problem but the artifacts seem to appear
  when the desktop effects are activated. As you can see in the video,
  mesa 9.0 displays much "jerkier" effects and it seems that when the
  artifacts come this jerking becomes really bad just before the
  artifacts appear. Just now I did notice that the artifacts appeared at
  the mouse pointer when I clicked in a window. The artifacts followed
  the mouse pointer as I moved it but after clicking a few times they
  disappeared.

  WORKAROUND:
  As described in bug 1042211 I downloaded the 8.0.4 version of mesa from 
https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1. This fixed the 
problem for me.

  Since it took a little while for me to figure out how to get the .deb 
packages from that page, here is how for anyone who wants to try:
  1) Go to the above page.
  2) Under "Builds" select your architecture
  3) This will bring you to a page with all the .deb files for your 
architecture. I only installed the libgl1-mesa-dri, libgl1-mesa-glx, 
libglapi-mesa and libglu1-mesa packages.

  Please let me know if you need more information.

  p.s. I had some problems choosing the package for this bug. It
  wouldn't let me put it on libgl1-mesa so I put it on libgl1-mesa-dri.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 15:40:20 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroRelease: Ubuntu 12.10
  DistroVariant: kubuntu
  DkmsStatus: virtualbox, 4.1.18, 3.5.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f3]
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  MachineType: LENOVO 2347W2U
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=c8916e6c-a99f-43f1-9d8c-c1daf21fedac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Tags:  quantal kubuntu
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET41WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347W2U
  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:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2347W2U:pvrThinkPadT430:rvnLENOVO:rn2347W2U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347W2U
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri

[Desktop-packages] [Bug 1061073] Re: Desktop effects are slow and desktop corruption using mesa 9

[Rich Sezov]

Did I say Render (yes I did)? Yes, I meant Raster. That seems to have at
least gotten rid of the screen corruption, though the effects are still
slow.

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

Title:
  Desktop effects are slow and desktop corruption using mesa 9

Status in Mesa:
  Unknown
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I have Kubuntu 12.10 set up on a ThinkPad T430.

  I'm experiencing both desktop corruption and slow performance of
  desktop effects. I've tried to downgrade mesa to 8.0.4 and that fixed
  the problem.

  Attached is a video comparing the two. The video does not show the
  desktop corruption I mention (vertical lines appearing) but I will
  attach a screenshot of that.

  I originally thought this was related to bug 1042211 but they told me
  to file another report since it seems to be different artifacts that
  I'm seeing.

  Of course I can't say for sure whether the slow performance and the
  artifacts are due to the same problem but the artifacts seem to appear
  when the desktop effects are activated. As you can see in the video,
  mesa 9.0 displays much "jerkier" effects and it seems that when the
  artifacts come this jerking becomes really bad just before the
  artifacts appear. Just now I did notice that the artifacts appeared at
  the mouse pointer when I clicked in a window. The artifacts followed
  the mouse pointer as I moved it but after clicking a few times they
  disappeared.

  WORKAROUND:
  As described in bug 1042211 I downloaded the 8.0.4 version of mesa from 
https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1. This fixed the 
problem for me.

  Since it took a little while for me to figure out how to get the .deb 
packages from that page, here is how for anyone who wants to try:
  1) Go to the above page.
  2) Under "Builds" select your architecture
  3) This will bring you to a page with all the .deb files for your 
architecture. I only installed the libgl1-mesa-dri, libgl1-mesa-glx, 
libglapi-mesa and libglu1-mesa packages.

  Please let me know if you need more information.

  p.s. I had some problems choosing the package for this bug. It
  wouldn't let me put it on libgl1-mesa so I put it on libgl1-mesa-dri.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 15:40:20 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroRelease: Ubuntu 12.10
  DistroVariant: kubuntu
  DkmsStatus: virtualbox, 4.1.18, 3.5.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f3]
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  MachineType: LENOVO 2347W2U
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=c8916e6c-a99f-43f1-9d8c-c1daf21fedac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Tags:  quantal kubuntu
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET41WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347W2U
  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:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2347W2U:pvrThinkPadT430:rvnLENOVO:rn2347W2U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347W2U
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3
  version.libgl1-

[Desktop-packages] [Bug 1061073] Re: Desktop effects are slow and desktop corruption using mesa 9

[Rich Sezov]

Just so you know, I'm not trying to take away from the real (and hard)
work you're doing on this issue: it is a bug, plain and simple, and it
needs to be fixed. I'm just offering a workaround for those of us who
may have installed the beta on our main machines, since we were so close
to the release. :-)

My effects are still slow, but the glitchy windows aren't preventing me
from getting work done anymore. Very much looking forward to the proper
resolution of this issue, and I wish I knew more about KDE development
so that I could be of help. Thanks for your efforts!

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

Title:
  Desktop effects are slow and desktop corruption using mesa 9

Status in Mesa:
  Unknown
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I have Kubuntu 12.10 set up on a ThinkPad T430.

  I'm experiencing both desktop corruption and slow performance of
  desktop effects. I've tried to downgrade mesa to 8.0.4 and that fixed
  the problem.

  Attached is a video comparing the two. The video does not show the
  desktop corruption I mention (vertical lines appearing) but I will
  attach a screenshot of that.

  I originally thought this was related to bug 1042211 but they told me
  to file another report since it seems to be different artifacts that
  I'm seeing.

  Of course I can't say for sure whether the slow performance and the
  artifacts are due to the same problem but the artifacts seem to appear
  when the desktop effects are activated. As you can see in the video,
  mesa 9.0 displays much "jerkier" effects and it seems that when the
  artifacts come this jerking becomes really bad just before the
  artifacts appear. Just now I did notice that the artifacts appeared at
  the mouse pointer when I clicked in a window. The artifacts followed
  the mouse pointer as I moved it but after clicking a few times they
  disappeared.

  WORKAROUND:
  As described in bug 1042211 I downloaded the 8.0.4 version of mesa from 
https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1. This fixed the 
problem for me.

  Since it took a little while for me to figure out how to get the .deb 
packages from that page, here is how for anyone who wants to try:
  1) Go to the above page.
  2) Under "Builds" select your architecture
  3) This will bring you to a page with all the .deb files for your 
architecture. I only installed the libgl1-mesa-dri, libgl1-mesa-glx, 
libglapi-mesa and libglu1-mesa packages.

  Please let me know if you need more information.

  p.s. I had some problems choosing the package for this bug. It
  wouldn't let me put it on libgl1-mesa so I put it on libgl1-mesa-dri.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 15:40:20 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroRelease: Ubuntu 12.10
  DistroVariant: kubuntu
  DkmsStatus: virtualbox, 4.1.18, 3.5.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f3]
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  MachineType: LENOVO 2347W2U
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=c8916e6c-a99f-43f1-9d8c-c1daf21fedac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Tags:  quantal kubuntu
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET41WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347W2U
  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:bvr

[Desktop-packages] [Bug 1061073] Re: Desktop effects are slow and desktop corruption using mesa 9

[Rich Sezov]

I left OpenGL enabled, and only changed the Qt Graphics Subsystem. All
my desktop goodies are in place, so far.

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

Title:
  Desktop effects are slow and desktop corruption using mesa 9

Status in Mesa:
  Unknown
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I have Kubuntu 12.10 set up on a ThinkPad T430.

  I'm experiencing both desktop corruption and slow performance of
  desktop effects. I've tried to downgrade mesa to 8.0.4 and that fixed
  the problem.

  Attached is a video comparing the two. The video does not show the
  desktop corruption I mention (vertical lines appearing) but I will
  attach a screenshot of that.

  I originally thought this was related to bug 1042211 but they told me
  to file another report since it seems to be different artifacts that
  I'm seeing.

  Of course I can't say for sure whether the slow performance and the
  artifacts are due to the same problem but the artifacts seem to appear
  when the desktop effects are activated. As you can see in the video,
  mesa 9.0 displays much "jerkier" effects and it seems that when the
  artifacts come this jerking becomes really bad just before the
  artifacts appear. Just now I did notice that the artifacts appeared at
  the mouse pointer when I clicked in a window. The artifacts followed
  the mouse pointer as I moved it but after clicking a few times they
  disappeared.

  WORKAROUND:
  As described in bug 1042211 I downloaded the 8.0.4 version of mesa from 
https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1. This fixed the 
problem for me.

  Since it took a little while for me to figure out how to get the .deb 
packages from that page, here is how for anyone who wants to try:
  1) Go to the above page.
  2) Under "Builds" select your architecture
  3) This will bring you to a page with all the .deb files for your 
architecture. I only installed the libgl1-mesa-dri, libgl1-mesa-glx, 
libglapi-mesa and libglu1-mesa packages.

  Please let me know if you need more information.

  p.s. I had some problems choosing the package for this bug. It
  wouldn't let me put it on libgl1-mesa so I put it on libgl1-mesa-dri.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 15:40:20 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroRelease: Ubuntu 12.10
  DistroVariant: kubuntu
  DkmsStatus: virtualbox, 4.1.18, 3.5.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f3]
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  MachineType: LENOVO 2347W2U
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=c8916e6c-a99f-43f1-9d8c-c1daf21fedac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Tags:  quantal kubuntu
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET41WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347W2U
  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:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2347W2U:pvrThinkPadT430:rvnLENOVO:rn2347W2U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347W2U
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-

[Desktop-packages] [Bug 1061073] Re: Desktop effects are slow and desktop corruption using mesa 9

[Rich Sezov]

I've gotten this problem to mostly go away (see my post here:
http://www.kubuntuforums.net/showthread.php?60502-Screen-artifacts-
Intel-video) by changing Qt Graphics System to Render in System Settings
-> Desktop Effects.

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

Title:
  Desktop effects are slow and desktop corruption using mesa 9

Status in Mesa:
  Unknown
Status in “kde-workspace” package in Ubuntu:
  Confirmed
Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  I have Kubuntu 12.10 set up on a ThinkPad T430.

  I'm experiencing both desktop corruption and slow performance of
  desktop effects. I've tried to downgrade mesa to 8.0.4 and that fixed
  the problem.

  Attached is a video comparing the two. The video does not show the
  desktop corruption I mention (vertical lines appearing) but I will
  attach a screenshot of that.

  I originally thought this was related to bug 1042211 but they told me
  to file another report since it seems to be different artifacts that
  I'm seeing.

  Of course I can't say for sure whether the slow performance and the
  artifacts are due to the same problem but the artifacts seem to appear
  when the desktop effects are activated. As you can see in the video,
  mesa 9.0 displays much "jerkier" effects and it seems that when the
  artifacts come this jerking becomes really bad just before the
  artifacts appear. Just now I did notice that the artifacts appeared at
  the mouse pointer when I clicked in a window. The artifacts followed
  the mouse pointer as I moved it but after clicking a few times they
  disappeared.

  WORKAROUND:
  As described in bug 1042211 I downloaded the 8.0.4 version of mesa from 
https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1. This fixed the 
problem for me.

  Since it took a little while for me to figure out how to get the .deb 
packages from that page, here is how for anyone who wants to try:
  1) Go to the above page.
  2) Under "Builds" select your architecture
  3) This will bring you to a page with all the .deb files for your 
architecture. I only installed the libgl1-mesa-dri, libgl1-mesa-glx, 
libglapi-mesa and libglu1-mesa packages.

  Please let me know if you need more information.

  p.s. I had some problems choosing the package for this bug. It
  wouldn't let me put it on libgl1-mesa so I put it on libgl1-mesa-dri.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 15:40:20 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroRelease: Ubuntu 12.10
  DistroVariant: kubuntu
  DkmsStatus: virtualbox, 4.1.18, 3.5.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f3]
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905)
  MachineType: LENOVO 2347W2U
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic 
root=UUID=c8916e6c-a99f-43f1-9d8c-c1daf21fedac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Tags:  quantal kubuntu
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET41WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347W2U
  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:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2347W2U:pvrThinkPadT430:rvnLENOVO:rn2347W2U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347W2U
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-

[Desktop-packages] [Bug 1027724] Re: [nvidia] Xorg freeze

[Rich Price]

I am still having periodic freezes.  Has anyone done any work on this?

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

Title:
  [nvidia] Xorg freeze

Status in “nvidia-graphics-drivers” package in Ubuntu:
  Confirmed

Bug description:
  This is yet another case of a hard freeze which started happening
  after upgrading to Ubuntu 12.04. The freeze usually happens when using
  Firefox to access something like a Youtube video. Though this is not
  always the case.

  The upgrade was done about two weeks ago and when I did a update
  Friday the freeze started happening within minutes after the Desktop
  was powered up. IE: The problem was much worse after the upgrade!

  The Dell is also freezing under Ubuntu 2d whenever I start Firefox!

  The freeze is immediate and it has not happened under Ubuntu 2d with
  any other application.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  295.40  Thu Apr  5 21:28:09 PDT 
2012
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDmesg:
   [   42.568030] eth0: no IPv6 routers present
   [   61.529598] init: mysql post-start process (1042) terminated with status 1
   [   70.066948] init: plymouth-stop pre-start process (1713) terminated with 
status 1
   [ 1032.933089] sched: RT throttling activated
   [ 1034.961927] NVRM: Xid (:01:00): 13, 0001  5097 0548 
3f80 0080
  Date: Sun Jul 22 14:46:26 2012
  DistUpgraded: 2012-07-10 15:54:00,643 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 295.40, 3.0.0-16-generic, i686: installed
   nvidia-current, 295.40, 3.2.0-26-generic, i686: installed
  ExtraDebuggingInterest: Yes,
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8300 GS] [10de:0423] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0494]
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: Dell Inc. Inspiron 530
  ProcKernelCmdLine: root=UUID=9c842111-a0d0-46db-9511-94f5833f3f96 ro quiet 
splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to precise on 2012-07-10 (11 days ago)
  dmi.bios.date: 07/12/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 0RY007
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd07/12/2007:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.2
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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

[Desktop-packages] [Bug 980710] Re: black font on black background in xfce terminal

[Rich Winslow]

For the command line inhibited that read this thread; on my Ubuntu 12.04
/ XFCE system I was able to get Evolution's colors to be correct by
using Synaptic package manager to install the "shimmer-themes" package.
It includes the albatross, bluebird and greybird themes.  Select one of
these themes and Evolution follows the theme and looks good.  Reading
elsewhere it appears that Evolution wants a GTK3 theme.  Later I
installed some other GTK3 themes from gnome-look.org and Evolution is OK
with any of them as well.

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

Title:
  black font on black background in xfce terminal

Status in “gnome-terminal” package in Ubuntu:
  Confirmed

Bug description:
  Fresh 12.04 beta 2 install, added gnome, xfce4 and synaptic, all
  packages up to , didn't customize any settings yet

  Loging in with xfce as session type, picking  "Terminal Emulator" from
  the XFCE menu.

  Gnome Terminal starts but only shows a black content area, only after
  disabling "use colors from system theme" in the default profile i'm
  getting a readable font/background color combination

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-terminal 3.4.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 13 12:55:29 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1029926] [NEW] Auto-login does not work with lightdm

[Justin Rich]

Public bug reported:

Release from lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
 **Note** This is actually Xubuntu, with XFCE 4.8.

Lightdm Package:
lightdm:
  Installed: 1.2.1-0ubuntu1
  Candidate: 1.2.1-0ubuntu1
  Version table:
 *** 1.2.1-0ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
100 /var/lib/dpkg/status


Attempted asking on launchpad first, this is the post:
https://answers.launchpad.net/ubuntu/+source/lightdm/+question/204213

In summary, when I installed I selected to use autologin and it worked
fine, except that it was using en_GB locale instead of en_US.  Didn't
know how to change locale at first so I just went to
Applications>System>Users and Groups and made it ask for a password to
login.  This allowed me to select locale on login.  I've since changed
it to automatically use en_US so I tried to turn auto-login back on.  I
at first just clicked the box to no longer ask for a password and it
didn't work.  It switched to a nosplash view for about a second and
switched back to the greeter.  Had to log in as a guest and change it
back to asking for a password so that I could log in.  This is my
/etc/lightdm/lightdm.conf output:

[SeatDefaults]
user-session=xubuntu
greeter-session=lightdm-gtk-greeter
autologin-user=justin
autologin-user-timeout=0

Just like http://xubuntu.org/news/faq-1204-precise/ says.

This is the only thing that stuck out from /var/log/lightdm.log:

[+941.41s] WARNING: Could not call SetLanguage:
GDBus.Error:org.freedesktop.Acc$

Syslog only had one thing when I grepped "lightdm":

Jul 27 07:16:00 justin-Presario-V2000-EZ617UA-ABA lightdm: pam_ecryptfs:
Passphrase file wrapped

Thanks in advance!

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


** Tags: auto autologin lightdm login xubuntu

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

Title:
  Auto-login does not work with lightdm

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Release from lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04
   **Note** This is actually Xubuntu, with XFCE 4.8.

  Lightdm Package:
  lightdm:
Installed: 1.2.1-0ubuntu1
Candidate: 1.2.1-0ubuntu1
Version table:
   *** 1.2.1-0ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  
  Attempted asking on launchpad first, this is the post:
  https://answers.launchpad.net/ubuntu/+source/lightdm/+question/204213

  In summary, when I installed I selected to use autologin and it worked
  fine, except that it was using en_GB locale instead of en_US.  Didn't
  know how to change locale at first so I just went to
  Applications>System>Users and Groups and made it ask for a password to
  login.  This allowed me to select locale on login.  I've since changed
  it to automatically use en_US so I tried to turn auto-login back on.
  I at first just clicked the box to no longer ask for a password and it
  didn't work.  It switched to a nosplash view for about a second and
  switched back to the greeter.  Had to log in as a guest and change it
  back to asking for a password so that I could log in.  This is my
  /etc/lightdm/lightdm.conf output:

  [SeatDefaults]
  user-session=xubuntu
  greeter-session=lightdm-gtk-greeter
  autologin-user=justin
  autologin-user-timeout=0

  Just like http://xubuntu.org/news/faq-1204-precise/ says.

  This is the only thing that stuck out from /var/log/lightdm.log:

  [+941.41s] WARNING: Could not call SetLanguage:
  GDBus.Error:org.freedesktop.Acc$

  Syslog only had one thing when I grepped "lightdm":

  Jul 27 07:16:00 justin-Presario-V2000-EZ617UA-ABA lightdm:
  pam_ecryptfs: Passphrase file wrapped

  Thanks in advance!

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

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

[Desktop-packages] [Bug 1028608] Re: package gdm (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 128

[rich]

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

Title:
  package gdm (not installed) failed to install/upgrade: подпроцесс
  установлен сценарий post-removal возвратил код ошибки 128

Status in “gdm” package in Ubuntu:
  New

Bug description:
  package gdm (not installed) failed to install / upgrade: subprocess
  installed post-removal script returned error code 128

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: gdm (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  AptOrdering:
   gdm: Purge
   linux-image-3.2.0-27-generic: Configure
   linux-image-generic: Configure
   linux-image: Configure
  Architecture: amd64
  Date: Tue Jul 24 23:55:46 2012
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 128
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: gdm
  Title: package gdm (not installed) failed to install/upgrade: подпроцесс 
установлен сценарий post-removal возвратил код ошибки 128
  UpgradeStatus: Upgraded to precise on 2012-03-30 (115 days ago)

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

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

[Desktop-packages] [Bug 1028608] [NEW] package gdm (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 128

[rich]

Public bug reported:

package gdm (not installed) failed to install / upgrade: subprocess
installed post-removal script returned error code 128

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: gdm (not installed)
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
AptOrdering:
 gdm: Purge
 linux-image-3.2.0-27-generic: Configure
 linux-image-generic: Configure
 linux-image: Configure
Architecture: amd64
Date: Tue Jul 24 23:55:46 2012
ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 
128
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
SourcePackage: gdm
Title: package gdm (not installed) failed to install/upgrade: подпроцесс 
установлен сценарий post-removal возвратил код ошибки 128
UpgradeStatus: Upgraded to precise on 2012-03-30 (115 days ago)

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


** Tags: amd64 apport-package precise

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

Title:
  package gdm (not installed) failed to install/upgrade: подпроцесс
  установлен сценарий post-removal возвратил код ошибки 128

Status in “gdm” package in Ubuntu:
  New

Bug description:
  package gdm (not installed) failed to install / upgrade: subprocess
  installed post-removal script returned error code 128

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: gdm (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  AptOrdering:
   gdm: Purge
   linux-image-3.2.0-27-generic: Configure
   linux-image-generic: Configure
   linux-image: Configure
  Architecture: amd64
  Date: Tue Jul 24 23:55:46 2012
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 128
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: gdm
  Title: package gdm (not installed) failed to install/upgrade: подпроцесс 
установлен сценарий post-removal возвратил код ошибки 128
  UpgradeStatus: Upgraded to precise on 2012-03-30 (115 days ago)

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

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

[Desktop-packages] [Bug 1025786] Re: Screencloud updates by commercial-ppa-uploaders added by software center fail with error 401

[Rich]

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

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

Title:
  Screencloud updates by commercial-ppa-uploaders added by software
  center fail with error 401

Status in “software-center” package in Ubuntu:
  Fix Released

Bug description:
  When I run an apt-get update, at the end of the update it outputs that the 
screencloud ppa from commercial-ppa-uploaders failed.
  The screencloud ppa is added when you install "screencloud" from the Ubuntu 
Software Center.
  Output:

  W: Failed to fetch https://private-ppa.launchpad.net/commercial-ppa-
  uploaders/screencloud/ubuntu/dists/precise/main/binary-i386/Packages
  The requested URL returned error: 401

  E: Some index files failed to download. They have been ignored, or old
  ones used instead.

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

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

[Desktop-packages] [Bug 902698] Re: lightdm crashed with SIGSEGV in check_stopped()

[Rich Hart]

Both this and GDM are crashing on my system.It started after I tried
the latest graphic driver #876499.I have X working again, but
neither graphic login package will run.

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

Title:
  lightdm crashed with SIGSEGV in check_stopped()

Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged

Bug description:
  Bug last reported on 2011/9/14 with "Fix Released" stated but seems to
  have happened again in 12.04 alpha

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.0.6-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Dec 11 11:25:45 2011
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: lightdm
  ProcEnviron: PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x411138:  mov0x28(%rax),%ecx
   PC (0x00411138) ok
   source "0x28(%rax)" (0xaad2) not located in a known VMA region 
(needed readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to precise on 2011-12-04 (6 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 986107] [NEW] keyboard arrow keys up/down does not work

[rich]

Public bug reported:

not possible without a mouse to change the window manager

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm 1.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
Date: Fri Apr 20 12:57:21 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100913)
SourcePackage: lightdm
UpgradeStatus: Upgraded to precise on 2012-03-21 (30 days ago)

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


** Tags: apport-bug i386 precise

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

Title:
  keyboard arrow keys up/down does not work

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  not possible without a mouse to change the window manager

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  Date: Fri Apr 20 12:57:21 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100913)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-21 (30 days ago)

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

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

[Desktop-packages] [Bug 986107] Re: keyboard arrow keys up/down does not work

[rich]

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

Title:
  keyboard arrow keys up/down does not work

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  not possible without a mouse to change the window manager

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  Date: Fri Apr 20 12:57:21 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100913)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-21 (30 days ago)

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

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

[Desktop-packages] [Bug 975414] Re: lightdm failed to run

[rich]

/var/log/Xorg.0.log

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/975414/+attachment/3021319/+files/Xorg.0.log

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

Title:
  lightdm failed to run

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  On my netbook dell inspiron 1501 lightdm failed to run.
  I see the message 
  "The system is running in low-graphics mode"
  The next step is proposed 
  - run in low-graphics mode for just one session
  - reconfigure graphics
  - trubleshoot the error
  - Exit to console login
  but all options are returned to me  to console login.

  If i`m use 
  exec gnome-session or exec gnome-shell in .xinitrc and run startx in tty1 
graphical environment is started successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Fri Apr  6 22:41:39 2012
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-30 (6 days ago)

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

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

[Desktop-packages] [Bug 975414] Re: lightdm failed to run

[rich]

lspci -v

** Attachment added: "lspci-v"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/975414/+attachment/3021307/+files/lspci-v

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

Title:
  lightdm failed to run

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  On my netbook dell inspiron 1501 lightdm failed to run.
  I see the message 
  "The system is running in low-graphics mode"
  The next step is proposed 
  - run in low-graphics mode for just one session
  - reconfigure graphics
  - trubleshoot the error
  - Exit to console login
  but all options are returned to me  to console login.

  If i`m use 
  exec gnome-session or exec gnome-shell in .xinitrc and run startx in tty1 
graphical environment is started successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Fri Apr  6 22:41:39 2012
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-30 (6 days ago)

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

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

[Desktop-packages] [Bug 975414] Re: lightdm failed to run

[rich]

Files in /var/log/lightdm/

** Attachment added: "var-log-lightdm.tar"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/975414/+attachment/3021292/+files/var-log-lightdm.tar

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

Title:
  lightdm failed to run

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  On my netbook dell inspiron 1501 lightdm failed to run.
  I see the message 
  "The system is running in low-graphics mode"
  The next step is proposed 
  - run in low-graphics mode for just one session
  - reconfigure graphics
  - trubleshoot the error
  - Exit to console login
  but all options are returned to me  to console login.

  If i`m use 
  exec gnome-session or exec gnome-shell in .xinitrc and run startx in tty1 
graphical environment is started successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Fri Apr  6 22:41:39 2012
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-30 (6 days ago)

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

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

[Desktop-packages] [Bug 975414] Re: lightdm failed to run

[rich]

** Attachment added: "IMG_0108.JPG"
   
https://bugs.launchpad.net/bugs/975414/+attachment/3017999/+files/IMG_0108.JPG

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

Title:
  lightdm failed to run

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  On my netbook dell inspiron 1501 lightdm failed to run.
  I see the message 
  "The system is running in low-graphics mode"
  The next step is proposed 
  - run in low-graphics mode for just one session
  - reconfigure graphics
  - trubleshoot the error
  - Exit to console login
  but all options are returned to me  to console login.

  If i`m use 
  exec gnome-session or exec gnome-shell in .xinitrc and run startx in tty1 
graphical environment is started successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Fri Apr  6 22:41:39 2012
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-30 (6 days ago)

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

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

[Desktop-packages] [Bug 975414] [NEW] lightdm failed to run

[rich]

Public bug reported:

On my netbook dell inspiron 1501 lightdm failed to run.
I see the message 
"The system is running in low-graphics mode"
The next step is proposed 
- run in low-graphics mode for just one session
- reconfigure graphics
- trubleshoot the error
- Exit to console login
but all options are returned to me  to console login.

If i`m use 
exec gnome-session or exec gnome-shell in .xinitrc and run startx in tty1 
graphical environment is started successfully.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm (not installed)
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Fri Apr  6 22:41:39 2012
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to precise on 2012-03-30 (6 days ago)

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


** Tags: amd64 apport-bug precise

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

Title:
  lightdm failed to run

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  On my netbook dell inspiron 1501 lightdm failed to run.
  I see the message 
  "The system is running in low-graphics mode"
  The next step is proposed 
  - run in low-graphics mode for just one session
  - reconfigure graphics
  - trubleshoot the error
  - Exit to console login
  but all options are returned to me  to console login.

  If i`m use 
  exec gnome-session or exec gnome-shell in .xinitrc and run startx in tty1 
graphical environment is started successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Fri Apr  6 22:41:39 2012
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to precise on 2012-03-30 (6 days ago)

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

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

[Desktop-packages] [Bug 899830] [NEW] I can not reboot or shut down computer

[rich]

Public bug reported:

 I can not restart or shut down computer from lightdm login screen when
are logged in tty1.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 1.0.6-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sun Dec  4 12:02:18 2011
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to oneiric on 2011-12-01 (2 days ago)

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


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  I can not reboot or shut down computer

Status in “lightdm” package in Ubuntu:
  New

Bug description:
   I can not restart or shut down computer from lightdm login screen
  when are logged in tty1.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 1.0.6-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Dec  4 12:02:18 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-12-01 (2 days ago)

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

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

[Desktop-packages] [Bug 899830] Re: I can not reboot or shut down computer

[rich]

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

Title:
  I can not reboot or shut down computer

Status in “lightdm” package in Ubuntu:
  New

Bug description:
   I can not restart or shut down computer from lightdm login screen
  when are logged in tty1.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 1.0.6-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Dec  4 12:02:18 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-12-01 (2 days ago)

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

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

[Desktop-packages] [Bug 877684] Re: in the terminal is not typed commands

[rich]

Case closed.
I` recreate my home dir and its fixed.

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

Title:
  in the terminal is not typed commands

Status in “gnome-terminal” package in Ubuntu:
  New

Bug description:
  after the transition to tty1 or exit from sleep mode in the terminal
  is not typed commands and Duplicated characters when entering see
  attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 18 23:21:28 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (51 days ago)

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

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

[Desktop-packages] [Bug 848128] Re: metacity does not start after login

[rich]

Case closed.
I` recreate my home dir and its fixed.

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

Title:
  metacity does not start after login

Status in “metacity” package in Ubuntu:
  New

Bug description:
  Metacity does not start after login.

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=11.10
  DISTRIB_CODENAME=oneiric
  DISTRIB_DESCRIPTION="Ubuntu oneiric (development branch)"

  cat ~/.gconf/desktop/gnome/applications/window_manager/%gconf.xml
  
  

metacity


/usr/bin/metacity

  

  cat ~/.gconf/desktop/gnome/session/required_components/%gconf.xml
  
  

gnome-panel


metacity

  

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: metacity 1:2.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Mon Sep 12 21:52:50 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: metacity
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (15 days ago)

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

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

[Desktop-packages] [Bug 848128] Re: metacity does not start after login

[rich]

problem persists after the release :(

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

Title:
  metacity does not start after login

Status in “metacity” package in Ubuntu:
  New

Bug description:
  Metacity does not start after login.

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=11.10
  DISTRIB_CODENAME=oneiric
  DISTRIB_DESCRIPTION="Ubuntu oneiric (development branch)"

  cat ~/.gconf/desktop/gnome/applications/window_manager/%gconf.xml
  
  

metacity


/usr/bin/metacity

  

  cat ~/.gconf/desktop/gnome/session/required_components/%gconf.xml
  
  

gnome-panel


metacity

  

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: metacity 1:2.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Mon Sep 12 21:52:50 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: metacity
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (15 days ago)

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

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

[Desktop-packages] [Bug 877684] Re: in the terminal is not typed commands

[rich]

** Attachment added: "Duplicated characters when entering"
   
https://bugs.launchpad.net/bugs/877684/+attachment/2558271/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA-2011-10-18%2023%3A28%3A32.png

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

Title:
  in the terminal is not typed commands

Status in “gnome-terminal” package in Ubuntu:
  New

Bug description:
  after the transition to tty1 or exit from sleep mode in the terminal
  is not typed commands and Duplicated characters when entering see
  attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 18 23:21:28 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (51 days ago)

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

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

[Desktop-packages] [Bug 877684] [NEW] in the terminal is not typed commands

[rich]

Public bug reported:

after the transition to tty1 or exit from sleep mode in the terminal is
not typed commands and Duplicated characters when entering see
attachment

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-terminal 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Tue Oct 18 23:21:28 2011
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to oneiric on 2011-08-28 (51 days ago)

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


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  in the terminal is not typed commands

Status in “gnome-terminal” package in Ubuntu:
  New

Bug description:
  after the transition to tty1 or exit from sleep mode in the terminal
  is not typed commands and Duplicated characters when entering see
  attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 18 23:21:28 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (51 days ago)

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

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

[Desktop-packages] [Bug 875267] Re: Initializing nautilus-gdu extension failed

[rich]

Yes, fixed.

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

Title:
  Initializing nautilus-gdu extension failed

Status in “nautilus” package in Ubuntu:
  Invalid

Bug description:
  nautilus-open-terminal extension
  ** (nautilus:6898): DEBUG: SyncDaemon already running, initializing 
SyncdaemonDaemon object

  (nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion
  `GTK_IS_ACTION (action)' failed

  (nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
  ^C
  [1]+  Ошибка сегментирования   nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 15 23:52:38 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (48 days ago)

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

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

[Desktop-packages] [Bug 836250] Re: [Oneiric] Intel Corporation Centrino Ultimate-N 6300 poor networking, packet loss and very slow Lenovo X201 and T500 laptops

[Rich R]

I'm getting this too. Intel Centrino Wireless-N 1000 on a Lenovo E420s.
Was fine under Natty. Frustratingly slow connection under Oneiric.
I can't easily get access to the router. Is there a corresponding work-around 
for this card?

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

Title:
  [Oneiric] Intel Corporation Centrino Ultimate-N 6300 poor networking,
  packet loss and very slow Lenovo X201 and T500 laptops

Status in “linux” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “linux” source package in Oneiric:
  Confirmed
Status in “network-manager” source package in Oneiric:
  Confirmed
Status in “linux” source package in Precise:
  Confirmed
Status in “network-manager” source package in Precise:
  Confirmed

Bug description:
  This may be either network-manager or kernel, depending on triage...

  I have verified this on both a Lenovo X201 and a Lenovo T500 laptop.

  Both work perfectly with fully updated 10.10 and 11.04 versions of
  Ubuntu.

  However, booting into a fully updated 11.10 (as of 28/08/11) I get
  very poor wireless networking performance. Between 6-10% packet loss,
  very very slow connection and transfer rate. All in all, practically
  unusable.

  I have reported the bug on the X201 laptop, I will add the similar
  logs from the T500 also if required.

  As soon as I swap back to either 10.10 or 11.04 I get perfect
  wireless, it's only on 11.10 that I get problems, this would suggest
  it's not hardware or configuration on my side.

  I have had this since first installing 11.10 which was a little after
  Alpha 2.

  Wired connection is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.9.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Aug 28 21:26:05 2011
  EcryptfsInUse: Yes
  Gconf:
   
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  IpRoute:
   default via 192.168.100.1 dev eth0  proto static 
   192.168.100.0/24 dev eth0  proto kernel  scope link  src 192.168.100.41
  Keyfiles: Error: [Errno 2] No such file or directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 875267] Re: Initializing nautilus-gdu extension failed

[rich]

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

Title:
  Initializing nautilus-gdu extension failed

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  nautilus-open-terminal extension
  ** (nautilus:6898): DEBUG: SyncDaemon already running, initializing 
SyncdaemonDaemon object

  (nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion
  `GTK_IS_ACTION (action)' failed

  (nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
  ^C
  [1]+  Ошибка сегментирования   nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 15 23:52:38 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (48 days ago)

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

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

[Desktop-packages] [Bug 875267] [NEW] Initializing nautilus-gdu extension failed

[rich]

Public bug reported:

nautilus-open-terminal extension
** (nautilus:6898): DEBUG: SyncDaemon already running, initializing 
SyncdaemonDaemon object

(nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion
`GTK_IS_ACTION (action)' failed

(nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
^C
[1]+  Ошибка сегментирования   nautilus

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Sat Oct 15 23:52:38 2011
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to oneiric on 2011-08-28 (48 days ago)

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


** Tags: amd64 apport-bug oneiric

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

Title:
  Initializing nautilus-gdu extension failed

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  nautilus-open-terminal extension
  ** (nautilus:6898): DEBUG: SyncDaemon already running, initializing 
SyncdaemonDaemon object

  (nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion
  `GTK_IS_ACTION (action)' failed

  (nautilus:6898): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
  ^C
  [1]+  Ошибка сегментирования   nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 15 23:52:38 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (48 days ago)

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

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

[Desktop-packages] [Bug 872139] Re: Banshee hangs if computer is offline

[Rich]

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

** This bug has been marked a duplicate of bug 871068
   Banshee (ubuntu one music store) crashes when not connected to the internet

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

Title:
  Banshee hangs if computer is offline

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Starting banshee either from unity or the command line causes it to
  hang. Only way to kill the process is to switch to another terminal
  _screen_ (ie CTRL+ALT+F1) and kill the PID from there. I'm 99% sure
  this was the first time that banshee had been run.

  Running in terminal gives a stack trace, attached.

  Release:
  Description:  Ubuntu 11.10
  Release:  11.10

  Version of Banshee:
  banshee:
Installed: 2.2.0-1ubuntu2
Candidate: 2.2.0-1ubuntu2
Version table:
   *** 2.2.0-1ubuntu2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  Expected:
  Banshee to not hang

  What happened instead:
  banshee hung, had to kill it using kill

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

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

[Desktop-packages] [Bug 872139] Re: Banshee hangs if computer is offline

[Rich]

By the way, this is when the computer is offline - I am finally online
and I have run Banshee again and it didn't hang.

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

Title:
  Banshee hangs if computer is offline

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Starting banshee either from unity or the command line causes it to
  hang. Only way to kill the process is to switch to another terminal
  _screen_ (ie CTRL+ALT+F1) and kill the PID from there. I'm 99% sure
  this was the first time that banshee had been run.

  Running in terminal gives a stack trace, attached.

  Release:
  Description:  Ubuntu 11.10
  Release:  11.10

  Version of Banshee:
  banshee:
Installed: 2.2.0-1ubuntu2
Candidate: 2.2.0-1ubuntu2
Version table:
   *** 2.2.0-1ubuntu2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  Expected:
  Banshee to not hang

  What happened instead:
  banshee hung, had to kill it using kill

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

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

[Desktop-packages] [Bug 872139] [NEW] Banshee hangs if computer is offline

[Rich]

Public bug reported:

Starting banshee either from unity or the command line causes it to
hang. Only way to kill the process is to switch to another terminal
_screen_ (ie CTRL+ALT+F1) and kill the PID from there. I'm 99% sure this
was the first time that banshee had been run.

Running in terminal gives a stack trace, attached.

Release:
Description:Ubuntu 11.10
Release:11.10

Version of Banshee:
banshee:
  Installed: 2.2.0-1ubuntu2
  Candidate: 2.2.0-1ubuntu2
  Version table:
 *** 2.2.0-1ubuntu2 0
500 http://fr.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
100 /var/lib/dpkg/status

Expected:
Banshee to not hang

What happened instead:
banshee hung, had to kill it using kill

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


** Tags: banshee hang

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

Title:
  Banshee hangs if computer is offline

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Starting banshee either from unity or the command line causes it to
  hang. Only way to kill the process is to switch to another terminal
  _screen_ (ie CTRL+ALT+F1) and kill the PID from there. I'm 99% sure
  this was the first time that banshee had been run.

  Running in terminal gives a stack trace, attached.

  Release:
  Description:  Ubuntu 11.10
  Release:  11.10

  Version of Banshee:
  banshee:
Installed: 2.2.0-1ubuntu2
Candidate: 2.2.0-1ubuntu2
Version table:
   *** 2.2.0-1ubuntu2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
  100 /var/lib/dpkg/status

  Expected:
  Banshee to not hang

  What happened instead:
  banshee hung, had to kill it using kill

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

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