Public bug reported:
Thunderbird received a version bump today. After Update Manager
installed the new version, any attempts to launch Thunderbird result in
an immediate crash. This happens even if I remove ~/.thunderbird
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1016818
Title:
Immediate crash on startup
Status in “thunderbird” package in Ubuntu:
New
Bug description:
Thunderbird received
Attached is an strace of startup with a deleted ~/.thunderbird
** Attachment added: Strace of startup (strace -f -o tb.strace thunderbird)
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1016818/+attachment/3201279/+files/tb.strace
--
You received this bug notification because
I submitted the crash numerous times to Mozilla. It didn't give me any
feedback other than saying I could relaunch. In any event I did use
apport to report the bug here and the doc you posted says Note that the
Apport hook provided from Firefox and Thunderbird 13 will automatically
attach the
Crash ID: bp-ce7dfec4-b140-4b3d-8cbc-ca5a72120623
Crash ID: bp-1ecdd5bf-c42f-49eb-9c54-0dfc82120622
Crash ID: bp-ec5f55d4-db94-4fa4-a17c-ce3d82120622
Crash ID: bp-012114a9-6ba4-41f1-a532-8a5042120622
Crash ID: bp-257ae38f-21d5-4eea-88e9-9c2862120622
--
You received this bug notification because
Public bug reported:
After upgrading to quantal suspend from the menu no longer works (pm-
suspend works just fine). .xsession-errors contains this relevant line:
gnome-session[2937]: libupower-glib-CRITICAL: up_client_get_can_suspend:
assertion `UP_IS_CLIENT (client)' failed
ProblemType: Bug
@Johann, thank you for that pointer. I had tried the official Samsung
driver earlier which has the world's worst installer and on printed to
half the page width.
Using the latest driver from bchemnet I found the following:
* Using the Samsung Configurator meant no print jobs came out and I was
Even after capitalization and using the config above I still get the
error.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vinagre in Ubuntu.
https://bugs.launchpad.net/bugs/992724
Title:
can't open .vnc file anymore after upgrading
That isn't the file in question - Osmos is something I installed while
the system was running natty a few months ago. I had to do a fresh
install of oneiric but kept my home directory so you are seeing older
detritus.
The file in question from this error message is Google Music Manager but
it
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/891811
Title:
Yahoo account fails to login
Status in “empathy” package in Ubuntu:
New
Bug description:
Ever since installing 11.10
Public bug reported:
Ever since installing 11.10 I cannot login to my Yahoo account. I've
deleted and recreated the account several times, each time getting the
same problem. After trying for several seconds Empathy says Connection
can't be established with no further information.
ProblemType:
** Attachment added: Log file - my Yahoo id is grotgrot
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/891811/+attachment/2600040/+files/mission-control-17-11-11_12-45-33.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Just to be clear the problem I reported is not invalid nor has it been
fixed. I'm using my Yahoo account name not email address as is shown in
the logs. Whoever was using an email address hijacked this issue.
--
You received this bug notification because you are a member of Desktop
Packages,
*** This bug is a duplicate of bug 868188 ***
https://bugs.launchpad.net/bugs/868188
** This bug has been marked a duplicate of bug 868188
Internal Error ...google-chrome-stable_current_amd64.deb could not be
opened
--
You received this bug notification because you are a member of
Why is this marked as incomplete? Confirmation and log files have been
provided. No additional information has been asked for.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/891811
@Muhammad: That is a completely different issue and a user error that
has somehow been attached to this bug and is not relevant.
As you can see from my logs I am using the username only and not an
email address. Please set back to confirmed.
--
You received this bug notification because you
I'm having this problem on Precise. The VNC viewer does start
fullscreen but then after a few seconds the top and bottom panels
intrude.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
I gave up on streaming completely and download everything locally first.
Even when the file is on disk I encounter banshee getting confused. The
UI will show that it is playing, but it isn't. Pressing play/pause has
no effect. Only double clicking on the file and moving the slider to the
right
Public bug reported:
There is no typing break setting in gnome-control-center. This is the
text from the package description:
This package contains the daemon which is responsible for setting the
various parameters of a GNOME session and the applications that run
under it. It handles the
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/991577
Title:
Package description says Typing break is a setting
Status in “gnome-control-center” package in Ubuntu:
New
Public bug reported:
In dconf I have the network-interface configured to lo (loopback). I
use ssh with port forwarding so I don't need or want vino externally
accessible. While port 5900 ends up restricted to localhost, port 5800
is not:
$ netstat -an | grep -i tcp | grep -i listen
tcp
Which driver did you get working in the end? My experience was having 3
monitors work fine in raring 13.04, until the driver that is in Saucy
13.10 at which point it started pulling the only two monitors at a
time stunt. Bug 1242180
--
You received this bug notification because you are a
xrandr output running command line from comment 2. Raring:
crtc 0:1920x1200 60.0 +1920+0 DP2
crtc 1:1920x1080 60.0 +3840+0 HDMI1
crtc 2:1920x1080 60.0 +0+0 HDMI3
Saucy livecd:
xrandr: Configure crtc 2 failed
crtc 0:1920x1080 60.0 +3840+0 HDMI1
crtc 1:1920x1080
@RichardNeill - already did all that as mentioned in comment 4 which
also has the advantage of working on the livecd.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Kernel 3.12 even in the prereleases fixed this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no longer work
It isn't invalid. This is a very real issue affecting the existing
Ubuntu release.
I have been personally compiling 3.12 kernels from kernel.org as a
workaround that works for me, so I don't need anything.
I'd suggest closing as Won't Fix since Ubuntu won't provide a fix.
--
You received this
If Ubuntu would actually backport the 3.12 kernel to Saucy then go for
it. The kernel team PPA does not do 3.12 for saucy. At a minimum
3.12.6 is needed due to lots of btrfs fixes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
All I know is that whatever the cause was, it was fixed in 3.12 even in
the rcs. I have no idea what the actual fix was.
Kernel 3.11 end of lifed November last year. I also use btrfs for which
there have been maintenance patches in 3.12.
I followed the Kernel Build and Installation section at
You do know that no one knows what the fix is, only that it is in 3.12?
You can see that Timo gave up trying to find it in mid-November. If
Ubuntu is actually going to figure out the fix and backport it, then go
for it. However I am extremely sceptical and had to devise my own
workaround.
--
** Attachment added: xorg log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884152/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Public bug reported:
I've just upgraded from raring. There I had 3 monitors attached to my
Intel HD Graphics 4000 (i7 3770 cpu) where it all works perfectly. (Two
monitors are identical flanking my centre displayport monitor.)
In saucy I can get any two monitors working, and any attempt to get
The failures to set occur using the graphical tool from system settings,
as well as the xrandr command line
xrandr --output DP2 --primary --auto --output HDMI3 --auto --left-of DP2
--output HDMI1 --auto --right-of DP2
** Attachment added: xrandr output
I also ran xorg-edgers-live-test as described in
https://wiki.ubuntu.com/XorgOnTheEdge and that didn't help. Restored
from my backup and everything works fine.
(xorg-edgers-live-test also needs updating - it tries to restart gdm
when it should be restarting lightdm)
** Attachment added: xrandr
** Attachment added: xorg log from raring where everything works fine
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884309/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Booting the raring kernel (3.8.0-33) under saucy results in all 3
monitors working correctly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy
I installed 3.12 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.12-saucy/
It failed to boot. With normal boot there was no further progress after
ramdisk loading. In recovery mode the kernel said it failed to execute
/init but gave no further details.
I am now trying
The drm-nightly from previous comment works
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no longer work
Status in
I'm confused as to what the goal is. The drm-intel-nightly works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no
This didn't work:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.7-saucy/
This did:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/
It would be ideal if you gave me a list of urls like above in preferred
testing order
--
You received this bug notification because you are
Can you point me to other builds you want me to try, ideally as ppa
links like the above?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy
I didn't know how much of this stuff had been folded in systemd, or is
affected by udev/hotplug etc :-)
In any event, I just retested and plugging the mouse into a 14.10
machine has upower show the mouse, and plugging into two different 15.04
systems will not show it (one upstart, one systemd).
The power manager plugin is greyed out so I can't add it -
http://i.imgur.com/X5K3loz.png
$ upower -d
Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: no
updated: Fri 24 Apr 2015 02:38:01 PM PDT (1019180 seconds ago)
has history: no
has
Public bug reported:
Symptom: booting 18.04 kernel reduces resolution available while 17.10
kernel (on 18.04) does not
I have a 3 identical monitor setup - all at 2560x1600 native resolution.
If I boot the current 18.04 kernel 4.15.0-13-generic then the third
monitor does not have the native
** Attachment added: "Xorg log when booting with 18.04 kernel"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+attachment/5109717/+files/newkernel.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
A victim of some other fix. This regression can be prevented by adding
amdgpu.dc=0 to the kernel command line.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1762818
Title:
Regression:
45 matches
Mail list logo
