Re: [Bug 1891771] Re: gdm3 crashes after upgrade from bionic to focal but lightdm and sddm work fine

2020-08-17 Thread Luca Maranzano
Hello Daniel,

here you can find the link:

https://errors.ubuntu.com/user/a0bccc0d41c89b42afbe332929a7f00566720fe2fcfc8f4ca657778404328e77f704f6088efe855865488a2f9635243b26b54e543fe6e58c26f7de6c73d1df8c

Thanks,
Luca


On Mon, Aug 17, 2020 at 5:55 AM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
> ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
>
> ** Changed in: gdm3 (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891771
>
> Title:
>   gdm3 crashes after upgrade from bionic to focal but lightdm and sddm
>   work fine
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Hi all,
>
>   after upgrading from bionic to focal I switched from lightdm to gdm3
>   to use Gnome Desktop.
>
>   Gdm3 crashes systematically when enabled as default display-manager
>   with a blank display with the following message:
>
>   Oh no! Something has gone wrong.
>   A problem has occurred and the system can't recover. Please contact a
> system administrator.
>
>   In /etc/gdm3/custom.conf I've tried the following settings:
>
>   WaylandEnable=false   -> crash
>   WaylandEnable=true-> crash
>
>   I've enabled Debug but I cannot find any correlation with the error
>   message.
>
>   Gdm version 3.34.1-1ubuntu1.
>
>   Switching to another display manager like lightdm or sddm solves the
> problem.
>   I've a Dell Inspiron with Intel U620 graphic card.
>   The problems happens with the laptop display alone but also with
> external monitor connected via HDMI.
>
>   Thanks in advance for your help.
>
>   Regards
>   Luca
>   dpkg
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gdm3 3.34.1-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>   Uname: Linux 5.4.0-42-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.6
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Aug 15 23:06:37 2020
>   InstallationDate: Installed on 2016-12-14 (1340 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   SourcePackage: gdm3
>   UpgradeStatus: Upgraded to focal on 2020-08-11 (4 days ago)
>   mtime.conffile..etc.gdm3.custom.conf: 2020-08-15T00:22:27.116452
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1891771/+subscriptions
>

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

Title:
  gdm3 crashes after upgrade from bionic to focal but lightdm and sddm
  work fine

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

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

[Bug 1891771] [NEW] gdm3 crashes after upgrade from bionic to focal but lightdm and sddm work fine

2020-08-15 Thread Luca Maranzano
Public bug reported:

Hi all,

after upgrading from bionic to focal I switched from lightdm to gdm3 to
use Gnome Desktop.

Gdm3 crashes systematically when enabled as default display-manager with
a blank display with the following message:

Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. Please contact a system 
administrator.

In /etc/gdm3/custom.conf I've tried the following settings:

WaylandEnable=false   -> crash
WaylandEnable=true-> crash

I've enabled Debug but I cannot find any correlation with the error
message.

Gdm version 3.34.1-1ubuntu1.

Switching to another display manager like lightdm or sddm solves the problem.
I've a Dell Inspiron with Intel U620 graphic card.
The problems happens with the laptop display alone but also with external 
monitor connected via HDMI.

Thanks in advance for your help.

Regards
Luca
dpkg

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 15 23:06:37 2020
InstallationDate: Installed on 2016-12-14 (1340 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-08-11 (4 days ago)
mtime.conffile..etc.gdm3.custom.conf: 2020-08-15T00:22:27.116452

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


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

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

Title:
  gdm3 crashes after upgrade from bionic to focal but lightdm and sddm
  work fine

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

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

[Bug 1217191] Re: Send document as Open Document Text fails to attach doc when using Thunderbird

2015-05-05 Thread Luca Maranzano
If I run this from the shell:

thunderbird -compose
to='j...@example.com,ka...@example.com',cc='brit...@example.com',subject='dinner',body='How
about dinner tonight?',attachment='/home/liuk/test.txt'

as in the example on the Thunderbird website
(http://kb.mozillazine.org/Command_line_arguments_%28Thunderbird%29) , a
new window with the right fields filled and with the attachment is
opened, so it seems more a LibreOffice issue which is not invoking
Thunderbird with correct parameters.

Tested on :
lsb_release -sd
Ubuntu 14.04.2 LTS

thunderbird -v
Thunderbird 31.6.0

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

Title:
  Send document as Open Document Text fails to attach doc when using
  Thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1217191/+subscriptions

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


[Bug 974480] Re: Notification area whitelist is obsolete

2013-08-07 Thread Luca Maranzano
Today my unity has been upgraded from
7.0.0daily13.04.18~13.04-0ubuntu1systray1 to
7.0.0daily13.06.19~13.04-0ubuntu1 and so no more systray :-(

May be that timekiller will update his PPA, but if you are impatient and
you want to apply his systray patch and rebuild Unity the command to use
for getting the right Unity source code is this:

 bzr branch lp:unity/7.0

HTH
Liuk

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

Title:
  Notification area whitelist is obsolete

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

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


[Bug 974480] Re: Notification area whitelist is obsolete

2013-04-29 Thread Luca Maranzano
I've upgraded from 12.04 LTS to 13.04 and for the moment I need to have some 
important applications like SpiderOak and Druva InSync workig fine, so kudos to 
#42 @Jason aka timekiller++ for his work, it works for me like a charm.
I'm a Unity fan, but it is not affordable for me to give up on important 
applications that I use only for this imposed constraint.
IMHO AppIndicator is really a good framework, but in general I think that users 
*must have* the possibility to choose to have support for the old deprecated 
systray, expecially becasue they do not have the control over the fact that the 
those applications are not (yet?) using AppIndicator for whatever reason.
I think that this is a sort of freedom that has always characterized the Open 
Source from which Linux (and Ubuntu) comes.
Just to be propositive, one way to spread the adoption of AppIndicator is to do 
the right propaganda about its advantages and features with the developers of 
the (most used?) applications that Ubuntu users are using.
I'll start with Druva just after this post ;-)
Just my 2 cents.

Luca

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

Title:
  Notification area whitelist is obsolete

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

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


[Bug 974480] Re: Notification area whitelist is obsolete

2013-04-29 Thread Luca Maranzano
I'm happy to share with you that I already got a positive response from
Druva about AppIndicator:

http://gsfn.us/t/2yv3x

I'm quite convinced that time is not yet mature to be so drastic in
abandoning the systray.

Luca

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

Title:
  Notification area whitelist is obsolete

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

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


[Bug 1140060] Re: SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not installed

2013-04-26 Thread Luca Maranzano
Dear Matthew, is there a 4.9 beta available to do some test? 
I've just upgraded to Raring and using spideroak version 9948 (4.7) but the 
AppIndicator integration is not (obviously?) working, even if SpiderOak is 
starting fine.

Thanks!
Luca

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

Title:
  SpiderOak crashes: Settings schema 'com.canonical.Unity.Panel' is not
  installed

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

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


[Bug 864739] Re: Ubuntu doesn't work on HP Elitebook 8560w

2012-01-28 Thread Luca Maranzano
Hello all,

just to report that I'm currently using Ubuntu 11.10 64 bit on a 8760W
(model number LG760ET) with the ATI M5950 graphic card and I'm quite
happy with no particular issues after 3 days of heavy usage.

I'had only a really strange issue after the first installation. From the
Live CD all was working fine and installation went really really smooth,
but at the first reboot the screen was shifted like the attached photo!
I was able to enable the ATI fglrx proprietary driver and after the
reboot all was ok.

All is working fine so far, temperatures are quite cool and acpi reports
this:

$ acpi -t
Thermal 0: ok, 0.0 degrees C
Thermal 1: ok, 0.0 degrees C
Thermal 2: ok, 0.0 degrees C
Thermal 3: ok, 0.0 degrees C
Thermal 4: ok, 0.0 degrees C
Thermal 5: ok, 25.0 degrees C
Thermal 6: ok, 36.0 degrees C
Thermal 7: ok, 35.0 degrees C
Thermal 8: ok, 43.0 degrees C
Thermal 9: ok, 46.0 degrees C

If you need power and big screen with Full HD resolution I'd suggest this model 
which is a little cheaper than the NVidia ones.
The 8560W with the ATI card is actually the same exact hardware a part the LCD 
size.

HTH
Cheers,
Luca


** Attachment added: Strange shifted screen after installation
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/864739/+attachment/2698895/+files/Ubuntu11-10-SplitScreen-on-HP8760W.jpg

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

Title:
  Ubuntu doesn't work on HP Elitebook 8560w

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

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


[Bug 864739] Re: Ubuntu doesn't work on HP Elitebook 8560w

2011-12-18 Thread Luca Maranzano
Please note that the 8560w may have the NVidia Quadro 1000 (with the
Optimus feature...)  or the AMD M5950 graphic card (no optimus).

I think that the nouveau.modeset=0 patch is strictly NVidia related.

So may be that the different behaviours reported may be related to a
different hardware configuration.

It should be better to report the exact graphic card used.

Cheers,
Luca

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

Title:
  Ubuntu doesn't work on HP Elitebook 8560w

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

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


[Bug 563156] Re: [ATI Graphics][Lucid] laptop runs hot, shorter battery life, fan always on

2010-11-21 Thread Luca Maranzano
I've been struggling with this issue since my upgrade to 10.4. I've an
HP 8530p with ATI RadeonHD 3650, Ubuntu 64 bit.

Today I did the following and things seem to get better:
- Purged all the fglrx packages from Catalyst 10.10
- Installed Catalyst 10.11 (fglrx version 8.791)
- aticonfig --initial -f
- aticonfig --acpi-services=off
- from the Catalyst Control Center the PowerPlay option is enabled

Now the temperature is like this:
l...@spock:~$ aticonfig --odgt

Default Adapter - ATI Mobility Radeon HD 3650
  Sensor 0: Temperature - 49.00 C
l...@spock:~$ acpi -t
Thermal 0: ok, 16.0 degrees C
Thermal 1: ok, 43.0 degrees C
Thermal 2: ok, 55.0 degrees C
Thermal 3: ok, 24.9 degrees C
Thermal 4: ok, 45.0 degrees C
Thermal 5: ok, 30.0 degrees C

Thermal 2 with 9.10 was always about 50, and before the reinstallation
of today, Thermal 2 has always been around 60 or more.

So this could be a good trade off :-)

HTH
Luca

-- 
[ATI Graphics][Lucid] laptop runs hot, shorter battery life, fan always on
https://bugs.launchpad.net/bugs/563156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


[Bug 577477] Re: gdm fails to start sitting on plymouth boot

2010-10-14 Thread Luca Maranzano
Hello all,

I've upgraded from 9.10 to 10.4 two days ago, and I've enabled Plymouth, but 
I'm facing the same problem: the system boots, Plymouth is running for some 
seconds, then the progression bar stops and the switch to gdm does not happen.
The system is alive since if I press the power button it will do the shutodwn 
nicely.
Besides, if I disable gdm from upstart, I get the console login, and if I start 
gdm from the vty all is fine. So I really believe that the problem is the 
switching from plymouth to gdm.
My system is an HP EliteBook 8530p, with fglrx driver. I'm using the uvesafb 
module.
gdm   2.30.2.is.2.30.0-0ubuntu4
plymouth   0.8.2-2ubuntu2

Kernel:
Linux spock 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:05:27 UTC 2010 
x86_64 GNU/Linux

How can I debug more deeply this ?

Thanks,
Luca

-- 
gdm fails to start sitting on plymouth boot
https://bugs.launchpad.net/bugs/577477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


[Bug 314600] Re: [HD 3650] fglrx versions newer than 8.543 cause system hang and panic

2009-09-22 Thread Luca Maranzano
Hi,

I faced the fglrx bug on my Jaunty upgrade with my EliteBook 8530p and ATI HD 
3650.
I solved it with the Catalyst version 9.5 and 9.6 (8.620) which seems quite 
stable (the --acpi-services=off was still necessary) downloaded from the ATI 
site. 

I've also tryed the Catalyst 9.7, 9.8 and the latest 9.9. But:
- 9.7 and 9.8 have an annoying black flickering when paging up and down (for 
example inside a Gnome Terminal at full screen, or in Firefox)
- 9.9 is IMHO completely broken, just after the installation I got a Kernel 
NULL pointer error

Obviously I'm sticking to 9.6 :-)

So my question is: which version of Catalyst are you using for Karmic?

Thanks.
Luca

-- 
[HD 3650] fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


Re: [Bug 346028] Re: [ATI driver specific] Ubuntu Jaunty hangs after usplash with fglrx 8.600 or 8.6002

2009-06-22 Thread Luca Maranzano
Which version of fglrx? The one in the Jaunty repository (package version
should be 8.6002 I suppose) or the last one from the ATI site, i.e. Catalyst
9.6 which should get you after the build process these packages:

fglrx-amdcccle_8.620-0ubuntu1_amd64.deb
fglrx-kernel-source_8.620-0ubuntu1_amd64.deb
fglrx-modaliases_8.620-0ubuntu1_amd64.deb
xorg-driver-fglrx_8.620-0ubuntu1_amd64.deb
xorg-driver-fglrx-dev_8.620-0ubuntu1_amd64.deb

Ciao,
Luca



On Sat, Jun 20, 2009 at 4:49 PM, David Weiss dwei...@gmail.com wrote:

 I just updated to the latest release of jaunty and the video went out
 again.  I tried the fix that was mentioned above (removing fglrx) but
 that did not fix the problem this time.  Any ideas?

 --
 [ATI driver specific] Ubuntu Jaunty hangs after usplash with fglrx 8.600 or
 8.6002
 https://bugs.launchpad.net/bugs/346028
 You received this bug notification because you are a direct subscriber
 of the bug.

 Status in AMD fglrx video driver: Fix Released
 Status in “fglrx-installer” source package in Ubuntu: Confirmed
 Status in “usplash” source package in Ubuntu: Invalid

 Bug description:
 I updated my Ubuntu to the latest jaunty Alpha 6. On reboot, after the new
 progress completes, my screen flashes a couple of times and all I get after
 that is a messed up screen with a blurry text saying something like Asus.
 It just hangs there.

 Let me know what information I can provide and I can try to connect an
 ethernet cable and get that from the recovery mode. BTW I hope I got the
 package right.

 Thanks,
 ~Apoorva


-- 
[ATI driver specific] Ubuntu Jaunty hangs after usplash with fglrx 8.600 or 
8.6002
https://bugs.launchpad.net/bugs/346028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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