TLDR: the Xubuntu 18.04.1 installer does not recognize an NTFS EFI
partition. Then the process takes it course and fails.
Longer story. I recently staged two dual boot machines from scratch.
The only difference between them was the EFI partition.
Case 1:
* Laptop came with Windows 10
Affects also SONY Vaio Pro 13. Experienced this bug in August 2013 when
initially staging the brand new machine. Wasted a couple of hours on
it. Fixed it manually, essentially doing what Benjamin suggested in the
original report. Thought it was a SONY idiosyncrasy not worth reporting.
IT IS
Tested and confirmed on a SONY Vaio Pro 13 15.10 64bit. Problem
appeared since trying to import an OVPN file and is now happening at
every reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug has long been fixed. Comment #20 is absolutely unnecessary and
the kind of comment that makes me reconsider contributing bug reports at
all.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
@Moritz: Thanks for the great software. Easy fix to the concern
expressed in this bug report while keeping the software up to date and
possibly saving your time and resources: start a PPA on Launchpad. Then
you only need to upload the most recent source code package to Launchpad
and it builds
Note to self:
* I was too optimistic during bisection. the bug is spurious and just taking
the laptop on/off the grid and closing the lid a couple of times is not enough
testing to provoke it. Trigger requires more interaction with laptop such as
the type of interaction that is natural when on
I stand corrected: on that machine I get LibreOffice from
ppa:libreoffice/libreoffice-prereleases
It just updated to 4.4.0.0.beta2 and the problem described is still
present.
I had switched that machine July 16, 2014 to the prereleases PPA because I
needed to connect Base to a MySQL database
Public bug reported:
On one of my desktops I get LibreOffice from
https://launchpad.net/~libreoffice/+archive/ubuntu/ppa
The recent upgrade to 4.4.0.0.beta 1 breaks desktop integration. The entries
in Xubuntu's whisker menu do not have an icon, and returns an error message
saying:
Potential solutions to the bug report:
(1) The lazy solution: this report will be marked as invalid, because the
problem is not in the package but in the user's configuration file
(2) The smart solution: a parser to check the user's configuration file and
issue warnings for deprecated
I encountered the same problem and solved it. I have tried a number of
things, so I am not 100% sure which one it is that solved it. If I were
to do it all from scratch again, this is my suggestion for
troubleshooting the problem:
1. look at /var/log/mysql/error.log for lines with the [ERROR]
OK, I tried hard to trigger the bug and it does not. At the risk of
cutting things short, I try the following:
git bisect good 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52
output:
Bisecting: 12903 revisions left to test after this (roughly 14 steps)
[8cf126d92791381632818df862fdbc89ab6f7572] Merge
actually
yes '' | make oldconfig
before building is less painful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368908
Title:
[Sony VAIO SVP13215CDB] suspend/resume failure
To manage
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368908
Title:
[Sony VAIO SVP13215CDB] suspend/resume failure
To manage
I have set up to do the bisection. I am not sure if what I have done is
right, so here it is, comments are welcome.
Requirements:
* about 12 GB of free disk space
* 3-4 hours (YMMV depending on internet connection speed and processing power)
Dependencies:
* Some were already present on the
so it was missing an assignment to myself. fixed. your recent feedback
has not been helpful at all, Christopher
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Yuv (yuv)
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
--
You received this bug notification
** Changed in: hugin (Ubuntu)
Status: Confirmed = 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/486303
Title:
Every illegal character aren't well detected and forbidden
To
put one out there.
Thanks for bearing with me.
Regards,
Yuv
** Changed in: hugin (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384674
Title:
enblend running
for understanding,
Yuv
** Changed in: hugin (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/820237
Title:
hugin crashed with SIGSEGV in
HuginBase
for understanding,
Yuv
** Changed in: hugin (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/815367
Title:
hugin becomes unresponsible if load buttons is pressed
Setting to invalid in hugin(Ubuntu) since this is not a package issue.
The feature request is tracked in hugin.
** Changed in: hugin (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Addendum: no need to file a new report in this case, I added this bug
report to the Hugin code bug tracker.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219248
Title:
Displays error during
code bugs are tracked at
https://bugs.launchpad.net/hugin.
This will ensure that your bug report gets the attention it deserve.
Thanks for understanding,
Yuv
** Also affects: hugin
Importance: Undecided
Status: New
** Changed in: hugin (Ubuntu)
Status: New = Invalid
--
You
for understanding,
Yuv
** Changed in: hugin (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/820390
Title:
Hugin crashes: Memory access violation
To manage
Bug is not specific to the Hugin package, setting to invalid as there is
nothing more that the packagers can do to help.
L'erreur n'est pas liée au packet Hugin. Je change le status du bug à
invalid car il n'y a plus rien qu'on peut faire au sujet.
** Changed in: hugin (Ubuntu)
Status:
** Also affects: hugin
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210930
Title:
hugin assert failure: hugin: tif_ojpeg.c:886: OJPEGPostDecode:
Lucky (or unlucky) me, I intensified usage by opening and closing the lid and
connecting/disconnecting the power plug and the bug was triggered with 3.17.1.
The behaviour that seems to trigger it / the last activities were:
* leave Thunderbird and Skype running to have some disk activity going
I actually went back to v3.12.30-trusty -- the most recent in the 3.12
line, because I remembered that 14.04, when the problems started,
installed v3.13.something. I no longer have record of what was the last
working kernel under 13.10, but I remember 3.11 is the first one that
did work with this
On 14-10-18 10:49 AM, Christopher M. Penalver wrote:
Yuv, if the problem is reproducible on the latest mainline kernel
available (now 3.17.1)
Why did you mark the bug as incomplete?
I know 3.17.1 is the latest mainline kernel now available. When it was
published I could not install it without
Just when I started to believe that the bug is gone, after 12 days and
23 hours of uptime on 3.17-rc7 it is here again:
[366556.560757] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[366556.560759] sd 3:0:0:0: [sda] CDB:
[366556.560760] Read(10): 28 00 0a 07 62 58 00 00 08 00
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368908
Title:
[Sony VAIO SVP13215CDB] suspend/resume failure
To manage
the bug is alive and well. For the past two weeks I have not been using
the laptop but I have left it on, sporadically opening and closing the
lid, connecting and disconnecting the power adapter and doing some light
web surfing / text editing. then last Tuesday I used it to help a
friend get a
Thank you for the quick reply, Christopher.
The report in comment #5 was against ustream 3.17-rc4, so I will add the
tag kernel-bug-exists-upstream-3.17-rc4. RC4 was the latest available
upstream kernel at the time of rebooting the laptop, and it has not been
rebooted since. With my current
I just started testing 3.17-rc7. It will take a couple of weeks to tell
if this bug is reproducible or not. A symptom that is consistently
reproducible is that hibernation does not work, however I am not sure it
is related and the system does not let me file a bug report, saying that
It appears
On 14-10-04 07:25 PM, Christopher M. Penalver wrote:
hibernate, this is treated as a separate issue
That's what I suspected. Hibernation is a very minor issue compared to
the system melt downs and data loss that I have experienced with the
issue reported in this ticket. I will not file a
Christopher, thank you for the helpul directions. I was not aware of the
BIOS update. I updated the BIOS, and I also updated
https://help.ubuntu.com/community/BiosUpdate (the path to the EFI
partition was wrong in the initial considerations section, and I added
the SONY experience).
sudo
Thanks for the hint. Done:
https://bugzilla.xfce.org/show_bug.cgi?id=11157
** Bug watch added: Xfce Bugzilla #11157
https://bugzilla.xfce.org/show_bug.cgi?id=11157
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: yuv1970 F pulseaudio
/dev/snd/controlC1: yuv1970 F pulseaudio
CurrentDesktop: XFCE
Date: Fri Sep 12 14:41:40 2014
MachineType: Sony Corporation SVP13215CDB
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot
Short answer: sorry, Christopher, I cannot bissect on this machine. I
have a couple of other machines that are misbehaving after the 14.04
upgrade and I will probably file a report against them, with the extra
steps.
Longer answer: This is a production critical machine (family storage).
When I
Public bug reported:
* Machine was happy with Xubuntu 13.10, but the software has been discontinued
and I was forced to upgrade.
* USB stick with 14.04.1 would reboot continuously. Temporary workaround:
press F6 and select NOMODESET
* USB stick with 14.04.1 server installs flawlessly, but then
and another one: bug 1367064
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309578
Title:
Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k
To manage notifications about this
the same happens with ubuntu 14.04/trusty
$ pactl load-module module-alsa-sink device=btheadset
Aug 26 14:08:34 yuv-SVP13215CDB pulseaudio[4420]: [pulseaudio] module.c:
Failed to load module module-alsa-sink (argument: device=btheadset):
initialization failed.
--
You received this bug
Has an upstream bug report been filed?
The exact same issue affects a SONY Vaio Pro 13 (Haswell ULV CPU).
Which one is the latest trusty mainline kernel? sorted by last modified
date, it seems to be [0] from less than ten days ago, but sorted by
version number it seems to be [1] from four
Documenting the workaround for people who bumps in the same issue
(documentation around the web is scattered and unclear).
* start a terminal (pressing the key combination Super+T should do)
* enter the following commands to create the configuration file
sudo mkdir -p /etc/X11/xorg.conf.d/
Worked for me too. Documented workaround in Launchpad
* start a terminal (pressing the key combination Super+T should do)
* enter the following commands to create the configuration file
sudo mkdir -p /etc/X11/xorg.conf.d/
sudo nano /etc/X11/xorg.conf.d/20-radeon.conf
* in the configuration
Public bug reported:
Testing with Xubuntu 14.04 and with LibreOffice version
1:4.3.0~rc2-1ubuntu1~trusty0 from the pre-releases PPA.
Server Side:
CREATE DATABASE test;
GRANT ALL PRIVILEGES ON test.* to 'dbuser'@'localhost' IDENTIFIED BY
'password';
FLUSH PRIVILEGES;
dbuser
More research into this:
* I can create tables from LibreOffice to MySQL, but they must have primary keys
* Once tables have primary keys, they can be edited
* Table created MySQL-side, that works:
CREATE TABLE idxtest (a INT NOT NULL AUTO_INCREMENT PRIMARY KEY, b
VARCHAR(10));
* Table that did
Xubuntu 14.04LTS, still affected. While I do not use NTFS myself, a
Windows-using friend brought this NTFS formatted USB harddisk. Needless
to say that what he saw has undermined my efforts to convert him to use
Linux...
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
To whom it may concern:
Apology if I assigned the bug to the wrong package, my understanding is
that keyboard layout is an xorg thing.
I have just installed Xubuntu 14.04 on a bare metal laptop. I closed
the lid thinking it would hybernate. Instead it depleted the battery
Some more observations:
* I assigned this bug to the wrong package. It is not xorg. After removing
the default GRUB_HIDDEN stuff (really not a good default IMHO, it prevents
users from learning things, and it also prevents users who may want to dual
boot Windows) I verified that the bad key
and not much in use these days.
* It's currently installed system started life in 2010 or 2011 and has
been regularly upgraded every six months with no particular troubles.
Thanks again for taking up this bug report. Let me know if I can be of
any help testing patches, etc.
Yuv
--
You received
Public bug reported:
Upgrading
Fetched 0 B in 0s (0 B/s)
Exception during pm.DoInstall(): E:Internal error, packages left
This behaviour is present on Xubuntu 14.04 amd64 both when upgraded
(from 13.10) and when installed from scratch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131044
Title:
Shortcuts such as
Public bug reported:
* Xubuntu 14.04 LTS amd64 installed from scratch.
* I want to edit a keyboard application shortcut.
To reproduce:
* Enter the Keyboard Settings, Application Shortcuts tab
* Select shortcut to edit
* Click Edit
* Click Open
* Browse to the command and select it
* click OK
Public bug reported:
Fresh install, Xubuntu 14.01 amd64.
When I either press the computer's power button or the Logout Button in the
Whisker Menu, the computer hangs, more or less unresponsive, for a few minutes,
before showing me the choices of logout, reboot, or shutdown.
Workaround: open a
Trusty has been released and a sudo apt-get upgrade still yields the
error message. This thing is really just a couple of lines to fix. The
error has been known for months and the simple fix (comment #4, thank
you very much) known for weeks. This kind of errors just make the users
feel
I am on libreoffice 4.2.3.3 and it is completely, utterly broken.
I have text with a footnote. In the footnote I have reference to the footnote
number of another footnote. I copy paste the text. It creates a new footnote.
The reference in the new footnote is to itself! With a 24 hours
Use cases:
- transcode camcorder videos into something I can share with family and friends
over the internet
- sometimes improve them (e.g. deshacking
http://www.youtube.com/watch?v=HYE3KAl8RAQfeature=youtu.be)
- automatically build thumbnails and navigation tree of my home videos
collection
I am experiencing this bug with a CF media. I can mount it manually with
sudo mount -r -t ufs -o ufstype=ufs2 /dev/sdh m
but Dolphin (and Thunar) give me an error trying to mount /dev/sdh1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is another one of these cases where developers do not think of the
consequences of their actions on the common user downstream. Sure, Mr.
Langasek, ia32-libs is a monstrosity, but users prefer a monstrosity
that works for them to the technically elegant solution that you imposed
on them and
Public bug reported:
Dear experts,
with the fresh package buildup (ppa of 17.12), sane-find-scanner finds
scanner (vendor=0x04a9 [Canon Inc], product=0x2759 [MF3010]), but does
not identify any scanner...
see my post http://ubuntuforums.org/showthread.php?t=2194282
I have Ubuntu 13.10,
I experience the same problem as the original poster of question 240955.
Unlike him, I do not have the luxury of testing with 12.04LTS. The USB
scanner (Canon) is not recognized by scanimage -L, even if sane-find-
scanner finds and recognize it properly..
--
You received this bug notification
Public bug reported:
To reproduce:
* open pavucontrol, output devices tab
* move the slider for Built-in Audio Analog Stereo
* listen
Expected result:
*audio feedback (system beep or something) at the newly set level
Observed result:
* audio feedback at the previously set level
In other words:
Since the most recent kernel upgrade I am experiencing these symptoms.
I try:
killall pulseaudio
pulseaudio -D
E: [pulseaudio] main.c: Daemon startup failed.
[27088.699803] hda-codec: out of range cmd 0:5:707:fffc
[27088.701436] hda-codec: out of range cmd 0:5:707:fffc
[27088.707801]
** Changed in: ghostscript (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218350
Title:
stackunderflow in .setdistillerparams
To manage notifications about
On 10/28/2013 10:37 AM, Brad Figg wrote:
This bug is awaiting verification that the kernel in -proposed
Thanks for letting me know, I will do so ASAP.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
WOW,
libx264-123 from saucy-proposed fixed the bug for me as well. It is not
yet in the main saucy repository where the segfault still happens. What
does it take to move the package over from proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, I am back home and can test a bit more. Unfortunately my other
headsets are all 2.5mm and do not fit into the SONY Vaio Pro's 3.5mm
jack. Nevertheless, I am pretty confident that the headset I tested
with is fully functional because it works with both the SONY Vaio Pro
(when booted to
*** WORKAROUND ***
* point your browser to http://localhost:631/printers/PDF
* Administration dropdown, select Modify printer
* enter admin credentials
* select radio button CUPS-PDF (Virtual PDF Printer) next to Local Printers and
click Continue
* on the next page click Continue
* click on
I am experiencing the exact same symptoms since about three weeks.
Uninstalling and reinstalling does not help:
sudo dpkg -P cups-pdf
sudo apt-get install cups-pdf
It says:
Setting up cups-pdf (2.6.1-9)
but when I print, no matter from what application, the result is an
empty 2.2KiB file
On 10/10/2013 09:26 AM, David Henningsson wrote:
The problem here is somewhat lack of testers. We have only one person
with a headset (with alias Yuv) and that person reports that it does not
work. However, the problem might be with that person's headset so I
probably don't want to completely
On 10/08/2013 05:21 AM, David Henningsson wrote:
When you try it in Windows, does it automatically distinguish between a
headphone and headset, or is there some sort of what did you plugin
dialog where you choose manually?
I have never used the headphone in Windows. It seems to recognize the
P.S.:
to install the deb I did
sudo apt-get install dkms
sudo dpkg -i oem-audio-hda-daily-dkms_0.1_all.deb
Will the following command be good enough to revert back once the distro
packages are fixed?
sudo dpkg -p oem-audio-hda-daily-dkms_0.1_all.deb
--
You received this bug notification
On 10/07/2013 05:21 AM, David Henningsson wrote:
Ok, so let's see if we can fix this bug for everyone.
Thanks for the patch. Works better than before but not there yet.
Expected behaviour:
- When there is nothing plugged in, speakers and internal mic should work.
PERFECT!
- Whenever
On 10/06/2013 12:54 PM, Thijs wrote:
This might be a handy workaround for Skype until the pulseaudio bug is
completely fixed:
Thanks Thijs, but I do not need the workaround that you are suggesting
and in my opinion it is bad practice to make a Skype-specific workaround
for an issue that affect
On 10/05/2013 11:13 AM, Raymond wrote:
if the Mic and headphone of your headset works with the SONY Vaio Pro
13 in Windows , the alsa driver can use the presence detect of
headphone node 0x21 to switch the Mic from int Mic node 0x12 to headset
Mic node 0x18
Makes sense! I am really not
://mobile.slashdot.org/story/13/09/28/1955211/eu-committee-votes-to-make-all-smartphone-vendors-utilize-a-standard-charger
Thanks again for helping me configure my notebook properly. This bug
report can be closed as fixed from my perspective.
Yuv
--
You received this bug notification because you
/~hugin/+archive/hugin-
builds?field.series_filter=precise
I am marking this bug as invalid because it is highly unlikely that the
maintainer of the official Ubuntu repository will update an outdated
release. There are good reasons for that.
Sincerely yours,
Yuv
** Changed in: hugin (Ubuntu
Good news. David Henningsson replied to my comment to the people listed
on the patch mentioned in comment #17. For completness, he did not
just ask me to test the three scenarios in comment #18, he also asked me
what driver is used on Windows for this hardware. Because it is a
Microsoft
Retested on David's request.
1) nothing connected
$ sudo hda-jack-sense-test -a -c1
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x17 (Not connected): present = No
Pin 0x18 (Black Mic): present = Yes
Pin 0x19 (Not
Thank you for the continued support and research on the issue.
sudo hda-jack-sense-test -a -c1
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x17 (Not connected): present = No
Pin 0x18 (Black Mic): present = Yes
Pin 0x19
$ sudo modinfo snd-hda-intel
filename:
/lib/modules/3.11.0-8-generic/kernel/sound/pci/hda/snd-hda-intel.ko
description:Intel HDA driver
license:GPL
srcversion: 487D576FC93C49CD204AA81
alias: pci:v1022d*sv*sd*bc04sc03i00*
alias:
I have sent an email, now let's hope for the best. Thank you for
leading me so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228689
Title:
sony vaio pro 13 internal microphone not working
/share/snd-hda-tools/hda_codec.py, line 1023, in __init__
self.fd = os.open(/dev/snd/hwC%sD%s % (card, device), os.O_RDWR)
OSError: [Errno 13] Permission denied: '/dev/snd/hwC0D0'
I also copeid it to my PPA: https://launchpad.net/~yuv/+archive/yuv-stuff
The package conflicts with alsa-tools
I
/etc/asound.conf
Thanks for the link. Edited to the default configuration. I will be
repeating the diagnostic steps requested in comment #1 and post the
updated output.
Little apparent change so far. Audio output still works as expected.
Microphone still not working, neither the internal one
Thank you for your continued help Raymond, it is very much appreciated.
I'll try to answer your questions, but bear with me, I am a n00b as far
as audio is concerned so there are more questions back to you than
answers.
why do you overwrite pcm.default and ctl.default if you are running
Public bug reported:
A number of people are reporting the same issue:
http://ubuntuforums.org/showthread.php?t=2172364
I have lived with it for a couple of months silently, but now audio
recording is becoming a necessity. I don't have much to add, other than
I have gone through the usual
Thank you for the quick reply.
Attached is the output of pactl list
however the two URLs that you pointed me to say This page does not
exist yet. You can create a new empty page, or use one of the page
templates.
** Attachment added: output of pactl list as requested
Correction: the two URLs had a %E2%80%8E at the end when clicked. Once
removed, I got to the inteded destinations and followed the
instructions.
http://www.alsa-
project.org/db/?f=cfb15d2374ed789c7543388ae242666a06488c51
log coming next.
--
You received this bug notification because you are a
I was following the instructions in https://wiki.ubuntu.com/PulseAudio/Log
at the killall command, the computer prompted that an error occured and asked
me to report it. It also promted that /etc/xdg/autostart/pulseaudio.desktop
has been modified
I am using Lubuntu 13.10
--
You received this
the information about the killall prompted error is in bug 1228759
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228689
Title:
sony vaio pro 13 internal microphone not working
To manage
Here is the log. Got the SIGABRT error again when pressing CTRL+C to
terminate the logging.
** Attachment added: pulseverbose.log
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1228689/+attachment/3834212/+files/pulseverbose.log
--
You received this bug notification because you
Alberto, the bug is still there. No grub-efi package listed in
http://cdimage.ubuntu.com/lubuntu/daily-live/current/saucy-desktop-
amd64.list. Whoever has the power to make the change should include
grub-efi on the image to allow for offline-installation as well as
installation on devices whose
Nice to see that somebody has picked this report up. In the meantime,
newer version of the kernel shipped with saucy support the network card
of the SONY Vaio Pro 13. I guess this has defused the issue for network
connected machines. Also, I have been able to dual boot in UEFI.
What worked for
Public bug reported:
The following command was working until yesterday`s update to
Ghostscript 9.10~dfsg~rc1-0ubuntu2 on Saucy.
$ gs -q -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=debug.pdf
-dSubsetFonts=true -dPDFSETTINGS=/printer a.pdf b.pdf
Now it reports the following error:
GPL
Frankly: if a change breaks an existing behaviour, it is a bug, even if
the existing behaviour is an unintended/wrong one in the first place.
Downstream users have relied on the existing behaviour and breaking it
causes pain. In my case, I was using ghostscript to merge customized
books of
The bug I was reporting is actually specific to the Lubuntu LiveCD. I
filed bug 1201101. This one can probably be closed, either because the
original report affects no longer supported releases, or because it is
fixed in subsequent releases. I was able to install Kubuntu and Xubuntu
from their
Public bug reported:
I had to submit this report on a different machine because the machine
affected is not currently connected to the net.
The current (saucy, as of July 13, 2013) Lubuntu LiveCD boots and gives
the user the *impression* that it works on UEFI machines. Then, when
the user is
** Description changed:
I had to submit this report on a different machine because the machine
affected is not currently connected to the net.
The current (saucy, as of July 13, 2013) Lubuntu LiveCD boots and gives
the user the *impression* that it works on UEFI machines. Then, when
Although both 11.04 (Natty) and 11.10 (Oneiric) have reached End Of
Life, this bug seems to be still alive in newer versions of Ubiquity.
It may be a duplicate of bug 1176674. I have encountered something very
similar (I would dare to say the same error) trying to install Lubuntu
13.10 (Saucy)
Something is wrong when a user can't control the automatic start of non
essential services. UbuntuOne starts itself despite me selecting in the
UbuntuOne System Settings not to.
I have done a bit of research and I found a file that seems to be
controlling it in
1 - 100 of 265 matches
Mail list logo
