[Desktop-packages] [Bug 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standar

2019-06-03 Thread giannione
Same problem on 18.10. Every app crashes after powersave or what else it
is doing, and the I have to login again in a new session.

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

Title:
  Some code accessed the property 'discreteGpuAvailable' on the module
  'appDisplay'. | This was previously supported, but is not correct
  according to the ES6 standard.

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  On-boot message in the log:

  окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the
  property 'discreteGpuAvailable' on the module 'appDisplay'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6
  standard. Any symbols to be exported from a module must be defined
  with 'var'. The property access will work as previously for the time
  being, but please fix your code anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 02:05:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-02-27 (229 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

2019-06-03 Thread giannione
Same problem on ubuntu 18.10. Everything crashes when the screen timouts
or goes in powersaving who knows. Every app closes and I have to login
again.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect:
  Connection refused

  then:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+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 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta

2019-05-13 Thread giannione
*** This bug is a duplicate of bug 1717170 ***
https://bugs.launchpad.net/bugs/1717170

Idem here, 18.10, every app crashes - including the gnome session -
after the screen goes blank into powersaving.

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

Title:
  Screen blanking and/or screen lock crashes gnome-shell user session on
  wayland - Ubuntu 17.10 beta

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Filed against Xorg due to selection limitations of apport. Mutter is
  the best guess of responsible application/package.

  Automatic (timed) screen blanking (or manually locking the desktop)
  causes the wayland gnome-shell session to crash and drop to user login
  prompt. The monitor fades the background to black (but oddly the mouse
  cursor does not fade). The monitor blanks and goes into signal search
  and then power saving mode. Almost immediately the monitor switches
  back on, displaying the login prompt (note login and not unlock as
  would be expected). Thereafter the screen stays on indefinitely
  without further attempts to blank or power-save.

  Ubuntu artful 17.10 beta. Dell monitor at 1920x1080x60hz using hdmi
  connected to nvidia card with nouveau drivers on wayland session. Xorg
  session seems to work as expected.

  /var/crash is empty and manually running Apport and reproducing crash
  does not produce a crash report, as Apport crashes with the user
  session. Have included Apport output, though I had to select xorg from
  limited options in app and this is clearly technically incorrect (xorg
  session works fine).

  Have attached an exported log file of screen blanking causing the
  crash. Blanking probably starts at about the 16:04:22 entry, and the
  actual crash seems to happen at 16:04:35.

  ...
  16:04:35 gnome-session-b: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 6
  16:04:35 gnome-shell: Fatal server error:
  16:04:35 update-notifier: Error reading events from display: Broken pipe
  16:04:35 gnome-shell: 
mutter:ERROR:backends/meta-monitor-manager.c:2267:meta_monitor_manager_get_logical_monitor_from_number:
 assertion failed: ((unsigned int) number < g_list_length 
(manager->logical_monitors))
  16:04:28 gnome-software: no app for changed ubuntu-appindicat...@ubuntu.com
  16:04:22 gnome-shell: Some code accessed the property 'Client' on the module 
'dbusMenu'. That property was defined with 'let' or 'const' inside the module. 
This was previously supported, but is not correct according to the ES6 
standard. Any symbols to be exported from a module must be defined with 'var'. 
The property access will work as previously for the time being, but please fix 
your code anyway.
  ...

  Crash of gnome-shell can be avoided by changing "Settings - Power -
  Power Savings - Blank screen" to "never", and never attempting to lock
  the desktop. Alternatively logging in to a Xorg session seems to avoid
  crashes.

  Bug may be related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721577 but
  circumstances leading to crash are completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 17:47:51 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:84f5]
  InstallationDate: Installed on 2017-10-08 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: PINNACLE MICRO PROLINE DQ57TM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=805df197-93bb-4468-8ac9-c1611d91bbbf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TMIBX10H.86A.0050.2011.1207.1134
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DQ57TM
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70931-402
  dmi.chassis.type: 3
  dmi.chassis.version: UATX
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTMIBX10H.86A.0050.2011.1207.1134:bd12/07/2011:svnPINNACLEMICRO:pnPROLINEDQ57TM:pvr:rvnIntelCorporation:rnDQ57TM:rvrAAE70931-402:cvn:ct3:cvrUATX:
  dmi.product.name: PROLINE DQ57TM
  dmi.sys.vendor: PINNACLE MICRO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  

[Desktop-packages] [Bug 1790100] Re: unable to write ~ and ^ chars in the terminal

2019-05-11 Thread giannione
still can't type ^
... :-(

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] ProcCpuinfoMinimal.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213544/+files/ProcCpuinfoMinimal.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-16 Thread giannione
hello, I run that command
"ubuntu-bug -u 1790100"

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] ProcEnviron.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213545/+files/ProcEnviron.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] apport information

