** Attachment added: installer logs from failed Lucid install
http://launchpadlibrarian.net/42024569/Xenophon_amd64_install_log.tar.gz
--
kubuntu 64bit lucid alternate (text-based) beta daily 2010-03-25 throws error
while installing software
https://bugs.launchpad.net/bugs/548572
You
Public bug reported:
Binary package hint: resolvconf
Bug entry started directly from launchpad because of connectivity
failure in lucid install:
1. Problematic install of kubuntu lucid daily alternate amd64. Software
installation step stopped with red screen error (reported in separate
bug
Public bug reported:
Binary package hint: kdebase
Have *_zero_* functionality in konqueror
Following a disk crash which wiped out (a carefully backed-up) /home
drive, performed a clean install of Kubuntu Lucid Lynx beta 1 on
2010-03-20. Have reported in separate bug that KDE appears to load
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41614331/Dependencies.txt
--
nspluginscan crashes on startup; Protocol not supported: http
https://bugs.launchpad.net/bugs/544200
You received this bug notification because you are a member of Kubuntu
Bugs, which is
Forgot to include:
this problem affects the amd64 instance only. My ia32 setup, which has been
running Kubuntu 10.04 Alpha versions since 2009.11, continues to run routinely.
--
nspluginscan crashes on startup; Protocol not supported: http
https://bugs.launchpad.net/bugs/544200
You received
Good question.
The package is not installed and the question is therefore why not? If
it is required in order for dkms to install the proprietary module
(nvidia-current in this case), should it not be listed as a dependency
of either dkms and/or the proprietary module package?
nvidia-current
Marking this bug invalid is to treat the symptom while disregarding the
cause. That solves nothing. There is a problem here; I have no idea how
many users are affected, but if it strikes a reviewer after Lucid is
released, there is certain to be negative comment on Lucid. It is that
risk which I
As requested, I performed a re-install of Kubuntu Lucid beta1. I used
the daily alternate build of Mon 2010-04-05.
I had previously had problems with Kubuntu daily builds around the time
Beta1 was released: the problem with the LiveCD is Bug #548373 and with
the alternate install CD is Bug
*** This bug is a duplicate of bug 451105 ***
https://bugs.launchpad.net/bugs/451105
Bug #451105 applies to karmic and a fix has been released.
The traceback on that bug reported ImportError: No module named
kdecore. The traceback on this bug reports ImportError: No module
named kdecore.
Is
Further to point 8 above:
$ sudo apt-cdrom add
Using CD-ROM mount point /media/apt/
Identifying.. [88fcd7dee0ea7d715b004f299ca0b300-2]
Scanning disc for index files..
Found 2 package indexes, 0 source indexes, 0 translation indexes and 1
signatures
This disc is called:
'Kubuntu 10.04 _Lucid
Duplicate Bug #548576 reports this same problem in Kubuntu Lucid Lynx
Beta 1 amd64 daily disks of 2010-03-25 and 2010-03-27.
On this network, individual hosts are set up to use DHCP and individual
nameservers are not listed in /etc/network/interfaces. Predictable IP
addresses are assigned by the
** Changed in: kdebase-workspace (Ubuntu)
Status: Fix Released = New
** Changed in: kdebindings (Ubuntu)
Status: Fix Released = New
** Tags added: regression-potential
** Tags removed: regression-retracer
--
jockey-kde crashed with ImportError in module()
I have just experienced this bug on Kubuntu Lucid Lynx 10.04 beta 1
(daily 2010-03-27) amd64, The bug appeared as soon as KDE loaded after a
reboot.
Interestingly, I had installed a printer during the previous session.
That is the action which triggered this bug's original report.
--
I am experiencing this bug as well when I try to print. As it happens, I
had started gnumeric from a command line:
I was careful within Gnumeric to set a print area.
br...@xenophon:~/PDF$ gnumeric ~/Documents/fin/erik-2010.gnumeric
[1] 6576
br...@xenophon:~/PDF$
(gnumeric:6576): Gtk-WARNING
I have always set aside a small boot partition of 100 MB.
This appears to be no longer enough.
This is the error report that I get when I tried to install apport-
collect:
Get:1 http://us.archive.ubuntu.com/ubuntu/ raring/main python-problem-report
all 2.9.2-0ubuntu8 [9,532 B]
Get:2
apport-collect attempted to open a chromium-browser window. Nothing
happened.
Attempting to open chromium-browser manually generated the following
message:
ruce@Pericles:~$ chromium-browser
[1] 4649
bruce@Pericles:~$ [4649:4649:0429/130426:ERROR:process_singleton_linux.cc(907)]
Failed to
Interestingly, when this error message first appeared, chromium
complained that it could not be run as root unless I set up a new
profile.
But at the same time, a launchpad log-in page opened in Firefox and it
is from there that I am commenting on this bug report.
I am going to try living
the same permission denied error:
Launchpad.net
Not allowed here
Sorry, you don't have permission to access this page or the information
in this page is not shared with you.
You are logged in as Bruce Miller.
I am trying to provide the information which you requested from the original
reporter
Public bug reported:
Please see my comments under bug 1170320, which explains why I am
following this process.
cat version.log
Ubuntu 3.5.0-27.46-generic 3.5.7.7
bruce@Pericles:~/scratch$
lspcivnvn.log is attached.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package:
I submitted the information requested as Bug #1174432 for the reasons
explained above.
I had to delete both /boot/initrd.img from 12.10 and 13.04 to get the
installation process to complete satisfactorily, but the system has now
booted into 13.04.
** Changed in: ubuntu-release-upgrader (Ubuntu)
The same problem appears to have occurred during the upgrade from
3.8.0-19 to 3.8.0-21. In other words, this bug appears to be of broader
scope than just the release upgrade.
I worked around the problem by deleting the abi, initrd.img and
System.map files for 3.8.0-19. I did so with much
Public bug reported:
This is the within-release equivalent to Bug #1173468. An upgrade to
kernel 3.8.0 within raring failed because there was no space left on
/boot.
It is my recall that upgrades to 3.5.0 automatically cleaned up the old
kernel files in /boot. If so, this would make this problem
[BACK TO SQUARE 1]
So, having got it all working, the new linux kernel headers arrived.
3.2.0-24-generic #37 upgrade to #38 and now it has all stopped
working . Argh... (check with 'uname -r' and 'uname -v')
FWIW: people used to the terminal alsa panel may have noticed my
No.
From: Phillip Susi ps...@ubuntu.com
To: b...@brmiller.ca
Sent: Monday, January 13, 2014 3:35:26 PM
Subject: [Bug 444740] Re: Karmic beta installer fail to reboot at the end of
the installation.
9.10 reached end of life several years ago, are you able
Public bug reported:
My wish is to simplify the language referring to Windows partitions in
/boot/grub/grub.cfg. The current language is in terms that only a Unix
geek could love: Windows 7 (loader) (on /dev/sda1). This does not
contribute to resolution of bug #1.
I am an advanced intermediate
bruce@Xenophon:~$ amarok -d --nofork
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
unnamed app(13110): KUniqueApplication: Can't setup D-Bus service. Probably
already running.
bruce@Xenophon:~$
Could you please run Amarok from a
Public bug reported:
This error occurs consistently every time I start a new KDE session.
This instance of precise 12.04 is updated once or twice daily.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: amarok 2:2.5.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986744
Title:
On session start, amarok throws error: Process for file protocol died
unexpectedly
To manage notifications about this bug go to:
This seems to be an upstream kernel bug.
I am having problems myself with this. Not sure if the latest ppa
release will fix this. Upstream fix feb13, ubuntu ppa date feb16.
Posting this up while the data is on my screen, before I do the reboots
and such ...
From:
*** This bug is a duplicate of bug 985145 ***
https://bugs.launchpad.net/bugs/985145
** This bug has been marked a duplicate of bug 985145
no audio on ubuntu 12.04 on an intel hda vt1705
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 985145 ***
https://bugs.launchpad.net/bugs/985145
** This bug has been marked a duplicate of bug 997671
[Ubuntu 12.04, N10/ICH 7, Green Headphone Out, Front] No sound at all
** This bug is no longer a duplicate of bug 997671
[Ubuntu 12.04, N10/ICH 7,
Have just linked two duplilicate threads to this one. Seems to be
affecting several people.
Apparently there is an upstream fix available but it needs packaging:
http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.2.7
commit 852c3a36c216e351d07ca96e9af30b81fff30ccc
Author: Takashi Iwai
!!
!!ALSA Information Script v 0.4.60
!!
!!Script ran on: Sat May 19 07:11:55 UTC 2012
!!Linux Distribution
!!--
Ubuntu 12.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION=Ubuntu
12.04 LTS
!!DMI Information
[SOLUTION / WORK-AROUND]
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/385076
Message #6
I found that similar worked for me -
At terminal, I ran 'alsamixer'. The Via VT1705 showed by default. At
the interface I cursored over to make 'front' highlight in red then
pressed 'm' as
Public bug reported:
first output is with kwallet disabled.
second output is after re-enabling kwallet
ruce@Pericles:~$ ATTENTION: default value of option force_s3tc_enable
overridden by environment.
[6251:6251:0419/183400:ERROR:sandbox_linux.cc(268)] InitializeSandbox() called
with multiple
Reading around the problem, I found that some wifi drivers don't seem
to run the KeyRing Authorization routine properly if a hidden SSID is
used. This leads to the authorization not getting saved.
This FIXED it for me: At the router, temporarily enable SSID broadcast.
Make a connection and
Workaround:
sudo dpkg -i --force-overwrite
/var/cache/apt/archives/kaccounts-providers_4%3a15.12.3-0ubuntu1_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573787
Title:
package
Update: It did fix it. But then I tried again to use the WiFi today
and now it's stopped.
Sorry to build up peoples' hopes. On the bright side, it looks like
like it may be a clue to the source of the problem though. Maybe someone
can figure out the rest for us?
--
You received this bug
Public bug reported:
immediately after login, ran daily update; script uses "aptitude --with-
recommends full-upgrade"
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-google 0.12+16.04.20160126-0ubuntu1 [modified:
usr/share/accounts/providers/google.provider]
Public bug reported:
Dmesg:[ 573.856456] traps: sushi-start[4619] trap int3 ip:7f7ea46c3241
sp:7ffe3ae23350 error:0 in libglib-2.0.so.0.5000.0[7f7ea4673000+11]
Since upgrade to 16.10 from 16.04 Sushi fails when pressing space-bar.
In Mate, space-bar causes pluma text editor to open ...
** Summary changed:
- Sushi-start fails with 16.10, both Unity and Mate
+ Sushi-start fails with 16.10 upgrade, both Unity and Mate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644781
Title:
1. The no-run problem still exists with Ubuntu Mate.
I, personally, use Mate on older laptop. I prefer it to Lubuntu. I can
live without Sushi running there. Others, however may not. Mate may be
their main OS.
Taking another look at my the Mate problem, I wonder if it is 64bit
versus 32bit
Let me know if more needed.
** Attachment added: "Screenshot from 2017-03-13 12-56-02.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-sushi/+bug/1644781/+attachment/4836947/+files/Screenshot%20from%202017-03-13%2012-56-02.png
--
You received this bug notification because you are a
Yep. I think this is it.
If I manually adjust the window it all goes away. But if I close the
default window it doesn't remember the size I set it to. It goes back to
being off size.
Do you know where the configs are for the default window sizes?
Reducing the vertical height seems to fix it for
Looks like a good move in the right direction! Not a full fix for me
but a definite improvement.
Installing gir1.2-evince-3.0 gets Sushi starting when using the Unity
interface. It works on different types of files; .txt .png ..
There's a wierd extra section to the menu bar though. I guess
Try this. I think this might be the fix?
Edit /usr/share/sushi/js/util/constants.js
Change 'let VIEW_PADDING_Y = 28;' to 'let VIEW_PADDING_Y = 2;'
Tell me what you think. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug still affects Ubuntu 17.04. Uninstalling and re-installing
chromium-browser has not helped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318834
Title:
Applications can no longer access
Public bug reported:
The following packages have unmet dependencies:
libnss-resolve : Depends: systemd (= 234-2ubuntu12.1) but 234-2ubuntu12.2 is
to be installed
open: 23; closed: 490; defer: 5; conflict: 5
Sorry for the poorly formatted reply. In future, I will not use a
webmail client tto send bugmail.
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Incorrect. I am *_not_* installing packages from artful-proposed. I do *_not_*
upgrade packages individually.
Here is my sources.list:
deb http://ca.archive.ubuntu.com/ubuntu/ artful main restricteddeb
http://ca.archive.ubuntu.com/ubuntu/ artful-updates main restricteddeb
Thanks for getting back to me. Can you recommend one or two books to
help?
On Mon, Jan 3, 2022, 8:55 PM Chris Guiver <1956...@bugs.launchpad.net>
wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> Unfortunately, we cannot work on this bug because
Public bug reported:
I have been using ubuntu for nearly ten years, but have only recently
started taking things seriously. My particular issue is that every now
and then I have a screen blinking problem. I have done a bunch of
research, and it points to the grub configuration. I have
301 - 352 of 352 matches
Mail list logo
