[Bug 1718931] Re: No VPN autoconnect

2023-06-16 Thread Marco Dal Moro
it's 2023 and this is still an issue. I'm trying with an ethernet
connection and if I trigger for it to connect automatically with a VPN
then my Ubuntu logs in with neither connected: I have to MANUALLY click
on  WIRED Connection then both connects correctly.

This is incredible.

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

Title:
  No VPN autoconnect

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]

2022-12-30 Thread Marco Rolfini
Bug fixed after updating to jammy-proposed/nautilus/1:42.2-0ubuntu2

Testing procedure:
Booted with Wayland
Reproduced bug (as described in test case above)
Updated to jammy-proposed/nautilus/1:42.2-0ubuntu2
Rebooted with Wayland
Performed test case as above
Already open Nautilus windows remain and window for selected place opens as 
expected

When the updated package will be released?
(The updated package will be released to -updates after the bug(s) fixed by 
this package have been verified and the package has been in -proposed for a 
minimum of 7 days.)

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

Title:
  Nautilus crashes when opening places from the dock context menu
  [SIGSEGV in delete_outdated_error_traps() from
  gdk_x11_display_error_trap_push()]

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

2022-01-16 Thread marco
Firefox 96 deb on 22.04 is broken again.

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1943534] Re: Add kernel version to 'About' page in Settings

2021-09-15 Thread Marco Aurélio Gonçalves Pinto
I don't have a clue on how to get that information.

All I see is that when I update VirtualBox on Windows 10, the guest
additions CD for Ubuntu guest refers to the kernel version.

Besides that, I am clueless.

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

Title:
  Add kernel version to 'About' page in Settings

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

2021-06-07 Thread Marco van Zwetselaar
Confirming that gnome-shell 3.38.4-1ubuntu3~21.04.1 resolves the issue.
Thank you for your work, it is much appreciated.

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1800043] Re: nautilus cannot write on nfs file share base dir

2021-05-02 Thread Marco
Hi, I have here exactly the same issue on ubuntu 20.04
can't write to the 1st directory of nfs share in nautilus.
In the terminal window no problem

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

Title:
  nautilus cannot write on nfs file share base dir

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1920239] [NEW] UBUNTU 21.04: Dash to dock wrong focus

2021-03-19 Thread Marco Giannini
Public bug reported:

Ubuntu Hirsute Hippo (development branch)
gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1

BUG
When I press on "Show applications" on the dock the animation starts and at the 
end I end up with the application icons in the background. The icons are partly 
overlaid by the program preview.

Video of the bug https://youtu.be/eodtSxRRiNg

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Schermata da 2021-03-19 17-01-45.png"
   
https://bugs.launchpad.net/bugs/1920239/+attachment/5478314/+files/Schermata%20da%202021-03-19%2017-01-45.png

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

Title:
  UBUNTU 21.04: Dash to dock wrong focus

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1903446] [NEW] the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason

2020-11-08 Thread marco franzini
Public bug reported:

it take also 1 Gbyte of memory

I expect not using these resoruces from my cpu.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  8 23:13:43 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-10-04 (34 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  the process gnome-shell stay active for ever, and take 6-7 perc. of
  resorce, without apparent reason

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-21 Thread Marco Giannini
The patch seems to work fine on Ubuntu 20.10 too.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-20 Thread Marco Giannini
As for Ubuntu 20.10, what is the timing for the arrival of the patch?
Will it take some time after arriving on 20.04 or will they be
contextual? (yes, the bug is also present in the development branch I'm
testing)

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-20 Thread Marco Giannini
For now it seems to work, no problems have emerged after the update.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards

2020-08-21 Thread Marco Giannini
Same problema with same workaround

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

Title:
  [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu
  20.04 with nvidia cards

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892404] [NEW] busted scale with lowercase characters

2020-08-20 Thread Marco Giannini
Public bug reported:

UI resolution busted after updating to mutter 3.36.4-0ubuntu0.20.04.2
The writing in the top bar is too small. The bug also shows up on the login 
screen. To reset I have to change the UI scale factor and then reapply the 100% 
one

Ubuntu 20.04.x LTS
NVIDIA 440.x

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

** Attachment added: "photo_2020-08-20_20-07-12.jpg"
   
https://bugs.launchpad.net/bugs/1892404/+attachment/5403214/+files/photo_2020-08-20_20-07-12.jpg

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

Title:
  busted scale with lowercase characters

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1890949] [NEW] GIMP Crash

2020-08-09 Thread Marco Agudelo
Public bug reported:

```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-8 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx 
--enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch 
--disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) 

using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.62.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Aborted

Stack trace:
```
/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7fc96e0ee8c7]
gimp-2.10(+0xd14a0)[0x55db628b14a0]
gimp-2.10(+0xd18d8)[0x55db628b18d8]
gimp-2.10(+0xd2037)[0x55db628b2037]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x15540)[0x7fc96d5fc540]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fc96d43a3eb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fc96d419899]
/lib/x86_64-linux-gnu/libc.so.6(+0x25769)[0x7fc96d419769]
/lib/x86_64-linux-gnu/libc.so.6(+0x37006)[0x7fc96d42b006]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3f493)[0x7fc96d2ef493]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3f53d)[0x7fc96d2ef53d]
/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5a)[0x7fc96d2ef83a]
/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x61)[0x7fc96d2e1171]
/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x5c3ef)[0x7fc96e1af3ef]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d1)[0x7fc96d7b04e1]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x51a52)[0x7fc96d7b0a52]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x83)[0x7fc96d7b0e33]
gimp-2.10(app_run+0x357)[0x55db628b0cb7]
gimp-2.10(main+0x395)[0x55db628b05b5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7fc96d41b1e3]
gimp-2.10(_start+0x2a)[0x55db628b073a]

```

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

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

Title:
  GIMP Crash

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1876491] Re: Ubuntu 20.04 Freezes

2020-06-28 Thread Marco
Hi! I'm experiencing exactly the same problem. I've added the package
name. Hope someone can help me/us

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

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

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

Title:
  Ubuntu 20.04 Freezes

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1877401] [NEW] The Italian translation is not complete

2020-05-07 Thread Marco
Public bug reported:

The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is not
complete. Some items in the menu are shown in English, like "Right to
Left Document" and "Properties".

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

** Description changed:

- The Italian translation in the version 3.36 in Ubuntu 20.04 LTS is not
+ The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is not
  complete. Some items in the menu are shown in English, like "Right to
  Left Document" and "Properties".

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

Title:
  The Italian translation is not complete

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1876696] [NEW] Install button still actionable when snap install in progress

2020-05-04 Thread Marco Boneff
Public bug reported:

When installing a new snap from gnome-software, the "install" button
remains clickable while installing is in progress. If you press the
button once again, the store returns an error "Impossible to install
«%snap_name%»: snap "%snap_name%" has "install-snap" change in
progress".

Test Case
1. Open GNOME Software
2. Select a snap and click on the install button
3. Click again on the same button

Expected result:
- When the button "Install" is clicked once, it should become inactive (change 
color and not be clickable anymore).
- the label on the button should change showing something like "install in 
progress"
- (Desired, not forcefully required) A progress bar should indicate that 
something is happening

Observed result:
Install button is always active and clickable.
When the "install" button clicked , gnome-software returns the error 
"Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" 
change in progress

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

** Description changed:

  When installing a new snap from gnome-software, the "install" button
  remains clickable while installing. If you press the button once again,
- the store returns says install-snap change is in progress.
+ the store returns an error "Impossible to install «%snap_name%»: snap
+ "%snap_name%" has "install-snap" change in progress".
  
  Test Case
  1. Open GNOME Software
  2. Select a snap and click on the install button
  3. Click again on the same button
  
  Expected result:
  - When the button "Install" is clicked once, it should become inactive 
(change color and not be clickable anymore).
  - the label on the button should change showing something like "install in 
progress"
  - (Desired, not forcefully required) A progress bar should indicate that 
something is happening
  
  Observed result:
  Install button is always active and clickable.
  When the "install" button clicked , gnome-software returns the error 
"Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" 
change in progress

** Description changed:

  When installing a new snap from gnome-software, the "install" button
- remains clickable while installing. If you press the button once again,
- the store returns an error "Impossible to install «%snap_name%»: snap
- "%snap_name%" has "install-snap" change in progress".
+ remains clickable while installing is in progress. If you press the
+ button once again, the store returns an error "Impossible to install
+ «%snap_name%»: snap "%snap_name%" has "install-snap" change in
+ progress".
  
  Test Case
  1. Open GNOME Software
  2. Select a snap and click on the install button
  3. Click again on the same button
  
  Expected result:
  - When the button "Install" is clicked once, it should become inactive 
(change color and not be clickable anymore).
  - the label on the button should change showing something like "install in 
progress"
  - (Desired, not forcefully required) A progress bar should indicate that 
something is happening
  
  Observed result:
  Install button is always active and clickable.
  When the "install" button clicked , gnome-software returns the error 
"Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" 
change in progress

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

Title:
  Install button still actionable when snap install in progress

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1874303] [NEW] Random high CPU usage

2020-04-22 Thread Marco
Public bug reported:

Epiphany randomly causes a high CPU usage, often when opening multiple
tabs or playing high resolution videos on YouTube, but it also happens
when opening a single tab. This issue used to happen even with previous
versions of Epiphany on the previous versions of Ubuntu, but I never
noticed it on other distros like Fedora.

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

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

Title:
  Random high CPU usage

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1868437] [NEW] I was closing the program. The last commando was to save the image.

2020-03-22 Thread Marco Penitenti
Public bug reported:

This is the message of the crash. I don't know anything about this, I
just hope it can be usefull.

Thanks,
Marco 


```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-8 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx 
--enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch 
--disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) 