2018-11-16 Thread giannione
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-10-25 (387 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Tags:  bionic wayland-session
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-10-13 (34 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] Dependencies.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213543/+files/Dependencies.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-16 Thread giannione
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-10-25 (387 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Tags:  bionic wayland-session
Uname: Linux 4.15.0-38-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-10-13 (34 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True


** Tags added: apport-collected bionic

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] ProcCpuinfoMinimal.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213547/+files/ProcCpuinfoMinimal.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] Dependencies.txt

2018-11-16 Thread giannione
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1790100/+attachment/5213546/+files/Dependencies.txt

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+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 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-07 Thread giannione
synaptic works
remmina works

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+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 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-07 Thread giannione
gedit works

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+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 1716056] Re: Multiple context menus appearing

2018-11-05 Thread giannione
How can you say that it was resolved? I still have this bug.

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

Title:
  Multiple context menus appearing

Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator source package in Artful:
  In Progress

Bug description:
  I have dropbox installed on my up to date 17.10 system. Clicking the
  dropbox icon triggers multiple menus, over the top of eachother (see
  screenshot). One is a gnome style menu, the other is a white native
  dropbox menu.

  I'd imagine I should really only see one menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 23:09:09 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-08-02 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1716056/+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 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-05 Thread giannione
I still have the problem in gnome terminal, it didn't go away...

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+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 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-04 Thread giannione
gnome says that it's not their problem
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/48

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+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 1790100] Re: unable to write ~ and ^ chars in the terminal

2018-11-04 Thread giannione
I have the same problem on ubuntu 18.10 on gnome terminal (the problem
appeared after upgrading from an 17.04ubuntu).

*xev gnome terminal output (in gnome terminal ^ doesn't work)*

KeyPress event, serial 37, synthetic NO, window 0x2c1,
root 0x2ac, subw 0x0, time 12476575, (1386,-67), root:(1426,349),
state 0x11, keycode 21 (keysym 0x5e, asciicircum), same_screen YES,
XLookupString gives 1 bytes: (5e) "^"
XmbLookupString gives 1 bytes: (5e) "^"
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2c1,
root 0x2ac, subw 0x0, time 12476723, (1386,-67), root:(1426,349),
state 0x11, keycode 21 (keysym 0x5e, asciicircum), same_screen YES,
XLookupString gives 1 bytes: (5e) "^"
XFilterEvent returns: False

*xev terminator output (in terminator ^ works perfectly)*

KeyPress event, serial 37, synthetic NO, window 0x2a1,
root 0x2ac, subw 0x0, time 12700278, (680,1395), root:(756,1613),
state 0x11, keycode 21 (keysym 0x5e, asciicircum), same_screen YES,
XLookupString gives 1 bytes: (5e) "^"
XmbLookupString gives 1 bytes: (5e) "^"
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2a1,
root 0x2ac, subw 0x0, time 12700465, (680,1395), root:(756,1613),
state 0x11, keycode 21 (keysym 0x5e, asciicircum), same_screen YES,
XLookupString gives 1 bytes: (5e) "^"
XFilterEvent returns: False

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

Title:
  unable to write ~ and ^ chars in the terminal

Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I am using Ubuntu 18.10 and since the last update, I am unable to
  write ~ and ^ chars in the terminal, in both gnome-terminal and Geany
  (both using libvte2.91).

  I don't have this issue with other applications (terminator, xterm,
  Firefox, Gedit, etc.). But note that now, when I type ^ for the first
  time in Gedit for example, I see this char but underlined. If I type
  it a second type (or press space), it is transformed in ^ without line
  under it. This is a new behaviour that can cause this bug in libvte.

  Please tell me if I need to join other info!

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libvte-2.91-0 0.52.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 31 11:17:43 2018
  InstallationDate: Installed on 2015-08-10 (1116 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: vte2.91
  UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+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 1716056] Re: Multiple context menus appearing

