date:20220212

[Desktop-packages] [Bug 1955044] Re: [SRU] /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token (with GCC 11 in C++20 mode)

2022-02-12 Thread Jeremy Bicha

** Changed in: glibmm2.4 (Ubuntu)
   Status: New => Fix Released

** Also affects: glibmm2.4 (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Changed in: glibmm2.4 (Ubuntu Impish)
   Status: New => Triaged

** Description changed:

- There are compilation errors when I try to include the  header 
under C++20 and run default compiler, GCC 11.
- This is reproducible in Ubuntu 21.10 (Impish Indri) or Ubuntu devel (Jammy 
Jellyfish) but not in Ubuntu 21.04 (Impish Indri) or Debian unstable. And this 
is effecting building of the telegram-desktop package.
+ Impact
+ ==
+ It's not possible to build using the  header under C++20 with the 
default compiler, GCC 11. This is interfering with being able to build 
telegram-desktop.
  
- mymedia@barberry:~$ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int 
main(){}' `pkg-config --cflags --libs glibmm-2.4` -o /dev/null
+ This was fixed for Ubuntu 22.04 LTS with 2.66.1
+ 
+ Demonstration of the Issue
+ ==
+ $ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int main(){}' `pkg-config 
--cflags --libs glibmm-2.4` -o /dev/null
  In file included from 
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
   from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
   from /usr/include/glibmm-2.4/glibmm.h:92,
   from :
  /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected 
unqualified-id before ‘)’ token
    956 |   Variant();
    |^
  /usr/include/glibmm-2.4/glibmm/variant.h:1017:25: error: expected 
unqualified-id before ‘)’ token
   1017 |   Variant< Variant >();
    | ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1070:26: error: expected 
unqualified-id before ‘)’ token
   1070 |   Variant();
    |  ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1240:24: error: expected 
unqualified-id before ‘)’ token
   1240 |   Variant();
    |^
  /usr/include/glibmm-2.4/glibmm/variant.h:1286:30: error: expected 
unqualified-id before ‘)’ token
   1286 |   Variant< std::pair >()
    |  ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1335:29: error: expected 
unqualified-id before ‘)’ token
   1335 |   Variant< std::vector >()
    | ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1404:41: error: expected 
unqualified-id before ‘)’ token
   1404 |   Variant< std::vector >();
    | ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1530:39: error: expected 
unqualified-id before ‘)’ token
   1530 |   Variant< std::vector >();
    |   ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1606:29: error: expected 
unqualified-id before ‘)’ token
   1606 |   Variant< std::map >()
    | ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1679:33: error: expected 
unqualified-id before ‘)’ token
   1679 |   Variant>()
    | ^
  In file included from /usr/include/glibmm-2.4/glibmm/variant.h:1742,
   from 
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
   from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
   from /usr/include/glibmm-2.4/glibmm.h:92,
   from :
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:23:17: error: expected 
unqualified-id before ‘)’ token
     23 |   Variant()
    | ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:66:26: error: expected 
unqualified-id before ‘)’ token
     66 |   Variant()
    |  ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:109:19: error: expected 
unqualified-id before ‘)’ token
    109 |   Variant()
    |   ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:152:20: error: expected 
unqualified-id before ‘)’ token
    152 |   Variant()
    |^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:195:19: error: expected 
unqualified-id before ‘)’ token
    195 |   Variant()
    |   ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:244:20: error: expected 
unqualified-id before ‘)’ token
    244 |   Variant()
    |^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:287:19: error: expected 
unqualified-id before ‘)’ token
    287 |   Variant()
    |   ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:330:20: error: expected 
unqualified-id before ‘)’ token
    330 |   Variant()
    |^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:373:19: error: expected 
unqualified-id before ‘)’ token
    373 |   Variant()
    |   ^
  In file included from 
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,

[Desktop-packages] [Bug 1875744] Re: xdg-user-dir does for root does not return the locale names of the directories

2022-02-12 Thread Launchpad Bug Tracker

[Expired for xdg-user-dirs (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: xdg-user-dirs (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  xdg-user-dir does for root does not return the locale names of the
  directories

Status in xdg-user-dirs package in Ubuntu:
  Expired

Bug description:
  When upgrading from Ubuntu 18.04 to 20.04, the root user does not
  receive the file ~/.config/user-dirs.dirs and thus the locale names
  are not translated.

  Example:

  $ sudo bash
  [sudo] password for gga:

  # xdg-user-dir DESKTOP
  /root/Desktop

  With the proper (Spanish) .config/user-dirs.dirs:

  $ sudo bash
  [sudo] password for gga:

  # xdg-user-dir DESKTOP
  /root/Escritorio

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:09:45 2020
  InstallationDate: Installed on 2020-04-25 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-04-27 (1 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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

[Desktop-packages] [Bug 1954569] Re: unable to open/start the transmission app

2022-02-12 Thread Launchpad Bug Tracker

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

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

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

Title:
  unable to open/start the transmission app

Status in transmission package in Ubuntu:
  Expired

Bug description:
  on clicking open the app does not open

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: transmission-gtk 3.00-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 12 01:04:02 2021
  InstallationDate: Installed on 2021-07-25 (139 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/usr/bin/zsh
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: transmission
  UpgradeStatus: Upgraded to impish on 2021-12-11 (0 days ago)

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


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

[Desktop-packages] [Bug 1958019]

2022-02-12 Thread info

(In reply to darnellkeithj from comment #375)
> Thought i'd reinstall linux to see if there were any changes with this Yoga
> Duet 7i. Still no sound with the newer kernels but 5.4.88-1-lts with Arch
> "Arco"linux does works every time. Microphone does not work. Why it works in
> 5.488-1-lts and not newer is beyond me. Why devs haven't compared the two
> and fixed it is also puzzling.

Hi all,

New Lenovo Yoga Duet 7 13IML05 (2020) user here. The Duet 7 is a really
nice, light and compact 13-inch tablet, ideal for triple-booting
Windows, Linux and macOS. The only issue currently with this device is
getting the ALC287 sound chip to work in Linux and macOS.

I confirm darnellkeithj's findings that the sound output (speakers and
headphones) works out of the box with the Arch kernel up to and
including 5.4.88-1-lts. I'm actually using Manjaro Linux for testing,
which allows installing several kernels and switching easily between
them. Older Arch kernels may be downloaded from the Arch Linux Archive
at https://archive.archlinux.org/packages/l/linux-lts/ and
https://archive.archlinux.org/packages/l/linux/.

Kernel 5.4.89 breaks sound output on the Yoga Duet 7 because of the following
commit:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/releases/5.4.89/alsa-hda-realtek-fix-speaker-volume-control-on-lenovo-c940.patch?id=1889f9ac9f9eb7f91ffc22e607a2e3db3db2e72e
For some odd reason, the Lenovo Yoga C940 seems to be using the same audio
subsystem ID 0x17aa, 0x3818 as the Yoga Duet 7, so any quirk applied to the
C940 will apply to the Duet 7 as well, even if it is not required. Reverting
this commit fixes the sound output for kernels up to and including
5.4.98-1-lts. Kernels 5.x break sound output again, even with this commit
reverted... So this is not an optimal approach.

However, I found an easy way for fixing the sound output (speakers and
headphones) on the Yoga Duet 7. The cool thing is that it doesn't require
compiling a custom kernel. Sadly, the fix works only for kernels up to and
including 5.10.1.
Simply disable the snd-sof-pci driver and force the use of the legacy
snd-hda-intel driver by adding the following two lines to
/etc/modprobe.d/alsa-base.conf
"blacklist snd-sof-pci"
"options snd-intel-dspcfg dsp_driver=1"

With both solutions, the digital microphone won't work at all, as it requires
the SOF firmware.
The mic is detected and works perfectly on newer kernels (> 5.9.x) when using
the SOF firmware. The headphones work as well, only the speakers won't emit any
sound.

Basically, you have to choose between having a mic or having a speaker.
No microphone is fine for me and kernel 5.10.1 is quite modern, so I could live
with the situation for the time being.

I'll play around with the Realtek verbs in the next few days to find a
real solution, as the above fixes are dead ends.

I'd be very glad to receive some input from the other Yoga Duet 7
owners.

Cheers for now!

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

Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
sound at all

Status in sound-2.6 (alsa-kernel):
Confirmed
Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
internal speakers, but it work by headphones connected to standard
jack aux.

uname -r
5.11.0-44-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: i3draven 1266 F pulseaudio
/dev/snd/controlC0: i3draven 1266 F pulseaudio
/dev/snd/controlC1: i3draven 1266 F pulseaudio
/dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 15 15:10:53 2022
InstallationDate: Installed on 2021-10-11 (96 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio
Generic
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: i3draven 1266 F pulseaudio
/dev/snd/controlC0: i3draven 1266 F pulseaudio
/dev/snd/controlC1: i3draven 1266 F pulseaudio
/dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [82N6, Realtek ALC287, Speaker, Internal] No sound

[Desktop-packages] [Bug 1958813] Re: [snap] I have on clean install some weird folder /home/user/Downloads/firefox.tmp/

2022-02-12 Thread Bug Watch Updater

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1733750.

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

On 2021-10-02T04:43:17+00:00 Douglas Silva wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:92.0) Gecko/20100101
Firefox/92.0

Steps to reproduce:

1. Install Ubuntu 21.10 (impish). It ships with Firefox installed as a Snap 
that is maintained by Mozilla.
2. Check the ~/Downloads directory, it should be empty
3. Run Firefox.
4. Check the ~/Downloads directory, it should now have an empty directory named 
"firefox.tmp".

Actual results:

An empty directory is being created at ~/Downloads and I believe this is
not the intended behavior. The directory never goes away, it just stays
there. If you delete it, it will be recreated when you run Firefox
again.

Expected results:

It shouldn't create temporary files in my Downloads directory.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1958813/comments/0

On 2021-10-02T05:17:38+00:00 Release-mgmt-account-bot wrote:

The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug
should belong to the 'Core::Widget: Gtk' component, and is moving the
bug to that component. Please revert this change in case you think the
bot is wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1958813/comments/1

On 2021-10-22T15:13:36+00:00 Sygczsjy wrote:

User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101
Firefox/91.0

I have observed the same problem. Ubuntu 21.10, default installed
Firefox, Snap version 93.0 according to About Firefox.

If the user deletes the directory ~/Downloads/firefox.tmp/ while Firefox
is running, Firefox may recreate it at a later point. In some cases the
directory is empty. In other cases, it contains temporary files.

My best guess is that it has to do with a change noted in [this
thread](https://forum.snapcraft.io/t/xdg-open-not-working-on-
firefox/17670/14):

> There’s no `mimeapps.list` file any more, and the `snapcraft.yaml` now sets 
> `GTK_USE_PORTAL=1` in the environment. This causes the GLib APIs to ask 
> `xdg-desktop-portal` to open any files it can’t otherwise find a handler for.
>
> The other change in tip is to set `$TMPDIR` to somewhere other than `/tmp` 
> (specifically, it sets it to `~/Downloads/firefox.tmp`). When Firefox tries 
> to open a file of a type it doesn’t understand, it downloads and saves a copy 
> of it to the temp files directory, and then tries to open that file with its 
> associated handler. This is a problem for snaps, since `/tmp` inside the 
> sandbox is different to `/tmp` outside of the sandbox. Using a different 
> location allows the file to be passed to the helper outside the sandbox.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1958813/comments/2

On 2021-10-22T15:18:35+00:00 Olivier Tilloy wrote:

This is actually intended: it was added in
https://hg.mozilla.org/mozilla-central/rev/015f42782c5e, to ensure that
other snaps can open files downloaded by firefox. See
https://forum.snapcraft.io/t/sharing-files-via-tmp/1613 for details.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1958813/comments/3

On 2021-10-22T15:36:15+00:00 Olivier Tilloy wrote:

And with https://git.launchpad.net/~mozilla-snaps/+git/firefox-
snap/commit/?id=f7022494b8d02835617be47226cd55d455ee84fd I moved the
workaround and added a comment to make the intent clearer.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1958813/comments/4

On 2021-10-22T21:55:48+00:00 Sygczsjy wrote:

"Downloads" seems like an inelegant place for the firefox tmp dir.
Downloads is normally the directory for files the user downloads,
whereas software usually stores its temporary files in a hidden
directory like `.cache` or `.local/share/`. The effect is that the
user's Downloads directory is intruded upon by the seemingly random
files like a `mesa_shader_cache` directory. Perhaps the firefox
temporary directory could be placed in a less obtrusive location.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1958813/comments/5

On 2021-10-25T15:36:56+00:00 Olivier Tilloy wrote:

Of interest, is bug 1710926 : if I set
`browser.download.improvements_to_download_panel` to `true`, then files
are

[Desktop-packages] [Bug 1515446] Re: network file systems in FSTAB no longer mount at boot with NetworkManager

2022-02-12 Thread Bug Watch Updater

** Changed in: network-manager (Debian)
   Status: New => Fix Released

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

Title:
  network file systems in FSTAB no longer mount at boot with
  NetworkManager

Status in One Hundred Papercuts:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Wily:
  Fix Released
Status in network-manager package in Debian:
  Fix Released

Bug description:
  [Impact]

   * This breaks NFS mounts coming up reliably.  In some cases this can
  be quite intermittent.

  [Test Case]

   1. Add a mountpoint to an NFS share by name to fstab.
   2. See that it mounts with the mount command.
   3. Reboot 5+ times, note that it doesn't come up all (or the majority of the 
time).  

  [Regression Potential]

   * There could be a regression for the same reason it's blocked in
  Debian, because of dependency issues with packages not converted to
  systemd that want to run /etc/rcS.d/.

  You can check for this by looking for breaking/disable services during
  bootup.  Ubuntu is in a much better state than Debian, but there is a
  possibility we missed something.

  Otherwise, this will increase boot time, but when the user logs the
  networking will be more likely to be ready.

  
  -Previous description-
  After a fresh install of 15.10, nfs shares no longer mount on boot.   I'm 
using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
    Installed: 1:1.2.8-9ubuntu10
    Candidate: 1:1.2.8-9ubuntu10
    Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
     Loaded: loaded (/etc/fstab)
     Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
     man:systemd-fstab-generator(8)
    Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

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


-- 
Mailing list: https://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 1498058] Re: Display freezes

2022-02-12 Thread Ervin Bolat

I don't even have that system anymore. Sorry.

On Sat, Feb 12, 2022, 19:15 Paul White  <1498...@bugs.launchpad.net>
wrote:

> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
>
> Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
>
> Do you still see a problem related to the one that you reported when
> using a currently supported version of Ubuntu? Please let us know if you
> do otherwise this report can be left to expire in approximately 60 days
> time.
>
> Thank you for helping make Ubuntu better.
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1498058
>
> Title:
>   Display freezes
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Display freezes with the following repeating:
>   Sep 21 18:06:40 ervin-Lenovo-G550 kernel: [ 2589.417953] nouveau E[
> PGRAPH][:01:00.0] TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 07e6c0
> warp 29, opcode ffe7f2f6 ffe7f2f6
>   Sep 21 18:06:40 ervin-Lenovo-G550 kernel: [ 2589.417975] nouveau E[
> PGRAPH][:01:00.0] TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 07e6c0
> warp 28, opcode ffe7f2f6 ffe7f2f6
>   Sep 21 18:06:40 ervin-Lenovo-G550 kernel: [ 2589.417981] nouveau E[
> PGRAPH][:01:00.0] ch 7 [0x001f7e chrome[2686]] subc 3 class 0x8597
> mthd 0x1b0c data 0x1000f010
>
>   WORKAROUND: Use proprietary nvidia drivers.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: xorg 1:7.7+1ubuntu8.1
>   ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
>   Uname: Linux 3.19.0-28-generic x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.14.1-0ubuntu3.13
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Mon Sep 21 18:22:09 2015
>   DistUpgraded: Fresh install
>   DistroCodename: trusty
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GpuHangFrequency: Very infrequently
>   GraphicsCard:
>NVIDIA Corporation GT218M [GeForce G210M] [10de:0a74] (rev a2) (prog-if
> 00 [VGA controller])
>  Subsystem: Lenovo Device [17aa:389f]
>   InstallationDate: Installed on 2015-09-17 (3 days ago)
>   InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64
> (20150805)
>   MachineType: LENOVO 20023
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/21/2010
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 18CN46WW(V2.55)
>   dmi.board.name: NITU1
>   dmi.board.vendor: LENOVO
>   dmi.board.version: REFERENCE
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: No Enclosure
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnLENOVO:bvr18CN46WW(V2.55):bd05/21/2010:svnLENOVO:pn20023:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
>   dmi.product.name: 20023
>   dmi.product.version: Lenovo G550
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri N/A
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core N/A
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>   xserver.bootTime: Mon Sep 21 18:10:56 2015
>   xserver.configfile: default
>   xserver.errors:
>Failed to load module "nvidia" (module does not exist, 0)
>Failed to load module "nvidia" (module does not exist, 0)
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.17.1-0ubuntu3~trusty1
>   xserver.video_driver: nouveau
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1498058/+subscriptions
>
>

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

Title:
  Display freezes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Display freezes with the following

74 matches

Mail list logo