I have *no* nVidia card present on my laptop running with Intel HD4000
*only*, yet I have the same issue. Fresh install of Ubuntu 16.10. I am
unable to start GDM as a service (systemctl), but I am able to start it
directly ('gdm3') just fine as root from a TTY.
--
You received this bug
Well, I just did discovered something by accident. I *DID* manage to
start GDM3 just by executing 'gdm3' as *root* from a TTY. I am now able
to login just fine and GNOME works fine.
Launching GDM as a service (systemctl) does not work, though. Why is
this so? And what can I do to resolve the
Similarly to comment #74, I have exactly the same symptoms on a Samsung
laptop with Intel HD4000 graphics (i.e. *no* nVidia or any other video
card is/was present). Moreover, it's a fresh install of Ubuntu 16.10. It
is also of note that I've never had this issue before on the same
machine with any
Just noting that installing version 2.1-0ubuntu7.2 from Vivid and
pinning it works as workaround.
In addition, I tend to agree with comment #6 on the importance of having
an adequate understanding of the severity of the issue. Nobody can
expect and force all those faulty Radius servers to be
The patch seems to have been included in Linux 3.13.11.5, released on July
18[1]. Looking forward to its inclusion in the official Ubuntu kernel
builds.
1. http://patchwork.ozlabs.org/patch/370345/
2014-08-06 20:18 GMT+02:00 29185159 celiosidneisi...@gmail.com:
ops... broadcom
--
You
*** This bug is a duplicate of bug 1331654 ***
https://bugs.launchpad.net/bugs/1331654
Just noting that the patch seems to have been included in Linux 3.13.11.5,
released on 18 July[1]. Looking forward to its inclusion in the official
Ubuntu kernel builds.
1.
Hey all. Apologies for the long silence. I confirm that shacharr's
prebuilt packages with the cherry-picked
2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 commit fixed the issue for me.
It must be included it in the next kernel update for Trusty.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1331654 ***
https://bugs.launchpad.net/bugs/1331654
Since shacharr's prebuilt packages with the cherry-picked
2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 commit fixed the issue for me
and you, I'm marking this as a duplicate. The patch must be included it
in
I believe it indeed is a duplicate of your report. Just let me check if
2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 solves the issue on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315277
Oh, I see that you've already uploaded it on dropbox! I will give it a
test run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331654
Title:
[Dell Inspiron 1525] Cannot resume from suspend
To
Dear shcharr,
A prebuilt 3.13.0-30.54 with that patch applied would be nice to have. I
could give it a test on my machine as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331654
Title:
Dear Iuri, I have reported your bug with your comments to the upstream
bugzilla as https://bugzilla.kernel.org/show_bug.cgi?id=78381 Feel free
to comment if you have anything else to add or want to change something.
** Bug watch added: Linux Kernel Bug Tracker #78381
Dear Chris, have you *actually* read Iuri Diniz's messages you are thanking
him for? At this stage your template messages ARE NOT helpful and are
redundant.
Let me put it this way. First, he's having the same damn hardware as many
other users facing this bug that no one from the Ubuntu kernel
Dear Iuri, maybe upstream (or even freedesktop.org's) kernel folks can help
with this? I don't think this bug has been reported to their bugzilla.
Maybe it's worth to report it there and expect their comments that would
help you out with these tags?
2014-06-17 4:24 GMT+02:00 Iuri Diniz
with answering that very exact question.
2014-06-18 1:22 GMT+02:00 Christopher M. Penalver
christopher.m.penal...@gmail.com:
Žygimantas Beručka, as you can respect, this isn't userspace, and the
triaging is done differently, both down and upstream. So, as you put it,
he can have the same
Has this bug been reported on the kernel.org's/freedesktop.org's
bugzilla at all? Since it exists in mainline builds it's an upstream
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315435
Title:
Hey Adrian,
Let me just quote what I wrote above 11 months ago:
First of all, I have installed SAMSUNG BIOS upgrades from within Windows 8,
then reduced Windows partition to leave around 40–50 Gb of free space, the
remaining free space on a HDD was allocated for Ubuntu's /home directory.
Next I
Andrea, it should work just fine. Which basically means: there were no new
reports of machines getting bricked that I know of since many months. For
example, I've been using np530U3C-A05 in UEFI mode just fine since June.
2014-05-09 11:24 GMT+02:00 Andrea Biolo andrewbiol...@gmail.com:
Hi! I
Okay, I fooled around here with several mainline kernel versions,
letting them run for a decent amount of time, just to make sure the bug
is hit on resume.
3.13.0 – the bug IS triggered. I just booted, logged in and forgot about
it. When I came back to it, it was sleeping; on resume the bug got
Maybe it's worth the time to involve Unity/compiz devs in this? After
all it's very likely to be their code which screws the kernel up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310823
Title:
Played around with Unity/Compiz (moving windows, opening dash, etc.)
while running 3.13rc1 to make sure the bug is triggered. And after a
suspend it didn't come back. This leaves us with 3.12.19 being the last
version which is known for working fine, and 3.13rc1 is the first
version which is
I found out the last working version to be 3.12.19 (latest in the
series) and the first buggy one – 3.13rc1. Therefore the offending
commit is somewhere in the early 3.13 series. I'm afraid cannot do much
more about this, as I am not a too tech-savvy user. I have no experience
in doing the
I suspect that too as I already mentioned I can suspend/resume before a
Unity/compiz session is actually started. With only a lightdm running it
just works. You trying out a GNOME session just confirms it.
However, it still means there's a bug in the kernel since a piece of
third-party software
Public bug reported:
The issue hit the system right after uprading from Saucy to Trusty.
Ubuntu Trusty freezes on resume from a suspend on a DELL Inspiron 1525
machine. All I see is just LEDs for disk (just blinks for a moment) and
wifi (stays lit), fan noise and a black screen. No mouse cursor,
Christopher, I reported the same issue as bug #1315277
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310823
Title:
[Dell Inspiron 1525] Ubuntu freezes when lid closed
To manage notifications
Joseph, I've already mentioned that I am unable to test 3.15rc since it
boots with a completely black screen start to finish. I don't know what
is the cause and how to circumvent it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
By the way, is it possible to collect any freeze data which might shed a
light on a possible cause?
When I boot after a unclean/hard reboot and log into a Unity session, I
see a number Apport dialog windows (3 to 5 usually). However, when I
press 'OK' on one of them, enter my password, it starts
Thanks, Christopher. I had wanted to submit those logs apport collects
on a fresh boot after the freeze way before, but no matter how many
times I tried, once I press the submit button, it would just close and
nothing happens. Will try to do it later the way you're suggesting.
And concerning my
I'm having the same issue with the same Inspiron 1525. I have also tried
booting with mainline 3.14.1{,2}, but the issue is still present in
these versions. I haven't tried 3.15rc as of yet since the Broadcom
wireless kernel module fails to build with it.
I just tried, however, running the
I also noticed that if I try to suspend the system *before* actually
logging in into a Unity session, that is, while lightdm alone is
running, resume from suspend works flawlessly. But once I login to a
Unity/compiz session, there's no comming back from a suspend.
--
You received this bug
I have some results from my investigation. I just tried a number of
mainline builds: 3.13rc1, 3.13.{0,6,8,9,11}. With all of them, that is,
from the first RC to the most current release in the 3.13 series,
resuming works flawlessly. It is also of note, as have already been said
above, that
Bad news. I just removed all the kernels I tested except the last one
(3.13.11), and after some time tried to suspend it again. It froze again
while coming back from a suspend. If this bug likes to hide like this
and activates just on some condition, it will be hard to nail it down. I
will try,
Public bug reported:
When Tomboy search source is ENABLED in Unity Dash, a simple search is
enough to trigger launching of new Tomboy instances. Once the source is
DISABLED, no search triggers this bug.
How to reproduce: Enable the Tomboy source, open Dash and start typing
something what might
*** This bug is a duplicate of bug 1307128 ***
https://bugs.launchpad.net/bugs/1307128
I believe this is a Unity's bug, not Tomboy's. I found out how it can be
reproduced at will. See
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307128
** This bug has been marked a duplicate of bug
Public bug reported:
It is impossible to maximize EasyTAG's main window. Once I double click
the title bar under GNOME, only window decorations/shadows change at the
edge of the window; the size remains the same. See attached screenshots.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package:
** Attachment added: This is how an unmaximized window looks
https://bugs.launchpad.net/ubuntu/+source/easytag/+bug/1307020/+attachment/4082155/+files/easytag%20unmaximized.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any ideas what an average user can do to help solving this?
I reported this bug on the upstream bugzilla.
** Bug watch added: GNOME Bug Tracker #719990
https://bugzilla.gnome.org/show_bug.cgi?id=719990
** Also affects: gnome-media via
https://bugzilla.gnome.org/show_bug.cgi?id=719990
Chris, a recent GTK3 update (3.8.6-0ubuntu2) from the saucy-proposed
overrides your version and pinning the right version is quite a hassle
since it requires downgrading of quite a number of packages. Would you
be so kind to build a newer version with your patch included?
It's a pity upstream
Having the most recent packages from the -proposed, I noticed some
strange and different scenarious.
Firs of all, on my laptop running GNOME 3.8 from the GNOME3 PPA:
1. I _am_ able to change the keyboard layout with the (now default) Super+Space
combo; however,
2. Whenever I press my old combo
Christopher, nothing fancy in my case, it's basically a default Unity
configuration with just the workspace switcher turn back on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
I had this issue to, but the package in your ppa fixed it. Thanks!
By the way, wouldn't it be reasonably to push your patched version into
the official repos so that other folks would get the fix without having
to swim trough google or launchpad first?
--
You received this bug notification
Ladies and gentelmen, this is a farce. What age are we living in? For at
least three releases they didn't care about GNOME lacking the keyboard
indicator because of how they mixed up wrong versions of GNOME and IBus
packages. It took 1.5-2 years to get this fixed. Thanks! Alas the rocket
In the upstream bug report one user reported:
I have a samsung series 9 np900x3c affected by the same issue.
I've noticed a pattern in this bug's behavior and I would like to know if
someone else can confirm the following:
The bug triggers ONLY if a suspend/resume (hibernate/thaw) event
I can confirm – it's fixed in Saucy! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045914
Title:
Keyboard layout doesn't show in GNOME Shell session
To manage notifications about this bug
I started having this on my SAMSUNG NP530U3c-A05EE machine this
September (or at least I did not notice it before, although I had been
using it with Quantal since June). Decided to upgrade to Saucy, however
this did not fix the issue for me. No ACPI event is triggered after
Calant, let me put it this way. There were no confirmations either from
SAMSUNG or from Ubuntu/kernel devs that the fixes released necessarily
solve those issues (no info from SAMSUNG at all). However, as you can see,
there are almost no new reports that people are still facing the issue.
If you
And do not forget to get the latest Samsung BIOS updates from within
Windows first! This is of utmost importance.
2013/9/11 calant 1040...@bugs.launchpad.net
So I figure the safest thing to do is to wait for Ubuntu 13.10 release?
Since this uses linux kernel 3.11 which contains the anti brick
I have been running Ubuntu 13.04 on SAMSUNG NP530U3C-A05EE for a good week
and a half. So far so good. Please note, that I am running a mainline 3.10
kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ which among
other things contains Matthew Garrett's UEFI anti-bricking patches.
First of
Just noting you don't have to use the i386 image on the 64bit i5 CPU,
unless you want to install the 32bit version of Ubuntu. Amd64 images is
what you should be using if you want to run a 64bit OS; it has nothing to
do with the AMD vs. Intel distinction.
By the way, I have also ordered a
The aforementioned modified UEFI anti-bricking code has been released in
Linux 3.10-rc6, see:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f8b8404337de4e2466e2e1139ea68b1f8295974fI
hope it really works. :)
Hopefully, this kernel will be included in Saucy images/daily
There's a mistake in the link above, it has caught an I as a part of the
link. The actual link is the following:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f8b8404337de4e2466e2e1139ea68b1f8295974f
2013/6/16 Žygimantas Beručka zygimanta...@gmail.com
I know where to get the packages, but thank you anyway. :)
My question was rather how to build an image with those packages or where
it would be possible to get one. So that people would be able to install
Ubuntu from such images containing a (hopefully) safe kernel, i.e. to boot
it right away
Here's a very fresh update on the matter from the fantastic Mr. Matthew
Garrett: http://mjg59.dreamwidth.org/25091.html
Here's the summary of it:
Hence this patch. The new approach is to ask the firmware how much
space is available. If the size of the new variable would reduce this to
less than
Public bug reported:
GNOME Shell 3.8.2-1ubuntu2~raring1 (from GNOME3 PPA) is not installable
in Raring due to broken dependencies. It depends on libpango-1.0-0 (=
1.14.0) and libpangocairo-1.0-0 (= 1.14.0), however, only libpango1.0-0
(1.32.5-0ubuntu1) is available and libpangocairo-1.0-0 seems
** Description changed:
GNOME Shell 3.8.2-1ubuntu2~raring1 (from GNOME3 PPA) is not installable
in Raring due to broken dependencies. It depends on libpango-1.0-0 (=
- 1.14.0) and libpangocairo-1.0-0 (= 1.14.0), however, only libpango1.0-0
- (1.32.5-0ubuntu1) is available and
** Description changed:
GNOME Shell 3.8.2-1ubuntu2~raring1 (from GNOME3 PPA) is not installable
in Raring due to broken dependencies. It depends on libpango-1.0-0 (=
1.14.0) and libpangocairo-1.0-0 (= 1.14.0), however,
- libpangocairo-1.0-0 seems to be unavailable at all.
+
Works great now. Thank you very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186506
Title:
[GNOME3 PPA] GNOME Shell 3.8.2-1ubuntu2~raring1 not installable
To manage notifications about
Try better asking for it here https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1096901 I believe no one gives a damn about this bug –
see its „Fix Released“ (the fix that never happened) status.
No idea what else there is to do, Ubuntu developers do not investigate
into this matter.
Public bug reported:
There is no keyboard layout indicator in GNOME Shell 3.8.2 session on
Raring Ringtail.
This bug has been reported for Quantal too. It is claimed that the fix
for the bug has been released for Quantal, however, the actual fix has
never happened.
At
This bug is still present in 1.12.0-1ubuntu2 from Raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956893
Title:
Tomboy slowly accumulates zombie children.
To manage notifications about this
Did you try to update Samsung provided BIOS from within Windows first?
Rumour has it that Samsung released an updated BIOS that has this issue
ironed out. (And yes, there indeed have been two or three BIOS updates from
Samsung on my sister's presumably affected laptop since I am following this
Public bug reported:
Gnome Sushi 3.8.0-1build0 [GNOME3 PPA] is not installable in Raring due
to broken dependencies in libgjs0c 1.36.1+js17-0ubuntu1~raring0 [GNOME3
PPA].
`apt-get install gnome-sushi':
[...]
The following packages have unmet dependencies:
gnome-sushi : Depends:
This is fixed by 3.8.0-1build0.1.
** Changed in: gnome-sushi (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181599
Title:
[GNOME3 PPA] Sushi
How do you know if it _really_ contains the fix for this particular
issue?
2013/5/3 SiM santiag...@gmail.com
HI ALLL; I HAVE THE ULTIMATE SOLUTION BIOS UPDATE phoenix
technologies motherfuking drivers
http://support-
I can confirm that installing freeglut3 solved the issue.
2013/5/1 Kamil Markiewicz 1171...@bugs.launchpad.net
I don't exacly know for what this are used, I've get depslist from
Ubuntu package from hedgewars.org.
hedgewars_0.9.18-1~getdeb2_i386.deb contains:
Depends: libavcodec53 (=
Public bug reported:
Hedgewars gameplay cannot start in Ubuntu 13.04. Whatever game type is
chosen, one just gets a stuck string In game... and some fullscreen
background, and that's it. It doesn't go as far as to load any level,
therefore nothing works. The only option left is just closing it
Yes, I can run both Totem and Supertuxkart flawlessly on 13.04 (they ran
fine on 12.10 and 12.04 too). In fact, Hedgewars ran just fine on 12.10 on
the very same machines too so I'm not convinced it's related in any way to
your bug.
2013/4/23 LocutusOfBorg costamagnagianfra...@yahoo.it
could
This bug has been reported many times, yet nothing has been done so far.
I doubt anyone cares about it, it's all about Unity these days.
It seems to me that vanilla GNOME doesn't have this bug and it's purely
Ubuntu's fault, i.e. bad patches.
--
You received this bug notification because you
It seems that no one cares about this bug despite it being reported many
times, see, e.g.:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1096901
https://bugs.launchpad.net/ubuntu/+bug/1096862
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1154486
Thanks, this patch fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159636
Title:
python2.7 failed to import webbrowser: NameError in
register_X_browsers(): global name 'Chrome' is not
I can confirm that. The issue is still present in 13.04.
2013/3/17 Anton Anikin an...@anikin.name
I have the same problem with 13.04 Alpha (raring)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems that this patch is a step in the right direction, although more
patches are needed:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=83e68189745ad931c2afd45d8ee3303929233e7f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm curious what is the point installing 12.04 over 12.10 and still
using (a modified) kernel from 12.10?
Correct me if I'm wrong, but if one is afraid of installing 12.10 solely
because of 'samsung-laptop' module being loaded, one can just easily
blacklist the module _before_ booting from the
I face the same problem on an Ultrabook Series 5 laptop and confirm that
items 8 and 9 do work as a workaround as described.
However, after realizing this, I started digging into a riddle why
Ubuntu fails to load the 'samsung-laptop' kernel module in the UEFI mode
and actually bumped into bug
Val, Voria's 'samsung-laptop' package builds a slightly modified kernel
driver to make some features of certain machines work on pre-Quantal
systems. For that reason, it used to override the 'samsung-laptop'
driver that came with your version of the kernel. However, you can see
that it's not
I'm following GNOME3 PPA since before the official Quantal release,
therefore every single package is updated. (I've got no other third-
party GNOME packages.)
I've tried steps 2-4 many times; I've even tried removing all 4 layouts
(Lithuanian, Russian, Greek and French) that I use (except the
Julien, it seems that my case was fixed by this upload:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1082856/comments/4. I don't know you are (were) affected by
the same bug.
Jeremy, I don't know how many of you are able to see a keyboard layout
indicator, but I
I don't use Jeremy's ibus PPA, only GNOME3 PPA. But after the
yesterday's update I was unable to start neither GNOME nor Unity, all
the apps would segfault leaving such messages in dmesg:
[ 47.716480] nm-applet[2399]: segfault at 30 ip 7f22bc896526 sp
7fff1ea24670 error 4 in
Okay, thanks! You fixed those segfaults with this upload.
However, I just found another source of segfaults related to these
recently updated packages. I lost the ability to adjust screen
brightness using my laptop's Fn+ScreenBrightnessUp/Down keys. Instead,
it causes gnome-settings-daemon to
And when running gnome-settings-daemon from a terminal, I get this on
triggering that keyboard shortcut:
(gnome-settings-daemon:9651): GLib-GObject-WARNING **: invalid
uninstantiatable type `(null)' in cast to `GsdMediaKeysManager'
--
You received this bug notification because you are a member
Is there a way to have both Adwaita and overlay-scrollbars?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059374
Title:
Using Adwaita, many widgets are drawn with a solid black background
To
Any chance of getting this in Quantal? If not in quantal-updates then at
least in GNOME 3 PPA. Raring is still irrelevant for the majority of
users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just noting that during the time v3.6.2 has also been released with the
following changes:
* Add assets for insensitive radio/check states for the GTK2 theme
* Fix active spinner when no animations are in use
* Fix gray menu separators under some circumstances
* Fix the build on non-X11
Public bug reported:
First of all, I'm not sure if this is a bug in xserver-xorg, so feel
free to reassign, nevertheless it has as its effect a crashed X session.
As the title says, this reproducable crash of X server is triggered by a
clicked dropdown list on one website (I haven't looked for
May I ask why does it take so long to release an updated package
containing a tiny tiny fix that solves one of the most annoying issues
on Ubuntu's GNOME? It's been available on Tim's PPA
https://launchpad.net/~darkxst/+archive/ppa/+build/3935337 for ten days
already, even longer on Debian and
Public bug reported:
There are evident bugs in Adwaita, for example, in Nautilus the space
around tabs for some reason goes black. Also the same black color is
present where it shouldn't be in Evince, in the sidebar and space around
the document. I'm attaching a screenshot.
Another bug I face
I'm having this as well. Gnome-shell version 3.6.1-0ubuntu1.
It's extremely annoying because I have to ask people to repeat what they
have said.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049210
** Bug watch added: GNOME Bug Tracker #686880
https://bugzilla.gnome.org/show_bug.cgi?id=686880
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=686880
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1049210 ***
https://bugs.launchpad.net/bugs/1049210
** Bug watch added: GNOME Bug Tracker #686880
https://bugzilla.gnome.org/show_bug.cgi?id=686880
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=686880
Importance:
Public bug reported:
I just upgraded to 1:3.6.2~rc2-0ubuntu1 and the menu bar is gone under
GNOME Shell session. Since I cannot use the menus, LibreOffice is
unusable.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libreoffice 1:3.6.2~rc2-0ubuntu1
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062757
Title:
No menu bar under GNOME Shell
To manage notifications about this bug go to:
** Attachment added: Screenshot
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1062757/+attachment/3378989/+files/Nuotrauka%20i%C5%A1%202012-10-06%2012%3A59%3A15.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm what itsjustarumour is facing. Menu bar is gone under GNOME
Shell. I hadn't bumped into this bug until today's upgrade to 3.6.2. I
didn't even realize that people were facing this issue in previous
versions too. Without the menu bar LibreOffice is unusable.
--
You received this bug
Public bug reported:
After upgrading LibreOffice to 1:3.6.2~rc2-0ubuntu1 it shows the file
recovery dialog every time I open any file (odt, docx, xls, etc.)
presuming that LO crashed the last time it was launched, which is not
the case it seems since it closes normally. More over, it keeps adding
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062789
Title:
File recovery dialog is shown on every launch
To manage notifications about this bug go to:
It doesn't crash for me. But it does open the file recovery dialog every
time I open any file (odt, docx, xls, etc.) presuming that LO crashed
the last time it was launched, which is not the case. More over, it
keeps adding up those files opened to the recovery dialog; at first I
had one file on
Public bug reported:
There's neither plymouth graphics nor resolution higher than 800x600
(both in console and X) with 3.5.0-17.26 on boot on my SAMSUNG 300V3A
machine w/ i3 2310M and HD3000 graphics. Judging from dmesg (with
drm.debug=0xe set), Intel graphics is not detected and the driver ends
** Attachment added: dmesg_xrandr_output.tar.gz
https://bugs.launchpad.net/bugs/1061421/+attachment/3370332/+files/dmesg_xrandr_output.tar.gz
** Description changed:
There's neither plymouth graphics nor resolution higher than 800x600
(both in console and X) with 3.5.0-17.26 on boot on
** Attachment added: lspci output on 3.5.0-16.25
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1061421/+attachment/3370343/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
There's neither plymouth graphics nor resolution higher than 800x600
(both in console and X) with 3.5.0-17.26 on boot on my SAMSUNG 300V3A
machine w/ i3 2310M and HD3000 graphics. Judging from dmesg (with
drm.debug=0xe set), Intel graphics is not detected and the
1 - 100 of 174 matches
Mail list logo