2018-10-13 Thread giannione
I still have this problem after upgrading to ubuntu 18.04, dropbox
59.4.3

The problem persists if I switch themes throug ubuntu tweak

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

Title:
  Multiple context menus appearing

Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator source package in Artful:
  In Progress

Bug description:
  I have dropbox installed on my up to date 17.10 system. Clicking the
  dropbox icon triggers multiple menus, over the top of eachother (see
  screenshot). One is a gnome style menu, the other is a white native
  dropbox menu.

  I'd imagine I should really only see one menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 23:09:09 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-08-02 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1716056/+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 841369] Re: English (South Africa) Language Pack is installed by default in Mozilla Firefox

2018-01-21 Thread giannione
I still find this problem in ubuntu 17.10 and firefox 57.

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

Title:
  English (South Africa) Language Pack is installed by default in
  Mozilla Firefox

Status in firefox package in Ubuntu:
  Won't Fix

Bug description:
  In addition to the 'English (GB) Language Pack', 'English (South
  Africa)' is also installed by default in Mozilla Firefox on Oneiric
  Ocelot. This is not useful to everyone and it is a repetition.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 7.0~b3+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sipherdee   1884 F pulseaudio
  BuildID: 20110830191244
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf100 irq 50'
 Mixer name : 'IDT 92HD73C1X5'
 Components : 'HDA:111d7675,102802bd,00100103'
 Controls  : 17
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 51'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: beta
  Date: Sun Sep  4 17:20:06 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  IpRoute:
   default via 10.153.108.1 dev wlan0  proto static 
   10.153.108.0/24 dev wlan0  proto kernel  scope link  src 10.153.108.135 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0/20110830191244 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd03/30/2011:svnDellInc.:pnStudio1557:pvrA09:rvnDellInc.:rn:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1557
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/841369/+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 40872] Re: Desktop icons are allowed to overlap

2017-11-14 Thread giannione
** Changed in: desktop
   Status: New => Confirmed

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

Title:
  Desktop icons are allowed to overlap

Status in Desktop:
  Confirmed
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus-elementary:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have some icons with long file names.  Sometimes I unintentionally
  end up with completely illegible icon labels and overlapping icons.  I
  have created a snapshot of my intentionally horrific example.

  This problem is easy to reproduce when working with file previews
  (irregularly shaped images) and icons with long file names.  Just
  create some and drag them close together, paying attention to not
  trigger the a file move event.

  I have noticed what I consider to be a related problem.  When I remove
  a file from my desktop or a new icon is added as a result of some
  program adding an entry, the desktop isn't refreshed with autoarranged
  icons.  I have looked and looked and can find no way to make this my
  desktop's behavior.  I think this is terrible UI from a usability
  standpoint.  I will attach the image showing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/desktop/+bug/40872/+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 40872] Re: Desktop icons are allowed to overlap

2017-11-05 Thread giannione
The most annoying consequence of this bug happens when you mount a new
drive whose icon overlaps with the existing ones, forcing you to
rearrange your desktop.

How can we report on gnome bugzilla? Is this the url?
https://bugzilla.gnome.org/

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

Title:
  Desktop icons are allowed to overlap

Status in Desktop:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus-elementary:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have some icons with long file names.  Sometimes I unintentionally
  end up with completely illegible icon labels and overlapping icons.  I
  have created a snapshot of my intentionally horrific example.

  This problem is easy to reproduce when working with file previews
  (irregularly shaped images) and icons with long file names.  Just
  create some and drag them close together, paying attention to not
  trigger the a file move event.

  I have noticed what I consider to be a related problem.  When I remove
  a file from my desktop or a new icon is added as a result of some
  program adding an entry, the desktop isn't refreshed with autoarranged
  icons.  I have looked and looked and can find no way to make this my
  desktop's behavior.  I think this is terrible UI from a usability
  standpoint.  I will attach the image showing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/desktop/+bug/40872/+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 40872] Re: Desktop icons are allowed to overlap