using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.62.1 (compiled against version 2.58.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Errore di segmentazione

Stack trace:
```

# Stack traces obtained from PID 24485 - Thread 24485 #

[New LWP 24488]
[New LWP 24489]
[New LWP 24490]
[New LWP 24491]
[New LWP 24492]
[New LWP 24495]
[New LWP 24496]
[New LWP 24497]
[New LWP 24498]
[New LWP 26312]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7fff3c399ed0, fd=16) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7f8b72231e00 (LWP 24485) "gimp-2.10"   __libc_read (nbytes=256, 
buf=0x7fff3c399ed0, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f8b71a10700 (LWP 24488) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f8b7120f700 (LWP 24489) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f8b68a0e700 (LWP 24490) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f8b6b1c3700 (LWP 24491) "gmain"   0x7f8b731d3c2f in 
__GI___poll (fds=0x55f32ebdfc90, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7f8b6a184700 (LWP 24492) "gdbus"   0x7f8b731d3c2f in 
__GI___poll (fds=0x55f32ebf19d0, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7f8b4f942700 (LWP 24495) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f8b4f141700 (LWP 24496) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f8b4e940700 (LWP 24497) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f8b4e13f700 (LWP 24498) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f8b37fff700 (LWP 26312) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 11 (Thread 0x7f8b37fff700 (LWP 26312)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f8b734c6d83 in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f8b73984799 in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3  0x7f8b734a4111 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f8b732ba669 in start_thread (arg=) at 
pthread_create.c:479
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140235916703488, 
590778903850546053, 140734203805342, 140734203805343, 140734203805488, 
140235916699904, -638189844953140347, -638323540362497147}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x

[Bug 1860899] Re: Add extra information to tabs in folders

2020-01-27 Thread Marco Aurélio Gonçalves Pinto
Hello!

See the attachment.

Right-clicking on a folder tab in Windows allows to add/remove tabs.

See the tab for the video time and it is also possible for the
resolution but I wasn't able to make it appear.

** Attachment added: "windows10_folder_properties_20200127.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1860899/+attachment/5323317/+files/windows10_folder_properties_20200127.png

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

Title:
  Add extra information to tabs in folders

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1860899] [NEW] Add extra information to tabs in folders

2020-01-26 Thread Marco Aurélio Gonçalves Pinto
Public bug reported:

Windows 10 allows to select in the tabs to show the resolution and
length of the video/audio files.

Could something similar be implemented in Ubuntu?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 26 08:33:44 2020
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'244'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+102+146'"
InstallationDate: Installed on 2020-01-07 (18 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug bionic

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

Title:
  Add extra information to tabs in folders

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1857027] Re: Bytes are not correctly converted to GygaBytes

2019-12-19 Thread marco
Oh interesting!.

Always thought it should have been this way, but I thought it wasn't
standard.

Thanks!

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

Title:
  Bytes are not correctly converted to GygaBytes

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1857027] [NEW] Bytes are not correctly converted to GygaBytes

2019-12-19 Thread marco
Public bug reported:

6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB

This happens in the *folder view* and in the properties of the file

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 19 11:12:55 2019
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2019-01-31 (321 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot from 2019-12-19 11-21-32.png"
   
https://bugs.launchpad.net/bugs/1857027/+attachment/5314052/+files/Screenshot%20from%202019-12-19%2011-21-32.png

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

Title:
  Bytes are not correctly converted to GygaBytes

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1842953] [NEW] GIMP crashed with a fatal error: fatal error: Abortado

2019-09-05 Thread Marco Antonio Castro Collazos
Public bug reported:

```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-8 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx 
--enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch 
--disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) 

using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.60.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Abortado

