[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
Submitted upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=122075 ** Bug watch added: Document Foundation Bugzilla #122075 https://bugs.documentfoundation.org/show_bug.cgi?id=122075 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: New Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
Right - I have managed to force over my libreoffice to using ps (uncheck the 'PDF as standard print job format' option, click Okay, and let lo restart). When in 'PS' mode, you are correct that the bug as I have described does not manifest. I conclude that it only manifests when in 'PDF' mode. However, even in 'PS' mode you can see a strain of the bug. Ensure you have in your directory a 'sample.ps' file (can be empty). Follow through steps 1 to 6d (changing pdf to ps). Then click on 'Any Type' and change to 'PostScript'. On my system I then observe that my edited filename in the name type-in field has been changed, and another ps file (probably sample.ps) has been selected in the chooser. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: Incomplete Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
Hmmm - somewhat curious that your setup is locked into ps and mine is pdf with no apparent way of switching. But in step 6-c it is important to click on a file name in the chooser, and then edit it in the type in field. The bug doesn't manifest if you just edit the name type in field to the desired file name. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: Incomplete Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
Okay - your print defaults are to 'print to ps' rather than 'print to pdf'. So to recreate the steps you can either: a) Go to Tools -> Options -> Print -> and enable 'PDF as standard print job format, then re-run the steps OR b) wherever in my steps I say 'pdf' or filename.pdf, change to 'ps' and filename.ps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: Incomplete Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
>I think the bug happens when the dialogue self-flips the type selector to 'Portable Document Format'. Yep ... if I manually flip the type selector to 'Portable Document Format' it loses my desired file name and pseudo-randomly selects a pdf file from the list of files in the folder. So there are actually 2 incorrect behaviours going on: 1) changing type selector to 'Portable Document Format' should not change the file name in the 'name' field IF the user has already made some edits in that field (i.e. has taken the trouble to choose a name) 2) pressing Enter (or Save button) should not trigger the type selector to change -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: New Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] [NEW] Print to File writes to incorrect file
Public bug reported: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description:Ubuntu 18.10 Release:18.10 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: New Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
This screenshot manages to show the problem. Here I have typed in the 'Name' field 'test_2.pdf' when I already have that filename in my folder (as well as the dummy sample.pdf). I then press Enter, expecting to get the confirmation dialogue box asking about overwriting the file. The confirmation box appears, but look at it carefully compared to what the FileChooser GTK3 widget is now showing behind it: the confirmation box shows name 'test_2.pdf' (which is what I typed), and the GTK3 widget not shows 'sample.pdf' (and also has changed the type selector to 'Portable Document Format'. Pressing 'okay' results in 'sample.pdf' being overwritten. I think the bug happens when the dialogue self-flips the type selector to 'Portable Document Format'. ** Attachment added: "Screenshot from 2018-12-10 17-08-18.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+attachment/5220930/+files/Screenshot%20from%202018-12-10%2017-08-18.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: New Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732454] Re: Reply to message composer window opens behind main evolution window
Yep - I'm on Ubuntu 18.04 using gnome-shell/wayland 3.28 and confirm it is now working okay -- 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/1732454 Title: Reply to message composer window opens behind main evolution window Status in evolution package in Ubuntu: Confirmed Bug description: In evolution, open a message which opens a 'message reader' window. In that window press the 'Reply' button - this opens a new 'message composer' window in which to type the reply In 17.10 running under gnome-shell, the composer window is opened, but it also seems that the main Evolution window is also brought to the front ... leaving the newly opened composer window behind in the window stack. Running 17.10 with the old unity does not have this problem So I guess this bug may be a problem with gnome-shell rather than evolution - something is making it ping the main application window to the front. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1732454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732454] [NEW] Reply to message composer window opens behind main evolution window
Public bug reported: In evolution, open a message which opens a 'message reader' window. In that window press the 'Reply' button - this opens a new 'message composer' window in which to type the reply In 17.10 running under gnome-shell, the composer window is opened, but it also seems that the main Evolution window is also brought to the front ... leaving the newly opened composer window behind in the window stack. Running 17.10 with the old unity does not have this problem So I guess this bug may be a problem with gnome-shell rather than evolution - something is making it ping the main application window to the front. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- 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/1732454 Title: Reply to message composer window opens behind main evolution window Status in evolution package in Ubuntu: New Bug description: In evolution, open a message which opens a 'message reader' window. In that window press the 'Reply' button - this opens a new 'message composer' window in which to type the reply In 17.10 running under gnome-shell, the composer window is opened, but it also seems that the main Evolution window is also brought to the front ... leaving the newly opened composer window behind in the window stack. Running 17.10 with the old unity does not have this problem So I guess this bug may be a problem with gnome-shell rather than evolution - something is making it ping the main application window to the front. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1732454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245097] Re: Internal data flow error playing dvds
Hi Ablenzo Its highly unorthodox as a method ... but in this case it gets us out of a hole. - Use packages.ubuntu.com to find the gstreamer1.0-plugins-ugly package from the Trusty series - From that page, 'Downloads' section near the bottom, you can click on 'i386' or 'amd64' link (depending on your architecture) to download the package .deb file (it will take you to a page to choose a mirror site, just pick one that seems to be in your geography) - Do the same for liborc-0.4-0 package - at command line do sudo dpkg -i liborc*.deb gstreamer1.0-plugins-ugly*.deb and you should be done. Enjoy! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1245097 Title: Internal data flow error playing dvds Status in The GStreamer Multimedia Framework: Unknown Status in “gst-plugins-ugly1.0” package in Ubuntu: Confirmed Status in “totem” package in Ubuntu: Confirmed Bug description: Since upgrading to saucy salamander, with totem 3.8.2-0ubuntu1, I have errors playing DVDs. They start playing, but after a little while, I get the Internal data flow error and playback stops. This didn't happen before upgrading ubuntu. The dvds are actually iso files created with ddrescue, but I don't expect that would change things. The same files play without problem in mplayer. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1245097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245097] Re: Internal data flow error playing dvds
Installing version 1.2.2 of gstreamer1.0-plugings-ugly in saucy (by using the latest package from Trusty archive) fixes the problem on my system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1245097 Title: Internal data flow error playing dvds Status in The GStreamer Multimedia Framework: Unknown Status in “gst-plugins-ugly1.0” package in Ubuntu: Confirmed Status in “totem” package in Ubuntu: Confirmed Bug description: Since upgrading to saucy salamander, with totem 3.8.2-0ubuntu1, I have errors playing DVDs. They start playing, but after a little while, I get the Internal data flow error and playback stops. This didn't happen before upgrading ubuntu. The dvds are actually iso files created with ddrescue, but I don't expect that would change things. The same files play without problem in mplayer. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1245097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245097] Re: Internal data flow error playing dvds
My (32 bit) system is showing the same behaviour, and totem gives the following error message each time: ** (totem:7505): CRITICAL **: gst_video_decoder_allocate_output_frame: assertion 'frame-output_buffer == NULL' failed A quick trawl on upstream gstreamer lead me to: https://bugzilla.gnome.org/show_bug.cgi?id=710615 This is marked fixed a few weeks back. I wonder if it can make it through to 13.10 repositories? ** Bug watch added: GNOME Bug Tracker #710615 https://bugzilla.gnome.org/show_bug.cgi?id=710615 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1245097 Title: Internal data flow error playing dvds Status in “totem” package in Ubuntu: Confirmed Bug description: Since upgrading to saucy salamander, with totem 3.8.2-0ubuntu1, I have errors playing DVDs. They start playing, but after a little while, I get the Internal data flow error and playback stops. This didn't happen before upgrading ubuntu. The dvds are actually iso files created with ddrescue, but I don't expect that would change things. The same files play without problem in mplayer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1245097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171578] Re: Unable to Play DVD's in Ubuntu 13.04
I have this problem too, but my totem depends on gstreamer1.0, not 0.10. Could the problem be upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=688803 apparently fixed, though I don't think the code has trickled into the ubuntu repos ** Bug watch added: GNOME Bug Tracker #688803 https://bugzilla.gnome.org/show_bug.cgi?id=688803 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1171578 Title: Unable to Play DVD's in Ubuntu 13.04 Status in “gstreamer0.10” package in Ubuntu: Confirmed Bug description: Many DVD's which played fine in 12.10 will not play in 13.04. An error windoe comes up saying the stream is in the wrong format. Medibuntu and libdvdcss2 are installed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Apr 22 14:42:15 2013 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2013-04-09 (13 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1171578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075478] Re: bluetooth keyboards and mice not working after suspend/resume
This bug is because of kernel upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=52471 All the info is in that bug report, including 2 patches to fix it. In short form, the (doomed to fail by timeout) battery status reporting injects a 5 second delay in keyboard device removal. Due to races in the kernel bluetooth code, this leads the code to remove devices from sysfs in the wrong order. This in turn leads to udev events being sent out with truncated device paths. This in turn causes Xorg evdev to receive the 'remove' events, but ignore them because they cannot match them up. When the keyboard re-connects, Xorg then sees the 'add' events matching a keyboard it thinks it already has, so ignores them ... so your keyboard doesn't work (or mouse too, if bluetooth as well!). IMHO This is NOT a problem in Xorg - it is a kernel issue leading to faulty udev events. Note the Google Chrome people patched their Xorg to work around the issue ... but the real fix should be in the kernel. ** Bug watch added: Linux Kernel Bug Tracker #52471 http://bugzilla.kernel.org/show_bug.cgi?id=52471 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1075478 Title: bluetooth keyboards and mice not working after suspend/resume Status in xserver-xorg-input-evdev: Unknown Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 12.10 I encountered the following problem: I have my apple wireless bluetooth keyboard paired up to Ubuntu, and it works fine when I boot up my laptop (HP EliteBook 8530w) as soon as I hit the login screen. However, if I then suspend and resume my laptop again, the bluetooth keyboard does not respond anymore. According to the bluetooth GUI applet it is still succesfully paired up and connected, and I see the green light on my keyboard blinking a few times when I hit a key for the first time after resume which is also the case when it _does_ work, but I get no response whatsoever from Ubuntu when typing on my keyboard. sudo service bluetooth restart does not work. Please let me know what additional information to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1075478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1055497] Re: Signature inserted twice when replying or forwarding
Apparently upstream this is fixed in 3.6.1 maintenance release. Can this be built and released in Ubuntu main? -- 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/1055497 Title: Signature inserted twice when replying or forwarding Status in “evolution” package in Ubuntu: In Progress Bug description: After a recent upgrade to 12.10 beta 1: I have an e-mail signature with five lines of text: Line A Line B Line C Line D Line E This is inserted properly into new messages. However, when replying to a message, or forwarding a message, it is inserted twice, separated by a blank line: -- Line A Line B Line C Line D Line E Line A Line B Line C Line D Line E ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evolution 3.5.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Mon Sep 24 09:30:21 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release Candidate amd64 (20100928) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash LC_PAPER=en_GB.UTF-8 SourcePackage: evolution UpgradeStatus: Upgraded to quantal on 2012-09-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1055497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993937] Re: Totem can't play some FLV videos encoded by H.264 codec
This is surely a bug in gstreamer. Pitivi can't open such videos either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/993937 Title: Totem can't play some FLV videos encoded by H.264 codec Status in Totem Movie Player: New Status in “totem” package in Ubuntu: Confirmed Bug description: If i open h.264 video with totem it doen't play it showing in properties that video have a 0x0 pixel resolution. Browsing scroller i can see that sound works. Parole,VLC works normaly. This proble occures after upgradin to 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Thu May 3 16:15:18 2012 EcryptfsInUse: Yes InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to precise on 2012-04-28 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/993937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 545346] Re: [upstream] [3.3] Sound is Duplicated and produces echo
Libreoffice 3.5.3 (recently in the Ubuntu Precise repos) fixes this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/545346 Title: [upstream] [3.3] Sound is Duplicated and produces echo Status in LibreOffice Productivity Suite: Confirmed Status in The OpenOffice.org Suite: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: The current workaround is to: Immediately switch (after starting your video) to the Slides view and switch back. This will kill the double audio. --- Binary package hint: openoffice.org Using Lucid Lynx and OpenOffice 3.2.0. openoffice.org-presenter-console using two monitors sound from embedded movie is generated (fed to speakers) from both the console presenter pane and the projection screen. This is a new bug, or rather a regression to a problem when presenter console was first introduced. Sound should only come from the projection screen Let me know if you need more debugging information, or testing. This bug also exists in Karmic (x32) using the PPA-Scribblers repo builds - CH ProblemType: Bug Architecture: amd64 Date: Tue Mar 23 15:16:07 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Package: openoffice.org-presenter-console 1.1.0+OOo3.2.0-4ubuntu1 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: openoffice.org Uname: Linux 2.6.32-17-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/545346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