2017-10-30 Thread giannione
Launchpad couldn't connect to GNOME Bug Tracker.
(what does this mean?)

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

Title:
  Desktop icons are allowed to overlap

Status in Desktop:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus-elementary:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have some icons with long file names.  Sometimes I unintentionally
  end up with completely illegible icon labels and overlapping icons.  I
  have created a snapshot of my intentionally horrific example.

  This problem is easy to reproduce when working with file previews
  (irregularly shaped images) and icons with long file names.  Just
  create some and drag them close together, paying attention to not
  trigger the a file move event.

  I have noticed what I consider to be a related problem.  When I remove
  a file from my desktop or a new icon is added as a result of some
  program adding an entry, the desktop isn't refreshed with autoarranged
  icons.  I have looked and looked and can find no way to make this my
  desktop's behavior.  I think this is terrible UI from a usability
  standpoint.  I will attach the image showing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/desktop/+bug/40872/+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 40872] Re: Desktop icons are allowed to overlap

2017-10-30 Thread giannione
[Desktop icons are not aligned in the horizontal grid]
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1323075


[Desktop icons should have vertical align grid and exact size]
https://bugzilla.gnome.org/show_bug.cgi?id=530430

[Gnome lost icons position on the desktop]
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/401446

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

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

Title:
  Desktop icons are allowed to overlap

Status in Desktop:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus-elementary:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have some icons with long file names.  Sometimes I unintentionally
  end up with completely illegible icon labels and overlapping icons.  I
  have created a snapshot of my intentionally horrific example.

  This problem is easy to reproduce when working with file previews
  (irregularly shaped images) and icons with long file names.  Just
  create some and drag them close together, paying attention to not
  trigger the a file move event.

  I have noticed what I consider to be a related problem.  When I remove
  a file from my desktop or a new icon is added as a result of some
  program adding an entry, the desktop isn't refreshed with autoarranged
  icons.  I have looked and looked and can find no way to make this my
  desktop's behavior.  I think this is terrible UI from a usability
  standpoint.  I will attach the image showing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/desktop/+bug/40872/+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 40872] Re: Desktop icons are allowed to overlap

2017-10-30 Thread giannione
This problem is still present in ubuntu 17.10, eleven years after the
bug was created. How can this be solved? Is there a similar bug in the
gnome bug tracking tool?

** Also affects: desktop
   Importance: Undecided
   Status: New

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

Title:
  Desktop icons are allowed to overlap

Status in Desktop:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus-elementary:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have some icons with long file names.  Sometimes I unintentionally
  end up with completely illegible icon labels and overlapping icons.  I
  have created a snapshot of my intentionally horrific example.

  This problem is easy to reproduce when working with file previews
  (irregularly shaped images) and icons with long file names.  Just
  create some and drag them close together, paying attention to not
  trigger the a file move event.

  I have noticed what I consider to be a related problem.  When I remove
  a file from my desktop or a new icon is added as a result of some
  program adding an entry, the desktop isn't refreshed with autoarranged
  icons.  I have looked and looked and can find no way to make this my
  desktop's behavior.  I think this is terrible UI from a usability
  standpoint.  I will attach the image showing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/desktop/+bug/40872/+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 1728313] Re: integrated intel GPU doesn't work with wayland on ubuntu 17.10

2017-10-28 Thread giannione
** Description changed:

  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10
  
  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"
  
  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]
  
  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.
  
+ If I switch from gdm3 to lightdm, I can see the wayland gnome and ubuntu
+ sessions in the list of the available sessions, but I can't login. To be
+ precise, using lightdm I can't login at all.
+ 
  When logging, there are some errors, for example:
  [OK] Starting session manager for UID 121
- Stopping session manager for UID 121 
- 
- 
- 
+ Stopping session manager for UID 121
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: weston (not installed)
  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.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 29 00:22:36 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  Renderer: Software
  SourcePackage: weston
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
   integrated intel GPU doesn't work with wayland on ubuntu 17.10

Status in wayland package in Ubuntu:
  New
