Public bug reported:
During upgrade to next LTS occurred this Bug
No idea what this package does
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: sgml-base 1.30
ProcVersionSignature: Ubuntu 5.4.0-169.187-generic 5.4.257
Uname: Linux 5.4.0-169-generic x86_64
ApportVersion: 2.20.11-0ubuntu
Public bug reported:
Reason:
We're trying to protect an internal APT source from trivial accidental
modification by users (who do have sudo as root).
Steps to reproduce:
echo '# dummy' > /etc/apt/sources.list.d/dummy.list
chattr +i /etc/apt/sources.list.d/dummy.list
add-apt-repository -y ppa:lo
We're seeing this same issue. The postinst script in the 22.04 package
seems to be missing a few lines that were still there in 21.10, one of
which would be the one that executes systemctl enable pcscd.socket.
--
You received this bug notification because you are a member of Desktop
Packages, whi
The workaround provided by Ronzo is much appreciated, but considering
that this will mostly be relevant in larger environments with central
authentication, keeping the cached credentials openly in the middle of
the home directory may at least open support issues with users wondering
what that file
** Also affects: alsa-lib
Importance: Undecided
Status: New
** Also affects: alsa-utils
Importance: Undecided
Status: New
** Also affects: alsa-lib (Ubuntu)
Importance: Undecided
Status: New
** Also affects: alsa-utils (Ubuntu)
Importance: Undecided
Status
I feel like the update im-config 0.34-1ubuntu1.1 bugged out ibus-mozc on
Wayland.
I'm getting crashes in LibreOffice---and in some other applications
(Gnome shell search bar), the candidate window is not showing up. It
was definitely working at some point before this update.
Could be that I'm wr
Hi,
the first message about lack of permissions is common and should be
harmless. The failure happens possibly with the attempt to get 16 MiB
of memory via call mmap(2). But it is not obvious why this only succeeds
if you are superuser.
So this might too be a red herring and the actual reason for
Hi,
> Is there a way to place a DVD burner into simulation mode as with CD
> recording so as to test the commands without wasting the disc?
Not with DVD+R and DVD+R DL, i fear.
Only DVD-R and unformatted DVD-RW can simulate.
> nodao.log
Now that's a short one.
It can hardly be that growisofs i
... and there is a copy+paste error with
{{{
GET CONFIGURATION
46 01 00 00 00 00 00 00 08 00
From drive: 8b
00 00 00 9c 00 00 00 00
From drive: 8b
00 00 00 9c 00 00 00 00
8 ms
}}}
Of course, the drive replied only once.
--
You received this bug notification because you are a me
Urm. The last stement should have been:
"... i will probably _not_ get to doing it soon."
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dvd+rw-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1757030
Title:
Lite-On DS8A1H Slimline fa
Hi,
attached is a patch which enables SCSI logging to stderr in dvd+rw-tools.
It is based on dvd+rw-tools-7.1.tar.gz (MD5 8acb3c885c87f6838704a0025e435871).
There is no run-time control for this feature yet. Define or undefine
macro Libburnish_scsi_log_to_stderR and run "make" to enable or
disabl
Hi,
> With -tao option, xorrecord has no trouble at all.
I am out of ideas, for now.
> Is there an easy way to dump the raw commands before the one that
failed?
I am not aware whether the Linux kernel has a logging facility for
ioctl(SG_IO). That's the system call by which we perform the SCSI c
Hi,
this time the layer break position was not set by growisofs.
Now i wonder what is the difference between the commands sent by growisofs
and libburn underneath xorriso.
Looking at the source code of growisofs it seems that no command RESERVE
TRACK is sent for DVD+R DL. libburn sends it if it d
Hi,
the problem looks like it is triggered by growisofs' habit to explicitely
set the layer break position. See its message
/dev/dvdrw: splitting layers at 2009552 blocks
and its error message
4115562496/8231090176 (50.0%) @0.0x, remaining 16:15 RBU 100.0% UBU 100.0%
:-[ WRITE@LBA=1ea9d0h f
(only once during the last few weeks,
If I remember it correctly) and is not predictable.
Best regards, Peter
On Mon, 26 Feb 2018, Christopher M. Penalver wrote:
> Peter Schmitt, to see if this is already resolved in your release,
could
> you please update your HWE stack as per
> https://wik
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063895/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063894/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063898/+files/UdevDb.txt
--
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/1705297
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063896/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063897/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063903/+files/xdpyinfo.txt
--
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/17
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063899/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063900/+files/XorgLog.txt
--
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/1705
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063901/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063902/+files/Xrandr.txt
--
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/1705297
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063893/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063890/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063892/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063891/+files/Lspci.txt
--
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/1705297
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063889/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063885/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063887/+files/DpkgLog.txt
--
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/1705
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063886/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1705297/+attachment/5063888/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Tags added: apport-collected compiz-0.9 ubuntu xenial
** Description changed:
The following occurs occasionally (seemingly at random):
After booting and logging in only the background image is shown, and no
action is possbile.
After switching to tty1, logging in a
Still in xenial
affected: xkb-data 2.16-1ubuntu1
│Jan 8 11:49:55 user.warning /usr/lib/gdm3/gdm-x-session[3463 >
Warning: Type "ONE_LEVEL" has 1 levels, but has 2 │
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboar
JournalErrors.txt has been deleted – see
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1738564
Title:
'File/Save As' p
*** This bug is a security vulnerability ***
Public security bug reported:
See the bug report
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
created with ubuntu-bug.
Apport includes the file JournalErrors.txt
This file includes e.g. the following line.
Dez 16 19:11:31 hostname
** Attachment removed: "JournalErrors.txt"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564/+attachment/5023512/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs
On some machines I'm using a 'no change backport' from artfull:
3.26.2-1~ubuntu16.04.1~c42.ppa1 from ppa:dirk-computer42/c42-backport-gnome3
The problem isn't related to this version - so it seems for me to be
solved (or hidden) in a newer version.
--
You received this bug notification because
Public bug reported:
Composing a new mail and selecting in the menu '/File/Save As' should
normally save the composed email message to a local file.
This applies to the current xenial package: 3.18.5.2-0ubuntu3.2 and can
be reproduced on several machines.
ProblemType: Bug
DistroRelease: Ubuntu
Hi,
the initial error report of 2009 is probably due to a hardware problem
in the computers bus controller, or the cabling, or the drive's bus
controller.
> BraseroWodim stderr: CDB: 2A 00 00 01 6C 7E 00 00 1F 00
> ...
> BraseroWodim stderr: Sense Key: 0x0 No Additional Sense, Segment 11
> ...
>
The undocumented location is implemented in the file pkcs11/gkm/gkm-
util.c
gkm_util_locate_keyrings_directory (void)
{
[…]
old_directory = g_build_filename (g_get_home_dir (), ".gnome2",
"keyrings", NULL);
new_directory = g_build_filename (g_get_user_data_dir (), "keyrings",
NU
Public bug reported:
I found keyrings on different locations.
Sometime below ~/.gnome2/keyrings, sometimes below ~/.local/share/keyrings/,
sometimes in both locations.
The README.Debian is only mentioning: .gnome2/keyrings
The man page for gnome-keyring-daemon doesn't document any location.
Th
Correction:
Some windows can be moved (if their menu bar is "thicker" than the desktop menu
bar, and thus can be grapped with the cursor).
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg
** Package changed: ubuntu => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1705290
Title:
all windows are put in the top left cornerThe following packages will
For me it is working below 16.04 if I tweak my system.
1. The udev rules tweak isn't needed any more - it is in the package
version of the file now correct.
2. Check 'lsmod |grep cdc' - below xenial the modules aren't loaded any more
Add to /etc/modules a line with the content:
cdc-wdm
Aft
Public bug reported:
The handling of codepages by gedit is inconsistent and
may corrupt files and/or cause loss of data:
gedit 3.18.3 / Ubuntu 16.04 LTS
If I use the command
gedit --encoding ISO-8859-15
If, for some reason, the (new) input contains an UTF-8 character
(e.g., by typing, or b
Hi,
congrats to the success.
I have to stress, though, that cdrskin and xorriso are not forks of cdrecord
or growisofs, but applications of libburn, an independent implementation
of an SCSI/MMC driver in userspace.
In the end it depends on what the drive's firmware makes out of the SCSI
command
Hi,
yes, DVD-R and DVD+RW are treated quite differently by the drives.
The former is a sequential multi-session medium, the latter is a
random-access read-write medium. Firmware procedures inside the drive
differ. The laser used is the same, afaik. But the dye on the media is
quite surely not the
Hi,
this looks like a bad relationship between drive and medium.
OPC (Optimum Power Calibration) is preparation stage of burning were the
drive makes experiments about the laser settings. The media have an
especially reserved data area for that.
Those experiments did not yield a satisfying resul
Hi,
did you already try -speed=1 in order to get the lowest possible speed ?
-
The growisofs function to set the speed
set_speed_B6h
in
https://sources.debian.net/src/dvd%2Brw-tools/7.1-11.1/growisofs_mmc.cpp/#L1090
is
Public bug reported:
When upgrading from 16.04 to 14.04, the package tex-common 6.04 seems to
have caused problems.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion:
Hi,
growisofs wrote:
> :-[ WRITE@LBA=10h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid
> argument
LBA=10h means that the second WRITE command yielded a failure message
from the drive. The accusation is strange.
I have seen this only with cdrecord yet, when the Linux kernel reported
(fal
Hi,
> growisofs
> ...
> :-[ WRITE@LBA=220h failed with SK=3h/WRITE ERROR]: Input/output error
Regrettably it does not tell the additional info numbers ASC and ASCQ.
But SK=3 means that the drive cannot write to the medium because of
unexpected problems. I.e. not because the DVD would not be writa
The version released to xenial-proposed is fixing the issue
evolution (3.18.5.2-0ubuntu3) xenial; urgency=medium
* debian/control:
- remove the X-Ubuntu-Use-Langpack line rather than commenting it
due pkgstriptranslations not understanding the # (being fixed,
but meanwhile let
** Summary changed:
- locales are missing
+ locales are missing - menu entries and messages only in english
** Attachment added: "Here is a sample screen shot."
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1584538/+attachment/4669276/+files/Bildschirmfoto%20von%20%C2%BB2016-05-24
The problem applies also to the packages in
ppa:gnome3-team/gnome3-staging
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1584538
Title:
locales are missing
Status in evolution pac
Public bug reported:
The localization is missing in evolution-common.
e.g. the file /usr/share/locale/de/LC_MESSAGES/evolution-3.18.mo
The debian version in stretch contain this file.
Comparing the file size of the packages between debian and ubuntu show also
that a huge part of files are missin
Hi,
i am somewhat confused. The fix is part of Debian's packaging
https://sources.debian.net/src/dvd%2Brw-tools/7.1-11/debian/patches/10-blue-ray-bug713016.patch/
(It is theoretically well understood and clearly correct.)
So why can't it stay in Ubuntu ?
--
You received this bug notification bec
Hi,
it is quite sure that you do not suffer from this old bug.
Please file a new bug. Tell what you did with which program,
which drive, which kind of media. Tell what error messages
you get when you try to read the discs.
Please notify me by mail to scdbac...@gmx.net about the
new bug report num
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=89842
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.
The issue affects also in the 14.04.2 - xserver-xorg-input-wacom-lts-
utopic
Comment #8 works also here for fix it.
** Tags added: 14.04.2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpa
Hi,
> It is not that simple.
> The same burn that failed with growisofs here
> https://bugs.launchpad.net/ubuntu/utopic/+source/dvd+rw-tools/+bug/1113679/comments/13
> finishes correctly with cdrecord.
> [...] they all burn
> flawlessly at 4X (1 GB/s). K3B using growisofs (besides never burning
>
Hi,
i got the growisofs log of K3b in a mail of 1.3 MB
From: Federico Tello Gentile <1113...@bugs.launchpad.net>
which does not show up here.
The growisofs run failed with:
> :-[ WRITE@LBA=b47400h failed with SK=5h/END OF USER AREA ENCOUNTERED ON THIS
> TRACK]: Input/output error
This is a
Public bug reported:
Hi,
firstly: thanks for taking care of
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1113679
Secondly: I hate to say it now, but i think a Debian user
just complained about the problem's little brother:
http://forums.debian.net/viewtopic.php?f=10&t=120566
So you do not have a miracle burner which can do multi-session on DVD-R
DL. :))
Well, if i were the maintainer of dvd+rw-tools in Ubuntu, i would flatly disable
the 4 GB check or replace the error message and exit() by a loud warning
message.
(I would also fix
https://bugs.launchpad.net/ubuntu/
Hi,
are you really sure that the medium is DVD-R DL and not DVD+R DL.
DVD-R DL is said to be incapable of multi-session at all. I never
bought one. So i cannot tell what my drives would offer to do with
them.
I would be interested in seeing the output of
dvd+rw-mediainfo /dev/sr0
The 4GB-check
This narrows the set to: DVD-R, DVD-RW, DVD+R, DVD+RW.
(DVD-RAM and DVD+R DL have significantly different sizes.)
You should try a different brand of media. Best a different
type. E.g. try DVD+R if the failing ones are DVD-R.
If all reachable kinds of DVD fail, then consider to exchange
the drive.
Dani, your problem is not related to this old Brasero bug.
You experience problems between drive and medium after
Brasero, libburn, and the drive all accepted the medium
as suitable for writing. The drive performed two WRITE
commands before it complained about the outcome of the
third one.
Further
Hi,
> something to the effect that beyond the first 2 KB the disk is not
empty
Original message texts may help to find out what's wrong.
Currently it looks like the burn programs get no error
indication from the drive, despite it does not burn the
medium properly.
Probably you used my libburn u
Hi,
since the problem will soon be old enough to go to school,
i propose to fix a bug in the libburn plugin of Brasero
which is to see at
https://git.gnome.org/browse/brasero/tree/plugins/libburnia/burn-libburn.c#n558
This line obviously gets a number out of brasero's state:
brasero_jo
Hi,
the drive tells libburn that the medium is not a DVD-RW
but a DVD+R. xorriso forwards this info:
> Media current: DVD+R
> Media status : is written , is closed
The perception of media type stems from "00 1b" in the reply
to the GET CONFIGURATION command
> GET CONFIGURATION
> 46 00 00 00 00
The following policy allows also the unmount and eject:
[Mounting, checking, etc. of internal drives]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-mount;org.freedesktop.udisks2.eject-media;org.freedesktop.udisks2.power-off-drive;org.freedesktop.udisks2.ata-check-power;org.
#9 doesn't help me
I could resolve the problem (below gnome3) with the addition of the following
policy file:
/etc/polkit-1/localauthority/50-local.d/org.freedesktop.udisks2.filesystem-mount.pkla
[storage group mount override]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesyste
still a problem in raring
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/449506
Title:
No GUI option to set screen rotation of greeter
Status in “gdm” package in Ubuntu:
Confirmed
Bug
@Chris Coulson: bug #776490 as noted in comment #1
lockPref is already possible in preference file for firefox
--
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/1081015
Title:
lockPr
I would suggest to think about integrating the debian/icedove patch back to
thunderbird.
The behaviour of thunderbird for lockPref is unexpectedly different from the
firefox behaviour.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thu
I just retest the issue. It seems to be a thunderbird@ubuntu problem.
* I can still reproduce it in thunderbird 24 below ubuntu 13.04.
* I have also "backported" icedove from debian/jessie. Here the problem is not
reproducible and the lockPref statement is working correct.
--
You received this
I just retest the issue. It seems to be a thunderbird@ubuntu problem.
* I can still reproduce it in thunderbird 24 below ubuntu 13.04.
* I have also "backported" icedove from debian/jessie. Here the problem is not
reproducible and the lockPref statement is working correct.
The icedove backport i
Public bug reported:
If thunderbird 24 is used with an lan account - it segfaults
stat("/etc/ldap.conf", {st_mode=S_IFREG|0664, st_size=9584, ...}) = 0
geteuid() = 11000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++
If it runs
Using thunderbird 17 works as before.
Maybe remarkable is that I can see the following console output either on
raring/gnome-shell and precise/unity installations.
(process:4343): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size
== 0' failed
(thunderbird:4343): GLib-WARNING **: g
Also here using lts-raring kernel on precise.
Switching to xserver-lts-raring doesn't help (and breaks other packages like
virtualbox/wine)
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Tags added: precise
--
You received this bug notification because you are a mem
Another workaround is to format the BD-R before use by growisofs,
or to use growisofs option
-use-the-force-luke=spare:none
Whatever, is it so hard for Ubuntu to fix its dvd+rw-tools package ?
Like Fedora did ?
--
You received this bug notification because you are a member of Desktop
Packages,
Hi,
the same problem is reported by
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1113679
I proposed a remedy there:
--
--- growisofs_mmc_orig.cpp 2013-06-14 19:53:51.0 +0200
+++ growisofs_mmc.cpp 2013-06-
Hi,
Frank Griffin reports in
http://lists.alioth.debian.org/pipermail/debburn-devel/2013-June/000928.html
that my proposed change in growisofs_mmc.cpp indeed silences
the error message at the end of growisofs BD-R writing.
Have a nice day :)
Thomas
--
You received this bug notification beca
Hi,
after re-reading this diagnosis of the problem by the
author of growisofs
http://lists.debian.org/cdwrite/2008/07/msg00092.html
i developed a theory.
For details see
http://lists.alioth.debian.org/pipermail/debburn-devel/2013-June/000924.html
I do not want to use up a blank BD-R for growi
Add backport request https://bugs.launchpad.net/bugs/1184572
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1004515
Title:
segfault in accounts-daemon when logging in / gdm crash if user
I have a similar problem as described in
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414
I can confirm that the solution is to upgrade the accountservice
packages.
In my ppa https://launchpad.net/~dirk-
computer42/+archive/c42-backport/+packages I provide a "no change"
back
** Summary changed:
- segfault in accounts-daemon when logging in
+ segfault in accounts-daemon when logging in / gdm crash if user account is
added or deleted
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.
*** This bug is a duplicate of bug 1004515 ***
https://bugs.launchpad.net/bugs/1004515
** This bug has been marked a duplicate of bug 1004515
segfault in accounts-daemon when logging in
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
*** This bug is a duplicate of bug 1004515 ***
https://bugs.launchpad.net/bugs/1004515
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubunt
Maybe related:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1067414
Title:
gdm crashes if a user account is delete
Problem also triggered by installing libvirt-bin and virt-manager which
triggers the add of:
libvirt-qemu:x:124:128:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false
libvirt-dnsmasq:x:125:138:Libvirt Dnsmasq,,,:/var/lib/libvirt/dnsmasq:/bin/false
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubunt
Error message in syslog: gdm-session-wor[4145]: segfault at 50 ip
7f0a30df22ff sp 7499e230 error 4 in
libc-2.15.so[7f0a30d72000+1b5000]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/
Problem still existing
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1067414
Title:
gdm crashed if a user account i
On 05/17/2013 11:20 PM, Matthieu Baerts wrote:
> Ok thank you,
>
> Can you check that you're using Compiz? E.g. by launching this command from a
> terminal which should print something if Compiz is running:
> $ ps aux | grep "[c]ompiz"
>
> If Compiz is running, can you give us more details abo
On 05/17/2013 08:19 PM, Matthieu Baerts wrote:
> Hello and thank you for this bug report,
>
> Is it maybe possible to share a screenshot with us?
> Do you also have this bug if you use the dock without the OpenGL backend?
> $ cairo-dock -c
>
> Or with the default theme?
> $ cairo-dock -d ~/
Hi,
i am the developer of libburn, which would probably be in charge
for burning underneath Brasero in younger Ubuntu versions.
(One can learn from Brasero logs, whether libburn is used as
burn backend. Search for "Libburn".)
There was a bug when the application asked for minimum speed
and the f
Hi,
To my own experience, the code which governs creation and burning of
ISO images on-the-fly is separate from the code that governs burning
of pre-produced image files from hard disk.
(I am developer of libburn and libisofs, not a user of Brasero.
But i once had reason to find out how Brasero m
1 - 100 of 131 matches
Mail list logo