Stack trace:
```

# Stack traces obtained from PID 19106 - Thread 19106 #

[Nuevo LWP 19144]
[Nuevo LWP 19145]
[Nuevo LWP 19146]
[Nuevo LWP 19211]
[Nuevo LWP 19212]
[Nuevo LWP 19239]
[Nuevo LWP 19240]
[Nuevo LWP 19241]
[Nuevo LWP 19242]
[Nuevo LWP 19711]
[Nuevo LWP 19740]
[Nuevo LWP 19782]
[Nuevo LWP 24829]
[Depuración de hilo usando libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7fffc9710690, fd=25) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7feaf589ee00 (LWP 19106) "gimp-2.10"   __libc_read (nbytes=256, 
buf=0x7fffc9710690, fd=25) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7feaf4df1700 (LWP 19144) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7feaf45f0700 (LWP 19145) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7feaf3def700 (LWP 19146) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7feaf1708700 (LWP 19211) "gmain"   0x7feaf7588729 in 
__GI___poll (fds=0x557b19506720, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7feaf0f07700 (LWP 19212) "gdbus"   0x7feaf7588729 in 
__GI___poll (fds=0x557b19518340, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7fead2180700 (LWP 19239) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7fead197f700 (LWP 19240) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7fead117e700 (LWP 19241) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7fead097d700 (LWP 19242) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7feac28c0700 (LWP 19711) "threaded-ml" 0x7feaf7588729 in 
__GI___poll (fds=0x7feaac007030, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  12   Thread 0x7feac20bf700 (LWP 19740) "dashboard"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7feac3fff700 (LWP 19782) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  14   Thread 0x7feac356f700 (LWP 24829) "paint"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 14 (Thread 0x7feac356f700 (LWP 24829)):
#0  0x7feaf758e2e9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7feaf787293f in g_cond_wait () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x557b1833dcdd in  ()
#3  0x7feaf785087d in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7feaf766d182 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140646276331264, 
-2235778285477159597, 140736573015614, 140736573015615, 140736573015760, 
140646276327680, 

[Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

2019-08-11 Thread Marco Lopilato
Will the fix be released for 18.04 also? Thx

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

Title:
  [xfce] nautilus don't open files if set as default file manager

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1825710] Re: Remove "Application is ready" notification

2019-06-12 Thread Marco Aurélio Gonçalves Pinto
This window that keeps appearing is very annoying.

Can't a setting be created in the OS with a CheckBox gadget to
enable/disable the warning?

"blah blah is ready" is very annoying.

:-(


** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825710/+attachment/5270401/+files/VirtualBox_Ubuntu%2018.04.2%20LTS%20x64%20%28PureBasic%29%20-%202019-06-12.png

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

Title:
  Remove "Application is ready" notification

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 49348] Re: List view in Nautilus does not allow dragging a selection by mouse

2019-05-03 Thread Marco Aurélio Gonçalves Pinto
Here are two video captures, one in Windows 10 and other in Ubuntu
19.04.


** Attachment added: "Windows 10 behaviour"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/49348/+attachment/5261178/+files/win10_drag_mouse_20190503.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/49348

Title:
  List view in Nautilus does not allow dragging a selection by mouse

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 49348] Re: List view in Nautilus does not allow dragging a selection by mouse

2019-05-03 Thread Marco Aurélio Gonçalves Pinto
Ubuntu 19.04 behaviour

** Attachment added: "Ubuntu 19.04 behaviour"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/49348/+attachment/5261179/+files/ub1904_drag_mouse_20190503.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/49348

Title:
  List view in Nautilus does not allow dragging a selection by mouse

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1774957] Re: Network icons in status menu disappearing

2019-03-18 Thread Marco Ferretti
Following up on #30 and #29 I can confirm that ubuntu 18.04.2 is working
fine with the patch from comment #23

Thanks a lot for the support !

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

Title:
  Network icons in status menu disappearing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1774957] Re: Network icons in status menu disappearing

2019-03-18 Thread Marco Ferretti
Hi Daniel,

will install the patch later today and let you know.

Thanks for pointing me to a possible solution (I completely missed it).

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

Title:
  Network icons in status menu disappearing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1774957] Re: Network icons in status menu disappearing

2019-03-16 Thread Marco Ferretti
p.s.: restarting gnome-shell (with SIGQUIT) works as a temporary patch.

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

Title:
  Network icons in status menu disappearing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1774957] Re: Network icons in status menu disappearing

2019-03-16 Thread Marco Ferretti
I am still experiencing the issue on ubuntu 18.04.4 :

dpkg -s gnome-shell
Package: gnome-shell
Status: install ok installed
Priority: optional
Section: universe/gnome
Installed-Size: 7350
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 3.28.3-0ubuntu0.18.04.4
Provides: notification-daemon, polkit-1-auth-agent
Depends: libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 (>= 1.12.4), libc6 (>= 
2.14), libcairo2 (>= 1.14.0), libcanberra-gtk3-0 (>= 0.25), libcanberra0 (>= 
0.2), libcroco3 (>= 0.6.2), libecal-1.2-19 (>= 3.17), libedataserver-1.2-23 (>= 
3.17.2), libgcr-base-3-1 (>= 3.8.0), libgdk-pixbuf2.0-0 (>= 2.22.0), 
libgirepository-1.0-1 (>= 1.35.9), libgjs0-libmozjs-52-0, libgjs0g (>= 1.52.1), 
libglib2.0-0 (>= 2.53.0), libgstreamer1.0-0 (>= 1.4.0), libgtk-3-0 (>= 3.21.6), 
libical3 (>= 3.0.0), libjson-glib-1.0-0 (>= 0.13.2), libmutter-2-0 (>= 3.28.3), 
libnm0 (>= 1.0.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), 
libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.94), 
libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), libsecret-1-0 (>= 
0.7), libstartup-notification0 (>= 0.11), libsystemd0, libx11-6, libxfixes3, 
evolution-data-server (>= 3.17.2), gir1.2-accountsservice-1.0, gir1.2-atspi-2.0 
(>= 2.9.91), gir1.2-freedesktop, gir1.2-gdesktopenums-3.0 (>= 3.12), 
gir1.2-geoclue-2.0, gir1.2-gcr-3 (>= 3.7.5), gir1.2-gdm-1.0 (>= 3.18.2), 
gir1.2-glib-2.0 (>= 1.45.3), gir1.2-gnomebluetooth-1.0 (>= 3.12.0), 
gir1.2-gnomedesktop-3.0 (>= 3.12.0), gir1.2-gtk-3.0 (>= 3.16), 
gir1.2-gweather-3.0, gir1.2-ibus-1.0 (>= 1.5.2), gir1.2-mutter-2 (>= 3.27.91), 
gir1.2-nm-1.0, gir1.2-nma-1.0, gir1.2-pango-1.0, gir1.2-polkit-1.0, 
gir1.2-rsvg-2.0, gir1.2-soup-2.4 (>= 2.40.1), gir1.2-upowerglib-1.0 (>= 0.99), 
gjs (>= 1.47.90), gnome-settings-daemon (>= 3.16.0), gnome-shell-common (= 
3.28.3-0ubuntu0.18.04.4), ubuntu-wallpapers, gsettings-desktop-schemas (>= 
3.21.3), mutter (>= 3.27.91), python3, libglib2.0-bin (>= 2.53.0)
Recommends: xserver-xorg-legacy, bolt (>= 0.2), gkbd-capplet, 
gnome-control-center, gnome-user-guide, iio-sensor-proxy, unzip, ubuntu-session 
| gnome-session
Suggests: gir1.2-telepathyglib-0.12, gir1.2-telepathylogger-0.2 (>= 0.8.0), 
chrome-gnome-shell, gdm3 (>= 3.10.0.1-3~), gnome-themes-standard-data, 
switcheroo-control
Breaks: gdm3 (<< 3.19.92), gnome-session (<< 3.19)
Conflicts: gnome-screensaver (<< 3.6)
Description: graphical shell for the GNOME desktop
 The GNOME Shell provides core interface functions like switching
 windows, launching applications or see your notifications. It takes
 advantage of the capabilities of modern graphics hardware and
 introduces innovative user interface concepts to provide a
 delightful and easy to use experience. GNOME Shell is the defining
 technology of the GNOME 3 user experience.
Homepage: https://wiki.gnome.org/Projects/GnomeShell
Original-Maintainer: Debian GNOME Maintainers 


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

Title:
  Network icons in status menu disappearing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1819945] [NEW] nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()

2019-03-13 Thread Marco Giannini
Public bug reported:

Ubuntu 19.04 dev
Nautilus 3.31.90-stable

The crash occurred when I clicked the trash can icon on the desktop

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.31.90-1ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 13 18:08:09 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2019-02-26 (14 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x557faa5f70d9 :  mov
(%rbx),%rdi
 PC (0x557faa5f70d9) ok
 source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_view_get_selection ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
 
usr_lib_nautilus:

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


** Tags: amd64 apport-crash disco

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813542] [NEW] launcher is available on locked screen

2019-01-28 Thread Marco Tanner
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

Public bug reported:

The launcher bar is accessible to me even though the screen is locked. I
was able to take a screenshot via right-clicking the Shutter icon and
selecting 'Capture the entire screen'. See attachment. I'm able to
launch new applications via launcher and close open ones. (New windows
aren't shown, but are open after unlocking).

Re-locking yields the same situation again. I have yet to reboot to see
if the problem persists.

The expectation is that the launcher bar is not available whilst the
screen is locked.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 28 10:05:38 2019
InstallationDate: Installed on 2018-04-20 (282 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180420)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdm3 (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot of bad behaviour"
   
https://bugs.launchpad.net/bugs/1813542/+attachment/5233169/+files/Workspace%201_167.png

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

Title:
  launcher is available on locked screen

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812279] [NEW] The ubuntu dock (ubuntu-dock-extension) appears when the screen lock is activated, enabling the access to the applications.

2019-01-17 Thread Marco Furlan
Public bug reported:

The problem is the same as reported in https://github.com/micheleg/dash-
to-dock/issues/649.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
Uname: Linux 4.16.3-041603-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 17 21:35:02 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2016-07-25 (906 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to bionic on 2018-07-18 (183 days ago)

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  The ubuntu dock (ubuntu-dock-extension) appears when the screen lock
  is activated, enabling the access to the applications.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1806983] Re: desktop environment resumes badly when resuming from suspend mode

2019-01-07 Thread Marco
Yes, I'm using some extensions. I'll try to deactivate them all and
report if issue exists anymore.

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

Title:
  desktop environment resumes badly when resuming from suspend mode

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2018-12-06 Thread Marco
My report (1806983) is slightly different and more problematic: when the bug 
occurs, the interface, the app bar now keeps beeing buggy until I reboot and 
the unlock interface doesn't shows at all even if I re-put on suspend and 
re-resume.
I had the "desktop showed for one second" bug but it this case I have the "lock 
screen not showed at all" one

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1806983] [NEW] desktop environment resumes badly when resuming from suspend mode

2018-12-05 Thread Marco
Public bug reported:

I've a problem when resuming from suspend mode and try to unlock my pc.

Expected Behavior:

Interface shows correctly after resuming from suspend mode.

Real Behavior:

Interface shows badly after resume PC from suspend.
unlock interface doesn't shows at all; instead of it, desktop (or last 
application) is shown.

Have to re-suspend PC and re-resume, so the unlock interface is showed
but application's bar shows like pc is still locked, so it doesn't show
real opened applications.

"resize and move windows" shortcuts doesn't work either.

How to reproduce bug:

Go to suspend mode, resume. mostly the bug doesn't appear, but sometimes
yes.

Distro Description: Ubuntu 18.10

  Installed: 3.30.1-1ubuntu5
  Candidate:  3.30.1-1ubuntu5
  Version Table:
 *** 3.30.1-1ubuntu5 500
500 http://it.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.30.1-1ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  5 20:16:03 2018
InstallationDate: Installed on 2017-10-21 (410 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (46 days ago)
mtime.conffile..etc.gdm3.Init.Default: 2017-11-21T14:48:20.846402
mtime.conffile..etc.gdm3.custom.conf: 2018-10-20T16:29:04.442996

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


** Tags: amd64 apport-bug cosmic

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

Title:
  desktop environment resumes badly when resuming from suspend mode

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1805503] [NEW] Files and folders search doesn't work properly with Nautilus 3.30 from the GNOME 3 Staging PPA

2018-11-27 Thread Marco
Public bug reported:

On my Ubuntu 18.10 I upgraded Nautilus from the GNOME 3 Staging PPA. But
with Nautilus 3.30, when I try to search my files and my folders from
the activity view, I almost never get results. With Nautilus 3.26 the
files and folders search works flawlessly, but with Nautilus 3.30 does
not work properly neither with Tracker 2.0.3 nor with Tracker 2.1.3 from
the GNOME 3 Staging PPA.

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

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


** Tags: files folders nautilus search tracker

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

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

Title:
  Files and folders search doesn't work properly with Nautilus 3.30 from
  the GNOME 3 Staging PPA

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1797553] Re: file-roller extract and replace does not replace

2018-10-12 Thread Marco van Zwetselaar
Sorry about that, this is 18.04 bionic.  Have tagged the bug.

** Tags added: bionic

** Description changed:

  When extracting a file over an existing file, clicking "Replace" in the
  dialog that asks to confirm overwriting a file, does not replace the
  file.
  
- Reproduce: 
+ Reproduce:
  - Open any archive (I've tested zip and 7z)
  - Right click a file and extract
  - Edit the extracted file so you can see that it will not be replaced
- - Right click the and extract the file again, to the same file name
+ - Right click and extract the file again, to the same file name
  - In the dialog asking whether to replace the file, click "Replace".
- - File confirms extraction, however the file was *not* replaced by the copy 
from the archive
+ - File roller confirms extraction, however the file was *not* replaced by the 
copy from the archive

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1797553

Title:
  file-roller extract and replace does not replace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1797553/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1797553] [NEW] file-roller extract and replace does not replace

2018-10-12 Thread Marco van Zwetselaar
Public bug reported:

When extracting a file over an existing file, clicking "Replace" in the
dialog that asks to confirm overwriting a file, does not replace the
file.

Reproduce: 
- Open any archive (I've tested zip and 7z)
- Right click a file and extract
- Edit the extracted file so you can see that it will not be replaced
- Right click the and extract the file again, to the same file name
- In the dialog asking whether to replace the file, click "Replace".
- File confirms extraction, however the file was *not* replaced by the copy 
from the archive

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1797553

Title:
  file-roller extract and replace does not replace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1797553/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

2018-08-14 Thread Marco van Zwetselaar
Added gnome-shell to affected packages, as the issue is independent of
gnome-power-manager.

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

2018-08-14 Thread Marco van Zwetselaar
Adding some more information. Running the following as root in a gnome
terminal:

   SYSFILE=/sys/class/backlight/intel_backlight/brightness
   OLD_VAL=$(cat $SYSFILE)
   NEW_VAL=$((OLD_VAL + 100))

   T0=$(date +%N)
   time echo $NEW_VAL  | tee $SYSFILE
   T1=$(date +%N)

   echo "Total time (millis): $(((T1 - T0)/1000))"

Gives the following:

   real0m0.002s
   user0m0.002s
   sys 0m0.001s
   Total time (millis): 3502

In other words, the write to sysfs returns in 2ms (and indeed,
brightness changes instantly), but it takes 3502ms for control to get
back to the prompt.

During that time, the system seems to hang, but keypresses are
collected: they are all echoed to the terminal right after the command
returns.  So the question then is: where are the 3 seconds spent?

I'm happy to experiment if someone has instructions.

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

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

2018-08-14 Thread Marco van Zwetselaar
Bug reappeared in 18.04.

Dell Precision M4800, running the standard Ubuntu Gnome shell desktop
(on Xorg), Intel Graphics.  No issues in 16.04 (or perhaps a tiny
delay?), but unworkable in 18.04.

Both Fn-Up/Down and `echo value | sudo tee brightness` exhibit the delay
(~2-3 seconds normally). Notable is that the brightness seems to change
*immediately* after echoing into sysfs, so all the delay occurs in the
return of the call back to the prompt.

In /sys/class/backlight I have only intel_backlight. No difference with
or without Backlight option in xorg.conf, nor with the
acpi_backlight=vendor kernel param.

Also notable: when performing the brightness change in a virtual
terminal, it is *instantaneous*.  The issue only occurs in the graphical
VT running the desktop environment.

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779846] Re: Pressing Alt+Backslash locks up all windows (no focus)

2018-07-06 Thread Marco Gaiarin
> First, please try removing these shell extensions:

A-Ha! Sorry, i've played with some extensions and never minded about
them.

I've disabled (it suffices, it was not needed to uninstall them)
'system-monitor' and 'windows-alt-tab' and problem desappear.

Many thanks and sorry for that bug report!

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

Title:
  Pressing Alt+Backslash locks up all windows (no focus)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779846] [NEW] Pressing Alt+Backslash locks up all windows (no focus)

2018-07-03 Thread Marco Gaiarin
Public bug reported:

I've recently switched from 16.04/Unity to 18.04/Gnome3, with new
hardware (a Lenovo Thinkpad T470s) used mostly with a docking station
and external keyboard.

I do heavily use of in-workspace windows switch (eg, Alt+Esc) and i've found 
that every time i press Alt+Backslash (in Italian keyboard layout Backslash is 
all left, between TAB and Esc keys) my session ''lock up'': i can switch 
between windows, i can use the gnome shell and the top bar (status bar?), i can 
even run other application (via Alt+F2 or gnome shell menu) but every window 
(old or new) are ''locked'', like there's no focus: no keyboard nor mouse 
interaction is possible.
Application are not 'locked', they continue to run, but there's no way to 
interact with them.

I can also lock the screen, or put the system in standby: i can awaken
from that, insert the password but still no focus on windows.

The only solution: logout.

I've also tried to define a keyboard shortcut to map Alt+Backslash,
but... gnome keyboard configurator locks as every other window when i
press the keys.

Please, help me at least to disable that 'killer' keyboard shortcut! ;-)

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  3 12:16:18 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' 
b"['system-moni...@paradoxxx.zero.gmail.com', 
'workspace-g...@mathematical.coffee.gmail.com', 'windows-alt-...@tglman.org']"
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-05-25 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Pressing Alt+Backslash locks up all windows (no focus)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777318] Re: GDM3 completely ignore pam_group

2018-06-19 Thread Marco Gaiarin
Done.

https://gitlab.gnome.org/GNOME/gdm/issues/393

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

Title:
  GDM3 completely ignore pam_group

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777318] [NEW] GDM3 completely ignore pam_group

2018-06-17 Thread Marco Gaiarin
Public bug reported:

I'm using some ubuntu machine in a network where users data came from
LDAP.

I've setup PAM/NSS to use LDAP account and all works as expected.
Apart assigning local group to users, via pam_group.

I've added to /etc/pam.d/common-auth (to the end):
 authoptionalpam_group.so

and added to /etc/security/group.conf:
 *; *; %sysops; Al-2400; 
adm,sudo,admin,dip,cdrom,floppy,plugdev,lpadmin,sambashare

but groups are not added as expected, i'm not in 'admin' or 'sudo' group
(eg, i cannot do administrative tasks) and if i fire up a terminal:

 gaio@dora:~$ id
 uid=1000(gaio) gid=1001(casa) gruppi=1001(casa),1000(sysops),1003(bbs)

note that group assignment works, eg:

 gaio@dora:~$ ssh localhost
 gaio@localhost's password: 
 Welcome to Ubuntu 18.04 LTS (GNU/Linux 4.15.0-23-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage


 * Canonical Livepatch is available for installation.
   - Reduce system reboots and improve kernel security. Activate at:
 https://ubuntu.com/livepatch

 0 pacchetti possono essere aggiornati.
 0 sono aggiornamenti di sicurezza.

 Last login: Sun Jun 17 14:36:50 2018 from 127.0.0.1
 gaio@dora:~$ id 
 uid=1000(gaio) gid=1001(casa)  
gruppi=1001(casa),4(adm),24(cdrom),25(floppy),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1000(sysops),1003(bbs)

Previous LTS (16.04) with LightDM works as expected. This bug seems very
similar to #880104 .

Thanks.

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

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

Title:
  GDM3 completely ignore pam_group

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-31 Thread Marco
*** This bug is a duplicate of bug 1726930 ***
https://bugs.launchpad.net/bugs/1726930

I can confirm that the workaround worked also for me!
Yeah, this bug seems a duplicate of https://bugs.launchpad.net/bugs/1726930

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-30 Thread Marco
I tried those debs (kernel 4.4.0-21-generic, however (with battery) I
have same behaviour: black screen a PCIe Bus Error: printed which I
cannot copy easily since, for some reason, the file system becomes read-
only.

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-30 Thread Marco
I found the debs. Sorry I am not that confident with launchpad.

Can these debs be installed from 17.10?

* 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168/+files/linux-headers-4.4.0-21-generic_4.4.0-21.37_amd64.deb
* 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168/+files/linux-headers-4.4.0-21_4.4.0-21.37_all.deb
* 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/9594168/+files/linux-image-4.4.0-21-generic_4.4.0-21.37_amd64.deb

And,are they the ones that you would like me to try?

Thanks

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-30 Thread Marco
Yes I can. Should I install debs or re-build it from source? If debs are
available I can give it a try really quick. Thanks

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-30 Thread Marco
I tried also to boot with 4.7.2-040702-generic with no success (it was an old 
kernel that worked on this machine)
The first kernel version that I have on this machine is 4.5.0-040500-generic, 
and even that one does not go after the splash screen. In previous ubuntu 
releases everything was working.

I noticed also when being on battery and booting that I can switch to a
tty with ctrl+alt+F1 and I see some pcierror message. Not sure if it's
relevant

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-30 Thread Marco
I do not remember for sure but I guess it was the last kernel provided
with ubuntu 17.04. I upgraded 17.04 to keep in sync with security
updates. My guess is that it's the 4.10 "series"

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-30 Thread Marco
Hi,

It happened when upgrading from ubuntu 17.04 to 17.10
On 17.04 everything worked as expected on battery.

Steps that I tried as you suggested:

* I booted into 4.10 kernel and with battery power the problem still happens
* I booted into 4.15 kernel downloaded from the ubuntu mainline repo and with 
battery power the problem still happens.

I attached the logs again including JournalErrors.txt

Hope it helps! Thank you in advance

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

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] ProcCpuinfoMinimal.txt

2018-01-30 Thread Marco
apport information

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

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] ProcEnviron.txt

2018-01-30 Thread Marco
apport information

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

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] Re: On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-30 Thread Marco
apport information

** Tags added: apport-collected

** Description changed:

  Also happens other people here https://askubuntu.com/questions/987821
  /asus-laptop-wont-boot-to-login-screen-when-on-battery-power-
  after-17-10-upgrade
  
  I tried to manually upgrade the kernel to the latest one from the ubuntu 
mainline.
  I tried to setup lightdm/gdm3 with no success.
  However when setting up lightdm I can access to a tty and login. The file 
system for some weird reason becomes read-only.
  
  If I plug the power chord and I reboot everything works fine. Lightdm
  comes up or gdm3 comes up depending on the setup that I made.
  
  Hope this helps
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu3
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Jan 29 22:25:14 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-10 (690 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2018-01-27 (1 days ago)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ CurrentDesktop: GNOME-Flashback:GNOME
+ DistroRelease: Ubuntu 17.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-03-10 (691 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ Package: linux
+ PackageArchitecture: amd64
+ Tags:  artful
+ Uname: Linux 4.15.0-041500rc9-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2018-01-27 (2 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] JournalErrors.txt

2018-01-30 Thread Marco
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1746099/+attachment/5045716/+files/JournalErrors.txt

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1746099] [NEW] On *battery* power when ubuntu 17.10 boots, after the splashscreen a black screen appears

2018-01-29 Thread Marco
Public bug reported:

Also happens other people here https://askubuntu.com/questions/987821
/asus-laptop-wont-boot-to-login-screen-when-on-battery-power-
after-17-10-upgrade

I tried to manually upgrade the kernel to the latest one from the ubuntu 
mainline.
I tried to setup lightdm/gdm3 with no success.
However when setting up lightdm I can access to a tty and login. The file 
system for some weird reason becomes read-only.

If I plug the power chord and I reboot everything works fine. Lightdm
comes up or gdm3 comes up depending on the setup that I made.

Hope this helps

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.1-3ubuntu3
Uname: Linux 4.15.0-041500rc9-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
Date: Mon Jan 29 22:25:14 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-10 (690 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gdm3
UpgradeStatus: Upgraded to artful on 2018-01-27 (1 days ago)

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

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


** Tags: amd64 apport-bug artful

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1746099/+attachment/5045203/+files/JournalErrors.txt

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

Title:
  On *battery* power when ubuntu 17.10 boots, after the splashscreen a
  black screen appears

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

2017-09-14 Thread marco ghidinelli
I've checked now: other users can use wayland without problem, so it's
specific to my user.

After further analysis i found that it's the "focusli" gnome extension.

thanks for the help.

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

2017-09-14 Thread marco ghidinelli
I've checked now: other users can use wayland without problem, so it's
specific to my user.

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

2017-09-14 Thread marco ghidinelli
ii  gnome-shell-extensions  3.25.91-1all
Extensions to extend functionality of GNOME Shell

the current package is installed since the 4th of september:

marcogh@fate:~$ grep gnome-shell-ext /var/log/dpkg.log
2017-09-04 22:46:26 upgrade gnome-shell-extensions:all 3.24.2-0ubuntu2 
3.25.91-0ubuntu2
2017-09-04 22:46:26 status half-configured gnome-shell-extensions:all 
3.24.2-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all 3.24.2-0ubuntu2
2017-09-04 22:46:26 status half-installed gnome-shell-extensions:all 
3.24.2-0ubuntu2
2017-09-04 22:46:26 status half-installed gnome-shell-extensions:all 
3.24.2-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all 3.25.91-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all 3.25.91-0ubuntu2

i just tried to uninstall and reinstall the package (just in case) but
the issue remains.

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

2017-09-14 Thread marco ghidinelli
** Attachment added: "the update journal"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716503/+attachment/4949922/+files/journalctl.txt

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

2017-09-13 Thread marco ghidinelli
** Attachment added: "the journal"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716503/+attachment/4949309/+files/journal.txt

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

2017-09-12 Thread marco ghidinelli
sorry for the delay.

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

2017-09-12 Thread marco ghidinelli
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
Subsystem: Dell HD Graphics 620
Kernel driver in use: i915
Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 02)
Subsystem: Dell Skylake Processor Thermal Subsystem
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
Subsystem: Dell Sunrise Point-LP USB 3.0 xHCI Controller
Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
Subsystem: Dell Sunrise Point-LP Thermal subsystem
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #0 (rev 21)
Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #1 (rev 21)
Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
Subsystem: Dell Sunrise Point-LP CSME HECI
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
Subsystem: Dell Sunrise Point-LP LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
Subsystem: Dell Sunrise Point-LP PMC
Kernel driver in use: intel_pmc_core
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 075b
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
Subsystem: Dell Sunrise Point-LP SMBus
Kernel modules: i2c_i801
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
Subsystem: Dell RTS525A PCI Express Card Reader
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
3c:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 
0115 (rev 01)
Subsystem: Toshiba America Info Systems Device 0001
Kernel driver in use: nvme
Kernel modules: nvme

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1716503] [NEW] gnome-shell --wayland works only when --mode=initial-setup

2017-09-11 Thread marco ghidinelli
Public bug reported:

Package: gnome-shell 
Version: 3.25.91-0ubuntu4

marcogh@fate:~$ lsb_release -rd
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10


Since a couple of version of gnome-shell, --wayland doesn't work anymore.

When launching from console with:

  gnome-shell --wayland --display-server --mode=classic

the screen remains black, the cursor appears in the middle, and nothing
else.

killing gnome-shell from remote ssh brings the console back, with no
error.

Curiously, it works (and it's wayland) when i add

  --mode=initial-setup

The Xorg version works fine.

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

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1713363] [NEW] package systemd 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-08-27 Thread Marco Serra
Public bug reported:

-Computer-
Processor   : Intel(R) Celeron(R) M processor  900MHz
Memory  : 2052MB (940MB used)
Operating System: Ubuntu 17.04
User Name   : casaserra (casaserra)
Date/Time   : dom 27 ago 2017 22:21:26 CEST
-Display-
Resolution  : 1280x1024 pixels
OpenGL Renderer : Unknown
X11 Vendor  : The X.Org Foundation
-Multimedia-
Audio Adapter   : HDA-Intel - HDA Intel
-Input Devices-
 Lid Switch
 Sleep Button
 Power Button
 Power Button
 AT Translated Set 2 keyboard
 Video Bus
 SynPS/2 Synaptics TouchPad
 Asus EeePC extra buttons
 HDA Intel Mic
 HDA Intel Headphone
 UVC Camera (eb1a:2761)
-Printers-
No printers found
-SCSI Disks-
ATA SILICONMOTION SM
 USB DISK 3.0
USB2.0 CardReader SD0

systemd:
  Installato: 232-21ubuntu5
  Candidato:  232-21ubuntu5
  Tabella versione:
 *** 232-21ubuntu5 500
500 http://it.archive.ubuntu.com/ubuntu zesty-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main i386 Packages
100 /var/lib/dpkg/status
 232-21ubuntu2 500
500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
3) What you expected to happen: software updates should be got installed
4) What happened instead: I got a masseage saying some pacakages couldn't be 
installed

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: systemd 232-21ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
Date: Sun Aug 27 20:27:49 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2017-08-27 (0 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
MachineType: ASUSTeK Computer INC. 701
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=dffd559d-cd18-4fee-a7c2-7a0504a4b587 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: systemd
Title: package systemd 232-21ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1302
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 701
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/11/2009:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 701
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

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


** Tags: apport-package i386 zesty

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

Title:
  package systemd 232-21ubuntu5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1677305] [NEW] /dev/sda1 is checked at every boot instead of every 31 mounts

2017-03-29 Thread Marco Lazzaroni
Public bug reported:

Every time I login I get the message:

*** /dev/sda1 will be checked for errors at next reboot ***

/dev/sda1 is my root partition. fsck was successfully run, but it looks
like systemd is not aware of this, so fsck will be run again at the next
boot.


root@serverlinux:~# lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

root@serverlinux:~# LANG=en_US apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu16
  Candidate: 229-4ubuntu16
  Version table:
 *** 229-4ubuntu16 500
500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

root@serverlinux:~# cat /run/initramfs/fsck.log
Log of fsck -C -a -T -t ext4 /dev/sda1
Wed Mar 29 00:26:26 2017

/dev/sda1: clean, 612205/6725632 files, 17326020/2688 blocks (check
in 2 mounts)

Wed Mar 29 00:26:26 2017


root@serverlinux:~# LANG=en_US ls -l /run/initramfs/
total 4
-rw-r--r-- 1 root root   0 Mar 29 02:26 fsck-root
-rw-r--r-- 1 root root 194 Mar 29 02:26 fsck.log

[There's a discrepancy between the time in fsck.log and the time of the
fsck.log but I suspect this is a UTC/CEST issue:

root@serverlinux:~# LANG=en_US date
Wed Mar 29 17:43:17 CEST 2017
root@serverlinux:~# LANG=en_US date -u
Wed Mar 29 15:43:21 UTC 2017

The system was planned for reboot at Mar 29 2:25 CEST (Mar 29 0:25 UTC)]

This is the content of /etc/fstab:

root@serverlinux:~#  cat /etc/fstab
#
proc/proc   procnodev,noexec,nosuid 0   0
# / was on /dev/sda1 during installation
UUID=c50edc7d-9f0b-4958-8e44-00bb5433ba42 /   ext4
errors=remount-ro,noatime,nodiratime,commit=60 0   1
# swap was on /dev/sda5 during installation
UUID=93b413bc-8663-44b4-81de-1a225a2f90da noneswapsw
  0   0
# /dev/sdb1 in ext4 250GB
UUID=5f987a15-685a-4d2b-adf9-8bcde0eca04e   /data ext4 
errors=remount-ro,noatime,nodiratime,commit=60   0   1

The output of LANG=en_US dumpe2fs /dev/sda1 is:
root@serverlinux:~# LANG=en_US dumpe2fs /dev/sda1 
Filesystem created:   Thu Apr 15 15:23:07 2010
Last mount time:  Wed Mar 29 02:26:26 2017
Last write time:  Wed Mar 29 02:26:26 2017
Mount count:  30
Maximum mount count:  31
Last checked: Tue Sep  6 02:46:17 2016
Check interval:   15552000 (6 months)
Next check after: Sun Mar  5 01:46:17 2017

For some reason, "Last checked:" time is not up to date (see above for
the content of /run/initramfs/fsck.log), hence the problem (I suppose).

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

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

Title:
  /dev/sda1 is checked at every boot instead of every 31 mounts

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1143282] Re: Unable to add podcasts in rhythmbox

2017-03-22 Thread Marco van Zwetselaar
This problem still persists in Xenial (16.04), but I may have spotted
the cause.  Checking my apt log, a libc upgrade had taken place before I
tried to update my podcast feeds, and I hadn't since rebooted.  Libc
upgrades prompt for a system reboot - which I usually defer.  As for #3,
a reboot fixed the problem.

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

Title:
  Unable to add podcasts in rhythmbox

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

2016-10-28 Thread Marco
I confirm this bug with gedit, the calculator and text boxes in gtk3
-widget-factory. Changing the colour scheme in Gedit is a workaround. I
have this problem with my user, on Ubuntu 16.10 upgraded from 16.04, but
not logging in the guest session. So I guess the reason is some hidden
setting left by 16.04

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1565814] Re: Unable to click pause, stop or move progressbar in the video

2016-08-27 Thread Marco Giannini
The bug is still present on stable release with nvidia-304 driver.

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

Title:
  Unable to click pause, stop or move progressbar in the video

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1617098] [NEW] network-manager-openvpn max-routes support

2016-08-25 Thread Marco
Public bug reported:

Hi,

Currently in Ubuntu 16.04 network-manager-openvpn does not support the openvpn 
--max-routes switch.
This means that per omission the VPN connection supports 100 routes that can be 
pushed by the openvpn server to the client. If the openvpn server pushes more 
100 routes, which can happen in some cases, the VPN establishment fails.

>From OpenVPN manual:
"--max-routes n
Allow a maximum number of n --route options to be specified, either in the 
local configuration file, or pulled from an OpenVPN server. By default, n=100."

Can you do one of the following?
- Fully support max-routes in the GUI, with an option to choose the value of 
the max-routes
or, simpler:
- Do not implement the max-routes in the GUI but add '--max-routes 500' for 
example for all openvpn connection establishments. I mean increase the number 
of maximum routes for all openvpn connections with network-manager.

There is also a gnome bugzilla related to this issue which was recently
closed with a patch: https://bugzilla.gnome.org/show_bug.cgi?id=720097

When can we have the max-route implementation on network-manager-openvpn
in ubuntu?

mm:~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

mm:~$ apt-cache policy network-manager-openvpn
network-manager-openvpn:
  Installed: 1.1.93-1ubuntu1
  Candidate: 1.1.93-1ubuntu1
  Version table:
 *** 1.1.93-1ubuntu1 500
500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/statusThanks,

mm:~$ apt-cache policy network-manager-openvpn-gnome
network-manager-openvpn-gnome:
  Installed: 1.1.93-1ubuntu1
  Candidate: 1.1.93-1ubuntu1
  Version table:
 *** 1.1.93-1ubuntu1 500
500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

mm:~$ apt-cache policy openvpn
openvpn:
  Installed: 2.3.10-1ubuntu2
  Candidate: 2.3.10-1ubuntu2
  Version table:
 *** 2.3.10-1ubuntu2 500
500 http://pt.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

Regards,

Marco

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


** Tags: max-routes network-manager openvpn

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

Title:
  network-manager-openvpn max-routes support

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

2016-08-23 Thread Marco Hegenberg
I encountered the same problem for Ubuntu 16.04.

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

Title:
  gnome-session-flashback/Unity fails to start without hardware
  acceleration in cloud/remote environments
  (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1582142] Re: Gimp menu disaaperas from menu bar

2016-05-22 Thread Marco Righi
Fix after dist-upgrade (proposed activated)

** Changed in: gimp (Ubuntu)
   Status: New => Fix Released

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

Title:
  Gimp menu disaaperas from menu bar

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1582142] [NEW] Gimp menu disaaperas from menu bar

2016-05-16 Thread Marco Righi
Public bug reported:

Hi, the Gimp menus have disappeared from the top menu bar. It is
happened after an upgrade (from scratch, only /home was not formatted)
from Ubuntu 14.04 to Ubuntu 16.04.

Please contact me if you need more information.

Best
MR

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gimp 2.8.16-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May 16 11:14:20 2016
InstallationDate: Installed on 2016-04-28 (17 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gimp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Missing menu"
   
https://bugs.launchpad.net/bugs/1582142/+attachment/4663726/+files/Schermata%20del%202016-05-16%2011-21-46.png

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

Title:
  Gimp menu disaaperas from menu bar

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1093121] Re: Shotwell Crashes on Import

2016-04-16 Thread Marco Fornoni
*** This bug is a duplicate of bug 990947 ***
https://bugs.launchpad.net/bugs/990947

I had a similar segfault during import

I fixed the problem by installing gstreamer 1.6 from here
https://launchpad.net/~dan-witt/+archive/ubuntu/gstreamer

and gstreamer1.0-libav 1.59 from here
https://launchpad.net/~ricotz/+archive/ubuntu/experimental

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

Title:
  Shotwell Crashes on Import

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1565814] [NEW] Unable to click pause, stop or move progressbar in the video

2016-04-04 Thread Marco Giannini
Public bug reported:

Unable to click pause, stop or move the progressbar on totem 3.18.1
This is a video of the problem

Ubuntu 16.04 64-bit daily
Totem 3.18.1
driver nVidia current (304.131)

If i launch Totem from terminal and play a video I have this message

(totem:11965): Cogl-WARNING **: driver/gl/cogl-framebuffer-gl.c:1078: GL
error (1280): Invalid enumeration value

https://youtu.be/HdvlArbO0M8

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

** Summary changed:

- Unable to click pause, stop or scroll in the video
+ Unable to click pause, stop or move progressbar in the video

** Description changed:

- Unable to click pause, stop or move the bar on totem 3.18.1
+ Unable to click pause, stop or move the progressbar on totem 3.18.1
  This is a video of the problem
  
- Ubuntu 16.04 64-bit daily 
- Totem 3.18.1 
+ Ubuntu 16.04 64-bit daily
+ Totem 3.18.1
  driver nVidia current (304.131)
  
  If i launch Totem from terminal and play a video I have this message
  
  (totem:11965): Cogl-WARNING **: driver/gl/cogl-framebuffer-gl.c:1078: GL
  error (1280): Invalid enumeration value
  
- 
  https://youtu.be/HdvlArbO0M8

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

Title:
  Unable to click pause, stop or move progressbar in the video

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work

2016-01-25 Thread Marco Ceresa
I found what it seems to be a breakthrough on this issue. I hope it does
not only relate to my case.

I use a Colemak layout. Compared to the standard QWERTY, in Colemak the
T is where the F is in QWERTY, and where T is in QWERTY Colemak has a G.
See http://colemak.com/wiki/images/e/ef/Colemak_fingers.png for a visual
comparison.

Well, what do you know? ctrl-alt-t does not work, but ctrl-alt-g (which
is the qwerty shortcut for ctrl-alt-t) behaves as expected, firing up
the terminal.

It looks like the package responsible for the CTRL-ALT-T shortcut still
uses the default keyboard layout, not picking up the new layout (Colemak
in my case) at startup. Perhaps a loading order bug?

Can you guys test it and see if that's the case for you too?

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

Title:
  CTRL+ALT+T - shortcut to open Terminal is does not work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

2015-12-18 Thread Marco Hegenberg
** Also affects: putty (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work

2015-11-21 Thread Marco Ceresa
Same here, fresh new installation Ubuntu 15.10. 
Ctrl + Alt - t does not work despite being configured properly in the shortcuts 
config panel.

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

Title:
  CTRL+ALT+T - shortcut to open Terminal is does not work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1503525] [NEW] package libgnome2-common (not installed) failed to install/upgrade: impossível executar "stat" de './usr/share/doc/libgnome2-common' (que eu estava prestes a instalar): Erro de ent

2015-10-06 Thread Marco Barbieri
Public bug reported:

A preparar para desempacotar .../libgnome2-common_2.32.1-4ubuntu1_all.deb ...
A descompactar libgnome2-common (2.32.1-4ubuntu1) ...
dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libgnome2-common_2.32.1-4ubuntu1_all.deb (--unpack):
 impossível executar "stat" de './usr/share/doc/libgnome2-common' (que eu 
estava prestes a instalar): Erro de entrada/saída
A preparar para desempacotar .../libgnome2-0_2.32.1-4ubuntu1_i386.deb ...
A descompactar libgnome2-0:i386 (2.32.1-4ubuntu1) ...
dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libgnome2-0_2.32.1-4ubuntu1_i386.deb (--unpack):
 impossível limpar a sujeira em torno de './usr/share/doc/libgnome2-0' antes de 
instalar outra versão: Erro de entrada/saída
Erros foram encontrados durante o processamento de:
 /var/cache/apt/archives/libgnome2-common_2.32.1-4ubuntu1_all.deb
 /var/cache/apt/archives/libgnome2-0_2.32.1-4ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libgnome2-common (not installed)
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
Date: Wed Oct  7 01:26:33 2015
DpkgTerminalLog:
 A preparar para desempacotar .../libgnome2-common_2.32.1-4ubuntu1_all.deb ...
 A descompactar libgnome2-common (2.32.1-4ubuntu1) ...
 dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libgnome2-common_2.32.1-4ubuntu1_all.deb (--unpack):
  impossível executar "stat" de './usr/share/doc/libgnome2-common' (que eu 
estava prestes a instalar): Erro de entrada/saída
DuplicateSignature: package:libgnome2-common:(not installed):impossível 
executar "stat" de './usr/share/doc/libgnome2-common' (que eu estava prestes a 
instalar): Erro de entrada/saída
ErrorMessage: impossível executar "stat" de './usr/share/doc/libgnome2-common' 
(que eu estava prestes a instalar): Erro de entrada/saída
InstallationDate: Installed on 2015-10-06 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: libgnome
Title: package libgnome2-common (not installed) failed to install/upgrade: 
impossível executar "stat" de './usr/share/doc/libgnome2-common' (que eu estava 
prestes a instalar): Erro de entrada/saída
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 vivid

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

Title:
  package libgnome2-common (not installed) failed to install/upgrade:
  impossível executar "stat" de './usr/share/doc/libgnome2-common' (que
  eu estava prestes a instalar): Erro de entrada/saída

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1475788] [NEW] gnome-settings-daemon no autostart after qtcreator-plugin-ubuntu installation

2015-07-17 Thread Marco A. Harrendorf
Public bug reported:

Dear experts,

I am using Gnome Ubuntu 15.04 and everything was fine. However,  after the 
installation of the qtcreator-plugin-ubuntu I noticed that the panel and icon 
size was very small and also the wrong kind of icons and fonts was used in the 
Gnome Classic Shell.
For this reason, I removed all the packages which were installed together with 
the qtcreator-plugin-ubuntu.
Nevertheless, I observe still this problem.

The only solution which I found up to now is to launch the gnome-
settings-daemon manually after I have logged myself into the session.
After starting the gnome-settings-daemon the layout of the gnome session
is okay again.

I already tried a purge and reinstallation of gnome-settings-daemon,
gnome-settings-daemon-schemas, gnome-shell and ubuntu-gnome-desktop.
Nothing solved my problem.

Here is the output of the ~/.cache/gdm/session.log:

/etc/gdm/Xsession: Beginning session setup...
localuser:marco being added to access control list
localuser:marco being added to access control list
openConnection: connect: Datei oder Verzeichnis nicht gefunden
cannot connect to brltty at :0
upstart: upstart-event-bridge-main-Prozess (1668) wurde mit dem Status 1 beendet
upstart: upstart-event-bridge-main-Prozess beendet, wird neu gestartet
upstart: upstart-event-bridge-main-Prozess (1678) wurde mit dem Status 1 beendet
upstart: upstart-event-bridge-main-Prozess beendet, wird neu gestartet
upstart: upstart-event-bridge-main-Prozess (1680) wurde mit dem Status 1 beendet
upstart: upstart-event-bridge-main-Prozess beendet, wird neu gestartet
upstart: upstart-event-bridge-main-Prozess (1710) wurde mit dem Status 1 beendet
upstart: upstart-event-bridge-main-Prozess beendet, wird neu gestartet
upstart: upstart-event-bridge-main-Prozess (1727) wurde mit dem Status 1 beendet
upstart: upstart-event-bridge-main-Prozess beendet, wird neu gestartet
upstart: upstart-event-bridge-main-Prozess (1736) wurde mit dem Status 1 beendet


upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: at-spi2-registryd-main-Prozess beendet, wird neu gestartet
upstart: Neustart von at-spi2-registryd zu schnell, unterbrochen

Any ideas?
If I can provide further logs please tell me. I am really eager to solve this 
bug.

Ubuntu release:
Description:Ubuntu 15.04
Release:15.04
gnome-settings-daemon:
  Installiert:   3.14.2-3ubuntu1
  Installationskandidat: 3.14.2-3ubuntu1
  Versionstabelle:
 *** 3.14.2-3ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qtcreator-plugin-ubuntu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gnome3

** Also affects: qtcreator-plugin-ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Dear experts,
  
- I am using Gnome Ubuntu 15.04 and everything was fine. However,  after the 
installation of the qtcreator-plugin-ubuntu I noticed that the panel and icon 
size and also the wrong kind of icons and fonts were used in the Gnome Classic 
Shell was very small. 
+ I am using Gnome Ubuntu 15.04 and everything was fine. However,  after the 
installation of the qtcreator-plugin-ubuntu I noticed that the panel and icon 
size was very small and also the wrong kind of icons and fonts was used in the 
Gnome Classic Shell.
  For this reason, I removed all the packages which were installed together 
with the qtcreator-plugin-ubuntu.
  Nevertheless, I observe still this problem.
  
  The only solution which I found up to now is to launch the gnome-
  settings-daemon manually after I have logged myself into the session.
  After starting the gnome-settings-daemon the layout of the gnome session
  is okay again.
  
  I already tried a purge and reinstallation of gnome-settings-daemon,
  gnome-settings-daemon-schemas, gnome-shell and ubuntu-gnome-desktop.
  Nothing solved my problem.
  
  Here is the output of the ~/.cache/gdm/session.log:
  
  /etc/gdm/Xsession: Beginning session setup...
  localuser:marco being added to access control list
  localuser:marco being added to access control list
  openConnection: connect: Datei oder Verzeichnis nicht gefunden
  cannot connect to brltty at :0
  upstart: upstart-event-bridge-main-Prozess (1668) wurde mit dem Status 1 
beendet
  upstart: 

[Bug 1434081] [NEW] package shared-mime-info 1.3-1 failed to install/upgrade: ciclo nei trigger, abbandono

2015-03-19 Thread Marco Giannini
Public bug reported:

fresh install
no more information
Ubuntu 15.04 (daily 06/03/2015)

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: shared-mime-info 1.3-1
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
Date: Thu Mar 19 13:33:59 2015
DuplicateSignature: package:shared-mime-info:1.3-1:ciclo nei trigger, abbandono
ErrorMessage: ciclo nei trigger, abbandono
InstallationDate: Installed on 2015-03-19 (0 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306)
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.3-1 failed to install/upgrade: ciclo nei 
trigger, abbandono
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package vivid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1434081

Title:
  package shared-mime-info 1.3-1 failed to install/upgrade: ciclo nei
  trigger, abbandono

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1434081/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1420975] [NEW] nautilus crashed with SIGSEGV ubuntu 15.04

2015-02-11 Thread Marco Giannini
Public bug reported:

nautilus crashed with SIGSEGV ubuntu 15.04

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Feb 11 22:15:47 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2015-02-05 (6 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc3ee363ff3:  mov(%rax),%rax
 PC (0x7fc3ee363ff3) ok
 source (%rax) (0x) not located in a known VMA region (needed 
readable region)!
 destination %rax ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2015-02-11T10:07:14.797057

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


** Tags: amd64 apport-crash apport-failed-retrace vivid

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV ubuntu 15.04

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1415194] [NEW] nautilus crashed with signal 5 when launch from terminal

2015-01-27 Thread Marco Giannini
Public bug reported:

nautilus crashed with signal 5 when launching from terminal

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
Uname: Linux 3.18.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 27 21:03:59 2015
Disassembly: = 0x7f09cb3d7f90: Cannot access memory at address 0x7f09cb3d7f90
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2015-01-25 (2 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150124)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace vivid

** Information type changed from Private to Public

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

Title:
  nautilus crashed with signal 5 when launch from terminal

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking

2014-12-11 Thread Marco
I confirm the bug.

$ uname -a
Linux pc-marco 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.10
Release:14.10
Codename:   utopic

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

Title:
  Mouse pointer disappears and cursor stops blinking

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1292398] Re: Second screen position isn't saved from one session to another

2014-11-28 Thread marco tarabella
Same problem for me, fresh install of ubuntu gnome 14.04,
monitor change position when i reboot or when i do ALT f2 r
another thing: when i do alt f2 r the keyboard layout switch from italian to 
english.
hoping gnome team solve

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

Title:
  Second screen position isn't saved from one session to another

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 35223] Re: Laptop TFT monitor - brightness level is not saved

2014-11-16 Thread Marco Agnese
The same on this system:
Asus UX31A
Ubuntu 14.10 64 bit

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

Title:
  Laptop TFT monitor - brightness level is not saved

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1390068] [NEW] Gedit crashes when editing a file

2014-11-06 Thread Marco Gavanelli
Public bug reported:

I am using Linux Mint (I don't know if I should report bugs here or somewhere 
else).
After upgrading to Qiana, gedit has become very slow, in particular after long 
sessions of editing Prolog files,
and seems to be very slow in finding matching brackets.
I don't know if this can help, but I noticed that the bracket matching tries to 
match the symbols less than  and greater than 
as if I was editing an html file; maybe it gets confused and finds too many 
unmatched '' symbols?

Occasionally, it crashes. This happens rather often, but non-
deterministically.

This is the message I got:

(gedit:6314): Gdk-ERROR **: The program 'gedit' received an X Window System 
error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 3222167 error_code 16 request_code 18 (core protocol) 
minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gedit 3.10.4-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Thu Nov  6 13:34:59 2014
InstallationDate: Installed on 2013-02-27 (617 days ago)
InstallationMedia: Linux Mint 14 Nadia - Release amd64 (20121120)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Gedit crashes when editing a file

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1237355] Re: Logitech Ultrathin Touch Mouse needs to be repaired

2014-09-02 Thread Marco Bernasocchi
thx @rjb for #4 works perfectly

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

Title:
  Logitech Ultrathin Touch Mouse needs to be repaired

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1350621] [NEW] indicator-power battery with locked screen

2014-07-30 Thread Marco Agnese
Public bug reported:

When the screen is locked and the battery is very low the battery symbol is 
always white. 
Instead I would expect that it becomes red when is low and an exclamation mark 
inside when is very low (as it happens when the computer is not locked)

** Affects: indicator-bluetooth (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1350621

Title:
  indicator-power battery with locked screen

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1081019] Re: Benchmark for Harddisk fail

2013-11-06 Thread Marco Bottacin
i've got same bug even on my 13.04 and 13.10 ubuntu. Cant benchmark with
samsung ssd 840 120gb  and WDC green 1tb

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

Title:
  Benchmark for Harddisk fail

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1201889] [NEW] nautilus crashed with SIGSEGV in g_type_check_instance()

2013-07-16 Thread Marco Giannini
Public bug reported:

crash when i rename a file

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Tue Jul 16 18:56:33 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b'840x550+57+24'
InstallationDate: Installed on 2013-07-08 (8 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130707)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6b07621 g_type_check_instance+33:   mov
(%eax),%edx
 PC (0xb6b07621) ok
 source (%eax) (0x0020) not located in a known VMA region (needed 
readable region)!
 destination %edx ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_connect_data () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: apport-crash i386 need-i386-retrace saucy

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in g_type_check_instance()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1201535] [NEW] evolution-addressbook-factory crashed with SIGABRT in raise()

2013-07-15 Thread Marco Giannini
Public bug reported:

evolution has crashed while alone chatted with empathy

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.8.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Mon Jul 15 20:08:40 2013
ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory
InstallationDate: Installed on 2013-07-08 (7 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130707)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory
ProcEnviron:
 XDG_RUNTIME_DIR=set
 SHELL=/bin/bash
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
Signal: 6
SourcePackage: evolution-data-server
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: evolution-addressbook-factory crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace saucy

** Information type changed from Private to Public

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

Title:
  evolution-addressbook-factory crashed with SIGABRT in raise()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1200745] [NEW] eog crashed with SIGSEGV during the upgrade

2013-07-12 Thread Marco Giannini
Public bug reported:

The crash happened while I was updating the system from the terminal
with the dist-upgrade

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: eog 3.8.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Wed Jul 10 13:09:07 2013
ExecutablePath: /usr/bin/eog
InstallationDate: Installed on 2013-07-08 (2 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130707)
MarkForUpload: True
ProcCmdline: eog /home/marco/Schermata\ del\ 2013-07-10\ 12:49:26.png
ProcCwd: /home/marco
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb689a15c g_type_check_instance_cast+44:  mov
(%eax),%eax
 PC (0xb689a15c) ok
 source (%eax) (0x) not located in a known VMA region (needed 
readable region)!
 destination %eax ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: eog
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 g_object_set_property () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: eog crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: apport-crash i386 need-i386-retrace saucy

** Information type changed from Private to Public

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

Title:
  eog crashed with SIGSEGV during the upgrade

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1164016] Re: restore type-ahead find

2013-07-03 Thread Marco Lackovic
I switched to Kubuntu, now happily using Dolphin in place of
Nautilus/File.

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

Title:
  restore type-ahead find

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 878339] Re: Copy disk - disk to copy disappears when 'copy' button clicked

2013-05-27 Thread Marco Lackovic
Still present on Ubuntu 13.04 / brasero 3.6.1 amd64.

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

Title:
  Copy disk - disk to copy disappears when 'copy' button clicked

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1164016] Re: restore type-ahead find

2013-05-22 Thread Marco Lackovic
I also find the removal of type-ahead very frustrating. I think an
option to re-enable it should be available.

In my opinion the previous behavior was more intuitive: if I wanted to
search fo something I would have used the search function at hand.
Before it was possible to discern the two things, (1) go to the
file/folder in the current folder, (2) search for a file/folder in the
current folders and subfolders. Now only option (2) is possible.

As a workaround, I followed the following suggestion and installed Nemo:
http://askubuntu.com/questions/285793/how-do-i-disable-recursive-search-in-nautilus-3-6

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

Title:
  restore type-ahead find

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


  1   2   3   4   5   6   7   >