Status in weston package in Ubuntu:
  New

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10

  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"

  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]

  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.

  If I switch from gdm3 to lightdm, I can see the wayland gnome and
  ubuntu sessions in the list of the available sessions, but I can't
  login. To be precise, using lightdm I can't login at all.

  

[Desktop-packages] [Bug 1728313] Re: integrated intel GPU doesn't work with wayland on ubuntu 17.10

2017-10-28 Thread giannione
** Also affects: wayland (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
   integrated intel GPU doesn't work with wayland on ubuntu 17.10

Status in wayland package in Ubuntu:
  New
Status in weston package in Ubuntu:
  New

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10

  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"

  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]

  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.

  When logging, there are some errors, for example:
  [OK] Starting session manager for UID 121
  Stopping session manager for UID 121 



  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: weston (not installed)
  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.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 29 00:22:36 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  Renderer: Software
  SourcePackage: weston
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1728313/+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 1728168] Re: integrated intel GPU doesn't work on ubuntu 17.10

2017-10-28 Thread giannione
I submitted a new bug.

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

** Tags removed: amd64 apport-bug artful performance ubuntu wayland-
session

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

Title:
  integrated intel  GPU doesn't work on ubuntu 17.10

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU.

  If I run ubuntu connecting the monitor to the integrated GPU, after
  phisically removing the Asus Radeon card, the performance is very
  sluggish, unusable both in a wayland session and in an X session.

  If I run ubuntu without phisically removing the Asus Radeon Card
  (disabled from the bios), there is an error that prevents me from
  logging in, and that makes the TTY consoles unusable: all I get is a
  blank screen with infos about /dev/sda1

  If I use the radeon card, the performace is more or less ok.

  My question is why the integrated intel GPU doesn't work.

  OS:
  ubuntu 17.10

  graphic card:
   description: VGA compatible controller
 product: Turks XT [Radeon HD 6670/7670]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:131 memory:c000-cfff memory:dfe2-dfe3 
ioport:e000(size=256) memory:c-d

  integrated GPU, which doesn't work very well;
  intel i5-8400 cpu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Oct 27 23:37:35 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1728168/+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 1728168] [NEW] integrated intel GPU doesn't work on ubuntu 17.10

2017-10-27 Thread giannione
Public bug reported:

I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
installed an old asus [Radeon HD 6670/7670] GPU.

If I run ubuntu connecting the monitor to the integrated GPU, after
phisically removing the Asus Radeon card, the performance is very
sluggish, unusable both in a wayland session and in an X session.

If I run ubuntu without phisically removing the Asus Radeon Card
(disabled from the bios), there is an error that prevents me from
logging in, and that makes the TTY consoles unusable: all I get is a
blank screen with infos about /dev/sda1

If I use the radeon card, the performace is more or less ok.

My question is why the integrated intel GPU doesn't work.

OS:
ubuntu 17.10

graphic card:
 description: VGA compatible controller
   product: Turks XT [Radeon HD 6670/7670]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:01:00.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
   configuration: driver=radeon latency=0
   resources: irq:131 memory:c000-cfff memory:dfe2-dfe3 
ioport:e000(size=256) memory:c-d

integrated GPU, which doesn't work very well;
intel i5-8400 cpu

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
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.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Oct 27 23:37:35 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
InstallationDate: Installed on 2017-10-25 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0419
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful performance ubuntu wayland-session

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

Title:
  integrated intel  GPU doesn't work on ubuntu 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU.

  If I run ubuntu connecting the monitor to the integrated GPU, after
  phisically removing the Asus Radeon card, the performance is very
  sluggish, unusable both in a wayland session and in an X session.

  If I run ubuntu without phisically removing the Asus Radeon Card
  (disabled from the bios), there is an error that prevents me from
  logging in, and that makes the TTY consoles unusable: all I get is a
  blank screen with infos about /dev/sda1

  If I use the radeon card, the performace is more or less ok.

  My question is why the integrated intel GPU doesn't work.

  OS:
  ubuntu 17.10

  graphic card:
   description: VGA compatible controller
 product: Turks XT [Radeon HD 6670/7670]
 vendor: Advanced Micro Devices,