The enigma wrote:
Cristian Aravena Romero wrote:
** Changed in: Ubuntu
Sourcepackagename: None = beagle
Please explain in further detail.
Thanks
Beagle states Beagle has to close and any work will not be saved,
please report bug every once in a while. I seems to happen
dBera wrote:
Enigma, you seem to be having the problem on a regular basis. With a little
effort, you may be able to provide valuable input in identifying the problem.
After you login, in a terminal give,
$ beagled --replace --fg
This will start beagle in the terminal and print all kind
Public bug reported:
While creating a folder on the GNOME desktop version 2.16.1 on Ubuntu
edgy 6.10 eft, a dialog box appears stating that Beagle has to close,
you may lose any work. Closing the warning then continuing naming the
folder, or whatever on the desktop seems to have no effect on the
Cristian Aravena Romero wrote:
** Changed in: Ubuntu
Sourcepackagename: None = beagle
Please explain in further detail.
Thanks
--
~Rick Donahue
_
When you do the right thing,
most people won't notice.
SeaMonkey Email Client
***Linux***
--
Beagle crashes
Public bug reported:
Binary package hint: mono
I'm running Ubuntu 6.10 Edgy eft and GNOME Desktop 2.16.1, both are
October builds. I suddenly, without any applications running, had a pop-
up dialog box stating that mono crashed. I closed the dialog box, and
continued working without any
Public bug reported:
I was running an update, the update manager said that everything
installed correctly, the system prompted me to reboot, then I had a
dialog box that said Buildindex.exe unexpectedly crashed. It seemed to
cause no issue after that. I just upgraded to Ubuntu 7.04 The feisty
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6856772/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6856773/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/6856774/Disassembly.txt
** Attachment
*** This bug is a duplicate of bug 512096 ***
https://bugs.launchpad.net/bugs/512096
Public bug reported:
pkg (子进程)：无法运行 已安装的 post-installation 脚本: 可执行文件格式错误
dpkg：处理 avant-window-navigator (--configure)时出错：
子进程 已安装的 post-installation 脚本 返回了错误号 2
dpkg：依赖关系问题使得 awn-applets-c-core
*** This bug is a duplicate of bug 512096 ***
https://bugs.launchpad.net/bugs/512096
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/51033877/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51033878/Dependencies.txt
** Attachment
For me the issue was that I was launching mumble via a .desktop that
pointed to a sym link I placed in /usr/bin pointing to
~/mumble/release/mumble.
If I launched mumble manually through it's release directory, I didn't
get this warning.
To fix this I added `CONFIG+=no-bundled-celt` to the qmake
Still an issue with Nvidia 660 Ti running propriety drivers on Ubuntu
GNOME 16.04.1.
Freezes within 1 minute of resuming 100% of the time (about 12/12 so far
before disabling it).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Has nothing to do with Nouveau for me. Been using proprietary Nvidia
drivers from day one and 100% of suspend sessions freeze after resuming
usually within a minute or less.
Base system is a fresh Ubuntu GNOME 16.04.1 install.
--
You received this bug notification because you are a member of
Public bug reported:
do-release-upgrade fails to upgrade from 16.04 to 17.04 - no
information/error given as to why.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.22
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux
Damn... how many duplicates have to get created before this gets
fixed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069133
Title:
Get upgrade error 12.04 - 12.10 "Could not determine upgrade"
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
Damn... How many duplicates have to get created before this issue gets
fixed...
It's not just that the do-release-upgrade should automatically handle
what is needed to be done - it also fails even after I
Huh? What's this about?
There should be enough info in the logs to confirm this.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Turned out that the culprit, despite a very long list of Broken packages
in Apt.log, was this inconspicuous line in Main.log:
DEBUG Installing 'xserver-xorg-video-all' (Distro KeepInstalledPkgs
rule)
So while technically my issue with this is fixed I think some work needs
to be done to provide
I did see that unhelpful generic boiler plate message every time I tried
to run `sudo do-release-upgrade` yes. That doesn't exactly constitute a
helpful error message. It's more like saying, "There's a problem and
what you tried to do failed" which I already knew by the process not
succeeding.
Public bug reported:
I originally installed Kubuntu 16.04 but since upgraded to 16.10 and
switched over to Ubuntu GNOME (ubuntu-gnome-desktop).
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubuntu-release-upgrader-core 1:16.10.10
Uname: Linux 4.11.1-041101-generic x86_64
ApportVersion:
This is still broken in Ubuntu 17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300215
Title:
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
object file: No such file or
This resolved the issue for me:
https://askubuntu.com/a/968265/89202
"If you wish to do it permanently, edit
/etc/gdm3/custom.conf and uncomment the line
#WaylandEnable=false by removing the # in front.
Save the file and then on reboot you will never see the cog asking for
which session to
Ehh... Not really worth the trouble at this point as I've resolved it
myself by just disabling Wayland.
Since Wayland won't be default in 18.04 anyway, there's a good chance
the issue will be fixed by 18.10.
I've posted the same solution on an Ask Ubuntu question so it may help
others.
--
You
Here it is: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1747568
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730174
Title:
[artful] mouse clicks are completely ignored both in
Public bug reported:
If I disable Wayland, mouse clicks start working again.
Randomly started occurring sometime after initial install.
Ubuntu 17.10
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
If you can instruct me on how to gather the pertinent information, I can
make a report.
Honestly though, it seems like the chances of some unique rare issue
that few have is going to get much attention. If it comes to it that I
need Wayland on this system, I'd sooner just reinstall which
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1747568/+attachment/5049501/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1747568/+attachment/5049502/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1747568/+attachment/5049503/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected artful third-party-packages
** Description changed:
If I disable Wayland, mouse clicks start working again.
Randomly started occurring sometime after initial install.
Ubuntu 17.10
+ ---
+ ApportVersion: 2.20.7-0ubuntu3.7
+
@tkr Np - it really smoothed things over for me too.
In terms of oibaf PPA, I am also pretty sure that mouse stuff was
working for quite a while after initially setting up the PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
GSettingsChanges:
org.gnome.shell enabled-extensions ['temperature@xtranophilist',
'openweather-extens...@jenslody.de',
'screenshot-window-si...@gnome-shell-extensions.gcampax.github.com',
'user-th...@gnome-shell-extensions.gcampax.github.com',
'show...@kyle.aims.ac.za',
** Attachment added: "Journal Errors"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+attachment/5049824/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@tkr
Same fix for me but I am using:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
Hovering also was ignored for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747568
Title:
** Description changed:
I can't log in anymore. I've force rebooted several times. Was working
fine with occasional freezes until recently but now it freezes every
login.
17.10 - Wayland was disabled as per:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568
(system
Public bug reported:
Could be virt-manager or gnome-shell related.
I was passing through 1 USB device that wasn't my main mouse or
keyboard. Otherwise pretty normal configuration that I've used before.
After the VM's bios screen, the whole system froze except the clock in
the desktop menu
:~$ virt-manager --version
1.4.0
** Attachment added: "about virt-manage"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+attachment/5057545/+files/virt-manager-about.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm not sure but can try. The issue is that the system freezes when
trying to start the VM at all so it doesn't get far enough.
Are you sure you don't mean to install the -evdev package in the host?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yeah 'guest' for me means VM running on a host. That VM system is unable
to start so I wouldn't be able to gather or report anything from there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749895
Same issue... Still broken.
X.org works - Wayland doesn't let you click on anything. This includes
the login screen.
Running kernel 14.5-rc7.
sudo ubuntu-drivers autoinstall did nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743183
Title:
Mouse left button not being noticed when clicked under Wayland -
*** This bug is a duplicate of bug 1747568 ***
https://bugs.launchpad.net/bugs/1747568
Well... It doesn't sound like it's fixed & certainly not invalid.
If it still doesn't work when using updated versions of packages
available in those PPA's, it's not really fixed.
Is there a way to mark
*** This bug is a duplicate of bug 1747568 ***
https://bugs.launchpad.net/bugs/1747568
So.. I marked it as a duplicate of the bug you mentioned. Still..
invalid really doesn't seem appropriate.
The description says:
Invalid:
Not a bug. May be a support request or spam.
--
You received
I'd point my finger a the amdgpu driver in that case. Unplugging the
monitor in question did the trick (allowed system to blank properly).
The cable is definitely good & the connection ports on both ends should
be fine. This particular system is dual booted into Windows 10 where
this is a
Public bug reported:
After some idle period (5-15 minutes) the screens are supposed to blank
and power off.
They appear to do this once but then come right back on and stay on.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu
Why is this still marked incomplete?
What other info is necessary?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835863
Title:
Screens do not stay off when blanking
To manage notifications about
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835863
Title:
Screens do not stay off when blanking
To manage notifications about this bug go to:
Thanks for the quick reply.
Here ya go.
** Attachment added: "curjournal.txt"
https://bugs.launchpad.net/ubuntu/+bug/1835863/+attachment/5275982/+files/curjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please feel free to do whatever you like.
I gave up on Unbunto when there was no interest in anyone fixing this
issue, which PREVENTED me using Ubuntu.
I exclsuively use Compaq hardware, and this device is the built-in Video
supported by Compaq Diagnostics. By nobody addressing this issue, it
Public bug reported:
Binary package hint: mkvmlinuz
The Cirrus Logic CL5446 is the embedded Video hardware in one of the
Compaq ProLiant 1600 models.
As soon as vmlinuz is loaded, the screen goes BLANK (What I call the
Black Screen Of Death - BSOD [I pronounce it: Bee Sod]).
In fact, you
Public bug reported:
Compaq ProLiant computers usually have a small Diagnostics Partition
(About 50MB). This is accessed at the end of the POST.
The results of the POST are cleared from the screen, and a reminder
message is displayed saying that to access the Diagnostic software, you
should
Regardless of what you might think, Windows does NOT 'erase' the F10
'feature' of the Compaq system. Ubuntu is the only Operating system
that I have experienced doing it.
Regards, Wesley.
Ante Karamatić [EMAIL PROTECTED] wrote:
If this 'shortcut' is really in MBR, then installation
for my assistance again.
Wesley.
==
Ante Karamatić [EMAIL PROTECTED] wrote:
Enigma-TS wrote:
Regardless of what you might think, Windows does NOT 'erase' the F10
'feature' of the Compaq system.
Then it isn't in MBR or you where using modified Windows installation
(default
Um, it's me again.
Just ran out of space in one of my several medical dictionaries
Maybe there's another way to approach the problem? (LARGE list of user words to
spellcheck.)
--
want more features for Writer user dictionaries
https://bugs.launchpad.net/bugs/417085
You received this bug
Interesting thread. I found it because I'm needing _more_ custom
dictionary options. Until recently, I was only a casual word processor
user, but have been using multiple user dictionaries for many years. I
figured that if I was going to modify (add to) the dictionary(s), I
should learn how to use
Public bug reported:
Binary package hint: openoffice.org
I'm working as a English-language editor/proofreader for a small
writer/publisher of reference books AND for the English-language-
instruction faculty of a major university - in a country where English
is broadly, but very poorly, known.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30647645/Dependencies.txt
--
want more features for Writer user dictionaries
https://bugs.launchpad.net/bugs/417085
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
56 matches
Mail list logo
